1 / 7

Identifying and Mitigating Risks for Build 2 Deployment in PDS Management

This report presents the identified risks associated with Build 2 deployment and operations, along with proposed mitigations. Key areas of risk include Tool Support, Central Catalog Migration, and PDS3 Operations, all assessed as "Low" risk. Mitigations involve careful scoping of tools, offline search functionality, and continuity planning for submission processes. The architecture of PDS4 is designed to minimize impact on users while ensuring essential functionality. This phased approach facilitates building and releasing core components effectively.

tave
Download Presentation

Identifying and Mitigating Risks for Build 2 Deployment in PDS Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Risks for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman

  2. Overview • Present the identified risks for Build 2 deployment and operations along with any associated mitigations. • Risks have been identified in: • Tool Support • Central Catalog Migration • PDS3 Operations System Risks for Build 2

  3. Tool Support • The entire tool suite is not available for Build 2 operations. • This risk is assessed as “Low” risk. • Mitigations: • Build 2 is scoped so that minimal tools are necessary. • Few schemas will be developed, and much of this can be done in house. • Initial validation tool will be in place. • Future builds can add more tools in conjunction with the budget and PDS experience working with PDS4. System Risks for Build 2

  4. Central Catalog Migration • Much of the current search functionality of the PDS web site depends on the central catalog database. • This risk is assessed as “Low” risk. • Mitigations: • Real-time access to the central catalog for users is limited. • The search indexes are generated as an offline activity and can be generated on demand. There is limited risk to end users. • Search maintenance from the central catalog in PDS3 is limited. • The improvements will come with PDS4. System Risks for Build 2

  5. PDS3 Operations • PDS3 operations will be impacted by the release of PDS4. • This risk is assessed as “Low” risk. • Mitigations: • Build 2 exposure can, for the most part, be scoped internal to PDS. • Submission of catalog files to EN will continue. EN will ensure the registry infrastructure is updated. System Risks for Build 2

  6. Conclusion • It is not always easy to identify or mitigate all risks associated with deployment of new software. • The PDS4 software has been architected and designed from the beginning to provide the necessary functionality while minimizing impact on the data providers, data consumers and the Discipline Nodes. • This approach has been aided by the phased development schedule allowing us to to build and release core components and then build on them in subsequent releases. System Risks for Build 2

  7. Questions/Comments

More Related