RFP N66001-17-R-0036.pdf

CODE

(Hour)

PAGE(S)

until 04:00 PM local time 03 Oct 2017

X

A X B X C

D

EX

X G F 80 - 90

91 - 106 X H 107 - 111 keiko.dagostino@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 111

(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 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

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

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

KEIKO D'AGOSTINO 619-553-5585

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 6

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

7 - 26 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 29 - 34 X

SPECIAL CONTRACT REQUIREMENTS

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

52 - 78

PART II - CONTRACT CLAUSES

SPAWAR SYSTEMS CENTER PACIFIC

KEIKO D'AGOSTINO, CODE 22560

KEIKO.DAGOSTINO@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152

SEE SECTION L

ELECTRONIC SUBMISSION

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

CA 619-553-5585

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

1300613160

5. DATE ISSUED

31 Aug 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6600117R0036

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 (Section C) as specified in individual task orders.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300613160

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 1 Lot Other Direct Costs (ODC)

COST

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

0003 Lot Data-Base Period-Not Separately Priced

0004 1 Lot OPTION Services

CPFF

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

FIXED FEE

TOTAL EST COST + FEE

0005 1 Lot Other Direct Costs (ODC)

COST

Option period of two years. ODC including but not limited to travel, materials, and equipment.

OPTION

0006 Lot OPTION Data-Option Period-Not Separately Priced

CLAUSES INCORPORATED BY FULL TEXT

B-TXT-01 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JUN 2017)

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

FIXED FEE: $*. 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 ** 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 *** 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.

* To be completed upon award of the contract

** To be determined at the Task Order level. The allowable fee percentage will be negotiated at the Task Order level, and shall not exceed the percentage proposed at the basic contract level

*** To be determined at the Task Order level.

(End of clause)

B-TXT-04 LEVEL OF EFFORT--FEE ADJUSTMENT FORMULA (JUN 2017)

***This clause shall be used in term/level-of-effort task orders. This clause will be completed at the task order level.***

