N00024-17-R-5216_Final_Solicitation.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 14 Aug 2017

X

A X B X C X D

EX

X

G F 82 - 87

88 - 122 X H 123 - 133 simone.brightmon@navy.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

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

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

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

DO-03 1 133

(If other than Item 7)

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

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

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

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N00024 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 5 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.1.5 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

SIMONE L BRIGHTMON 202-781-4188

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 14

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

15 - 39 40 - 41

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

42 - 45 46 - 48

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 49 - 52 X

SPECIAL CONTRACT REQUIREMENTS

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

57 - 80

PART II - CONTRACT CLAUSES

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

N0002415NR46120

5. DATE ISSUED

15 Jun 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N00024-17-R-5216

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

CLIN

Number

1 Lot

Navy ECDIS SW 1.0 Production Build

CPIF

Navy ECDIS Software 1.0 (Production Build) Completion Task

SOW 4.0

Note A NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PURCHASE REQUEST NUMBER: N0002415NR46120

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

OPTION ESS in Support of CLIN 0001 Engineering Support Services (ESS) for Navy ECDIS Software 1.0 (Production Build) Level of Effort (LOE)

SOW 5.0

Note B, C, E, and F

CPFF

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002AA

2,841 Hours

OPTION Engineering Services Year 1 Engineering Services in Support of Navy ECDIS Software 1.0 (Production Build) Level of Effort (LOE) Note B, C, E, and F

0002BA

2,841 Hours

OPTION Engineering Services Year 2 Engineering Services in Support of Navy ECDIS Software 1.0 (Production Build) Level of Effort (LOE) Note B, C, E, and F

OPTION Travel and ODC

COST

Travel and Other Direct Costs (ODC) in support of CLIN 0002 Note C and D

SOW 6.0

Data

Data for CLIN 0001 Not Separately Priced (NSP) Note G

SOW 7.0

NET AMT

OPTION Navy ECDIS SW 1.1 Maintenance Build Navy ECDIS Software 1.1 (Maintenance Build) Engineering Services Option Period 1 Level of Effort (LOE)

SOW 5.0

Note B, C, E, and F

1001AA

14,204 Hours

Navy ECDIS Software 1.1 (Maintenance Build) Engineering Services Year 3 Option Period 1 Level of Effort (LOE) Note B, C, E, and F NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

1001BA

Navy ECDIS Software 1.1 (Maintenance Build) Engineering Services Year 4 Option Period 1 Level of Effort (LOE) Note B, C, E, and F NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

COST

Travel and ODC in support of CLIN 1001 Option Period 1 Note C and D

SOW 6.0

Data Rights/ Licenses

FFP

OPTION Data Rights/ Licenses Note C and H

SOW 8.0

NET AMT

OPTION Navy ECDIS SW 1.2 Maintenance Build Navy ECDIS Software 1.2 (Maintenance Build) Engineering Services Option Period 2 Level of Effort (LOE)

SOW 5.0

Note B, C, E, and F

2001AA

Navy ECDIS Software 1.2 (Maintenance Build) Engineering Services Year 5 Option Period 2 Level of Effort (LOE) Note B, C, E, and F NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

2001BA

Navy ECDIS Software 1.2 (Maintenance Build) Engineering Services Year 6 Option Period 2 Level of Effort (LOE) Note B, C, E, and F NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

COST

Travel and ODC in support of CLIN 2001 Option Period 2 Note C and D

SOW 6.0

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contact, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term “residual dollar amount” shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ B-2-0007 LIMITATION OF COST/LIMITATION OF FUNDS (NAVSEA) (SEP 1990)

The clause entitled "LIMITATION OF COST" (FAR 52.232-20) or "LIMITATION OF FUNDS" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Applicable CLIN(s): 0001, 0002, 0003, 1001, 1002, 2001, and 2002

HQ B-2-0013 PAYMENT FOR ENGINEERING SERVICES AND SUPPORT – ALTERNATE I (NAVSEA) (JAN 2008)

(a) Invoices for engineering services and overtime shall contain the name(s) of engineer(s), date(s) and place(s) of performance, and a brief description of the services performed. This information may be included in the Comments tab of the applicable WAWF document. Each invoice shall be accompanied by a copy of the authorization for services and the original certification of performance. These documents may be attached to the invoice as described in the Invoice Instructions in Section G. A copy of each invoice shall be furnished to the applicable NAVSEA/DRPM/PEO code identified in Section C under Engineering Services.

