N6449820R4008-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

Amendment 0003 is issued to update the Level of Effort Chart, Labor Categories Key/Non Key Personnel Requirements, and the CSWF Matrix in Section C; add CDRL A022 Softw are Development Plan; add NAVSEA Clause C-227-H007; delete Attachment 1 Declaration of Non-Collusion Certification; add NAVSEA Clause L-227-H002 Softw are Development Plan; add Subfactor 3C – Softw are Development Approach under Technical Evaluation Factor 3 “Softw are Development Plan” to the solicitation; update Clause 52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment (AUG 2020); and respond to submitted Requests for Information (RFIs).

The hour and date specified for receipt of Offer is not extended from 28 August 2020 4PM EST.

FAILURE TO ACKNOWLEDGE THIS AMENDMENT WITH SUBMISSION OF YOUR PROPOSAL MAY RESULT IN REJECTION OF YOUR OFFER.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 51

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 11-Aug-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N6449820R4008

X 9B. DATED (SEE ITEM 11)

17-Jun-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

11-Aug-2020

CODE

NAVAL SURFACE WARFARE CENTER PHILA

CODE 0222, MICHELE EVANS

267-990-4646, MICHELE.EVANS1@NAVY.MIL

5001 SOUTH BROAD STREET

PHILADELPHIA PA 19112

N64498 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6449820R4008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 0001

Amendment 0001 Requests for Information (RFIs):

1. In reference to Page 27/182, Table 1, of the RFP, will the Government add the word “or” between each certification requirement and degree/education requirement in the “Baseline Qualification” column of Table 1?

RESPONSE: Page 27, Section C, Statement of Work, Table 1 has been revised.

2. In reference to Page 28/182, Section C, Table 1, in the CSWF table, instead of Technician, Engineering III, it says Technician Engineering II. Will the Government please confirm that Engineering III is correct?

RESPONSE: Page 28, Section C, Statement of Work, Table 1 has been revised to correct Technician Engineering II to Technician Engineering III.

3. In reference to Page 28/182, Section C, Table 1, in the CSWF table, Welder (23960) was omitted from the CSWF table. Will the Government please add this to the table?

RESPONSE: Page 28, Section C, Statement of Work, Table 1, has been revised to add Welder.

4. In reference to Page 163/182, Section L.2, will the Government allow the use of 10 point Times New Roman font in tables/charts?

RESPONSE: Page 163, Section L.2, has been revised to include Times New Roman Font Size 10 for all tables, charts, diagrams, or graphical material.

5. In reference to Page 163/182, Section L.2, Section L, 1st Paragraph states: “Proposals shall be prepared on standard 8-1/2” by 11’ paper, set at single-spaced with 1” width spacing, 0” left and right indent and a single blank line before and after each paragraph. The font shall be Times New Roman with a font size of 12 throughout the document unless otherwise specified in these instructions.” Since the Technical Proposal is page-constrained, please confirm the use of no smaller that 8-point size for tables, diagrams, charts, or graphic material.

6. In reference to Page 163/182, Will the Government modify this guidance to allow an exception for diagrams, charts/tables, or graphic material for a font size as low as 10-point size?

7. In reference to Page 163/182, Section L.2.1, Glossary of abbreviations and acronyms is excluded from page count. Is a Glossary of Abbreviations and Acronyms required, or optional at the discretion of the offeror?

RESPONSE: Glossary of abbreviations and acronyms are at the discretion of the Offeror.

8. In reference to Page 163/182, Section L.2.1, Past Performance References are excluded from page count.

However, Volume V. Factor 4 – Past Performance applies a 10-page limit to the past performance volume.

Please clarify.

RESPONSE: Section L has been revised. Past Performance references are excluded from page count.

9. In reference to Page 164/182, Section L, Page 164-165 displays a table under L.3-Proposal Content and organization, Volume 5-Factor 4- Past Performance indicates a 10-page Limit, and page 163 L.2.1 under “the following are not included in the page limitations” shows item e. Past Performance References. Please clarify that the latter statement constitutes no page count for the Past Performance volume.

RESPONSE: Section L has been revised. Past Performance references are excluded from page count.

10. In reference to page 169/182, Section L.3.5, given that, this is a MAC and subcontractor workshare will not be fully determined until issuance of a task order, would the government accept past performance from subcontractors who we believe may complete at least 30% of the work?

RESPONSE: In accordance with Section L.3.5, Past Performance, the Offeror shall list no more than five

