Ismt s-599 Capstone Seminar in Enterprise Systems Summer 2015 Team 3



Download 214.01 Kb.
Page8/12
Date08.01.2017
Size214.01 Kb.
#7835
1   ...   4   5   6   7   8   9   10   11   12

4.2Solution Deployment

Migration Steps


The project will be focused first on business expansion by offering a new service. However, all of the work executed for this function will be reused to facilitate the merger integration and the ultimate replacement of the monolithic systems.

Pilot Phase


The AHC application rollout will be to cardiac patients first then incrementally extend to all departments over a 6-month period. Testing of the application and feedback to the teams will be done during this phase. The pilot phase will start after the 5th development Sprint and include the following user groups:

All of the test subscribers and the providers will be in one geographic location to simplify integration with existing external providers. The pilot run will have the following stages:

  1. Enroll home healthcare providers.

  2. Train internal users.

  3. Provide certification of competency of external providers.

  4. Enroll cardiac patients only.

  5. Assist to activate patient medical devices.

  6. Verify patient is using third party data aggregator for providing data.

  7. Ensure domain experts (data scientists, doctors and medical informatics) are analyzing and viewing patient's near real-time health data.

Go-Live


Once the pilot phase is complete, the experience and outcome of trial period will be analyzed and corrections will be made in the system before Go-Live. Following are the key steps for Go-Live:

    1. Get system ready: Extensive testing to make sure that system will at least support basic features.

    2. Set marketing ready: Marketing and promotional activities should be ready at the same time the AHC service is ready.

    3. Start visibility of the process: Setup all dashboards and monitoring tools to ensure the entire visibility of the platform and services, engineering and operation, expert inputs and continuous improvement. Revenue generation visibilities will be also very key along with continuous user feedback monitoring.

Project Risks


Risks

Impact

Probability

Detail

Depending on third party provider

High

Low

This project depends on third party data aggregators. The system will be useless if those data providers refuse to provide data.

Partnership with other small provider

Medium

Medium

Risk can be associated with the partnership of GlocoHCP with Nursing, and Ambulatory Care provider. In case those people refuse to join the initiatives, it will be difficult to manage the operation.

Marketing and User subscription

High

High

If marketing fails to bring customers, this project will not return back its investment.

DevOps skills shortage

High

Medium

Required to build internal resources for DevOps.

Significant Operations overheads

Medium

High

Properly plan microservices so that it will not be too granular.

Duplication of effort

Medium

High

Each microservice needs data and rules, which can be duplicated among many services if it is not maintained.

Distributed system complexity

Medium

High

Maintain guidelines and principles with effective tool chains.

Testability challenges

High

High

Idiomatic microservices involves placing less emphasis on testing and more on monitoring so we can spot anomalies in production and quickly rollback or take appropriate action.

Asynchronicity is difficult

Medium

High

Manage asynchronous operation using event notification rather than process notification.

4.3Operational readiness

Release Management


Component

Usage

Sprint Planning, Bug Tracking

Jira24 will generate development and support tasks. Engineering bugs and features will be tracked here.

Release Management and Deployment

Chef25 will run every 20 minutes to check for updates, and will update server instances with current code and configurations as needed.

Change Management


GlocoHCP’s existing change management process for IT will be used including its current investment in ServiceNow (See Glossary). TIP will participate in GlocoHCP’s Change Advisory Board (CAB) meeting to submit and approve changes for the new microservices and AHC changes.

Operational teams will be assigned a CTASK (change task) in ServiceNow once the change is approved. The CTASK will specify the exact steps to make the change, the back out plan (or Fail Forward26 plan), and the change window.



The operators will use ChatOps to discuss the status of the changes or any issues in real-time during the release.

Performance Requirements

4.3.1.1Customer Satisfaction (Anywhere Healthcare)


Patient satisfaction surveys will be used to ascertain the performance and overall value the patients are receiving from the new service. Patients will also be given the opportunity to give immediate feedback the service provided by AHC system. The GlocoHCP customer satisfaction and quality assurance group will also conduct a semi-annual survey, and analyze the results to determine the patient satisfaction of the AHC program. This survey will focus on the following:

  • Ease of use of Anywhere Healthcare

  • Satisfaction of the level of service provided by agents and nurses

  • Patient’s current health versus their health at the start of monitoring

  • Patient’s overall relationship with their doctors and hospital

4.3.1.2Response Time


TIP will provide GlocoHCP with a quarterly review of the uptime of the services for the first year of service. The information will be based on the TIP-installed monitoring system and will exclude any GlocoHCP mandated outages. If TIP needs to be engaged during this first year of production, the following thresholds will be used:

Priority

Descriptions

Response Time

1

Critical – Entire Service Outage

2 hours

2

High – Individual Component Outage

6 hours

3

Medium – Localized system issue

Next Business Day

4

Low – Reporting errors

Two Business Days


Download 214.01 Kb.

Share with your friends:
1   ...   4   5   6   7   8   9   10   11   12




The database is protected by copyright ©ininet.org 2024
send message

    Main page