(b) Invoices for subsistence and transportation shall be supported by a statement of actual costs incurred by the Contractor and claimed to be reimbursable and shall be in such form and reasonable detail as required by the cognizant Defense Contract Audit Agency (DCAA). The Government shall make provisional payment after submission of each invoice and statement of costs. At any time prior to final payment, DCAA may audit the invoice(s) and statement(s) of costs, as appropriate.

(c) Each provisional payment for subsistence and transportation costs shall be subject to reduction to the extent any amount included in the related invoice and statement of costs is found not to be reimbursable under the support item(s) and shall also be subject to reduction for overpayment or to increase for underpayment on preceding invoices. Any disputes under this requirement shall be determined in accordance with the clause of this contract entitled "DISPUTES"

(FAR 52.233-1).

(d) Separate invoices shall be submitted for selected replacement repair parts subsequent to the establishment of prices therefor in accordance with SECTION C of this contract.

Applicable CLIN(s): 0002, 1001, and 2001

HQ B-2-0014 PAYMENTS OF FEE (S) (COMPLETION) (NAVSEA) (MAY 1993)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, "fixed fee" in cost-plus-fixed-fee type contracts for completion and phase type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal to Offeror to Fill-in percent (Offeror to Fill-in %) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, in accordance with the clause of this contract entitled "LIMITATION OF FUNDS" (FAR 52.232-22) or "LIMITATION OF COST" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with paragraph (c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

Applicable CLIN(s): 0001

HQ B-2-0015 PAYMENT OF FEES(S) (LEVEL OF EFFORT – ALTERNATE I) (NAVSEA) (MAY 2010)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts for level of effort type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable, and shall be paid at the hourly rate(s) specified above per man-hour performed and invoiced. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

Applicable CLIN(s): 0002, 1001, and 2001

HQ B-2-0020 TRAVEL COSTS – ALTERNATE I (NAVSEA) (APR 2015)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs determined to be allowable, allocable and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer or their duly authorized representative, as advised by DCAA.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

Applicable CLIN(s): 0003, 1002, and 2002

HQ B-2-0023 CONTRACT SUMMARY FOR PAYMENT OFFICE (COST/FIXED PRICE) (FEB 1997)

This contract includes the following mixture of cost reimbursement and fixed price line items:

Item Type

0001 CPIF

0002, 1001, 2001 CPFF

0003, 1002, 2002 COST

1003 FFP

SECTION B NOTES

NOTE A - INCENTIVE FEE INSTRUCTIONS FOR CLIN 0001

Note: Upon award, the successful Offeror's proposed maximum and target fee percentages, if less than the solicitation stated thresholds, will be incorporated in the paragraph below and in FAR clause 52.216-10 INCENTIVE FEE in Section I.

Minimum fee shall be zero percent (0%). Maximum fee shall be eleven percent (11%). Target fee shall not be greater than nine (9%). Additionally, these fee maximums apply to all subcontractors when CPIF type subcontracts are proposed.

(1) The target cost, target fee amounts shall be based upon the actual cost the Contractor provides. Average hourly rate is determined by including all allowable costs (including Facilities Capital Cost of Money (FCCM), if applicable). Fee/hour is calculated on cost less FCCM (if applicable). (If FCCM is proposed please add needed columns.)

INCENTIVE FEE TABLE

INCENTIVE FEE TABLE*

Hourly Rates Totals

QTY

(HOURS)

Min Fee/Hrs (MinF)

Target Fee/Hrs

(TF)

Max Fee/Hour

(MF)

Target Cost/Hrs (Rate)

Min Fee (Hrs*MinF)

Target Fee (Hrs*TF)

Max Fee (Hrs*MF)

Target Cost (Hrs*Rate)

*Offerors shall complete this table.

(i) The CPIF target cost for CLIN 0001 shall be entered in the Target Cost column in the INCENTIVE FEE TABLE above. The Target Cost is determined by multiplying the allowable hours worked (Qty (Hrs)), including subcontractor hours, corresponding to each CLIN by the target cost per hour (Target Cost/Hour (Rate). The target cost per hour (Target Cost/Hour (Rate)) shall include all proposed cost (including FCCM (if proposed) and subcontractor costs) for the corresponding CLIN. Fees charged by subcontractors shall also be included in the target cost.

(ii) The CPIF target fee for CLIN 0001shall be determined by multiplying the allowable hours worked (Qty (Hrs)), including subcontractor hours, for the corresponding CLIN by the target fee per hour (Target Fee/Hour (TF)) from the INCENTIVE FEE TABLE. This shall be entered in the Target Fee (Target Fee (Hrs * TF)) column of the INCENTIVE FEE TABLE above.

(iii) The share ratio for the CPIF portion of the fee structure is 50/50 (50% Government and 50% Contractor) for both under-runs and over-runs. The fee earned under the CPIF portion of the fee structure will be based on the total allowable cost incurred by the contractor in comparison to the final target cost for CLIN 0001. See the Incentive Fee clause (FAR 52.216-10) in Section I of this contract for further information on how the target cost and target fee are determined and the fee earned is calculated.

(iv) Final Costs & Fees. Actual resulting fee will be calculated at the end of the POP for CLIN 0001 at the CLIN level. Final cost and fee are shown in the following table.

Delivered Hours

Actual Cost Per Hour

Actual Cost (A*B=C)

Final Target Incentive Fee

Incentive Fee Share Line Adjustment

Computed Incentive Fee (D+E=F)

Total (C+F=G)

A B C D E F G

NOTE B - Applicable to CLINs 0002, 1001, and 2001 - These CLINs are Cost Plus Fixed Fee (CPFF). The Offeror shall propose no more than eight percent (8%) for fixed fee. The available fixed fee amount shall be calculated as a percentage of cost, less FCCM. The Government will issue Technical Instructions in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 2015) included in Section H of this contract. This is an estimated amount of labor hours, and does not indicate that the Government will necessarily require this amount or any at all.

CLIN Hours Section B Fixed Fee Amount

Section B Fixed Fee Amount/Hours

0002 5,682 * *

1001 28,408 * *

2001 28,408 * *

* Offerors shall complete this table. The Offeror shall divide the proposed Section B fixed fee amount by the associated hours and insert the result rounded to the nearest penny in the appropriate column in the table above. The Offeror shall propose no less than zero percent (0%) and no more than eight percent (8%) for fixed fee. The proposed Section B Fixed Fee Amount shall be in whole dollars. The Government reserves the right to unilaterally correct any mathematical errors.

NOTE C - Option item to which the option clause in SECTION I-2 applies and which is to be supplied only if and to the extent said option is exercised. Applicable CLINs: 0002, 0003, 1001, 1002, 1003, 2001, and 2002.

NOTE D - Applicable to CLINs 0003, 1002, and 2002 - Offeror is to propose the Government specified Estimated Cost only amount indicated in the table below.

CLIN Travel Material Total Estimated Cost

0003 $70,000 $0 $70,000 1002 $70,000 $0 $70,000

2002 $70,000 $0 $70,000

NOTE E - Applicable to CLINs 0002, 1001, and 2001 - Level of Effort Items in accordance with NAVSEA Provision 5252.216-9122 entitled “LEVEL OF EFFORT” to the contract. The hours shown in the schedule are the hours allocated for each CLIN to be performed within the period established under Section F of the contract entitled “DELIVERIES OF PERFORMANCE” and include both prime and subcontracts hours.

NOTE F- Applicable to CLINs 0002, 1001, and 2001 - The Government will issue Technical Instructions (TIs) in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 1999) included in Section H of this contract. The Contractor shall not perform any efforts under these items until and unless tasked by the Government. The Offeror is required to price man-hours per option year. This is an estimated amount of labor hours, and does not indicate that the Government will necessarily require this amount or any at all. These CLINs are Cost Plus Fixed Fee (CPFF). Any allowable Travel, Other Direct Costs (ODC) or Incidental Material associated with the performance of the TIs will be reimbursed with the associated Travel/ODC CLINs.

NOTE G - Applicable to CLIN 0004 (Data CLIN). The item is NOT SEPARATELY PRICED (NSP).

NOTE H – Applicable to CLIN 1003, Data Rights/ Licenses - The Offeror shall fill this in with their proposed price for those rights which the Offeror is willing to sell in accordance with Section L.4.1 paragraph (7) which states - the Government desires at least Government Purpose Rights (GPR), as defined at DFARS 252.227-7013 and - 7014, in all non-commercial technical data and computer software. Where less than GPR are being provided to the Government, the Government requests that the Offeror provide the price of buy-out for GPR for those rights which the Offeror is willing to sell. The Offeror shall not include the prices of the buy-out options in the Technical Approach, Volume II, of the proposal. Rather, for each technical data/computer software deliverable which is being offered with less than GPR, prices for conversion of the deliverable data rights to GPR shall be included in CLIN 1003.

Section C - Descriptions and Specifications

STATEMENT OF WORK (SOW)

1.0 SOW Scope

This Statement of Work (SOW) addresses the Software Design Agent support required to produce, maintain, and upgrade the Navy Electronic Chart and Display Information System (ECDIS) Software (SW).

This SOW specifies the requirements for the production, integration, documentation, testing and delivery of the Navy ECDIS SW. The requirements in this SOW shall be applied to the initial Navy ECDIS SW Production Build (CLIN 0001) as well as the follow-on Maintenance Builds (CLINs 1001 and 2001), if options are exercised.

2.0 RESERVED

3.0 SOW Applicable Documents

3.1 Military Specifications, Standards, and Handbooks

MIL-STD-1472G Human Engineering dated 11 Jan 2012

3.2 Department of Defense (DoD) and Other Government Documents

Software Requirements Document (SRD) for the U.S. Navy Electronic Chart Display and Information System (NAVY ECDIS), Rev 1.0 (with Change 1), 13 JAN 2016 Requirements Traceability Matrix for the U.S. Navy Electronic Chart Display and Information System (NAVY ECDIS), Rev 1.0 (with Change 1), 13 JAN 2016 Configuration Management Plan for PEO IWS 6.0 Command and Control Directorate, Rev 4, 8 Sep 2014 NAVSEAINST 9410.2A, Naval Warfare Systems Certification Policy, 24 Aug 2012

OPNAVINST 9420.2A, Navy Electronic Chart Display and Information System Policy and Standards, 31 Oct 2014 PEO IWS / NAVSEA 05H Technical Review Manual, Version 2.0, 18 Dec 2009

DoD Open Systems Architecture, Contract Guidebook for Program Managers, v.1.1, Jun 2013

Electronic System Technical Manual for Navy Electronic Chart Display and Information System, Technical Manual Contract Requirement (TMCR) No. SNIPP-160030-000, 18 Dec DoDI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test and Evaluation (RDT&E), 28 May 2015 DoD Anti-Tamper (AT) Guidelines, Version 2.0 DoDI 8500.01, Cybersecurity, dated 14 March 2014 DoDI-8510.01 Risk Management Framework for DoD information Technology dated 12 March 2014

3.3 Non-Government Documents

ASTM F1166-07 Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities

IEEE 1044-2009 Standard Classification for Software Anomalies IEEE/EIA Std. 15289-2015 ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)

IEEE/EIA 12207-2008 Systems and software engineering -- Software life cycle processes NIST SP 800-64 Rev 2 National Institute of Standards and Technology (NIST) Security Considerations in the System Development Life Cycle NIST SP 800-53 Rev 4 NIST Security and Privacy Controls for Federal Information Systems and Organizations

Security Technical Implementation Guides (STIGs) Open Web Application Security Project (OWASP), Code Review Guide ISO 9001:2015 Quality Management Systems Requirements

3.4 Use of Standards

The Contractor shall use the following standards in descending order of importance:

a. Standards as specified in 3.1, 3.2 and 3.3.

b. Commercial standards developed by international or national industry standards bodies that have been widely adopted by industry. Examples of widely adopted standards include SQL for databases (e.g., SQL for databases ANSI ISO/IEC 9075-1, ISO/IEC 9075-2, ISO/IEC 9075-3, ISO/IEC 9075-4, ISO/IEC 9075- 5), HTML for presentation layer (e.g., XML 1.0 www.webstandards.org), XML for data transfer, Web services for remote system calls.

c. Standards adopted by industry consensus-based standard bodies and widely adopted in the market place.

d. De facto standards (those widely adopted and supported in the market place).

3.5 Contract Security Classification

The Contractor shall comply with Department Of Defense Contract Security Classification Specification, DD Form 254, attached hereto.

The Contractor is required to have an Active SECRET Facility Clearance for performance on this contract. The Contractor must have a Safeguarding Level of SECRET. The Government’s Program Manager will designate certain Contractor personnel required to have and maintain at a minimum a final SECRET security clearance.

The Contractor requires access to “For Official Use Only (FOUO)” which shall be managed in accordance with DoD M-5200.01 Volume 4, DoD Information Security Program: Controlled Unclassified Information (CUI) of 2/24/2012

The contractor requires access to classified source data up to and including SECRET in support of this contract.

Classified material generated in support of this contract shall be classified in accordance with the DD 254.

Automated Information Systems (AIS) must be certified and accredited by the Defense Security Services (DSS) prior to processing classified information.

The Contractor may be required to fabricate, modify, operate or store classified hardware, such as processor hard drives. All classified data and hardware will be protected in accordance with (IAW) DoD 5220.22-M, National Industrial Security Program Operation Manual (NISPOM) and DSS.

The Contractor, and any subcontractors or supplier, shall also comply with all requirements set forth in the DD-254.

The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical Assistance Agreements (TAA), etc. required by the International Traffic in Arms Regulations (ITAR). The Contractor shall submit all requests for State Department approvals, licenses, TAAs, etc. to the Program Office for review.

4.0 SOW Requirement for Navy ECDIS SW, CLIN 0001

The Contractor shall produce Navy ECDIS SW in accordance with this SOW. The Navy ECDIS SW shall meet all requirements of the SRD for the U.S. Navy ECDIS. The following requirements apply to the initial Navy ECDIS SW Production Build 1.0 (CLIN 0001).

4.1 Software Development

The Contractor shall develop and implement secure coding and cyber security in accordance with NIST SP 800-64 Rev 2; NIST SP 800-53 Rev 4; the STIGs; DoDI 8500.01, Cybersecurity, dated 14 March 2014; DoDI-STD-

8510.01 Risk Management Framework for DoD information Technology dated 12 March 2014; and the Open Web Application Security Project (OWASP) Secure Coding Practices Reference Guide 2.0.

The Contractor shall develop and implement Anti-Tamper software protection measures, as appropriate, for the case of unplanned loss, to protect Critical Program Information (CPI) and Anti-Tamper Critical Technologies defined by DoDI 5200.39. DoD Anti-Tamper Guidelines, Version 2.0, is available as guidance. Anti-Tamper measures shall deter efforts to reverse engineer, exploit, or develop countermeasures. Anti-Tamper measures shall prevent unauthorized access to critical software functionality regardless of the system configuration.

4.1.1 Open System Architecture (OSA)

The Contractor shall produce the software with an OSA using modular design, standards-based interfaces, and widely-supported consensus-based standards in accordance with the SRD for Navy ECDIS SW paragraph 3.13.

The Contractor shall define, document, and follow an Open Systems Management Plan that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

CDRL A001 Management Plan, Open Systems Management Plan

4.1.2 Human Systems Integration (HSI)

The Contractor shall incorporate HSI principles and design during software design and integration activities in accordance with the SRD for Navy ECDIS SW. Periodic HSI Reviews will be held to allow user feedback into the Human Machine Interfaces (HMI). The Contractor shall develop a Human Systems Integration Program Plan (HSIPP) that describes their approach to develop and manage HSI requirements, elements, and functionalities to ensure the attainment of all HSI objectives. The Contractor shall incorporate the "Department of Defense Design Criteria Standard – Human Engineering" (from MIL-STD-1472G), into the HSI design of Navy ECDIS.

CDRL A002 Human Systems Integration Program Plan

4.1.3 Hardware Integration

The Navy ECDIS SW will be installed on all US Navy Commissioned Ships, Military Sealift Command vessels and Expeditionary platforms. The software will be installed at various shore commands in support of operational units.

This will require the software to operate on a wide variety of hardware configurations. SRD for Navy ECDIS SW Appendix A identifies platform configurations for many of the US Navy ships and Appendix J identifies the minimum expected hardware requirements that the software must operate on. The Contractor shall conduct testing IAW SOW 4.1.7.

The Contractor shall assess the system design defined by the SRD during initial production build, and if required, follow-on Maintenance Builds. The Contractor shall submit a Request for Variance (RFV) to propose any alternate design approaches and planned modifications to the system hardware for successful achievement of the SRD requirements in the event that hardware technology improvements are required to ensure performance of the system.

CDRL A006 Request For Variance (RFV)

4.1.4 Quality Assurance

The Contractor shall provide and maintain a quality management system in accordance with HQ-E-2-0015 QUALITY MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA)(SEP2009) and shall adhere to the quality program controls of HQ-E-2-0014 QUALITY IN SOFTWARE DEVELOPMENT AND PRODUCTION (NAVSEA)(MAY1995). The Contractor shall submit a Quality Assurance Program Plan (QAPP) that documents all of the information, instructions and documentation necessary to produce quality software in complete conformity with contractual requirements. The QAPP shall address the software quality provisions of IEEE/EIA 12207.2008.

The QAPP shall contain measurable quality objectives and the metrics by which they are to be measured. The Navy ECDIS SW shall adhere to the approved QAPP. The QAPP shall be reviewed with each exercised contract option and, if required, revised and resubmitted.

CDRL A003 Quality Assurance Program Plan

4.1.5 Configuration Management (CM)

The Contractor shall prepare and submit a Software Configuration Management Plan. The CM Plan shall describe, at a minimum, the configuration management activities, procedures, and schedule for performing software CM activities; the organization(s) responsible for performing configuration management and activities; and their relationship with other organizations, such as software development and software maintenance. The Navy ECDIS SW shall adhere to the approved CM Plan. The CM Plan shall be reviewed, revised, and resubmitted as required.

A Software Configuration Control Board (SCCB) is to be established to control the software baseline. The SCCB shall be chaired by the Government (PEO IWS 6) and consist of both Contractor and Government representatives.

The SCCB shall discuss and review Software Problem Improvement Reports (SPIRs), review GFE/GFI deficiencies, review Request for Variance. The Government shall schedule the SCCB meeting as needed to address SPIRs. The SCCBs shall be via teleconference and scheduled within five working days of SPIR entry. The Government shall provide a list of SPIRs to be reviewed with each meeting notification.

The Contractor shall be responsible for maintaining the software configuration baseline over the life of this contract.

The Contractor shall use an industry standard distributed Software Configuration Management (SCM) system such as Git or Mercurial for all software production. The initial software baseline shall be established going into FQT, at which time the SCCB shall assume configuration control and no changes shall be implemented without SCCB approval.

The Contractor shall prepare and submit a GFI Deficiency/Change Report of the potential impact of deficient information provided under this contract. The Contractor shall prepare and submit a RFV to obtain authorization to deliver non-conforming material which does not meet the prescribed configuration documentation but is suitable for use or to depart from the contractually-specified configuration documentation for a specific period of time.

CDRL A004 Management Plan, Software Configuration Management Plan

CDRL A005 Government Furnished Information Deficiency Report

CDRL A006 Request For Variance (RFV)

4.1.5.1 Software Deficiency/Problem Corrections

The SCCB shall utilize the Naval Surface Warfare Center, Philadelphia Division (NSWC PD) Information Center Website SPIR database to document and manage all identified software discrepancies. Access to the SPIR database shall be granted to the Contractor for read access of the database. The Contractor shall be provided an editable excel file to forward and/or update SPIRs into the government database. The Contractor shall record all software discrepancies discovered during Contractor Formal Qualification Test (FQT) and provide SPIR file updates within five working days of discovery.

SPIRs can be detected in one of four methods, Analysis, Inspection, Demonstration and/or Test. All SPIR entries shall be reviewed by the SCCB before being entered into the SPIR database by NSWC PD. Data entered shall include: Severity, Priority, State, Analyst, Title, Issue Description, Related Trouble Report(s), Location, Comments/Action, and Status. SPIRs shall include problems interrelated between the Computer Software Configuration Items (CSCIs) and problems related to the overall software architecture. SPIR consequence shall be assessed against the likelihood of occurrence as per NAVSEAINST 9410.2A. SPIR Priority shall be assessed against Probability as per IEEE 1044. All implemented SPIRs must be tested to verify correction prior to software delivery

CDRL A007 Technical Report–Study/Services, SPIR Database Entry File

4.1.6 Software Data Products

The Contractor shall produce and provide data products as detailed in subparagraphs 4.1.6.1 – 4.1.6.9 in support of the Navy ECDIS SW. All data developed shall include Government Purpose Rights (GPR) in accordance with DFARS 252.227-7014. The software data products previously submitted and approved shall be reviewed with each exercised contract option and, if required, revised and resubmitted in support of each Navy ECDIS SW Maintenance Build.

4.1.6.1 Software Development Plan (SDP)

The Contractor shall prepare and submit a Software Development Plan (SDP). The SDP shall define a software development approach appropriate for the computer software effort to be performed under this contract. The SDP shall be in compliance with Section C Clause HQ C-2-0065 Software Development Requirements (NAVSEA)(DEC 2006)(Modified)(SEP 2012), DoDI-STD-8500.01 Cyber Security, dated 14 March 2014 and DoDI-STD-8510.01 Risk Management Framework for DoD information Technology dated 12 March 2014. The Contractor shall follow this SDP for all computer software to be developed or maintained under this effort. The SDP shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build.

The SDP shall define the Contractor’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. 15289-2015 (system) and IEEE/EIA 12207- 2008 (software). The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this contract. 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. The Contractor shall provide this detailed information so the Government can assess whether the Contractor’s approach is viable. 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, at minimum, specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification.

