Attachment 1 - Base IDIQ PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR SINGLE AWARD IDIQ CONTRACT

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

March 1, 2020

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 for the single award IDIQ that are associated with the overarching EVAMOSC effort, which will aim to meet O&S cost data requirements for all DoD major weapons systems.

Task order one (1) will focus on U.S. Army weapon systems. Future task orders will address cost data requirements for U.S. Marine Corps, U.S. Navy, and U.S. Air Force major weapons systems, in addition to the long-term sustainment of the EVAMOSC platform. Whereas Army and USMC O&S cost data is relatively incomplete or missing in many cases, the Navy and Air Force currently have robust O&S cost data systems for certain commodity groups (e.g., ships and aircraft). As a result, future task orders focusing on Navy and Air Force, will primarily entail mapping and integration of existing data into EVAMOSC and improvement of reporting, in contrast to the complex data acquisition and business rule development required for the Army and USMC.

1.3 Objective: The primary objective of this effort is to develop, deploy, and sustain the EVAMOSC data platform. EVAMOSC will serve as the DoD’s authoritative O&S cost data source for major weapons systems, as required by 10 U.S. Code, Section 2337a (Guidance on Lifecycle Management). Further, the data in EVAMOSC will align to the cost element structure outlined in the OSD-CAPE 2014 Operating and Support Cost-Estimating Guide. As stated above, Task Order 1 will primarily focus on developing a database to collect cost data for U.S. Army major weapons systems, but EVAMOSC’s design and architecture must be 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 weapons, a task none of the upstream data systems were implemented to support.

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.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 a five year ordering period.

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, and will be identified in the task order level. 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.

1.6.6 Type of Contract: The contract type is a single award Indefinite Delivery, Indefinite Quantity (IDIQ) that consist of Firm Fixed Price, Cost, and Cost-Plus-Fixed-Fee task orders..

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. Unless stated elsewhere, 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: Special qualifications will identified in specific task orders. Contractor personnel will be required to sign a Non-Disclosure Agreement (DD Form 254) prior to beginning work on the task orders.

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: Key personnel will be identified at the task order level.

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. Specific travel requirements will be identified at the task order level. 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. T

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: Specific Other Direct Costs will be identified at the task order level.

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/Phase Out Period: Phase In/Phase Out requirements will be identified in specific task orders.

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 CAC Common Access Card

CAP Contractor Acquired Property CAPE Cost Assessment and Program Evaluation CAR Corrective Action Report 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 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 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 provide 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) DoD data to support a range of O&S cost analytics requirements. Hosting is provided by CAPE via AWS DoD CC SRG IL4 (GovCloud), and is provided by IMAG 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 Adjudication Facility Office 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, title of 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

General Tasks

5. GENERAL 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: The contractor shall manage requirement, stakeholders' roles and while meeting cost, schedule, and performance expectations.

5.3 Design, Develop, and Maintain an Enterprise O&S Data Platform: The contractor shall design, develop, and implement solutions to store, rapidly access, and maintain large amounts of UNCLASSIFIED data in 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.

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. 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.). 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.

5.5 Operating and Support Cost Self-Service Analytics and Dashboard Development: This task focuses on the development and sustainment of EVAMOSC’s required self-service analytics capabilities. The contractor shall create an analytics roadmap for O&S cost data estimating and metrics reporting. The contractor will implement the capability to use those analytics in a self-service manner to improve visibility, accessibility, and opportunities to manage O&S cost outcomes for major weapons systems. The capability will allow authorized users to access large amounts of data at scale and to perform ad-hoc analysis, including the use of raw source and EVAMOSC-published O&S cost data.

5.6 System User Management and Training. This task focuses on the development and sustainment of processes and EVAMOSC platform features used to manage System user interactions with the platform.

5.7 Platform Sustainment: This task is to continuously innovate and research ways to improve and sustain the EVAMOSC data platform and its analytic capabilities.

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS:

6.1 The Contractor must abide by all statutes, applicable regulations, publications, manuals, and federal policies, procedures.

6.2 Operating and Support Cost Estimating Guide, Office of the Secretary of Defense, Cost Assessment and Program Evaluation, March 2014.

6.3 Department of Defense Instruction 5000.73: Cost Analysis Guidance and Procedures, 2 October 2017.

6.4 Department of Defense Directive 8140.01: Cyberspace Workforce Management, 11 August 2017.

6.5 DPAP memorandum of 28 November 2012, “Enterprise-wide Contractor Manpower Reporting.”

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachment/Technical Exhibit List:

7.1. Attachment 1/Technical Exhibit 1 – Performance Requirements Summary

7.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule

7.3 Attachment 3/Technical Exhibit 3 – Estimated Workload Data

TECHNICAL EXHIBIT 1

Performance Requirements Summary

Performance requirements will vary by task and will be defined in specific task orders.

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

Deliverables schedule will vary by task and will be defined in specific task orders.

TECHNICAL EXHIBIT 3

ESTIMATED WORKLOAD DATA

The estimated workload data will be provided in specific task orders.