N66001-17-R-0291.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 11 Apr 2017

X

A X B X C

D

EX

X G F 83 - 95

96 - 112 X H 113 - 119 christina.neto@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 119

(If other than Item 7) N66001

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.

N66001 8. ADDRESS OFFER TO

9. Sealed offers in original and 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

Section L conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

CHRISTINA E. NETO 619-553-5829

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 7

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

8 - 29 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 32 - 37 X

SPECIAL CONTRACT REQUIREMENTS

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

50 - 81

PART II - CONTRACT CLAUSES

SPAWAR SYSTEMS CENTER PACIFIC

CHRISTINA E. NETO, CODE 22560

CHRISTINA.NETO@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152-5001

SEE CLAUSE L-349

ELECTRONIC SUBMISSION

HTTPS://E-COMMERCE.SSCNO.NMCI.NAVY.MIL/

CA 619-553-5829

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

1300578584

5. DATE ISSUED

08 Mar 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N66001-17-R-0291

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot Services

CPFF

Base period of two years. Provide services in accordance with the Statement of Work (see Section C) as specified in individual task orders.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300578584

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 Lot Hardware/Prototype - Base Period - NSP

0003 1 Lot Other Direct Costs (ODC)

COST

Base period of two years. ODC including but not limited to travel, material, and equipment.

0004 Lot Data - Base Period - NSP

0005 1 Lot OPTION Services

CPFF

Option period of three years. Provide services in accordance with the Statement of Work (see Section C) as specified in individual task orders.

FIXED FEE

TOTAL EST COST + FEE

0006 Lot OPTION Hardware/Prototype - Option Period - NSP

0007 1 Lot Other Direct Costs (ODC)

COST

Option period of three years. ODC including but not limited to travel, material, and equipment.

OPTION

0008 Lot OPTION Data - Option Period - NSP

CLAUSES INCORPORATED BY FULL TEXT

5252.216-9200 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JAN 1989)

***This clause shall be used in completion task orders.***

FIXED FEE: $[Contracting officer insert negotiated fixed fee amount]. The Government shall make payment to the Contractor when requested as work progresses, but no more frequently than biweekly, on account of the fixed fee, equal to [Contracting officer insert fee percentage (total fixed fee divided by total estimated cost plus cost of money)] percent of the amounts invoiced by the Contractor under the “Allowable Cost and Payment” clause hereof for the related period, subject to the withholding provisions of paragraph (b) of the “Fixed Fee” clause. In the event of discontinuance of the work in accordance with clause of this contract entitled “Limitation of [Contracting officer insert “Cost” or “Funds”, as appropriate],” the fixed fee shall be redetermined by mutual agreement equitably to reflect the diminution of the work performed; the amount by which such fixed fee is less than, or exceeds payments previously made on account of fee, shall be paid, or repaid by, the Contractor, as the case may be.

(End of clause)

5252.216-9204 LEVEL OF EFFORT--FEE ADJUSTMENT FORMULA (MAR 1994)

***This clause shall be used in term/level-of-effort task orders.***

(a) Subject to the provisions of the “Limitation of Cost” or “Limitation of Funds” clause (whichever is applicable to this contract), it is hereby understood and agreed that the fixed fee is based upon the Contractor providing the below listed number of staff-hours of direct labor, hereinafter referred to as X, at the estimated cost and during the term of this contract specified elsewhere herein:

[Contracting officer insert number of estimated direct labor staff hours]

CLIN Total Staff-hours of Direct Labor (X)

The Contractor agrees to provide the total level of effort specified above in performance of work described in Sections “B” and “C” of this contract. The total staff-hours of direct labor shall include subcontractor direct labor hours for those subcontractors identified in the Contractor’s proposal as having hours included in the proposed level of effort.

(b) Of the total staff-hours of direct labor set forth above, it is estimated that [Contracting officer insert number of estimated direct staff hours identified as competitive (uncompensated overtime) hours] staff-hours are competitive time (uncompensated overtime). Competitive time (uncompensated overtime) is defined as hours provided by personnel in excess of 40 hours per week without additional compensation for such excess work. All other effort is defined as compensated effort. If no amount is indicated in the first sentence of this paragraph, competitive time (uncompensated overtime) effort performed by the contractor shall not be counted in fulfillment of the level of effort obligations under this contract.

