Attachment_19_-_Statement_of_Objectives.pdf

ARTS-V2 SOO 02-10-16

1 | P a g e Author: AFLCMC/HBZCD

STATEMENT OF OBJECTIVES

FOR

ADVANCED RADAR THREAT SYSTEM–VARIANT 2

1. OVERALL OBJECTIVE

1.1 The program objective is: Develop, produce, and field an economically sustainable Advanced Radar Threat System-Variant 2 (ARTS-V2) representative of a medium range, “double digit” Surface-to-Air Missile (SAM) to satisfy current and 5th Generation combat aircrew training gaps, to meet Initial Operational Capability (IOC), No Later Than (NLT) FY21, and Full Operational Capability (FOC), NLT

FY24.

NOTE A: The Capability Development Document (CDD) defines IOC as:

• Site Acceptance Test (SAT) complete for two (2) systems, one at Nevada

Test and Training Range (NTTR) and one at Utah Test and Training Range (UTTR).

• Validation and verification of systems for all Key Performance Parameters (KPPs) and Key System Attributes (KSAs).

• Spares and unique support equipment in place for fielded systems

• Trained field operators at NTTR and UTTR.

• Technical Orders (T.O.s) completed and approved in accordance with

(IAW) T.O. 00-5-1 (1 October 2014).

• Supply Support Plan (Integrated Logistics Support Plan-(ILSP)).

NOTE B: The CDD defines FOC as:

• 15 fully operational fielded systems.

• Spares and Peculiar Support Equipment (PSE) for fleet wide sustainment.

• Operators trained and educated at each fielding location related to ARTS-

V2 system operation.

2. CONTRACT OBJECTIVE

2.1 Develop, test, and deliver one (1) Production Representative Article (PRA). The PRA is defined as a fully operational fielded system in its final configuration conforming to all specifications and drawings.

2.1.1 Deliver PRA pre-provisioning spares.

2.1.2 Provide all unique tooling required in the manufacturing of the ARTS-V2 system.

2.1.3 After completion of all system level testing during the Developmental Test and Evaluation (DT&E), contractor will begin Factory Acceptance Testing (FAT) and Site Acceptance Testing including the associated Functional/Physical Configuration Audits (FCA/PCA).

2.2 Options to produce, test, and deliver twenty (20) Production Articles (PA).

ATTACHMENT 19

2 | P a g e

NOTE C: The Government’s plan is to acquire fourteen (14) PAs within the production options.

NOTE D: Testing in production is limited to parts, subsystem(s) or full system affected by changes to configuration from the PRA baseline.

NOTE E: It is expected that no significant ECPs will be required to change the "Developmental" drawing package and associated baseline into a "Production" drawing package and the new production baseline. Test Procedures will need to be updated to change references from "developmental Technical Orders" to "production Technical Order" references.

2.2.1 Options to produce, test and deliver five (5) each ARTS V2 Surrogate Shells, in addition to those delivered with the systems, not to include Shell Prime mover unless integrated into the shell.

2.3 Options for up to five (5) years of Interim Contractor Support (ICS).

2.4 Option to inspect, repair (as necessary), retrofit to the same configuration as the final production unit, test and install the PRA.

2.5 Option to develop, deliver, and install an Engineering Software Support Station (ESSS) to include all hardware and hardware spares, programs, tools, and libraries necessary to modify and maintain the software. In addition, include interfaces and simulations as necessary to verify or utilize all software functions.

2.6 Offeror shall use this SOO along with the Request for Proposal (RFP) as a basis for preparing a proposed Contractor Statement of Work (CSOW) and a complete set of Contract Data Requirements List (CDRLs) describing how they will meet the objectives of this document.

2.6.1 At a minimum, offeror shall include all CDRLs listed within Section J, Attachment 20, Exhibits of the solicitation.

2.6.2 Offeror shall complete Blk 5 in the DD 1423 Form per the CDRL Instructions.

2.6.3 Offeror may propose changes to CDRLs listed in Section J Exhibits of their proposals.