(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 105% of X or not less than 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 105 % 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 95% 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.

B-TXT-08 MINIMUM AND MAXIMUM QUANTITIES (JUN 2017)

As referred to in paragraph (b) of the “Indefinite Quantity” clause of this contract, the contract minimum quantity is a total of $20,000 worth of orders at the contract unit price(s). 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.

B-TXT-10 ALLOTMENT OF FUNDS (JUN 2017)

***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 (SOW)

Navy Common Data Link (CDL) Systems Engineering, Software Development and Maintenance, Integration, Test and Evaluation and

Program Support Services 30 May 2017

1. SCOPE

The contractor shall provide systems engineering and integration services, software development and maintenance, and test and evaluation services in support of the Space and Naval Warfare (SPAWAR) Systems Center Pacific (SSC Pacific) mission to provide full spectrum support of Advanced Navy communications systems including Navy CDL systems.

1.1 Background

SSC Pacific provides full spectrum support including systems engineering, software development, integration, test and evaluation, and program support for Advanced Navy communications systems including Network Tactical Common Data Link (NTCDL), Communications Data Link System (CDLS), CDLS – Technology Refresh (CDLS- TR), and Tactical Common Data Link (TCDL). Functions include mission analysis, assessment of the technology base, basic research, demonstration of the technology, engineering in support of design and production, customer support for new and existing operational systems, and integration of Navy CDL Systems. SSC Pacific’s continuing goal is to protect and accelerate information transfer within and between the various Navy CDL and Navy wideband communications systems for all U.S. and allied Services. This includes developing, migrating, integrating, and maintaining new technology for advances in communications and surveillance. This also includes integration of advanced concepts into formats compatible with Consolidated Afloat Networks and Enterprise Services (CANES), Automated Digital Network System (ADNS), Combat Systems Product Line Architecture (CS-PLA) and/or the Distributed Common Ground System (DCGS) architectures.

2. APPLICABLE DOCUMENTS

In the event of a conflict between the text of this SOW and the applicable documents cited herein, the text of this SOW shall take precedence. Nothing in this SOW, however, shall supersede applicable laws and regulations. The following documents are for reference only, except where invoked for a specific section of the SOW.

NTCDL-SDP-7004-0.1 Link Management System (LMS) & External Data User Interface (EDUI)

Software Development Plan (SDP) for AN/USQ-214 Network Tactical Common Data Link (NTCDL) Surface Terminal, July 2016 (draft)

Std-CDL F-1 Waveform Specification for the Standard Common Data Link (Std-CDL)

Waveform, Specification Number 7681990 Revision F, Change 1, February

Std-CDL H-2 Performance Specification for the Standard Common Data Link (Std-CDL)

Waveform, Specification Number 7681990, Revision H-2, December 2014

BE-CDL Performance Specification for the Bandwidth Efficient-Common Data Link

(BE-CDL) Waveform, Specification Number 60038368 Rev [B], August 2015

CAP 60038365 Rev A Capstone Specification for the Network-Centric Common Data Link (Capstone), Specification Number 60038365 Rev [A], July 2017

ISO/FDIS 9241-391:2016 International Standard 9241-210: Ergonomics of Human-System Interaction, February 2016

SPAWAR Style Guide SPAWAR Common User Interface Style & Interaction Guide, Version 2.5, December 2016

DoD8570.01-M Information Assurance Workforce Improvement Program, November 2015

SSCPACINST 5239.5 Cybersecurity Workforce Policy, February 2016

SECNAV M-5239.2 Cyberspace Information Technology and Cybersecurity Workforce

Management and Qualification Manual, June 2016

DoDD 8140.01 Cyberspace Workforce Management, August 2015

SECNAVINST 5000.2E Implementation and Operation of the Defense Acquisition System and the Joint

Capabilities Integration and Development System, September 2011

DoDD 5000.74 Defense Acquisition of Services, January 2016

DoDI 5000.02 Operation of the Defense Acquisition System, January 2015

PR-RSK-1000026 SSC Pacific Risk Management Process, November 2016

NTCDL-CMP-4001P-1.0 Network Tactical Common Data Link (NTCDL) Lifecycle Configuration

Management Plan (CMP), July 2014

Secure Room SOP Standard Operation Procedures (SOP) for Secure Room, Code 56190, May 2015

DoDI 8510.01 Risk Management Framework (RMF) for Department of Defense (DoD)

Information Technology (IT), May 2016

DID No. DI-IPSC-81427B Software Development Plan (SDP), March 2017

ISO/IEC Std. 12207:2008 Systems and software engineering – Software life cycle processes, February

NISPOM National Industrial Security Program Operating Manual, February 2006

SECNAV Manual 5510.30 Department of Navy Personnel Security Program, June 2006

SECNAV Manual 5510.36 Department of Navy Information Security Program, June 2006

OPNAVINST F3300.53C Navy Antiterrorism Program, May 2009

DOD 5200.01 Volumes 1 DOD Security Program, February 24, 2012 through 4

DOD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), February

28, 2006, CH 1 March 28, 2013

National Security Decision National Operations Security Program (NSDD) 298, January 22, 1988 Directive 298

DOD 5205.02 DOD Operations Security (OPSEC) Program, November 3, 2008

DOD Directive 5205.02 DOD Operations Security (OPSEC) Program, March 6, 2006

OPNAVINST 3432.1 DON Operations Security, November 4, 2011

SPAWARINST 3432.1 Operations Security Policy, February 2, 2005

3. TECHNICAL REQUIREMENTS

The contractor shall provide the following support as specified in individual task orders.

3.1 Systems Engineering & Integration

3.1.1 Systems Engineering

