team 4: ash shrivastav, david delong, eric mathiasen, subhasis datta “the clinic of the future is...

Team 4: Ash Shrivastav, David Delong, Eric Mathiasen, Subhasis Datta

“The clinic of the future is where the patient is, not where the doctor is.”

Logos are trademarks of their respective owners

BUSINESS JUSTIFICATION

• GLOCO-PAL experience will position GLOCO well for the branding, support and launch of consumer products.

• G-COM platform will create opportunities for additional health records and diagnostics services.

New Market Opportunities Financials

Bad News:

• R&D Investment total of $61 million applied against the first three years of sales

• Non-R&D operating costs of abot $25 million per year

• First year projected net loss of over $40 million

Good News:

• Profitable by second year

• Full ROI by end of year three

• Total net profit of over $275 million against gross revenues of over $900 million over the course of the first five years.

1. One time sale of mHealth Products (the

product component)

2. Recurring revenue from reporting of data

(the service component).

New Revenue Stream

2

Logos are trademarks of their respective owners 3


STAKEHOLDERS

4

Involvement Stakeholders

Designs and delivers overall GCOM solution Creates software for solution Provisions for cloud hardware resources

mHealth Product Development Team

No involvement with project implementation but is held accountable for overall success of the project

Receives reports from participants Provides input to the design process Provides feedback regarding the solution

mHealth Executives

Provides, acquires resources to support project Receives reports from participants Provides input to the design process Provides feedback regarding the solution Advises regarding change and risk Suggests course corrections as needed Monitors health of project Reports to supervisory stakeholders

Project Manager

Holds explicit responsibility for project success and is held accountable for success Acts toward supervising and advisory levels as those levels act toward the participant level:

provides resources, reporting, input, advice, and so forth.

GLOCO CEOGLOCO CFOGLOCO CTOGLOCO CIO


GOVERNANCE / ORGANIZATIONAL CHART

5


CHANGE MANAGEMENT

6

During Initial ProjectDuring the initial project all changes in project scope must be approved by the Governance Board.

Ongoing Post-ImplementationPost-implementation, a change review board will be created comprised of:

• Project Software Lead• Architect• QA representative • Executive team representative


RESOURCES

7

Roles Responsibilities Number Required PhasemHealth Sponsor(Senior GLOCO Leadership Team)

•Directs what the new subsidiary aims to achieve with the new service. •Keeps a track of the progress and intervenes if necessary.

N/A Pre-Implementation

Stakeholders Serves on advisory board, works to assure cooperation between departments and clears away roadblocks.

N/APre-Implementation

Project Manager • Works with Stakeholders and Product development team in understanding business needs and transforming into technical details with better project timelines. Manage deliverables, staff, budget, and additional resources assigned to the project.• Initiate corrective action when necessary.

1Pre-Implementation

Software Engineer Responsible for development of GCOM4

Pre-Implementation / Post Implementation

Amazon Architect Consultant

Designs architecture and advises team of best practices for Amazon cloud computing.

1Pre-Implementation / Post Implementation


RESOURCES

8

Roles Responsibilities Number Required PhaseClinical Software Engineer

Develops firmware to allow GLOCOPAL devices to communicate with GCOM 1


Business Analyst Develops business and functional requirements.

2 Post Implementation

Web Developer Develops web interface for providers, patients and mhealth

1 Pre-Implementation / Post Implementation

Quality Assurance Analyst

Develops quality of service requirements. Tests the service and provide appropriate

feedback.2


GLOCO CRM Architect Designs architecture and advises team of best practices for GLOCO CRM application.

1 Pre-Implementation

GLOCO CRM Software Engineer

Develops software to interface with GLOCO CRM application

1 Pre-Implementation

mHealth IT Support Overall customer support for providers and patients

5 Post-Implementation

Trainer Provides end user training Sales, Customer Support on applications.

4 Post-Implementation


GCOMArchitecture

9


TIMELINE

10

6/1/2013 10/31/2014

July October January April July October

June - JulyPlanning

August - SeptemberDesign

October - JuneImplemenation

June - AugustTesting

September - OctoberRelease

JulyRequirements

SeptemberSpecifications

OctoberAmazon Environment Setup

DecemberDatabase Creatioon

NovemberGLOCO-PALIntegration

JanuaryGLOCO CRM/ERP

Provisioning Integration

FebruaryHealthVault Setup

and InterfaceJune

Smoke Testing

JulyOperational Acceptance

Testing

AugustPilot Testing

SeptemberTraining

OctoberDeployment

OctoberMaintenance

DecemberGLOCO CRM/ERP

API finalized

JulyGLOCO CRM/ERPAPI discussions

MayDeveloper

Bug Fixes and Unit/Integration/Performance Testing

MarchHealth Information

System Creation

JuneQA Regression and User Acceptance

Testing

AprilReport Server

AprilmHealth Website


TIMELINE

11

Milestone Dependencies Deliverables Duration Due DateBusiness Requirements 2 Months 7/31/2013

GLOCO ERP/CRM API definition discussed and requested

Requirements specification document.

Technical Requirements 2 Months 9/30/2013 Technical specification

document.

System Development 8 Months 5/31/2014GLOCO ERP/CRM API finalized and provided