2.6.4 Offeror may propose changes to content of CDRLs in Section J Exhibits of their proposals.

2.6.5 Offeror may propose and include additional CDRLs using form DD 1423, in Section J Exhibits of their proposals.

3. PROGRAM OBJECTIVES

3.1 Deliver ARTS-V2 systems that will meet the System Performance Specification.

NOTE F: A classified, surrogate shell ModelMan faceted model will be provided as Government Furnished Information (GFI). Both full faceted and reduced faceted models will be provided.

3 | P a g e

NOTE G: The successful offeror may submit their unclassified, manufacturing Computer Aided Design (CAD) model of the surrogate shell for a government funded signature assessment by the Missile & Space Intelligence Center (MSIC) using the Dominant Spatial Scatterer Distribution (DSSD) tool. This assessment will be provided for contractor design purposes only; actual shell acceptance will be graded on RF measurements and signature assessment of the physical shell. The assessment is estimated to require approximately 90 days to complete.

NOTE H: The government will provide unclassified, mathematical derivations of the Radar Cross Section (RCS) Metric and DSSD Calculations to be used in validating the measured signatures of the physical surrogate shell as GFI. These are included in Section J of the solicitation.

NOTE I: A compilation of classified renderings generated using XPatch.si files of the reduced faceted ModelMan model will be provided via video files at multiple viewing angles as GFI. The videos provide a full resolution Synthetic Aperture Radar (SAR) image, as well as the RCS as a function of azimuth angle.

NOTE J: The successful offeror may request a copy of the classified full XPatch .si files derived from the full faceted ModelMan file. The government is also willing to sponsor XPatch software program access for the successful offeror if desired, however training/instruction would not be provided.

NOTE K: The missile fly-out model will be provided as GFI included in the classified MATLAB and Simulink Models

NOTE L: The Threat System to Range Interface Control Document is included in Section J, Attachment 17 Interface Control Document as GFI.

3.1.1 Follow a system engineering approach.

3.1.2 Design the system to be supportable for a planned system life of 25 years.

3.1.3 Design the antenna array to emphasize field repairability to the maximum extent possible.

3.1.4 Design the system utilizing open architecture to support future threat updates and upgrades.

NOTE M: Government DT&E facility costs for one round of DT&E will be directly funded by the government for system level testing. In the case of RCS testing the government will directly fund 2 rounds of system level testing.

NOTE N: Commercial DT&E facility costs will not be directly funded by the government for system level testing.

NOTE O: Planned locations for production fielding:

• Nevada Test and Training Range, NV

• Utah Test and Training Range, UT

• Poinsett Electronic Training Range, SC

4 | P a g e

• Barry M. Goldwater Range, AZ

• Yukon/Oklahoma Training Areas (within the Joint Pacific Alaska Range

Complex) AK

• Savannah Combat Readiness Training Center, GA

• Smoky Hill Air National Guard Range, KS

Volk Field Combat Readiness Training Center, WI

3.2 Provide programmatic support to the government to include assessments, reports, government access to testing activities, and assistance with government programmatic activities.

3.2.1 Assist the government in performing a Manufacturing Readiness Assessment (MRA).

3.2.2 Assist the Air Combat Command (ACC) in developing and updating all Department of Defense Architecture Framework (DoDAF) products associated with the ARTS-V2 Capabilities Production Document (CPD).

3.2.3 Assist the government in acquiring frequency authorization certifications for all open air test locations prior to open air radiation.

3.2.4 Assist the government in planning and conducting meetings and conferences e.g. Critical Design Review (CDR), Program Management Review (PMR), Integrated Product Team Meetings (IPTM), Security System Working Group (SSWG), Test Plan Working Group (TPWG), and Spares Provisioning Conference.

3.2.5 Assist the government during updates to the Programmatic Environmental, Safety, and Health Evaluation (PESHE).

3.2.6 Assist the Government in updating the ARTS-V2 Lifecycle Sustainment Plan (LCSP).

