DCPDS DRAFT Atch 16 - DCPDS Deliverable Reports

Attachment 16 DCPDS Deliverable Reports (Recurring) The following table provides a summary of the Contract Deliverable Reports in which the contractor shall be expected to provide. These deliverables shall be provided to the DCPDS COTR and other CPMS staff as necessary. The delivery schedule in the table identifies the deliverable report, its due date, and frequency. In the event the contractor, for any reason, anticipates or encounters difficulty in complying with the contract delivery schedule or date, or in meeting any of the other requirements of the contract, they shall immediately notify the DCPDS COTR in writing, providing all the pertinent details. This data shall be informational only in character and its receipt by the Government shall not be construed as a waiver by the Government of (i) any delivery schedule or date; (ii) compliance with any other contract requirement by the contractor; or (iii) any other rights of remedies belonging to the Government under law or otherwise under this contract.

DELIVERABLE SCHEDULE

Contractual Due Date Scheduled Frequency of Performance

Jul 15, Oct 15 Quarterly

Jul 15, Oct 15 Quarterly

Jul 20, Oct 20 Quarterly

Jul 20, Oct 20 Quarterly

Jul 20, Oct 20 Quarterly

Aug 1, Nov 1 Quarterly

Aug 15, Nov 15 Quarterly

Sep 15, Dec 15 Quarterly

Sep 15, Dec 15 Quarterly

each Month Monthly

Below is a description of each of the DCPDS deliverables identified in the above table.

Report 16.1, DCPDS Program Management Plan (PMP) – Submitted Annually (As prescribed by paragraph 2.1.30.2 of the PWS) The Program Management Plan (PMP) shall describe how the Contractor will provide support to operate, sustain, and maintain the DCPDS for the Department of Defense (DoD) CPMS. The plan shall outline the processes, methods, and controls the Contractor will use throughout the program period to ensure that the level of Contractor support meets or exceeds contractual requirements. This plan shall also address activities in the management, operational, and technical areas; outlines the communication approach the Contractor will follow; and describe the process methodology that will be used.