(c) Effort performed in fulfilling the total level of effort obligations specified above shall only include effort performed in direct support of this contract and shall not include time and effort expended on such things as local travel from an employee’s residence to their usual work location, uncompensated effort while on travel status, truncated lunch periods, or other time and effort which does not have a specific and direct contribution to the tasks described in Section B.

(d) It is understood and agreed that various conditions may exist prior to or upon expiration of the term of the contract, with regard to the expenditure of labor staff-hours and/or costs thereunder which may require adjustment to the aggregate fixed fee. The following actions shall be dictated by the existence of said conditions:

(1) If the Contractor has provided not more than [Contracting officer insert percentage (usually 105%)] % of X or not less than [Contracting officer insert percentage (usually 95%)] % of X, within the estimated cost, and at the term of the contract, then the fee shall remain as set forth in Section B.

(2) If the Contractor has provided X-staff-hours, within the term, and has not exceeded the estimated cost then the Contracting Officer may require the Contractor to continue performance until the expiration of the term, or until the expenditure of the estimated cost of the contract except that, in the case of any items or tasks funded with O&MN funds, performance shall not extend beyond 30 September. In no event shall the Contractor be required to provide more than [Contracting officer insert percentage (same as first percentage in subparagraph (d)(1)] % of X within the term and estimated cost of this contract. The fee shall remain as set forth in Section B.

(3) If the Contractor expends the estimated cost of the contract, during the term of the contract and has provided less than X staff-hours, the Government may require the Contractor to continue performance, by providing cost growth funding, without adjusting the fixed fee, until such time as the Contractor has provided X staff-hours.

(4) If the Contracting Officer does not elect to exercise the Government’s rights as set forth in paragraph (d)(2) and (d)(3) above, and the Contractor has not expended more than [Contracting officer insert percentage (same as second percentage in subparagraph (d)(1)] % of X staff-hours, the fixed fee shall be equitably adjusted downward to reflect the diminution of work.

(5) Nothing herein contained shall, in any way, abrogate the Contractor’s responsibilities, and/or the Government’s rights within the terms of the contract provision entitled “Limitation of Cost” or “Limitation of Funds” as they shall apply throughout the term of the contract, based upon the total amount of funding allotted to the contract during its specified term.

(e) Within 45 days after completion of the work under each separately identified period of performance hereunder, the Contractor shall submit the following information in writing to the Contracting Officer with copies to the cognizant Contract Administration Office and DCAA office to which vouchers are submitted:

(1) The total number of staff-hours of direct labor expended during the applicable period.

(2) A breakdown of this total showing the number of staff-hours expended in each direct labor classification and associated direct and indirect costs.

(3) A breakdown of other costs incurred.

(4) The Contractor’s estimate of the total allowable cost incurred under the contract for the period.

In the case of a cost under-run, the Contractor shall submit the following information in addition to that required above:

(5) The amount by which the estimated cost of this contract may be reduced to recover excess funds and the total amount of staff-hours not expended, if any.

(6) A calculation of the appropriate fee reduction in accordance with this clause.

All submissions required by this paragraph shall include subcontractor information, if any.

(f) SPECIAL INSTRUCTION TO THE PAYING OFFICE REGARDING WITHHELD FEE

Fees withheld pursuant to the provisions of this contract, such as the withholding provided by the “Allowable Cost and Payment” and “Fixed Fee” clauses, shall not be paid until the contract has been modified to reduce the fixed fee in accordance with paragraph (d) above, except that no such action is required if the total level of effort provided falls within the limits established in paragraph (d) above.

5252.216-9218 MINIMUM AND MAXIMUM QUANTITIES (JUL 1989)

As referred to in paragraph (b) of the “Indefinite Quantity” clause of this contract, the contract minimum quantity is a total of $100,000 divided by the number of contract awardees. The maximum quantity is the total estimated amount of the contract. The maximum quantity is not to be exceeded without prior approval of the Procuring Contracting Officer.

5252.232-9200 ALLOTMENT OF FUNDS (JAN 1989)

*** This clause shall be used in incrementally funded task orders.***

(a) This contract is incrementally funded with respect to both cost and fee.

(b) The amounts presently available and allotted to this contract for payment of fee, as provided in the Section I clause of this contract entitled “Fixed Fee”, are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided and under “Allotted to Fixed Fee” insert the amount of incremental funding allocated to fixed fee]

ITEM(S) ALLOTTED TO FIXED FEE

(c) The amounts presently available and allotted to this contract for payment of cost, subject to the Section I “Limitation of Funds” clause, the items covered thereby and the period of performance which it is estimated the allotted amount will cover are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided, under “Allotment of Cost” insert the amount of incremental funding allocated to total estimated cost, and under “Period of Performance” insert date by which funding expended]

