XLC Template Revision History The following records information regarding changes made to the XLC template over time. This table is for use by the XLC Steering Committee only. To provide information about the controlling and tracking of this artifact, please refer to the Record of Changes section of this document. This XLC Template Revision History pertains only to this template. Delete this XLC Template Revision History heading and when creating a new document based on this template. 1 - XLC Template Revision History Version Number Date Author/Owner Description of Change 1.0 11/13/2007 J. Shadoan, OIS/DITPPA Baseline Version 2.0 9/23/2009 K. Maenner, OIS/DITPPA Changes based on ILC CR58 based on comments from Lockheed-Martin 2.1 10/19/2009 K. Maenner, OIS/DITPPA Adjusted List of Tables Added Disaster Recovery Appendix Renamed Appendix E Removed Release Management Section 2.2 3/09/2010 K. Maenner, OIS/DITPPA Changed format of table 3.2.2 per 2.3 12/30/2010 C. Shaunessy, OIS/EASG/DITG Changes based on ILC CR090 requested by LM on behalf of Roxanne Byczkowski: Adjusted List of Tables Added verbiage to the Disaster Recovery Appendix 3.0 5/14/2014 C. Shaunessy, OIS/EASG/DITG Moved content to new XLC template format 3.1 8/7/2014 C. Shaunessy, OIS/EASG/DITG Corrected heading labels on Roles/Responsibilities table in Section 4. Adjusted table captions for 508 compliance Section 5.3: Production Control Procedures Other minor formatting and content changes per CR 14-012 3.2 02/02/2015 Surya Potu, CMS/OEI/DPPIG Updated CMS logo 3.3 02/17/2016 Rick CMS/OEI/DPPIG Updated Appendix 8-D with text from Operations & Maintenance (O&M) Manual template version 2.3
Notes to the Author/Template Instructions This document is a template for creating an Operations & Maintenance Manual for a given investment or project. The final document should be delivered in an electronically searchable format. The Operations & Maintenance Manual should stand on its own with all elements explained and acronyms spelled out for reader/reviewers, including reviewers outside CMS who may not be familiar with CMS projects and investments. This template includes instructions, boilerplate text, and fields. The developer should note that: Each section provides instructions or describes the intent, assumptions, and context for content included in that section. Instructional text appears in blue italicized font throughout this template. Instructional text in each section should be replaced with information specific to the particular investment. Some text and tables are provided as boilerplate examples of wording and formats that may be used or modified as appropriate. When using this template, follow these steps: Table captions and descriptions are to be placed left-aligned, above the table. Modify any boilerplate text, as appropriate, to your specific investment. Do not delete any headings. If the heading is not applicable to the investment, enter “Not Applicable” under the heading. All documents must be compliant with Section 508 requirements. Figure captions and descriptions are to be placed left-aligned, below the figure. All figures must have an associated tag providing appropriate alternative text for Section 508 compliance. Delete this “Notes to the Author/Template Instructions” page and all instructions to the author before finalizing the initial draft of the document.
Record of Changes Instructions: Use the below to record information regarding changes made to the document over time. Table 2 - Record of Changes Version Number Date Author/Owner Description of Change <X.X> <MM/DD/YYYY> CMS <Description of Change> <X.X> <MM/DD/YYYY> CMS <Description of Change> <X.X> <MM/DD/YYYY> CMS <Description of Change>
Special Server Conditions (If Applicable) 6 - Application Special Server Table Server Condition Server Name OS Primary Function Dedicated <Server> <Condition> <Server Name> <OS> <Primary Function> <Dedicated> <Server> <Condition> <Server Name> <OS> <Primary Function> <Dedicated> <Server> <Condition> <Server Name> <OS> <Primary Function> <Dedicated> System Firewall Specifications Table 7 - Firewall Information Firewall Originating Server Destination Server Port <Firewall> <Originating Server> <Destination Server> <Port> <Firewall> <Originating Server> <Destination Server> <Port> <Firewall> <Originating Server> <Destination Server> <Port> System User Overview Instructions: Provide a number reference for the estimated/actual amount of per application. Also provide the impact for users if the production environment is unavailable or in the event of processing malfunctions. Estimated Users Peak Processing Time Hours of Operation User Impact for System Failure Processing Overview Instructions: Provide information that is applicable to the processing of the system. Identify the state(s) and mode(s) of operation. Identify the types of inputs/access that can be made to the software and the software’s response to each type. Provide a flow chart depicting how the information moves from the application to the database. If any portion of the system is run in batch mode, provide an inventory of all runs showing the software components, the job control batch file names, run jobs, and purpose of each
15 - IT Support Responsibilities Responsibilities Lead/1st Contact Lead/2nd Contact Backup/2nd Contact Backup/3rd Contact CMS IT Service Desk () or 410-786-2580/800-562-1963 <Lead/2nd contact information> N/A N/A Tier 1 <Lead/1st contact information> <Lead/2nd contact information> <Backup/2nd contact information> <Backup/3rd contact information> Tier 2 <Lead/1st contact information> <Lead/2nd contact information> <Backup/2nd contact information> <Backup/3rd contact information> Tier 3 <Lead/1st contact information> <Lead/2nd contact information> <Backup/2nd contact information> <Backup/3rd contact information>
Appendix 8-H: Contact List Table 16 - Contact List Contact Sequence Contact Name Organization Application Phone Cell/Pager Email 1st CMS IT Service Desk CMS CMS Help Desk () 2nd Level Name Last Name> <Organization> <Application> <Email address> 3rd Level <First Name Last Name> <Organization> <Application> <Email address> CMS GTLs <First Name Last Name> <Organization> <Application> <Email address> CMS Business Owners <First Name Last Name> <Organization> <Application> <Email address> Developers <First Name Last Name> <Organization> <Application> <Email address>