A03_Draft_PWS_EVM_CR_April_v2_eud.pdf

Performance Work Statement (PWS) Earned Value Management – Central Repository (EVM-CR)

Support for The Office of Performance Assessment and Root Cause Analysis (PARCA)

1.0 GENERAL INFORMATION

1.1 Description of Services/Introduction. The Contractor shall provide all personnel, equipment, tools, materials, supervision, and other items necessary to provide non-personal technical support services in support of The Office of Performance Assessment and Root Cause Analysis (PARCA) as defined in this performance work statement (PWS) except as specified in Part 3 as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 This PWS describes the technical support required by the Office of Performance Assessment and Root Cause Analysis (PARCA) as the designated office for the administration of the Earned Value Management System. The services of technical specialists and functional experts are required to maintain and upgrade the EVM-CR as well as provide tools that enable data submission and review. The EVM-CR provides centralized reporting, collection, and distribution for key acquisition EVM programmatic and schedule data; a reliable source of authoritative EVM data and access for OSD, the Services, and the DoD Components; houses IPMR (Integrated Program Management Reports) Cost Performance & Schedule reports for ACAT 1C & 1D (MDAP), ACAT 1A (MAIS), and other EV reporting programs.

1.3 Objectives. The objective of this effort is to provide non-personal technical support and Information technology support services of the PARCA office

1.4 Scope of Work. The task areas in this PWS require the contractor to provide services to include both the maintenance of the existing EVM-CR systems as well as improvements and developing software requirements and software development, testing, and acceptance.

The contractor should be prepared to have operations/support personnel on-site at PARCA, as well as to provide extensive reach-back capability for policy development, analysis, EVM-CR development and sustainment, workload surge requirements, and other necessary support.

1.5 Type of Contract/Period of Performance: The government anticipates award of a Fixed Price Contract. The period of performance shall be for xxx year from xxxxx to xxxxxxx.

1.6 General Information

1.6.1 Recognized Holidays: The contractor is not required to work the following holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.2 Hours of Operation/Place of Performance. The contractor is responsible for conducting business, between the hours of 8:00 – 4:30 Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this statement of work when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the work force are essential.

1.6.3 Security Requirements: Contractor personnel performing work in support of this effort must have a SECRET security clearance. The contractor shall forward security clearances and visitor requests to PARCA for all personnel assigned to work on task orders issued in support of PARCA under this contract.

1.6.3.1 PHYSICAL Security. The contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.3.2 Key Control. The Contractor shall establish and implement methods of ensuring all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the government will be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas.

The Contractor shall immediately report any occurrences of lost or duplication of keys to the Contracting Officer.

1.6.3.2.1 In the event that keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks;

however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.3.2.2 The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.3.3 Lock Combinations: The Contractor shall establish and implement methods of ensuring that lock combinations are not revealed to unauthorized persons. The Contractor shall notify the COR when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.4 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.4.1 Task Manager: The contractor shall provide a task manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer.

The program manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

1.6.4.2 Identification of Contractor Employees: All contract personnel performing work under this requirement at a Government facility are required to identify themselves as contractor personnel to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

PART 2

DEFINITIONS & ACRONYMS

CLS: Contractor Logistics Support

Contracting Officer’s Representative (COR): A representative from the requiring activity assigned by the Contracting Officer to perform surveillance and to act as liaison to the contractor

Contracting Officer’s Technical Representative (COTR): A designated qualified person acting as the COR’s authorized representative to assist in the technical monitoring or administration of a contract.

CWBS: Contractor Work Breakdown Structure

DAMIR: Defense Acquisition Management Information Retrieval

DAU: Defense Acquisition University

DCMA: Defense Contract Management Agency

Defective Service: A service output that does not meet the standard of performance associated with it in the Performance Work Statement.

DFARS: Defense Federal Acquisition Regulation Supplement

EITSD: Enterprise IT Services Directorate

EVMIG: Earned Value Management Implementation Guide

MAIS: Major Automated Information System

IBR: Integrated Baseline Review

MDAP: Major Defense Acquisition Programs

