15RJT82_syn_0002_att.docx

Statement of Work for the Prototyping of Advanced Sensors and Sensor Systems

1.0 Scope

This Statement of Work (SOW) sets forth the requirements to provide prototypes of advanced sensors and sensor systems in support of Intelligence, Surveillance, and Reconnaissance (ISR) and Force Protection missions. The contractor shall furnish all material, labor, documentation, and technical support services for the research, design, development, repair, and prototyping of new technology items, modified piece parts, subsystem components, or systems as required by the contract, and per each Delivery Order (DO)/Task Order (TO).

1.1 Background

ISR systems provide expeditionary forces a theater-wide, 24 hour (day/night), persistent, surveillance capability. The warfighter requires this capability to disrupt insurgent sniper activities and to counter the threat of indirect fires and improvised explosive devices (IEDs). This capability must achieve absolute tactical over-watch coverage of the entire area of operations in order to a) enable offensive counter-insurgency operations to be conducted more effectively b) allow tracking of cross border activities of foreign forces; and c) allow tracking on inter-theater movement and activities of Terrorist, Insurgents, and Criminals (TIC).

2.0 Applicable Documents

The documents listed below are not necessarily all of the documents referenced herein, but are the ones that are needed to fully understand the information provided. The following documents form a part of this SOW to the extent specified herein. Unless otherwise specified, the most current version of these documents as of the date of solicitation issue listed in the Department of Defense Index of Specification and Standards (DoDISS) and supplement there to shall be applicable.

2.1 Government Documents

Performance on this contract, requires all contractor performance to be in accordance with the below sited documents; and all applicable regulations, instructions, and policies of the Defense Information Systems Agency (DISA). The current websites for reviewing DISA requirements are http://www.disa.mil , and http://www.disa.mil/Services/Network-Services/Enterprise-Connections/References . Additionally contractor compliance with National Security Agency (NSA) requirements is mandatory as applicable. The current websites for reviewing NSA requirements are http://www.nsa.gov , and http://www.nsa.gov/ia . Contractors shall become familiar will all identified documents in the SOW to ensure responsibility in compliance during performance on this contract.

2.1.1 Specifications, Standards, and Handbooks

Standards, Department of Defense (DoD)

MIL-STD-130N Identification Marking of US Military Property, December 17, 2007

MIL-STD-810G Environmental Engineering Considerations and Lab Tests, October 31, 2008

MIL-STD-882D Standard Practice for System Safety, February 10, 2000 Manual, DoD

DoD 5220.22-M National Industrial Security Program Operating Manual, February 28, 2006

Directive, DoD

DoDD 4715.1E Environment, Safety, and Occupational Health (ESOH), March 19, 2005

CJCSI 6211.02D Defense Information Systems Network (DISN) Responsibilities, January 24, 2012

DoDI 6055.11 Protection of DoD Personnel from Exposure to Radio Frequency Radiation and Military Exempt Lasers, August 19, 2009

DoDI 8500.01 Cybersecurity, March 14, 2014

DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling, May 24, 2011

DoDI 8520.03 Identity Authentication for Information Systems, May 13, 2011

DoDI 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems, June 10, 2012

Other

Drawing Package As required by each DO/TO.

NSWCCR-4130-JXT-13-002 Surveillance and Reconnaissance Systems Division Configuration Management Plan and Document Control Plan (CMP), Date 08/16/2014

2.2 Non-Government Documents

2.2.1 Industry Standards

3.0 Requirements

The contractor shall furnish all materials, parts, supplies, equipment, labor, technical expertise, supporting documentation, and any other incidental items necessary to accomplish the Prototypes, Engineering Development Models (EDMs), and Pre-production components, subsystems, and systems of the specified advanced sensors and sensor systems identified in each Delivery Order (DO). The contractor shall build, test, and deliver documentation and prototypes of the specified advanced sensors and sensor systems in accordance with this SOW and as required by DOs. The contractor shall utilize modularity and/or integrated systems approaches to design and develop prototypes, EDMs, and pre-production units that meet the technical requirements of this contract, and as required per DO. DOs will focus on improving system life cycle costs, operational life, performance, sustainment including maintainability and support, safety and environmental influence, and operation friendliness and training. The contractor shall maintain appropriate subcontract relationships to support these requirements.

3.1 Detailed Tasks

The following paragraphs provide a general list of the required supplies and services that will be required throughout the period of performance of the contract. The contractor shall provide the necessary resources with knowledge and certifications to perform the tasks in this contract. Specific objectives will be dependent on the base contract and the DOs written against the base contract. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, quality, and meeting delivery schedules. Work shall not commence on a delivery order without authority from the appropriate Government Contracting Officer.

