J-3_SAMPLE_TO_1_Pool_1_3Oct17.docx

IAC MAC

Pool 1

Sample Task Order #1

Performance Work Statement (PWS)

Orville Wright Tactical Fighter (OWTF)

[Focus Areas: Reliability, Maintainability, Quality, Supportability, and Interoperability (RMQSI) Analysis; Weapons System Operational Analysis; and Software Data and Analysis]

Table of Contents

GENERAL

This document describes the objectives for a Task Order (TO) for a FICTIONAL DoD requirement. This document will be the basis of a potential offeror’s study approach and cost information in support of the Information Analysis Center (IAC) Multiple Award Contract (MAC) proposal preparation for the Full and Open Pool (Pool 1). The Section Three (3) and Four (4) of the PWS, includes a set of requirements including specific tasks and deliverables for the Sample Task Order #1.

All contents provided as a part of this PWS are fictional and no actual IAC involvement is to be pursued, neither any discussions nor details on specific requirements or deliverables will be provided. This document has been tailored to be at the UNCLASSIFIED//FOUO level and apply to this fictional Sample Task Order #1 only.

1.1 BACKGROUND

The Orville Wright Tactical Fighter (OWTF) is the Department of Defense (DoD)'s joint mobile fighter and command center, serving as the focal point for defining affordable next generation Unmanned Aircraft Systems (UAS) weapon systems for the Navy, Air Force, Marines, and our allies. It enables full-spectrum operations, to include target acquisition/attack missions; intelligence, surveillance, and reconnaissance (ISR); security; manned/unmanned teaming; communication relay; and command and control (C2). It provides the U.S. warfighting force with stealth technology and the ability to integrate both air and ground combat capabilities.

The OWTF Program Management Office (PMO) oversees the research, development, and fielding of the state-of-the-art command, control, communications, computing, cyber, and intelligence technologies that are linked to the OWTF for joint warfighters to enhance the Department of Defense’s (DoD) capability to successfully engage both ground and air adversaries. The PMO identifies key opportunities for UAS technologies and bridges technological gaps as a key part of developing joint unmanned aircraft with innovative capabilities, rather than continuing to acquire UAS that are primarily information-gathering enablers specific to each service. The OWTF PMO also operates a Technology Center / Laboratory to support technology evaluation, demonstration, simulation of integrated technologies, representative models, or rapid prototyping in a realistic operating environment.

The OWTF PMO is responsible for developing an overall strategy to employ the OWTF to perform tactical, persistent and penetrating Intelligence, Surveillance, and Reconnaissance in support of the services ability to use OWTF jointly in combat operations. The focus of the OWTF PMO is ensuring lifecycle affordability; Reliability, Maintainability, Quality, Supportability and Interoperability (RMQSI); Security; and Standardization and reducing the development cost, production cost, and cost of ownership of the OWTF family of aircraft while increasing the level of integration, standardization, and rapid fielding of warfighting capabilities.

Currently, the OWTF PMO is developing and implementing an Open Architecture for the development of its Ground Control Station (GCS), to rapidly incorporate new or modified off-the-shelf capabilities as they become available. In addition, the PMO is seeking solutions to improve its developmental and operational testing procedures to identify and defend against potential cyber-attack.

OBJECTIVE AND SCOPE

2.1 Objective

The primary purpose of this TO is to study, analyze, provide advice, research, and develop deliverables to advance IAC MAC related scientific and technical information (STI) through the application of knowledge and resources in achieving the requiring activity's mission requirements defined herein.

The objective of this TO is to provide basic and applied research services to enhance the current and future operation and evolution of the OWTF. The PMO requires contractor assistance in development of the capabilities which will be critical to the integration of unmanned aircraft operations and development of a next-generation, multi-mission UAS force.