MOU: Memorandum of Understanding

PARCA: Performance Assessments and Root Cause Analyses

PBL: Performance Based Logistics

PWS: Performance Work Statement

Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

Quality Control: Those actions taken by a contractor to control the performance of services so that they meet the requirements of the PWS.

Quality Assurance: Those actions taken by the government to assure services meet the requirements of the Performance Work Statement.

SOA: Service-Oriented Architecture

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1 GENERAL: The government will facilitate access of contractor staff to DoD offices, employees and data necessary to provide PWS deliverables. The Government will provide office space and normal office supplies and equipment for contractor personnel working at Government locations.

Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.

Contractor and/or contractor personnel will not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel or upon written approval of the Contracting Officer (CO). The contractor will not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein will preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner which provides for greater rights to the contractor.

At the request of the Government, or at completion of this effort, the contractor will immediately return any Government-provided property, including any equipment, specialized or off-the-shelf software, and all other property provided by the Government for the contractor to use to complete this effort.

Upon commencement of this effort, unless otherwise indicated, the Government will provide the following property to the contractor:

3.1.1 Government Furnished Information and Other Project Support The government will provide the contractors with access to relevant government facilities, studies, reports, data, and key staff as required to perform the Tasks contained in this PWS. The government will provide timely feedback and comments on contractor draft deliverables within ten (10) working days of receipt, to ensure final deliverables are received in a timely manner.

3.2 Services:

All utilities in the facility will be available for the contractor’s use in performance of duties outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

3.3 Facilities: When applicable, the Government will furnish the necessary workspace for the contractor staff to provide the support outlined in this PWS to include desk space, telephones, computers and other items necessary to maintain an office environment.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1 General: In fulfillment of this effort, the Contractor will provide the deliverables identified under Section 5.8, Table 1. entitled “Deliverables Schedule”. All deliverables will be submitted to the COR, unless otherwise agreed upon. Unless otherwise specified, the Government will have a maximum of twenty (20) working days from the day the draft deliverable is received to review the document, provide comments back to the contractor, approve or disapprove the deliverable(s). The contractor will have a maximum of twenty (20) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government. All days identified below are intended to be calendar days unless otherwise specified.

The format for individual deliverables will be determined through consultation between the COR and the contractor at the orientation briefing and identified in writing then provided to the contracting office, COR, and the contractor. Products that reflect the contractor’s analysis and opinion (e.g., studies or analyses) may be in contractor format. All documents will be provided in either hard copy or electronically as requested by the COR. Electronic documents will be provided in the appropriate Microsoft Office format (e.g., Word or PowerPoint); if appropriate, the Government may be asked that they be provided in compressed or PDF format.

4.2 Secret Facility Clearance: The Contractor shall possess or be eligible to receive and maintain a SECRET facility clearance from the Defense Security Service. The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office as required.

PART 5

SPECIFIC TASKS

5.0 BASIC SERVICES. The contractor in support of PARCA will perform the tasks listed below.

5.1 Maintain/Upgrade of the Earned Value Management-Central Repository (EVM-CR)

5.1.1 Contractor shall support reporting level data for all EV reporting programs with EVM- CR reporting requirements. The contractor shall coordinate closely with PARCA and the service system representatives to identify MDAP and other Programs and contracts to include in EVM-CR.

5.1.2 Contractor shall maintain the EVM-CR to provide PARCA, the Service Acquisition community, and the DoD acquisition timely access to EVM cost performance and schedule data when needed to support programmatic management oversight and management activities.

5.1.3 The contractor shall support use of the existing AT&L MilCloud network and server (or other PARCA approved and government provided network and server) capacity currently used to support the current AT&L Data Systems to meet the expected increase in data submissions for the EVM-CR. The contractor shall monitor resource demand closely and coordinate with PARCA and AT&L to define future IT requirements necessary to support the EVM reporting and repository functions.

5.1.4 The contractor shall work closely with PARCA to define and prioritize requirements for continued improvements to the EVM-CR, the EVM-CR Portal, and supporting applications.