The contractor shall provide systems engineering support for the development, deployment, and maintenance of NTCDL, CDLS TR, CDLS, TCDL, as well as general CDL systems. The systems engineering personnel shall recommend new approaches to meeting Department of Defense (DoD) systems requirements and propose enhancements to existing operational systems. The contractor shall provide/implement solution(s) when a system fails to meet operational specifications, fails to interface with other systems, or fails to meet required operational availability or mission requirements.

The contractor shall provide systems engineering support to include the analysis of CDL capabilities, functionality, and implementation alternatives. The systems engineering support shall include analysis and research of Navy CDL needs, future CDL operational constraints, and the evaluation of new technology impacts on CDL implementations and analysis of alternatives. The systems engineering support shall evaluate potential interference, electromagnetic effects, spectrum utilization, and exploitation system architectures.

The contractor shall provide systems engineering support to include reviewing, updating, and validating waveform requirements and specifications. The contractor shall review the scope, contents, and validity of proposed waveform revisions. The contractor shall evaluate and/or recommend changes to waveform specifications for incorporation into existing and future standards.

The contractor shall provide systems engineering support for Navy CDL interoperability across all Navy efforts.

This support includes, but is not limited to, compliance with Joint Interoperability Test Command (JITC), and PEO Unmanned Aviation and Strike Weapons (U&W) Naval Interoperability Profile (NIOP)/Interface Control Working Group (ICWG) requirements.

The contractor shall audit Earned Value Management (EVM) deliverables such as cost, schedule, and performance data. The systems engineering support shall include planning for and participating in Systems Engineering Technical Review (SETR) events. In addition, the contractor shall review and provide feedback on SETR work products.

3.1.2 Systems Analysis

The contractor shall perform systems and subsystems engineering analyses, to include feasibility studies, data analysis and design reviews to provide recommended design changes and/or enhancements. Technical solutions proposed by the contractor shall emphasize common and/or Non-Developmental Item (NDI) hardware/software architectures and components, and the use of cross platform compatible techniques.

3.1.3 Systems Integration

The contractor shall provide systems integration engineering and technical support related to transition and integration of subsystems and software for NTCDL, CDLS TR, CDLS, TCDL as well as general CDL systems. The integration engineering support services shall include the analysis of DoD requirements, development, and/or modification of system interface requirements, interface designs, and interface control documents for systems.

3.1.4 System Hardware Integration

The contractor shall support the integration of new and modified products into the systems, providing site surveys, site preparation, actual integration, and testing of the new product/enhancement to ensure functional performance.

The contractor shall support prototyping of new product designs/enhancements. The contractor shall support design and analysis for the integration of new products/enhancements into NTCDL, CDLS TR, CDLS, TCDL as well as general CDL systems. The contractor shall analyze and recommend solutions to system interface issues that may be encountered during system operations and maintenance.

3.1.5 System Software Integration

The contractor shall analyze proposed software for systems integration and testing on operational platforms and land based facilities. The contractor shall analyze and recommend solutions to software interface and communication problems that may be encountered during systems integration and system operations.

The contractor shall develop, modify, and/or evaluate and implement computer-automated software engineering tools, methods, databases, and procedural framework(s) to facilitate effective software integration with minimal risk.

The contractor shall develop, modify, and/or evaluate system level simulators and emulators used to test NTCDL, CDLS TR, CDLS, TCDL as well as general CDL systems.

3.1.6 Interoperability and Security

The contractor shall provide engineering support for improving the interoperability and security among existing sensitive compartmented information systems in accordance with Navy Cybersecurity Safety Program (CYBERSAFE) and Risk Management Framework (RMF) requirements. The contractor shall develop, modify, and/or evaluate System Security Authorization Agreements (SSAA), System Security Plans (SSP) and make necessary system modification recommendations to ensure compliance with individual project security requirements necessary for system certification by cognizant authorities, such as the Office of Naval Intelligence (ONI) and/or Joint Interoperability Test Command (JITC). The contractor shall participate in system design reviews during the development cycle to ensure security considerations are incorporated and implemented during system hardware and software development. The contractor shall develop, modify, and/or evaluate security test procedures, plans, and/or supporting documentation. The contractor shall conduct and/or support Cybersecurity testing as required by the government. The contractor shall participate in any interoperability testing as required by the government.

3.1.7 System Installation Support

The contractor shall install and provide integration support of new and modified system software at shore support facilities and onboard operational platforms. The integration services may include developing, modifying, and/or evaluating system requirements, system specifications, functional requirements, integration schedules, system installation and checkout plans and procedures, and integration test activities to demonstrate that the system interfaces and interdependencies have been properly designed and implemented.

3.1.8 Requirements Database

The contractor shall support Government development and maintenance of a requirements database. The primary use of this database will be to compare system requirements with the implementation of system hardware and software. The contractor shall use this database in the development of proposed systems specifications. The database may be developed and maintained within a Computer Aided Software Engineering (CASE) tool as designated by the government.

3.1.9 Requirements Analysis, Allocation, and Specification

The contractor shall perform systems engineering requirements analyses for existing and emerging CDL hardware and software systems and subsystems. This includes, but is not limited to, requirements definition, allocation to software segments and host hardware configurations, analyses of signal processing and signal-to-noise enhancement techniques, analyses of network integration and routing alternatives, and information processing approaches. The contractor shall incorporate analyses results into system architecture plans and system specifications.

3.1.10 Advanced Technology Development

The contractor shall perform technology development to support the evolutionary upgrade of NTCDL, CDLS TR, CDLS, TCDL as well as general CDL systems. Under this effort the contractor shall conduct science and technology projects. The contractor shall provide systems engineering services to support the evaluation of development options through system trade-off studies and/or prototyping of potential system alternatives.

3.1.11 Next Generation Specification Development

The contractor shall support development of next generation specifications. This requirement may include development support of the next generation CDL waveform specification based on ad hoc mesh networking, and/or the next generation CDL terminals. Development support includes evaluation of architecture options, modeling of networking options to assess performance and ability to be implemented, and development/evolution of the Operational Architecture, Technical Architecture, and System Architecture. In performance of this requirement, the contractor shall coordinate with appropriate organizations and agencies such as the CDL Program Office, Naval Command Operational Test and Evaluation Force (COMOPTEVFOR or COTF), Office of the Chief of Naval Operations (OPNAV), Naval Network Warfare Command (NETWARCOM), Pacific/Atlantic Fleet (PAC/LANTFLT), and National Security Agency (NSA).

3.1.12 System Design Changes/Modifications

The contractor shall prepare recommended specifications/designs for enhancements and/or new hardware/software products as directed by the government.

3.1.13 Integrated Product Teams

The contractor shall participate on designated Integrated Product Teams (IPTs) to review designs and/or specifications in order to assure compliance with the relevant specifications and mission requirements and as directed by the government.

3.1.14 Technical Working Groups

The contractor shall actively participate in designated Technical Working Groups (TWG) and Sub-TWGs, e.g. the CDL TWG, Simple Network Management Protocol (SNMP)/Management Information Base (MIB) Sub-TWG, and Common Core Modernization (CCM) Sub-TWG. The contractor shall be responsible for consistent meeting attendance, reports, meeting minutes, and summaries.

3.1.15 CDL Waveform Documentation

The contractor shall review and evaluate all approved and draft CDL Waveform documentation, e.g., Standard CDL, Bandwidth Efficient CDL, Discovery CDL, Network CDL, and Capstone.

3.2 Software Development

3.2.1 Software Analysis

The contractor shall analyze system requirements, system problems, and proposed changes to existing software.

The contractor shall decompose proposed changes into required new software modules or changes to existing software modules. The contractor shall identify the scope of the changes and risk factors. Analyses shall utilize existing software to the maximum extent feasible.

3.2.2 Software Planning

The contractor shall perform detailed planning to determine the complexity, size, schedule, personnel resources, equipment, and cost required to support the development of new or revised software programs. The contractor shall follow established processes (reference NTCDL-SDP-7004-0.1) or develop processes for software development and configuration management to meet requirements within allocated schedule and funding.

3.2.3 Software Design and Coding

The contractor shall design, code, document, support, and conduct automated tests of new or revised software and software support programs. The contractor shall utilize agile software development methodology and participate in sprint planning, daily standup meetings, and sprint retrospectives. The contractor shall complete software development tasks using a Behaviour Driven Development methodology and tracking assigned tasks in JIRA. The contractor shall utilize a visual and modeling tool that supports design and development of software, e.g. Enterprise Architect. The contractor shall develop software to monitor, control, and simulate a CDL system. The contractor shall develop software utilizing Java, Java Enterprise Edition, JavaScript, AngularJS, Extensible Markup Language (XML), Structured Query Language (SQL), HyperText Markup Language (HTML), Cascading Style Sheets (CSS), and Simple Network Management Protocol (SNMP). The contractor shall employ modular design for developing the software. The contractor shall reuse code when possible to shorten development and maintenance time, but that code must be made available to the Government in its original form.

The contractor shall provide system operations support in accordance with section ‘3.2.12 System Administration’ to support software design and development. The contractor shall provide programming and administration support for PostgreSQL and H2 databases. The contractor shall build and administer OpenShift Origin and Red Hat OpenShift Container Platform for both development and production purposes, as well as Kubernetes. The contractor shall interact with directory servers, Jenkins, JBoss Enterprise Application Platform, Selenium, Keycloak, Git Servers, and Red Hat Single Sign-On.

3.2.4 Software Testing

The contractor shall develop test plans and procedures to test the functionality of operational and/or support laboratory software. The contractor shall perform software testing. Testing at the lowest level possible will be utilized to minimize risks.

3.2.5 Software Integration

The contractor shall provide software development support for system integration, including applications development, installation, and testing. Integration support shall conform to specified environments and be performed in land-based facilities and on operational platforms. The contractor shall provide support to develop and utilize simulators to emulate communications between the software under development and any devices and/or computers being integrated with it as directed by the government. The contractor shall ensure the software supports successful system integration.

3.2.6 Software Documentation

The contractor shall support the writing or revision of documentation for new and modified software to include the following documents: Software Version Description (SVD), System/Subsystem Description Document (SSDD), Software Design Description (SDD), Database Design Description (DBDD), Software Test Plan / Description (STP/D), Software Test Report (STR), Software User Manual (SUM), Interface Design Description (IDD), Link Management Interface (LMI) IDD, software source code, scripts, and build scripts.

3.2.7 Graphics Support/Human Systems Integration (HSI)

The contractor shall provide graphic design and HSI support to create iconography and imagery for graphical user interface that is compliant with ISO 9241 (reference ISO/FDIS 9241-391:2016) and the SPAWAR Style Guide (referenced). All images will be property of the government and all files must be stored on government computers.

3.2.8 Naval Change Request (NCR) Database

The contractor shall maintain a Naval Change Request (NCR) database in accordance with the Configuration Management Plan or the SDP, e.g. Link Management System (LMS) & External Data User Interface (EDUI) Software Development Plan (SDP) for NTCDL SDP (reference NTCDL-SDP-7004-0.1).

3.2.9 Local Configuration Control Board (LCCB)

The contractor shall provide administrative and technical support to the Software LCCB for software and documentation. The contractor shall review NCRs and assure proper action is recorded, and that configuration status accounting records are accurate.

3.2.10 Software Installation

The contractor shall support the installation of system software on both at-sea and shore-based sites. The contractor shall perform pre-installation testing and checkout, software installation, post installation testing, and delivery of software and supporting documentation.

The contractor shall obtain certificates from proper authorities for the purposes of development, testing, and installation.

