Attachment 2 - Task Order One PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR TASK ORDER ONE (1)

Office of Cost Assessment and Program Evaluation (OSD-CAPE) Enterprise Visibility and Management of Operating and Support Cost (EVAMOSC)

General Information

1. GENERAL: This is a non-personnel services contract to provide Database Design, Implementation, Operation, and Data Platform Sustainment Services. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personnel services necessary to perform Database Design, Implementation, Operation, and Data Platform Sustainment Services as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: The mission of the Office of the Secretary of Defense Cost Assessment and Program Evaluation (OSD-CAPE) is to provide the Department of Defense (DoD) with timely, insightful and unbiased analysis on resource allocation and cost estimation problems to deliver the optimum portfolio of military capabilities through efficient and effective use of each taxpayer dollar. In achieving this mission, one of OSD-CAPE’s primary goals is to provide data driven insight into the costs of major acquisition programs. This detailed analysis enables responsible budgeting and proactive management decisions so that the Department can control cost and achieve savings. In recent years, the DoD has focused on understanding the costs incurred by weapons systems during the sustainment phase and underlying causes of these cost outcomes. However, despite renewed emphasis on controlling sustainment costs, the DoD lacks complete, accurate, and granular data on operating and support (O&S) costs for many major acquisition programs, including ground vehicles.

1.2.1 10 U.S. Code, Section 2337a (Guidance on Life-Cycle Management) assigns responsibility for “developing and maintaining a database on … actual operating and support costs for major weapons systems” to the Director, CAPE. While OSD-CAPE has historically administered its responsibility for O&S cost data via policy for Military Department data requirements, the enterprise O&S database required by Title 10 does not currently exist within the DoD. The lack of available O&S cost data has made it difficult to calculate sustainment costs for multiple systems, including ground vehicles. To address these deficiencies, OSD-CAPE will develop a data system to simultaneous address current O&S cost data deficiencies and its statutory requirement. The resulting Enterprise Visibility and Management of Operating and Support Costs (EVAMOSC) data system will address known issues with O&S cost data completeness, accuracy, granularity, and reporting frequency.

1.2.2 OSD-CAPE intends to develop and deploy the EVAMOSC data system in increments. This

Performance Work Statement covers the tasks and objectives associated with EVAMOSC Task Order 1, which will aim to meet O&S cost data requirements for U.S. Army weapons systems during the base period.

1.3 Objective: The primary objective of this effort is to develop and deploy the EVAMOSC data platform to collect cost data on U.S. Army major weapons systems, while implementing a design and architecture that is scalable to include weapon systems across the DoD in future increments. The EVAMOSC data system will incorporate technologies for ingesting, aggregating, standardizing, visualizing, reporting, and securing a large amount of data (i.e., over 75 sources) from an array of systems currently serving multiple functional communities: financial management, logistics, maintenance, human resources, property, and acquisition. The primary challenge in this effort is development of the business rules and logic model required to map O&S cost data from the aforementioned disparate functional areas to individual Army weapon systems.

1.3.1 This effort will demonstrate an enhanced capability to aggregate and fuse multiple data sources to provide complete, accurate, and granular O&S cost profiles at a required frequency (monthly in most cases). This investment in O&S cost data infrastructure will improve the DoD’s ability to understand the costs associated with operating and sustaining major weapons, the quality of lifecycle cost estimates for future programs, and the capability to identify and manage root causes of O&S cost growth.

1.3.2 The EVAMOSC data platform will reside on Amazon GovCloud and will host the development and test environments necessary to produce O&S cost data profiles for major weapons systems. The EVAMOSC platform will then transmit, or otherwise make available for ingestion, these cost data profiles for production and publication on the OUSD (Comptroller) ADVANA platform. The ADVANA platform will host any public-facing applications to enable broader DoD community to access EVAMOSC data.

Furthermore, CAPE will use ADVANA’s “platform-as-a-service” capabilities to address all Authority-to- Operate (ATO) and user management requirements associated with exposing the EVAMOSC application to NIPR access. While the contractor may generate information required to assist with security administration, authority to operate, and risk management framework processes, he will not be inherently responsible for execution of these functions for either the EVAMOSC or ADVANA platforms.

1.4 Scope: The contractor shall perform Database Design, Implementation, Operation, and Data Platform Sustainment support, to include technical, administrative, and professional services, for the purpose of developing and implementing the OSD-CAPE EVAMOSC system.