5.1.4.1 The contractor shall ensure that the EVM-CR portal applications remain accessible and up to date on all DoD security requirements. The contractor will also ensure the EVM- CR and application maintain compatibility with new hardware and operating system updates.

5.1.4.2 The contractor shall work with the PARCA government staff to document requirements for all new web applications or major enhancements to existing applications.

5.1.4.3 The contractor shall not perform any software development without government approval on requirements documentation.

5.1.4.4 The contractor shall conduct major upgrades to existing applications, or integrate third party applications in accordance with the documented requirements.

5.1.4.5 The contractor shall test all applications prior to installation. The contractor shall install all web applications following approval of the PARCA government staff. The contractor shall make new/upgraded applications available on a development server accessible to the PARCA government staff as necessary.

5.1.4.6 The contractor shall receive PARCA government approval prior to installing new/upgraded applications on the DCARC production servers.

5.1.4.7 Portal and Application Bug Fixes/Corrections

The contractor shall correct all reported software bugs to the EVM-CR and EVM-CR User Portal and applications. Bugs are defined as issues where the software is not working as intended or requirements were not understood and implemented correctly.

5.1.4.7.1 The contractor shall provide corrections to all reported bugs within 5 business days of report or if the bug cannot be corrected in that timeframe the contractor must provide an estimate of the number of man-hours required to correct the bug(s).

5.1.4.7.2 The contractor shall maintain a list of all bug-fixes identified, including the application(s) impacted, the requested date, and the approximate effort required to implement.

5.1.5 The contractor shall support PARCA in defining and implementing business rules for reporting of EVM submissions into the Central Repository, assessing compliance with the PARCA EVM policy, and evolving the EVM-CR architecture to support emerging business rules. The contractor shall support the expansion of metrics and compliance reports to assist PARCA in performing compliance checks and oversight on program reporting to the EVM-

CR.

5.1.6 The contractor shall support PARCA in defining and implementing efficient data exchange standards and supporting policy to support efficient IPMR data collection and utilization by PARCA, DCMA, and IPMR stakeholders. The contractor will support PARCA with change management and iterative improvements as needed of the latest IPMR data exchange standards (File Specification and Data Exchange Instructions)

5.1.7 The contractor will provide data technician and analyst support and coordinate with the PARCA team to investigate options which provide automated or semi-automated processes for use of EVM-CR data by EVM-CR stakeholders. The contractor will participate in exploration of options for use of Business Intelligence (BI) tools and appropriate hosting arrangements within CR or elsewhere in the AT&L enterprise.

5.1.8 The contractor shall maintain capability of the EVM-CR to support pushing level 1 data to DAMIR via web service or to expose level 1 data to the service databases via a pull web service. The contractor will also coordinate priorities with PARCA to establish necessary data exchange capabilities to allow external stakeholder data systems (e.g., CADE) to gain access to EVM-CR data in accordance with any established MOUs between PARCA and the external stakeholder. This effort will include coordination effort with stakeholders to align metadata between systems and participation in joint design, requirements definition and corrective action efforts.

5.1.9 Service-Oriented Architecture (SOA) Support for EVM-CR

The contractor will support PARCA in defining selected Defense Acquisition data elements to be exchanged, institutional responsibility for maintenance of the authoritative copy of each data element within the EVM-CR, and for making data available via SOA services. This effort will include participation in joint design and requirements meetings with the services and AT&L AV SOA team, review of draft policies and guidance, and supporting AV SOA, DAMIR, and service requirements for updates to the EVM-CR web services for remote data access.

5.2 EVM-CR Helpdesk

The contractor shall provide help desk and related support services to EVM Repository stakeholders.

5.2.1 Helpdesk User Account Administration

The contractor shall administer user accounts for the EVM-CR system and in doing so comply with all DoD security policies.

5.2.1.1 The contractor shall create and maintain an account management standard operating procedure for the EVM-CR and all related applications. This manual will describe use and operation of the account management application; the account creation, deletion, and administration process; and related business rules. Initial submission of this document to the PARCA government staff for approval is required within 30 days of contract award.