Knowledge and capability in the following areas are expected to be required to build advance sensors and sensor system prototypes under the contract:

-C2/C4 Software -Elevating Platforms (adjustable height platform, fixed platform, mobile vehicle platform) -Computing Hardware -Power Distribution -Alternative Energy -Sensor Interface (mechanical, electrical, computing) -Common Sensor Environments -Environmental Evaluations and testing -Electromagnetic Interference -DoDAF Development (DoD Architecture Framework) -DOORS (Dynamic Object Oriented Requirements System) -System and Component Modeling -CAD Support -System Development -Component Development -Network Engineering -Communication Devices -IA Accreditation (8570) -Analysis of Alternatives (AoA) -MTBF / MTTR projections (Mean Time Between Failure / Mean Time To Repair) -Machine Shop fabrication -Circuit Card Assembly -Cable Assembly

3.1.1 Fabrication

The contractor shall build and deliver prototypes, EDMs, and pre-production units for the specified advanced sensors and sensor systems according to the TDP &/or SOW provided with DO contract award. The contractor shall provide material, labor, and supporting documentation necessary for prototype production. Supporting documentation may include, but is not limited to, market research, component specifications, drafting, technical data, and assisting the government in documenting Analysis of Alternatives (AoAs) for such things as alternative energies, system configurations, or other – as identified per DO. Prior to implementing any changes, the contractor shall correct and document any design characteristics that are found to inhibit or make fabrication unnecessarily costly but that do not otherwise alter performance or system effectiveness characteristics. The contractor shall provide all studies and analyses information, documentation, and reports to the Government for review/approval per CDRL A001. (CDRL A001, Technical Report – Study/Services)

3.1.1.1 Equipment/System/Supply

As required by DO, ISR technical documents, Information Operations (IO), and/or Information Assurance (IA) procedures, the contractor shall develop, fabricate, modify, procure, evaluate, repair and deliver equipment/systems/supplies/components, Subject Matter Experts (SMEs), and technical support to the Government. All items shall conform to applicable product verification, validation, identification, and tracking requirements. The contractor shall provide the equipment, software/firmware, license/access keys, accessories, and all associated documentation such as: operator/maintenance manuals, technical specifications, parts lists, drawings, installation instructions, etc. Each DO will provide the specific equipment/system/supply performance requirements, salient characteristics, specifications, or brand name product and the minimum delivery schedule for each item ordered.

3.1.1.2 National Information Assurance/Computer Security Requirements The contractor shall ensure that all selected, developed, fabricated, and procured products impacting Information Assurance (IA) are included in the National Security Agency (NSA) and National Institute of Standards and Technology (NIST), National Information Assurance Partnership (NIAP) Validated Product List (VPL)/Program Product Compliant List as appropriate. Additionally, the contractor shall ensure that the products possess the appropriate Evaluated Assurance Level (EAL)/Protection Profile compliance for the secure/unsecure network involved. The contractor may be required to get advanced sensors and sensor systems products added to NSA & NIST, NIAP Product Compliant List as directed by DO. The contractor shall verify and validate that all applicable Information System (IS) hardware and technologies such as but not limited to Cross Domain Solutions (CDS) are in accordance with CJCSI 6211.02D. Compliance with CJCSI 6211.02D includes connections and transmission of information. The contractor shall only utilize the products in accordance with the current NSA and DISA orders, regulations and guidance documents at the time of award of each DO.

3.1.1.3 Cybersecurity

The contractor shall protect and defend DoD information and information technology (IT) to protect U.S. interests, DoD operational capabilities, and DoD individuals, organizations, and assets at all levels as required by DoDI 8500.01, Cybersecurity. The contractor shall address risk management as early as possible for all IT and in an integrated manner across the IT lifecycle. The contractor shall fully integrate Cybersecurity into system life cycles, and to the greatest extent possible standardize IT tools, methods, and processes to eliminate duplicate costs and focus on creating technological mature and verified solutions. The Government will oversee and govern the implementation and management of cybersecurity, measure and manage cybersecurity success, collect data for reporting. The Government reserves the right to inspect all contractor IA processes, procedures, guidance documents, training plans, facilities, authorized personnel lists, and IA equipment for research, design, and development of prototypes, EDMs, and pre-production units as necessary to verify compliance with all Government IA requirements.

3.1.1.3.1 Identity Assurance

