J-4_SAMPLE_TO_2_Pool_1_3Oct17.docx

IAC MAC

Pool 1

Sample Task Order #2

Performance Work Statement (PWS)

M100 Audie Murphy Tank

[Focus Areas: Military Sensing; Survivability & Vulnerability; and Cybersecurity]

TABLE OF CONTENTS

1.0 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 Full and Open (Pool 1). 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 #2.

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

1.1 BACKGROUND

The M100 Audie Murphy Tank is a fully integrated weapons platform with sophisticated information, targeting, navigation, and communications systems. These systems are potentially vulnerable to cyber-attacks and/or intrusion that could degrade or destroy platform performance. These systems’ cyber vulnerabilities must be identified and the systems made resilient to cyber-attacks. The M100 Audie Murphy Tank Program Management Office (PMO) provides state-of-the-art weapons, command, control, communications, computing, cyber, and intelligence technologies for joint warfighters to enhance DoD’s capability to successfully combat air, ground, and cyber adversaries as they relate to this platform.

The PMO is also responsible for conducting Life Cycle Management for the M100 Portfolio and for supporting the warfighter throughout the Force Generation Cycle by developing, producing, fielding, sustaining, resetting, and integrating new technologies using a system of systems approach. Further, the PMO seeks to enable rapid development of adversary anti-tank munitions demands on-going research and analysis of potential vulnerabilities in the M100’s construction and design.

The M100 PMO is currently evaluating sensor suite upgrade / replacement to address a sensor performance issue with its target identification capability of potential ground and air threats and targets. In addition, the M100’s current sensor system logs are not currently indicating cyber-attack, but the sensor test data displays irregularities which may indicate performance degradation or potential compromise.

2.0 OBJECTIVE AND SCOPE

2.1 Objective

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 enhance the M100 Audie Murphy Tank’s warfighting capabilities through the conduct of multifunction onboard sensor assessment; survivability, vulnerability, and lethality test and evaluation; and cybersecurity requirement assessments for both onboard and off-board M100 systems. These systems are designed and upgraded when necessary to ensure a continued technological edge against current and future threat forces. As a result, M100 PMO requires analysis, design, and testing support to develop the sensor capabilities, sensor suites, integration and employment concepts, and detailed technical characteristics to meet those requirements.

In fulfillment of this objective, the Contractor shall:

· conduct research, design, and analyses of existing and available military sensing technologies and commercial electronics/optoelectronics (including devices, components, subsystems);

· provide research on developmental semiconductor devices with emphasis on emerging electronic, plasmonic, and photonic technology;

· conduct live fire testing and evaluation (LFT&E) to identify and assess design deficiencies so that appropriate corrective actions can be taken; and

· conduct survivability and vulnerability assessment to develop recommendations to enhance M100 performance

2.2 Scope

2.2.1 IACMAC Basic PWS references. The work under this TO is within the scope of the IACMAC Basic Performance Work Statement for Military Sensing (1.4.2.2.3), Survivability and Vulnerability (1.4.2.2.1), and Cyber Security (1.4.2.3.2) Technical Focus Area(s). The work under this TO relates to the M100 Audie Murphy Tank.

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

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

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) - Technology Assessment, Research, Development, and Multifunction Onboard Sensor Assessment

The existing sensors that are on the platform require upgrades to assist the operators in targeting ability and in avoiding collisions in these harsh environments, to further enhance its capability to withstand extreme conditions (e.g., low visibility, cyber-attack, etc.) without degradation in its ability to assist the operators in targeting, identifying, terrain differentiation, etc., where visibility is very low and in a contested cyber environment. The Contractor shall perform independent technology assessments of M100 sensors onboard in the form of engineering technical analyses and other technical evaluations to fully understand the capabilities and potential applications of these new technologies. This may include the performance of in-depth analyses of a sensor performance, attainability, manufacturability, and operational impacts related to the integration of new technologies into future sensing capability. The contractor shall:

