14-R-0007_RFP.pdf

CODE

(Hour)

PAGE(S)

until 08:00 AM local time 30 Jan 2014

X

A X B X C X D

EX

X

G F 37 - 47

X H 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)

1 47

(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 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 3 - 4

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT

PACKAGING AND MARKING

5 - 15

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

18 - 19

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 20 - 23

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 24 - 26 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

27 - 36

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

31 Dec 2013

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N68936-14-R-0007

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 MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 95,242 Each DASCAN and Related Capabilities

CPFF

The contractor shall provide the DASCAN and related capabilities in accordance with Section C Statement of Work.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

5252.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR)(DEC 2012)

(a) The level of effort estimated to be ordered during the term of this contract is 95,242 man-hours of direct labor including authorized subcontract labor, if any. The contractor shall not, under any circumstances, exceed one hundred (100%) percent of the total level of effort specified in this basic contract. The estimated composition of the total man-hours of direct labor by classification is as follows:

Labor Category Man-hours Total Man-hours

Chief Strategist* 1,810 Chief Technology Officer* 1,505 Product Development Manager* 4,475 Information Technology Integration Manager* 5,900 Information Assurance Officer 3* 2,245 Information Assurance Officer 1* 4,475 Information Technology Integration Engineer 1* 6,350 Information Technology Integration Analyst 3* 6,800 Information Technology Integration Analyst 2* 6,800 Information Technology Integration Analyst 1* 6,800 Systems Engineer 2* 3,120 Systems Enginner 1** 2,000 Systems Analyst 2** 8,000 Software Developer 3** 6,000 Software Developer 2** 16,000 Software Developer 1** 10,000 Administrative Assistant 3* 2,962 *- VA Labor Category 95,242

**- CA Labor Category

(b) FAR Clause 52.232-20, "Limitation of Cost" applies to fully funded orders and FAR Clause 52.232-22, "Limitation of Funds" applies to incrementally funded orders. Nothing in this clause amends the rights or responsibilities of the parties hereto under either of those two clauses. In addition, the notifications required by this clause are separate and distinct from any specified in either FAR Clause 52.232-20 or FAR Clause 52.232-22.

(c) In the event that less than one hundred (100%) percent of the established level of effort of the contract/order is actually expended by the end of the performance period, the Government shall have the option of:

(1) Requiring the Contractor to continue performance, subject to the provisions of the FAR Clause 52.232-20 or 52.232-22, as applicable, until the effort expended equals 100% of the established Level of Effort; or

(2) Effecting a reduction in the fixed fee by the percentage by which the total expended man-hours is less than one hundred (100%) percent of the established Level of Effort.

(d) The contractor agrees that effort performed in fulfillment of level of effort obligations under this contract shall include only verifiable effort in direct support of the work specified. It shall not include efforts such as work performed in transit to or from an employee's usual workplace, work during lunchtime activities, or effort performed at other non-work locations.

(e) In performing the contract/order, the contractor may use any reasonable combination of hours for the labor categories in support of section C of this contract/order.

Section C - Descriptions and Specifications

SOW

STATEMENT OF WORK

Development and Fielding of Command, Control, Intelligence, Surveillance, Reconnaissance and

Targeting (C2ISRT) Systems for Deployable Tactical Operations Center (TOC) Components

1.0 BACKGROUND

The Mission Engineering and Interoperability (MEI) Division (41R100D) in the Systems Engineering Department (410000D) of the Naval Air Systems Command (NAVAIR), Naval Air Warfare Center Weapons Division (NAWCWD) supports Department of Defense (DOD) Agencies and Military Programs by providing research, development, testing and evaluation (RDT&E), technical assistance and systems engineering in the development, testing, and fielding of future Intelligence, Surveillance, Reconnaissance, and Targeting (ISRT) systems. The MEI serves as a focal point for defining system requirements, system design and integration plans, prototype systems development, and testing and evaluation (T&E) for Programs and/or Agencies that field systems or components that support or use ISRT products. Tasks described in this Statement of Work (SOW) focus on systems engineering, development, testing, and fielding of components that will support Command and Control (C2) operations with unmanned fixed-wing Marines Corps (VMU) units providing ISRT information and capabilities and fixed-wing Marines Corps fighter/attack (VMFA) units for delivering weapons to accurate target points in a timely manner.

1.2 SCOPE

