N6893621R0004 Solicitation.docx

N6893621R0004

Section A - Solicitation/Contract Form

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Contract Specialist:

Name: Aretha Jones Phone: 760-939-4737 Email address: aretha.y.jones@navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE D223000 (Aretha Jones, 760-939-4737)

NAVAIRWARCENWPNDIV

1 ADMINISTRATION CIRCLE, STOP 1303

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc.):

COMMANDER

CODE D223000 (Aretha Jones, 760-939-4737)

NAVAIRWARCENWPNDIV

BLDG 02334, STOP 1303

CHINA LAKE, CA 93555-6108

Contracting Officer:

Name: Melinda Childs Phone: 760-939-1932

DSN: 437-1932

Email address: Melinda.childs@navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE D223000 (Childs, Melinda, 760-939-1932)

NAVAIRWARCENWPNDIV

1 ADMINISTRATION CIRCLE, STOP 1303

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc.):

COMMANDER

CODE D223000 (Childs, Melinda, 760-939-1932)

NAVAIRWARCENWPNDIV

BLDG 02334, STOP 1303

CHINA LAKE, CA 93555-6108

NOTE TO OFFERORS:

The Government is conducting a single competition which will result in a Multiple Award Contract (MAC) for the CLINs in Section B for IETS. Awards of contracts under the MAC are based on full and open competition. The Government estimates that multiple awards will be made under this solicitation. This estimate in no way prohibits the Government from making either fewer or more awards than estimated based upon the offers received and a determination of the best interests of the Government.

The not-to-exceed ceiling for the Multiple Award Contract is $49,873,700

The MAC awarded from this solicitation will be an Indefinite Delivery/ Indefinite Quantity (ID/IQ) type contract with the ordering period as set forth in Section F.

Section B - Supplies or Services and Prices

Hours

IETS Prototypes

CPFF

The contractor shall provide delivery and fielding of IETS prototypes/systems in accordance with the Statement of Work (SOW) in Section C of the solicitation. Requirements will be specified in individual orders. Total Level of Effort (LOE) Not To Exceed (NTE) 228,800 hours FOB: Destination

PURCHASE REQUEST NUMBER: 1300840791

PSC CD: AC13

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

Other Direct Costs (ODCs)

COST

The contractor shall provide travel, materials ODCs, and subcontractor effort in accordance with the Statement of Work (SOW). ODCs are non-fee bearing but may be burdened in accordance with the contractor's routine practices.

FOB: Destination

PSC CD: AC13

ESTIMATED COST

NSP

The contractor shall provide data in accordance with the Contract Data Requirements List (CDRL), DD Form 1423 and Exhibit A in Section J. NSP = Not separately priced.

Contractor Acquired Property (CAP)

COST

The contractor shall deliver all contractor acquired property no longer needed for performance of the contract.

ESTIMATED COST

CLAUSES INCORPORATED BY FULL TEXT