ITEM(S) ALLOTTED TO COST PERIOD OF PERFORMANCE

(d) The parties contemplate that the Government will allot additional amounts to this contract from time to time by unilateral contract modification, and any such modification shall state separately the amounts allotted for cost and for fee, the items covered thereby, and the period of performance the amounts are expected to cover.

Section C - Descriptions and Specifications

STATEMENT OF WORK :

INTELLIGENCE SURVEILLANCE RECONNAISSANCE (ISR) SYSTEMS ENGINEERING,

SOFTWARE DEVELOPMENT & MODIFICATION, TEST AND EVALUATION

1.0 SCOPE

The scope of this Statement of Work (SOW) includes systems engineering; software development & modification, test and evaluation; and program management services in support of Intelligence Surveillance Reconnaissance surveillance systems to include ocean, airborne, land and space platforms. Within the scope of this effort are systems engineering tasks and support; requirements analysis; system design; system architecture studies;

independent analysis, verification and validation; tactical data applications; hardware and software development;

web page and database development, design, maintenance and system administration support. This effort also provides for life cycle support of surveillance programs/systems/networks, and tactical data communications systems including automated radio communications systems and satellite terminal systems. Trade-off studies may be required to provide a basis for the selection of software/firmware and development methods, which translate required system improvements into functional system elements.

1.1 BACKGROUND

The Space and Naval Warfare Systems Center, Pacific (SSC Pacific), is responsible for the development, test, and integration of Navy Command, Control, Communications, Computer, and Intelligence (C4I) systems, and ocean surveillance systems. This work is critical to the direct fulfillment of multi-service military intelligence missions.

To supplement its in-house capabilities, SSC Pacific requires contractor expertise in systems engineering, software development, project administration, and program management in support of the design, development, integration, test and evaluation, user training, and life cycle support of mission-critical systems and their supporting technologies.

Computer resources referred to in this statement of work may deploy as mission support in a combat environment.

Subject system functionality is surveillance and intelligence related, uses cryptologic equipment, and is integral to the performance of weapons systems such as CCS-MK2 Tomahawk, and Standard Missile Systems. The capability provided is critical to the direct fulfillment of the U.S. Army, Navy, Air Force, and Marine tactical missions excluding administrative/business applications and personnel management.

Examples of potential support areas under this SOW include the below programs and projects related to Intelligence, Surveillance, Reconnaissance and Information Operations (ISR/IO) systems.

Robust, integrated ISR capabilities to support situational awareness, data dissemination, Automated Tasking, Collection, Processing, Exploitation, and Dissemination (TCPED), and provide Common Operational Picture (COP) type output to enable informed decision making. Includes systems engineering, tool development, technical, and training support.

Accelerated Capability for Testing and Integration of Nanosats (ACTION) is the development, integration, and modification of small satellites that focus on communications, radar altimetry, and other software capabilities. Develop specialized software; support test, evaluation and integration efforts; develop prototypes and integrate payloads; implement cybersecurity solutions; and perform end-to-end testing of the entire nanosat system (satellite, ground station, communications, etc.).

Automated Radar Characterization & Development (ARCADE) development. ARCADE automatically characterizes unknown land, sea, and air radars and their modes of operation to enable future automated recognition. The software will extend and apply procedures to recognize & characterize new radar signals and will output "models" that describe the characteristics of candidate signals, which are delivered to analysts for investigation, validation, and incorporation into automated processors & databases.

Correlation and Fusion capabilities. Development, sustainment, and maintenance of software and algorithms that automatically correlate & fuse multiple source intelligence data from National & tactical systems to track operational targets. Capabilities may be implemented in a cloud computing environment.

Distributed Common Ground System – Navy Increment 2 (DCGS-N Inc. 2). DCGS-N provides the Navy’s primary Intelligence, Surveillance, Reconnaissance, and Targeting (ISR&T) support capability.

Engineering support for Software Development and Systems Integration.

Development oversight, technical expertise, ship shore installation, T&E leadership, and acquisition rigor for the development, integration, and testing of an Acoustic Intelligence analysis and information processing systems.

Embedded National Tactical Receiver (ENTR) software systems engineering and maintenance. The ENTR is scaled to fit on a single board within a terminal system and is designed to provide a complete solution for the receiver, cryptographic device and tactical message processing. ENTR interfaces with the Integrated Broadcast Service (IBS).