The contractor shall ensure that personnel identification, and authentication policies, and procedures are strong in order to eliminate anonymity in DoD IS and IT components and systems. The contractor shall ensure that all personnel are properly trained. The contractor shall use the most current DISA Security Technical Implementation Guide (STIGs) and scanning tools during development to ensure compliance, and additionally comply with 8500.21A controls. As required by DO, the contractor will be required to participate in PUBLIC KEY INFRASTRUCTURE (PKI) AND PUBLIC KEY (PK) ENABLING per DoDI 8520.02 as required, and comply with DoDI 8520.03.

3.1.2 Drawings

The contractor shall develop and deliver sketches, drawings and 3D models for prototypes, pre-production units, EDMs as required by each DO. The Government shall have Unlimited Data Rights for all drawings, technologies, software/firmware, hardware, products, and systems, discovered/utilized/designed/developed from performance on this contract unless an assertion is provided by the contractor and accepted by the Government. The Government will provide drawings numbers to the contractor for origination/revision of all drawings as applicable. The contractor shall make changes/revisions on Government drawings as they occur and as approved by the Government, and shall maintain updated drawing files. Per Government stipulations in applicable DOs, the contractor shall use Solid Edge, Innoventor, or similar software to provide all drawings to the Government for parametric, .STEP, .SAT data output files. The latest revision of drawings shall be submitted to the Government throughout the period of performance of the contract, per CDRL A002. (CDRL A002, 3D Mechanical Drawings)

3.1.2.1 Physical Configuration Audit (PCA).

The Contractor shall conduct a Government witnessed PCA as required by each DO or TO. The PCA shall be conducted on the prototype units delivered and shall be performed using a Government approved Contractor’s Configuration Audit Plan, PCA Plan (CDRL A008). Contractor shall perform PCA following successful completion of prototype testing. During the PCA, the Contractor shall establish a high level of confidence in the physical configuration of the as-built, as-designed, and as-maintained version of the system in order to finalize the product baseline.

3.1.3 Software

The contractor shall research, analyze, develop and deliver software/firmware for the specified advanced sensor and sensor system as required by each DO. The Government will retain Unlimited Data Rights. The contractor shall maintain and update Government software/firmware will all changes that occur. The latest revision of software/firmware shall be submitted to the Government throughout the period of performance, per CDRL A003. (CDRL A003, Software)

3.1.4 Characterization Testing

The contractor shall provide test facilities, conduct and provide technical support for characterization testing on prototype, EDMs, pre-production advanced sensors and sensor systems and/or Government hardware/software as required per DO. Characterization testing includes the following categories and may require the contractor to perform research, studies, and analysis:

· Environmental Testing in accordance with MIL-STD-810G.

· Performance Characterization Testing to determine maximum functional capability.

· Operational Simulation.

The contractor shall provide technical support information per CDRL A001, and the evaluation and test report to the Government per CDRLs A004 and A005, as required by DO. (CDRL A004, Test Report) (CDRL A005, IA Test/Evaluation Report) (CDRL A001 – Technical Report – Study/Services)

3.1.5 Engineering & Technical Support

The Contractor shall provide Engineering Services (ES) in support of the manufacture, assembly and testing of the prototype systems under this contract. ES shall be performed in accordance with Technical Instructions provided by the COR. This may include engineering and technical support for research, design, and development of prototype hardware/software/and firmware for advanced sensors and sensor systems. Engineering and technical support may include development and conducting testing of alternative energies, system configurations, information assurance capabilities, data types, finite element, and ability to provide the required technologies/capabilities to build prototypes and EDMs. The contractor shall provide process modeling, analysis, and re-engineering as specified per Task Order (TO) and/or TI. The contractor shall present design reviews including status, AoA, Requirements Traceability Matrix (RTM), reliability, test results, and cost as required by the TO/TI. Process characterization involves the development of ‘as-is’ or baseline models. The contractor shall use a structured approach to define how operations are currently performed, to determine the reasons for current success, and to identify those areas in need of improvement. The contractor shall provide engineering and technical services to provide advanced sensors and sensor systems such as, but not limited to a CDS that meets all data types as defined in TO/TIs. Meeting all data types is essential to CDS verification and validation testing for obtaining certification. The contractor may need to include SMEs as necessary to meet all Government requirements. The contractor shall provide evaluation and test reports to the Government per CDRL A001, CDRL A004, and CDRL A005, as required by DO. (CDRL A001, Technical Report – Study/Services) (CDRL A004, Test Report) (CDRL A005, IA Test/Evaluation Report)