3.2.7 Provide initial familiarization and operations training for up to 25 Government/Government support personnel post PRA Factory Acceptance Test (FAT) at the contractor facility. Training will consist of classroom presentations and practical on equipment instructions.

3.2.8 Provide familiarization, operations and Level I maintenance training for up to 10 Government/Government support personnel at ARTS-V2 fielding location Nevada Test Training Range (NTTR) and at each production fielding locations (one training event per site) upon system acceptance (post DD-250).

3.2.9 Develop and provide Level II maintenance training (depot) for up to 10 Government/Government support personnel one time at the contractor facility.

3.2.10 Assist the government in updating the PPP and Anti-Tamper Plan.

3.2.11 Assist the Government in acquiring ARTS-V2 Stage 3 Developmental

Frequency Certification from the National Telecommunications and Information Administration (NTIA).

3.3 Design ARTS-V2 to include Cybersecurity.

3.3.1 Identify, manage, verify, and validate cybersecurity/TEMPEST requirements in the same manner as all other program requirements.

5 | P a g e

3.3.2 Integrate cybersecurity/TEMPEST considerations into program systems engineering and design processes, including risk management.

3.3.3 Assist and provide support, source data, and analysis in obtaining Platform Information Technology (PIT) certification and accreditation (C&A) and TEMPEST approval for the system IAW DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) (12 March 2014) which includes assisting and providing support for Interim Authorization to Operate (IATO)/ Authorization to Connect (ATC)/ Authorization to Operate (ATO).

3.4 Design ARTS-V2 to include Cybersecurity/Software Assurance.

3.4.1 Acquire secure, robust, and assured software through use of disciplined processes and procedures that include analysis based on industry standard sources, including the implementation of Common Weakness Enumeration (CWE™), Common Vulnerability Enumeration (CVE®), Open Web Application Security Project (OWASP) tools and guidance, Common Platform Enumeration (CPE™), and Common Attack Pattern Enumeration and Classification (CAPEC™).

3.4.2 Acquire software that satisfies the requirements of Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and minimizes the overall Common Weakness Scoring System (CWSS) and Common Vulnerability Scoring System (CVSS) scores of the enterprise or standalone systems to which the software will be installed.

3.4.3 Minimize vulnerabilities and defects by creating processes to build security into software throughout its development and operational lifecycles as well as creating processes that identify and correct/mitigate vulnerabilities.

3.4.4 Build in resiliency to the architecture (fail securely) in order to reduce the impact of exploited software vulnerabilities.

3.4.5 Propose, and incorporate a set of cybersecurity controls designed to include the following cybersecurity areas (IAW NIST SP 800-59, NIST SP 800-53, NIST SP 800-53A, CNSSI 1253, CNSSI 1253F Attachment 5, FIPS-PUB-199):

3.4.5.1 Ensure that data is protected from improper disclosure (data generated by ARTS-V2 and exchanged with the training range).

3.4.5.2 Ensure boundary defenses for the ARTS-V2 system and any applicable subsystems that cannot defend themselves.

3.4.5.3 Ensure a risk-managed means of selectively allowing essential information to flow across the ARTS-V2 boundary.

3.4.5.4 Protect against systems and data being undermined by external systems or forces.

3.4.5.5 Provide strong authentication, ensuring authenticated access control of users using ARTS-V2 systems.

3.4.5.6 Protect against the delay, miss-delivery, or non-delivery of otherwise adequately protected information.

3.4.5.7 Ensure protection mechanisms do not interfere with operations

6 | P a g e

3.4.5.8 Provide intrusion detection, reporting, analysis, assessment, and response infrastructure that enables rapid detection and response to intrusions and other anomalous events, and that enables operational situation awareness.

3.4.5.9 Provide a means for execution and reporting requirements for contingencies and reconstitution.

3.4.5.10 Provide standard Air Force data protection and transportation measures ensure the computer, network attached storage, and data recorder drives are protected from disclosure to anyone not authorized access to the hard drives.

