Research, evaluate, design, test, implement, monitor, and iteratively improve a Cloud FinOPs model that can act as a starting point for bespoke application to a variety of initiatives relying on cost-recovery and automated reporting. This initiative will be expected as part of any operational projects in efforts of implementing cost-control, fiscal stewardship, and potentially recouping/defraying overhead costs on a fair and equitable basis reflected by actual usage.
⚒️ Tangible Outcomes
Scope
INCLUDED:
a. Environmental survey: internal to GoC of existing technologies/methods; external to other entities; Explore costing models used by other 3rd party providers and how this can be applied to FINOPs development.
b. Data Modelling: granularity to support equitable/fair use billing to clients and to support tiered access costing as well as report automation.
c. Development: Incremental development based on user-expected outcomes and supporting features. Includes SSO, oAuth, Active Directory integration, cloud agnostic templating / containerization.
d. Testing: Phased internal and external testing and part of refinement feedback process. Determine categories and patterns of traffic use and load.
e. Submission: sending findings, MVP, etc. Onwards through ATO process for methodology approval.
EXCLUDED:
Immediate applicability to all projects. Will start with the OpenRouteService (ORS) as a case-scenario and assume that this will be deployed in the GCP.
Priority Alignment
Detect, Understand, Act (DUA)
DUA Requirements
1.2.1 Establish an enterprise platform for public health intelligence integration to facilitate data access and insight development within the Agency.
1.2.9 Building a Data-as-a-product gateway. This would be characterized by
1) Using customizable, multi-purpose data;
2) Located on the cloud and would not require installation on a local server;
3) Would include built in support that considers features such as data governance, stream support, and cloud support;
4) Integration with HL7 or later standards;
5) Provision of adapters for exchanging data with existing systems.
1.3.2 Establish Protected B cloud infrastructure for public health intelligence in partnership with Health Canada and Central Agencies to facilitate the sharing of data with external public health partners, FPTM and FNIM jurisdictions.
1.3.3 Implementation of a public health-centric multi-cloud strategy, designed for secure integration with domestic and international external public health partners, in collaboration with partners in industry, and FPTM and FNIM jurisdictions.
1.3.6 60% of baseline surveillance data systems are interoperable.
Project Alignment
1.2.1: FINOPs is a cornerstone in a robust enterprise platform in that it shows system maturity, ability to be fiscally accountable in tracking usage and justify operational expense requests using empirical evidence.
Management Response & Action Plan (MRAP)
MRAP Recommendation
8.65.5 The Public Health Agency of Canada should finalize the improvements to its information technology infrastructure to facilitate the collection of timely, accurate, and complete surveillance information from provinces and territories, both during and after the COVID-19 pandemic. The agency should establish timelines for the completion of these improvements.
Action Required
Full Implementation of selected data sharing solution(s) by March 31, 2025
Project Alignment
In order to comply with mandate under 8.65.5, improving fundamental technologies for timely, accurate, and complete surveillance information services – the FINOPs is needed for operational sustainment and accurate/fair funding.
Success Criteria
Using the OpenRouteService (ORS) as a test candidate to apply FINOPs, success will be the establishment of a semi-reuasable front-end and back-end code that can restrict access via the webpage and/or the Web API.
Creating a re-usable data model that permits fine grain tracking and automated reporting.
Definition of “Done”
Creation of a fully-functioning FINOPS MVP applied to the ORS project that is able to issue tokens via oAuth and track per-call usage and store it in a suitable data table which will feed an interactive tracking/monitor dashboard and issue out usage warnings and monthly billing based on fair division of resource costs based on actual access.
Deliverables
Planning:
Determining correct front- and back-end technologies – with a preference towards OOTB Open Source.
Data Modelling: Physical and Logical models determined for testing with ORS
Testing:
Creating code to support the front- and back-ends in react.js
Determining Accessibility and OLA suitability and programming from the outset to meet these requirements. Obtain a WGAC score and do the Accessibility checklist.
Set up a RMDBs or a noSQL database and ensure that all scenarios are captured including verifying business rules account for all scenarios. Create an automated reporting pipeline is in place including an interactive dashboard.
Timelines
Key Milestones Target deadline
Planning and determining roles and responsibilities September 2024
Initial research completed Oct 2024
Testing all components Nov 2024 (decision point)
Collaborators
Team
Geordin Raganold (lead and front-end Dev)
Simardeep Singh (Cloud Arch)
Sami Atoui (front- and back-end dev and DB analyst)
Zachary Nick (motivator)
Andrew Nice (PM)
Stakeholders
Internal clients that will be onboarded with projects that consume cloud resources
TB (potentially) via sharing success or model
Users
Any client onboarded and/or user of exposed web services via Web API (i.e. geocoding, routing, etc.)
Responsibilities
The Interoperable Platforms and Produce Management unit will be responsible for:
•
The client’s team will be responsible for:
•
Resources
Open sandboxed environments such as the GCP
Human resources: minimum x2 Web devs/DBAs with minimal oversight
Risk Assessment
Risk 1: Moving Cloud environments. If the process and code is too integrated to the Google Cloud Platform, will require overhaul and cobbling if move operations to Azure. Mitigation: decouple the technology, process, etc. to a level of abstraction (80%) so customization can occur from this level of effort instead of re-creating from scratch. Impact low; Likelihood: low.
Risk 2: Data Quality: cannot obtain granular level data for meaningful reporting. Case and point: if a tech or API does not allow to track on a project or individual level or the sub resources used, it will aggregate the resource cost and may be unfair. Mitigation: for example, geospatial data resources and services can be tracked with custom JSAPI access. Will require so development and understanding of the JSAPI. Otherwise, reporting only as good as the data collected during the oAuth and/or issuing of tokens. Impact: low; likelihood: medium.
👨💻 Intangible Uutcomes
Lessons learned from other departments in establishing FINOPS
👱 Business Client
Zachary Nick
🎯 Milestone
M2 - Develop Strategic Plan
🟢 Start Date (expected)
01-09-2024
🔴 End Date (expected)
01-09-2025
📋 Detailed Description
Research, evaluate, design, test, implement, monitor, and iteratively improve a Cloud FinOPs model that can act as a starting point for bespoke application to a variety of initiatives relying on cost-recovery and automated reporting. This initiative will be expected as part of any operational projects in efforts of implementing cost-control, fiscal stewardship, and potentially recouping/defraying overhead costs on a fair and equitable basis reflected by actual usage.
⚒️ Tangible Outcomes
Scope
INCLUDED:
a. Environmental survey: internal to GoC of existing technologies/methods; external to other entities; Explore costing models used by other 3rd party providers and how this can be applied to FINOPs development. b. Data Modelling: granularity to support equitable/fair use billing to clients and to support tiered access costing as well as report automation. c. Development: Incremental development based on user-expected outcomes and supporting features. Includes SSO, oAuth, Active Directory integration, cloud agnostic templating / containerization. d. Testing: Phased internal and external testing and part of refinement feedback process. Determine categories and patterns of traffic use and load. e. Submission: sending findings, MVP, etc. Onwards through ATO process for methodology approval.
EXCLUDED: Immediate applicability to all projects. Will start with the OpenRouteService (ORS) as a case-scenario and assume that this will be deployed in the GCP. Priority Alignment Detect, Understand, Act (DUA)
DUA Requirements 1.2.1 Establish an enterprise platform for public health intelligence integration to facilitate data access and insight development within the Agency. 1.2.9 Building a Data-as-a-product gateway. This would be characterized by 1) Using customizable, multi-purpose data; 2) Located on the cloud and would not require installation on a local server; 3) Would include built in support that considers features such as data governance, stream support, and cloud support; 4) Integration with HL7 or later standards; 5) Provision of adapters for exchanging data with existing systems. 1.3.2 Establish Protected B cloud infrastructure for public health intelligence in partnership with Health Canada and Central Agencies to facilitate the sharing of data with external public health partners, FPTM and FNIM jurisdictions. 1.3.3 Implementation of a public health-centric multi-cloud strategy, designed for secure integration with domestic and international external public health partners, in collaboration with partners in industry, and FPTM and FNIM jurisdictions. 1.3.6 60% of baseline surveillance data systems are interoperable.
Project Alignment 1.2.1: FINOPs is a cornerstone in a robust enterprise platform in that it shows system maturity, ability to be fiscally accountable in tracking usage and justify operational expense requests using empirical evidence.
Management Response & Action Plan (MRAP) MRAP Recommendation
8.65.5 The Public Health Agency of Canada should finalize the improvements to its information technology infrastructure to facilitate the collection of timely, accurate, and complete surveillance information from provinces and territories, both during and after the COVID-19 pandemic. The agency should establish timelines for the completion of these improvements. Action Required Full Implementation of selected data sharing solution(s) by March 31, 2025 Project Alignment In order to comply with mandate under 8.65.5, improving fundamental technologies for timely, accurate, and complete surveillance information services – the FINOPs is needed for operational sustainment and accurate/fair funding.
Success Criteria
Definition of “Done”
Deliverables Planning:
Collaborators Team Geordin Raganold (lead and front-end Dev) Simardeep Singh (Cloud Arch) Sami Atoui (front- and back-end dev and DB analyst) Zachary Nick (motivator) Andrew Nice (PM)
Stakeholders Internal clients that will be onboarded with projects that consume cloud resources TB (potentially) via sharing success or model Users
The client’s team will be responsible for: •
Resources
👨💻 Intangible Uutcomes
✔️ Feature List
⛔ Dependencies
No response