(5) relevant contracts performed by the Prime Offeror or a major proposed Subcontractor (any entity proposed to perform 30% or more of the total proposed contract value for the purpose of this solicitation) within the last three (3) years, whether completed or not, including Federal, State and Local Government and private sector contracts.

11. In reference to Page 173/182, DFARs 252.215-7012 REQUIREMENTS FOR SUBMISSION OF PROPOSALS VIA ELECTRONIC MEDIA (JAN 2018), states: “The offeror shall submit all volumes of the proposal via the following electronic media: CD-ROM or DVD.” This conflicts with the instructions on page 164, which states that electronic delivery of proposals must be via DoD SAFE. Please clarify.

RESPONSE: DFARs Clause 252.215-7012 has been revised to state electronic delivery of proposals must be via DoD SAFE.

12. In reference to Page 177/182, NAVSEA Clause L-227-H001 SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT EXPERIENCE (NAVSEA) (OCT 2018) Item (b) says this description is not to exceed thirty (30) pages; however, page 164, Section L.3, allows 60 pages for FACTOR 3 – SOFTWARE DEVELOPMENT. Is it 30 pages each, for Subfactor 3A and 3B, for a total of 60? Please confirm.

RESPONSE: NAVSEA Clause L-227-H001 SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT EXPERIENCE (NAVSEA) (OCT 2018) has been revised to Sixty (60) total pages.

13. In reference to Page 26 & 44 of 182, Section C Paragraph 12.1, this section states that all proposed personnel shall be U.S. citizens with or having the ability to obtain a SECRET clearance. Clause C-222-

H0001 (page 44 of 182) addresses the use non-U.S. citizens for shipboard work. These two clauses appear to be in conflict. Would the government please clarify?

RESPONSE: All proposed personnel shall comply with the security requirements in Section 12 of the Statement of Work. Clause C-222-H0001 provides guidance, if during the performance of the contract, a contractor needs to request utilizing personnel who is not a US citizen.

14. In reference to Page 29-35/182, Labor Category Requirements, LGT2: For the minimum experience, should “weapons systems” be “HM&E systems” as shown in in LGT3?

RESPONSE: Minimum experience for Logistician II (LGT2) has been revised to deleted “weapons systems” and add “HM&E systems”.

15. In reference to Page 27/182, Section12 Personnel, will the Government please confirm the total hours for the Key Category, ENGINEER, SYSTEMS IV* (ESY4) Gov’t-Site, are correct at 45,705?

RESPONSE: The total hours for Key Category, Engineer, Systems IV (ESY4) GOV Site are correct at 45,705.

16. In reference to Page 165/182, page 165 identifies 1 hard copy is required for Volume V, Factor 4. Please confirm this is a typo and all submissions are to be electronic.

RESPONSE: Page 165 has been revised to delete the submission of a hard copy for Volume V, Factor 4.

17. In reference to Page 164-165/182, Page 164-165 displays a table under L.3-Proposal Content and organization. Volume 5-Factor 4- Past Performance indicates hard copy is required. Page 164 L.2.2-Hand delivery of proposals indicates an electronic delivery. Is the Past Performance volume electronic delivery only or hard copy also?

RESPONSE: Page 165 has been revised to delete the submission of a hard copy for Volume V, Factor 4.

18. In reference to Page 179/182, Page 179, Section M, 1st Paragraph states: “The Government will evaluate the effectiveness of each Offeror's technical approach to address the Scenarios regarding, a) Shipboard Alteration Process; and b) Machinery Control System Cybersecurity, and perform the requirements in the solicitation as stated in Section C.” Please confirm that only the relevant portions of Section C will be included in the response to a) and b).

RESPONSE: The Offeror does not have to submit a third item providing information to perform the requirements as stated in Section C, Statement of Work. The Offeror shall submit a response to Factor 1A in accordance with Solicitation Section L 3.2.1.

19. In reference to Page 176/182, Section L-219-H001 SUBMISSION OF SMALL BUSINESS SUBCONTRACTING PLAN (NAVSEA) (JAN 2019) states, “Offeror shall submit as part of its proposal a subcontracting plan in accordance with the clause entitled "Small Business Subcontracting Plan" (FAR 52.219-9) (Deviation 2018-O0018). The plan shall include a five percent (5%) goal for small disadvantaged business concerns or a detailed explanation as to why the goal cannot be included in the plan.

Since FAR 52.219-9 (a) states “This clause does not apply to small business concerns,” can the government please clarify that no Small Business Subcontracting Plan is required if the offeror is small for Small Business Concerns under NAICS 336611?

RESPONSE: NAVSEA CLAUSE L-219-H001 has been removed.

