Draft_-_SOW_CLB_BSS_RFI.pdf

STATEMENT OF WORK

FOR

COLUMBIA Class Submarine Bearing Support Structure (BSS) Inseparable Assembly, Plan Development and Manufacture

1. SCOPE. The Advanced Propulsor Management Office (Code 808) in the Naval Architecture and Engineering Department (Department 80) of the Naval Surface Warfare Center, Carderock Division (NSWCCD) is responsible for Engineering and Manufacturing Development (EMD) of US Navy COLUMBIA (CLB) Class submarine propulsors. The Bearing Support Structure (BSS) Inseparable Assembly is a key component. The BSS serves as the main structural interface between the propulsor and submarine.

2. APPLICABLE DOCUMENTS.

2.1. COLUMBIA Class BSS Inseparable Assembly, DWG C24521200B

2.2. DoDI 5230.24, Distribution Statements on Technical Documents, dated August 23, 2012

2.3. REQUEST FOR DEVIATION/WAIVER (RFD/RFW), DD 1694

3. TECHNICAL REQUIREMENTS

3.1. ASSEMBLY AND MANUFACTURING (A&M) PLAN DEVELOPMENT. The Contractor shall develop and submit for Government review and approval an A&M Plan, CDRL A0011 (A&M Plan), reference 2.1. The A&M Plan is inclusive of major technical disciplines requiring design development and associated drawings in order to prepare for BSS Inseparable Assembly fabrication, CDRL A012 (Technical Data Package).

3.1.1. The A&M Plan and associated drawings (CDRLs A011 and A012) shall have Unlimited Data Rights.

3.2. PROJECT SCHEDULING. Design and develop a graphical report depicting a composite schedule of all planned technical activities and milestones, CDRL A013 (Project Planning Chart).

3.2.1. Design the logical sequence of activities to correlate with the A&M Plan specified in Paragraph 3.1.

3.2.2. Subordinate level elements (3rd thru 5th level or greater activities) shall not exceed five (5) work days in duration. However, exceptions to this parameter shall be proposed to the Government for approval in writing.

3.3. ASSEMBLY AND MANUFACTURING PLAN EXECUTION.

3.3.1. END-ITEM DELIVERABLE.

3.3.1.1. Fabricate each CLB BSS Inseparable Assembly in accordance with the approved chapters of the A&M Plan, reference 2.1.

3.3.1.2. Observe and report planned-to-actual work progress utilizing the graphical report developed in Paragraph 3.2., CDRL A013 (Project Planning Chart). This data item shall be submitted as an appendix to the MSR, reference 4.2.

3.3.1.3. Deliver the CLB BSS Inseparable Assembly in accordance with the specified requirements in reference 2.1.

3.3.2. WORK-IN-PROGRESS (WIP) MANAGEMENT.

3.3.2.1. Identify, evaluate, and recommend changes to the approved A&M Plan for

Government consideration and re-approval in accordance with reference 2.1.

Outline and itemize any anticipated effects to cost and schedule.

3.3.2.2. Process requests for waivers, deviations, or technical specification changes by submitting standard form DD 1694, reference 2.3.

4. PROGRAM MANAGEMENT REQUIREMENTS

4.1. PROGRAM MANAGEMENT FOR POST-AWARD ACTIVITIES. The Contractor shall perform

Program Management (PM) services including the organization, planning and interdependencies, schedule, implementation, control, analysis, compliance, and reporting of all contractual elements to achieve technical, schedule and financial objectives. Develop and implement a PM plan to effectively and efficiently execute Delivery Order requirements such as methodology, procedures, and templates, CDRL A001 (PM Plan).

4.1.1. A clear line of authority shall exist among all organizational elements, including management of authorized Subcontractors.

4.1.2. Designate primary and alternate Contractors’ Points of Contact (CPOCs).

4.1.3. Arrange for access to authorized Subcontractor facilities and enable communication at all lower tiers.