3.2.1 Conduct Sensor Performance Analysis. The Contractor shall analyze the performance, survivability, vulnerability, and reliability of M100 onboard sensors in production or sustainment in order to assess the performance of those sensors in a known and potential operational environment. The Contractor shall perform research and analysis of current onboard sensor suite and support systems to determine how each component operates during extreme conditions, using modeling, laboratory testing, or field testing. This includes technical analyses of sensor designs and specifications (e.g. weight, dimension/size, power drain) to determine anticipated performance, technical risk, cost realism, and expected operational impacts. Based on the results of these analyses, document recommendations on system design, technology investment roadmaps, and development strategies to meet operational requirements, such as development of light-weight sensor suite with reduction in power consumption (Deliverable 2A: Sensor Performance Report).

3.2.2 Research and analyze available COTS and Government off the Shelf (GOTS) onboard sensors. Where appropriate, perform market research, trade studies, and analyses of alternatives to identify possible technical solutions for these requirements, define a methodology for evaluating each candidate solution, and evaluate the ability of each solution to meet the requirement. These analyses shall use computational methods, modeling and simulation tools, and operational data to translate these requirements into technical specifications for onboard sensor systems that can be used for development of new sensors or upgrades of existing ones. (Deliverable 2B: Sensing Technology and Threat Capability Report).

3.2.3 Research and analyze current COTS and GOTS sensor support systems (e.g., power systems, maintenance systems) and their vulnerabilities with respect to mission assurance and overall platform survivability. Assess the advantages gain, if any, with any of the COTS or GOTS systems. The Contractor shall evaluate both existing and emerging threat capabilities that impact military sensor technologies in order to assess their technical capabilities, potential impact on U.S. forces, likelihood of fielding and proliferation, and the timeline/probability associated with encountering them on the battlefield. The Contractor shall utilize the full spectrum of available information sources as appropriate in order to provide the most complete information. Where necessary, the Contractor shall collect data using laboratory and/or field testing to characterize threat system performance as well as full spectrum signatures of potential threat targets or backgrounds. The information collected under these efforts shall be analyzed using appropriate techniques, including modeling and simulation tools where available, to establish potential threat capabilities, their operational and technical impacts, and potential U.S. responses to counter those threats. (Deliverable 2B: Sensing Technology and Threat Capability Report; Deliverable 2F: Test Report).

3.2.4 Considering the results from task 3.1.1, 3.1.2, and 3.1.3, to develop and deliver M100 sensor system technical requirements with appropriate specifications. The Contractor shall design, implement, analyze, and document transition work efforts that include The Contractor shall analyze M100 onboard sensor-related requirements from results of analysis and data collected from Task 3.1.1-3.1.3, to support design, development, modeling, prototyping, integration, qualification, test, deployment, and installment required to implement a multifunction onboard sensor and ground support equipment to enhance threat detection and the survivability of the operators/crew/platform, and to develop a “plug and play” system that could easily be replaced on current tanks and upgradable in the future. These analyses shall use computational methods, modeling and simulation tools, and operational data to translate these requirements into technical specifications for sensor systems that can be used for development of new sensors or upgrades of existing ones.

The Contractor shall develop a sensing system prototype to provide M100 operators withhigh resolution visibility of their environment using terrain databases, sensor data, and radar data, which, when integrated, will give the operators a virtual 2D/3D view of their surroundings even when they are experiencing degraded visibility or in a cyber contested environment (Deliverable 2C: Design and Implementation Report; Deliverable 2D: Computer Software and Technical Data; Deliverable 2E: Sensor Prototype; Deliverable 2F: Test Report).

Task 2 – Deliverables Table

3.3 (Task 3) – Survivability, Vulnerability, and Lethality Test and Evaluation of the M100 Audie Murphy Tank

Following system modifications, the Contractor shall perform test and evaluation of M100 Audie Murphy Tank and its sensor suite using technical expertise in following:

· Systems survivability;

