RFP N6449823R40040002 AMENDMENT 0002.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

SEE THE BLOCK 14 CONTINUATION PAGE.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 48

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

16C. DATE SIGNED

BY 13-Feb-2023

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 N6449823R4004

X 9B. DATED (SEE ITEM 11)

19-Jan-2023

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

13-Feb-2023

CODE

NAVAL SURFACE WARFARE CENTER PHILA

CODE 02222, CRAIG WRIGHT

215-897-8275, CRAIG.WRIGHT@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:

N6449823R4004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

AMENDMENT 0002

The purpose of the subject Amendment 0002 is to perform the following:

1. Revise Section C, SOW Section 12.5 Non-Key Personnel, to replace asterisk removed under Amendment 0001 as follows: “Computer Engineer Level III* (EC3).” In regards to the asterisk, this category specifies within the same section the following: “*CSWF position, see Section 12.6.”

2. Revise Section L.2.1 PAGE NUMBERS AND LIMITS to delete the “Quality Assurance Acceptance Letter” bullet point on RFP page 201.

3. Revise Section L.3.2.1 SUBFACTOR A – FACILITIES first paragraph sentence from, “Offerors must demonstrate that they possess or have the ability to obtain facilities and equipment requirements of as specified in Paragraph 14.4 of the Statement of Work.” To “Offerors must demonstrate that they possess or have the ability to obtain facilities and equipment requirements of as specified in Paragraph 14.3 of the Statement of Work.”

4. Revise L.3.2.4 SUBFACTOR D – CORPORATE EXPERIENCE to remove all instances of the word “Modernization.”

5. Section L, Section L.3.2.4 SUBFACTOR D – CORPORATE EXPERIENCE has been updated to replace the requirement for examples to have been performed within the past three (3) years to within the past five (5) years.

6. Section L, Section L.3.3.2 SMALL BUSINESS COMMITMENT PAST PERFORMANCE has been revised to update references of three (3) years to five (5) years.

7. Section L, Section L.3.4 VOLUME IV: FACTOR 3 – PAST PERFORMANCE has been updated to replace the requirement for examples to have been performed within the past

8. Revise Section M.2, EVALUATION APPROACH, FACTOR 1 – TECHNICAL, SUBFACTOR A – FACILITIES, to remove repetition of items already listed under Section L L.3.2.1 SUBFACTOR A – FACILITIES.

9. Update SAM.GOV Notice ID N6449823R4004 for the following:

a. Attachment 4 - DD254

b. Conformed copy of solicitation N6449823R4004.

10. Answer potential Offeror questions received in regards to solicitation N6449823R4004.

The answers to questions received are below:

59. Section L3.2.4 Subfactor D – Corporate Experience (page 205) states that examples of corporate experience should be within the past three years. Will the Government consider extending this period to five years in order for non-incumbents to equally compete?

ANSWER: Section L, Section L.3.2.4 SUBFACTOR D – CORPORATE EXPERIENCE has been updated to replace the requirement for examples to have been performed within the past

60. L.3.4 Volume IV: Factor 3 – Past Performance (page 207) states that past performance contracts must have been performed within the last 3 years. Will the Government consider extending this period to five years in order for non-incumbents equally compete?

ANSWER: Section L, Section L.3.4 VOLUME IV: FACTOR 3 – PAST PERFORMANCE has been updated to replace the requirement for examples to have been performed within the past three (3) years to within the past five (5) years.

61. For requirements of RFP paragraph L-227-H001, SPD please confirm that the requirement for SDP development, paragraphs (a) and (b) applies only at the TO level and not required in proposal response. Also please confirm the paragraph (c) does not apply to our proposal response page limitation.

ANSWER: Confirmed, these SDP development requirements shall be determined and required at the Task Order (TO) level, and are not required for this proposal.

62. On pages 47 and 48 under C-227-H007 Software Development Plan paragraph (b). ISO/IEC/IEEE 15289:2017 has been replaced by ISO/IEC/IEEE 15289:2019. Should ISO/IEC/IEEE 15289:2017 or ISO/IEC/IEEE 15289:2019 be used for development of the

SDP?

ANSWER: The Contractor shall refer to the latest version of this standard when submitting their SDP, which is only required at the Task Order level per the response to Question 12.

63. Page 205 of 224, paragraph L.3.2.4, Section L Paragraph L.3.2.4 of Section L (on page 205 of 224) includes the following sentence, "Offerors shall not provide more than five (5) contract examples to address all of the referenced Modernization Programs." The RFP SOW (Section C) does not reference any specific Modernization Programs. Would the Government provide a list of Modernization Programs that Offerors are to provide corporate experience?

ANSWER: RFP Section L.3.2.4 SUBFACTOR D – CORPORATE EXPERIENCE has been revised to remove “Modernization.” Please refer to the systems and equipment listed in RFP

Section C, SOW Section 1.1.

64. Page 218 of 224, Section L-227-H001 - On page 218 of the RFP, section L-227-H001

SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT EXPERIENCE