Report 16.2, Report on Help Desk Production Capability – Submitted Annually (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall provide evidence that the Contractor and its sub-Contractors of the DCPDS Help Desk has attained and sustained production capability. At a minimum, this deliverable shall identify how the Help Desk is set up for 24 by 7 by 365 operation, how backup support is provided during non-duty hours, how the systems are monitored and how alerts are handled, how the Contractor will field trouble calls, what trouble management system is used, and how trouble tickets are tracked. It shall identify all the accomplishment activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.3, Systems Administrations Operational Manual – Submitted Annually (As prescribed by paragraph 2.1.4 of the PWS) This deliverable shall define the system administration duties and procedures for all servers supporting the Defense Civilian Personnel Data System (DCPDS). The duties and procedures shall describe how the Contractor will perform the daily ongoing system administration tasks. The manual shall also describe tasks on how the Contractor will plan for new server configuration and installation.

Report 16.4, Technical Review, System Status, and Recommendations for DCPDS Director, PM, and Key Staff – Submitted Annually (As prescribed by paragraphs 2.1.30.2 and 7.1 of the PWS) This annual report/review shall be briefed to the CPMS Director, DCPDS PM, and CPMS key staff. The report/review shall feature a roll up of all reports and activity for the previous fiscal year (FY).

Report 16.5, Report on Systems Administration Production Capability – Submitted Annually (As prescribed by paragraph 2.1.4 of the PWS) This deliverable shall provide evidence that the Contractor and its sub-Contractors DCPDS processes are in place to provide system administration production capability to support the DCPDS application and its subsystems. It shall identify all the accomplishment activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.6, Report on Performance Monitoring Capability – Submitted Annually (As prescribed by paragraph 2.1.4 of the PWS) This deliverable shall provide evidence that the DCPDS activities of the Contractor and its sub-Contractors have been initiated and sustained to provide performance monitoring capability to support the DCPDS application and its subsystems. It shall identify all the accomplishment activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.7, Report on Technology Refresh Capability – Submitted Annually (As prescribed by paragraph 2.1.21 of the PWS) This deliverable shall provide evidence that the DCPDS processes of the Contractor and its sub-Contractors are in place to provide technology refresh capability to support the DCPDS program. Technology refresh items/activities will be tracked an on-going basis and reported via this deliverable. It shall identify all technology refresh activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.8, Report on Information Assurance Capability – Submitted Annually (As prescribed by paragraph 2.1.15 of the PWS) This deliverable shall provide evidence that the Contractor and its sub-Contractors have properly secured all DCPDS assets in accordance with the DoD IA directives identified in this PWS. It shall identify all the accomplishment activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.9, Life Cycle Replacement Plans (LCRPs) – Submitted Annually (As prescribed by paragraphs 2.1.21 of the PWS) This deliverable shall provide for all technology refresh changes for each Component and the DCPDS Enterprise. It provides a recurring update on software, hardware, and architecture activities that may impact future procurements for DCPDS. The plan shall also identify the current key hardware in use and provide recommendations on expansion or replacement of hardware, when applicable, based on planned future changes in DCPDS software or hardware architecture.

Report 16.10, DRE Closeout Report – Submitted Annually (As prescribed by paragraph 2.1.16 of the PWS) This deliverable is the after action report from the annual Disaster Recovery Exercise of the Enterprise Production Data Center. It contains a summary of what was planned at the detail level, what actually occurred at the detail level, and any lessons learned that need to be incorporated into future exercises.

Report 16.11, Report on Applications Sustainment and Maintenance Production Capability – Submitted Semi-Annually (As prescribed by paragraph 2.1.5 of the PWS) This deliverable shall provide evidence that the DCPDS processes of the Contractor and its sub-Contractors are in place to provide applications operations, sustainment, and maintenance production capability to support the DCPDS application, and its subsystems. It shall identify all the accomplishment activities during the prior year, activities remaining to be accomplished, and all issues identified.

Report 16.12, IA Training Metrics to Track Compliance with DoD Directive (DoDD) 8570.1 – Submitted Quarterly (As prescribed by paragraph 2.1.15 of the PWS) This report shall document the Contractor’s performance with regard to the requirement to achieve 100% of their IA workforce meet the requirements of DoDD 8570.1.

Report 16.13, Report on All Contractor Personnel Performing Privileged or IA Manager Functions, to Include Certification Level, Certification and/or Training Status, and Cost – Submitted Quarterly (As prescribed by paragraph 2.1.15 of the PWS) This report lists all Contractor and sub-Contractor personnel performing privileged or IA manager functions that are subject to the requirements of DoDD 8570.1. The report shall include IA certification level, IA certification and/or training status, compliance or expected compliance date, and cost with regard to compliance with the requirements of the directive. In addition, the Contractor shall provide a copy of the certification certificate and signed statement of responsibility for individuals initially assigned IA responsibilities (or subsequently assigned IA responsibilities).

Report 16.14, Performance Metric (PM) Statistics - Service Level Agreement (SLA) Wrap-Up Reports (Including Monthly Reports for Quarterly Reporting) – Submitted Quarterly (As prescribed by paragraphs 2.1.4 and 6.1 of the PWS) The Contractor shall provide quarterly SLA reports based on the prior three (3) months performance metrics identified in Attachment 15 (Performance Metrics/Service Level Agreements). The Quarterly report shall be an accumulation of the three (3) monthly reports with each Monthly Performance Metric report provided for support. Each monthly and quarterly report shall include a SLA scorecard that shows the projected score for each PM/SLA except for SLAs #5 and #8. SLAs #5 and #8 are for CPMS management and the COTR to rate the Contractor. The report shall also include a section detailing the activity for each PM/SLA identified in Attachment 15 except for SLAs # 5 and #8.

Report 16.15, Help Desk Statistics by Monthly Activity - Submitted Quarterly (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall be broken into three different sections by monthly activity. The first section shall identify the DCPDS application related problem reports (PRs) by Component and by functional area. It shall identify the total number of PRs logged to include the percentage of PRs per each Component and functional areas. The second section shall identify the non-DCPDS related PRs by Component and problem type (e.g., circuit, power outage, hardware, etc.). It shall identify the total number of PRs logged to include the percentage of PRs per each Component and problem type. The third section shall identify the total number of incident reports (IRs) by Component. The report shall also show the percentage of IRs per Component.

Report 16.16, Help Desk Call Tree Reports by Monthly Activity – Submitted Quarterly (As prescribed by paragraph 2.1.2 of the PWS) The report shall provide the total number of tier-2 (Component) to tier-3 (Contractor) Help Desk calls, average speed of answer, and average duration of call broken out by technical problem type. This deliverable shall be provided by monthly activity with a quarterly rollup.

Report 16.17, Property Book Inventory Control Reports of All Government Furnished Equipment (GFE) – Submitted Quarterly (As prescribed by paragraph 11.1.1 of the PWS) This deliverable shall identify all GFE under the Contractor’s control that is required for the sustainment, maintenance and daily operations of DCPDS. The report will indicate the operational status and the physical location of all GFE.

Report 16.18, Security Investigation Status Reports – Submitted Quarterly (As prescribed by paragraph 2.1.15 of the PWS) This report lists the status of all Contractor and sub-Contractor personnel requiring any type of personnel investigation for either an IT level of trust designation or for a security clearance. The report lists the individual and the status of their progress through the process.

Report 16.19, Quarterly Travel Projections – Submitted Quarterly (As prescribed by paragraph 2.1.30.2 of the PWS) This deliverable shall provide the projected travel of Contractor and sub-Contractor personnel for the upcoming quarter. The report shall provide the traveler, destination, purpose of travel, dates, and estimated cost of travel.

Report 16.20, CSU Desk Guide – Submitted Quarterly (As prescribed by paragraph 2.1.8 of the PWS) The CSU Desk Guide shall provide a comprehensive description on how the CSU application functions and updated on a quarterly basis. It shall provide screen-shots to illustrate the various screens within the CSU system. It shall also provide separate appendices for CSU screen definitions, CSU Reports Guide, CSU Data Elements, and Schema Changes for CATS EUL. This guide shall be updated quarterly with all changes made in DCPDS that affects the CSU. After CPMS review the guide shall be posted to the CPMS Web site for customer use.

Report 16.21, DCPDS Integrated Master Schedule (IMS) – Submitted Monthly with updates as required (As prescribed by paragraph 2.1.30.2 of the PWS) This deliverable shall identify in graphic form all current, future, and pending projects to ensure successful program/contract execution and will be used by the customer to verify attainability of contract objectives, to evaluate progress toward meeting program objectives, and to integrate the program schedule of activities. The report shall project up to 24 months in the future.

Report 16.22, Project Status Reports – Submitted Monthly (As prescribed by paragraph 2.1.30.2 of the PWS) This deliverable shall list all Contractor deliverables from the prior month. The report shall provide the deliverable name and the date it was delivered. Also included in this report shall be all DCPDS software patch release activity, technology refresh papers, technology refresh items, key meeting and program reviews with CPMS, and key integrated product team (IPTs) or equivalent meetings.

Report 16.23, T&M Activity Reports – Submitted Monthly (As prescribed by paragraph 2.1.30.2 of the PWS) This deliverable shall provide contract execution for each month for each CLIN. The report shall be separated by tasks within the CLIN, identify the labor categories, company name, number of hours executed per month, labor category hourly rate, cost for current month, and total cost for option period.

Report 16.24, System Configuration and Performance Monitoring Report – Submitted Monthly (As prescribed by paragraph 2.1.4 of the PWS) This deliverable shall provide system configuration and performance for each server supporting DCPDS including the Component servers located at a Government facility. The report shall provide the system configuration for each server to include the server name, model, operating system version, number and speed of CPU, total memory, total disk space, server function, and database version (if applicable). This information shall be separated by site. The report shall also include an Exceptions report to highlight the servers that have exceeded defined thresholds for CPU, memory, I/O, file system volume, database disk volume, and system/application disk volume. Lastly, the report shall provide a graphic representation of each server showing the server’s CPU utilization, memory utilization, I/O utilization, database disk utilization, and system disk utilization.

Report 16.25, Software and Application Status Report – Submitted Monthly (As prescribed by paragraph 2.1.5 of the PWS) This deliverable is a running accumulation of all DCPDS software and application changes, additions, deletions, upgrades, problems, and fixes. The report shall include all known future requirements. The report shall be listed by quarter.

Report 16.26, Non-CAC Trend Report – Submitted Monthly As prescribed by paragraph 2.1.25 of the PWS) This report shall be run once a month at the beginning of the month. It shall provide a listing of all non-CAC users to include the number of non-CAC users with a14 day suspense and those without a suspense date for closure. The report shall also provide the total number of non-CAC users so it can be determined if the number is rising for any or all Components. There shall be a Non-CAC Trend graph showing the Components trends, as well as a report by Component, a Bar Chart indicating the “Other” reasons by Component, and a specific report that identifies each of the “Other” reasons in detail by Component.

Report 16.27, Help Desk Ownership Reports – Submitted Bi-Weekly (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall display the number of tickets still in the queue to be worked. The report shall be broken out by Components, CPMS, and/or Vendor (Oracle/LM), and who the ticket is assigned, when it was created, and the age of the ticket.

Report 16.28, Program Review for Senior CPMS Management – Submitted Bi-Weekly (As prescribed by paragraph 2.1.30.2 of the PWS) This review shall provide a project status of all on-going DCDPS projects. This review shall include the current status, issues, and upcoming activities for each project being reviewed, the current DCPDS Integrated Master Schedule (IMS), and all current action items.

Report 16.29, Help Desk Oracle Service Request Status Reports – Submitted Weekly (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall provide all Oracle Service Requests with status broken out by Severity level and CPMS Priority. The report shall include a summary of the Problem/Enhancement, the PR/TD QX number, CPMS POC, problem submitted by, SR#, Legacy, Oracle Bug#, date the SR was created, the age of the SR, LM Custom Fix, the last time the Bug was updated, the status and projected delivery date. This report shall also display all delivered but not yet fielded Oracle SRs.

Report 16.30, Help Desk Reports of 14-Day Production Defect Tickets – Submitted Weekly (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall display a list of Production Defect Tickets that have not been updated in 14 days. The report shall consist of the PR #, last time updated, the Assignee Name, and the Component.

Report 16.31, Help Desk Reports of 14-Day TestDirector Tickets – Submitted Weekly (As prescribed by paragraph 2.1.2 of the PWS) This deliverable shall display a list of Test Director Tickets that have not been updated in 14 days. The report shall consist of the PR #, last time updated, the Assignee Name, and the Component.

Report 16.32, Self Service Usage Reports (Including Reduced Sign-On [RSO] Accounts Reports) – Submitted Weekly (As prescribed by paragraph 2.1.11 of the PWS) This report shall provide the number of users by Component and type (HR vs SS) who have logged onto Self Service and have updated any of the updatable information. The report shall also include the number of RSO accounts that have been built per Component.

Report 16.33, Non-Common Access Card (CAC) Count Report – Submitted Weekly (As prescribed by paragraph 2.1.25 of the PWS) This report shall provide a listing of all non-CAC users, any new non-CAC users added with a14 day suspense and those without a suspense date for closure. It shall also provide a comparison to the previous week’s report allowing us to determine if the number is rising for any or all Components.

Report 16.34, Management/Team Leads Weekly Out-of-Office/Backup Forecast – Submitted Weekly with Daily Updates as required - (As prescribed by paragraph 2.1.30.2 of the PWS) This report shall include all Contractor management/team lead personnel who will be out of the office. The report shall provide a two week forecast of key personnel being out of the office.

Report 16.35, Security Incident Reports – Submitted as required (As prescribed by paragraph 2.1.15 of the PWS) This report documents all security incidents that occur. The report shall document the security incident that occurred, what parties responded to the incident, and what actions were performed by all parties to correct the situation. The report shall also list any lessons learned and any potential actions to mitigate future occurrences.

Report 16.36, Computer Emergency Response Team (CERT) Reports – Submitted as required (As prescribed by paragraph 2.1.15 of the PWS) This report provides the DCPDS program office with tasking orders and other requirements from USCYBERCOM, USCERT or other information assurance commands. The report shall list the required activities, the organization requiring the activities, and the status of completing the required tasks. These reports may be provide by email except in the cases where the DCPDS Program Office requests a formal report.

Report 16.37, Additional Reports – Submitted as required (As prescribed by paragraph 7.1 of the PWS) There may be times when the Government will request a report or white paper for a current issue, problem, or project. The Government will give the Contract adequate time to generate and deliver the report.

As of: Aug 4, 2011