3.1.5.1 Engineering Design, Safety

The contractor may be required to provide engineering and technical support for research, design, and development to provide for pollution prevention, environmental compliance, and pursue the means to develop, safeguard, or improve the protection of the health and wellbeing of personnel as a vital component of the system and/or its critical processes as provided for in the TO/TI for ES. The contractor shall ensure adherence and compliance with all environmental, health, and safety policies, regulations, and laws. All submitted engineering recommendations/solutions shall include consideration of the impact to the environment and to personnel health and safety, and address any concerns as appropriate.

3.1.5.2 Engineering presentation

The contractor may host design presentations of the engineering & technical support process and outputs. This may include in-process presentations and final presentations.

3.1.6 Preliminary Functional Verification Test (PFVT) Procedures The contractor shall develop all PFVT procedures necessary for the functional verification testing of the prototype advanced sensor and sensor systems per CDRL A006, and per DO/TO requirements. The PFVT procedures for the advanced sensors and sensor systems shall be submitted to the Government for review and approval. The contractor shall obtain Government approval in writing prior to any testing of the system. (CDRL A006, Preliminary Functional Verification Test Procedure)

3.1.7 Preliminary Functional Verification Test (PFVT) Reports The contractor shall document the PFVT results in the PFVT Report, and provide the Government signed test report to the Government technical point of contact per CDRL A006. The PFVT will be witnessed by a Government representative at contractor’s facility. The contractor shall coordinate testing schedules with the Government, and provide notification to the Government technical point of contact within a minimum of 10 calendar days prior to the scheduled test. Additionally, the contractor shall ensure that Government signature is obtained on PFVT report upon successful completion of PFVT (CDRL A006, Preliminary Functional Verification Test Report).

3.1.8 Certification & Security Testing & Evaluation (CT&E)

The contractor may be required to participate in CT&Es, including NSA and Security Testing & Evaluations (ST&E). CT&E & ST&E testing locations are anticipated to be CONUS locations, and will be identified as applicable per DO/TO. The contractor is responsible for operating and maintaining the pre-production units during CT&E and/or ST&E as required. The contractor shall provide all necessary artifacts for conducting the CT&E and ST&E, including independent test results, source solution codes, and source solution code analyses. The combined duration for the CT&E and ST&E testing is anticipated to be 9 months for the CDS. The contractor is required to obtain acceptable risk ratings from Decision Authorities, favorable recommendations from Technical Advisory Boards, and approvals from the Defense Information Security Accreditation Working Group (DSAWG), Interim approvals, and Certifications.

3.1.9 Acceptance Test

The contractor shall perform Acceptance Test Procedures (ATP)s for all prototypes, EDMs, and pre-production units as required by each DO/TO. The contractor shall ensure that ATPs include documentation of significant component serial numbers and software versions. The contractor shall provide the written ATP to the Government for review and acceptance per CDRL A007. The contractor shall make changes to the ATP as required by the Government, to obtain Government approval. Additionally the contractor shall provide documentation of test reports, findings, and analyses of all items tested via an Acceptance Test Reports (ATR)s per CDRL A008. The contents of the ATR shall ensure that the deliverable meets all Government contract requirements, as identified per DO. (CDRL A007, ATP) (CDRL A008, ATR)

3.1.10 Technical Manuals

The contractor shall develop technical manuals, to include operator manuals and user guides for the specified advanced sensor and sensor systems as required by each DO/TO. The contractor shall submit draft technical manuals to the Government for review and approval. The contractor shall develop all necessary edits to existing technical manuals for the specified advanced sensor and sensor systems as required per DO/TO. All edits and supplemental data to existing Technical Manuals shall be submitted to the Government for review and approval prior to final print/delivery. (CDRL A009, Technical Manual Research and Analysis Source Data)

3.1.11 Training

The contractor shall provide training and training material to government representative, and/or operators as required by each DO/TO. The contractor shall provide a copy of all training materials and presentations to each class attendee per CDRL A010. (CDRL A010, Course Conduct Information Packet)

3.2 Programmatic

3.2.1 Program Management

The contractor shall identify the Program Manager responsible for all efforts under this contract. The Program Manager shall be the main point of contact for all issues.

3.2.2 Quality

The contractor shall provide program management support to ensure all performance on the contract is planned, coordinated, controlled, monitored, managed, and reported consistent with International Organization for Standardization (ISO) ISO 9001 standards or equivalent. The contractor shall maintain effective control of quality of work, perform standard factory quality inspections, examinations and tests necessary to demonstrate conformance to contract requirements and shall only deliver products that conform to contract requirements. The contractor is responsible for ensuring that all deliverables as part of this contract meet all technical and quality requirements set forth in the contract. The ASQC Q9001:2008 may be used as a reference.