The contractor shall perform research, analysis, design, development, test and evaluation tasks in order to implement and deliver C2ISRT hardware and software components and systems that can be fielded in a US Marine Corps (USMC) TOC, or Command Operations Center (COC) environment. Prototype systems will be based upon analyses of requirements and fielded capabilities with known or documented limitations and/or technology demonstrations where deficiencies, shortfalls, or capability gaps may have been identified by the government.

Approximately 20% of the work anticipated will require analysis activities. Approximately 80% of the work will result in the contractor producing C2ISRT systems and components that will require the contractor to also provide some level of system demonstration, testing and training. As identified in each Delivery Order issued under the contract, the contractor shall perform one or more of the RDT&E activities listed in Section 3.0 Requirements of this Statement of Work in the delivery of required C2ISRT systems.

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 Systems,” 21 March 2012

b. Chairman Joint Chiefs of Staff Manual (CJCSM) 6510.01F, “Information Assurance (IA) and Computer

Network Defense (CND)”, 9 Feb 2011

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

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

Organizations,” 16 Jun 1992.

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 2.0 (STDI0002)

b. National Imagery Transmission Format Version 2.0 for the National Imagery Transmission Format

Standard (MIL-STD-2500C) through Notice 1

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

2.3 Additional Government Documents

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

2.4 Information Technology Related Clauses for Statement of Work

The Government will provide necessary reference documents not generally available to the Contractor. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any Information Technology (IT) equipment on behalf of NAVAIR in support of this Contract without a Naval Air Systems Command (NAVAIR) Command Information Officer (CIO) signed "IT" approval.

3.0 Requirements

The contractor shall conduct research and analysis on existing and emerging technologies, as described in section

1.2 Scope, in order to deliver appropriate design and development documentation. The contractor shall also conduct system development, integration, testing, and demonstrations to deliver C2ISRT components, modules, software, and systems through the performance of delivery orders. Specific types of activities to be performed are described in the following paragraphs.

3.1 Systems Engineering and Requirements Analysis

The contractor shall perform systems engineering analysis tasks including systems design studies, system functional decomposition, and identification of capabilities and limitations with respect to USMC C2ISRT requirements. The contractor shall also conduct analyses of system requirements, functions, capabilities, and performance. Systems engineering tasks may be conducted to help the Government understand and evaluate proposed or evolutionary capabilities without any follow-on development or software integration depending upon known USMC requirements for TOC/COC systems. Systems engineering or analyses may also be performed as initial phases of new or updated C2ISRT development or revision tasks. Results of systems engineering analyses, findings, and recommendations will be provided in Technical Briefings and/or Reports (CDRL A004, A005) and the status of their completion will be reported monthly (CDRL A001).

3.1.1 Operational Warfare Analysis

The contractor shall perform analyses of operational architectures with respect to the integration of new vehicles, sensors, and C2ISRT data into existing and future offensive and defensive TOC/COC system capabilities. These analyses will require evaluating warfare mission effectiveness through mission thread analyses, identifying data generation, display and distribution requirements, and documenting needs for operational air/ground movement simulation and visualization. Analyses will identify key operational deficiencies for which new technology and systems development may be needed (CDRL A004, A005).

Analysis activities will address: integrated air defense conducted in joint and independent USMC ground-based air defense operations; integrated offensive operations with air (VMFA) and ground operations with VMU sensor ISRT data collections; and time sensitive digitally-aided close air support (CAS) engagements. Capability analyses will provide traceability between operation analysis metrics and systems functional requirements and tactical deployment and/or field demonstration objectives. Systems analyses will provide traceability between capability functions and components and their required performance characteristics (CDRL A004, A005).

Analyses of defensive systems will include radar systems, close-in defense cameras and sensor systems, and C2 nodes. Analyses of offensive systems will include tactical air (TACAIR) systems (i.e., AV-8, F/A-18, and F-35), Joint Direct Attack Munitions (JDAM), ground-based (artillery, mortar, rocket) systems, coordinated time sensitive targeting (TST) and digitally-aided CAS systems; and C2 nodes, i.e., Forward Air Controllers (FACs).

3.1.2 Data Analysis, Interoperability, and Technical Studies

Data interoperability analyses shall address content generation, processing, and dissemination to the warfighter across limited capacity tactical communications. Analysis content will address the full range of C2ISRT data types:

full motion video (FMV), still frame and radar imagery, and their associated metadata, C2 systems tactical data, and mission planning and reporting data. The contractor may be required to deliver Department of Defense Architecture Framework (DoDAF) based architecture models of data flows between USMC TOC/COC systems and future TACAIR systems, e. g., F-35, in order to provide understanding of information exchanges, operational nodes and system-to-system interactions for land-based and afloat TOC/COC environments. Results of these analyses and technical studies 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).

3.1.3 Technical Briefings and Demonstrations

The contractor shall engage in technical exchange meetings with various external data producers and consumers in order to identify and define gaps in system designs and assess alternative solutions that will inform the requirements definition process. These will require the contractor to deliver technical briefings that describe the results of testing, research, analysis, integration, and/or demonstration tasks. These will consist of executive briefings at the contractor’s site, briefings at Navy or USMC training centers, briefings to official dignitaries, acquisition program offices, at design/delivery 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 A003, A004, A005).

3.1.4 Performance and Risk Analysis

The contractor shall conduct risk analyses and/or review performance analyses of C2ISRT systems provided by the government and provide documentation of results. Areas for analysis may stem from Fleet, Program Offices, or NAWCWD recommendations as to areas of risk for meeting future USMC TOC/COC system requirements. The contractor shall provide inputs to trade studies, analysis of alternatives (AoAs) and performance evaluations in an effort to assist NAWCWD with identification of potential prototype and operational developmental efforts for future C2ISRT systems. Results of this task will be documented in presentations (CDRL A004) and/or technical reports (CDRL A005) during Delivery Order performance.

3.2 System Design and Delivery

The contractor shall conduct systems design, development, integration, testing activities and systems delivery including rapid prototyping and advanced prototyping of systems. System designs will address TOC/COC processing, exploitation, dissemination (PED) and fusion of data from air, ground, fixed, mobile, manned, and unmanned ISR in support of target detection, classification, identification, and prosecution. PED capabilities must also address FMV, electronic warfare (EW), geo-spatial intelligence (GEOINT), and C2 situational awareness and direction. The Contractor shall apply expertise and understanding of currently deployed and developmental systems in tasks related to the development and integration of TOC/COC components or subsystems into the Dynamically Adaptive Secure Computer Area Network (DASCAN), the USMC Distributed Common Ground Station (DCGS- MC), and TACAIR (AV-8, F/A-18, or F-35) Family of Systems (FoS).

3.2.1 Architecture Design Review and Updates

The contractor shall review architecture and design impacts resulting from potential migration of prototype system capabilities into such products as the DASCAN, DCGS architecture, shipboard system networks and the TACAIR Family of Systems (FoS) that will be used by the USMC, Navy, and Joint Forces. These tasks will address application of DoD standards for communications, imagery and FMV PED, targeting, and mission planning activities that could impact USMC/USN operations, as well as support from other NAVAIR, OPNAV, DoD, and Intelligence Community (IC) offices. The scope of reviews will include the Joint Requirements Oversight Committee (JROC)-approved joint systems, e.g., the Joint Mission Planning System (JMPS), the Global Command and Control System – Integration of Imagery and Intelligence (GCCS-I3), the Joint Targeting Toolkit (JTT), the Global Information Grid (GIG), Network Centric Enterprise Services (NCES) and F-35 Mission Planning Systems.

Activities will be reported monthly (CDRL A001) and in Technical Reports (CDRL A004, A005) and/or meeting minutes (CDRL A003).

3.2.2 Interface Design and Documentation

The contractor shall review government provided documents on the definition, design, and validation of interfaces required by DASCAN, DCGS and other C2ISRT system components. The contractor shall report issues with ISRT system interface control documents (ICDs) and describe their potential impact on ISR product utility for targeting purposes. The contractor shall provide recommendations for interface design changes and potential ICD validation requirements in technical memoranda or briefings. The contractor shall develop and deliver interface requirements and design documents as well as ICD inputs for all prototype systems or software delivered under the contract

(CDRL A009, A00A, A00B, A00D).

3.2.3 System Design, Development and Implementation