The OWTF PMO requires contractor support with conducting trade studies, analyses, and planning activities for new capability integration in the OWTF’s next planned block which includes implementation of open architecture for the Ground Control Station (GCS). The Contractor shall perform architectural analysis, analysis of alternatives, rapid prototyping of components and / or subsystems, RMQSI assessments, survivability test planning of OWTF with its enhanced features, advanced sensors, data fusion, and improved force picture, to enable the OWTF PMO to achieve desired capabilities and integrate them into the system’s future capabilities. The Contractor shall prototype software to identify if the OWTF system is vulnerable to cyber-attack (e.g., external threats, internal threats).

In addition, the Contractor shall make recommendations on use of OA to increase collaboration between the Government and private industry to bring unique solutions to support the growth and sustainment of the OWTF.

The Joint Capabilities Integration and Development System (JCIDS) and Defense Acquisition System (DAS) will provide the framework and basis for defining, managing, and acquiring the envisioned OWTF enhancements.

2.2 Scope

2.2.1 IAC MAC Basic PWS references. The work under this TO is within the scope of the IAC MAC Basic Performance Work Statement for Weapons Systems (1.4.2.2.9), RMQSI (1.4.2.2.2), and Software and Data Analysis (1.4.2.3.1) Technical Focus Area(s). The work under this TO relates to next generation Unmanned Aircraft Systems weapon systems.

TASKS

The Contracting Officer (CO) is the only person authorized to direct the contractor or take any actions that would change the TO or commit the Government in any way.

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

Each subtask that requires the analysis and recommendations for the Government shall include the development and delivery of Analysis and Recommendation reports (Deliverable 4.14: OWTF Analysis and Recommendations Reports).

3.1 (Task 1) – Program Management

3.1.1 Post Award Orientation. The Post-Award Orientation shall be held within seven (7) calendar days of the start of performance. Schedule and conduct this meeting, in coordination with the ACOR, Contracting Office 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 (Deliverable 1A: Post Award Brief Slides and Minutes with Attendees List).

3.1.2 Program Management Plan. Provide a Program Management Plan (PMP) within fifteen (15) days after contract award. 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. If/when a project tasking is submitted to the contractor, the PMP will be updated within 15 days of each new project tasking. The update shall specify estimated project start and stop dates as well as a risk mitigation plan and an expenditure plan aligned to key milestones within the project, to include any anticipated Other Direct Costs (ODCs). The update should highlight any interdependencies within the tasks and/or 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 1B: Program Management Plan (PMP)) and shall report monthly status updates (Deliverable 1C: Monthly Status Report (MSR)).

3.1.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, 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. Specific MSR format, and additional content not specified in this section, shall be mutually agreed upon by the contractor and ACOR; this should be established no later than the Post-Award Orientation. If the MSR shows that the project is not meeting the performance thresholds set forth in the Service Summary found in Section 8.0, the contractor shall provide the rationale and circumstances preventing the threshold from being met, and provide an update to the PMP, to the satisfaction, acceptance and approval of the ACOR (Deliverable 1C: Monthly Status Report).

3.1.4 Final Technical Report. Prior to expiration of the order, submit a Final Technical Report (FTR) as detailed in section 4.0. The FTR shall include TAT-specific background information, objectives, assumptions, specific data collected, conclusions, analyses conducted, and recommendations. Each report shall be delivered to the ACOR and COR (Deliverable 1D: Final Technical Report (FTR)).

Task 1 Deliverables Table

Slides and Minutes with Attendees List

Award Orientation

(PAO)

(CDRL A008) Slides, as a minimum, should identify the key stakeholders and highlight their roles and responsibilities, summarize the tasks and associated deliverables (with specific focus of building on the BCO knowledge base and producing STI for future reuse), and monthly status reporting (cost, schedule, performance). Minutes (with a list of attendees) should capture the substance of the meeting. Provide draft of slides three days prior to PAO. Slides and Minutes should be provided to all attendees, including ACOR, COR and CO.

Management Plan

(PMP)