The SDP shall specify the entire software program and the performance characteristics of each CSCI. The SDP shall identify all third party software applications, and insure that the requirements of the application STIG are applied to such third party software application configuration required to by this plan, or submit a Request for Variance of non-conformance. For the purposes of this contract, any non-conformance of Application Security requirements as outlined per the STIGs is considered a variance from the CSCIs, but may be grouped together into a single Request for Variance for closely related STIG requirements relating to specific ECDIS functionality software requirements.

The Contractor shall allocate the Navy ECDIS performance requirements into the CSCIs listed in the SDP.

The Contractor shall be required to maintain the Navy ECDIS SW Requirements Traceability Matrix to further trace lower level software requirements and software testing beyond the SRD for Navy ECDIS SW. The Requirements Traceability Matrix shall be submitted concurrent with the submission of the lower level software requirements documents and software test documents; and in support of the SRR, SSR, PDR, CDR and TRR.

CDRL A008 Software Development Plan (SDP)

CDRL A009 Technical Report–Study/Services, Requirements Traceability Matrix

4.1.6.2 Software Requirements Specification (SRS)

The Contractor shall prepare and submit an SRS for each CSCI. The SRS shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The SRS shall specify the requirements for each CSCI and the methods to be used to ensure that each requirement has been met. Requirements pertaining to the CSCI’s external interfaces may be presented in the SRS or in one or more Interface Requirements Specifications (IRSs) referenced from the SRS. It has also been defined as a complete description of the behavior of the software to be developed. It includes a set of use cases that describe all of the interactions that the users shall have with the software. It also contains functional requirements, which define the internal workings of the software: that is, the calculations, technical details, data manipulation and processing, and other specific functionality that shows how the use cases are to be satisfied. It also contains nonfunctional requirements, which impose constraints on the design or implementation (such as performance requirements, quality standards or design constraints). Each CSCI shall reference the SRS that it implements, and in each subunit shall call out the specific requirement from the SRS that it implements to insure requirement traceability.

CDRL A010 Software Requirements Specification (SRS)

4.1.6.3 Software Version Description (SVD)

The Contractor shall prepare and submit a SVD. The SVD shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The SVD shall identify and describe a software version consisting of one or more CSCIs. It is used to release, track, and control software versions. The SVD shall provide a summary of code changes, a listing of SPIRs corrected in the build, and a list of open deficiencies.

CDRL A011 Software Version Description (SVD)

4.1.6.4 Software Product Specification (SPS)

The Contractor shall prepare and submit an SPS. The SPS shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build . The SPS contains the executable software, source files, and software support information, including "as built" design information and compilation, build (to include information sufficient to reproduce the build environment), and modification procedures, for each CSCI. It is the detailed design and description of Software Items (SI) comprising the product baseline and is analogous to the Item Detail Specification of hardware Configuration Item (CI) in the product baseline of a hardware system. The source files, compilation and build files (such as a Makefile), etc., shall be delivered in the form of a complete SCM repository copy of the current build, with additional documentation in the SPS required as outlined above.

CDRL A012 Software Product Specification (SPS)

4.1.6.5 Software Design Description (SDD)

The Contractor shall prepare and submit an SDD. The SDD shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The SDD shall describe the design of a CSCI. It describes the CSCI- wide design decisions, the CSCI architectural design, and the detailed design needed to implement the software. The SDD shall include a description of software tools necessary to compile and produce an installable, executable copy of the Navy ECDIS SW on a DVD, including: identification of software compilers; a summary of code changes and at a minimum the difference files showing all changes from the baseline or a copy of the SCM for that CSCI at that baseline with the differences being spelled out clearly in the history of the SCM; a list of Windows Services used by Navy ECDIS; and software build procedures. The SDD may be supplemented by the Interface Design Descriptions (IDDs).

CDRL A013 Software Design Description (SDD)

4.1.6.6 Interface Requirements Specification (IRS)

The Contractor shall prepare and submit the IRS. The IRS shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The IRS shall specify the requirements imposed on one or more systems, subsystems, Hardware Configuration Items (HWCIs), CSCI, manual operations, or other system components to achieve one or more interfaces among these entities.

CDRL A014 Interface Requirements Specification (IRS)

4.1.6.7 Software Transition Plan (STrP)

The Contractor shall prepare and submit a STrP. The STrP shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The STrP shall identify the hardware, software, and other resources needed for the life cycle support of the Navy ECDIS SW and describe the Contractor’s plans for transitioning the software to NSWC Philadelphia Division (NSWC PD).

CDRL A015 Software Transition Plan (STrP)

4.1.6.8 Interface Design Description (IDD)