4.1.4. Investigate, record facts and observations, and communicate any perceived or actual issues related to quality, schedule, cost control, management, utilization of small business, and regulatory compliance that if unresolved, would otherwise adversely affect performance and assessment.

4.1.5. First contact the Government Contracting Officer’s Representative (COR) for guidance or escalation of issues.

4.2. MONTHLY STATUS REPORTING. The Contractor shall observe and record work progress and status of the program, assigned tasks, costs, and existing or potential problem areas in narrative format, CDRL A002 (Monthly Status Report, MSR). The following activities and resulting data items shall be submitted as appendices to the MSR.

4.2.1. MONTHLY EXPENDITURE REPORTING. Observe and record all direct and indirect expenditures for both planned and actual transactions including labor hours against baseline values, and estimates of time and cost at completion, CDRL A003 (MER).

4.2.2. LIST OF DELIVERABLES. Draft and maintain a comprehensive list including all data items and all physical deliverables, CDRL A004 (List of Deliverables Report). Substantiating documentation for tangible items shall include a DD Form 1149 (Requisition and Invoice/Shipping Document).

4.2.3. CONTRACTOR PERSONNEL ROSTER (CPR). Draft and maintain a comprehensive list including all Contractor personnel and Subcontractor personnel by name and affiliation performing on each Delivery Order, CDRL A005 (CPR).

4.3. CONTRACT CHANGE PROPOSAL (CCP). The Contractor shall provide the data necessary to propose, control, and approve non-baseline changes to the Contract by the Contracting Officer (KO), CDRL A006 (CCP). The CCP shall NOT be used for making changes to requirements documentation specified in Chapter 2.0 Applicable Documents.

4.4. ELECTRONIC DOCUMENT LIBRARY (eDL). The Contractor shall develop and maintain an eDL containing all data items generated, obtained, or converted from hardcopy throughout performance, CDRL A007 (eDL).

4.4.1. For records management, utilize a file naming convention and file storage path that is not more than five (5) folders “deep”. For example, the folder for “DO 0001” may contain subfolders for “draft files” and “final files”. File naming convention by example may be “DO_0001_CDRL_A003_Encl A thru D_01FEB2020”.

4.4.2. Any physical (hard copy) data items shall be maintained separately and indexed for reference within the eDL.

4.4.3. Provide authorized Government personnel access to the eDL. Pre-authorized personnel include the KO and COR; all others shall be designated in writing by the COR.