3.2.3 Configuration Management

The contractor shall maintain a Configuration Management Plan of which the Government reserves the right to review. The contractor’s configuration management applies to pre-production assets and is in accordance with ISO9001 standards, or equivalent. This is to assure the configurations of assets meet the form-fit-function capability requirements during design and development. The contractor shall use Surveillance and Reconnaissance Systems Division Configuration Management Plan (CMP) document number # NSWCCR-4130-JXT-13-002, as guidance. The government reserves the right to make no cost impact redlined drawing changes as necessary. All redlined drawing changes will be provided by the Government technical point of contact identified in the contract. The contractor shall provide As-Built Configuration lists to the Government per CDRL A011, and as required by each DO/TO. (CDRL A011, As-Built List)

3.2.4 Environmental/Safety

The contractor shall ensure that all performance and deliverables on this contract meet all environmental, health, and safety requirements of the Environmental Protection Agency (EPA), Occupational Safety and Health Administration (OSHA), and local, state, and federal regulations. Additionally, all performance and deliverables must be in compliance with DoDD 4715.1E, DoDI 6055.11, MIL-STD-882D, MIL-STD-810G, IWTD JXT CM 09 001 Rev. 0 Performance Specification, and all DO/TO environment and safety requirements as applicable. The contractor shall ensure assigned personnel are adequately trained and qualified for the tasks performed on each DO/TO. Brief all personnel on the hazards involved with operations and applicable precautions to be taken. Should unidentified hazards arise, cease operations until actions are taken to eliminate or mitigate hazards to safe levels.

3.2.5 Marking

The contractor shall ensure that all prototypes, EDM, and Pre-production units meet the marking requirements of MIL-STD-130N as required by DO.

3.2.5.1 IUID

Any individually replaceable item with a value over $5,000.00 shall have a IUID type 2 label and shall be loaded into the IUID registry.

3.2.6 Progress Reports

The contractor shall provide progress status reports for each DO/TO as required. Progress reports shall identify detailed contractor performance on the contract, build and delivery schedules, as well as shipment status per CDRL A012. The delivery schedules for progress reports will vary per DO/TO requirements, but will not be less than once per month for both, the basic contract and the active DO/TOs. The Prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports, if applicable. (CDRL A012, Contractor’s Progress, Status, and Management Report)

3.2.7 Meetings

3.2.7.1 The contractor shall host and conduct a kickoff meeting at the contractor’s integration facility as required per DO/TO. At the kickoff meeting, the contractor shall present component lead times, build schedules, technical concerns, planning, potential issues, and other pertinent information. An estimated time for meeting is between 7 and 30 calendar days after delivery order award. Prior to the kickoff meeting, the contractor shall provide a meeting agenda per CDRL A013 to the Government Technical Point of Contact. After the kickoff meeting, the contractor shall provide meeting minutes per CDRL A014, and a copy of the presentation materials per CDRL A015 to the Government Technical Point of Contact. (CDRL A013, Conference Agenda) (CDRL A014, Conference Minutes) (CDRL A015, Presentation Material)

3.2.7.2 The contractor shall provide representatives for all Local Control and Configuration Board (LCCB) meetings sponsored by the Government.

3.2.7.3 The contractor shall host and conduct a final closeout meeting, within 7 calendar days before the end of the DO/TO period of performance. The contractor shall ensure that appropriate personnel are available for the meeting to address agenda items. The Physical Configuration Audit (PCA) shall be conducted at the closeout meeting or as directed per DO/TO. Prior to the closeout meeting, the contractor shall provide a meeting agenda per CDRL A013 to the Government Technical Point of Contact. After the closeout meeting, the contractor shall provide meeting minutes and a copy of the presentation materials per CDRL A014 to the Government Technical Point of Contact. (CDRL A013, Conference Agenda) (CDRL A014, Conference Minutes)

3.2.7.4 The contractor shall attend various informational meetings to provide technical expertise as required by DO/TO. Contractor personnel attending each meeting shall have the proper level of clearance, up to and including SECRET on file with the Government.

3.2.7.5 Design Reviews

The contractor may host design presentations of the engineering & technical support process and outputs. This may include in-process presentations and final presentations.

3.3 Engineering Change Proposal (ECP)