1.5 Period of Performance: The period of performance shall be for one (1) Base Period of 12 months and four (4) 12-month option periods.

1.6 General Information:

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. The QCP shall be delivered via electronic mail within 30 days after contract award. Amendments/changes to the QCP shall be delivered to the task monitor (TM), COR and KO within three business days following any change (Deliverable: Quality Control Program).

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays: The contractor is not required to perform service on 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.4 Hours of Operation: The contractor is responsible for conducting business, between the OSD-CAPE core hours of 8:00 AM to 5:00 PM, arriving no earlier than 6:30 AM and departing no later than 6:30 PM 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. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS 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 workforce are essential.

1.6.5 Place of Performance: The primary places of performance will be the Government facilities in the Washington/Northern Virginia area. The Government will furnish office space and office equipment for work performed at Government facilities. Contractor personnel may be requested to work at the Government’s alternate locations during emergencies and emergency exercises. Individual Contractor personnel may be designated as essential personnel to support contingency operations at alternate Government locations during actual emergencies and emergency exercises. The Government locations referenced in this paragraph are:

Office of Cost Assessment and Program Evaluation 1800 Defense Pentagon Washington, DC 20301

AND

Mark Center 4800 Mark Center Dr Alexandria, VA 22311

1.6.6 Type of Contract: The government will award a hybrid contract that will consist of Firm Fixed Price, Cost, and Cost Plus Fixed Fee.

1.6.7 Security Requirements: The contractor shall have a Secret Facility Clearance from the Defense Counterintelligence and Security Agency at the time of proposal submission and maintain the level of clearance for the life of the contract. All Contractor personnel performing work under this contract must possess an interim Secret security clearance from the DoD Consolidated Adjudications Facility prior to working on this contract and maintain a final Secret security clearance, once attained, for the life of the contract. These security requirements are in accordance with the attached DD Form 254. The Contractor shall comply with all security policies and procedures that apply to DoD and OSD-CAPE. Security procedures shall be made available to Contractor personnel upon award of the contract.

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information, and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured. The government will provide necessary credentials and training to individuals working in OSD-CAPE spaces to ensure all personnel are able to comply with opening and closure procedures for OSD-CAPE’s open-Secret spaces.

1.6.7.2 Key Control: The Contractor shall establish and implement methods of making sure 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 shall 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 duplicate keys/key cards to the Contracting Officer.

1.6.7.2.1. In the event 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.7.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.7.3 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed 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.8 Special Qualifications: Contractor personnel will be required to sign a Non-Disclosure Agreement once contract is awarded.

1.6.9 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), OSD-CAPE task monitor (TM), 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.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance;

maintain written and oral communications with the Contractor concerning technical aspects of the contract;

issue written interpretations of technical requirements, including Government drawings, designs, and specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Key Personnel: The labor categories listed below are considered essential to the work being performed under this contract. The Government reserves the right to review resumes for candidates in all listed Key Personnel billets to ensure the individuals are qualified to perform the tasks associated with the billet. Before removing, replacing, or diverting any of the listed or specified personnel, the Contractor shall

(1) notify the Contracting Officer reasonably in advance and (2) submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract. The Contractor shall make no diversion without the Contracting Officer's written consent; provided that the Contracting Officer may ratify in writing the proposed change, and that ratification shall constitute the Contracting Officer's consent required by this document. See Attachment 3 for estimated workload for these individuals.

All Key Personnel are required to have the following:

• Experience with development and deployment of data platforms and data analytics in a cloud computing environment

• Experience working with EVAMOSC stakeholder communities: OSD-CAPE, Cost, Financial

Management, Acquisition, Logistics, Maintenance, and Product Support.

• Experience with US Army and Marine Corps financial and logistic processes (Increment 1 specific)

• Experience with DoD business, financial management, and logistics, and maintenance Enterprise

Resource Planning (ERP) systems

Requirements for specific Key Personnel positions are stated below.

1.6.11.1 Product Manager:

Required: The contractor’s Product Manager is required to have a SECRET clearance. The designated Product Manager shall have a minimum of 10 years of experience relating to DoD major systems or programs. Familiarity with the OSD-CAPE 2014 Operating and Support Cost Estimating Guide and Risk Management Framework (RMF) is required. The designated Product Manager shall have, at minimum, a Bachelor’s Degree from an accredited institution.