The Contractor shall prepare and submit the IDD. The IDD shall be reviewed and updated, if required, with each Navy ECDIS SW Maintenance Build. The IDD shall describe the interface characteristics of one or more systems, subsystems, HWCIs, CSCIs, manual operations, or other system components. The IDDs shall identify all external interfaces. The documentation shall include details for each message sent by each executable, broken down by word and data element. Each word and data element shall be fully described within the documentation. For interfaces defined by other systems and published in other documents, the IDD shall only reference the other documents.

CDRL A016 Interface Design Description (IDD)

4.1.6.9 Software Delivery

The Contractor shall provide the executables, source code, Application Program Interfaces (APIs), and development tools for any Contractor developed software scripts and software applications not developed exclusively or partially at private expense in accordance with DFARS 252-227-7017. The Contractor shall provide a Government Purpose Rights (GPR) license for all Contractor developed software. The Contractor shall deliver the software to the Government with the developmental elements necessary to allow the Government to generate an installable image or modify any element of the system. The delivery shall support the Government in generating a loadable image and configuring an existing system or a new (never before configured) system such that the system performs the same as the developmental system did during test. The Contractor shall provide assistance during this transition as needed for the Government team to successfully compile, build, load, configure, and operate a newly installed version.

The Contractor shall deliver the initial Navy ECDIS SW 1.0 Production Build once Contractor and Government testing is completed and the software is approved for Full Rate Production. Follow-on Maintenance Builds 1.1 and

1.2 shall be delivered with each exercised contract option once Contractor and Government testing is completed and the software is approved for Navy ECDIS use.

The Contractor shall ensure interoperability of commercial computer software with the OE and shall document any interdependencies (such as minimal revision required) in the appropriate Software Version Description(s) (SVD).

All licensing requirements/restrictions for each Commercial Off-The-Shelf (COTS) product shall be provided as part of the SVD. This documentation requirement shall include delivery of full paid software licenses which provide sufficient rights for the Government to meet and fulfill the needed and necessary Navy ECDIS SW capabilities over its lifecycle.

CDRL A017 Computer Software Product

4.1.7 Software Formal Qualification Test (FQT)

The Contractor shall establish and conduct a robust, comprehensive, and effective FQT program that provides proof the software is in compliance with the technical requirements of the Navy ECDIS SRD and the government approved SRS's and IDDs CDRLs delivered under this contract. The Contractor shall conduct FQT on all of the CSCIs managed under this contract. FQT shall include software unit testing, software integration testing and software system testing. The Contractor shall structure the FQT program to support not only the Contractor's in-plant software testing, but also support Government testing at Navy facilities. Contractor FQT is subject to monitoring by the Government. The Government must be notified a minimum of thirty (30) calendar days prior to any testing event and given the option to witness each event.

The Contractor shall utilize Navy ECDIS SRD compatible hardware for testing and acceptance of Navy ECDIS SW.

Shipboard representative hardware and peripherals for hardware compatibility testing, ECDIS qualified displays for backlight control and color palette testing and external interface testing will be made available at the In-Service Engineering Agent (ISEA) facility at NSWC PD (surface) and Naval Undersea Warfare Center (NUWC) Newport (submarine). The Contractor shall perform the software FQT in accordance with the government approved Software Test Plan and Test Description. The Contractor shall document the FQT results via the Software Test Report. The STP, Software Test Description (STD) and Software Test Report (STR) shall be submitted for the initial Navy ECDIS SW 1.0 Production Build, as well as for each Navy ECDIS SW Maintenance Build.

Once the Contractor has successfully completed all FQT events, the Government shall perform formal Development Testing (DT) on the software at NUWC Newport, RI for submarine platform ECDIS configurations and at NSWC PD for surface platform ECDIS configurations. Once the Government Facilities DT is completed and all required SCCB identified SPIRs are corrected, Shipboard DT will be conducted in-port and underway on selected U.S. Navy platforms to further validate each software builds. Commander, Operational Test and Evaluation Force (COTF) will be conducting independent Operational Test (OT) of the software once the Government DT is successfully completed. The Contractor shall provide personnel to witness government testing at the labs and on the ships.

Personnel should have the required tools and documentation to be able to troubleshoot and document issues found for continuation of test events and to expedite SPIR resolution.

As part of the Contractor’s FQT the software is to be tested by an independent agency such as the U.S. Naval Research Laboratory, Stennis Space Center (NRL, SSC) to ensure the software can properly display of National Geospatial-Intelligence Agency (NGA) data products.