IBS systems engineering, support, software development, configuration management, cybersecurity, test and evaluation, installation, and documentation development and maintenance.

Image and Video processing frameworks, analytics, and algorithms to perform automatic detection, classification, and recognition of objects from a wide variety of imagery sources and exploit full motion video (FMV) data in a timely manner.

ISR capabilities for Unmanned Systems. Reach back engineering, development, integration, interoperability, and Ground Systems Network architecture support; Development of Naval Doctrine, Concept of Operations (CONOPS), Tactics, Techniques, and Procedures (TTPs), and Experimentation for long endurance Unmanned Air System (UAS).

Maritime Domain Awareness (MDA). Develop software for the visualization, sharing, and analysis of various maritime data to enhance MDA and collaboration with operational partners (Navies, Coast Guards) worldwide, and integrate developed algorithms and tools into coalition accessible web-based Common Operating Pictures.

Meteorological and Oceanographic (METOC) Support. Oceanographic/Atmospheric/environmental monitoring modeling capabilities and technologies.

Nanosatellite and space systems engineering. Feasibility studies, Technology enablers, Payload and sensor Development, Software Development, Integration, Testing, and infrastructure support. Assessments, analyses, testing, and systems engineering in support of Joint space defense capabilities.

Tactical Receiver Segment (TRS) Software Suite. TRS is a Tactical message processor that provides an interface with IBS radios for setup and control, and robust message receipt, translation, and reliable output of IBS tactical data.

Joint Tactical Terminal-Maritime (JTT-M) software development, test and evaluation services, software support, configuration management and logistic support.

Virtual Reality/Mixed Reality. Evaluate, integrate and exploit commercial mixed reality technology for adaptation to a virtual world battlespace.

Joint Tactical Terminal-Portable IBS Correlation Exploitation System (JTT-PICES) software sustainment, development, and maintenance. JTT-PICES is a software application for operational target tracking that automatically correlates & fuses multiple source intelligence data from National & tactical systems reported on Integrated Broadcast Service- Simplex (IBS-S).

SeaFire development. SeaFire provides a solution for conducting multiple intelligence (multi-INT) higher level information fusion in a cloud computing environment. It will use national technical means data from the IC community (to include US Navy). The intelligence sources utilized in this project will include Signals Intelligence (SIGINT) and Geographic Intelligence (GEOINT). Cloud Computing enables common hardware and software tools across the IC and the US Navy. With a common baseline of hardware/software a more efficient and cost effective solution is available to solve technical problems for the Warfighter.

2.0 REFERENCE DOCUMENTS

a. DOD-5220-22: Industrial Security Manual for Safeguarding Classified Information

b. MIL-STD-961E: Defense and Program-Unique Specifications Format and Content

c. MIL-HDBK-881: Work Breakdown Structure

d. MIL-HDBK-61A: Configuration Management Guidance

e. ISO/IEC 12207: Systems and Software Engineering – Software Life Cycle Processes

f. ISO/IEC 15288: Systems and Software Engineering- System Life Cycle Processes

g. ISO/IEC 26702: Systems Engineering- Application and Management of the Systems Engineering

Process

h. CMMI-DEV 1.3: Software Engineering Institute Capability Maturity Model Integrated – Development version 1.3

i. CMMI-SVC 1.3: Software Engineering Institute Capability Maturity Model Integrated – Services version 1.3

j. CubeSat Design Specification Rev.13 - The CubeSat Program California Polytechnic State University

– San Luis Obispo, CA 93407

k. DOD 5200.01 Information Security Program Manual, 24 February 2012

l. DoDI 5200.02, DoD Personnel Security Program (PSP), 9 September 2014

m. DoD 5220.22-M, DoD Manual – National Industrial Security Program Operating Manual (NISPOM), 28 February 2006

n. DoDI 5220.22, DoD Instruction – National Industrial Security Program, 18 March 2011

o. DoDI 6205.4, Immunization of Other Than U.S. Forces (OTUSF) for Biological Warfare Defense, 14

April 2000

p. DoDI 8500.01, Cybersecurity, 14 March 2014

q. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March

r. DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 December 2005 with

Change 3 dated 24 January 2012

s. DoDD 8140.01, Cyberspace Workforce Management, 11 August 2015

t. SECNAV M-5239.2, DON Information Assurance Workforce Management Manual, May 2009

u. SECNAV M-5510.30, DON Regulation – Personnel Security Program, 6 October 2006