The contractor shall perform system design and development tasks in order to implement hardware and/or software components, algorithms, or technology capabilities into prototype C2ISRT systems. Activities will include functional decomposition, requirements definition, resource allocation, integrated project build planning, and component specification. Prototype systems may include both hardware and software developed under other subtasks or provided by the Government. Systems may also require unique processing, display, or delivery mechanisms that require procurement or development. System design will be documented using drawings, block diagrams and/or appropriate design descriptions (CDRL A008). Interfaces will be described using requirement specification (CDRL A009) and design descriptions (CDRL A00A).

3.2.4 System Testing and Evaluation

The contractor shall test systems, components, and/or algorithms developed to evaluate concepts, performance and feasibility of integration with the USMC TOC/COC deployable systems. These systems may be discovered during reviews of candidate systems or segments that interface through DASCAN and its associated applications or to the DCGS, the Carrier Intelligence Center (CVIC), a Maritime Operations Center (MOC), or USMC COC installations.

The systems may contain updates and/or revisions to the DASCAN provided for testing during Weapons Tactics Instruction (WTI) events conducted at USMC or other military sites. The contractor shall document activities using test plans (CDRL A00H) and test reports (CDRL A00J), citing any capabilities and/or limitations discovered, while also evaluating potential improvements alternative technical approaches to relevant techniques or technologies. The contractor shall provide data inputs to NAWCWD (CDRL A004, A005) during government evaluations of C2ISRT systems, sensor payloads, communications, and ground station operations.

3.3 Software Development and Delivery

The development of C2ISRT systems will require software development in order to implement new capabilities that have the potential to make existing systems more usable or flexible as well as more effective. Activities will include integration of data flows and elements from imagery and/or FMV sources, signals intelligence (SIGINT) and other electronic intelligence (ELINT) or measurement and signature intelligence (MASINT) systems. Also, the integration of data flows and elements to/from TACAIR nodes and ground unit systems must be considered in order to make ISRT data available to weapon delivery 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 (CDRL A006, A00E, A00F).

3.3.1 Software Development and Documentation

The contractor shall provide a software development plan (SDP) for government review and approval before conducting software development activities under the contract (CDRL A007). The contractor shall follow the framework of DI-IPSC-81427A regarding SDP content, level of detail, and completeness. The SDP shall serve as the benchmark for the contractor’s software development efforts during delivery order performance. Any software delivered must be reusable by the government and must be compiled for execution on government-owned computer systems. The contractor will exercise best practices in conducting software development activities to deliver software to the Government without malicious code or proprietary, restricted data rights. All software delivered will be examined and analyzed for security accreditation purposes and may become integrated with deployed systems owned by the Government (CDRL A00C, A00D, A00E, A00F).

3.3.2 Software Design and Documentation

The contractor shall perform software design activities in order to provide an updated version of, or updates to, the Software Requirements and Design Document (SRDD) for each C2ISRT and/or DASCAN product related to a particular Delivery Order. The contractor shall schedule and conduct Preliminary and/or Interim 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 C2ISRT capabilities as well as planned functionality of new capabilities. Draft read-ahead packages of the software design review presentations (CDRL A004) shall be provided at least one week prior to each event. Results of reviews will be reported (CDRL A003, A004) and in the appropriate SRDD (CDRL A008, A009, A00A, A00B, A00D).

3.3.3 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 section 2.4.1 and shall ensure that all C2ISRT software delivered can be accredited in accordance with 2.1(f). Tasks will include test and evaluation of systems 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 systems. Security design issues, information assurance risk assessments, and mitigation strategies shall be included in the applicable SDD (CDRL A008) and/or System/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) certification letters as required by the process described in 2.1(f) (CDRL A00H, A00J).

3.3.4 Multi-INT Data Mining

The contractor shall perform software integration tasks in the development of C2ISRT systems to enable effective data mining across various multi-INT systems. These activities will focus on TOC/COC visualization tasks (i.e., spatial and temporal attributes) and server side database query, database mining, and access controls. The contractor shall provide the capability to mine local and network data sets across multiple heterogeneous data sources via interfaces to those sources and descriptions of the services to be provided in IDD (CDRL A00A) and/or ICD (CDRL A00B) documentation.

3.3.5 Multi-INT Data Integration

The contractor shall perform software integration tasks in the development of C2ISRT systems to support effective data integration within multi-INT TOC/COC environments. These activities shall focus on client side visualization tasks (i.e., spatial and temporal attributes) and server side database integration across multiple disparate data sources at potentially different points on the network (e.g. local, network, in-flight, in-transit). The contractor shall integrate multiple heterogeneous data sources in a coherent manner that is compatible with existing TOC/COC displays and emerging requirements and document those capabilities in user and/or operator manuals (CDRL A00E, A00F).

3.3.6 Time Sensitive Targeting (TST) Systems Integration

The contractor shall perform software and systems integration tasks in the development of TST system capabilities and interfaces to other systems, when applicable. Tasks will focus on new technology designs including laptop, tablet, and portable workstation configurations that can disseminate FMV and other ISRT information to the tactical edge and back to the TOC/COC commanders. 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, Link16, and Joint Tactical Radio System (JTRS) in order to disseminate TST information to remote networks and aircraft.

Capabilities delivered will be documented in design and interface documents (CDRL A008, A00A, A00B) and user or system operator manuals (CDRL A00E, A00F).

3.4 System Testing, Evaluation and Transition

The contractor shall perform DASCAN and C2ISRT system testing and evaluation according to a Government approved Software Test Plan (STP) (CDRL A00H) and document test results in a Software Test Report (STR) (CDRL A00J). Activities will include functional and performance evaluations of baseline TOC/COC systems and VMU ground station or shipboard components that are focused on transitioning to Programs of Record (PoR) in the DCGS-MC, VMFA, VMU, and C2ISRT communities. Evaluations will verify proper implementation of requirements, identify functional and performance requirements used to determine the suitability of candidate components for inclusion in a PoR system baseline. The contractor shall ensure that candidate systems have adequate test plans that can be incorporated into a Test and Evaluation Master Plan (TEMP) and shall perform execution of tests and experiments at government designated ranges or contractor facilities. Activities will be summarized in monthly reports (CDRL A001) and/or documented in technical reports (CDRL A004, A005).

3.5 Operations and Liaison

The contractor shall perform liaison tasks in order to interface and communicate with USMC personnel in the adaptation and/or integration of C2ISRT systems and/or software component services. Activities will include briefings for presentation at operational and training commands and communications with unit or installation personnel (CDRL A00G). The contractor may attend post-deployment intelligence debriefings that will allow interaction and coordination with fleet Integrated Product Teams (IPTs) and Operational Advisory Groups (OAGs).

The contractor shall conduct liaison activities between combatant unit commanders, VMU/VMFA operational commands and DOD program elements. Activities performed will be summarized in monthly reports (CDRL A001) and briefings (CDRL A004) that will be provided in electronic format (by electronic mail, if feasible) and/or as technical reports incrementally over the course of Delivery Order performance.

3.6 Training

The contractor shall provide government user or operator training documentation (CDRL A00F, A00G) and assistance on developed C2ISRT programs or application features, interfaces, or requirements. User training requirements for specific systems will be identified within the documentation deliverables required by specific Delivery Orders, but are expected to include briefing materials, user/operator instructions, system installation and administration documents (CDRL A00F, A00G).

4.0 Deliverables

All deliverables become the property of the United States Government. Unless otherwise stated, all deliverables will be submitted in both hardcopy and electronic media in Microsoft Word/PowerPoint/ Excel/Access/Visio/ or Project format. All deliverables must be submitted to the COR with notification to the contract specialist.

4.1 Monthly Report

The contractor shall submit a summarized monthly report (CDRL A001, A002), in contractor format, to include:

a. Task Status:

- Significant accomplishments during previous month;

- Recommendations related to the same,

b. Meetings attended/hosted

c. Status/results on previously identified problem areas

d. Impact on requirements (technical/cost/scheduling)

e. Products Provided / Actions / Performed

f. Planned Future Events

g. Problems encountered during this period

h. Financial Data (CDRL A002)

- invoiced to date

- remaining funds

- percent expended

4.2 Technical Reports

The contractor shall report and summarize all operational analysis, technology review and assessment findings and investigations in memoranda (CDRL A005) and/or the monthly report (CDRL A001, A002). It will describe activities performed, actions taken and provide recommendations for Government consideration. These findings will provide data and information that the Government may or may not use in the formulation of concepts.

4.3 Technical Briefings and Meetings

The contractor shall prepare briefings that will consist of executive briefings at the contractor’s site, briefings at Navy training centers, briefings to visiting dignitaries, acquisition program offices, and at meetings, conferences, and symposia. Content will be provided to the government for review prior to delivery to any audience outside

NAWCWD (CDRL A003, A004).

4.4 System / Software Documentation

While performing any development, implementation, testing or evaluation, all contractor documentation pertinent to the assigned project will be delivered to the government as systems / software developments once completed (CDRL A007, A008, A009, A00A, A00B, A00C, A00D). Testing and evaluation will be described in test plan (CDRL A00H) and report (CDRL A00J) documents. A goal of the contract procurement is for the complete descriptions of system and software design and implementation to become property of the US Government.

4.5 Software Items

All software, including source code, makefiles, build instructions, associated libraries, and/or utilities developed, will be delivered, when needed, on electronic media suitable for installation, compilation, and use on government-owned computers (CDRL A006). Software shall be accompanied by any necessary installation or build module instructions (CDRL A00E) and/or administrator function descriptions (CDRL A00F).

4.6 Training Materials

The contractor shall provide government user or operator training documentation and assistance on developed prototype programs or application features, interfaces, or requirements (CDRL A00E, A00F, A00G).

5.0 TRAVEL

The contractor will be required to travel to various military installations and other contractor facilities during the performance of delivery orders under the contract. Travel destinations are expected to include: NAWCWD, China Lake, CA; MCAS, Yuma, AZ; Quantico, VA, Springfield, VA, San Diego, CA, and NAS Fallon, NV. The contractor should plan for 3 trips by 2-3 people for 3-5 days for each of these potential destinations for each year of the contract.

6.0 GOVERNMENT FURNISHED PROPERTY/EQUIPMENT

The contractor shall receipt for and maintain custody of any GFE provided during the course of performance of this effort. The workspace to include a desk and office facilities will be provided for the on-site full time support contractors. For Web/Application support, the contractor shall provide their own hardware and software development environment. The government shall provide the end production environment in which all solutions are to be deployed as well as a code repository to be used for delivery of the underlying code for the solutions.

7.0 SOFTWARE AND SOFTWARE DOCUMENTATION RIGHTS

The contractor shall mark all developed software and software documentation under this task with clear language that gives the government Unlimited Rights (UR). All software (e.g., code, executable, minimized run-time scripts, etc.), will be delivered to a government identified software repository (e.g., forge.mil) with a final accounting of the software repository and a description of the accounting to be delivered to the government 60 days prior to final delivery. Any software applications along with associated software documentation developed during this contract remains the property of the government after contract conclusion.

8.0 SECURITY REQUIREMENTS:

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 DoDM5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI) Vol. 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. Contractor shall not store or transmit CUI on personal IT systems or via personal e-mail.

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

Distribution Statement X: (TPOC to determine and insert the appropriate distribution statement here):

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:

Assignment of responsibility for OPSEC direction and implementation.

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

Establishment of OPSEC education and awareness training.

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

Flow down of OPSEC requirements to subcontractors when applicable.

The contractor shall provide an Operations Security (OPSEC) Plan to cover performance of Delivery Orders issued under the contract. Deviations from or exceptions to the OPSEC Plan for a particular order, will require a revision or identification of applicable or inapplicable sections of the plan with rationale for required changes (CDRL A00K).

The contractor shall provide personnel with the appropriate security clearance levels for the work to be performed.

Access to Top Secret information is required in the performance of this contract and shall be in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and applicable DoD, DoN, and Marine Corps Personnel Security regulations. The contractor shall maintain sufficiently cleared personnel with appropriate personnel security clearance (PCL) background investigations to perform the tasks required by this SOW in accordance with the DoD Contract Security Classification Specification (DD Form 254) and the contract.

All contractor personnel shall possess the requisite security clearance, accesses, and need-to-know commensurate with the requirements of their positions.

The contractor shall notify the Naval Air Warfare Center Weapons Division (NAWCWD) Command Security Manager upon notification of on-site contractor support service personnel receiving a no determination made, revocation or denial of an interim PCL, or a final denial of security clearance eligibility.

In accordance with the NISPOM, contractor personnel working on a federal installation in support of this contract shall report to the NAWCWD Command Security Manager any adverse information or circumstances of which they are aware pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

On-site contractor support service (CSS) personnel shall cooperate with any preliminary inquiries conducted by NAWCWD Command Security Manager regarding loss, compromise or suspected compromise of classified information or inquiry into significant command security weaknesses. NAWCWD CSM will notify the appropriate Facility Security Officer and/or Program Manager if a contractor or subcontractor is involved in an inquiry and questioning from the CSS employee is required.