(NAVSEA) (OCT 2018), the RFP asks for: "A description of previous relevant experience, within the past TBD at the Task Order Level months in developing software of the similar size and complexity as that required under the statement of work." Describe any previous relevant CMMI® or equivalent model-based process maturity appraisals performed within the past 24 months."

Are the above required for this proposal, or will they be required at the task order competition level? If they are required for this proposal, SOW paragraph 3.2.5 Computer Programming, Software Engineering and Network Support does not define in any detail software development tasking that can be used as a measure of size or complexity. Can the Government provide an example of a software development task?

ANSWER: Software Development plans, as they apply to provision L-227-H001, are not required as part of the base contract solicitation. Software Development Plans will be evaluated at the Task Order Level as required.

65. Page 219 of 224, Section L-227-HOO2 - On page 219 of the RFP, section L-227-H002 SOFTWARE DEVELOPMENT PLAN (NAVSEA) (OCT 2018), the RFP asks for an SDP rationale. This rationale is subject to the page limitations of the technical proposal. Will the government allow this rationale to be submitted as an appendix to the proposal, and not subject to the page limitations?

ANSWER: Provision L-227-H002 is intended for use at the Task Order level when a specific software development requirement exists.

66. Section L.3.2.1: Subfactor A – Facilities (page 203) refers the offeror to Paragraph 14.4, however, there does not appear to be a Paragraph 14.4. Will the Government please clarify?

ANSWER: Reference has been corrected to state Section 14.3 Contractor Facilities.

67. Section L.3.2.4: Subfactor D – Corporate Experience (page 205) states “Offerors should provide specific accomplishment experience in the Programs listed in SOW paragraph 2.”

Paragraph 2 appears to be a list of applicable documents/reference. Will the Government please clarify?

ANSWER: This has been revised to state SOW paragraph 1.1, which lists the programs/systems that are covered under this contract.

68. Section L3.2.4 Subfactor D – Corporate Experience (page 205) states “Offerors shall not provide more than five (5) contract examples to address all of the referenced Modernization Programs”. Will the Government consider increasing the number of contract examples given the large number of systems and programs cover in this solicitation?

ANSWER: The Government will not increase the number of contract examples.

69. Section L.3.2.4 Subfactor D – Corporate Experience instructions 10 And 11 (Page 205) require the contractor to provide all completed task orders for each cited contract and provide their proposed value versus total cost value and their proposed completion date vs. actual completion date. This list could be quite lengthy. Would the Government consider omitting this list of Task Order information from the page limit for Factor 1: Technical?

ANSWER: The list of Task Order information will remain as part of the stated page limit.

70. May the QMS Level 1 and Level II procedures (Page 204) be provided as a separate .pdf attachment to Volume II?

ANSWER: The QMS Level 1 and Level II procedures may be provided as a separate attachment, and this attachment may be omitted from the page count limit.

71. RFP L.3.2.4 Subfactor D Corporate Experience includes a detailed discussion regarding experience in systems listed in SOW 1.1, experience in programs listed in SOW paragraph 2, and eight technical areas of SOW paragraph 3. This Corporate Experience discussion is included in the Technical volume page allocation of 35 pages while the Past Performance page allocation is unlimited. Would the government please consider removing the Corporate Experience discussion from Volume II page allocation?

ANSWER: Under RFP Amendment 0001, the page limit for Volume II has been increased to 50 pages. Therefore, the Government will not remove Corporate Experience from the Volume II page limit.

72. RFP L.3.2.4 Subfactor D Corporate Experience includes a discussion regarding programs listed in SOW paragraph 2, however SOW paragraph 2 is a listing of Applicable Documents.

Would the government please clarify.

ANSWER: Please see the response to Question #67.

73. RFP L.3.2.4 Subfactor D Corporate Experience includes a detailed discussion regarding experience including information for each DO executed. The requirement to detail each DO will require multiple pages for each citation. Would the government please consider removing the Corporate Experience discussion from Volume II page allocation?

ANSWER: Please see the response to Question #69.

74. Paragraph 1.3.2.1 on page 203 SUBFACTOR A – FACILITIES on page 220 refer to paragraph 14.4 of the Statement of Work. Paragraph 14.4 does not exist. Please confirm these sections should refer to paragraph 14.3 on page 34.

ANSWER: Please see the response to Question #66.

75. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON 203 of 224 L.3.2.1 SUBFACTOR A – FACILITIES The Government states "must demonstrate that they possess or have the ability to obtain facilities and equipment requirements of as specified in Paragraph 14.4 of the Statement of Work." Does the Government intend to state that “Offerors must demonstrate that they possess or have the ability to obtain facilities and equipment requirements as specified in Paragraph 14.3 of the Statement of Work."?

ANSWER: Please see the response to Question #66.

76. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON Page 220 of 224 M.2 EVALUATION APPROACH SUBFACTOR A - FACILITIES The Government states "Proposals will be evaluated based upon its possession or the ability to obtain facilities and equipment as specified in Paragraph 14.4 of the Statement of Work." Does the Government intend to state that "Proposals will be evaluated based upon its possession or the ability to obtain facilities and equipment as specified in Paragraph 14.3 of the Statement of Work."?