3.4.5.11 Provide automated removal of sensitive data from ARTS-V2 computer buffers, file system directories, file system metadata, and data storage areas.

3.4.5.12 Provide measures to restore the system to its original configuration from backup media in the event a disruption occurs.

3.4.5.13 Ensure cybersecurity products are compliant with the Committee on National Security System’s Policy Number 11 (CNSSP No. 11). .

3.4.5.14 Maintain cybersecurity situational awareness, manage risk, and comply with standards/regulations to support the Government in complying with the Federal information Security Management Act (FISMA).

3.4.5.15 Cybersecurity controls up to the SECRET/Special Access Request (SAR) level.

3.5 Develop error-free modular software using widely adopted industry and government-based data formats and interface standards in a layered architecture by exploiting open source technologies and commercial development tools.

3.6 Design ARTS-V2 to include Software Metrics:

3.6.1 Develop, collect, analyzes and report software metrics and document this approach in a Software Development Plan (SDP).

3.6.2 Utilize software metrics to effectively manage and control software development and integration activities.

3.7 Design ARTS-V2 to address Software and Hardware Interfaces.

3.7.1 Conduct comprehensive, rigorous, and disciplined interface management for both internal and external interfaces.

3.7.2 Integrate interface management with requirements management and configuration management.

3.8 Implement a System Security Engineering (SSE) process that:

3.8.1 Identifies and reduces the system’s susceptibility to damage, compromise, or destruction.

3.8.2 Identifies, evaluates, and eliminates or contains the system’s vulnerabilities to known or postulated security threats in its operational environment.

7 | P a g e

3.9 Develop secure, reliable, standards-compliant, defect-free firmware utilizing disciplined developmental, integration, and verification methodologies and document this approach in a Firmware Development Plan (FDP).

3.10 ESSS development shall include: CDR, FAT, SAT, and Test Readiness Review (TRRs).

3.11 Provide technical data , computer software , and computer software documentation associated license rights required for the Government to execute system, sub-system, and component competitive procurement, accomplish program sustainment, and perform organic or Contractor Logistics Support (CLS) maintenance throughout the expected life of the system.

4. OTHER PROGRAM ACTIVITIES: This section includes specific programmatic activities and deliverables required by the ARTS-V2 Program. The list may not be comprehensive to support contract activities therefore additional work statements and CDRLs may be proposed in CSOW.

4.1 Prime Mission Product

In development and production of ARTS-V2 systems:

4.1.1 Develop a software architecture that is highly modifiable and lends itself to scalability.

4.1.2 Implement a robust and tamper-resistant architecture.

4.1.3 Utilize the National Security Agency (NSA) Trusted Access Program

Office (TAPO) trusted suppliers for all cyber security related hardware.

NOTE P: See www.nsa.gov/business/programs/tapo.shtml for TAPO information.

4.1.4 Develop a system that affordably, efficiently, and effectively leverages Commercial-Off-The-Shelf (COTS) IT products.

4.1.4.1 COTS software shall be approved by the government prior to use IAW NSTISSP No. 11 National Information Assurance Acquisition Policy (July 2003).

4.1.5 Utilize an Environmental Stress Screening (ESS) program during development and production phase to improve field reliability and reductions in field maintenance costs.

4.1.6 Non-commercial code and associated libraries shall be delivered in the native source format in which it was developed. Commercial and open source code shall be delivered IAW the license agreement and will include any and all libraries and source code covered by the license

4.2 System Integration

4.2.1 Include Human Systems Integration elements in system and subsystem design to address human operator and maintainer actions.

4.2.2 Perform site survey for planned ESSS installation location and deliver a report IAW CDRL AG29 that outlines:

4.2.2.1 Identify discrepancies between actual on-site conditions and conditions required to support full ESSS functionality.

4.2.2.2 Report complete listing of contractor findings.

http://www.nsa.gov/business/programs/tapo.shtml

8 | P a g e

4.2.2.3 Include summary of anticipated site infrastructure changes required to support ESSS.