5.2.1.2 The contractor shall submit a need to know verification request within .5 business days of receiving an account request.

5.2.1.3 The contractor shall submit the account for final approval to a PARCA government POC within 0.5 business days of receiving need to know verification.

5.2.1.4 The contractor shall ensure all user account information is normalized per the account management standard operating procedure.

5.2.1.5 The contractor shall ensure all user accounts are deleted or made inactive as appropriate per the account management standard operating procedure.

5.2.1.6 The contract shall perform all account management and maintenance procedures in accordance with the SOP, to include account creation, renewals, change audit management, etc.

5.2.1.7 The contractor shall manage and administer the EVM-CR Portal NDA repository and access control functions. This will include collection, review, and organization of NDAs, user groups and access control within the EVM-CR and Portal.

5.2.2 Helpdesk Resolution of User Issues

The contractor helpdesk shall provide resolution to all EVM-CR issues including but not limited to: accessibility issues, website issues, or how-to issues dealing with the EVM- CR. If the issues cannot be resolved by the helpdesk, the contractor shall refer the issues to the appropriate third party.

5.2.2.1 The contractor shall acknowledge receipt of all helpdesk requests to the user within .5 business days of the request.

5.2.2.2 The contractor shall provide a weekly update to users for any issues that cannot be resolved immediately.

5.2.2.3 Routine password reset requests will be resolved within .5 business days.

5.2.2.4 The contractor shall forward non-IT inquiries to the appropriate parties (e.g., the PARCA government staff or other PARCA support contractors).

5.2.3 Helpdesk Tracking of User Issues

The contractor helpdesk shall maintain a detailed tracking system for all help desk inquiries to the EVM-CR system.

5.2.3.1 The contractor shall maintain a database that tracks all inquiries to the help desk, including the initial date, description of issue, helpdesk analyst assigned, status, application the issue is associated with, organization or program the user is associated with, and resolution date. Additional fields may be requested by the PARCA government staff as necessary.

5.2.3.2 The contractor shall ensure that all helpdesk inquiries forwarded to other parties (e.g., the PARCA government staff, other PARCA support contractors) are tracked to resolution.

5.2.3.3 The contractor shall make recommendations on software or business process improvements to avoid repeat issues as appropriate.

5.3 Database Administration. The contractor shall be responsible for a variety of EVM-CR and Portal database administration activities.

5.3.1 The contractor shall ensure that the contract list and all associated information are normalized and up to date in the EVM-CR.

5.3.2 The contractor shall assist the PARCA government staff in ensuring that data within the EVM-CR is correctly labeled and properly organized.

5.3.3 The contractor shall provide hands-on support to assist with initialization and startup for new programs, contracts, and other data reporting activities within the EVM-CR and Portal.

5.4 Data Quality & Analysis.

5.4.1 Contractor shall monitor EVM cost performance and schedule Reporting Compliance and submission data quality. The contractor will collect and review contract CDRLs and assess reporting compliance in accordance with CDRL requirements and PARCA defined business rules.

5.4.2 The contractor shall provide data technician and analysis support to help define and implement standardized methods of assessing cost performance and schedule data quality. Data quality assessments will includes reporting level 1 DAMIR-compatible checks, lower level WBS quality checks, cross-checks between IPMR cost performance and IMS data checks, etc.

5.4.3 The contractor will work with Services and Agencies to resolve data quality gaps.

5.4.4 The contractor will interface with other OSD entities to gather and document requirements to expose data quality metrics and assessments across the enterprise.

5.5 EVM CR Training Support

5.5.1 The contractor will support the development of EVM-CR training and outreach materials in close coordination with PARCA. This may include PowerPoint slides, hands on training materials and exercises, on-line training environments, and other formats as prioritized and envisioned by PARCA.

5.5.2 The contractor will support the update of the EVM CR User’s Manual as required to maintain consistency with current operational functionality and other training and outreach materials.

5.5.3 The contractor will support quarterly and ad hoc training sessions via webcast or travel to PARCA designated location.