ANSWER: All references to Section C, SOW Section 14.4 have been revised to state Section 14.3.

77. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON Pages 211-214 of 224 L.2. PROPOSAL

FORMAT 252.204-7019 NOTICE OF NIST SP 800-171 DOD ASSESSMENT

REQUIREMENTS (MAR 2022) (b) Requirement. (1) RFP states (in Section L) 252.204- 7019 (c) (1) the Offeror shall verify that summary level scores of a current NIST SP 800-171 DoD Assessment (...) are posted in the Supplier Performance Risk System (SPRS) (...)

Would the Government like the inclusion of pages 211-214 in Section K - Reps and Certs?

ANSWER: The inclusion of these pages is not required per the solicitation.

78. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON Page 204 of 224 L.3.2.1 SUBFACTOR

A – FACILITIES The Government states "The above information may be submitted as an attachment to the Offerors’ proposal, and the attachment is excluded from the page limit described above.” Does the Government intend those responses to ALL numbered items 1 -3 are to be submitted as attachments and excluded from page count?

ANSWER: Yes, items 1-3 in RFP Section L.3.2.1 Facilities are to be submitted as Attachments and are excluded from the page count.

79. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON Page 219 of 224 L-227-H002 SOFTWARE DEVELOPMENT PLAN Submission of SDP L-227-H002 (b) states Offerors shall also submit an SDP rationale (...) and that the SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 20 pages. Would the Government allow BOTH the SDP and the SDP Rationale to be outside the page limitation of Volume II?

ANSWER: Please see the response to Question #61.

80. Would the government please consider adding an Administrative Assistant to the approved labor category list?

ANSWER: The Government will not add to the approved labor category list.

81. SOW Section 12.5 Non-Key Personnel - Computer Engineers, Page 30, Why are Computer

Engineers asterisked?

ANSWER: The asterisk in Sow Section 12.5 Non-Key Personnel was removed under Solicitation Amendment 0001. However, upon further review, the asterisk has been put back in its original position, with an explanation that these are Cybersecurity Workforce (CSWF) labor categories.

82. L.3.2.4 Corporate Experience, Experience examples, Page 205, five (5) Contract examples are required. No page limit for each is given. What is the page limit per contract example and are these pages part of the technical proposal 35 page limit? Can the contract examples be placed in an appendix?

ANSWER: Please see response to Question #71.

83. How does the Agency plan to evaluate Subfactor A, considering that no manufacturing/shop capability is defined in the SOW or elsewhere in RFP?

ANSWER: The evaluation criteria for Subfactor A, Facilities, are detailed in Sections L.3.2.1 Subfactor A – Facilities, and M.2 Evaluation Approach, Factor 1 – Technical, Subfactor A – Facilities. The latter has been revised.

84. L.3.2.4, 2nd paragraph says what "should" be indicated. Considering evaluation is acceptable/non-acceptable based on minimum requirements, can the Agency confirm it meant to use FAR 2.101 definition of "should" instead of "shall"?

ANSWER: The Government confirms that it meant to use “should.”

85. What is the purpose of Major Subcontractors (L.1, pg 200), considering that they are defined based on total proposed contract value that is not required?

ANSWER: Please use the program ceiling amount of $496,122,347 of which ODCs total $227,784,120.

86. Since no cost proposal is required, is there any requirement in the RFP to support how the offeror will demonstrate capability to meet 52.219-14 (Deviation 2021-O0008), beyond the general representation that one will comply?

ANSWER: No, there is no such requirement.

87. M.2 Subfactor A - Facilities evaluates physical facilities, all of which provide an off-ship/shop work capability. Does Agency require capability to accomplish shipboard work (C.3.3.2.3) be described, and if so, where in Section L is it to be done?

ANSWER: Please see response to Question #83.

88. How will Agency evaluate risk of obtaining resources, facilities and processes for M.2

Subfactor E - Technical and Management Approach, Start-up Plan?

ANSWER: Subfactor E, Technical and Management Approach, item e., Start-up Plan, will be evaluated per the evaluation criteria provided in Section M.2 Evaluation Approach, Factor 1 – Technical, Subfactor E – Technical and Management Approach, item e., Start-up Plan.

89. L.3.2.5 Subfactor E - Technical and Management Approach, c. Subcontractor Management requires Offeror to discuss "...the extent of the subcontractor's involvement in the performance of the contract", but there nothing on how the extent will be evaluated in M.2 Subfactor E - Technical and Management Approach. Will extent of subcontractor involvement be evaluated and if so, in what terms are its size or scale to be described?

ANSWER: Yes, subcontractor involvement will be evaluated as required by the solicitation.

90. L.3.2.4 Subfactor D - Corporate Experience, 3rd para, item 9 requires Offeror to note reference to SOW paragraph number. At the 3rd level are 23 paragraphs and at the lowest level, which varies to 3rd, 4th and 5th levels, are 111 paragraphs. Is it acceptable to Agency to reference at 3rd level (i.e. 3.6.1, 3.2.5, etc.)?

ANSWER: Yes, this is acceptable.

91. Would the Government confirm that L.3.3.2 Small Business Commitment Past Performance requirement does not apply to small business Offerors?

ANSWER: L.3.3.2, Small Business Commitment Past Performance does indeed apply to small business Offerors.

92. RFP Document Page 74 of 224, 2 (g) - Does the Small Business Subcontracting Goal of 20% apply to small business prime Offerors?

ANSWER: Small businesses are exempt from submitting subcontracting plans per FAR 19.702(b)(1).

93. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON and Attachment 1 - Pre Award Survey of

Prospective Contractor Accounting System Checklist Page 178 of 224 Section J, Attachment

1. Would the Government please clarify if Attachment 1 is due at proposal submission and, if so, should it be included in Volume I or is Attachment 1 to be submitted post award?

ANSWER: Attachment 1, Pre-Award Survey of Prospective Contractor Accounting System Checklist, is provided in the event that your company does not have an approved accounting system, as is required for cost reimbursable type contracts. If required, Attachment 1 is due at time of proposal submission, and should be submitted as part of your cover letter.

94. Would the government provide a conformed copy of the RFP with the most recent

Amendment changes?

ANSWER: A conformed copy of the RFP with the most recent Amendment changes has been added to SAM.GOV.

95. Section L: 14.1.4 (page 33) states “The Contractor shall maintain Quality Management

System (QMS) acceptance from NAVSEA 09MP in accordance with NAVSEA Technical Specification 9090-310 (series) (Modernization work only).” Tech Spec 9090-310G (latest) does not require submission or acceptance by NAVSEA 09MP. Will the Government please clarify that should read acceptance by NAVSEA 04RP?

ANSWER: The latest revision of TS 9090-310 is rev H, which now requires QMS approval by NAVSEA 09MP, and generates the QA Acceptance Letter.

96. The RFP states that “QA acceptance letter” is exempt from the page count (Page 201).

However, Section L does not contain a requirement for QA acceptance letters. Are they required? If so, where should they be included?

ANSWER: A Quality Assurance Acceptance letter is not required. The list on page 201 has been updated to remove this reference.

97. RFP N6449823R4004 - 41-43 MAC FOLLOW-ON Page 200 of 224 L.2.1. PAGE NUMBERS AND LIMITS The bulleted list references a Quality Assurance Acceptance Letter as excluded from the page limitations; yet we are unable to locate any reference in the instructions as to where this Quality Assurance Acceptance Letter is to be included. Would the Government clarify in which Volume the Quality Assurance Letter is to be included?

ANSWER: Please see the response to Question #96.

98. L.2.1 (pg 201) excludes Quality Assurance Acceptance Letter, but nowhere in RFP is it requested. Is the letter required and who must acceptance be by? For reference, NAVSEA 04RP (now 09MP) has historically reviewed and approved contractor Quality Assurance systems/manuals.

ANSWER: Please see response to Question #96.

99. L.3.2.2 requires submittal of QMS meeting ASQ/ANSI/ISo 9001:2015 and C14.1.4 (pg 33) lists acceptance from NAVSEA 09MP in accordance with NSTS 9090-310 (series) for modernization work. Is acceptance of QMS required?

ANSWER: Please see response to Question #96.

100. How does the Agency plan to evaluate risk from reliance on experience of subcontractors to demonstrate M.2, Subfactor D - Corporate Experience?

ANSWER: The Government will evaluate Subfactor D – Corporate Experience in accordance with solicitation Section M.2. Subfactor D – Corporate Experience.

The following have been deleted:

AMENDMENT 0001

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Statement of Work (SOW) for Hull, Mechanical and Electrical (HM&E) Machinery and Systems Services

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 Divisions 41, 43, and 45, which are responsible for Auxiliary Machinery Systems, and Hull, Sail, and Machinery Systems, respectively.

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

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

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

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

1.0.4 Employee Relationship:

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

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

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

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

1.0.4.4 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.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email 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 Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

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

Naval Surface Warfare Center, Philadelphia Division (NSWCPD), as the Division's Machinery Engineering Directorate, is the Navy’s agent for the coordination and planning of all the engineering and technical support services for Hull, Mechanical and Electrical (HM&E) machinery and systems. To accomplish this mission, NSWCPD utilizes extensive resources to conduct its business to the best advantage of the Navy, Fleet and other Federal Agency maritime assets. The engineering and technical support services are accomplished in all areas where Foreign Military, U.S.

Navy, and Military Sealift Command (MSC) ships operate and are homeported. These services are accomplished in whole or in phases that minimize interruption in ship operating schedules while maximizing the capacity of Type Commander and NAVSEA agencies to upgrade and modernize systems.

Examples of the HM&E machinery and systems that are supported by the engineering and technical services described under this SOW are provided below.

AUXILIARY SYSTEMS

Auxiliary Machinery & Fluid Systems Auxiliary Machinery Silencing Systems Climate Control & Refrigeration Systems Compressed Air & Gas Systems Fluid Systems Automation Seawater, Chill Water & Combat Support Systems Sonar Systems Steam Systems Submarine Fluid Systems Submarine Life Support Systems Submarine Sail Systems Vertical Launching Systems (VLS)