4.2.2.4 Document findings concerning other on-site conditions that could impact ESSS operations.

4.2.3 Perform site survey for PRA fielding at Nevada Test & Training Range (NTTR) IAW CDRL BZ31 and the following instructions.

4.2.3.1 Identify discrepancies between actual on-site conditions and conditions required to support full ARTS-V2 functionality.

4.2.3.2 Report complete listing of contractor findings.

4.2.3.3 Include summary of anticipated range infrastructure changes required to support ARTS-V2.

4.2.3.4 Document findings concerning other on-site conditions that could impact ARTS-V2 operations.

4.3 Systems Engineering

4.3.1 Develop, deliver, and follow throughout the life of the contract a Quality

Assurance Plan (QAP) IAW CDRL BZ28.

4.3.2 Minimize the use of peculiar support equipment in the design, manufacture, testing, calibration, and support of ARTS-V2.

4.3.3 Develop, deliver, and follow throughout the life of the contract, a Systems

Engineering Management Plan (SEMP) that follows the principles of Electronic Industries Alliance (EIA) 632 Processes for Engineering a System (September 2003). Deliver IAW CDRL BZ09.

4.3.3.1 Perform SAT for every delivered system.

4.3.4 Acquire ARTS-V2 Internal Air Transport Certification for C-5 and C-17 aircraft through the Air Transportability Test Loading Agency (ATTLA).

4.3.5 Develop a Technical Staffing Profile and deliver at Post Award Conference with updates at PRA CDR, PRA FAT, 30 days after any ICS option is exercised, and 30 days after any production option is exercised

IAW CDRL BZ37, GZ16, NZ16, QZ16, SZ16, UZ12, WZ12, YZ12,

AA12, AC12.

4.3.6 Develop, deliver, and follow throughout the life of the contract a Configuration Management (CM) Plan IAW CDRL BZ11.

4.3.7 During the production option years if the program requires a change due to obsolescence or a government imposed new requirement, contractor shall submit Class I Engineering Change Proposals (ECP) to ARTS-V2 Program Office for approval prior to making Class I configuration changes against the government owned/controlled baseline(s) IAW CDRL FZ01, MZ01, PZ01, RZ01, TZ01, VZ01, XZ01, ZZ01, AB01, AD01, & AF01.

NOTE Q: ECPs during Engineering and Manufacturing Development (EMD), (PRA development) under CDRL FZ01 may only be applied when changes are driven by events outside the contractor’s control (e.g.

government action). All normal design/build/test iteration costs shall be included in CLIN 0001.

9 | P a g e

NOTE R: ECPs during the Production option years under CDRLs MZ01, PZ01, RZ01, and TZ01 may only be applied when changes are driven by events outside the contractor's control (e.g. obsolescence and/or Government imposed requirement changes).

NOTE S: ECPs during Interim Contractor Support (ICS) under CDRLs VZ01, XZ01, ZZ01, AB01, and AD01 may be applied when the deployed systems require repair, test and/or replacement of LRUs/SRUs.

4.3.7.1 ECPs are required for changes to Functional, Allocated, and

Product Baselines for both the PRA and Production.