· Low observable technology requirements for system survivability;

· Laser effects;

· Advanced materials for enhanced survivability;

· High power microwave (hpm) susceptibility and vulnerability;

· Battle damage repair;

· Advanced weapon survivability/vulnerability;

· Cyber weapon systems analyses, prototyping, and material and non-material solutions development

· Tank survivability equipment;

· Munitions/ammunition vulnerability/lethality;

· Live fire testing analysis;

· Ballistic test facility;

· Modeling and simulation tools that are vital to survivability/vulnerability and lethality analysis;

· Integrated survivability with respect to air, ground, and cyber threats;

· Crew casualty methodology improvement;

· Support of combat operations;

· Damage repair methodologies;

· Logistics implications of survivability The Contractor shall conduct Live Fire Testing and Evaluation (LFT&E) of the M100 Audie Murphy Tank to identify and assess armor design deficiencies so that appropriate corrective actions can be taken, and examine the vulnerability and lethality to the full spectrum of validated combat threats and targets. The contractor shall:

3.3.1 Conduct Modeling and Simulation (M&S) with pre-existing models and use other analytic efforts as needed to identify the best strategy for LFT&E to enable an assessment of armor vulnerability and lethality. This may include the use of pre-shot predictions. Develop a recommendation for the Live Fire Test (LFT) that balances cost effectiveness with the ability to represent a realistic environment. The Contractor shall develop, utilize, and validate M&S tools as needed to predict threat capabilities and the performance of M100 sensors in order to inform the design, testing, and sustainment of new and existing sensor systems. The design of these models and the results of validation efforts shall be documented for distribution to users of the simulations (Deliverable 3A: Test and Evaluation Master Plan; Deliverable 3B: Detailed Test and Evaluation Plan).

3.3.2 Evaluate LFT results to address M100 sensor vulnerability and lethality against known and potential threats. The Contractor shall examine basic damage and kill mechanisms and their interactions with the target system, and develop recommendations to decrease the susceptibility and vulnerability of the M100 (Deliverable 3C: Detailed Test and Evaluation Report).

Task 3 Deliverables Table

3.4 (Task 4) Cybersecurity Requirement Assessments

The Contractor shall support the development and delivery of reports that capture the analysis conducted and recommendations for the Government (Deliverable 4A: Cybersecurity Analysis and Recommendations Reports). The Contractor shall:

3.4.1 Identify requirements for integration of cybersecurity architecture and technical patches in maintaining and development of sensor suite, and provide technical analysis and recommendations for future architecture requirements. The Contractor shall provide recommendations to the Government for updating and revising architecture designs to accommodate changing requirements, emerging technology, and results of M100 vulnerability assessments (Deliverable 4B: Architecture Analysis Results and Alternatives).

3.4.2 Develop test plans and perform system security level baseline measurement of current performance of the M100 sensor suite and its risk mitigation systems against the prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communication services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and non-repudiation of M100 systems. (Deliverable 4C: Test Plan Reports; Deliverable 4D: Risk Mitigation Baseline Analysis).

3.4.3 Conduct assessments of the current M100 sensor suite’s monitoring capabilities, during and after simulated electronic systems/cyber-attacks. The Contractor shall define cyber requirements and develop recommendations regarding risk mitigation solutions and contingency plans. The Contractor shall provide recommendations for system improvements, integration and implementation of software, hardware and services capabilities including, for example, onboard and offboard sensor networks, messaging, traffic, and cross-domain solutions. (Deliverable 4E: Threat and Post threat Assessment Plan; Deliverable 4F: Risk Assessment Recommendations; Deliverable 4G: Project Documentation).

Task 4 Deliverables

5.0 ADMINISTRATIVE REQUIREMENTS

1.

2.

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

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

5.3 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 $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

5.4 Period of Performance

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

5.5 Place of Performance

The place of performance will be the contractor’s facility (80%) and the Audie Murphy PMO office in Aberdeen, MD (20%).

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

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