Title or Labor Category [Labor Occupation] (SOC #)

Section C - Descriptions and Specifications

STATEMENT OF WORK

INTELLIGENCE EXPLOITATION AND TARGETING SYSTEMS

STATEMENT OF WORK

Development and Fielding of Intelligence Exploitation and Targeting Systems

1. BACKGROUND

The Mission Engineering Division (D582000) in the Mission Engineering and Analysis Department (D582000) of the Naval Air Warfare Center Weapons Division (NAWCWD), China Lake, CA, manages the Joint Common Geo-positioning Services (CGS) Project (CGSP) Team, which investigates, analyzes, defines, and documents requirements for current Intelligence Exploitation and Targeting Systems (IETS) capability requirements. The CGSP provides the core CGS software and system capabilities required for accurate geo-location, image exploitation, precise target point mensuration, and targeting product generation for intelligence personnel in operational units and command centers of the Army, Navy, Air Force, and Marines Corps.

The CGSP has been supported by:

· The Distributed Common Ground System (DCGS) Navy (DCGS-N) Program under the direction of the Program Executive Office for Command, Control, Communications, Computers and Intelligence (PEOC4I)

· Air Force Air Combat Command (ACC) Intelligence, Surveillance and Reconnaissance (ISR) Operations Division (A2/O) and the Air Operations Center Weapon System (AOCWS) Program under the direction of the Air Force Life Cycle Management Center (AFLCMC)

· Office of Naval Research (ONR)

· Office of Naval Intelligence (ONI)

· Office of the Under Secretary of Defense (OUSD) for Acquisition, Technology and Logistics (AT&L)

· National Geo-spatial Intelligence Agency (NGA)

· National Reconnaissance Office (NRO)

· Various Joint and Coalition components.

Efforts of the team have resulted in the deployment of a common IETS capability to Army, Navy, Air Force, National Agency and Coalition operational units since 2006. In recent years, the CGSP has successfully completed IETS integration efforts with aircraft (F/A-18E/F, P-3C, and P-8A) and weapon system (Tomahawk, Storm Shadow) programs.

The NAWCWD CGSP Team has managed the development, testing, validation, and delivery of CGS-based Intelligence Exploitation and Targeting Systems (IETS) since 2005. The Naval Air Warfare Center, Weapons Division (NAWCWD), Research and Development Group, Mission Engineering & Analysis (MEA) Department anticipates future needs for computer software and system products to be used in the continued fielding of IETS components and systems by respective Service and Joint Programs.

1.1 Scope

Tasks described in this Statement of Work (SOW) focus on the development and fielding of IETS systems/prototypes related to future systems or the sustainment of deployed systems. It describes tasking requirements for continued delivery and fielding of IETS that are based upon or derived from the CGS package of software and related hardware components deployed in the DCGS family of Programs by the Army (DCGS-A), the Air Force (DCGS-AF), the Navy (DCGS-N) and the Marines Corps (DCGS-MC) as well as in intelligence training centers operated by each of the Services and operational installations worldwide. IETS requirements are also applicable to similar systems deployed by NAVAIR Program Manager for Acquisition (PMA) organizations (i.e., Precision Strike Weapons Program Office (PMA-201), Program Manager Air (PMA-265), Strike Planning and Execution Systems (PMA-281) and Maritime Patrol and Reconnaissance Aircraft (MPRA) program office (PMA-290)) and NGA systems deployed in Combatant Command (CCMD) operations centers and Joint Intelligence or Analysis Centers (JIC/JAC).

The contractor shall deliver IETS or components in accordance with each Task Order issued under the contract. The contractor will perform systems engineering analysis, software design and product reviews, system and software development, integration, testing, installation, operation, training, sustaining engineering and help desk technical assistance.

The contractor will perform technical studies and trade-off analyses, as well as evaluations of capabilities and requirements in supporting the definition of requirements and capabilities for future CGS-based IET systems and/or implementations.

Included in the delivery of these requirements will be the execution of management, scheduling, planning, monitoring, and reporting functions normally associated with CGSP objectives and Service Program requirements.

As identified in each Task Order issued under the contract, the contractor shall perform one or more of the Research, Development, Testing, and Evaluation (RDT&E) activities listed in Section 3.0.

2.0 APPLICABLE DOCUMENTS

Applicable documents and technical material (i.e. requirements documents, reference texts, specific design requirements, and other references) will be defined by individual orders. The following list is a sample of applicable documents and technical material that may be included in orders.

2.1 Department of Defense Directives and Instructions

a. CJCSI 5123.01G, Interoperability and Supportability of Information Technology and National Security Systems, 12 Feb 2015.

b. CJCSI 6510.01F, Chairman Joint Chiefs of Staff Manual Information Assurance (IA) and Computer Network Defense (CND), 9 Feb 2011.

c. DCI Directive 6/3, Director of Central Intelligence Directive Protecting Sensitive Compartmented Information within Information Systems, 5 June 1999.

d. DoDI 8523.01, Communications Security (COMSEC), 23 Apr 2008.

e. DoDD 5230.11, Disclosure of Classified Military Information to Foreign Governments and International Organizations, 16 Jun 1992.

f. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 28 July 2017.

2.2 Department of Defense Standards

a. Compendium of Controlled Extensions (CE) for the National Imagery Transmission Format (NITF) Version 2.1 STDI0002

b. MIL-STD-2500A, National Imagery Transmission Format Version 2.0 for the National Imagery Notice 3 Transmission Format Standard

c. MIL-STD-2500C, National Imagery Transmission Format Version 2.1 for the National Imagery Notice 2 Transmission Format Standard

2.3 Additional Government Documents

a. Community Sensor Model Working Group (CSMWG) Requirements Document V. 3.0, 2010-11-15

b. DoD Enterprise DevSecOps Reference Design V. 1.0, August 12, 2019

c. SPAWAR C2C24 Implementation Standard

2.4 Industry Standards

a. IEEE/EIA Std 12207 Information Technology – Software Life Cycle Processes

2.5 Information Technology Related Clauses for Statement of Work

2.5.1 Clinger-Cohen Act

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology. In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT).

