These are the risks towards the R3 program across different projects and how the PMC team is managing the risk mitigations and contingencies.
|WORKSTREAM||PMC / R3 AP||RISK DESCRIPTION||IMPACT DESCRIPTION||IMPACT
|PROBABILITY LEVEL||PRIORITY LEVEL||MITIGATION NOTES||OWNER||ETA|
|Give a brief summary of the risk.||What will happen if the risk is not mitigated or eliminated?||Rate
1 (LOW) to
1 (LOW) to
|(IMPACT X PROBABILITY)
Address the highest first.
|What can be done to lower or eliminate the impact or probability?||Who's responsible?|
|E&O||PMC||Refined version of H1 & H2||Will be working in abstract & CSP implementation||4||4||16||Prioritize to draft out H1 and H2 to plug them to Milestone Deliverable||Raj, Hrvoje and Khadija||44209|
|EDS||PMC||Ingestion Framework and Workflow||With no ingestion framework and workflow available EDS functionality can't be delivered||5||2||10||Closely work with EPAM to assess on their ingestion framework and Alan H||Jacob & Ash||44209|
|Data Loading||PMC||No deliverables with defined dates||Data loading team must be ready to leverage Ingestion framework to validate the assumptions||5||5||25||Prep and curate test data
Continue to refine Manifest Generation script
Bake in Manifest rules
|OpenVDS||PMC||Lack of environment with DMS code||Not able to test until Azure / AWS is ready by mid of January||3||4||12||Azure is working to see how they can unblock. Trying to schedule meeting with this team as well||Dania K and Marius||44227|
|Manifest Ingestion||PMC||Manifest Ingestion effort regarding the R3 1.0.0 schemas.
The schemas are stored in GitLab on the Member side, meaning they are not yet Open Source.
|Can't code against anything that is not yet Open Source and released under Apache 2.0. The comments in PMC mentioned that Thomas and the Data Definitions team is working on a script that will create the final JSON schemas by resolving the $ref elements. The composited schemas (by script) aren't expected until the 2nd or 3rd week of January, which puts us too close to M3 to incorporate. This is a risk for us as we were hoping to have R3 1.0.0 schema support for M3 in the Manifest Ingestion pipeline||4||2||8||Ingestion team can build against the schema that is available (M1) in Community Gitlab. Still we need to find a way to incorporate evolving schema changes to ingestion framework once they move to community
Alan to schedule touchpoint with CSV, Energistics, Data Defn team
|Multi Region Deployment||PMC||Multi-region H1 has not yet been tested due to 'data set ingestion performance' showstoppers. (Now expected week of January 18th.)
H2 design review not scheduled. (Unclear how to evolve the design without inspection of H1 delivery.)
Lack of detailed requirements grounded in business need. (No business owner pushing for specific capability.)
AWS is canary
Other CSP are not onboard (Post R3)
|Need more collaboration and business sponsorship.||5||4||20||H2 proposed scope is signicantly reduced relative to original intent.
Seeking release requirements & mandatory acceptance criteria from Johan.
|CSV ingestion||PMC||Absence of active engagement with CSP leads.
Finalize Horizon and milestone to reflect accurately in R3 Planning xls
|Very likely miss CSP specific tasks if not actively engaged.
Can’t track the progress against milestones if not refined accurately
|3||2||6||Proj lead will schedule set cadence to drive the engagement with CSP leads.
In the coming week will submit refined Horizon and Milestones to the Prgm
|Seismic DDMS||PMC||No information or present in the meeting||Can't be delivered as part of R3 if not addressed and understood well||3||3||9||Celina is scheduled to present her work by next week in EA meeting (01/11)||Raj & Celina||44209|
|Wellbore DDMS||PMC||Horizon and Milestones to be defined||Can't be delivered as part of R3 if not addressed and understood well||3||3||9||This could be an incremental delivery post R3||Raj & Francois||44209|
|PMC||Target a freeze date for Schema Changes||Constant changes to schema hinders progress on Manifest ingestion, other ingestion work across various teams||5||5||25||Work with PMC and Ingestion team to define freeze date||Raj & Joe||44209|
|EDS||PMC||Design changes based on ADR approval||EDS should be desigining based on this ADR becos file & delivery service are replaced with dataset service
|4||1||4||-- [Complete] EDS to incorporate Dataset service in its design
-- [In Progress] Finalize schema changes to support Dataset service
Jacob - Incorporate Dataset service into EDS
Joe N / Data Definitions: Finalize schema changes to enable Dataset service
|Data Loading||R3 AP||Updating the TNO & VOLVE data set with new schema changes||These data sets should be udpated with new schema changes to support data feeding into OSDU (similar to R2)||3||1||3||Michael and James Pipe?||44209|
|E&O||PMC||Team scheduled to complete Incubator by end of Dec which is not complete. Team is reassessing the effort to finish by M3||Broader team must align should we cntinue with Entitlement similar to R2?||4||5||20||Hrvoje & CSP Leads|
|Infosec||R3 AP||M2 deliverable of Dev Security Guidelines spilled over||Withtout this document Operators will not have understanding of Security guildelines to be followed during OSDU installation||3||1||3||Paco is working to complete this by M3 (95% is already complete but few tweaks are being made)||Paco Hope||44227|
|Documentation||R3 AP||Lack of resource to drive this for completion||Will greatly impact testing & validation in Pre Ship||3||3||9|
|Admin UI||R3 AP||Scope Creep||Team is unclear of scope and alignment must occur||3||4||12||Chris Mcginn & Paco||44227|
|EDS||PMC||Additional ADRs for Workflow Service and EDS DMS service + associated cloud implementations on relatively short timeline||1. Additional CSP CI/CD and implementation below Cloud SPI
2. Review periods (ADR, legal, etc.) challenges timeline
|3||4||12||-- Publish ADRs for workflow and EDS DMS services and solicit feedback
-- Focus on clarity around Cloud SPI implementation requirements
Jacob/Rawaa: CSP engagement
|Workflow Service ADR: Week of Jan 11
EDS DMS: Week of Feb 1
|Ingestion Framework||PMC||Multiple ADRs coming for R3 design||Need to understand combined impact to Ingestion Framework and corresponding timeline for implementation if ADRs approved.||2||2||4||Coordinating amongst ADR authors to help align incoming requests. Pre-sharing information where useful to help inform upcoming conversation. Changes should be non-breaking.||Alan Henson||44218|
|Manifest Ingestion||PMC||Architecture misalignment||Data loading expectation was via streamlined service (API), but implementation is via ingestion workflow (DAG). November agreement on approach maybe misaligned from implementation.||3||2||6||Speaking with OSDU architects and data loading team to resolve.||Alan Henson||44211|
|OSDU||PMC||Standard way of deploying Operators
Stadndard way of deploying DAGs
Standardize Python version
|5||4||20||Raj and Joe|
|Admin UI||PMC||Clarity on whether Data Loading and Ingestion are in scope for Admin UI||Scope Creep||2||2||4||Chris McGinn|