3.2.11 Training and Technical Assistance

The contractor shall prepare new and/or update existing training materials for the operation of the designated hardware, software and support systems. The contractor shall provide training for maintainers and operators of the systems. The contractor shall provide technical assistance to operational systems worldwide.

3.2.12 Systems Administration

The contractor shall provide systems administration for computers, network devices, peripherals, printers, and similar devices as specified by the government. The contractor shall have and maintain Cybersecurity Workforce (CSWF) or appropriate Cyber IT certification of IAT Level 2 (or equivalent Cyber IT level) and be a System Administrator of Record (SAR). The SAR shall comply with all relevant SSC Pacific, SPAWAR, Navy, and Department of Defense requirements and obligations for the position. The contractor must have a SAR who is CSWF (or equivalent Cyber IT) qualified to administer a mainstream or extended support Microsoft Windows client operating system as well as an equivalent to CompTIA Linux+ (the same person need not do both). Refer to DoD 8570.01-M, Information Assurance Workforce Improvement Program, and SSCPACINST 5239.5, Cybersecurity Workforce Policy, for DoD-approved cybersecurity workforce certificate appropriate for each category and level, and appropriate operating system certification for cybersecurity technical positions. The provisions contained within SECNAV M-5239.2, Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual, and DoDD 8140.01, Cyberspace Workforce Management, will supersede DoD 8570.01-M as directed by the SSC Pacific Cybersecurity Office.

3.3 Test and Evaluation (T&E)

3.3.1 Independent Software Evaluation and Support

The contractor shall conduct independent evaluations and/or reviews of designated system and software developer’s processes and products. The contractor shall provide support to the Government developers to assist in the development and efficient implementation of software systems.

3.3.2 System Evaluation and Support

The contractor shall develop, modify, and/or evaluate procedures to fully test and evaluate the capabilities and functions of systems, sub-systems, modules, interfaces, logistics, hardware and software in order to determine system operational effectiveness and suitability, and to identify areas of technical risk. The contractor shall develop test plans, test tools and scenarios to accomplish test and evaluation of new products and changes to existing systems. The contractor shall participate in system design reviews and test readiness reviews.

3.3.3 Test Plans and Procedures

The contractor shall develop, modify, evaluate, and verify Test and Evaluation Master Plans (TEMP), test plans and test procedures structured to test systems. In performance of this work, the contractor shall use system design requirements, e.g., Capability Development Document (CDD), Capabilities Production Document (CPD), and individual System Performance Specifications (SPS). The contractor shall provide test support to verify proper operation of the systems and the interfaces to all other systems associated with the system under test. The contractor shall support tests performed on systems. Contractor support shall be compatible with project T&E processes i.e., those defined in references SECNAVINST 5000.2E, DoD Instruction 5000.74, and DoD Instruction 5000.02.

3.3.4 Test Resources

The contractor shall develop, modify, evaluate, verify, and schedule test equipment, test tools, and test facilities. In addition, the contractor shall deliver the services necessary to conduct test and evaluation of systems in a multi-platform operational environment. The contractor shall provide support to develop, test and deliver solutions for software and/or operating system issues as required to support Fleet operations. The contractor shall provide support to develop, modify, and/or evaluate and utilize testing tools and facilities as necessary to fully test and evaluate operational systems.

3.3.5 Testing

Utilizing government provided or contractor developed plans, procedures and resources, the contractor shall conduct testing in development laboratories, at land based test facilities or at operational sites as directed by the government.

The contractor shall collect and analyze data on system equipment. The contractor shall participate in development testing to minimize risk of problems during integration testing and evaluation activities.

The contractor shall provide support to perform necessary modeling and simulations designed to evaluate system technical performance for those test cases that cannot be accomplished during operational scenarios or actual operations.

The contractor shall evaluate and recommend the scope of testing for Commercial Off-the-Shelf (COTS) and NDI hardware/software incorporated within designated Navy systems.