a. DoDD Number 5000.01, “The Defense Acquisition System,” 31 August 2013

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” 7 January 2015

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” 13 July 2010

d. SECNAVINST 5000.2E, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” September 1, 2011 2,5,2 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. OMB Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised, https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/circulars/A130/a130revised.pdf

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04, https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-04.pdf

c. Section 508, Rehabilitation Act of 1973, https://www.section508.gov/

d. Department of Defense Web Policies and Guidelines, https://dodcio.defense.gov/DoD-Web-Policy/

e. US Navy CIO Website, DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators, https://www.doncio.navy.mil/ContentView.aspx?id=577

2.5.3 Information Assurance (IA)

NAVAIR’s IA Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. IA is required operationally throughout the DON. The DON CIO is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002.

All IA will be in compliance with the following listed instructions to include those referenced within the below listing:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, 1 Sept 2011

b. (Chairman of the Joint Chiefs of Staff Instruction) CJCSI 3170.01H (series), “Joint Capabilities Integration and Development System”, 31 Aug 2018

c. CJCSI 6211.02D (series) – “Defense Information System Network (DISN) Responsibilities,” 4 Aug 2015

d. CJCSI 5123.01G (series) – “Net Ready Key Performance Parameter (NR KPP),” 12 Feb 2015

e. CJCSI 6510.01F, “Information Assurance (IA) and Support Computer Network Defense (CND),” 9 February 2011

f. (Chairman of the Joint Chiefs of Staff Manual) CJCSM 6510.01B – “Cyber Incident Handling Program”, 10 July 2012

g. Defense Acquisition Guidebook (DAG)– Chapter 6 “Information Technology, and Business Systems,”; Section 2.2 “DoD Information Technology (IT) Acquisition”

h. DoD 5220.22-M, “National Industrial Security Program Operating Manual,” 18 May 2016 (NISPOM)

i. DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, 19 Dec 2005 (Incorporating Change 2, Feb 25, 2010)

j. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” 17 Mar 2016

k. DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

l. DoDI 8500.01, “Cybersecurity,” March 14, 2014

m. DoDD 8140.01 “Cyberspace Workforce Management,” August 11, 2015

n. DoDI 8330.01, “Interoperability of Information Technology (IT). Including National Security Systems (NSS),” May 21, 2014

o. DoDI 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT), ” July 28, 2017

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

q. DoDI 8551.01, “Ports, Protocols, and Services Management (PPSM),” May 28, 2014

r. DoDI 8580.1, “Information Assurance (IA) in the Defense Acquisition System,” July 9, 2004

s. DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the Department of Defense,” June 8, 2010

t. DoDI 5200.48, “Controlled Unclassified Information (CUI),” March 6, 2020

u. DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology,” April 26, 2010

v. Committee on National Security Systems (CNSS) Policy No. 11, National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology Products

w. (Office of the Chief of Naval Operations) OPNAV INST 5239.1D, “U.S. Navy Cybersecurity Program,” July 18, 2018

x. SECNAV M-5239.1, “Department of the Navy Information Assurance Manual,” November 1, 2005

y. SECNAVINST 5230.15, “Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software,” April 10, 2009

z. SECNAVINST 5239.3C, “Department of the Navy Cybersecurity Policy,” May 2, 2016

aa. SECNAVINST 5239.19A, “Department of the Navy Computer Network Incident Response and Reporting Requirements,” September 4, 2019

ab. SECNAV M-5510.36, “Department of the Navy Information Security Program”, July 12, 2019

2.5.4 Contractor Networks and Connections

Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract without approval from the NAVAIR Chief Information Office (CIO). The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

3. REQUIREMENTS

Within the Scope described in 1.1 above, Task Orders will require the contractor to perform the following IETS activities in support of the specific deliverables called for in each order.

3.1 Systems Engineering Analysis

The contractor shall perform systems engineering tasks including systems analysis, system functional decomposition, testing, and evaluation. The contractor shall also conduct analyses of system functions, requirements, capabilities, and performance. These evaluations may be in response to data calls from the Intelligence Community (IC) (NRO, NGA, National Security Agency (NSA), etc.), DOD Agencies and Commands (NAVAIR, OPNAV, USAF, USMC, etc.). Systems engineering tasks are conducted to help the Government understand and evaluate proposed or evolutionary IETS hardware or capabilities. Systems engineering or analyses are performed as initial phases of new or updated IETS development or revision tasks. Results of systems engineering studies and recommendations will be provided in Technical Reports (CDRL A005) and their status will be reported monthly (CDRL A001).