v. SECNAVINST 4440.34, Secretary of the Navy Instruction – Implementation of Item Unique

Identification within the DoN, 22 December 2009

w. SECNAVINST 5239.20A, DON Cybersecurity Policy, 2 May 2016

x. SECNAVINST 5239.3C, DON Cybersecurity Policy, 2 May 2016

y. SECNAVINST 5510.30, DON Regulation – Personnel Security Program, 6 October 2006

z. DON CIO Memorandum, Acceptable Use of Department of the Navy Information Technology (IT), 12

February 2016

aa. SPAWARINST 4440.12, Management of Operating Materials and Supplies (OM&S), Government

Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory

bb. SPAWARINST 5721.1B, SPAWAR Section 508 Implementation Policy, 17 November 2009

cc. COMUSFLTFORCOM/COMPACFLTINST 6320.3A, Commander US Fleet Forces Command/Commander US Pacific Fleet Instruction, Medical Screening For US Govt Civilian Employees, Contractor Personnel, and Guests prior to embarking Fleet Units, 7 May 2013

dd. Navy Telecommunications Directive (NTD 10-11), System Authorization Access Request (SAAR) – Navy

3.0 TECHNICAL REQUIREMENTS

3.1 SYSTEMS ENGINEERING

Systems engineering tasks include the analysis, design, development, installation, test and evaluation, testbed integration, training, and documentation for new systems and for life cycle support of fielded systems including but not limited to: ARCADE, DCGS-N, IBS, ENTR, TRS, JTT-M, and SeaFire. Areas of research and development will encompass but not be limited to Virtual Reality/Mixed Reality, Nanosatellite and space systems, Maritime Domain Awareness, Image and Video processing frameworks, Correlation and Fusion capabilities, Unmanned systems, and TCPED as they relate to ISR / IO. As specified in individual delivery/task orders, and as the tasking relates to specified programs the contractor shall recommend communications architectures, planning and specific approaches to system implementation. Systems engineering shall also include identification and development of interface requirements for various systems, Human-Machine Interface (HMI) design analyses and trade-off analyses for systems being formulated. Systems engineering shall also ensure that adequate consideration is given to system safety objectives. As specified in individual delivery/task orders, the contractor shall:

3.1.1 Perform trade-off analysis pertaining to the design and performance of systems, and of modifications and upgrades to systems.

3.1.2 Perform studies to determine most effective methods and procedures for systems implementation with minimum operational force disruption.

3.1.3 Produce procedures, perform surveys, and conduct analyses pertaining to the performance of existing and future systems to identify requirements for improvements and upgrades.

3.1.4 Perform design/engineering for new tactical surveillance C4I systems, and for modifications and upgrades to existing systems.

3.2 PROTOTYPE DEVELOPMENT AND LOGISTICS SUPPORT

As specified in individual delivery/task orders, the contractor shall:

3.2.1 Fabricate and assemble prototypes and advanced development equipment models and prototype subsystem configurations for demonstration tests and early deployment.

3.2.2 Investigate and model software to support systems under development. Evaluate the impacts of such software on existing hardware and software programs.

3.2.3 Support integration of each prototypes into the full systems architecture and provide integration, installation, test and maintenance support for these systems.

3.2.4 Prepare drawing packages and/or specifications for integration of each prototype into the full systems architecture.

3.2.5 Establish and maintain an Integrated Logistics Support (ILS) program to document the manner in which each applicable element of ILS is obtained and integrated with all other elements of systems.

3.2.6 Develop a reliability and maintainability program to define and implement detailed techniques and tasks required to ensure that Reliability, Maintainability, and Availability

(RMA) requirements are satisfied.

3.2.7 Plan and implement a comprehensive Configuration Management (CM) and documents the security program to cover design, development, and maintenance activities. This will include a Data Management function/document library, and software CM functions such as on-line/networked tracking of hardware and software trouble reports, document discrepancies, documentation and software changes, and software version control.

3.2.8 Develop and implement Quality Assurance (QA) procedures and practices to ensure compliance with all applicable requirements. Ensure that quality functions, planning, and tasks are fully integrated. Provide direction for the QA engineering, design, product development, integration, and test activities, which will include hardware and software Quality Assurance Plans.

3.3 SOFTWARE SYSTEM ENGINEERING, DESIGN AND DEVELOPMENT