20. In reference to Page 176/182, Page 176 L-219-H001 SUBMISSION OF SMALL BUSINESS SUBCONTRACTING PLAN (NAVSEA) (JAN 2019), requires a small business subcontracting plan, and a 5% goal for SDB utilization. Neither section L nor M reflects any indication of where this should be included or how it will be evaluated. Can the Government please clarify the requirement?

21. In reference to Page 176/182, The RFP references submission of a SMALL BUSINESS

SUBCONTRACTING PLAN. Would the government clarify the desired location/proposal volume for inclusion of this plan?

22. In reference to Page 163/182, Section L.2.1, is an OCI mitigation plan required for all offerors, or only in cases where the offeror has identified a real or perceived OCI?

RESPONSE: An OCI Mitigation Plan is required when an Offeror has identified a real or perceived OCI.

23. In reference to Page 3/182, Section B, for purposes of completing Section B for submission, is the

Labor LOE estimate total inclusive of fee, or is the Offeror to add fee on top of the stipulated amount per CLIN?

RESPONSE: The Labor LOE estimate is inclusive of fee. The Offeror shall breakout Cost & Fee per

CLIN.

24. In reference to Page 29/182, Section C, Page 29 invokes Clause 52.237-3 Continuity of Services (Jan 1991), since this is a ship repair and maintenance contract (NAICS 336611) the SCA is generally not applicable, and the IDIQ/MAC nature of this vehicle makes it difficult to establish a steady workforce. Will the government remove this clause or clarify how it will be used under an IDIQ vehicle?

RESPONSE: FAR Clause 52.237-3 Continuity of Services is not included in the Solicitation. Reference in Paragraph 29 has been removed.

25. In reference to Page 166/182, Section L.3.1.1 Transmittal/Cover Letter, The Offeror shall provide its most recent DCAA and DCMA rate reports (i.e. Final/Established Indirect Rates, Approved Provisional Billing Rates (PBR), Forward Pricing Rate Agreement (FPRA), etc.).” Will the DCAA/DCMA rate reports be required for the Offeror only or for the Offeror and any proposed subcontractors?

RESPONSE: The Offeror shall submit information for Prime and any proposed Subcontractors. The Prime Contractor is responsible for ensuring that Subcontractors provide the information required to the Government.

AMENDMENT 0003

Amendment 0003 is issued for the following:

a. The Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

b. CDRL A022 Software Development Plan has been added to Section C, Statement of Work, Paragraph 4.22.

c. CDRL A022 Software Development Plan has been added to NAVSEA Clause C-227-H-006 and Section J.

d. NAVSEA Clause C-227-H007 has been added to Section C incorporated by Full Text.

e. Attachment 1 Declaration of Non-Collusion Certification has been deleted.

f. NAVSEA Clause L-227-H002 has been added to Section L incorporated by Full Text.

g. Subfactor 3C Software Development Approach under Technical Evaluation Factor 3 Software Development Plan has been added to Section L and Section M.

h. NAVSEA Clause M-227-H001 has been revised to add Subfactor 3C Software Development Approach.

i. FAR Clause 52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment has been updated (AUG 2020) and added as full text to Section K.

j. Respond to the following Requests for Information (RFIs):

26. Would the Government consider removing the CSWF Baseline requirements for the Program Manager (MANP2) labor category, given that all program manager work is to be performed at contractor site, and this person will have no access to government site IT assets?

RESPONSE: MANP2 CSWF requirements have been removed. Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

27. For the Computer Programmer IV (14074) labor category, the Minimum Education requirement is a

BS in Computer Science, Electrical Engineering, or Computer Engineering from an ABET program.

However, the CSWF (advanced/master) requirement is a Graduate Degree. Would the government please reconcile these requirements by changing the CSWF proficiency level to Intermediate/Journeyman?

RESPONSE: Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

28. ESY4: Targeted experience in the Navy’s material procurement procedures seems out of place for a graduate degree engineer. Offeror recommends deleting this requirement.

RESPONSE: Labor Category ESY4 has been removed from the solicitation. Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

29. ANP1: Would the government consider expanding the minimum education requirements to read

“bachelors degree in a related field from an accredited university”?

30. Would the government verify that there are no government site hours for the following LCATs:

Engineer, Systems II (ESY2), Computer Programmer IV (14074), and Specialist, Configuration Management III (SCM3)?

31. Would the government consider a BS Degree and additional years of experience in lieu of a graduate degree for the ESY4 position?

RESPONSE: Labor Category ESY4 has been removed from the solicitation. Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

32. Would the government consider adding labor categories for SISS1, SISS2, SISS3, ISSM1, ISSM2, ISSM3, FQNV2, and FQNV3 in order to satisfy the requirements of SOW Section 3.4?

RESPONSE: Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

33. On page 46, the RFP states “the contractor is responsible for providing an experienced Safety Inspector/Fire Marshal who will accomplish daily Inspections” yet there is no labor category for either.

Would the government consider adding the relevant labor category(ies)?

34. Would the Government consider an experience equivalency in the form of 15 years of Program

Management experience in place of the CCNA, CAP, Security+, or Program management professional certifications?

35. There do not seem to be an appropriate labor category for quality assurance personnel. Would the Government consider adding a quality assurance specialist labor category?

36. With regards to the Key Personnel Labor Category: Program/Project Manage, would the Baseline Qualification for Program Management Professional (PgMP) proposed as “Pending”, be acceptable?

37. With regards to the “Program/Project Manager” position, the “Task Area” identify Sections “3.1, 3.3.

3.5, and 3.6”. However, the “Baseline Qualifications” specify requirements for “task Area” Section 3.2 and 3.4. Could the Government please clarify.

38. The CSWF Certification requirements for the Systems Engineer IV key labor category seems overly restrictive due to the fact that the generally accepted CSWF certification, as defined by DoD Directive 8570 for IAT Level II and IAM Level I and SECNAV M-5239.2 Department of Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual, is the CompTIA Security+ certification. The Navy’s Credential Opportunities Online (COOL) Website https://no-click.mil/?https://www.cool.navy.mil/usn/cswf/index.htm, for example, does not list a systems engineer IV specifically. Additionally, when combining this overly restrictive certification requirement with the Target Experience requirement of ten years of experience with Navigation Systems and HME systems and equipment, any prospective bidder other than an incumbent currently performing this exact work while holding these certifications would be hard pressed to have such a person in their employ or even be able to recruit such a person. Furthermore, the listed CWSF certifications (CISSP, CISM, GSLC, and CASP) are all advanced level cyber security certifications and yet the Target Experience does not mention any work experience related to cyber security. In our experience, only people who have a career focus on cyber security possess these types of cyber certifications. We respectfully request that the Government reconsider its stated CWSF Certification requirements for this labor category.

39. The Systems Engineer IV requires an ABET accredited Graduate Degree and this seems to be a very restrictive requirement. Of the 812 institutions with ABET approved degrees only 42 institutions have any ABET approved Master’s level degreed programs. For example, there are only 5 institutions with ABET accredited Computer Engineering or Systems Engineering degrees at the Master’s level. Will the government consider removing the ABET accreditation for the Graduate Level degree or making the requirement for an ABET approved Bachelor’s Degree with a Graduate level degree?

40. Labor categories : Computer Programmer II and IV - the requirement of CSSLP or CISSP or ECSP or

Secure C++ seems restrictive. Typically an individual performing software development does not possess a CSSLP or CISSP certification. Also we have never heard of the Secure C++ cert and can't find it specifically referenced as SECURE C++ online anywhere but at least it would be relevant for someone doing programming. Can the Government please clarify?

RESPONSE: Labor Categories, Level of Effort, Key/Non-Key Personnel Requirements and CSWF Matrix in Section C have been revised.

41. In citing the target experience of several labor categories [Technician, Engineering VI (30086), Material Coordinator (21030), and Engineer III (E3)], experience necessary with “ordnance equipment and systems” and “ordnance management” is required. However, in the SOW and in 3.0, Requirements, there is no mention of “ordnance” support requirements. Since this solicitation is oriented toward software engineering support for shipboard systems, and especially for Navigation Systems and H&ME monitoring system related equipment, does the Government also require support for ordnance-related equipment and systems?

RESPONSE: All references to ordnance requirements have been removed.

42. In reference to Page 3/182, Section B, for purposes of completing Section B for submission, is the Offeror to breakout Cost & Fee?

RESPONSE: No. Cost & Fee will be established at the Task Order level.

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

NOTES

1. CONTRACT TYPE:

It is the intent of the Naval Surface Warfare Center Philadelphia Division (NSWCPD) to award more than one contract as a result of this solicitation. NSWCPD reserves the right to make one or more awards based on the number of acceptable proposals received and the availability of funding. One (1) or more Cost-Plus-Fixed-Fee (CPFF) Indefinite-Delivery, Indefinite-Quantity (IDIQ) contract(s) are expected to result from this RFP. The resultant contract(s) will also contain provisions for Task Orders to be awarded on a fixed price basis when feasible.

