J-5_SAMPLE_TO_3_Pool_2_3Oct17.docx

IAC MAC

Pool 2

Sample Task Order #3

Performance Work Statement (PWS)

Virtual Battlefield Display System (VBDS)

[Focus Areas: Weapon Systems; Survivability & Vulnerability; and Software Data and Analysis]

September 9, 2017

TABLE OF CONTENTS

SAMPLE TO 3 (Pool 2) 11

GENERAL

This document describes the performance 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 Small Business Set-Aside (Pool 2). The Section Three (3) and Four (4) of the PWS, includes a set of requirements including specific tasks and deliverables for this Sample Task Order #3.

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 #3 only.

BACKGROUND

The Close Air Support Program Office (CASPO) was formed to develop decisive tactical advantage and capability to rapidly deploy precision-guided ordnance against elusive mobile targets through air-ground fire coordination, Close Air Support (CAS), and increase CAS effectiveness by enabling real-time battlefield awareness and data sharing. In order to accomplish this mission, the CASPO conducts research, design, and development of new and evolution of existing technologies designed to enhance the efficiency of Close Air Support (CAS) to warfighters on the battlefield. In addition, CASPO assesses capability of test range equipment and surrogate weapon systems used to evaluate the survivability and effectiveness of aircraft performing CAS missions. CASPO currently seeks to develop system capability to enhance rapid, simultaneous target identification while minimizing collateral damage through integration of Virtual Battlefield Display System (VBDS) into fixed-wing CAS aircrafts, a three dimensional (3D) topographical system designed to visualize and display physical battlefield and the disposition of friendly and enemy forces in a high-fidelity, virtual environment.

VBDS is a fictional system, consisting of various Commercial-Off-The-Shelf (COTS) software and hardware components. VBDS continuously updates battlespace situational awareness and provides a comprehensive communications network for the commanders involved in combat to synergistically direct the fight as well as a means for the war fighters to execute and report. VBDS’s manned platform receives the tasking, acknowledges the assignment, adds the targets to a customized display of the battlespace, and recommends a course of action to the operator. The goal of VBDS integration is to enable three-dimensional visualization of the battlespace that can be customized to display to present only relevant information and forces, which can assists ground commander to designates targets for destruction, containment, or immobilization, and the timing of the CAS mission.

OBJECTIVE AND SCOPE

The primary purpose of this TO is to study, analyze, provide advice, research, and develop deliverables to advance IACMAC 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 enable the incorporation of a Virtual Battlefield Display System (VBDS) into existing fixed wing CAS aircraft, and the requirements of the VBDS include incorporating real time battlefield movement and satellite renderings of ground cover/features. To meet this objective, the Contractor shall support CASPO’s technology insertion efforts including engineering analysis; hardware and software design, integration and testing; and survivability assessment. To ensure planned testing is adequate, accurate, and representative of the system being tested, the Contractor shall provide support to assess the capability of test range equipment and surrogate weapon systems used to evaluate the survivability and effectiveness of VBDS. The Contractor may be required to apply information from this study to develop and assess new and applied technology to support the CAS mission.

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), Survivability and Vulnerability (1.4.2.1) and Software and Data Analysis (1.4.2.3.1) Technical Focus Area(s). The work under this TO relates to the Virtual Battlefield Display System (VBDS)

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

(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

Due Date / Frequency Description

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)

if sensitive internal information is contained in the FTR, every attempt shall be made to produce a sanitized (redacted) version of the FTR for distribution within DoD (Distribution D) and inclusion in the DTIC database. For classified reports to be included in DTIC classified databases, an unclassified SF298 will be produced and signed by the Government ACOR; this document shall serve as the basis for creating unclassified metadata, which the BCO will add to the DTIC unclassified database, in accordance with established policy and procedures.

3.2 (Task 2) – VBDS Engineering Analysis The Contractor shall perform engineering analyses, to evaluate mission assurance best practices for VBDS Integration into fixed wing CAS Aircrafts. The Contractor shall coordinate requirements analyses with CASPO stakeholders, and conduct technical and policy analysis across a broad spectrum of community issues, including emerging technologies, current technical specifications and functions, system architecture issues and recommended implementation, and policies related to system survivability, interoperability, and cybersecurity. The Contractor shall:

3.2.1 Conduct Feasibility Analysis

3.2.1.1 The Contractor shall conduct Feasibility Analysis (FA) of the VBDS integration requirements, performance standards, potential technologies, and concepts of employment. FAs shall include analysis of viable technical alternatives based on existing, emerging, and future technologies, logistics support analysis, and cost benefit analysis to identify optimum solutions to existing and future requirement gaps and shortfalls (Deliverable 2A: VBDS Feasibility Study).

3.2.1.4 The contractor shall analyze information direction flow, source and target networks, and data types used in VBDS. The Contractor shall provide subject matter expertise in the theory and application of “Big Data” and “Large Data” and information system solution support tools, as well as expertise in enabling architectures, in operational environments, to support design of enterprise point to point, interoperable data architecture and solutions. The Contractor shall conduct and provide documentation of technical analysis and recommendations (Deliverable 2D: System Engineering and Test Analysis).

Task 2 Deliverables

3.3 (Task 3) – VBDS Integration Support The Contractor shall develop technical recommendations and software products that allow for encryption, ensure cybersecurity, and are able to pull down satellite feeds of friendly forces and/or foes as well as environmental data. The Contractor shall:

3.1

(Deliverable 3A: Source Code; Deliverable 3B: Software Requirements; Deliverable 3C: Software Requirements Specifications; Deliverable 3D: Interface Requirements Specifications; Deliverable 3E: Interface Management Documents; Deliverable 3F: V&V Documentation).

Task 3 Deliverables

Task 4 Deliverables

Due Date / Frequency Description

ADMINISTRATIVE REQUIREMENTS

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.

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.

Travel 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 $30,000 per year ($150,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

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 VBDS PMO office at Fort Belvoir, VA (20%).

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

SERVICE SUMMARY

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.