NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


DescriptionStatus

Mitigation


Probability


Overall Impact

Scope Impact 


Budget Impact

 

 Schedule Impact 


Quality Impact 

ResolutionResolution DateNotes
The known Use Cases may only be a small fraction of the Use Cases the community requires. As such, our level of efforts estimates may not be enough to cover the effort required to meet the new use cases.

Not Active

Frequent communication with the NCI program leadership to prioritize Use Cases to use in the Prototyping and Production stages HighLowModerateMinorModerateLow


2Amount of data to be stored is larger than the free-storage can handle, so could exceed our estimated costs. Not ActiveWork with the NCI programs to identify this issue if it arises and evaluate options before implementing a solutionLowMediumLowModerateLowLow


3The level of detail in the SOW is low and the Data Commons concept is new. So there are a lot of unknowns that will only be encountered during implementation. So this adds a lot of uncertainty to the timelines and the effort estimatesNot Active Focus on uncovering those unknowns during the Prototyping stage so they do not arise late in the project at Production. At the completion of the Prototyping phase we will conduct an assessement of costs and schedule for the development of the Production system.MediumMediumModerateLowModerateLow


4Unable to staff the project in a timely fashion with either/or FNL or subcontractor staff. This could delay progress towards meeting milestonesNot Active The initial phases will focus on activities such as data inventory, harmonization and use case definition that utilize existing or soon to be hired staff (anticipated to be onboard before project starts). This will allow time to find any additional staff or subcontractors to staff up. LowMediumLowLowModerateLow


5The Gen3 architecture is still new and not extensively documented or field tested. It is possible there are missing elements needed to fully support the ICDC or there are performance gaps in functionality or stability. Not ActiveGen3 was assembled by UChicago so by using UChicago as SME(s) during development we can be guided by them with respect to what features are incomplete and if there are roadmaps to complete those features. This will enable us to determine prioritization of ICDC system development to avoid any known issues and to plan around Gen3 development releasesLowMediumLowLowModerateLowAccept11/20/18We were informed yesterday that the dockerized version of Gen3 to which we had been pointed by UChicago staff was incomplete and outdated and was not planned to be supported. Meetings were held with UChicago staff yesterday and it was resolved that they would point us to current code and help us stand up a non-dockerized version over the course of the next few weeks. This has resulted in a loss of time/money for all work done on the system since Nov. 1, 2018.