N68936-14-R-0001.pdf

CODE

(Hour)

PAGE(S)

until 11:00 AM local time 24 Mar 2014

X

A X B X C X D

EX

X

G F 56 - 62

63 - 78 X H 79 - 86 kelley.mcclean@navy.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

DO-C9 1 86

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N68936 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 0 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

See Page 2 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

KELLEY A. MCCLEAN (760) 939-8638

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

4 - 15 16 - 17

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

18 - 19 20 - 21

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 22 - 26 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 27 - 36 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

37 - 54

PART II - CONTRACT CLAUSES

CDR NAWCWD CODE 254100D

ATTN: K. MCCLEAN

(760) 939-8638

429 E BOWEN RD - STOP 4015

CHINA LAKE CA 93555-6108

(760) 939-8638

(760) 939-0528FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

06 Feb 2014

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N68936-14-R-0001

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Name: Kelley McClean Phone: (760) 939-8638

DSN: 437-8638

FAX: (760) 939-0528

Email address: kelley.mcclean@navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE 254100D (K. McClean – 760-939-8638)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc):

COMMANDER

CODE 254100D (K. McClean)

NAVAIRWARCENWPNDIV

BLDG 982, MAIL STOP 4015

CHINA LAKE, CA 93555-6108

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 30 Each IETS Prototypes/Systems

CPFF

Delivery and fielding of IETS prototypes/systems that are based upon or derived from the CGS package of software and related hardware components deployed in the DCGS family of Programs IAW Section C SOW. Requirements will be specified in individual delivery orders. This is a CPFF (Completion) type CLIN.

The Independent Government Costs Estimate including burdens and fixed fee for this CLIN is $45,044,669.00 for all orders placed against all awards combined.

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

ITEM NO SUPPLIES/SERVICES AMOUNT

0002 Contract Data Requirements Lists (CDRLs)

NSP

In Accordance with form DD1423

Section C - Descriptions and Specifications

STATEMENT OF WORK (SOW)

HEADER

The scope of this Statement of Work in its entirety applies to requirements to be delivered against CLIN 0001. Data requirements to be delivered in connection to CLIN 0002 will be specified in the individual orders.

INTELLIGENCE EXPLOITATION AND TARGETING SYSTEMS STATEMENT OF WORK

Development and Fielding of Intelligence Exploitation and Targeting Systems (IETS)

1.0 BACKGROUND

The Mission Engineering and Interoperability (MEI) Division (41R100D) in the Systems Engineering Department (410000D) at the Naval Air Warfare Center Weapons Division (NAWCWD), China Lake, CA manages the Joint Common Geo-positioning Services 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 Navy (DCGS-N) Program under the direction of the Program Executive Office for Command, Control, Communications, Computers and Intelligence (PEOC4I), the 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), the Unmanned Aircraft Systems Project Management Office (PMUAS) in the Army Program Executive Office for Aviation (APEOA), the Office of Naval Research (ONR), the Office of Naval Intelligence (ONI), the Office of the Under Secretary of Defense for Acquisition, Technology and Logistics (OUSD(AT&L)) the National Geo-spatial Intelligence Agency (NGA), the National Reconnaissance Office (NRO), and 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 MEI Division 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.2 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., PMA-201, PMA-265, PMA-281 and PMA-290) and NGA systems deployed in Combatant Command (COCOM) operations centers and Joint Intelligence or Analysis Centers (JIC/JAC).

The contractor shall deliver IETS or components in accordance with orders issued under the contract. The contractor shall 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. It is anticipated that approximately 80-90% of the orders will require the contractor to produce and deliver new or upgraded IETS or components.

The contractor shall 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. It is anticipated that approximately 10-20% of the orders will require delivery of analysis reports.

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 Delivery 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 Delivery Orders. The following list is a sample of applicable documents and technical material that may be included in Delivery Orders.

2.1 Department of Defense Directives and Instructions

a. CJCSI 6212.01F Interoperability and Supportability of Information Technology and National Security 21 March 2012 Systems

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

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

d. DoDD C-5200.5 Communications Security (COMSEC) 22 Apr 2008

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