In accordance with appropriate and agreed-upon parts of ISO/IEC 12207, and as the tasking relates to programs listed in paragraph 1.1 above, the contractor shall provide requirements analysis, verification, validation, and traceability, design and development of software/firmware, technical/user documentation, and test bed integration support for Navy and joint service surveillance, intelligence, and tactical data systems; their associated communications systems and interfacing subsystems; and establish a software quality program for software under development. As specified in individual delivery/task orders, the contractor shall:

3.3.1 Perform system concept formulation analysis and feasibility determinations. Develop CONOP and Concept of Employment (CONEMP) type documentation to guide the definition of system functionality.

3.3.2 Develop and document system architecture criteria for new system development and for modification of existing systems.

3.3.3 Prepare impact studies related to the addition, deletion, or modification of system requirements.

3.3.4 Analyze system/software requirements, identify system engineering requirements, and perform and document trade-off studies. Allocate system requirements between hardware, software, and personnel to partition the system into Hardware Configuration Items (HWCI), Computer Software Configuration Items (CSCI), and manual operations.

Prepare or update a System/Subsystem Design Document (SSDD) for each CSCI.

Define engineering requirements for each CSCI.

Prepare or update a Software Requirements Specification (SRS) for each CSCI. Identify external interface requirements of systems being formulated.

Prepare or update an Interface Requirements Specification (IRS).

Prepare or update the Software Development Plan (SDP), which shall include software development standards and procedures.

Conduct Software Specification Review.

Prepare or update the Requirements Traceability Matrix (RTM).

3.3.5 Provide independent analysis, verification and validation of Commercial Off-The-Shelf (COTS) and non-proprietary systems from other developers.

Analyze design documentation and test results to verify compliance with system requirements.

Review test plans and procedures to verify test conduct will properly validate conformance to requirements.

Develop and maintain program master plans and schedules.

3.3.6 Provide program/project management planning and coordination services, and support for Government sponsored meetings. Generate meeting summaries and/or trip reports.

3.3.7 Develop the preliminary top level design of each CSCI.

Provide sizing and timing estimates and develop risk management procedures.

Document the top level design or update existing top level design in the SSDD.

Prepare or update the Software Test Plan (STP) Prepare or update Software Test Procedures.

Conduct Preliminary Design Review (PDR).

3.3.8 Develop a modular detailed design for each CSCI.

Document the detailed design or update existing detailed design for each CSCI in the SSDD and Interface Design Document (IDD) and Interface Control Document (ICD).

Create or update the Interface Requirements Specification (IRS), and Software Test Description (STD) for each CSCI.

Create and maintain a Software Development File (SDF) for each unit of code and a software development library.

Prepare or update the Computer Programming Manual (CPM) and Firmware Support Manual (FSM).

Conduct Critical Design Reviews (CDR).

3.3.9 Perform and document informal software design reviews and support formal program design reviews provided by SSC Pacific for the system procurement agency/office.

3.3.10 Provide software support documentation and operational documentation.

Prepare or update the Computer Operator's Manual (COM), Software User's Manual (SUM), Software Transition Plan (STrP) and Software Design Document.

3.3.11 Develop and support revisions to systems software, applications software, and simulation software. Produce source and object code, and conduct code walk-throughs.

3.3.12 Modify source and object code as a result of independent testing by other testing agents.

Update Software Development Files with test results and changes to the software design and code.

Provide the Software Product Specification (SPS).

3.3.13 Update source and object code in response to approved problem solutions and requirements changes.

Update software and user documentation to represent the current software configuration. Provide Software Trouble Reports (STR’s) for each CSCI.

Provide Software Version Description (SVD), which details changes between software versions for each CSCI. Provide updated SPS document.

3.3.14 Provide web support for information databases, documentation updates and web page design and development.

3.3.15 Provide system administration services for software being developed at SSC Pacific.

3.3.16 Develop training materials and provide software installation, checkout and user training services at government selected sites.

3.4 SOFTWARE CONFIGURATION MANAGEMENT, TEST AND EVALUATION

As specified in individual delivery/task orders, and as the tasking relates to programs listed in paragraph 1.1 above, the contractor shall:

3.4.1 Perform CM for software being developed or maintained in accordance with the Government approved software development plan. Establish and maintain configuration status accounting information, which provides the current status of the system configuration. Support efforts to accomplish changes to baseline requirements, and to obtain deviations and waivers for approved requirements. Analyze proposed changes for detailed impacts and implementation requirements, and provide appropriate documentation (Engineering Change Proposals (ECP’s) and Request for Deviation and Waivers (RDW). Provide Specification Change Notice (SCN) and Notice of Revision (NOR) documentation. The contractor shall be responsible for conducting a Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) of each CSCI.