updated within 15 days of each new project tasking (CDRL A009) PMP shall include a schedule that outlines the steps to take and a timeline to completion of the program and all projects as well as any interdependencies amongst the projects’ schedules. The schedule shall specify estimated project start and stop dates as well as a risk mitigation plan and expenditure plan aligned to key milestones within the project, to include any anticipated Other Direct Costs (ODCs).

Report (MSR)

Receipt of Order (ARO), Monthly, thereafter. Final MSR due with

FTR.

(CDRL A010) Includes actual versus planned task expenditures, technical progress made, schedule status, travel conducted, meetings attended, issues, and recommendations. The MSR reports cost, schedule, risks, and performance against PMP and PWS requirements. Identifies funding compared to ceiling, planned versus actual expenditures, status of known risks, risk mitigation efforts, deliverables funded and date they were funded, technical progress made and schedule status per deliverable, deliverable titles and numbers completed within the previous month, and the deliverables scheduled to be delivered during the upcoming month. Reports all Military Interdepartmental Purchase Request (MIPRs) received and details the funding source of each MIPR Specific MSR format and content shall be mutually agreed upon by the contractor and ACOR, per the guidance contained herein. Establishes a baseline schedule for and steps to completion for each requirement. Upon acceptance and approval by the Government, the Contractor shall meet the schedule and forecasted delivery date of all deliverables by taking all reasonable measures to fulfil the requirement.

The MSR content should be established no later than the postaward conference. The MSR shall be in PDF format, e-mailed to the ACOR, COR, and CO.

Report (FTR)

3.2 (Task 2) - Reliability, Maintainability, Quality, Supportability, and Interoperability (RMQSI) Assessments Due to the growth of operational use of the OWTF as well as increased UAV use, the existing hardware that composes the OWTF’s Ground Control System has been identified as a critical component in need of modifications and improvements. As flight hours increase, RMQSI issues become more apparent. The Contractor shall provide expertise in following areas:

· Interrelations between forms/functions/ shapes/ behaviors/structures/ dynamics, principles and constraints that govern the interactions between multiple functions;

· Multi-functional component integration issues and system adaptation capabilities that allow systems to select and switch functions based on tasks and environments; and

· Reliability and life-lengthening methodologies for analyzing mechanical and electrical systems, especially those with extremely high failure rates

The Contractor shall provide research, development, engineering, analysis and testing to identify approaches for reliability and maintainability improvements including UAV associated support and production systems as well as vulnerability studies leading to increased equipment reliability and a reduction in support costs. The contractor shall:

3.2.1 Collect, compile, and analyze existing deployed OWTF maintenance records, retrieved hardware, and mishap reports such as Combat Data Incident Reports (CDIRs) related to the retractable landing gear assembly. The Contractor shall provide a list of identified failure points and components (Deliverable 2A: OWTF Retractable Gear Failure Points).

3.2.2 Provide an engineering assessment using current industry forensic engineering practices to determine the root cause of the identified faults. The Contractor shall utilize procedures such as fractographic analysis, finite element analysis, raised stress analysis and other analytic methods as needed to determine the structural integrity of materials exhibiting fatigue. The Contractor shall assess the components and provide recommendations on improvements to the existing design or more sustainable replacement materials, and perform research and analysis of existing Commercial off the Shelf (COTS) systems and components for replacement feasibility (Deliverable 2B: OWTF Retractable Gear Upgrade and Replacement Recommendations).

3.2.3 Assess existing OWTF maintenance procedures associated with the retractable landing gear and recommended upgrades, and provide recommendations on inspection procedures as well as maintenance procedures such as cleaning and lubrication of mechanical and hydraulic components (Deliverable 2C: OWTF Retractable Gear Maintenance and Inspection Recommendations).

Task 2 Deliverables Table

3.3 (Task 3) - Weapons Systems Research and Analysis The Contractor shall provide Research and Analysis of the OWTF including but not limited to: trade studies, analyses, and planning activities for new capability integration in the OWTF’s next planned block. The priority is incorporating the principles of modular design and design disclosure, reusable application software, interoperability and secure information exchange, and lifecycle affordability of OWTF. In order to offer continual enhancements to the operation of the OWTF in an environment where there is an ongoing evolution of threats, provide expertise in the following systems including anti-satellite systems; guidance systems; combat systems found in tanks, aircraft, ships, submarines, and missiles; countermeasures against laser-guided or laser-aided threats; and revolutionary lethal, less lethal and non-lethal munitions-related research for new airframe/ordnance and guidance/control technology weapon paradigms. The Contractor Shall:

3.3.1 Analyze operational, system, and technical views of the OWTF architecture to identify and assess the interactions between manned and unmanned systems (Deliverable 3A: Architectural Analysis of OWTF).

3.3.2 Assess and provide recommendations to the government on the technical viability and use of new technologies, alternate commercial hardware and software applications, development environments, differing software and network architectures, and performance enhancements.

3.3.3 Conduct Analysis of Alternatives (AoA), trade studies, and evaluation of system and/or component hardware, software, and communication links for the OWTF, and analyze systems for compliance with requirements and operational effectiveness. The Contractor shall conduct engineering analysis with a focus on critical technology elements associated with each proposed AoA solution for the OWTF, including technology maturity, integration risk, manufacturing feasibility, and, where necessary, technology maturation and demonstration needs. The Contractor shall evaluate the OWTF’s reuse of systems, sub-systems, and components for improved functionality, flexibility and performance used for defeating adversaries (Deliverable 3B: AoA Report).

3.3.4 Design and develop prototypes of components or subsystems to meet emerging or new operational requirements for the OWTF, and provide recommendations for engineering design and modification of systems, subsystems and components to meet critical warfighting requirements that address systems operational serviceability; functionality; flexibility; performance; integration readiness; and ease of operation (Deliverable 3C: Component/Subsystem Prototypes; Deliverable 3D: System/Component Design Report).

3.3.5 Develop and analyze technology solutions and designs for achieving desired capabilities and insert those solutions into future capability options and provide recommendations for documents required by the Joint Capabilities Integration Development System (JCIDS) (Deliverable 3E: Analysis of System Technology Solutions and Designs; Deliverable 3F: JCIDS Documentation).

Task 3 Deliverables Table

3.4 (Task 4) - Software Design and Development The Contractor shall support development of software that will identify potential vulnerabilities to cyber-attack that are indicated by dissonance and irregularities shown in test data. The Contractor shall design and develop prototypes which can be used to locate the system’s vulnerabilities to cyber-attack (e.g., external threats, internal threats) as well as to improve its developmental and operational testing procedures. The Contractor Shall:

3.4.1 Research and analyze OWTF current assets including approved algorithms, identifications of data elements, and data sources (interfaces). The Contractor shall develop design and technical specifications within the OWTF framework (Deliverable 4C: Software Requirements; Deliverable 4D: Software Requirements Specifications; Deliverable 4E: Interface Requirements Specifications; Deliverable 4F: Interface Management Documents).

3.4.2 Develop software code using Commercial off the Shelf (COTS) technologies and Open Source Standards (OSS) that will allow the integration of existing Information Technology (IT) systems capable of meeting identified requirements. The Contractor shall develop software code using the detailed design documented in Deliverables 4C-4F. The Contractor shall conduct all required engineering, integration, testing, operations, maintenance, documentation, and logistical support of the system to identify potential vulnerabilities within the asset. (Deliverable 4B: Source Code).

3.4.3 Perform system level verification and validation (V&V) to determine if requirements are met and determine whether operational environment performance requirements are achieved (Deliverable 4G: V&V Documentation).

Task 4 Deliverables Table

3.5 (Task 5) – Open Architecture (OA) Support The Contractor shall support the adoption of an open GCS architecture that will allow rapid addition of modular functionality to OWTF GCS, allowing warfighting flexibility. The Contractor shall support the collection, creation, and utilization of reusable information while fostering the business and technical exchanges across DoD S&T and R&D community to support the evolving Joint, net-centric warfare environment (Deliverable 5A: OWTF Analysis and Recommendations Reports). The Contractor Shall:

3.5.1 Develop recommendations, lessons learned, tools, as well as AoA of OWTF GCS to determine OA reuse practices within and across the DoD Communities of Interest or other available resources, to help facilitate cooperative relationship and collaboration in cross-domain / service relationships.

3.5.2 Identify and develop best practices and recommendations to support the development and utilization of common software components, functions, and reuse methodologies relevant to implementing Open Architecture for OWTF GCS.

ADMINISTRATIVE REQUIREMENTS

4.1 Security

The work on this TAT is anticipated to have a classification level up to TOP SECRET. The proposed Contractor shall ensure all personnel (including administrative and subcontractor personnel) specified as requiring access to classified facilities, systems, and information with TOP SECRET classification, have a TOP SECRET security clearance.

Offeror shall consider for this fictional task that contractor personnel to perform tasks described in Section 3.0 of this PWS need to possess current DoD Top Secret clearances.

4.2 Software

The Contractor shall possess and utilize approved software that are compatible with the ones used by the Government, which consists of latest versions of Microsoft Office Professional (Word, PowerPoint, Excel and Access), Microsoft Project Standard, and Adobe Acrobat Reader. An appropriate industry standard software of the Contractor’s choice, shall be used to develop/produce all required system / software architecture views. A software license for required software shall be provided by the government for the period of the study.

4.3 Travel, Materials & Supplies

The Contractor travel shall be authorized in writing by the COR, to support customer requirements including but not limited to interviews, User Conference, Government Program Reviews, Government team meeting, or other technical meetings or conferences as required. The Contractor reimbursement for travel expenses shall be billed without fee and at the rates provided in the Joint Travel Regulations (JTR). The Contractor travel shall not exceed $64,000 per year ($320,000 over the entire PoP).

All potential Offerors shall use the minimum Government estimate for Other Direct Costs (ODCs) provided in the table below. The Government ODC estimates are inclusive of any subcontractor travel costs, material, and supplies but do not include any material handling fee or General and Administrative (G&A) costs. Contractors may propose additional ODCs but they must be clearly identified, fully justified, and will be evaluated as part of the overall price of the proposal.

Government ODC Estimate

4.4 Period of Performance

Period of Performance will be 60 months. The period of performance will be 1 January 2018 to 31 December 2022.

4.5 Place of Performance

The place of performance will be the contractor’s facility (80%) and the OWTD PMO office in Arlington, VA (20%).

1. GOVERNMENT FURNISHED INFORMATION (GFI) AND EQUIPMENT (GFE)

The government will make available the GFI reference material and GFE required to perform tasks described in the SOW.

SERVICE SUMMARY

Service Summary Table

TO

PERFORMANCE OBJECTIVE

TO

PWS REFERENCE

TO

PERFORMANCE STANDARD/THRESHOLD

Threshold: Completed on time and updated to reflect changes as they occur 100% of the time. A corrected PMP will be submitted within 5 business days of identification of an error.

Threshold: 100% compliance with PWS and CDRL requirements. The Government shall receive no more than three Corrective Action Reports (CARs) or similar deficiency reports during the contractor’s performance of the entire task order. Provide a get well plan within 5 business days of identification of deficiency.

Threshold: 100% compliance with CDRL requirements. The contractor shall submit all Deliverables/CDRLs as instructed per the established schedule (due date) with no need for substantive changes. Provide a revised deliverable within 5 business days of identification of deficiency.

Threshold: The Government shall perform random service sampling (reviews) to gauge the contractor’s customer service responsiveness and professionalism. The Government shall receive no more than three complaints or negative reviews denoting a customer service/business acumen deficiency during the contractor’s performance of the entire task order. Provide a get well plan within 5 business days of identification of deficiency.