ELECTRICAL SYSTEMS

400 Hertz and DC Electrical Power Systems Advanced Electrical Power Systems Energy Conversion Systems Gas Turbine Electrical Power Systems Steam and Diesel Electrical Power Systems

HULL & DECK MACHINERY & HABITABILITY SYSTEMS

Amphibious Assault Systems Anchor, Mooring and Towing Systems Aviation & Material Handling and Stowage Boat and Towed Body Handling & Stowage Hull Outfitting & Shipboard Habitability Systems Hydraulics and Steering Systems Shipboard Cranes Underway Replenishment Systems Weapons/Cargo Handling and Stowage Systems

PROPULSION SYSTEMS

Diesel Engine Systems Power Transmission Systems Propulsion Steam Plant Automation Systems Surface Combatant Gas Turbines

1.2 SCOPE OF WORK

The Statement of Work establishes the requirement for non-commercial engineering and technical services to include: design, development, build, and testing support; prototype engineering; technology insertion; development and revision of test specifications and technical documentation; performance and data analysis; system safety and fault analysis; system integration; installation support; computer programming and software engineering; software verification and validation; Integrated Logistics Support (ILS) document preparation and system training development; program management and presentation support; and on-site technical support, alteration services, Integrated logistics, system certification support and staging in support of surface fleet, submarine, and shore-based installations in support of HM&E machinery and systems, other Federal Agency vessels, federally contracted vessels and platforms, selected maritime agency vessels, and select land-based sites.

2.0 APPLICABLE DOCUMENTS

2.1. ASTM-1166, Human Systems Interface for Marine Systems

2.2. NAVSEA S9AA0-AB-GSO-010, General Specification for Overhaul of Surface Navy Ships

2.3. NAVSEA 0902-018 2010 Rev B, General Overhaul Specifications for Deep Diving SSBN/SSN

Submarines (DDGOS), dated 1-Aug-2018

2.4. NAVSEA S9AA0-AA-SPN-010/GEN SPEC, General Specifications for Ships

2.5. NAVSEA SL720-AAMAN_010/FMP, Fleet Modernization Program (FMP) Management & Operations

Manual, dated 15-Apr-2016

2.6. MIL-HDBK-454B, Standard General Guidelines for Electronic Equipment

2.7. NAVSEA Technical Publication S9074-AQ-GIB-010/248, Requirements for Welding and Brazing

Procedure and Performance Qualification (Amend 002)

2.8. NAVSEA S9300-AW-EDG-010, Electrical Plant Installation Standard Methods

2.9. Electrical Workmanship Standards, Portsmouth Naval Shipyard Standard 4855.1 through 4855.6

2.10. MIL-DTL-81927C, Manuals, Technical: General Style and Format of Work Package Concept, dated 26

Nov 1997

2.11. MIL-STD-38784(1), Standard Practice for Manuals, Technical: General Style and Format, dated 1 Dec

2.12. MIL-PRF-87269A, Interactive Electronic Technical Manuals, dated 15 Aug 2000, Data Base, Revisable

2.13. MIL-DTL-24784 06, Manuals, Technical: General Acquisition and Development Requirements, dated

June 2017

2.14. MIL-STD-1689A, Fabrication, Welding and Inspection of Ship Structures (Amend 002)

2.15. MIL-STD-0022, Welded Joint Design

2.16. MIL-STD-882E, System Safety

2.17. MIL-P-24534A (Navy); Planned Maintenance System: Development of Maintenance Requirement Cards, Maintenance Index Pages, and Associated Documentation, dated 7 May 1985

2.18. S0005-AA-GYD-030, Guide for User Maintenance of NAVSEA Technical Manuals, dated 30 Sep 1988

2.19. S0005-AA-GYD-070, Guide for Quality Assurance of NAVSEA Technical Manuals, dated 01 Feb 1991

2.20. OPNAV Instruction 5100.23B, Navy Safety and Occupational Health Manual

2.21. NAVSEA T9074-AS-GIB-010/271, Requirements for Nondestructive Testing Methods

2.22. AWS B4.0, Standard Methods of Mechanical Testing of Weld

2.23. AWS Z49.1, Safety Welding and Cutting

2.24. Standards and Interpretations, Occupational Safety and Health Chapters 1915.14, 1915.15 and 1915.16

2.25. NAVSEA Technical Publication S9074-AR-GIB-010/278, Requirements for Fabrication Welding

2.26. NAVSEA Standard Items

2.27. NAVSEA TS9090-310 (Latest Revision) Alterations to Ships Accomplished by Alteration Installation

Teams

2.28. NAVSEA TS9090-600 Ship Alteration Drawing Preparation

2.29. NAVSEA TS9090-400 Ship Change Document

2.30. IEEE Std 610.12-1990, Standard Glossary of Software Engineering Terminology (ANSI)

2.31. IEEE Std 12207.0-1996, Software Life Cycle Process

2.32. IEEE Std 12207.1-1997, Software Life Cycle Process-Life Cycle Data

2.33. IEEE Std 12207.2-1997, Software Life Cycle Process-Implementation Considerations

2.34. NAVSEA Information Technology Standard Guidance

2.35. ASQ/ANSI/ISO 9001:2015, “Quality Management Systems — Requirements”

2.36. ISO-9002 Quality Systems - Model for Quality Assurance in Production, Installation and Servicing

2.37. COMFLTFORCOMINST 4790.3, Joint Fleet Maintenance Manual at www.submepp.navy.mil/jfmm/index.htm

2.38. NIST SP-800-37, Risk Management Framework for IT and Organizations

2.39. NIST SP-800-53, Security and Privacy Controls for Federal IS and Org.

2.40. DoD 5220.22-M National Industrial Security Program Operating Manual

2.41. DoD 8510.01 Risk Management Framework for Information Technology

2.42. DoD 8570.01-M Information Assurance Workforce Improvement Program

2.43. DoD 8140.01 Cyberspace Workforce Management Requirement

2.44. DoD Cyber Exchange Public, DoD Approved 8570 Baseline Certifications, available https://public.cyber.mil/cwmp/dod-approved-5870-baseline-certifications/

2.45. NAVSEAINST 4720.14E, Temporary Alterations to Fleet Submarines

2.46. NAVSEAINST 4350.2D, Contract Work Onboard Nuclear-Powered Ships, dated 5 Jun 2013

2.47. NAVSEAINST C9210.4A, Changes, Repairs and Maintenance to Nuclear Powered Ships

2.48. NAVSEAINST 4120.8A, NAVSEA Policy for Commonality of Systems, Subsystems, and Components, 22 Sep 2016.

These documents can be referenced at: https://mercury.tdmis.navy.mil unless otherwise noted. The Contractor shall reference and utilize the latest version available unless otherwise noted.

Additional reference documents and applicable standards may be listed on individual Task Orders.

3.0 REQUIREMENTS

The specific services to be provided and required deliverables shall be detailed in the individual Task Orders placed against the contract by the Contracting Officer, and shall be within the parameters of one or more of the tasks listed below. To fulfill Task Orders written under this Contract, the Contractor shall:

3.1 Program Management

3.1.1 Ensure mission responsive, cost efficient management of the cost, schedule and performance goals and objectives of the contract. Plan and conduct Program Review Meetings in accordance with Task Order requirements. (CDRL A001, A002, A003, A016, A019)

3.1.2 Analyze technical goals and facility requirements, and assist the Government in developing proposals to support the research, development, test and evaluation (RDT&E) of HM&E machinery and systems.

3.1.3 Prepare technical reports that document engineering efforts. Reports may be informal summary reports, or drafts or final submittals of formal technical reports, as specified by the Government in accordance with CDRL A004.

3.1.4 Assist in the review of technical documentation, such as specifications, drawings, and procedures, and provide comments relative to established technical objectives. (CDRL A004, A005, B001)

3.1.5 Prepare presentation materials such as view graphs, slide decks and videos, military equipment specifications, equipment acquisition specifications, etc. Provide technical writing and publication support, and related services.

3.2 Engineering and Technical Support Services

3.2.1 Component and System Level Engineering Analysis, Development, and Design

3.2.1.1 Provide engineering, testing, and analysis services to evaluate safety, reliability, maintainability, performance, qualification, and availability, and to identify and develop solutions to engineering, design, and maintenance problems. Performance may occur on-site at Government facilities or at Contractor’s facilities.

3.2.1.2 Provide support for engineering and technical investigations and analyses relating to concepts and designs, focusing on systems engineering, compatibility and operability, and interfaces. Prepare procedures for integration of new installation/alteration projects, including identifying and defining interfaces and relationships between these programs and other DoD systems and subsystems.

3.2.1.3 Develop or review test specifications, and monitor testing of HM&E and associated electronic systems. (CDRL A004, A005)

3.2.1.4 Provide support to develop drawings, field sketches, test memoranda, installation procedures, and maintenance procedures, as required to accomplish the necessary work. (CDRL A004, B001)

3.2.1.5 Provide new, revised or updated documentation reflecting changed configurations.

(CDRL A004, A008, B001)

3.2.1.6 Conduct systems engineering to include fault analysis, detection, and isolation, casualty control, human engineering factors, and operations sequencing capabilities in the ships detail design. Establish detailed maintainability design criteria to minimize the maintenance man-hours required. Calculate and provide available equipment reliability data, such as Mean Time to Repair (MTTR), Mean Time Between Failures (MTBF) and Maximum Corrective Maintenance Time values.

3.2.1.7 Conduct ship assessment engineering visits in support of various material assessment programs. (CDRL A006, A015)

3.2.2 Prototype Engineering

3.2.2.1 Provide engineering services to analyze Non-Developmental Item (NDI)/Commercial

Off the Shelf (COTS) technology insertion, prototype demonstrations and evaluate integration with existing systems and perform system qualification.

3.2.2.2 Develop integrated Operational Evaluations (OPEVALs) and Technical Evaluations (TECHEVALs), planning and necessary ship change documentation (i.e. Ship’s Change Documents (SCDs), Ship Alterations (SHIPALTs), Temporary Alterations (TEMPALTs), Ordnance Alterations (ORDALTs), Field Changes, Alterations Equivalent to Repair (AERs), etc.) for system integration and installation.

3.2.2.3 Establish performance and design specifications for prototype equipment and testing articles.

3.2.2.4 Provide engineering and design services, and analyses, for newly developed or modified COTS systems.

3.2.2.5 Test, evaluate and install prototype equipment in accordance with performance specifications and other applicable requirements as specified in Task Orders.

3.2.2.6 Develop design drawings for installation of shipboard systems, including prototype systems and equipment. (CDRL B001)

3.2.2.7 Design and fabricate models, prototypes and other testing articles to be evaluated in RDT&E efforts.

3.2.3 System Automation

3.2.3.1 Provide engineering services to analyze, develop, design, and support automation of system operation and maintenance.

3.2.4 Graphics Support

3.2.4.1 Prepare graphic materials, such as Plan of Action and Milestones (POA&Ms) and Variant-tree diagrams, in support of engineering programs. (CDRL A019)

3.2.4.2 Develop orientation and presentation materials (i.e., written, viewgraphs, DVDs, Blu-rays, CD-ROM, etc.).

3.2.4.3 Develop layouts, charts, graphs, visuals, and other graphics as needed for engineering drawings, documentation, technical manuals (TMs), and training materials.

3.2.5 Computer Programming, Software Engineering and Network Support (CDRLs A017, A018, A025)

3.2.5.1 Provide analysis and design of computer software systems.

3.2.5.2 Provide software verification and validation services including software system emulation.

3.2.5.3 Develop software and graphical user interfaces (GUIs). Document and test code in accordance with established NSWCPD policy.

3.2.5.4 Develop simulation techniques, real-time software architectures, and graphics screen interfaces.

3.2.5.5 Develop software on communications algorithms. (e.g. TCP/IP, UDP).

3.2.5.6 Develop software on Component Object Model (COM) and Active Template Library

(ATL) programming.

3.2.5.7 Provide server and workstation setup and administration. Personnel performing under this task must meet all applicable Cybersecurity Workforce (CSWF) requirements and provide proof of current (ongoing) certification.

3.2.5.8 Modify and/or develop computer code in the following languages: C/C++, SQL, Java, CMS2, Ada, Visual Basic and Delphi, and other languages as specified on individual Task Orders. Computer programming languages selected for use in all applications shall require approval by the Navy.

3.2.5.9 Develop and deliver documentation for computer software in accordance with IEEE/EIA 12207 requirements. Tailored requirements will be provided by the Navy.

Comments to all source code and any developmental tools shall be provided in a format approved by the Navy.

3.2.5.10 Design, develop, administer, implement, test, modify, and upgrade database maintenance support programs utilizing latest COTS software.

3.2.5.11 Develop and deliver software development plans (CDRL A018) and software products

(CDRL A025).

3.2.5.12 Conduct software development testing and configuration management in accordance with IEEE 12207 and other standards as specified on individual Task Orders.

3.2.5.13 Provide network engineering and technical services as required to support alteration installation as directed by individual Task Orders.

3.2.6 Human Systems Interface and Engineering Risk/Safety Assessment Support

3.2.6.1 Provide engineering services to identify system hazards or safety concerns to machinery and personnel during technology insertion, prototype demonstrations or designs and integration with existing systems.

3.2.6.2 Provide engineering services to identify Human Systems Interface (HSI) during technology insertion, prototype demonstrations or designs and integration with existing systems.

3.2.6.3 Provide engineering services to analyze and quantify system hazards or safety concerns to machinery and personnel for frequency and impact during technology insertion, prototype demonstrations or designs and integration with existing systems.

3.2.6.4 Provide engineering support for technology insertion, prototype demonstrations or designs and integration with existing systems.

3.3 Shipboard, Submarine and Shore-Based Installations

3.3.1 Perform Installation/Repair Planning: Plan and coordinate the use of facilities, equipment, materials and personnel resources necessary to efficiently and effectively accomplish installations and repairs.

3.3.1.1 Designate a Contractor Installation/Repair Team Leader. The Team Leader shall be the Contractor’s focal point to the Program Office Alteration Installation/Repair Team (AIT) installation manager.

3.3.1.2 Conduct pre-installation/pre-repair site surveys and ship checks on designated ships (CDRL A006, A015), and develop a detailed installation/repair schedule and POA&M which details the installation/repairing, testing and checkout phases of the effort

(CDRL A019).

3.3.1.3 Review and compare applicable ship change documentation (SCD, ORDALTs, SHIPALTs, MACHALTs, TEMPALTs and AERs) or working plans for each ship class for compliance with existing Installation Control Drawings (ICD) and recommend changes. Include findings and recommendations in the Ship Check Report. (CDRL A006, A015, A020)

3.3.1.4 Ensure that all requirements of the Industrial/Alteration Pre-start Checklist are accomplished prior to the start of the installation/repair. (CDRL A022)

3.3.1.5 Coordinate installation/repair schedule and POA&M with ship’s force, Government and other activities as necessary to ensure proper support is available and interference or delays are minimized. (CDRL A019)