The contractor shall implement all changes to the Product Base Line (PBL) and Bill of Materials (BOM) via the ECP process as described in the Surveillance and Reconnaissance Systems Division CMP document number NSWCCR-4130-JXT-13-002. The contractor shall submit all ECPs to the Government to review for approval, per CDRL A016. Preparation of ECPs shall be accomplished IAW Surveillance and Reconnaissance Systems Division Configuration Management Plan, document number NSWCCR-4130-JXT-13-002. (CDRL A016, Engineering Change Proposal)

3.3.1 Class I ECPs

Class I ECPs shall be defined as any change to the product baseline which affects form, fit, or function. All Class I ECPs shall be tracked to the unit part number and serial number affectivity. The contractor shall submit Class I ECPs to the Government within a minimum of 14 calendar days prior to proposed execution date of the ECP per CDRL A016. The Government shall review each Class I ECP submitted and provide concurrence or non-concurrence through the Contracting Officer with the Government’s assessment that the change is a Class I change within 10 calendar days of receipt. The contractor shall not implement any changes prior to receipt of Government concurrence. All risk will be the burden of the contractor for implementation of any changes prior to receipt of Government concurrence. (CDRL A016, Engineering Change Proposal)

3.3.2 Class II ECPs

Class II ECPs shall be defined as any, which does not meet the definition of a Class I ECP. Class II ECPs shall be tracked to serial number effectively. The contractor shall submit Class II ECPs to the Government within a minimum of 14 calendar days prior to proposed execution date of the ECP per CDRL A016. The Government will review each Class II ECP submitted and provide concurrence or non-concurrence through the Contracting Officer with the Government’s assessment that the change is a Class II change within 10 calendar days of receipt. The contractor shall assume risk for implementation of changes prior to notification of Government concurrence. (CDRL A016, Engineering Change Proposal)

3.3.3. Deviations and Waivers

Deviations and Waivers are all changes affecting (as a minimum) form, fit, function, reliability, cost and maintainability for hardware/software/firmware. The contractor shall submit to the Government for review, all requests for Deviations (RFD) in accordance with CDRL A017, and all requests for Waivers (RFW) in accordance with CDRL A018. (CDRL A017, Request for Deviation) (CDRL A018, Request for Waiver)

3.4 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The contractor shall be responsible for managing obsolescence over the entire period of the contract to ensure compliance with all performance and contract requirements.

3.5 Government Furnished Equipment (GFE) Asset Tracking

The Government will provide hardware as identified per DO/TO. The contractor shall have sufficient bonded storage facilities to accommodate all GFE identified. The Contactor shall manage and track the status of GFE inventory by serial number and part number, and provide a monthly asset tracking log to the Government per CDRL A019. The contractor shall return GFE to the Government as required per DO. (CDRL A019, Government Property Physical Inventory Count or Custodial Balance Report)

3.6 Government Furnished Information (GFI)

When the contractor has a requirement for special or specific Government information in addition to what is listed in this SOW and the DOs/TOs, the contractor may identify and request GFI in writing to the Technical Point of Contact, which may be provided at the Government’s discretion. All GFI shall be destroyed by the contractor within 30 calendar days of end of delivery order period of performance in accordance with the destruction notice, and proper Security Regulations for Destruction of Classified Information identified in DD 254. The contractor shall provide all GFI inventory status to the Government per CDRL A019. (CDRL A019, Government Property Physical Inventory Count or Custodial Balance Report)

3.7 Government Furnished Material (GFM)

The Government will provide selected components as GFM. GFM will be provided in accordance with DO’s as required. The contractor shall have sufficient bonded storage facilities to accommodate all GFM identified. Sufficient is defined as a minimum of 100 sq. ft. up to 500 sq. ft. or larger. The Contactor shall manage and track the status GFM inventory by serial number and part number, and provide a monthly asset tracking log as appropriate, to the Government per CDRL A019. (CDRL A019, Government Property Physical Inventory Count or Custodial Balance Report)

3.8 Government Furnished Software (GFS)

The Government will provide selected components as GFS. GFS will be provided in accordance with DOs/TOs. The GFS will be maintained and updated with all changes that occur. The latest revision of software shall be submitted to the Government as required, throughout the period of performance of the Contract and/or DO/TO. The DOs/TOs will delineate the software requirements. The prime contractor and affiliated subcontractors are only authorized to use the GFS for performance on this contract, as required per DOs/TOs. The contractor shall ensure the GFS is appropriately protected and shall maintain software a tracking log per CDRL A019. (CDRL A019, Government Property Physical Inventory Count or Custodial Balance Report)