3.1.1 Technical Studies and Assessments

The contractor shall conduct studies and analyses tasks that will support IETS development and integration of CGS, or DCGS, or PMA related capability enhancements, based upon requirements documented by the Government or IETS requirements levied by external programs or user agencies. The Contractor shall apply expertise and understanding of currently deployed and developmental systems in tasks related to the development and integration of components or subsystems into the DCGS Family of Systems (FoS), Command and Control (C2) support systems, and Mission Planning FoS. Requirements for new technology integration or specific capabilities may necessitate some level of study and/or assessment prior to a recommendation for further software design or development effort. Results of these studies and analyses shall be provided in presentations and/or Technical Reports (CDRL A004, A005), and the ongoing status of these activities will be reported in the monthly status reports (CDRL A001). Any data and information developed from the studies and analyses may or may not be used in future IETS developments at the sole discretion of the Government.

3.1.2 Technical Reports, Briefings and Demonstrations

The contractor shall deliver technical reports (CDRL A005) that describe IETS’ development under an order, and provide demonstrations of those systems. Demonstrations shall include executive briefings. Demonstrations and briefings on technical reports may be presented at the contractor’s site, Navy training or intelligence centers, to visiting dignitaries, acquisition program offices, and design review meetings, and/or symposia when approved by the Government. Content of these briefings and descriptions of demonstrations shall be provided to the government for review as specified during order execution and prior to delivery to any audience outside NAWCWD. (CDRL A004, A005).

3.1.3 Product Chain Analysis

The contactor shall provide Product Chain Analysis (PCA)/Image Chain Analysis (ICA)/Kill Chain Analysis (KCA) in evaluations of current and proposed space-based, theater, and tactical ISR systems, focused on quality assurance of the ISR end products and capability gaps. The contractor shall use specifications and requirements documentation to generate performance predictions, review potential system capabilities, and to identify opportunities for insertion of advanced technologies or capabilities. The contractor shall apply PCA/ICA/KCA skills associated with system design, analysis, verification, and technical issues; such as calibration, anomaly resolution, performance assessments, and potential enhancements. The contractor shall also apply PCA/ICA/KCA expertise in evaluations of future ISR sensor trends; such as persistence, timeliness, wide area, multi-mode, and cross-platform collections, sensor cross-cueing, horizontal integration, and adaptable, scalable, modular, and open architected sensor architectures. Sensor trends shall be applied to study a broad range of targeting payloads, including standard weapons and hypersonic vehicles. PCA/ICA/KCA documentation shall be provided in briefings, white papers, or memoranda (CDRL A005), and/or provided in conjunction with monthly reports (CDRL A001) as directed by the Government.

3.2. Software Design and Product Reviews

The contractor shall conduct requirements analyses and perform software design in order to provide an updated version of, or updates to, the Software Requirements and Design Document (SRDD) for each IETS product related to a particular order. The contractor shall schedule and conduct Preliminary and/or Interim Product Design Review (PDR/IDR) and Final Design Review (FDR) meetings, as well as any Application Programming Interface (API) or Human Interface (HI) design reviews, as may be necessary for an order. These reviews will focus on program or user requirements for changes to existing IETS capabilities as well as planned functionality of new IETS capabilities. Draft read-ahead packages of the software design description (SDD) (CDRL A008) review presentations shall be provided at least one week prior to each event. Results of reviews will be reported in briefings and meeting minutes (CDRL A003, A004), and in the appropriate SDD, interface requirements specification (IRS), interface design description (IDD), and interface control document (ICD) (CDRL A008, A009, A00A, A00B).

3.2.1 Security Design and Accreditation Documentation

The contractor shall perform tasks in order to design and deliver software/systems in compliance with security requirements as identified in reference document 2.4(a) and shall ensure that all IETS delivered under orders can be accredited in accordance with 2.1(f). Tasks will include test and evaluation of IETS and documentation of software security issues relating to the design or final implementation. The contractor shall provide security risk assessments and other relevant security information deemed necessary to help the government integrate software modules into operational IETS. Security design issues, information assurance risk assessments, and mitigation strategies shall be included in the applicable SDD (CDRL A008) and/or Software Version Description (SVD) (CDRL A00C) in addition to documents required for a particular order that may be subject to 2.1(f). Orders may be issued for the purpose of conducting testing and providing documentation in order to obtain Authority to Operate (ATO) or Authority to Test (ATT) letters as required by the process described in 2.1(f) (CDRL A00H, A00J).

3.2.2 Interface Design, Updates and Documentation

The contractor shall perform tasks described in orders that require engineering design and documentation of interfaces between the IETS and relevant external systems, such as the Joint Mission Planning System (JMPS), the Joint Weaponeering System (JWS), the NGA iStore, the Geo-spatial Product Library (GPL) and the Joint Targeting Toolkit (JTT). CGS also supports the Tomahawk Command and Control System (TC2S) Targeting and Navigation Toolset (TNT) by providing an interface to the Pixel Database (PIXDB), the Digital Scene Matching Area Correlation (DSMAC) and Rapid Precise Point Measurement (RPPM) applications. The contractor shall provide software updates to the interface with the Target Model Preparation System (TMPS) for Storm Shadow Mission Planning. The contractor shall make updates and changes to the interfaces between CGS and the Joint Stand-Off Weapon (JSOW) and Surface Land Attack Missile Expanded Response (SLAM ER) mission planning capabilities. Interfaces that have been implemented for CGS-based IETS shall be maintained and/or changed to accommodate new capabilities or external system data format requirements. Interfaces, including XML schemas used by IETS, shall be described in Interface Requirements Specification (IRS) (CDRL A009), Interface Design Description (IDD) (CDRL A00A), and/or Interface Control Document (ICD) (CDRL A00B) as required by individual orders. The contractor shall provide updates to current or prior IDDs as necessary to assist the Government with its configuration management (CM) in synchronization with changes to the software under appropriate orders (CDRL A00D).

3.2.3 Architecture Design and Review

The contractor shall review potential architecture and design impacts resulting from potential migration of prototype system capabilities into the DCGS architecture and shipboard system networks that will be used by the Navy and Joint Forces. These tasks shall address DoD standards, communications, imagery, targeting, and mission planning activities that could impact the Navy, as well as support from other NAVAIR, OPNAV, DoD, and Intelligence Community (IC) offices. These tasks shall also address autonomous weapon planning assignment and targeting, and future precision targeting frameworks regarding intelligence, surveillance and reconnaissance (ISR), command and control (C2), mission planning and weapon planning systems across Navy PEO organizations. Navy integration with the Joint Requirements Oversight Committee (JROC)-approved joint systems, such as the JMPS, the Global Command and Control System – Joint (GCCS-J), the JTT, Global Information Grid (GIG), and Network Centric Enterprise Services (NCES) will be the focus of this task. Results of investigations shall be summarized in monthly reports (CDRL A001) and/or documented in technical reports (CDRL A005) during the period of performance.

3.3 Software and System Development, Integration and Test

The contractor shall perform software and systems engineering in order to deliver systems and components for fielding within existing or emerging programs. The contractor will also conduct testing and verification to establish functionality and detect deficiencies in developed software and/or systems. Software, including source code, make files, build instructions, associated libraries, and/or utilities developed under this contract will be delivered on electronic media suitable for installation, compilation, and use on government-owned computers (CDRLs A006, A00E, A00F).

3.3.1 Software Development Architecture

The contractor shall adhere to modern software development methodologies including Agile Software Development (unless a waterfall approach is specified), Cloud Computing, Automated Testing / Automated Security Testing, and Development, Security, and Operations (DevSecOps). The requirements as outlined and practiced in utilizing these methodologies shall enable the Navy’s emerging Compile to Combat in 24 hours (C2C24) implementation framework to transition to modern cloud-based containerized software solutions for Navy systems supporting warfighting, business, Navy Intelligence, and Enterprise information environment mission areas. This effort will support the Navy’s transformation of systems and portals into agile, secure and streamlined micro-web services using industry open standards and best practices by accelerating technology used by commercial industry and adaptation of commercial best practices for software modernization to speed capability delivery to the fleet.

3.3.2 Sensor Model Development