3.4.2 Establish a software quality program plan. Obtain Government approval of the program plan and implement required procedures.

3.4.3 Perform functional and performance evaluation, and formal and informal testing of the systems, subsystems, components and interfacing systems. Perform requalification of the systems for operational acceptance.

3.4.4 Develop test plans and test procedures, which will be used during all formal testing of systems and associated interfaces. Upon completion of formal testing, test reports will be required. These will include the completed test procedure checklist forms and a listing of all open trouble reports, document discrepancy reports, and change proposals.

3.4.5 During test and evaluation operations, formally document observed discrepancies in trouble reports. Trouble reports of released system/components received from customer agencies will be received in various formats. The contractor shall participate in the evaluation and responses to these reports.

3.4.6 Develop, maintain and re-validate the support tools necessary for the conduct of system performance evaluations. These tools will be revised for compatibility with future upgrades and newly developed systems for interface test requirements.

3.4.7 Assess the impact of on-going design changes on security characteristics of the developed systems and their associated interfaces. Provide impact analysis reports documenting any deficiencies in meeting required certification levels and recommend corrective actions. The deficiencies shall be identified in a timely manner to allow correction prior to system certification and operational release. Based on the resulting design, the contractor shall prepare the system certification documentation package for formal agency cybersecurity certification and re-certification.

3.4.8 Perform IV&V to determine whether products of a given phase of the software development cycle fulfill the requirements established during the previous phase. Software shall be evaluated at the end of the development process to ensure compliance with requirements and that the software system performs to the customer’s expectations under operational conditions.

3.4.9 Conduct analysis to evaluate potential sources risks throughout the software and system life cycle. Analysis shall include identification, likelihood, acceptable levels, and risk handling options, and risk prevention, mitigation, and contingency plans.

3.5 SOFTWARE ENGINEERING APPROACH

The contractor shall define a software development approach appropriate for the computer software effort to be performed under this contract. This approach shall be documented in a Software Development Plan (SDP) (see DID No. DI-IPSC-81427A for required format and content). Once defined, the contractor shall follow this SDP for all computer software to be developed or maintained under this contract.

The SDP shall define the offeror’s proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207.0. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this contract.

In accordance with the framework defined in IEEE/EIA Std. 12207.0, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std. 12207 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the Government can assess whether the offeror’s approach is viable.

The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as a minimum, specific standard, methods, tools, action, strategies, and responsibilities associated with development and qualification.

The contractor’s software engineering approach shall afford opportunities for input and oversight by the Government.

4.0 CYBERSECURITY COMPLIANCE

Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

4.1 CYBER IT AND CYBERSECURITY PERSONNEL

(a) The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

(b) The contractor shall be responsible for identifying, tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF) and Cyber IT workforce personnel. Although the minimum frequency of reporting is monthly, the task order can require additional updates at any time.

(c ) Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented in para 8.2.2.4(b).

When a contractor requires logical access to a government IT system or resource (directly or indirectly), the required CAC will have a Public Key Infrastructure (PKI). A hardware solution and software (e.g., ActiveGold) is required to securely read the card via a personal computer. Pursuant to DoDM 1000.13-M-V1, CAC PKI certificates will be associated with an official government issued e-mail address (e.g. .mil, .gov, .edu). Prior to receipt of a CAC with PKI, contractor personnel shall complete the mandatory Cybersecurity Awareness training and submit a signed System Authorization Access Request Navy (SAAR-N) form to the contract’s specified COR. Note: In order for personnel to maintain a CAC with PKI, each contractor employee shall complete annual cybersecurity training. The following guidance for training and form submittal is provided; however, contractors shall seek latest guidance from their appointed company Security Officer and the SSC Pacific Information Assurance Management (IAM) office:

1. For annual DoD Cybersecurity/IA Awareness training, contractors shall use this site:

https://twms.nmci.navy.mil/. For those contractors requiring initial training and do not have a CAC, contact the SSC Pacific IAM office at phone number [insert applicable contract information] (843)218-6152 or e-mail questions to ssc_lant_iam_office.fcm@navy.mil for additional instructions. Training can be taken at the IAM office or online at http://iase.disa.mil/index2.html.