3.9 Counterfeit Parts and Materials. The Contractor shall implement procedures to minimize the risk of procuring and/or using counterfeit parts and materials. Counterfeit electronic parts may typically be used parts which have been refurbished and represented as new. These parts may or may not contain authentic die, and will often pass most if not all of the system performance requirements and data sheet parameters. However, the part reliability may have been compromised during removal, handling, or remarking, and a reduced life can be expected. Commonly counterfeited electronic parts include expensive parts such as microcontrollers or specially-screened devices, or common parts which have several pincompatible versions from multiple Original Component Manufacturers (OCM), such as memory devices and operational amplifiers.

Counterfeit mechanical parts are typically improperly made, marked, or treated products. Examples are improper anodizations or heat treatments (or falsified data), mismarked parts sold as a higher grade steel, or used/bogus parts such as valves or circuit breakers. As with electronic parts, counterfeit mechanical parts are significantly more likely to fail prior to the part's expected life.

Solicitations and subcontracts for all suppliers shall contain a requirement for procedures to minimize the risk of procuring and/or using counterfeit parts and materials. Refer to SAE AS5553 contains information regarding the detection, avoidance, and mitigation for guidance.

3.10 Trade Agreement Act

The contractor shall ensure TAA compliance where applicable.

4.0 Special Conditions

The following conditions apply to the contractor in the performance of the contract.

4.1 Travel

The contractor will be required to travel throughout the Continental United States (CONUS) and may be required to travel to locations Outside of the Continental United States (OCONUS) per DOs/TOs. All travel requests for contractor’s travel will be authorized by the Government Contracting Officer.

Subject to FAR/DFARS Part 31, the contractor will be reimbursed for travel costs (plus applicable burdens) including transportation, meals, and lodging at the actual amount incurred in direct performance of this contract. Travel costs, including per diem will be payable only when the contractor employee is in authorized travel status. Per diem rates shall not exceed the maximum amount permitted by the Joint Travel Regulations. The contractor will be authorized to travel upon receipt of a funded DO/TO AND authorization by the COR.

4.2 Facility

The contractor shall possess or be capable of possessing a sufficient integration facility to assemble a mobile surveillance system, such as a single axle trailer or truck bed platform. Sufficient floor space and minimum of a 15’ indoor ceiling to accommodate.

4.3 FunctionalTest Facilities

The contractor shall possess readily available access to test facilities including a 0.5 mile Line of Sight range for conducting extended long distance testing of hardware and technologies such as but not limited to radio communications and sensor target identification. Test facilities may be an outdoor range, air strip, or similar with an extended line of sight range (minimum of a half of a mile, 2,640 feet).

4.4 Frequency Allocation

The contractor shall obtain all Frequency Allocation Approvals by following the Joint Frequency Allocation-to-Equipment Process, or the “J-12 Process”. The contractor shall complete the DD 1494 Application for Equipment Frequency Allocation and submit the request for approval to U.S. Military Communications-Electronics Board (MCEB). The contractor must possess approval from the Joint Frequency Panel of the MCEB prior to performance on this contract when approval is required.

4.5 Defense Information Systems Network Responsibilities

Per CJCSI 6211.02D, the contractor shall obtain security approval by the Air Force GPS Joint Program Office (JPO) for Key Data Processor (KDP) Loading and Installation Facility (KLIF) prior to award of any DO under this contract.

4.5 Security

Contractor performance will require access to, and handling and storage of classified information, documents, and secure areas up to and including SECRET including transporting to/from meetings as required by each DO/TO. The contractor must possess a facility clearance and contractor personnel must possess the proper level of clearance up to and including SECRET, and have a Single Scope Background Investigation (SSBI) prior to access to classified information, documents, and secure areas. Access to classified information is limited to security clearance level and need to know. All classified information and material shall be handled in accordance with Government approved security practices and procedures including DoDD-5220.6, Defense Industrial Personnel Security Clearance Review Program. Contractor personnel in contact with classified information/documents/material/facilities and/or equipment shall have the proper level of clearance on file with the local Government Security Office. A Department of Defense Form 254 (DD 254) shall be filed with the contract. Classified information shall not be disclosed by the contractor, and must be protected by the contractor in accordance with DoD-5220.22-M, National Industrial Security Program Operating Manual (NISPOM) to fulfill the requirements of this contract. The Government will release Classified Information to the contractor for receipt and storage.

4.5.1 Security Program