Installation SoftwareSource Code.GLOCO Integration Documentation.mHealth System Documentation.mHealth Developer Documentation.

Training 1 Month 9/30/2014

Full Deployment 1 Month 10/31/2014 User Documentation

Installation DocumentationTechnical DocumentationTraining DocumentationDisaster Recovery Plan

RISK AND MITIGATIONRisk Probability Severity Mitigation

Unfavorable acceptance of new webinterfaces and poor user adoptionrates.

High High mHealth will implement feedback program during the UserAcceptance Test phase to obtain user feedback forimprovements. Pilot release will also provide opportunity toget first-hand comments from users on how well it will suitthe user needs.

Inadequate trainee participationreduces training effectiveness

Medium Medium mHealth will be providing two repeated in-person training sessionsand provided recorded trainings for absent or new staff. Inaddition, we’ve put forth an extensive communications planthat focuses on functions and individuals, companywide.

Schedule overages High High • Analyze critical path in task schedule• Utilize fast tracking where necessary• Allow for some schedule slack• Advisory board• Bonus Pool

Cost overages High HIgh • Cost analysis done on each hardware and software component• Employee resource assignments are balanced across tasks so

as to reduce or eliminate the need for overtime hours.

ICT resource constraints Medium High Have an outsourcing organization in place if more labor is neededWork with key stakeholders to make sure resources will be available for the project

Resource shortage Medium High GLOCO resources are currently focused on other ERP activities and this could cause us to miss our initial schedules

The cloud strategy related risks are due to lack of SLAs, uncertainty of availability, concern over data security, and loss of organizational management over own assets.

High High These issues can be addressed by working closely with AWS as they are one of the most reputed service providers in the industry

12

Risk Probability Severity MitigationUnspecified Project Requirements

Project High Thorough identification of necessary functionality during Inception phase.

Input from all affected entities within the business.

Signoff by all stakeholders before Integration phase commences.

User buy-in High High End users should be shown the Portals benefits in a tangible way.

Training

User adoption High High Steering committee

Communication

Change management

Project Schedule Impacted by Operational Responsibilities

Project High Frequent communication among project team members on current and future workloads.

Weekly project status updates to identify slippages and problem areas early.

User Acceptance Project Medium Frequent communication about the project.

Demos and other “pre-training” oriented informational sessions.

User adoption/rejection

High High Steering committee

Loss of Network connectivity

Low Medium Cache logs

Helpdesk / Toll-free number for mHealth

RISK AND MITIGATION

13

Risk Probability Severity MitigationNetwork bandwidth dictates speed of access to the order database, which could lead to variable performance of the application

Medium Medium dedicated T1 lines for efficient accessibility

Data Loss High Low Drills to simulate equipment failures

Change committee

Network monitoring

Backups

RISK AND MITIGATION

14


USER ENABLEMENT / ONBOARDING

15

Pilot TestThe mHealth Division will conduct a controlled “Pilot Test” to help shake out early issues.

Initial SetupInitial Provider setup will be made at the time of sale.

Online HelpPrior to the Pilot Test, the mHealth Portal will have Online Help content made available for the two external interfaces.

Online TrainingIn addition to the Online Help section, web-based training screens for both providers and patients will be available.

Onsite TrainingOnsite training for providers that exceeds the scope of initial setup will be available on a service-fee basis.


SYSTEM MANAGEMENT

16

Ongoing ManagementmHealth will continue to improve its service based on the user feedback. System changes will be staged and

tested first in development using test data. From there, they will be moved to a Quality Assurance (QA)

environment for further testing before final deployment to production. All stakeholders and affected

departments will be alerted to pending changes and notified of their success or failure post deployment.

Revision ManagementVersion control will be implemented as part of both development and operational management processes. A

disk image of the original configuration and database backups will always be maintained for rollback in case

of failed deployments. Each change phase will require sign off by stakeholders.

Monitoring and MaintenancemHealth will require ongoing monitoring of its service and maintenance to ensure continuous availability.

mHealth will set up daily automated testing of critical integration components.


SUCCESS METRICS

17

Revenue• 20% per annum growth in GLOCO-

PAL sales

• Net profit in second year

• Positive ROI by the end of third year

Market Adoption• 100,000 new accounts for the first

year

• 10 providers per month with increments of 2 per month

Employee Feedback• Ease of use

• Applicability to work activities

• Responsiveness

• Suggested improvements

• Simplicity

User Adoption• 5000 registered users per day

• 5000 patient & provider logins per day


SUCCESS METRICS

18

KPI Reporting• Providers offering mHealth

• Number of patients per provider

• Devices Sold

• Device usage activity

• Number of patient & provider logins

Employee Performance• Training Scores

• Customers per minute

Implementation Metrics

• Project cost variance <15%

• Project Schedule variance < 15%

Training• Complete training on schedule for

95% of employees

• Positive training feedback from 80% of trained employees


DEMO

19

www.glocomhealth.com

http://www.glocomhealth.com/


Have a healthy day!

20

team 4: ash shrivastav, david delong, eric mathiasen, subhasis datta “the clinic of the future is...

Documents

project implementation

project success

initial project

project scope

respective owners resources

better project timelines

solution mhealth executives

new service