The contractor shall investigate, document and support resolution of system problems encountered during integration and evaluation testing.

3.3.6 Software Documentation

The contractor shall review software documentation to ensure documents reflect the software requirements used to develop the software. The contractor shall document discrepancies between requirements and the developed software. The contractor shall review documents such as the SVDs, Functional Description Documents (FDDs), SSDDs, SDD, DBDD, STPs, STDs, and STRs, SUMs, Software source code, scripts, and build scripts.

3.3.7 Configuration Management

The contractor shall review configuration documents to ensure they accurately reflect the configuration of the developed software. Discrepancies shall be documented. The contractor’s configuration management review shall include, but not be limited to, a review of program source code, scripts, build scripts, and other software and documentation. The contractor shall conduct technical reviews and configuration audits, and shall participate in software Engineering Change Proposal (ECP) technical meetings.

3.3.8 Post Installation Testing

The contractor shall support system testing after the installation of new or upgraded system software on both at-sea and shore-based sites. The contractor shall review recorded message traffic in order to extract data and perform data analysis on the findings. The contractor shall support Fleet exercises and experimentation.

3.4 Cybersecurity

Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DoN/Navy cybersecurity requirements. The contractor shall ensure compliance with Cybersecurity and information systems security protocols throughout the course of software development, testing, and integration, including the following:

• The contractor shall ensure Cybersecurity compliance certified by the following designated authorities:

Navy Certifying Authority (Navy CA), Office of Naval Intelligence (ONI), and/or Joint Interoperability Test Command (JITC).

• The contractor shall comply with congressional Cybersecurity mandates such as Federal Information Security Management Act of 2002 (FISMA).

• The contractor shall provide Cybersecurity documentation in support of obtaining Interim Authorization to Operate (IATO), Authorization to Operate (ATO) and/or Certification and Accreditation (C&A).

• The contractor shall perform application and operating system Cybersecurity hardening of the computers and networking equipment to provide compliance with Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG)s and Security Reference Guides (SRG)’s. The contractor shall analyze and interpret STIG’s and SRG’s, and recommend implementation plans of adherence for systems.

• The contractor shall provide Cybersecurity support during the Cybersecurity certification approval process to include attendance of Cybersecurity collaboration meetings and Cybersecurity certification testing.

• The contractor shall support the creation of Cybersecurity documentation developed by the government.

• The contractor shall provide personnel who can be certified as Information Systems Security Officers

(ISSO), Navy Cybersecurity Safety Program (CYBERSAFE), Risk Management Framework (RMF) validators, and data transfer agents (DTA).

• The contractor may be required to access unclassified and classified DISA Enterprise Mission Assurance Support Service (eMASS).

3.4.1 Security Architecture

The contractor shall provide a specialist with Cybersecurity (reference DoD 8570.01-M) work force credentials and a Certified Information Systems Security Professional (CISSP) with Security Architecture specialization. The contractor shall develop architectures for communications systems with embedded TRANSEC (COMSEC). The contractor shall assist in the development of red/black security design and servicing multiple security enclaves. The contractor shall work with an Operational Designated Approving Authority (ODAA) to obtain NSA accreditation/approval of a COMSEC device.

3.5 Program Support

3.5.1 Program Support

The contractor shall develop program documents such as meeting agendas, meeting minutes, program schedules and milestone charts. The contractor shall support the Program Office in the development of position papers, technical summaries and highlights of key program issues, trade-off analyses, and the preparation of technical briefings related to Navy advanced wideband communication systems.

3.5.2 Program Acquisition Documentation Support

The contractor shall assist the Program Office in the development of Program Acquisition Documentation including CDDs, CPDs, Integrated Master Schedules (IMS), cost models, Information Support Plan (ISPs), and other acquisition documents.

3.5.3 Management Support