2. SET-ASIDE:

This requirement is being procured as a Total Small Business Set-Aside.

3. MULTIPLE AWARDS:

The minimum value of services (including Cost-Plus-Fixed-Fee) that must be ordered from each awardee will be $500. The minimum shall be satisfied by the issuance of the first Task Order issued under each resultant contract award.

4. PERFORMANCE VS NON-PERFORMANCE BASED MEASURES:

For Completion CLIN 0003 and FFP CLIN 0004, performance vs. non-performance based determinations will be made at the Task Order level and documented appropriately at that time with performance-based approaches being utilized to the maximum extent practicable.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0005

The CLIN extended description has changed from:

Technical Data in support of Line Items 0001 through 0004 in accordance with Contract Data Requirements List (DD Form 1423) contained herein. NSP: Not Separately Priced.

To:

Technical Data in support of Line Items 0001 through 0004 in accordance with Contract Data Requirements List (DD Form 1423) contained herein. NSP: Not Separately Priced.

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

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been added by full text:

C-227-H007 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (OCT 2018)

(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall be delivered to the Government for concurrence under CDRL A022 and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior Government concurrence.

(b) The SDP shall, at a minimum:

(1) 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 Std. 12207:2017;

(2) Contain the information defined by ISO/IEC/IEEE 15289:2017, section 7.3 “Plan - generic content” and Table 2 “Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software Life Cycle Process.” In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted for this contract;

(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;

(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE Std. 12207:2017 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;

(5) Adhere to the characteristics defined in ISO/IEC/IEEE 15289:2017 section 6.1 “Life-cycle data characteristics,” as appropriate;

(6) Be in accordance with the framework defined in IEEE Std. 12207:2017, including, but not limited to, defining 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;

(7) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with ISO/IEC/IEEE 15289:2017 Section 7.3, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.

(End of text)

The following have been modified:

STATEMENT OF WORK

Statement of Work (SOW) for Modernization and Life Cycle Engineering Support

For Cybersecure Machinery Control Systems & Networks

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Department 50, which is responsible for Cybersecure Hull, Mechanical & Electrical (HM&E) Control Systems & Networks.

1.0.2 This Contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied.

1.0.3 Government / Contractor Relationship

(a) The services to be delivered under this Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

(b) The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence

(c) Contractor personnel under this Contract shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

(d) Employee Relationship:

1) The services to be performed under this Contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

2) Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

(e) Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship.

Accordingly, entitlements and benefits applicable to such relationships do not apply.

(f) Notice. It is the Contractor's, as well as the Government's, responsibility to monitor Contract activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1) The Contractor should notify the Contracting Officer in writing within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the estimate in time by which the Government must respond to this notice to minimize cost, delay, or disruption of performance.

2) The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

1.1 BACKGROUND

The mission of NSWCPD Department 50 is to protect and transition HM&E technology throughout the acquisition phases to the U.S. Navy Active and Reserve Fleet, and to support sponsors of Navy Modernization Programs. The acquisition phases include: Advance planning, Research and Development (R&D), ship check, surveys, assessments, fabrication, prototype/proof-in installations, final design shipboard installation, testing, lessons-learned gathering, and close-out.

Throughout the acquisition phases, NSWCPD develops and executes Ship Changes (SC) and Ship Alterations (SHIPALT) utilizing the Alteration Installation Team (AIT) process to upgrade and maintain system and equipment readiness of Navy HM&E and electronic systems in a cost-effective and timely manner.

Programs currently supported include, Instrumentation and Sensor Systems; HM&E Control Systems (of the following classes: DDG 1000, LCS, LDP; CVN; DDG 51; CG, LHA, LHD; LSD, FFG, and MCM), Onboard Trainer; Casualty Control Automation; HM&E Enterprise Info Systems; HM&E Info Systems Technology; Mission Critical Interior Communications Data Networks; Ships Navigation, Ship Control & Integration Bridge Systems;

and CVN Networks, Navigation & Ship Controls.

1.2 SCOPE OF WORK

This Contract is to support NSWCPD Department 50 with its work on Modernization Programs and in its capacity as the In-Service Engineering Agent (ISEA) for various HM&E systems and equipment. The programs consist of critical-path Life Cycle Engineering and System Modernization Support for efforts, such as SC/SHIPALTs, as part of key production light-off and testing milestones during Chief of Naval Operations availabilities; timely execution of these installations is crucial to the success of these programs. Additionally, these installs are intricate and affect system arrangement, interface, and distributive systems.

Work includes performance on shipboard and shore-based systems, in the areas of Cybersecure Engineering Support, Integrated Logistics Support, and Quality Assurance Support. The target platforms are primarily U.S.

Navy Surface Ships, Carriers, Submarines and Service Craft. In addition to the Active and Reserve U.S. Navy ships, this Contract will also support HM&E upgrades on Army watercraft, Coast Guard vessels, Foreign Military Sales (FMS) platforms, Military Sealift Command (MSC) vessels, National Oceanic and Atmospheric Administration (NOAA) Vessels, land-based test sites, and other DOD platforms.

The Contractor shall provide all required labor, materials, and resources to integrate and modify shipboard and shore-based systems. Modernization services include fabrication of related components, shipboard installations, material support and Quality Assurance inspection. Services are required to support various levels of ship systems integration. This integration covers component level digital upgrades through system level upgrades. Systems shall include HM&E and Electronic. Requirements and specifications, along with Government furnished Information/Equipment, will be provided per individual Task Order.

2.0 APPLICABLE DOCUMENTS

2.1 MIL-STDS, MIL-SPECS, and Instructions at, http://www.dsp.dla.mil/app_uil/SpecsAndStandards.aspx

2.2 Navy Modernization Program (NMP) Manual SL720-AA-MAN-030 at, https://www.nde.navy.mil/

2.3 NAVSEA Technical Specification 9090-310 (revision) at, https://www.nde.navy.mil/

2.4 NAVSEA Standard Items at, http://www.navsea.navy.mil/CNRMC/SERMC/SSRAC1/standard.aspx

2.5 NAVSEA C9210.4 (revision) - All non-nuclear work on nuclear powered ships must be in strict compliance with the Naval Sea Systems Command Instruction (classified instructions under separate cover)

2.6 Applicable Ship Change Documents (SCDs)/Ship Alteration Records (SARs) provided by NSWC

PHILADELPHIA SME

2.7 Applicable Ship's Installation Drawings (SIDs) and Sketches provided by NSWC PHILADELPHIA SME

2.8 NAVSEA S9AAO-AB-GSO-010/GOS, General Specification for Overhaul of Surface Navy Ships

2.9 NAVSEA S9AAO-AA-SPN-010/GEN SPEC, General Specifications for Ships

2.10 CINCLANTFLT/CINCPACFLTINST 4790.3, Joint Fleet Maintenance Manual (JFFM)

2.11 MIL-STD-1310, (Navy) Bonding and Grounding

2.12 NAVSEA S9300-AW-EDG-010, Electrical Plant Installation Standard Methods (EPISM)

2.13 NAVSEA Technical Publication S9074-AQ-GIB-010/248, Requirements for Welding and Brazing Procedure and Performance Qualification

2.14 NAVSEA Technical Publication S9074-AR-GIB-010/278, Requirements for Fabrication Welding and Inspection, and Casting Inspection and Repair for HM&E, Piping, and Pressure Vessels

2.15 MIL-STD-1689A, Fabrication, Welding and Inspection of Ship Structures

2.16 NAVSEA Technical Publication 59074-AR-GIB-010/1688, Requirements for Fabrication Welding and inspection of Submarine Structure.

2.17 ISO-9001 Quality Systems - Model for Quality Assurance in Design, Development, Production, Installation and Servicing http://www.iso.org

2.18 ISO-9002 Quality Systems - Model for Quality Assurance in Production, Installation and Servicing http://www.iso.org

2.19 Joint Fleet Maintenance Manual (JFMM) – CINCLANT/CINCPACFLTINST 4790 (series).

2.20 NAVSEA Fleet Modernization Program (FMP) Management and Operations Manual (NAVSEA SL720-AAMAN010/020) (series).

2.21 MIL-STD-480: Configuration Control - Engineering Changes, Deviations and Waivers

2.22 General Specification for Overhaul of Surface Ships (NAVSEA S9AA0-AB-GSO-010) (series)

2.23 Technical Specification 9090-310 (series).

2.24 MIL-M-38784: Manuals, Technical: General Style and Format Requirements.

2.25 MIL-P-24534: Planned Maintenance System: Development of Maintenance Requirement Cards, Maintenance Index Pages, and Associated Documentation.

The Contractor shall reference and utilize the latest version available when performing tasks within this SOW.

3.0. REQUIREMENTS

3.1 Engineering Analysis: NSWCPD Department 50 provides oversight, inspection, certification and repair recommendations for various shipboard systems. For this effort, the Contractor shall:

3.1.1 Ship Checks - assist with onboard ship evaluation and assessments in preparation for the execution of system installations and upgrades. Duties include reviewing existing drawings, verification of equipment locations, determining cable management requirements and interfacing with the applicable Planning Yard to support Ship Installation Drawing development. Finding shall be documented and delivered in accordance with CDRL A014, Pre-Installation Site Survey Results.

3.1.2 Technical Data Packages – assist with the development of Technical Data Packages in relation to the planning and execution of shipboard alterations. Duties include the creation of Functional Block Diagrams, Wiring Tables, Equipment Specifications and Interface Design Documents. Proposed drawings shall be delivered in accordance with CDRLs A009 and A018, as applicable.

3.1.3 Ship Installation Drawing Reviews – assist with the review of Ship Installation Drawings received from the Planning Yard. Duties include verifying that the Ship Installation Drawings are accurate and reflect the guidance provided from the Technical Data Package. All discrepancies shall be noted and communicated to the Planning Yard through Liaison Action Requests (LARs) and captured in accordance with CDRL A009.

3.1.4 Failure Review Boards – shall assist with the preparation and support of Failure Review Boards. Duties include participating in any associated technical or project related teams. Also, tasks include the compiling of existing system documentation, development of risk assessments and failure analysis reporting. When applicable, provide CDRL A010.

3.1.5 Ship Change Documents – assist with the development and review of Ship Change Documents in relation to shipboard alterations and upgrades. Duties include reviewing the documentation for technical and programmatic accuracy, confirming the recommended fielding plan supports the most current ship availability schedule and ensuring the Cost Benefit Analysis correlates to the cost estimate.

3.1.6 Liaison Action Requests – create, review and respond to Liaison Action Requests (LARs) in relation to shipboard installations and system configuration updates. Duties include initiating LARs to request the Planning Yard to develop Ship Installation Drawings, review LARs from the Planning Yard requesting system information for interfacing alterations and responding accordingly.

3.1.7 Specification Reviews – support development and review of system and equipment specifications. Duties include developing and updating specifications due to system modifications. Also, the review of all specifications for technical accuracy is required.

3.1.8 System Troubleshooting – participate in system assessment and evaluation in relation to reported issues from the Fleet. Duties include attempting to replicate the issue in a land based test facility and validate potential resolutions. Shipboard support could be required to assist Ship’s Force and Regional Maintenance Centers with the determination of the root cause.

3.1.9 Fleet Support Coordination – support coordination efforts in relation to Fleet assistance requests. Duties include capturing specific details on the request; tracking hours expended and follow-up communication until the issues are resolved. Fleet support requests could be related to system failures, operational questions, maintenance support, supply support and logistics updates.

3.1.10 Land Based Test Site Support – support with the continued operation and maintenance of land based test sites. Duties include configuring equipment to support system testing and fleet support validation efforts.

3.2 Software Development in Support of Modernization Efforts: NSWCPD Department 50 provides software engineering support related to various shipboard systems. There are a variety of programming languages and system platforms that are associated with the required system design and development tasking. For the following areas, the Contractor shall:

3.2.1 Programmable Logic Controllers – provide engineering and programming support in relation to

Programmable Logic Controllers (PLC). Duties include software development utilizing various PLC programming methods, participation in code reviews and supporting system integration testing efforts.

Developed code shall be delivered in accordance with CDRL A019.

3.2.2 Embedded Software - provide engineering and programming support in relation to embedded computing devices. Duties include software development on various embedded computing platforms, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.2.3 C++ Programming Language - provide engineering and programming support in relation to C++ associated software applications. Duties include software development, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.2.4 Java Programming Language - provide engineering and programming support in relation to Java associated software applications. Duties include software development, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.2.5 Windows Operating System Programming - provide engineering and programming support in relation to the Windows Operating System programming environment. Duties include Operating System modifications, Information Assurance implementation, the application of security patches, software development, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.2.6 Linux Operating System Programming - provide engineering and programming support in relation to the Linux Operating System programming environment. Duties include Operating System modifications, Information Assurance implementation, the application of security patches, software development, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.2.7 VXWorks Operating System Programming - provide engineering and programming support in relation to the VXWorks Operating System programming environment. Duties include Operating System modifications, Information Assurance implementation, the application of security patches, software development, participation in code reviews and supporting system integration testing efforts. Developed code shall be delivered in accordance with CDRL A019.

3.3 Alteration/Ship Change Installation Support: NSWCPD Department 50 provides on-site shipboard alteration, upgrades, and/or modernization support to other agencies. Government personnel serve as On-Site Installation Coordinators (OSIC) and lead a team of Contractor-personnel to install systems and components in accordance with drawings and specifications. To support these type of activities, the Contractor shall:

3.3.1 Research requirements for HM&E Control, Ship Control, Navigation, Integrated Bridge Controls and Networking system equipment alterations, upgrades, or modernizations. Research and assistance includes the gathering of engineering data, drawings and specifications, and the development of execution Plans of Action & Milestones (POA&Ms), "white paper" technical studies, cost estimates, and preparation of engineering technical documents including Ship Change Documents (SCDs), Selected Record Drawings (SRDs) and Quality Assurance Workbooks (QAWBs). POA&Ms shall be delivered in accordance with CDRL A005, and QAWBs shall be delivered in accordance with CDRL A006.

3.3.2 Perform engineering analysis in preparation for shipboard configuration changes, which includes conducting ship checks, arrangement of and review of detailed drawings, and assessing the scope of the installation requirements. This may include installations of refurbished components salvaged from decommissioned ship assets, and back-fitting more supportable equipment in place of unsupported items

3.3.3 Assist with the resolution of Planning Yard and installing-activity Ships Installation Drawing (SID) and ILS comments, and update drawing packages to reflect as-found (built) conditions. Contractor shall develop instructions and drawings for installations. Contractor shall identify and resolve compatibility issues with other ships systems or subsystems interfacing with proposed SCDs.

3.3.4 Propose design alterations and develop test procedures for SCDs, based on research and test results, and submit to NSWCPD for approval.

3.3.5 Update and/or create ILS, as required, if changes to original material or configuration are made by overhauls, upgrades, modernizations, or installations. Contractor shall perform ILS updates/development for new equipment, components and systems and deliver CDRLs A009, A013, A015, A017, and A018, as applicable.

3.3.6 Perform system ship checks, identify diagrammatic and labeling requirements, update information for existing and newly installed systems or modified systems to assist in maintaining accurate configuration control of Engineering Operational Sequencing System (EOSS), and associated drawings such as Ship Selected Record Drawings (SSRDs). Contractor shall ensure EOSS is in agreement with SSRDs with regard to valve numbers and associated figures.

3.3.7 Support System Operational and Verification Testing (SOVT) during ship availabilities to validate full system performance and operation.

3.3.8 Deploy Alteration/SC teams to support major Modernization Programs for industrial installations and test the new technologies’ performance in the existing platforms.

3.3.9 Integrate new technologies into existing ship HM&E and electronic systems; test the newly integrated technologies and deliver CDRL A015.

3.3.10 Procure material required for fabricating, assembling, installing, and conducting the testing for each applicable ship class as defined by the design guidance package, including NAVSEA approved drawings.

3.3.11 Assign a Contractor's Team Leader (Manager, Engineer or designee) to attend a "team leader meeting” with NSWCPD program/ISEA/SME representative for review of Alteration/SC Installation requirements prior to an installation. Contractor shall prepare a draft POA&M that lays out the installation schedule prior to team leader meeting; be prepared to discuss all aspects of installation including material status, shipping schedule, installation requirements, proposed financial costs, Quality Assurance, and safety concerns; coordinate schedule information with NSWCPD, ship's force, and other activities as necessary to ensure proper support is available and interference or delays are minimized. Contractor shall deliver CDRL A008.

3.3.12 Provide redlined drawing packages (if applicable) to the Government On-Site Install Coordinator (OSIC) and/or NSWCPD Program Manager, ISEA or SME not later than ten (10) days after completion of each installation. Redlined drawing packages shall be delivered in accordance with CDRL A009.

3.4 Research, Development and Cybersecurity Supporting Modernization Efforts: NSWCPD Department 50 participates in Research, Development, Test and Evaluation (RDT&E) projects, which include efforts to replace obsolete equipment with updated technology and Cybersecurity initiatives. Contractor support is required during all phases of the project, including requirements analysis, prototyping, hardware design, software development and final product testing. The Contractor shall:

3.4.1 New Product Research: Conduct a thorough study of existing technologies and products to support the project. The research phase includes determining product specifications, production costs and a production time line. The research also is likely to include an evaluation of the need for the product before the design begins to ensure it is a functional product that customers want to use. Findings shall be documented in CDRL A001.

3.4.2 New Product Development: Support efforts related to the actual development based on the requirements and ideas created during the research phase. Efforts are in regards to electrical engineering, software development and system design.

3.4.3 Develop Risk Management Framework (RMF) package documentation required for Authority To Operate (ATO)-submission in accordance with DoD/NAVSEA directives, which includes the…