f. DoDI 8510.01 DoD Information Assurance Certification and Accreditation Process (DIACAP) 28 Nov 2007.

2.2 Department of Defense Standards

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

b. MIL-STD-2500C National Imagery Transmission Format Version 2.0 for the National Imagery

Notice 1 Transmission Format Standard

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

2.3 Additional Government Documents

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

2.4 Industry Standards

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,” May 12, 2003, Certified Current as of November 20, 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” December 8, 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” Mar 8 2002

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 http://www.whitehouse.gov/omb/circulars_a130_a130trans4

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

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

d. Department of Defense Web Policies and Guidelines http://www.defense.gov/webmasters

e. NAVAIR CIO Website (NAVAIR specific policy and guidelines https://mynavair.navair.navy.mil/portal/server.pt/community/dcio_applications_integration___business_int elligence_%287_2_2%29/1491/web_enablement/57583

2.5.3 Information Assurance (IA)

NAVAIR’s Information Assurance (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 shall 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, July 31, 2009

b. (Chairman of the Joint Chiefs of Staff Instruction) CJCSI 3170.01H (series), “Joint Capabilities Integration and Development System”, 10 January 2012

c. CJCSI 6211.02D (series) – “Defense Information System Network (DISN) Responsibilities,” 24 January

d. CJCSI 6212.01F (series) – “Net Ready Key Performance Parameter (NR KPP),”21 March 2012

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 – Chapter 7 “Acquiring Information Technology, Including National

Security Systems,”; Section 7.5 “Information Assurance (IA)”

h. DoD 5220.22-M, “National Industrial Security Program Operating Manual,” February 28, 2006 (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,” February 10, 2009

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. DoDD 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

m. DoDD 8570.01 “Information Assurance Training, Certification, and Workforce Management,” August 15, 2004, Certified Current as of April 23, 2007

n. DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

o. DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

p. DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP),”

November 28, 2007

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

r. DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

s. DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

t. DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the Department of

Defense,” June 8, 2010

u. DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum 02-10

Information Assurance Policy Update for Platform Information Technology,” 26 April 2010

v. (National Security Telecommunications and Information Systems Security Policy) NSTISSP No. 11, “Revised Fact Sheet National Information Assurance Acquisition Policy,” July 2003

w. (Office of the Chief of Naval Operations) OPNAV INST 5239.1C, “Navy Information Assurance (IA)

Program,” 20 Aug 08

x. SECNAV M-5239.1, “Department of the Navy Information Assurance Program; Information Assurance

Manual,” November 2005

y. SECNAVINST 5230.15, “Information Management/Information Technology Policy for Fielding of

Commercial Off the Shelf Software,” 10 April 2009

z. SECNAVINST 5239.3B, “Department of the Navy Information Assurance Policy,” June 17, 2009

aa. SECNAVINST 5239.19, “Department of the Navy Computer Network Incident Response and Reporting

Requirements,” 18 March 2008

2.5.4 Contractor Networks and Connections

a. 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 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.0 REQUIREMENTS

Within the Scope described in 1.2 above, Delivery Orders will require the contractor to perform the following RDT&E 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. Systems engineering tasks may be conducted to help the Government understand and evaluate proposed or evolutionary IETS hardware or capabilities without any follow-on development or software integration or planned requirements for CGS within or external to those systems. Systems engineering or analyses may also be 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 Briefings (CDRL A004, 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. These studies may show that the addition or integration of a proposed capability is not feasible or cost-effective given certain constraints, or suggest that a requirement will not serve to enhance existing capabilities of the current IETS. 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 Technical Reports (CDRL A004, A005) and the ongoing status of these activities will be reported in the monthly reports (CDRL A001). These tasks will provide data and information that the Government may or may not use in future IETS developments.

3.1.2 Technical Briefings and Demonstrations

The contractor shall deliver technical briefings that describe IETS developed under a delivery order, and provide demonstrations of those systems. These will consist of executive briefings at the contractor’s site, briefings at Navy training or intelligence centers, briefings to visiting dignitaries, acquisition program offices, and at design review meetings, and/or symposia when approved by the Government. Content of these briefings and descriptions of demonstrations will be provided to the government for review as specified during Delivery Order performance and prior to delivery to any audience outside NAWCWD. (CDRL A004, A005).

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 Delivery 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 a Delivery 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 review presentations (CDRL A004) shall be provided at least 1 week prior to each event. Results of reviews will be reported (CDRL A003, A004) and in the appropriate SRDD (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 Delivery 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 SRDD (CDRL A008) and/or Software Version Description (SVD) (CDRL A00C) in addition to documents required for a particular Delivery Order that may be subject to 2.1(f). Delivery 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 Image Product Library (IPL) or its iStore variant, 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 will need to 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 Delivery Orders. The contractor will 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 Delivery Orders (CDRL A00D).

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, makefiles, 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 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 will 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). Documentation on the design, attributes, a priori factor analysis, limitations, and implementation will also be provided as part of the software end item delivery that will include source code and makefiles (CDRL A006, A00A).

3.3.2 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, such as the DCGS Integration Backbone (DIB). Delivery 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.

3.3.3 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 National Geospatial-Intelligence Agency (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 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). 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.4 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, makefiles, 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.5 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), 3D Active Targeting (3DAT) supporting the use of LIDAR data sources, and the NGA validated auto-registration capability. Software, including source code, makefiles, build instructions, associated libraries, and/or utilities will be delivered on electronic media suitable for installation, compilation, and use on government systems (CDRL A006, A00E).

3.3.6 System Testing and Verification

Delivery 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 will be provided in a Test Report (TR) (CDRL A00J, which will contain the results of all tests described in the Test Plan (CDRL A00H). Compilation of the TR 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 may observe or participate in the SAT activities at the request of the Government, but may also be excluded from Government-only test procedures. Results of SAT activities will be provided by the Government to the contractor for inclusion in the final TR (CDRL A00J).

3.3.7 System and Software Configuration Management (CM)

The contractor shall perform CM activities specified in Delivery 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, 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 or Military facilities. This work shall consist of providing installation instructions, briefings, and/or guidance based upon lessons learned from FAT, SAT or prior installation activities in a User Manual (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 delivery orders, but may include PEO (C4I) facilities, NAVAIR facilities, or those associated with other Combat Support Agency Programs. Results of these activities shall be reported in monthly status reports (CDRL A001) and training materials (CDRL A00F, A00G).

3.5 Training Documentation and Material

The contractor shall conduct training classes and provide training documentation as required on specific Delivery 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 documentation (CDRL A00G) will be provided as part of the standard software release documentation or IETS operation manual (CDRL A00E, A00F).

Training classes will be scheduled under Delivery Orders depending upon the needs of the Services and their DCGS Programs. The contractor may need to 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 may be 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 will 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 a monthly Sustaining Engineering Activity Report (SEAR) document (CDRL A005).

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 SEAR (CDRL A005).

4.0 DELIVERABLES

4.1 Delivery Order Status and Financial Reports

The contractor shall provide monthly progress, status and financial reports. Delivery order progress and status reports shall be delivered along with monthly financial reports (CDRL A001, A002).

4.2 Technical Reports

The contractor shall provide technical reports and/or documentation as required by Delivery Order work statements on dates to be arranged after initiation of a task. The contractor shall provide meeting minutes and/or briefing materials (CDRL A003, A004) after completing a Program Management Review (PMR), Interim Design Review (IDR), Critical Design Review (CDR), Technical Exchange Meeting (TEM), and/or Test Readiness Review (TRR).

The contractor shall provide presentation materials or briefings (CDRL A004) that relate to information or data or testing, evaluation, demonstration or training as described in Section 3.0. Technical reports (CDRL A005) shall be delivered as required by specific Delivery Orders.

4.3 Computer Software

The contractor shall provide software for IETS in a format suitable for use on government computer systems (CDRL A006). Delivery orders aimed at updates to deployed systems may also require computer software products (CDRL A006) in a form suitable for compilation under a specific operating system or operational environment.

Requirements for software deliverables will be stated in relevant delivery orders, but all software delivered under the contract will become the property of the government and will not be burdened or encumbered by restricted data rights or intellectual property rights or commercial licenses unless specifically stated in the work statement issued before award of the delivery order. No proprietary or executable-only modules, i.e., without source code will be allowed or delivered as part of systems developed and/or delivered under the contract.

4.3.1 Commercial Software

Upon receipt of requests from Government Agencies, Programs, or Operational Units, the CGSP Team may issue a Delivery Order for the contractor to provide Commercial Off-the-shelf (COTS) software licenses and/or upgrade entitlements (UEs) for ELT and/or related plug-in COTS application products. These shall be purchased according to a price schedule that will be provided by the contractor upon receipt of a request for a quotation from the Government. Software and documentation or data items delivered under a Purchase Order or Delivery Order will be described and accounted for in the monthly PSR (CDRL A001).

4.4 Software Development Documentation

The contractor shall provide a Software Development Plan (SDP) (CDRL A007) for the contract that will be applicable to each delivery order requiring delivery of software. The contractor shall also provide standard software development documents that include Software Design Description (SDD) (CDRL A008), Interface Requirements Specification (IRS) (CDRL A009), and Interface Design Description (IDD) (CDRL A00A) products. Each final software product or end item delivery will be described in a Software Version Description (SVD) document (CDRL A00C) and updates or revisions to prior software deliverables will require modifications to existing government SDD, IDD, and/or SVD documents (CDRL A00D).

4.5 System Operator/User Documentation

The contractor shall provide user or operator documentation for IETS that are planned for deployment by a program or sustainment to an operational status. Documentation will include a Software User Manual (SUM) (CDRL A00E) and for IETS that include specific hardware, a Computer Operation Manual (COM) (CDRL A00F). The contractor shall provide Training Materials (CDRL A00G) for IETS that will be used during a demonstration or exercise or for rapid deployment.

4.6 Testing and Evaluation Documentation

The contractor shall provide testing and/or evaluation documentation. The contractor shall provide a system and/or software test plan (CDRL A00H) to support acceptance testing for a IETS or for completion of the delivery order, and the results of testing and evaluation will be provided in a test report (CDRL A00J).

4.7 Operations Security Plan

The contractor shall provide an Operations Security (OPSEC) Plan (CDRL A00K) as described in section 5.0 below.

5.0 SECURITY

Due to the classification levels of systems, documentation, locations, and intelligence sources associated with the tasks outlined herein, the Government requires the contractor to provide personnel with the appropriate security clearance levels for the work to be performed. Performance of work under this SOW will require access to Top Secret material and data and shall be in accordance with DoD 52220.22-M, National Industrial Security Program Manual (NISPOM) and applicable DoD Security regulations. The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW IAW with the DD Form 254 and the Contract. All contractor personnel shall possess a security clearance and need-to-know commensurate with the requirements of their positions. All deliverable products, reports, and media provided under the contract will be either UNCLASSIFIED or SECRET. Non-substantial access to TS/SCI will be required for access to planning, schedule, and documentation on national intelligence systems. Special clearances will also be required for access to the Storm Shadow Mission Planning Facility (SSMPF) in the UK and the Cruise Missile Support Activity (CMSA) sites in the US and UK.

The contractor shall comply with the information assurance requirements for accessing U.S. Government IT systems. The contractor shall adhere to the Department of the Navy’s (DON)s Information Assurance Program prescribed methodologies for the protection of information to support DON Missions.

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-

5510.36. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified information and materials.. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only in accordance with DoDM 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3) and DoD 5400.7-R (Freedom of Information Act Regulation) (Chapter 3).

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01(DoD Information Security Program: Controlled Unclassified Information (CUI)) Volume 4 (enclosure 3 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf and DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) available at http://www.dtic.mil/whs/directives/corres/pdf/540007r.pdf.

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement:

Distribution Statement D: Distribution authorized to the DoD and U.S. DoD contractors only, Test and Evaluation, 14 November 2012. Other requests shall be referred to Commander, NAWCWD, Attn: 41R100D, 1900 North Knox Road, Stop 6510, China Lake, CA 93555-6106.

In addition, all technical documents that are determined to contain export-controlled technical data shall additionally be marked with the export controlled warning statement in accordance with the SECNAV Manual 5510.36.

PUBLIC RELEASE: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release through Commander, Code 4L0000D, Naval Air Warfare Center Weapons Division, China Lake, California 93555-6100.

OPERATIONS SECURITY (OPSEC): The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

The contractor shall prepare an Operations Security Plan for government review in accordance with the CDRL (A00K) that will be applicable to all task orders issued under the contract.

6.0 NMCI

Any tools developed that will be hosted by NAVY MARINE CORPS INTRANET (NMCI) or run on NMCI workstations will be certified for NMCI by the Government to comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned by the Government to meet the requirements of the current NAVAIR Server Consolidation effort.

7.0 GOVERNMENT FURNISHED INFORMATION (GFI)

Due to the nature of systems, documentation, and intelligence sources associated with the tasks outlined herein, the Government may have to provide data, software, and other items to the Contractor in order to facilitate the work required. The Contractor is expected to identify and request GFI in response to requests for proposals for each Delivery Order. The Government may or may not be able to provide the GFI, which may impact the cost or time required to perform the work. These requirements will be negotiated with the Government for each delivery order.

Section D - Packaging and Marking

HEADER

The following clauses in Section D apply to CLIN 0001 IETS protoype/system deliveries:

5252.247-9508 5252.247-9509

The following clauses in Section D apply to CLIN 0002 CDRL deliveries:

5252.247-9507 5252.247-9514

5252.247-9507 PACKAGING AND MARKING OF REPORTS (NAVAIR) (OCT 2005)

(a) All unclassified data shall be prepared for shipment in accordance with best commercial practice. Classified reports, data and documentation, if any, shall be prepared for shipment in accordance with the National Industry Security Program Operating Manual, DoD 5220.22-M.

(b) The contractor shall prominently display on the cover of each report the following information:

(1) Name and business address of contractor.

(2) Contract Number/Delivery/Task order number.

(3) Contract/Delivery/Task order dollar amount.

(4) Whether the contract was competitively or non-competitively awarded.

(5) Name of sponsoring individual.

(6) Name and address of requiring activity.

5252.247-9508 PROHIBITED PACKING MATERIALS (NAVAIR) (JUN 1998)

The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hydroscopic or non-neutral material) is prohibited. In addition, loose fill polystyrene is prohibited for shipboard use.

5252.247-9509 PRESERVATION, PACKAGING, PACKING AND MARKING (NAVAIR)(JUL 1998)

(a) Preservation, packaging and packing shall conform to prevailing industry standards for the type of commodity purchased under this contract.

(b) All packages will be clearly marked with applicable contract number/delivery order number, and will contain appropriate packing slip. All deliveries will be marked for and/or consigned as follows:

**To be completed at award

(c) In the event of any discrepancy in material shipped (overage, technical rejection, damage), the contractor shall, immediately upon request of the Contracting Officer, furnish disposition instructions. Normally, such disposition instruction shall be a properly completed Commercial Bill of Lading, which includes, but is not limited to, the mode of shipment, routing, special handling, and so forth.

(d) If the contractor is required to install equipment upon delivery, then the contractor shall inform the Government of the date of shipment from the contractor’s facilities and the anticipated date of arrival at the site.

This report shall be made no later than the actual date that the shipment is made from the contractor’s facilities. The report may be made by facsimile or e-mail, to the point of contact listed in Section G. All transportation, rigging, drayage, packing, unpacking, and handling necessary to accomplish the installation shall be the responsibility of the contractor.

5252.247-9514 TECHNICAL DATA PACKING INSTRUCTIONS (NAVAIR) (SEP 1999)

Technical Data and Information shall be packed and packaged for domestic shipment in accordance with best commercial practices. The package or envelope should be clearly marked with any special markings specified in this contract (or delivery/task order), e.g., Contract Number, CLIN, Device No., and document title must be on the outside of the package.