The contractor shall provide task management support, including analysis of management plans, schedules, and progress/status reports. The contractor shall support project schedule development and maintenance. The contractor shall analyze developed schedules.

The contractor shall not request, and shall not analyze “proprietary information” in the reports of other contractors without express written consent of the submitting contractor, signed by an officer of the submitting contractor’s company, who is authorized to bind his company contractually. Proprietary information includes, but is not limited to, financial reports and data such as invoices, business system reviews, business rates, or rate structures; or any other documentation carrying a legend warning that proprietary data is contained in the document. In the event that proprietary documents are submitted to the contractor, they shall immediately, and without reading them, provide all copies to the Contracting Officer’s Representative (COR). The COR will contact the submitting contractor to resolve whether the proprietary markings are legitimate and future documents are to be submitted directly to the COR, or whether the markings were applied in error and the documents can be analyzed by the contractor performing this contract. The contractor shall participate in management and technical meetings and provide minutes of those meetings.

The contractor shall review software and systems engineering documentation and design of the other vendors. The contractor shall provide a liaison between the vendor and the government.

3.5.4 Risk Management

The contractor shall participate in all Risk Management processes. The contractor shall perform risk identification and risk assessment. The contractor shall make risk mitigation recommendations relative to the testing and evaluation of system software. The contractor shall use accepted SPAWAR risk management tools, procedures, and reporting processes in performance of this requirement (reference PR-RSK-1000026). The contractor shall develop and use a risk management database for software and systems engineering, which will be used for the duration of the development effort.

3.5.5 Configuration Management

The contractor shall provide configuration management system support, including tracking of all new and changed operation or support software and documentation, to ensure reliable configuration management for all software and documentation. The contractor shall adhere to the NTCDL CMP (reference NTCDL-CMP-4001P-1.0) and the LMS & EDUI SDP (reference NTCDL-SDP-7004-0.1) to perform configuration management. Software developers shall maintain configuration management on all code, including program source code, scripts, build scripts, and other software documentation, slides and notes utilizing the government approved procedures. The contractor shall use government approved Configuration Management Processes. The following elements define the functions of configuration management, applicable to this requirement:

a. Configuration identification

b. Technical Review

c. Configuration Audit

d. Configuration Control

e. Configuration Status Accounting

3.5.6 Integrated Product Teams & Meetings

The contractor shall participate in designated IPTs to review system software and/or hardware designs and/or specifications, and to identify the impact on the testing and evaluation of the new or modified system. The contractor shall participate in meetings and teleconferences to support software activities.

3.5.7 Laboratory Operations/Support

The contractor shall provide maintenance and technical support to operate and maintain Software Engineering Integration and Test (SEIT) laboratories, e.g., laboratory operations, equipment integration, equipment maintenance and repair, systems administration and maintenance, logistics and inventory management.

The contractor shall aid in the development and maintenance of standard laboratory operating procedures (reference Secure Room SOP) IAW established DoD Guidelines, develop and implement inventory control procedures for hardware and software, monitor security, and ensure that all site personnel are adequately trained therein.

3.5.8 Land Based Test Facility (LBTF) Support

The contractor shall provide engineering support for system LBTFs, including assistance in the determination of the most economical and best technical approach for installing and maintaining systems required to perform the Software Support Activity (SSA) roles.

3.5.9 Equipment Integration

The contractor shall develop, integrate and test system software in government owned laboratories. This shall include test and evaluation of equipment interfaces and functions. The contractor shall provide the hardware and support software required for development and maintenance of system operational software.

3.6 Radio Frequency (RF) Engineering

The contractor shall provide RF engineering services that require in depth RF knowledge and skill set based in advanced wideband communications and information operations systems. The contractor shall provide RF engineering design and analysis for NTCDL, CDLS TR, CDLS, TCDL, as well as general CDL systems. The contractor shall use Link Budget software to quantify link performance, calculate free space loss, and automate the process of planning radio links.