5.5.4 The contractor is also expected to support a variety of outreach activities, for example EVM-CR presentations at NDIA-sponsored events.

5.6 Network/Systems Administration for EVM-CR Systems

The contractor will be involved in every aspect of maintaining EVM-CR systems, installing new hardware/software, and ensuring that all IT security requirements are met. The contractor shall assist PARCA staff and support contractors and its users on all EVM-CR-related IT issues. The contractor shall provide back-up support for IT staff so that there is no disruption to operations when key personnel are unavailable to complete assigned tasks.

The contractor shall provide Systems Administrator support to the EVM-CR with a wide variety of network, database, and security systems administration activities. These include fault monitoring, performance monitoring and reporting, trouble isolation and coordination, configuration management (CM), software/hardware installation, and security management.

5.6.1 Contractor shall prepare test plans and test and configure new versions of currently installed and newly identified software, develop and maintain Standard Operating Procedures and other related documentation for server hardware and configurations, troubleshoot Windows-related problems; maintain currency of security patches; and establish and maintain individual, organizational, project, and enterprise file-share permissions, install cable runs among network servers, interconnections, bridges, repeaters, switches and workstations, as needed.

5.6.2 Contractor shall provide preventative maintenance functions, including pre-approved, coordinated, and planned authorized outages (AOs) in order to perform proactive and remedial maintenance using software tools.

5.6.3 Contractor shall interact with network services, software systems engineering, and applications development to restore service or identify and correct core problems.

Contractor shall simulate or recreate user problems to resolve operating difficulties as needed or caused by the EVM-CR.

5.6.4 Contractor shall act as liaison among the PARCA, suppliers, and other technical groups to resolve network and hardware problems. Contractor shall analyze performance problems and recommend solutions to enhance functionality, reliability, and usability of the EVM-CR.

5.6.5 Contractor shall notify all users via email at least 3 days prior to any planned system outages.

5.7 EVM-CR Public Website

The EVM-CR public website provides policy information and training materials to stakeholders from government and industry. The contractor will be responsible for posting content developed by the PARCA government staff and other PARCA support contractors and also for developing content for IT-related topics.

5.7.1 Website Content Posting

The contractor shall post all content provided by the PARCA government staff and not requiring a design change to the public website within 1 business day of receipt.

5.7.2 Website Maintenance

The contractor shall maintain the public website and ensure that it is up to date with all DoD content and security rules and regulations.

5.7.3 Website Development

The contractor may be required to make design changes to the EVM-CR public website as directed by the PARCA government staff.

5.8 Contract Management.

Table 1 provides a schedule of additional contractor deliverables.

Table 1. Deliverables Schedule

DELIVERABLE

DUE DATE

EVM-CR Monthly Report Monthly

Non-Disclosure Agreement As required EVM-CR Data Quality Analysis Monthly EVM-CR input to DAES Monthly Bug/Enhancement Lists As required Training and Outreach Materials and Documentation Updates As required EVM CR User Guides As Required Development Status Summary Metrics and Product Backlog Weekly EVM-CR Enhancement Build/Sprint Plan Quarterly EVM-CR Maintenance and Enhancements Updates In accordance with Build/Sprint Schedule

In fulfillment of this effort, the contractor shall provide the deliverables identified above. All deliverables shall be submitted to the Deputy Director PARCA, unless otherwise agreed upon.

Unless otherwise specified, the Government will have a maximum of ten (10) working days from the day the draft deliverable is received to review the document, provide comments back to the contractor, or disapprove the deliverable(s). The contractor will have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government.

The format for individual deliverables will be determined through consultation between the Task Monitor and the Deputy Director PARCA. Products that reflect the contractor’s analysis and opinion (e.g., studies or analyses) may be in contractor format. Products that are to be used by the Deputy Director PARCA in the execution of his responsibilities (e.g., briefings, plans or reports) will be in a specified Government format. All documents will be provided in either hard copy or electronically as requested by the COR. Electronic documents will be provided in the appropriate Microsoft Office format (e.g., Word or PowerPoint); if appropriate, the Government may be asked that they be provided in compressed or PDF format.