The contactor shall create new sensor model software or use existing sensor model software to adapt, modify, and deliver sensor models that can be used with CGS and/or other IETS applications or web services. Development and refinement of sensor model software will be applied to emerging and changing sensor systems that can be used in the exploitation and targeting processes and may require coordination and interaction with other national agencies and their contractors. Sensor models developed shall be as generic in design as possible to facilitate future re-use and/or adaptation for other sensors but must also be compliant with and usable by the NGA Mensuration Services Program (MSP). The contractor shall support National System for Geospatial-Intelligence (NSG) effectivity updates and coordinate integration and testing of CGS and IETS applications when emergent enhancements to the NSG architecture are developed and deployed. The contractor shall interface with all applicable NSG components and provide technical guidance to Navy’s program leadership. Documentation on the design, attributes, a priori factor analysis, limitations, and implementation will also be provided as part of the software end item delivery. The software end item delivery shall include source code with embedded developer comments, remarks, and annotations, and make files, build instructions, associated libraries, and/or utilities. The software end item shall be delivered on electronic media suitable for installation, compilation, and use on government systems (CDRL A006, A00A).

3.3.3 Application Programming Interface (API) Development and Documentation The contractor shall perform tasks that will yield updates to CGS and/or DCGS API software and documentation, which will facilitate integration of CGS and related software components with Commercial off-the-shelf (COTS) or Government off-the-shelf (GOTS) applications. Orders will address software development and documentation efforts to maintain the CGS and related DCGS APIs and/or provide Software Developer Kit (SDK) deliveries for use by developers of related applications and/or integrators of systems that may require DCGS and/or IETS related capabilities. Delivered API and SDK products will be maintained by the Government and made available to the Services, their DCGS Programs, or other related IETS development efforts within the DoD. API and/or SDK software and documentation shall be provided in accordance with (CDRL A009 and/or CDRL A00A) as directed by the Government.

3.3.4 Photogrammetric Algorithm Development

The contractor shall provide photogrammetric, geo-positioning, and error estimation/propagation algorithm development in order to improve the performance and/or reliability of current and proposed imagery intelligence (IMINT)-based targeting or related systems. Applications of interest are expected to include the sensor models previously provided by NGA through the MSP. Tasks may also address improvements to and/or integration with CGS and/or applications that may have integrated or embedded CGS capabilities. The contractor shall development new automated methods to reduce operational timelines including Automated Point Measurement, Automated rational polynomial coefficient (RPC) and replacement sensor model (RSM) generation, and Automated Image Resection techniques. Enhanced automated registration techniques will include automated terrain extraction or applying existing densely spaced digital elevation files (i.e, LiDAR) to the target area of interest. The contractor shall provide photogrammetric and technical evaluation reports on targeting capabilities and compliance with stated requirements. Recommendations and reviews will be documented in contractor formatted memoranda provided as attachments to monthly reports (CDRL A001) and/or individual technical briefings or reports (CDRL A004, A005) as directed by the Government. Documentation on the design, attributes, a priori factor analysis, limitations, and implementation will also be provided as part of the software end item delivery (CDRLs A006, A008, A009, A00A).

3.3.5 Validation Testing and Evaluation

The contractor shall make target point measurements, compile error statistics, and deliver sufficient and correct data to facilitate sensor model validation efforts with the NGA. The contractor shall integrate validated sensor models with CGS versions and other IETS applications for use in systems deployed by DCGS and other Programs. Results of validation and integration activities shall be summarized in monthly reports (CDRL A001). Software resulting from sensor model integration shall be delivered as software end items (CDRL A006).

3.3.6 Web Services and Distributed Systems Development