The contractor shall appoint a Security Officer who shall (1) be responsible for all security aspects of the work performed under this contract, (2) ensure compliance with the National Industry Security Program Operating Manual (NISPOM, DoD-5220.22-M), and (3) ensure compliance with any written instructions from NSWC Crane Security Officer.

4.5.2 Personnel Security

Contractor and Subcontractor personnel assigned work under this basic contract and subsequent delivery orders shall as a minimum be U.S. Citizens and have a valid SECRET clearance as required.

4.5.3 Government System Access

The contractor may require access to classified information systems when at Government locations. This includes access to the following classified information systems, SIPRNET and JWICS. The contractor shall possess and is responsible for maintaining the ability to access command/organizational email, web sites, portals, etc. The contractor shall possess and is responsible for maintaining the ability to obtain computer seats via Naval Marine Corps Intranet (NMCI) and to obtain Common Access Card (CAC) badges for personnel and Subcontractors as required.

4.5.4 Government Facility Access

Access to SECRET facilities at Government and other contractor facilities may be required in the execution of the SOW as required by each DO/TO. The ability to store SECRET is required for the duration of the contract.

4.5.5 Classified Storage

The contractor shall provide Government approved containers for storage of classified material up to SECRET level. All classified contents are the property of the U.S. Government, and shall be protected during performance on this contract, and immediately returned to the proper technical Government representative as requested by the Government – or upon completion of this contract, whichever occasion happens first.

4.5.6 Special Compartment Information Facility (SCIF)

The contractor may be required to have a SCIF or dedicated access to SCIF, exclusive of the Government provided SCIF access. Requirement for a SCIF will be identified six (6) months prior to need or activation date. The contractor shall provide facilities for personnel and equipment predominately involved in processing and handling of classified data/information/documents/equipment when specified in a DO/TO.

4.5.7 Other Security Considerations

The contractor shall comply with any and all other special security requirements that are addressed in individual DO/TOs.

4.6 Information Non-Disclosure

The contractor shall not disclose any information/material/documents provided or developed under this contract outside of the Government without prior approval from the appropriate Government Contracting Officer. The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID’s, passwords, or other knowledge they may have gained, to anyone who is not authorized by the appropriate Government Contracting Officer. Non-disclosure applies to unclassified, sensitive unclassified, and classified information. The contractor shall comply with DoDI 8582.01 Security of Unclassified DoD Information on Non-DoD Information Systems, and shall abide by Directive-Type Memorandum 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems and implement the applicable information safeguards if the contractor stores or processes DoD information on a Non-DoD information system.

4.7 Release of Information

All technical data provided or obtained by the contractor shall be protected from the public. All other information relating to the items to be delivered and services to be performed may not be disclosed by any means without prior written approval from the appropriated Government Contracting Officer. Dissemination or public disclosure includes permitting access to such information by foreign nationals or by any other person or entity, or publication of technical or scientific papers, or advertising, or any other proposed public release. The contractor shall provide adequate protection to such information so as to preclude access by any person or entity not authorized to have such access.

Data Deliverables All data deliverables provided by the contractor shall be UNCLASSIFIED per the following:

Seq. No Data Description DID NO (CDRL A001, Technical Report – Study/Services) 3.1.1, 3.1.4 (CDRL A002, 3D Mechanical Drawings) 3.1.2 (CDRL A003, Software) 3.1.3 (CDRL A004, Test Report) 3.1.4, 3.1.5 (CDRL A005, Information Assurance Test/Eval of Government Hardware/Software) 3.1.4, 3.1.5 (CDRL A006, Preliminary Functional Verification Test Procedure/Report) 3.1.6, 3.1.7

(CDRL A007, ATP) 3.1.9

(CDRL A008, ATR) 3.1.9

(CDRL A009, Technical Manual Research and Analysis Source Data) 3.1.10 (CDRL A010, Course Conduct Information Packet) (CDRL A011 As-Built Configuration List) 3.2.3 (CDRL A012, Contractor’s Progress, Status, and Management Report) 3.2.6 (CDRL A013, Conference Agenda) 3.2.7.1, 3.2.7.3 (CDRL A014, Conference Minutes) 3.2.7.1, 3.2.7.3 (CDRL A015, Presentation Material) 3.2.7.1 (CDRL A016, Engineering Change Proposal) 3.3, 3.3.1, 3.3.2 (CDRL A017, Request for Deviation) 3.3.3 (CDRL A018, Request for Waiver) 3.3.3 (CDRL A019, Government Property Physical Inventory Count or Custodial Balance Report) 3.5, 3.6, 3.7, 3.8