Preferred: It is preferred that the contractor’s Program Manager have at least 2 years of experience with DoD cost data analytics and weapons system cost estimating procedures, Project Management Professional certification, and experience with operating in NIPR environments.

1.6.11.2 Technical Architects:

Required: The contractor’s Technical Architects are required to have a minimum SECRET clearance.

Technical Architects shall have at least a B.S. degree from an accredited institution in either information technology, computer science, computer engineering, or a related field. The designated Technical Architects shall have appropriate certifications required for implementation of the contractor’s proposed technical solution. The Technical Architects shall have experience working with DoD business and financial management source data systems.

Preferred: It is preferred that the contractor’s Technical Architects have experience with DoD Enterprise Resource Planning systems and experience with operating in NIPR environments.

1.6.11.3 Senior Cost Analyst:

Required: The contractor’s senior cost analyst is required to have a minimum SECRET clearance. Senior cost analysts will have at least a M.S. degree from an accredited institution in either Operations Research, Applied Mathematics, Industrial Engineering, Economics, or a related Field. The Senior Cost Analyst will have a minimum of 5 years’ experience in DoD business cost analysis and cost policy. The designated Senior Cost Analyst will have experience in operations research, cost estimating methodologies, and cost analysis techniques.

Preferred: It is preferred that the contractor’s Senior Cost Analyst has worked in weapons system cost estimation and has experience in preparing estimates for the O&S portion of the weapon system lifecycle.

1.6.11.4 Functional Expert Consultants and Subject Matter Experts:

Required: The contractor’s Functional Expert Consultants and Subject Matter Experts are required to have a minimum SECRET clearance.

Preferred: It is preferred that the contractor’s Functional Expert Consultants and Subject Matter Experts have experience with weapons system cost data and experience with operating in NIPR environments.

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such 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. Contractor personnel will be required to obtain, use, and display a Common Access Card in the performance of this service.

1.6.13 Contractor Travel: In accordance with FAR 31.205-46, Travel Cost, the contractor shall provide travel in support of this contract. The contractor shall provide a written request to the Contracting Officer Representative (COR) for approval prior to making any travel arrangements. Requests for travel shall include the name of the person(s) traveling, travel destination, dates of travel, mode of transportation, and estimated costs for travel. All travel must be pre-approved in writing by the COR prior to purchase of any tickets and commencement of travel. The Contractor shall be reimbursed for actual allowable, allocable, and reasonable travel cost incurred during performance efforts in accordance with FAR 31.205-46. Travel shall be addressed as a Cost item

Note. Travel to and from the contractors’ normal place of duty will be not be covered by the Government under this contract. Parking expenses at the normal place of duty, commuter lots, or metro parking garages will not be paid by the Government under this contract.

1.6.14 Other Direct Costs: The contractor shall be responsible, at the direction of the COR, for purchasing any software licenses, hardware, and/or virtual computing products required for performance of the architecture tasks described in Part 5 of this PWS.

1.6.15 Data Rights: The Government has unlimited rights to all documents and material produced under this contract. Any and all source code, models, prototypes, programming, language, licensure, enterprise-wide rights, software, Contract Data Requirement Lists (CDRLs), manuals, training documents, and other similar products and related data developed, modified, or created under this PWS shall be exclusively at the United States (U.S.) Government's expense. Per DFARS 252.227-7014(b)(1), all of these items must be delivered to the U.S. Government with unlimited rights. As such, the Government may use, modify, reproduce, release, perform, display, or disclose the source code in whole or in part, in any manner and for any purpose whatsoever, and it may authorize others to do so. These documents and materials, exemplified in the list above, may not be used or sold by the contractor without written permission from the Contracting Officer. This right does not abrogate any other Government rights.

1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Phase In: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board during the 30-days Phase-In. During the phase-in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date for the PWS task areas described in Section 5

1.6.17.1 Phase In Period: During the phase in period, the Contractor shall facilitate the accomplishment of a seamless transition. Phase in services shall begin on the effective date of the award and shall be complete on the date which is 30 days after the effective date when the contractor will assume full responsibility for Tasks 5.2 and beyond in Part 5 of this PWS.

1.6.17.2 Phase In Plan: The Contractor shall provide a Phase In Plan, which shall include the following elements: (Deliverable: Phase In Plan)

a. A detailed transition methodology in logical sequence to ensure a smooth transition of all tasks and subtasks of the contract without interruption or degradation of service levels;