2. For SAAR-N form, the contractor shall use OPNAV 5239/14 (Rev 9/2011). Contractors can obtain a form from the SSC Pacific IAM office at or from the website: https://navalforms.documentservices.dla.mil/. [insert applicable contract information] Digitally signed forms will be routed to the IAM office via encrypted e-mail to ssclant_it_secmtg@navy.mil.

(d) Contractor personnel with privileged access will be required to acknowledge special responsibilities with a Privileged Access Agreement (PAA) IAW SECNAVINST 5239.20A.

4.2 DESIGN, INTEGRATION, CONFIGURATION OR INSTALLATION OF HARDWARE AND

SOFTWARE

The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official. Contractors that access Navy IT are also required to follow the provisions contained in DON CIO Memorandum: Acceptable Use of Department of the Navy Information Technology (IT) dtd 12 Feb 16. Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System (DADMS) and is Functional Area Manager (FAM) approved can be used as documented in para 5.2.2. Procurement and installation of software governed by DON Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON CIO Policy and DON ELAs awarded.

4.3 CYBERSECURITY WORKFORCE (CSWF) REPORT

DoD 8570.01-M and DFAR’s PGI 239.7102-3 have promulgated that contractor personnel shall have documented current cybersecurity certification status within their contract. The contractor shall develop, maintain, and submit a CSWF Report as applicable at the task order level. IAW clause DFARS 252.239-7001, if cybersecurity support is provided, the contractor shall provide a Cybersecurity Workforce (CSWF) list that identifies those individuals who are IA trained and certified. Utilizing the format provided at the task order level , the prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. Contractor shall verify with the COR or other government representative the proper labor category cybersecurity designation and certification requirements.

5.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

This paragraph only applies to IT contracts. Information Technology (IT) is defined as any equipment or interconnected system(s) or subsystem(s) of equipment, that is used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data of information by the agency. IT includes computers, ancillary equipment, peripherals, input, output, and storage devices necessary for security and surveillance. Electronic and Information technology (EIT) is IT that is used in the creation, conversion, or duplication of data or information. EIT includes: telecommunication products, such as telephones; information kiosks; transaction machines; World Wide Web sites; multimedia (including videotapes); and office equipment, such as copiers and fax machines.

5.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

When applicable, the contractor shall be responsible for the following:

• Ensure that no production systems are operational on any RDT&E network.

• Follow DoDI 8510.01 of 12 Mar 2014 when deploying, integrating, and implementing IT capabilities.

• Migrate all Navy Ashore production systems to the NMCI environment where available.

• Work with government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).

• Follow SECNAVINST 5239.3B of 17 June 2009 & DoDI 8510.01 of 12 Mar 2014 prior to integration and implementation of IT solutions or systems.

• Register any contractor-owned or contractor-maintained IT systems utilized on contract in the Department of Defense IT Portfolio Registry (DITPR)-DON.

• Only perform work specified within the limitations of the contract/task order.

5.2 ACQUISITION OF COMMERCIAL SOFTWARE PRODUCTS, HARDWARE, AND RELATED

SERVICES

This paragraph only applies to the purchasing/hosting of commercial software. Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

5.2.1 DON ENTERPRISE LICENSING AGREEMENT/DOD ENTERPRISE SOFTWARE INITIATIVE

PROGRAM

Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA) dtd 22 Feb 12, contractors that are authorized to use Government supply sources per FAR 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the task order level.

5.2.2 DON APPLICATION AND DATABASE MANAGEMENT SYSTEM (DADMS)

The contractor shall ensure that no Functional Area Manager (FAM) disapproved applications are integrated, installed or operational on Navy networks. The contractor shall ensure that all databases that use database management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting Navy applications and systems be registered in DoN Application and Database Management System (DADMS) and are FAM approved. All integrated, installed, or operational applications hosted on Navy networks must also be registered in DADMS and approved by the FAM. No operational systems or applications will be integrated, installed, or operational on the RDT&E network.

5.3 SECTION 508 COMPLIANCE

This paragraph only applies to IT contracts. The contractor shall ensure that all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B of 17 Nov 2009. In accordance with FAR 39.204, this requirement does not apply to contractor acquired software that is incidental to the task, software procured/developed to support a program or system designated as a National Security System (NSS) or if the product is located in spaces frequented only by service personnel for maintenance, repair or occasional monitoring of equipment.

5.4. SOFTWARE DEVELOPMENT/MODERNIZATION AND HOSTING

This paragraph only applies to software development and modernization. The contractor shall ensure all programs utilizing this contract for software development/ modernization (DEV/MOD),…