Direct support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with local security provisions and the requirements of SECNAV M-5510.36 (series).

Contractors requiring access to federal installations shall obtain the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s). During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site(s). The contractor shall notify the Government (written notice) within twenty-four hours of any contractor personnel added or removed from the contract that have been granted access to classified material, issued a Common Access Card and/or MCSC Building access. Upon completion or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes issued to contractor employees are returned to the appropriate issuing office.

Contractor employees shall comply with local base procedures for entry into Navy and Marine Corps restricted areas. If contractor employees require unescorted entry into controlled or restricted areas, the contractor shall comply with the applicable Federal Installations Command Physical Security Plan and DoD and/or Marine Corps Personnel Security Program.

Common Access Cards (CACs) will only be issued to those contractors supporting this contract that have been authorized by the COR. CACs are not issued for convenience. All contractor personnel in support of this contract with requirements for access to government IT systems, shall provide a completed System Authorization Access Record – Navy (SAAR-N) form (OPNAV 5239/14 (Rev 9/2011) or latest version thereof) and a completed DOD- IAA-V11.0 DoD Cyber Awareness Challenge V1 Training Certificate or latest version thereof. This training is available at the following locations: https://ile-deers.nko.navy.mil, https://www.us.army.mil, http://iase.disa.mil/eta/cyberchallenge/launchPage.htm. The contractor shall establish a CAC/SAAR-N Point of Contact (POC) to coordinate with the government in such matters. The CAC/SAAR-N POC shall deliver completed Contractor Verification System (CVS) and SAAR-N forms electronically for approval and processing by the government Contracting Officer Representative (COR). SAAR-N forms should be digitally signed by all signatories using either their DoD or ECA issued PKI certificate.

Contractor personnel assigned to perform work under this contract may require access to Navy IT resources (e.g., computers, laptops, personal electronic devices/personal digital assistants (PEDs/PDAs), NMCI, RDT&E networks, websites such as MyNAVAIR, and Navy Web servers) requiring CAC PKI. Contractor personnel (Prime, subcontractor, consultants and temporary employees) requiring access to Navy IT resources (including those personnel who previously signed SAAR DD Form 2875) shall electronically submit a completed System Authorization Access Request Navy (SAAR-N) OPNAV 5239/14 (Rev 9/2011) form or latest version thereof, and have initiated the requisite background investigation (or provide proof of a current background investigation) prior to accessing any Navy IT resources.

In order to maintain access to Navy IT resources, the contractor shall ensure completion of initial and annual DoD Cyber Awareness Challenge V1. The contractor shall complete DoD Cyber Awareness Training latest version thereof, monitor expiration of requisite background investigations, and initiate re-investigations as required. If requested, the contractor shall provide to the COR or designated SAAR-N Government sponsor documentation sufficient to prove that it is monitoring tracking the SAAR-N requirements for its employees who are accessing Navy IT resources. For those contractor personnel not in compliance with the requirements of this clause, access to Navy IT resources will be denied or revoked.

The contractor shall require non-substantial SCI access in performance of tasking under the SOW. A Top Secret Personnel Security Clearance (PCL) based upon a Single Scope Background Investigation (SSBI) or SSBI-PR with SCI eligibility is required. Total labor hours executed against requirements requiring SCI access will be XXX hours. The contractor shall not be required to store SCI material or maintain an SCI facility. All SCI work will be conducted in SCI facilities authorized by the U.S. Government. The contractor’s primary SCI work related site will be onboard XXXXXXX.

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, 1 Administration Circle, STOP 6305, China Lake, CA 93555-6100.

The Contractor will ensure that personnel conducting Information Assurance (IA) functions within the DoD workforce supporting the DoD Global Information Grid (GIG) have and maintain the required system and IA certifications. The DoD IA Workforce includes, but is not limited to, all individuals performing any of the IA functions described within the DoD 8570.01M. (CDRL A00K)

Section D - Packaging and Marking

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:

[Insert specific instructions]

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

To be completed at award

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-3 Inspection Of Supplies Cost-Reimbursement MAY 2001 52.246-8 Inspection Of Research And Development Cost

Reimbursement

MAY 2001

52.246-16 Responsibility For Supplies APR 1984…