The data below identifies the deliverables resulting from the above defined tasks. All due date are to be completed within the period of performance. Weekends and Government holidays are non-working days.

Monthly Status Report and Quarterly Reviews Within 30 days after the date of award, the contractor shall provide a work plan to the COR and the Deputy Director PARCA which will present detailed information regarding the specific contractor tasks that will be performed and how the tasks will be accomplished. The contractor shall document the efforts performed in the completion of each task in a detailed monthly status report due on or before the 15th of each month and include a breakdown by task of the amount of funding expended on each task for the preceding month and the cumulative total for each task. The status report shall include, at a minimum:

Progress for the period: detailed progress report of findings, activities and accomplishments during the reporting period, and summary of work accomplished during the reporting period and percent complete.

Resource status; costs shall be attributed to specific subtasks or activity.

Problems encountered: identification of any problems, issues or delays and recommendations as to their resolution, and any corrective action that was taken to correct identified problems.

Activities planned for the next reporting period: planned activities, as well as the status of any/all deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s).

Strategy revisions: recommended changes to include any lessons learned

“If Necessary” a quarterly review shall be conducted between the contractor representatives, Task Monitor, COR and CO. The meeting shall be held at either the contractor facility or Government program office location. At the meeting, the program status shall be brief by the contractor and identify any potential problems that may adversely impact the program cost and schedules. Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR.

5.9 Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

General quality measures, as set forth below, will be applied to each work product received from the contractor under this statement of work.

Accuracy - Work Products will be accurate in presentation, technical content, and adherence to accepted elements of style. Written documents will be in formats as specified above and shall be 99% free of grammar and spelling errors.

Appearance - All work products will be neat and attractive, reflecting the role that the DCARC fulfills and the level at which work products will be used.

Clarity - Work Products will be clear and concise. Any/All diagrams shall be easy to understand and be relevant to the supporting narrative.

Consistency to Requirements - All work products must satisfy the requirements of this statement of work.

File Editing - All text and diagrammatic files will be editable by the Government.

Format - Work Products will be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals.

Timeliness - Work Products will be submitted on or before the due date specified in this statement of work or submitted in accordance with a later scheduled date MUTUALLY AGREED UPON WITH the Deputy Director PARCA and the contractor Task Manager. ALL DEVIATIONS WILL BE

PROVIDED IN WRITING.

Performance Requirements Summary

Performance Objective Standard Performance Threshold Method of Surveillance

PRS #1

Contractor shall maintain the EVM-CR to provide PARCA, the Service Acquisition community, and the DoD acquisition and cost communities timely access to EVM data when needed to support management oversight and cost estimate activities.

(5.1)

Operation & maintenance of EVM-CR applications

Maintenance of Security program

EVM-CR working as intended

EVM-CR applications remain security compliant & minimal downtime

No Security Violations

All critical bugs corrected within 5 business days

99.9% Operational Availability except planned maintenance schedule

100% Inspection by the COR/

TM

PRS #2

The Contractor shall support Monthly EVM-CR Data quality analysis and reporting to AT&L and into the DAES reporting process. (5.1.2)

100% Inspection by the COR/

TM

PRS #3

Helpdesk Support (5.1.8)

Administration of user accounts

Response received for user issues

Compliance with standard operating procedure and PWS timetables

100% of requests acknowledged and/or addressed

90% resolution within 10 days

100% Inspection by the COR/

TM

PRS #4

Portal and application minor enhancements (5.3)

Operation, installation of third party,& maintenance of portal/applications

Bugs corrected

Portal and applications remain security compliant & minimal downtime

All critical bugs corrected within 5 business days

99.9% Operational Availability except planned maintenance schedule

Contractor monitoring and

COR/TM

verification

PRS# 5

The contractor shall correct all reported software bugs to the EVM-CR portal applications.

(5.3.1)

EVM-CR portal applications working as intended

Correct all reported bugs within 5 business days of report or if the bug cannot be corrected in that timeframe the contractor must provide an estimate of the number of man-hours required to correct the bug(s).