The contractor shall perform software development tasks for the delivery of web services and/or systems that support multi-INT (IMINT, SIGINT, MASINT, human intelligence (HUMINT), open source intelligence (OSINT) data collection, mission management, processing, exploitation, and dissemination. These software services and systems shall support the efforts of multiple echelons of command by utilizing existing and planned intelligence channels and systems. Software, including source code, make files, build instructions, associated libraries, and/or utilities, shall be delivered on electronic media suitable for installation, compilation, and use on government systems (CDRLs A006, A00E, and A00F).

3.3.7 Time Sensitive Targeting (TST) Systems Integration

The contractor shall perform software integration tasks and systems integration tasks in the development of IETS. These tasks will focus on client side designs including hand-held, laptop, and portable workstation configurations. The contractor shall develop capabilities to integrate multi-INT network services (e.g. web services) using multiple network/radio protocols (e.g. TCP/IP, UDP/IP, IXP, Link16, JTRS). Systems that are applicable for TST integration and/or software updates include the Targeting Analysis Workstation (TAW), the F/A-18 Distributed Targeting System (DTS), supporting the use of LIDAR data sources, and the NGA validated auto-registration capability. Software, including source code, make files, build instructions, associated libraries, and/or utilities, shall be delivered on electronic media suitable for installation, compilation, and use on government systems (CDRL A006, A00E).

3.3.8 System Testing and Verification

Orders will provide requirements for the contractor to perform software testing at the unit level and during integration of software components needed to exercise a new CGS version or IETS hardware update. Documentation of testing at the unit level will not be required, but documentation of testing after integration upon specific hardware of all included software components shall be provided in a Software Test Report (STR) (CDRL A00J), which will contain the results of all tests described in the Software Test Plan (STP) (CDRL A00H). Compilation of the STR will commence with the Test Readiness Review (TRR) and include the Factory Acceptance Test (FAT) results. The System Acceptance Test (SAT) will be conducted at NAWCWD facilities by Government and Military personnel after delivery of a completed IETS baseline product. The contractor shall observe or participate in the SAT activities at the request of the Government. Results of SAT activities will be provided by the Government to the contractor for inclusion in the final STR (CDRL A00J).

3.3.9 System and Software Configuration Management

The contractor shall perform CM activities specified in orders, which will include tracking of system and software versions, specific requirements for each version, and known issues, errors, or deficiencies identified for a particular version. The contractor shall use its change request (CR) and deficiency report (DR) tracking system and provide periodic CR/DR status reports (CDRL A005) at project management, design, or test readiness reviews. Upon delivery of IETS updates and/or new CGS versions and per the risk assessment processes identified in 2.5.3.o, the contractor shall document all existing CR/DRs and their severity in the SVD (CDRL A00C). The Government will use the SVD to understand the nature and severity of each CR/DR and establish priorities for implementing future updates or changes.

3.4 Installation and Operations Technical Assistance

The contractor shall provide installation and testing or operation of IETS at Government and/or Military facilities. In addition, the contractor shall provide installation instructions, briefings, and/or guidance based upon lessons learned from FAT, SAT or prior installation activities in a Software User Manual (SUM) (CDRL A00E). The contractor may also be required to provide hardware for software installation, checkout, and testing at activities related to operational assessment or evaluation testing of DCGS or IETS used by National Agencies. Requirements to provide technical assistance, IETS, and testing at other facilities will be specified in specific orders, but may include PEOC4I facilities, NAVAIR facilities, or those associated with other Combat Support Agency Programs. Results of these activities shall be reported in the monthly reports (CDRL A001), Computer Operations Manual (COM) (CDRL A00F), and training materials (CDRL A00G).

3.5 Training Documentation and Material

The contractor shall conduct training classes and provide training documentation as required on specific orders. Training is expected to cover each release of the CGS software, utilities, API/SDK updates, external interfaces to relevant DCGS applications, and completed IETS. Training Materials (CDRL A00G) shall be provided as part of the standard SUM or COM (CDRL A00E, A00F). Training classes shall be scheduled under orders depending upon the needs of the Services and their DCGS Programs. The contractor shall provide appropriate hardware systems for training at locations where permanent installation may be impractical. Training documentation or IETS operation manuals shall not contain any proprietary or copyrighted information. Training is required in OCONUS locations.

3.6 Sustaining Engineering

The contractor shall perform technical review activities that ensure the ongoing maintenance of existing IETS installations, users, and sponsor programs. These are expected to include attendance at planning and review meetings of DCGS Programs and other Service Agencies, presentation of briefings, technical papers, or memoranda at symposia related to current or future needs of the precision targeting, geo-spatial intelligence, or C4I communities. Meetings and associated memoranda may lead to recommendations and/or requirements for future IETS updates and may precipitate systems engineering or studies and analysis tasking as described herein.

Sustaining activities are necessary to ensure that IETS dependent upon CGS software remain viable in the operational arenas of precision targeting, imagery exploitation, and intelligence collection, processing, and dissemination. Deliveries in these areas by the contractor shall assist the Government in maintaining and sustaining the CGS capabilities and its continued support of IET system operational needs. Reports of sustaining activities will be contained in the monthly reports (CDRL A001).

3.7 Help Desk Technical Assistance

The contractor shall provide technical assistance support to the IETS and CGS user community through the maintenance of a website that can be accessed by Government and contractor personnel on a 24-hour and 7-days per week (24/7) basis. Support for commercial or non-Government personnel will be on a normal workday (8am-5pm Pacific) basis. The levels of effort applied to external and Government users shall be documented in logs of website activity and submitted with the monthly reports (CDRL A001).

3.8 Labor Qualifications

The following provides a description of the labor categories to support this effort.

3.8.1.1 The Contractor shall be responsible for employing personnel having at least the minimum level of education and training, experience, and security clearance as stated for each labor category specified herein.

3.8.1.2 College Degree. All degrees shall be obtained from an “accredited college or university” as recognized by the U.S. Department of Education.

3.8.1.3 Degree Majors. If specific field is required, the field is specified under the applicable labor category.

Technical disciplines: when used in relation to educational or work experience requirements, “technical discipline” shall mean a degree in the field of Computer Science, Computer Technology, Information Systems Management, Cybersecurity, Mathematics, Physical Science, Physics, Statistics, Engineering Technology, Information Technology, or Engineering.

Business disciplines: when used in relation to educational or work experience requirements, “business” shall mean any of the following specific subjects, disciplines or areas of work experience only: accounting, business, finance, law, contracts, purchasing, economics, industrial management, marketing, quantitative methods, or organization and management.

3.8.1.4 Technical Certification Training. If specific field is required, the field is specified under the applicable labor category.

3.8.1.5 Professional Level, Experience, and Education Level Definitions. Unless otherwise noted in the specific labor category description.

JUNIOR: A Junior level person is responsible for assisting more senior positions and/or performing functional duties under the oversight of more senior positions.

JOURNEYMAN: A Journeyman level person typically performs all functional duties independently.

SENIOR: A Senior level person typically works on high-visibility or mission critical aspects of a given program and performs all functional duties independently. A Senior level person may oversee the efforts of less senior staff and/or be responsible for the efforts of all staff assigned to a specific job.

Additionally, the following qualification substitution chart provides acceptable experience/education substitutions, unless otherwise noted in the specific labor category description.

“Years of experience” shall mean full, productive years of participation.

“Productive years” shall mean 52 weeks of work reduced by reasonable amounts of time for holidays, annual and sick leave.

If participation was part-time, or if less than one-half of the standard workweek was spent performing qualifying relevant functions, the actual time spent performing qualifying functions may be accumulated to arrive at full years of experience.

3.8.2 The following lists the minimum labor category education, experience, and security clearance requirements and the function descriptions for each labor category.

RFP Required Years of Experience, Standard

Functional Descriptions:

Task orders will specify labor categories, security level (Exempt, SECRET or TOP SECRET) and number of employees required to have the specified clearance levels. All Contractor personnel must have a minimum of an Interim SECRET and the ability to obtain a completed SECRET clearance at the time of task order award, unless exempted in the specific labor category description. Exempt labor categories do not require a DoD security clearance. For labor categories and task orders that require labor categories with a TOP SECRET clearance, the Contractor shall have up to 60 calendar days after task order award to get an Interim TOP SECRET security clearance, unless otherwise specified within the specific labor category or task order.

Service Contract Labor Standards:

This is not a Service Contract Labor Standards (SCLA) designated contract. The labor categories below do outline SCLA categories required for this effort and has been provided solely to locate the functional job descriptions for the labor categories as described by the Department of Labor’s Directory of Occupations. The McNamara-O’Hara Service Contract Act is not applicable to this contract in accordance with CFR Part 541 and wage determinations are not included as attachments.

3.8.2.1 Project Manager (SOC 11-1021)

Senior (SECRET)

Functional duties: Applies project principles to investigate, analyze, plan, design, develop, implement, test, or evaluate military weapon systems. Reviews and prepares project and technical analyses, reports, change proposals, and other technical documentation. Applies project experience to perform functions such as system integration, configuration management, quality assurance testing, or acquisition and resource management. Analyzes designs, develops, implements, tests, or evaluates automated data processing software related to engineering or functional requirements of military weapon systems, associated support systems, or management information systems. As the project manager for the contracted effort, ensure project procedures and controls are followed, manage manning and staffing project efforts, and lead problem resolution efforts. Interfaces with system or program Contractors, vendors, and Government representatives regarding the technical aspects of the programs/projects. Senior level person may oversee the efforts of less senior staff and/or be responsible for the efforts of all staff assigned to a specific job.

Required Education: BS or BA degree in Engineering, Computer Science or Information Systems.

Journeyman - Required Experience: At least five (5) years of experience in engineering management of a project in systems engineering, design or field service of Department of…