b. An overview of the transition efforts and a description of the activities to transition;

c. A schedule with milestones for each activity and anticipated completion date for Phase In;

d. Identification of points of contact (POCs) for liaison between the Government, the prime contractor, and other critical contracted industry partners; and

e. Identification of risks, issues, and mitigation strategies

1.6.18 Contractor Manpower Reporting:

(a) The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address:

http://www.ecmra.mil/.

(b) There are four separate ECMRA tools at the ECMRA website: Army, Air Force, Navy and All Other Defense Components. The appropriate ECMRA reporting tool to use is determined by the requiring activity being supported by the service. The Contractor shall use the “All Other Defense Components” tool unless otherwise directed by the Contracting Officer’s Representative or Contracting Officer.

(c) Reporting inputs will be for the labor executed during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. The Contractor shall completely fill in all required data fields. The Contractor shall enter initial data into the appropriate ECMRA tool to establish the basic contract record no later than 15 business days after receipt of contract award or contract modification incorporating this clause. The Contractor shall notify the Contracting Officer when the basic contract record has been established in the appropriate ECMRA tool.

(d) Contractors may direct technical questions to the help desk at: http://www.ecmra.mil.

[Reference: DPAP memorandum of 28 November 2012, “Enterprise-wide Contractor Manpower Reporting]

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

API Application Programming Interface BCTF Boards, Commissions, and Task Forces C5ISR C5 Intelligence, Surveillance, and Reconnaissance CAC Common Access Card CAP Contractor Acquired Property

CAPE Cost Assessment and Program Evaluation CAR Corrective Action Report CC Cloud Computing CDRL Contract Data Requirement List CFR Code of Federal Regulations CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative COTS Commercial-Off-the-Shelf DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DOD Department of Defense DODD Department of Defense Directive DTIC Defense Technical Information Center ERP Enterprise Resource Planning EVAMOSC Enterprise Visibility and Management of Operating and Support Costs FAR Federal Acquisition Regulation FTR Final Technical Report GFE Government Furnished Equipment GFI Government Furnished Information HIPAA Health Insurance Portability and Accountability Act of 1996 IGCE Independent Government Cost Estimate IL4 Impact Level 4 IMAG Information Management Advisory Group IMS Integrated Master Schedule IT Information Technology KO Contracting Officer MDS Mission-Description-Series MSR Monthly Status Report NIPR Non-Secure Internet Protocol Router OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Cost OSD Office of the Secretary of Defense O&S Operating and Support PAO Post Award Orientation PIPO Phase In/Phase Out PKI Public Key Infrastructure PMP Project Management Plan POC Point of Contact POP Period of Performance PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program RA Requiring Authority RMF Risk Management Framework SIA System Interface Agreement SME Subject Matter Expert SRG Security Requirements Guide TB Terabytes TBD To Be Determined TE Technical Exhibit TM Task Monitor

TMS Type-Model-Series USMC United States Marine Corps WHS Washington Headquarters Services

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The government will provide basic services to phones, desks, utilities, information technology, and general office supplies) while working in Government facilities.

3.2 Facilities: Basic facilities such as workspace and its associated operating requirements (i.e., phones, desks, utilities, information technology, and general office supplies) will be provided while working in Government facilities. Tele-workers will only use government furnished equipment (GFE) to remotely access the OSD-CAPE network.

3.3 Equipment: The Government will provide will provide basic services to phones, desks, utilities, information technology, and general office supplies while working in Government facilities. Tele-workers will only use government furnished equipment to remotely access the OSD-CAPE network. Additionally, the Government will provide access to government furnished computers to enable access to OSD-CAPE networks and For Official Use Only data.

3.4 Information: The Government will provide the contractor with access to information as necessary to complete the tasking under this contract. Any Government Furnished Information (GFI) such as federal policies, directives, instructions and documents provided during performance of/or resulting from this PWS shall be provided with a Distribution Statement setting forth the disclosure limitations with which the contractor must comply. In the event that GFI is provided without a Distribution Statement, any disclosure shall be in accordance with DFARS 252.204-7000, Disclosure of Information. The contractor shall treat technical data in its possession as Government sensitive information that is not to be released outside of the originating organization.