4.4.4. Transfer all eDL information via Secure Access File Exchange (SAFE, https://safe.amrdec.army.mil/) to the COR not earlier than five (5) business days prior to end Period of Performance. A guest account may be utilized and .zip file format is authorized for ease of file bundling and transmittal; contact the COR for assistance.

4.5. TECHNICAL OR ADMINISTRATIVE FORUMS. The Contractor shall participate in meetings in order to provide live or virtual subject-matter expertise and to communicate the status of actions, objectives, and milestones, CDRL A009 (Meeting Minutes).

4.5.1. Develop briefing materials such as slideshows or executive summaries and provide documentation for discussion, CDRL A010 (Presentation Materials).

4.5.2. Participate in the events below.

4.5.2.1. “Kick-off”. At Base Year Award conduct a comprehensive presentation to

Government key leadership inclusive of program office stakeholders. Agenda shall include introduction to key personnel and subContractor leads, workflows, lines of communication, priorities of work, and breakout sessions to review regulatory requirements such as data management and invoicing.

4.5.2.2. “Monthly Status Meeting”. Conduct routine discussion related to emergent issues, planned events and outcomes anticipated to occur within the next 30 calendar days. Agenda shall include discussion points focused on priorities of work and action item status.

4.5.2.3. “Semi-annual Contract Year Review”. Conduct a comprehensive presentation to Government key leadership inclusive of technical and contractual authorities.

Agenda shall include review of funded line items by planned-to-actual values and estimates-at-completion, revised workflows, cost, schedule, and performance items.

4.6. CONTROLLED UNCLASSIFIED INFORMATION (CUI). The Contractor shall identify and safeguard written and visual communications accessed, generated or Government-furnished for reference or development in accordance with DFARS 252.204-7012. Only Unclassified data is going to be handled as part of this effort. A DD254 will not be provided.

4.6.1. CUI shall be marked “For Official Use Only (FOUO)” subject to specified exemptions from the Freedom of Information Act (FOIA), as amended.

4.6.2. Technical documents are distribution controlled and shall be marked “DISTRIBUTION STATEMENT D.” with further specificity contingent upon content at time of generation or development. Reference 2.3 for detailed instructions.

4.6.3. Utilize the Safe Access File Exchange (SAFE, https://safe.amrdec.army.mil/) for encrypted electronic file transmittal of CUI and DISTRIBUTION D-type documents.

https://safe.amrdec.army.mil/ https://safe.amrdec.army.mil/

5. DATA MANAGEMENT. A summary of data items is provided below for ease of reference. Section J

(List of Attachments) contains each DD Form 1423-1 (Contract Data Requirements List, CDRL) and accompanying Data Item Description (DID).

CDRL Title Data Item Description (DID) A001 Program Management (PM) Plan DI-MGMT-80004 A002 Monthly Status Report (MSR) DI-MGMT-80368 A003 Monthly Expenditure Report (MER) DI-FNCL-81537 A004 List of Deliverables Report DI-MISC-81920 A005 Contractor Personnel Roster (CPR) DI-MGMT-81834 A006 Contract Change Proposal (CCP) DI-ADMN-81401 A007 Electronic Data Library (eDL) DI-MISC-81920 A008 Trip Report DI-MISC-81943 A009 Meeting Minutes DI-ADMN-81505 A010 Presentation Materials DI-MGMT-81373 A011 Assembly & Manufacturing (A&M) Plan DI-MISC-80508 A012 Technical Data Package (TDP) DI-SESS-80776A A013 Project Planning Chart DI-MGMT-80507

6. TRAVEL. The Contractor shall conduct official travel within the Continental United States (CONUS) as necessary to monitor subcontractors and report status to the government. The contractor shall propose an appropriate quantity of travel to execute the requirement.

6.1.1. In performance of official travel, document and provide planned and actual itineraries, CDRL A008 (Trip Report).

6.1.2. Specific events conducted within the trip and their outcome shall be recorded in a separate document, CDRL A009 (Meeting Minutes) submitted as an attachment to CDRL A008.

7. eCRAFT

(a) The Contractor agrees to upload the Contractor's Funds and Man-hour Expenditure Reports in the Electronic Cost Reporting and Financial Tracking (eCRAFT) System and submit the Contract Status Report on the day and for the same timeframe the contractor submits an invoice into the Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) system. Compliance with this requirement is a material requirement of this contract. Failure to comply with this requirement may result in contract termination.

(b) The Contract Status Report indicates the progress of work and the status of the program and of all assigned tasks. It informs the Government of existing or potential problem areas.

(c) The Contractor's Funds and Man-hour Expenditure Report reports contractor expenditures for labor, materials, travel, subcontractor usage, and other contract charges.

(1) Access:

eCRAFT: Reports are uploaded through the eCRAFT Periodic Report Utility (EPRU). The EPRU spreadsheet and user manual can be obtained at: http://www.navsea.navy.mil/Home/Warfare- Centers/NUWC-Newport/Partnerships /Commercial-Contracts/Information-eCraft-/ under eCRAFT information. The eCRAFT e-mail address for report submission is: ecraft.nuwc.npt.fct@navy.mil. If you have problems uploading reports, please see the Frequently Asked Questions at the site address above.

(2) Submission and Acceptance/Rejection:

The contractor shall submit their reports on the same day and for the same timeframe the contractor submits an invoice in iRAPT. The amounts shall be the same. eCRAFT acceptance/rejection will be indicated by e-mail notification from eCRAFT.

http://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships http://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships