Determine options for engaging IBM per their repeated offer

[scayzer]

Describe the issue IBM initially helped us with our Cloud Adoption Patterns initiative (within Enterprise Services), specifically in deploying the EPIC (Environmental Assessment Office) application on OpenShift, on IBM Cloud. The IBM team continues to offer help with Proof-of-Concept work, non-billable (undoubtedly with a view to paving the way for revenue generating engagement).

Likely candidates for IBM to help us with:

• Application Portfolio analysis to determine strategies for migrating workloads to cloud;
• Design of a Managed Cloud Service for BC government - which capabilities should and could be developed internally, which could be outsourced?
• Design and management of our Early Adopter Program - how to maximize the learnings and benefits.

Which Sprint Priority is this issue related to? The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?

Additional context Add any other context, attachments or screenshots

Definition of done

• Meet with IBM team to discuss possible options for engagement;
• Review topics discussed, and options that look promising, with Cloud Pathfinder leadership team;
• Develop a Decision Note for CP leadership, recommending best option(s) for engaging IBM.

[ActionAnalytics]

Park until after MVP, flag for attention of Enterprise Architecture Branch, Hosting Application Development Framework (HADF), Application Portfolio Summary

[scayzer]

Have moved this forward while waiting for blockers on sprint priority items - met with IBM, then with Mac and Greg, then with Jeff Card. Meeting scheduled with all parties (2020-11-17) to initiate engagement with IBM for the following: Initially help Mac and Greg with their high-level application portfolio review, refining this to the point where it can be applied to the NRM portfolio and will meet in the middle with the current lower level review of Forests apps that Jeff Card has underway.

Opportunity to inject some Cloud Pathfinder requirements into these review processes. Example:

• If new apps were directed to target cloud (either SaaS or build on containers, serverless or PaaS) then how many would go to cloud in the next 12-18 months?
• If major releases of existing apps were directed to port to cloud if feasible, then how many would migrate to cloud in the next 12-18 months?
• What volume of data could move to cloud storage options without incurring latency issues?
• What additional volume of data could move to cloud with affordable solutions to address latency issues?
• Will run these by Mac and Greg to see if they have other ideas.