3.5 Data Environment: The government will provide solutions to store, rapidly access, and maintain large amounts of UNCLASSIFIED Impact Level 4(IL4) DoD data to support a range of O&S cost analytics requirements. Hosting is provided by CAPE Information Management Advisory Group (IMAG) via Amazon Web Services Department of Defense Cloud Computing Security Requirements Guide (DoD CC SRG) (IL4) (GovCloud), in conjunction with C5ISR as the cybersecurity Service Provider.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Part 3 of this PWS.

4.2 Secret Facility Clearance: The contractor shall possess and maintain a SECRET facility clearance from the Defense Counterintelligence and Security Agency at the time of proposal submission and maintain the level of clearance for the life of the contract. The Contractor’s employees, performing work in support of this contract shall have been granted an interim SECRET security clearance from the DoD Consolidated Adjudications Facility at the time of proposal submission and maintain a final SECRET clearance for the life of the contract, once attained.

4.3. Materials: In accordance with FAR clause 52.245-1, Government Property (including material, information, and other direct costs) purchased by the contractor, for which the contractor is entitled to be reimbursed as a direct item of cost under this task order, shall pass to and vest in the Government upon:

- Issuance of the property for use in task order performance,

- Commencement of processing of the property for use in the task order performance, or

- Reimbursement of the cost of the property by the Government (whichever occurs first) As discussed in paragraph 1.6.14 “Other Direct Costs,” the contractor shall be responsible, at the direction of the COR, for purchasing any software licenses, hardware, and/or virtual computing products required for performance of the architecture tasks described in Part 5 of this PWS. Examples of such ODCs may include: virtual computing instances, virtual tool infrastructure, Crowd licenses, Confluence licenses, etc.

4.4. Equipment: NA

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

5.1. Basic Services: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personnel services necessary to perform Database Design, Implementation, Operation, and Data Platform Sustainment Services to support OSD-CAPE’s EVAMOSC initiative. Tasks will include program management; design, develop, and maintain an Enterprise O&S data platform; EVAMOSC data acquisition; analytics and dashboard development; system user management; and platform sustainment.

5.2. Project Management:

5.2.1 Post Award Orientation: The Contractor shall provide a Post-Award Orientation within 7 calendar days of the start of performance. Schedule and conduct this meeting, in coordination with the Task Monitor (TM), Contracting Officer's Representative (COR), and CO. The purpose of the Post-Award Orientation is to: 1) discuss any unique characteristics of the requirement(s); 2) identify stakeholders' roles and responsibilities; 3) review the 30 day transition-in to full performance, and 4) establish a common understanding of cost, schedule, and performance expectations. In preparation for this discussion, the contractor will prepare a briefing to cover the aforementioned discussion topics from the contractor’s perspective. The Government will provide Slides covering the Government perspective on these topics for inclusion in the orientation meeting. (Deliverable: Post Award Brief Slides and Minutes with Attendees List).

5.2.2 Project Management Approach: Provide a Program Management Plan (PMP) within 15 days after start of performance. The Program Management Plan shall provide a resource-loaded schedule that outlines the steps that will be taken, the timeline to completion, and any associated risks with execution of the order. The PMP will be updated quarterly. The update shall specify estimated start and stop dates for any new projects, as well as a risk mitigation plan and a budget aligned to key milestones within the project, to include any anticipated Other Direct Costs (ODCs). The update should highlight any newly defined interdependencies within the tasks and the project(s) schedules. Upon acceptance and approval by the Government, the contractor shall meet the cost, schedule, and forecasted delivery date of all deliverables by taking all reasonable measures to fulfill the requirement (Deliverable: Program Management Plan (PMP)) and shall report monthly status updates in the Monthly Status Report (MSR).

5.2.3 Monthly Status Report. Submit a Monthly Status Report. The MSR shall provide detailed status for the project(s) within the PMP as well as capture an overall status of the order. The MSR reports cost, schedule, and performance against PMP requirements and identifies status of funding, planned versus actual expenditures per project, total monthly and cumulative ODC expenditures, status of known risks, risk mitigation efforts, deliverables funded and date they were funded, technical progress made and schedule status per deliverable, the titles, dates and number(s) of deliverables completed, and the deliverables scheduled to be delivered during the upcoming month. The contractor and TM shall, mutually agree upon specific MSR format, and any additional content not specified in this section; this should be established no later than the Post-Award Orientation. If the MSR shows that a project is not meeting the performance standards set forth in the Service Summary found in Section 6.0, the contractor shall provide the rationale and circumstances preventing the standards from being met. (Deliverable: Monthly Status Report).