NOTE T: Baseline definitions and establishment events may be found in the Defense Acquisition Guidebook (https://dag.dau.mil/Pages/Default.aspx) in sections on System Functional Review (SFR), Preliminary Design Review (PDR), and Critical Design Review (CDR).

NOTE U: Changes to contractor controlled baselines do not require government approval however the contractor shall make available for government review ECPs, Specification Change Notices, or Requests for Deviation (as appropriate) to the government to document the changes.

NOTE V: ECPs will include all test efforts and technical data & software updates necessary to capture changes.

NOTE W: Contractor Class II Engineering Change Orders (ECOs) due to conversion of drawings from “developmental” to “production” levels shall always be delivered to the government via CDRL GZ08 and require government concurrence of the classification.

4.3.7.2 The definition of Class I and Class II ECPs shall be IAW MIL- HDBK-61A Table 6-2.

NOTE X: ARTS-V2 Program Office will take configuration control of the Functional Baseline after successful completion of PRA CDR and will retain control throughout the remainder of the contract.

NOTE Y: ARTS-V2 Program Office will take configuration control of the Allocated and Product Baselines after successful completion of PRA Factory Acceptance Testing, Functional Configuration Audit, Site Acceptance Testing and the Physical https://dag.dau.mil/Pages/Default.aspx

10 | P a g e

Configuration Audit and will retain control throughout the remainder of the contract.

NOTE Z: The ARTS-V2 Program Office will be the ECP Class I determination authority throughout the life of the contract.

4.3.7.3 Following the establishment of each PRA associated baseline the contractor will deliver periodic summaries of all changes to contractor managed baselines, IAW CDRL BZ83. At minimum, summaries shall include: drawing numbers affected, revision number and a brief description of the change.

4.3.8 Develop, deliver, and follow throughout the life of the contract a System Safety Program Plan that complies with all requirements in MIL-STD- 882E, Standard Practice for System Safety (11 May 2012) IAW CDRL

BZ15.

4.3.9 Establish an Environmental, Safety, and Occupational Health (ESOH) Program that complies with ESOH laws and regulations.

4.3.9.1 Utilize the Environmental Impact Analysis Process (EIAP) as described in Title 32, Code of Federal Regulations (CFR), Part 989 (32 CFR Part 989).

4.3.10 Minimize ESOH impacts to program cost, schedule, and performance for the planned life of the system.

4.3.11 Address the demilitarization ESOH considerations at PRA PDR and PRA CDR IAW DODI 4160.28-M, Vol 1-3, DoD Demilitarization (DEMIL) Program (7 June 2011).

NOTE AA: This should include disposal considerations, hazardous materials considerations, and will support the government in cost forecasting.

4.3.12 Develop, deliver, and follow throughout the life of the contract an Item Unique Identification (IUID) Marking Plan IAW CDRL BZ12.

4.3.13 Place IUID marks on required assets where mark is easily accessible for scanning while in an operational configuration, with the goal being not to require disassembly for access.

4.3.14 All IUID markings shall be produced and applied according to the Technical Data Package (TDP).

4.3.15 IUID markings will be produced and applied IAW the most recent version of MIL-STD-130N (16 November 2012) CDRL BZ12 & BZ40, GZ20, NZ20, QZ20, SZ20, UZ15, WZ15, YZ15, AA15, AC15, AE18, & AG18.

4.3.16 Develop, deliver, and follow throughout the life of the contract a Hazardous Material Management Program Plan IAW CDRL BZ13.

4.3.17 Develop, delivers, and follows throughout the life of the contract a Counterfeit Prevention Plan IAW CDRL BZ22.

11 | P a g e

4.3.18 Develop, deliver, and follow throughout the life of the contract a Parts Management Plan IAW CDRL BZ23.

4.3.19 Develop, deliver, and follow throughout the life of the contract a Reliability and Maintainability Program Plan IAW CDRL BZ27.

4.3.20 The contractor shall utilize a requirements management application that acts as a central repository for the official requirements baseline.

Program office will have daily read only access to the unclassified requirement portion remotely, and access to the classified requirements at contractor location. Requirements will be traceable and or linked to different level specifications and requirement verification activities. Each unique object in the application will include revision history. In addition, full system requirement definitions will be delivered IAW CDRL BZ53, GZ53, and AG09.

4.3.21 After completion of Factory Acceptance Testing (FAT) of the first production unit, complete a Functional/Physical Configuration Audit (FCA/PCA) to the Production Technical Data Package and Technical Orders.

NOTE BB: FCA will be a simplified review to confirm that ECPs have not affected functional performance. PCA will be complete to the subassembly level against the Production level drawing package with all ECPs incorporated. This will establish the new Product Baseline.

4.4 Program Management

4.4.1 Provide membership for, support, and attend meetings for the ARTS-V2

Program Office Systems Engineering & Integration (SE&I) Integrated Product Team (IPT)/working groups and the ARTS-V2 Integrated Test Team (ITT). Contractor may propose support for additional government activities.

4.4.2 Use commercial practices for Packaging, Handling, Storage & Transportation (PHS&T) IAW ASTM D3951-10-15 (August 2010) for ARTS-V2 components until the following required CDRLS are accepted:

GZ34, GZ35, GZ36, GZ37, & GZ39. Use AFMC Form 158 attached to section J, Attachment 32, Packaging Requirements, for preservation and packaging requirements associated with each CLIN. Add comparable language to that found in section J, Attachment 32, Packaging Requirements Packaging Instructions to the CSOW.

4.4.3 Identify and quantify amount (e.g. page count, number of drawings) of data to be delivered to support technical reviews no later than 90 days prior to review IAW CDRL BZ21.

4.4.4 Develop, deliver, and follow throughout the life of the contract a Risk Management Plan (RMP) to manage the risks of the ARTS-V2 Program and deliver IAW CDRL BZ14.

4.4.5 Develop, deliver, and follow throughout the life of the contract a Diminishing Manufacturing Sources and Material Shortages (DMSMS)

12 | P a g e

Management Plan to manage the risks of the ARTS-V2 Program and deliver IAW CDRL BZ55.

4.4.6 Verify ARTS-V2 parts list against Government Industry Data Exchange Program (GIDEP) for obsolescence and for components and parts for which alerts have been generated.

4.4.7 Provide alert/safe-alert responses to GIDEP as applicable.

4.4.8 Small Business Participation Requirements

4.4.8.1 The Government has set a minimum small business

subcontracting goal for this effort of 11% of the total subcontracted amount.

4.4.8.2 Small Disadvantaged Business (SDB): 5% of the total

subcontracted amount above.

4.4.8.3 Woman-Owned Small Business: 5% of the total subcontracted amount above.

4.4.8.4 Hub-zone: 3% of the total subcontracted amount above.

4.4.8.5 Service-Disabled Veteran-Owned Small Business: 3% of the total subcontracted amount above.

4.4.8.6 A Small Business Subcontracting Plan will be required IAW

Federal Acquisition Regulation (FAR) 52-219-9, Small Business Subcontracting Plan.

4.5 Data

4.5.1 Protect all classified information IAW DoD 5220.22-M National Industry

Security Program Operating Manual (NISPOM) (28 February 2006).

4.5.2 Protect all development and production data IAW Air Force (AF) and Air

Force Material Command (AFMC) Scientific and Technical Information (STINFO) policies and procedures. Department of Defense Instruction (DoDI) 5230.24 (23 August 2012) and Department of Defense Directive (DoDD) 5230.25 (6 November 1984), Air Force Instruction (AFIs) 63- 101/20-101 (7 March 2013, Incorporating Through Change 2, 23 February 2015), AFI 33-200 (31 August 2015), Air Force Manual33-282, Computer Security (COMPUSEC) (28 MARCH 2012, Incorporating Change 1, 15 January 2015),and AFI 61-204 (30 August 2002).

4.5.3 Deliver classified CDRL data IAW DoDM 5220.22-M National Industry Security Program Operating Manual (NISPOM) (28 February 2006).

4.5.4 Safeguard Critical Program Information (CPI) and provide countermeasures against accidental and intentional disclosure.

4.5.5 Integrate cybersecurity considerations into program systems engineering and design processes, including risk management.

4.5.5.1 Comply with DoDI 8500.01 Cybersecurity (14 March 2014), NIST FIPS PUB 199 National Institute of Standards and Technology - Standards for Security Categorization of Federal Information and Information Systems (February 2004), NIST SP 800-53A Rev. 1, Guide for Assessing Security and Privacy Controls in Federal Information Systems and Organizations (June 2010), NIST SP 800-53 Rev 4, National Institute of Standards and Technology - Security and Privacy Controls for

13 | P a g e

Federal Information Systems and Organization (30 April 2013).

4.5.6 Develop, deliver, and follow throughout the life of the contract a Program Protection Implementation Plan IAW CDRL BZ26 that incorporates protection measures contained in the government ARTS-V2 PPP.

4.5.6.1 Comply with Air Force Communications Security (COMSEC) and Air Force Communications Security (COMSEC) Operations (AFKAG) for COMSEC requirements.

4.5.6.2 Adhere to approved foreign national visit procedures IAW AFI 16-201 Chapter 5 (2 June 2015).

4.5.6.3 Comply with DoDI 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems (6 June 2012), and DFARS Subpart 204.73 Clause 252.204-7012 Safeguarding Unclassified Controlled Technical Information.

Comply with DoD 5220.22-M, The National Industrial Security Program Operating Manual, (NISPOM) (28 February 2006).

4.5.7 Develop, deliver, and follow throughout the life of the contract a TEMPEST Control Plan IAW CDRL BZ88.

4.5.8 Develop, deliver and follow throughout the life of the contract an Information Assurance Test Plan IAW CDRL EZ13.

4.5.9 Develop and deliver all drawings, technical data package materials, and technical orders IAW CDRL CZ01, DZ01, DZ03–DZ07, DZ10, DZ12, GZ33, HZ01, JZ01, AG23, and AG25.

4.5.10 Develop, deliver and follow throughout the life of the contract an Information Systems Security (INFOSEC) Anonymity Plan (IAP) IAW

CDRL BZ25.

4.5.11 Develop and deliver familiarization and operations training materials IAW CDRL BZ51, BZ68, GZ21, & GZ41 to address the following topics at minimum:

4.5.11.1 Familiarization of major subsystem location and operations.

4.5.11.2 Set up and power up procedures.

4.5.11.3 Pre-mission set up instructions.

4.5.11.4 Orientation on typical target acquisition and track procedures.

4.5.11.5 Orientation on typical post mission procedures.

4.5.11.6 Within mission move considerations.

4.5.11.7 Introduction Built-in-Test error interpretation.

4.5.11.8 Tear down and power down procedures.

4.5.11.9 General maintenance overview.

4.5.11.10 Utilize and refer to T.O. Sections wherever possible.

4.5.12 Develop and deliver Level II Repair training materials IAW CDRL AH01 & AH02 to address the following topics at minimum:

4.5.12.1 Familiarization and operations training materials.

4.5.12.2 Detailed maintenance overview.

4.5.12.3 Utilize and refer to Operator & Depot T.O. Sections.

4.6 Interim Contractor Support

14 | P a g e

4.6.1 Provide ICS support for systems at all fielding locations listed in NOTE O as well as deployment locations to include Anderson AFB, Guam.

4.6.2 Provide an Integrated Logistics Support Management Organization and perform the following functions:

4.6.2.1 Program Management IAW CDRL UZ01-UZ05, UZ09, UZ37, WZ01-WZ05, WZ09, WZ37, YZ01-YZ05, YZ09, YZ37, AA01-AA05, AA09, AA37, AC01-AC05, AC09, AC37.

4.6.2.2 Business Management.

4.6.2.3 Subcontract Management.

4.6.2.4 Security.

4.6.2.5 Quality Assurance Program Execution.

4.6.2.6 Warranty Compliance Efforts.

4.6.2.7 Field Performance/Failure Reports & Configuration

Management Program for HW/SW.

4.6.2.8 Perform maintenance on assets removed and replaced by

Government Maintainers.

4.6.2.9 Level II Maintenance on fielded ARTS-V2 systems

4.6.2.10 Software Support as needed.

4.6.2.11 Spares Replenishment to support a 90% Operational

Availability requirement.

4.6.2.12 Establish a 24-hour Field Support Hotline (FSH) to support

Level-I Maintenance. Document all requests for support as well as provided support and deliver as a part of the Contractor Progress and Status Report.

4.7 Provisioning

4.7.1 Participate in the Provisioning process.

4.7.2 Support a Provisioning Guidance Conference (PGC).

2. contract objectivE