1. [Insert Project Name] Preliminary Design Review (PDR) [Insert Date of PDR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)

2. [Project Name] - PDR Template Instructions This document is a template for the Preliminary Design Review (PDR). Sections should not be removed from the presentation. If a section is not applicable, please indicate as such and provide an explanation. Additional slides may be added to convey information that you feel is important to share that is not addressed by this template. Please ensure that your presentation is Section 508 compliant by following the URL: http://www.hhs.gov/web/policies/checklistppt.html DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

3. [Project Name] - PDR Template Revision History DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION VersionDateAuthorDescription of Changes 1.09/16/2009K. Maenner, OIS/DITPPABaseline Version 1.11/15/2010K. Maenner, OIS/DITPPA 1.Removed planned tests from the Test Plan page. 2.Added slides to discuss Project Management. 1.36/11/2010C. Shaunessy, OIS/DITG Corrected Slide 8 (Design Considerations) to correspond to Section 5 of SDD. 1.47/14/2011C. Shaunessy, OIS/DITGAdded cost/schedule slide 2.04/23/2012C. Shaunessy, OIS/DITGReformatted for XLC.

4. [Project Name] - PDR Presenter’s NameRole Presenters 4 See this slide’s notes pages for slide instructions.

5. [Project Name] - PDR [Insert graphic providing a high-level overview of the business process from Section 5 of the Business Case.] 5 High Level Business Concept

6. [Project Name] - PDR Business Need [Insert condensed business need and drivers from the Business Case or from the AR presentation] Goals/Scope/Purpose [Insert condensed goals/scope from the Business Case and the business and functional purpose from the Requirements Document or from the AR presentation] Stakeholders [Insert stakeholder information from the Business Case or from the AR presentation] Project Information 6

7. [Project Name] - PDR 7 System Scope [Insert condensed system scope from the High-Level Technical Design.] High Level Functional Requirements [Insert high level functional requirements from the High Level Technical Design.] Summary of Changes [Insert condensed summary of changes of the current system from the High- Level Technical Design (if applicable).] Proposed System

8. [Project Name] - PDR [Identify any recommendations and/or findings from the AR/PSR and their resolution.] 8 AR/PSR Findings

9. [Project Name] - PDR [Describe where the system’s data will reside and identify any data exchanges that may occur. Alternatively, you may attach Section 5.1.6 of the project’s Requirements document.] Inputs: Identify all data (as well as the format of the data—paper, manual input, electronic data) supplied to the system as well as who/what is supplying the data. Provide instructions on what happens to the manual/electronic inputs after they are entered into the master file/database and are verified. Master Files – Provide a detailed description of the data maintained in the system/database. Provide detailed instructions for the retention and disposition of this data (where will the data be maintained, when will the data be deleted or destroyed). Outputs: List all reports, data sharing with other Agencies/CMS systems, etc. Provide instructions for how long the reports are needed for Agency business and when they should be destroyed/deleted. Is this system replacing a paper-based records system or an existing electronic system? If electronic, has the migration of the legacy data been addressed? 9 Records Management

10. [Project Name] - PDR [Summarize the design goals and guidelines, development methods and contingencies, and architectural strategies as described in the System Design Document.] 10 Design Considerations

11. [Project Name] - PDR [Insert the system architecture diagram depicting the overall, integrated structure of the system in terms of presentation, application and data regions including data storage and manipulation, user and external interfaces from Sections 6.4, 7.2, 8 and 12 of the System Design Document respectively.] System Architecture 11

12. [Project Name] - PDR Response Data Operational / System Environment System Interconnection / Information Sharing System Security Level E-Authentication Level: See this slide’s notes pages for slide instructions.

13. [Project Name] - PDR [Insert the testing approach / strategy from Section 5 of the Test Plan.] 13 Test Plan

14. [Project Name] - PDR [Insert the release content and schedule from Sections 5.2.1 and 5.2.2 of the Release Plan.] 14 Release Plan

15. [Project Name] - PDR [Insert the data conversion scope from Section 5.1 of the Data Conversion Plan.] 15 Data Conversion

16. [Project Name] - PDR [Provide an update on the status of the project.] 16 Project Management Update: Status

17. [Project Name] - PDR [Provide an update on the project risks and issues, including the probability of occurrence and the mitigation for each risk.] 17 Project Management Update: Risks & Issues

18. [Project Name] - PDR 18 Project Management Update: Cost & Schedule Cost Schedule See this slide’s notes pages for slide instructions.

19. [Project Name] - PDR [Provide an update on the status of the deliverables required for the project as documented in the Project Process Agreement. Also provide an update on the status of your Information Security Certification & Authorization process.] 19 Project Management Update: Deliverables Status

20. Conclusion of Preliminary Design Review for [insert project name]