5.2.4 Quarterly Program/Project Management Reviews: Conduct quarterly program/project management reviews with the Task Monitor to include detailed information on cost, schedule, performance, risk assessment, and risk mitigation plans (Deliverable: Quarterly Program/Project Management Review).

5.2.5 Final Technical Report: Prior to expiration of the Period of Performance (PoP), submit a Final Technical Report (FTR). The FTR shall include contract-specific background information, objectives, assumptions, specific data collected, conclusions, analyses conducted, and recommendations. Each report shall be delivered to the TM and COR (Deliverable: Final Technical Report).

5.2.6 Contractor Acquired Property (CAP) Report: Contractor Acquired Property (CAP) Report.

Provide copies of the DD Form 250 Material Inspection and Receiving report for all Contractor Acquired Property acquired via Other Direct Cost charging (Deliverable: Contractor Acquired Property Report).

5.3 Design, Develop, and Maintain an Enterprise O&S Data Platform:

5.3.1 Design and Develop an EVAMOSC data platform: The contractor shall use tools and infrastructure provided by the government, as described in Part 3 above, to support a virtual computing environment and rapid scalability for development and deployment of the EVAMOSC platform. Provide a secure and scalable repository of all data types and origins that can scale to 100 terabytes (TB) of data for the primary purpose of collecting, aggregating, and reporting O&S costs for major weapons systems. Integrate both open source and Commercial-Off-the-shelf (COTS) components, as provided on the government furnished cloud environment, to make data available for a wide breadth of analysis. Develop recommendations to ensure scalability and performance of the data platform. Provide engineering techniques to ensure that data platforms are readily accessible, maintained and performing optimally. The vendor is not required to demonstrate prior experience with AWS GovCloud. (Deliverable: Data Architecture Approach).

5.4 EVAMOSC Data Acquisition and Preparation: This task, from the US government’s perspective, is the most challenging aspect of the work required for EVAMOSC and represents the greatest value to OSD- CAPE and the DoD. This task focuses on acquiring and preparing data from DoD business systems in order to compile and present complete, accurate, and granular O&S cost profiles for major weapons systems. See Technical Exhibit 4 for a list of potential data sources. The objective is to develop and sustain data acquisition and business rule automation for O&S cost data reporting requirements and analytics. The Contractor shall generate EVAMOSC data from disparate Service business systems to produce complete O&S cost data profiles, as defined by the OSD-CAPE 2014 Operating and Support Cost Estimating Guide, for all Major Defense Acquisition Programs and any Type-Model-Series (TMS) or Mission-Description- Series (MDS) derivatives of the original programs (e.g., M1A2, M1A2SEP, M1A2SEPV3, etc.). See Technical Exhibit 5 for a list of US Army programs. The contractor shall work with DoD business systems owners from the Defense Agencies and Military Departments to determine what data is needed to complete an O&S cost data map for major DoD weapons systems. Once the contractor determines the data owners and data elements required to provide the desired O&S cost data output for each Military Department, the contractor shall implement an automated ingest approach of data from each identified source system. The Contractor’s ingestion approach shall include the automation of business rules, quality checks, and the development and sustainment of memorandum of agreements and system interface agreements. As previously stated, EVAMOSC Increment 1 will focus on U.S. Army and Marine Corps weapons systems in the ground vehicle commodity group, and the contractor will be responsible for collecting and reporting cost data from Fiscal Years 2015 and beyond. To the maximum extent possible, the contractor will leverage congruencies between the data needs for the ground vehicle commodity group and other commodity groups to enable concurrent development. For example, if an O&S cost data map for Army rotary wing weapons systems is identical to the data map for ground vehicles, the contractor will include this commodity group in Increment 1.

5.4.1 Plan and Coordinate with EVAMOSC stakeholders and Subject Matter Experts from the Military Departments and Defense Agencies to obtain access to data. Based on direction from the U.S. government EVAMOSC project lead, the contractor shall identify source data systems, data elements, and possible reporting frequencies to support EVAMOSC’s O&S data requirements. Coordinate with data system owners to finalize data requirements and formulate access agreements. Create a System Interface Agreement (SIA) for each source system to record the details of access and interface between the source system and EVAMOSC. Assess each system to track the progress of acquiring the data from the source system owner. The system coordination status shall be provided at least weekly. (Deliverables: Integrated Master Schedule (IMS), System Interface Agreement, Weekly System Data Update).

