Integration Project

9/10/2015

Intake Process

General Intake Process

Separate but similar process based on who does the work

• Project intake if the interface team does the work

• PaaS intake if the customer team does the work

2

Project Intake Process

DISCOVER

Define scope and requirements

•Receive integration project request•Acknowledge and record request in Innotas (<5 minutes)•Setup discovery meeting to identify high-level scope and introduce our process (~30 minutes)•SLA to have this meeting is 3 business days

•Requestor to complete intake form and provide documented requirements and scope•Discuss feasibility based on needs and timing (<10 minutes)

ASSESS

Solution design, Roles and responsibilities

•Setup detailed assessment meeting to (~60 minutes)•Collect requirements: functional, technical, testing, security, resource, governance•Discuss high-level design options and integration patterns•Identify team roles and responsibilities, and other team dependencies (security, testing etc…)•SLA to have this meeting is 5 business days after requestor provides documented requirements and scope

PLAN

Timeline and Funding

•If project is approved and funded, then…•Integration team assigns prioritization•Negotiate timeline: phases, milestones and start date•Interface team to provide a ballpark estimate

•Allocate resources•Schedule integration project kick-off

3

ESB Intake - Project

4

PaaS Intake Process

DISCOVER

Define scope and requirements

•Receive integration project request•Acknowledge and record request in Innotas (<5 minutes)•Setup discovery meeting to identify high-level scope and introduce our process (~30 minutes)•SLA to have this meeting is 3 business days

•Requestor to complete performance sizing form•Discuss feasibility based on needs and timing (<10 minutes)

ASSESS

Performance and sizing metrics

•Setup detailed assessment meeting to (~60 minutes)•Analyze performance sizing estimates•Discuss policies and standards: environments, deployments, security, governance, support and maintenance, change control•Define team roles and responsibilities•Discuss timeline and phases•SLA to have this meeting is 5 business days after requestor provides documented requirements and scope

PROVISION

Access

•If project is approved and funded, then…•Provision users for Mule access•Establish support levels and contact communication•Review our environment and deployment policies

5

ESB Intake - PaaS

6

General Approval Process

During the intake process we will discuss project approvals

All projects should be approved before our team can allocate resources to your project

7

IT Approval Process - DRAFT

The number of hours will determine the approval process

Executive Director approval is required for projects between 40-

200 hours

Joe Bengfort must approve projects between 201-500 hours

Committee approval is required for projects > 500 hours

8

IT Approval Process

9

Medical Center IT Approval Process

The number of hours will determine the approval process

Director approval is required for projects between 40-200 hours

Heidi Collins and Joe Bengfort must approve projects between

201-500 IT/CS hours

CTG approves projects over 500 IT/CS hours

10

Intake: via eMail, phone,

SN, water cooler, ...,

Assess

Scope

Estimate costs:

IT/CS H/SIT/CS Labor

Negotiate Timeline

CTG

> 500 IT/CS Hrs

with exceptions

Heidi C./Joe B.

200-500 IT/CS Hrs

BCD .pptor

BCD Light .xls

IT/CS Project Intake Work Flow Through to Approval

Size (IT/CS Hrs):< 200 (very small)

200 - 500 (small)501 - 1000 (medium)

1001 - 5000 (large)> 5000 (very large

Directors

40-200 IT/CS hrs

Heidi C./Joe B.

Service Continuity all sizes; with exceptions

Scoring and Prioritization

Governance: CTG: Care Technology Governance Committee

BCD: Business Case Document IT/CS: Information Technology / Clinical Systems H/S: Hardware / Software