99.9% Operational Availability except planned maintenance schedule

100% Inspection by the COR/ TM of bug-fixes log

PART 6

OTHER CONTRACT REQUIREMENTS

6.1 ADMINISTRATIVE CONSIDERATIONS

The Office of Performance Assessment and Root Cause Analysis (PARCA) was created in December 2009 as the principal DoD office for conducting performance assessments and root cause analyses of Major Defense Acquisition Programs (MDAPs) as statutorily required by the Weapon Systems Acquisition Reform Act (WSARA) of 2009, Public Law 111-23. A key element of PARCA's statutory responsibility entails evaluating the utility of performance metrics for cost, schedule, and performance of MDAPs. The implementation and use of EVM across the Acquisition Community falls within PARCA's area of responsibility. The contractor shall be responsive to the Deputy Director PARCA for completing the tasks and deliverables defined within this PWS.

Within two weeks of award, the contractor will conduct an initial orientation briefing. The intent of the briefing is to facilitate the communication process between the Government and the contractor by introducing key task participants and explaining their roles, reviewing communication ground rules, and assuring a common understanding of subtask requirements and objectives.

The orientation briefing will be held at a location and date and time mutually agreed upon by both parties. At the briefing, the contractor will outline the approach and schedule for the various subtasks as well as address the control and management mechanisms they will use to oversee their work.

6.2 Points of Contact

6.2.1 Contracting Officer’s Representative (COR)

The COR supports the CO/CA during administration of this effort by:

Making final decisions regarding any recommended rejection of deliverables;

Providing technical clarification relative to overall workload matters;

Providing advice and guidance to the Contractor in the preparation of deliverables and services; and Providing acceptance of deliverable products to assure compliance with requirements.

PARCA Government Task Monitors (TM):

Government Task Monitor (TM): The TM is the individual within the Program Management function who has overall technical responsibility for this effort. The TM provides technical direction to the Contractor, i.e., shifting work emphasis between areas of work; fills in details, or otherwise serves to accomplish the purposes of this effort

NEITHER the COR or TM have the authority to and may NOT issue any technical direction which:

Constitutes an assignment of work outside the general scope of this effort;

Constitutes a change as defined in the “Changes” clause;

In any way causes an increase or decrease in cost or the time required for performance;

Changes any of the terms, conditions, or other requirements of this effort; and Suspends or terminates any portion of this effort.

All technical direction will be issued in writing by the COR or will be confirmed by the COR in writing within 10 calendar days after verbal issuance. A copy of the written direction will be furnished to the CO and the CA.

In addition to providing technical direction, the TM will:

Monitor the Contractor’s technical progress, including surveillance and assessment of performance, and recommend to the COR to notify the CO and CA, any changes in the requirement;

Assist the Contractor in the resolution of technical problems encountered during performance; and Perform inspection and acceptance or recommendation for rejection of Contractor deliverables and identify deficiencies in delivered items.

If in the opinion of the Contractor, any instruction or direction issued by the COR is outside of their specific authority, the Contractor shall not proceed but shall notify the CO in writing within 5 working days after receipt of any instruction or direction, with an informational copy to the CA.

6.3 POST AWARD EVALUATION OF CONTRACTOR PERFORMANCE

6.3.1 Contractor Performance

Interim evaluations of contractor performance will be prepared on this effort in accordance with FAR Subpart 42.1500. An annual performance evaluation will be prepared, by the COR, at the time of completion of work. In addition to the annual evaluation, interim evaluations will be prepared, by the COR on a quarterly basis. A final evaluation will be prepared at the end of the period of performance of the contract, once all options have been exercised, or if the contract is ended prior to the exercise of some or all of the options. At a minimum the annual evaluations for this contract/task order will be entered into the Contractor Performance Assessment Reporting System (CPARS). The contractor will have access to CPARS for this contract and will enter their responses and comments to the evaluations and/or concurrence electronically in the system. The Contracting Officer’s Representative and the Contracting Officer will provide guidance on using CPARS. CPARS is available on line at http://www.cpars.csd.disa.mil/. The tentative schedule for interim annual and final performance evaluations is provided below, and will be finalized at the time of contract completion.