5.4.2 Perform data cleansing and wrangling to achieve assignment of O&S cost data to specific cost elements and major weapons systems. The contractor shall categorize and tag data from multiple DoD business systems for the purpose of assigning operating and support costs to specific elements of the Government’s required cost estimating structure (currently found in the 2014 OSD-CAPE O&S Cost Estimating Guide) and to specific weapons systems at the Type-Model-Series (TMS) or Mission-

Description-Series (MDS) level. The contractor shall document all business rules when standardizing data to support O&S data (cost and non-cost) aggregation or disaggregation to specific weapons systems.

Ensure that all incoming data expressed in dollars are in “Then-Year” and have not been adjusted for inflation or escalation. In instances when the contractor is required to convert incoming data expressed in dollars to a “Then Year” version, explicitly document the source, version, and base year of the index used to perform the conversion. Work with functional SMEs to validate business rules, data models, and create data dictionaries for each source data system. The contractor will document the participants, process, and validation output from testing used to allocate any cost to a particular weapons system (i.e., when assigning costs to a weapons system from an aggregate level that does not allow for direct attribution of a cost). The contractor will alert the Government project lead of any standardization issues identified when conducting data cleansing. (Deliverables: Data Dictionary, Business Rules, Data Models).

5.4.3 Demonstrate and implement a consistent approach for ingestion of new source data from multiple sources through automated data pipelines, currently scoped at 75 systems. Based on the source system agreements in task 5.4.1, the contractor shall develop automated data pipelines that will support the integration and loading of data sets, perform quality checks, transformation, meta-data tagging, and provide visual metrics and reports. The contractor shall report, at least monthly, the health of the data pipelines.

Provide logging and data lineage reports. The contractor shall develop test reports and perform configuration management. Incorporate tools available on the AWS DoD CC SRG IL4 (GovCloud) environment to automate this task to the maximum possible extent. (Deliverables: Automated Data Pipeline Plan, Data Lineage Reports, Data Pipeline Health Reports).

5.4.4 Provide analysis of data schema and structure, and functional validation of data ingested. The contractor shall validate received and ingested data against defined business rules and data structures.

Work with stakeholders to receive acceptance of business rules and data structures, with emphasis on any cost data outcomes requiring allocation versus direct attribution of costs to a weapons system. Document all business rules and data structures that will be used for validation, including stakeholder or participation in business rule development, where required. Design and implement a process for identifying and reporting data deficiencies, errors, and anomalies originating in EVAMOSC source data systems. The contractor’s process shall result in documentation of all data deficiencies, errors, and anomalies discovered.

Incorporate tools, available on the AWS DoD CC SRG IL4 (GovCloud) environment, optimally suited for virtual computing environments and rapid scalability to automate this task to the maximum possible extent.

(Deliverable: Data Validation Dashboard).

5.4.5 Develop a data catalog. The contractor shall develop and sustain an automated way to search a data inventory, data catalog, and metadata repository. The data catalog shall detail all source systems that are available in the EVAMOSC platform with appropriate metadata. The data catalog shall be the primary interface from which to access all information related to tracking data within the EVAMOSC platform.

The data catalog shall collect and display historical metrics from the data pipeline error logs and source data inventory. In addition to error logging, the data catalog shall provide tracking and reporting for data for the full data pipeline, meaning initial acquisition, quality assurance (QA) checking (possibly multiple instances until successful), normalization, and tabulation. This tracking procedure shall fuel many reports and other functionality, including a comprehensive report on all data within the data pipeline, system adherence to Memorandum of Agreements (MOAs), an inventory of all data incorporated into the system, and notifications sent to stakeholders. Incorporate tools available on the AWS DoD CC SRG IL4 (GovCloud) environment to automate this task to the maximum possible extent. (Deliverable: Data Catalog).

5.4.6 Provide support to data governance initiatives. As required by the EVAMOSC US Government Task Monitor, support data governance working group sessions with prepared briefs, data collection, and recommendations for policy change. The contractor shall provide recommendations for cost element definition or business rule changes to support emerging reporting requirements or comparison of costs at an enterprise level. The contractor shall provide feedback on the technical implications of changes to EVAMOSC data governance.

5.4.7 Integrate with the ADVANA Readiness Analytics Working Group. The contractor shall participate in regularly occurring working groups dedicated to improving the accuracy and usefulness of the

ADVANA Readiness Analytics platform.