3.3.1.6 Prepare and submit the necessary Quality Assurance (QA) documentation prior to the start of the installation or repair (CDRL A024).

3.3.2 Alteration Installations and Repairs

3.3.2.1 Provide the personnel necessary to successfully complete the installation or repair detailed on individual Task Orders.

3.3.2.2 Provide fabrication services for material, structures, cabinets and other components as specified by plans, drawings, schematics or other requirements as specified on individual Task Orders.

3.3.2.3 Provide portable workshops as required to support AIT. Provide the necessary tools, equipment and maintenance for the portable workshop.

3.3.2.4 Remove and relocate the necessary existing equipment per applicable alteration drawings. Dispose or reuse removed equipment as required by the Task Order.

3.3.2.5 Perform the alteration installation/repair in accordance with plans, procedures and drawings developed under Section 3.3.1, and specific guidance defined in individual Task Orders.

3.3.2.6 Rehabilitate affected spaces to original or equivalent condition. This includes:

3.3.2.6.1 Cleaning, preparing, priming and painting new and disturbed surfaces and components to match surrounding areas.

3.3.2.6.2 Replacing all deck coverings and insulation damaged incidental to installation.

3.3.2.6.3 Repairing all damaged lagging and installing new lagging where required.

3.3.2.6.4 Preparing and attaching applicable labels, tags, and nameplates to power panels, piping, data and power cables, and other equipment.

3.3.2.7 Develop and perform procedures for testing and checkout of installed/repaired systems, including system circuit tests, system operability tests and QA tests. (CDRL A004, A005, A022, A026)

3.3.2.8 Provide specific installation/repair status and financial reports as specified in individual Task Orders. (CDRL A001, A016, A021)

3.3.2.9 Provide materials, consumables, and tooling needed to complete the installation or repair as specified on individual Task Orders.

3.3.3 Post-Installation Reporting and Closeout

3.3.3.1 Provide Shipboard Industrial Work Completion Reports in accordance with NAVSEA

TS9090-310 (Latest Revision) Alterations to Ships Accomplished by Alteration Installation Teams. (CDRL A021)

3.3.4 Other Installation Requirements

3.3.4.1 Shipboard Industrial Safety: Conduct all installation/repair related activities in compliance with applicable federal, state, local, Naval, ship or industrial facility safety regulations, as applicable.

3.3.4.2 Conformance to Shipboard Routines: Review and ensure conformance to existing shipboard routines regarding cleanliness, personnel conduct, and ship’s security and integrity.

3.3.4.3 Compliance to Environmental Laws and Regulations: Comply with applicable environmental laws and regulations including federal, state, local, Naval, ship and industrial facility. Submit handling reports and disposal invoices to applicable government authorities when working with hazardous materials or waste.

3.3.4.4 Verification of Certifications: Provide verification of certification for welders and pipe fitters and all other applicable trades requiring certification. (CDRL A023).

Personnel shall carry a copy of the certification at all times during the alteration. No welder shall be permitted to work, in connection with alteration to vessels, unless they are, at the time of work being performed, qualified to the standards established by the U.S. Coast Guard American Bureau of Shipping or Department of the Navy for the type of welding being performed. No welder shall be permitted to work on production applications of welding other than those for which they have qualified and been approved by the Program Office.

3.3.4.5 All non-nuclear work on nuclear ships must be in strict compliance with Naval Sea Systems Command (NAVSEA) Instruction C9210.4A and applicable Task Order instructions.

3.4 Integrated Logistics Support (ILS)

3.4.1 Technical Documentation Support (CDRLs A004, A005, A008)

3.4.1.1 Review and evaluate existing technical documentation for systems. Technical documentation includes TMs, Preventative Maintenance Scheduling (PMS) documentation, Engineering Operation Sequencing System (EOSS) documentation, Combat Systems Operational Sequencing System (CSOSS) documentation, provisioning documents, and drawings.

3.4.1.2 Provide support for updating of technical documentation as a result of changes to equipment design and logistics support.

3.4.1.3 Develop the necessary documentation to support technology insertion of NDI/COTS.

3.4.1.4 Provide Provisioning Technical Data (PTD) for all materiel being newly introduced to systems.

3.4.1.5 Provide logistics support information, including diagrams, PMS, Integrated Logistics, and overhaul specifications for designated systems, and support for compiling data gathered into standard reports.

3.4.1.6 Provide the necessary administrative and logistics support on installation sites for the Contractor and Government personnel, which may include the need to provide materials, or coordinate special installation requirements, as specified in individual Task Orders.

3.4.2 Staging and Materials Handling Support (CDRLs A012, A013, A014)

3.4.2.1 Stage and store Government-furnished material designated as Industrial Activity

Furnished (IAF) as indicated on installation material lists. Provide warehousing and inventory management for material used for NSWCPD technical assistance programs.

3.4.2.2 Provide temporary storage, as required, for Government Furnished Material (GFM) as identified by the applicable installation documentation, which will be furnished as GFI in accordance with individual Task Orders.

3.4.2.3 Order/purchase or manufacture, stage, store until used, package and transfer all material designated as Contractor Furnished Material (CFM).