Interim and final evaluations will be provided to the Contractor as soon as practicable after completion of the evaluation but not longer than thirty (30) calendar days after the scheduled completion. The Contractor will be permitted thirty (30) calendar days to review the document and to submit additional information or a rebutting statement. Any disagreement between the parties regarding an evaluation will be referred to an individual one level above the CO, whose decision will be final.

Copies of the evaluations, Contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions.

Contractors that have Internet capability may access evaluations through a secure Web site for review and comment by completing the registration form that can be obtained at the following address:

http://cpscontractor.nih.gov.

6.4 INVOICING

The Contractor shall invoice no more frequently than MONTHLY against each separate order.

Invoices shall clearly identify hours, rates and materials charged during the period. Travel charges must contain location and dates and items must be identified by subject (i.e. meals, rental car, and airfare.) Training Facility charges must contain location and dates and itemized lists of expenditures.

Other invoice requirements are set forth in FAR 52.232-25 and the PWS.

6.5 TRAVEL

The Contractor will be reimbursed for travel to provide support at a Government site or other site as may be specified and approved by the COR or TM under this effort. All travel shall be approved, by the COR or TM, prior to commencement of travel. The contractor shall be reimbursed for actual allowable, allocable, and reasonable travel costs incurred during performance of this effort in accordance with the Federal Travel Regulations currently in effective on date of travel.

Work will be performed in contractor and government facilities located in the DC Metro area, currently Mark Center, Alexandria, VA. Travel requirements include travel to and from Pentagon and other government organizations’ facilities within Washington DC area. Travel may also be required in support of training activities both inside and outside of the DC Metro area.

6.6 PERSONNEL REQUIREMENTS

Contractor will provide personnel consistent with requirements from this PWS and the staffing plans in the contractor’s technical quote.

6.7 APPLICABLE PUBLICATIONS

http://www.cpars.csd.disa.mil/

Publications applicable to this PWS are listed below. All publications listed are available via the Internet at the specified address.

Mandatory – DoDD 5000.01, “The Defense Acquisition System”, November 20, 2007

Mandatory – DoDI 5000.02, “Operation of the Defense Acquisition System”, December 2, 2008

Mandatory - Military Standard 881C, “Work Breakdown Structures for Defense Materiel Items,” October 3, 2011

Mandatory – DoD Instruction 8510.02, DoD Information Assurance Certification and Accreditation Process (DIACAP), “November 28, 2007

Mandatory – Interim DoD IA Accreditation and Certification Process Guidance Memorandum, July 6, 2006 (http://iase.disa.mil/ditscap/signed-diacap-memo.pdf) and associated references

Mandatory – Department of Defense (DoD) Directive 5200.01, “DoD Information Security Program”, Certified Current as of October 9, 2008

Mandatory – DoD Directive 8500.1, “Information Assurance (IA)”, November 21, 2003

Mandatory – DoD Instruction 8500.2, “Information Assurance (IA) Implementation”, February 6, 2003

Mandatory – DoD 8570.01-M “Information Assurance Workforce Improvement”, Incorporate change 2, dated April 20, 2010

Mandatory – CJCSI 6510.01D, “Information Assurance (IA) and Computer Network Defense (CND)” 15 Aug 2007

Mandatory – DoD Instruction 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP)," November 28, 2007

Mandatory – Subchapter III of Chapter 35 of title 44, United States Code, “Federal Information Security Management Act (FISMA) of 2002”

Advisory – Defense Federal Acquisition Regulation Supplement (DFARS) Subpart 234.2

Advisory – Earned Value Management Implementation Guide (EVMIG)

Advisory – American National Standards Institute/Electronic Industries Alliance Standard 748

(ANSI/EIA-748)

Advisory – DoD 5000.04 M-1, Cost and Software Data Reporting (CSDR) Manual http://iase.disa.mil/ditscap/signed-diacap-memo.pdf