L3 Services IDIQ - SOW.docx
DOCX document 106 KB Posted
- Attached to
- PD-52-0031; L3 Services
- Solicitation number
- N64498-26-RFPREQ-PD-52-0031
About this file
This is a Statement of Work (SOW) for non-personal engineering and technical services supporting the Naval Surface Warfare Center Philadelphia Division (NSWCPD) Code 50, which oversees navigation, steering control, and machinery control systems for U.S. Navy surface vessels. The contractor shall provide comprehensive support across all ship lifecycle phases including engineering design and integration, test and evaluation, integrated logistics support, system installation oversight, training development, and technical publication creation. Specific systems supported include the Navigation Critical Distribution System (NCDS), Navigation Distribution System (NDS), Automated Bridge System (ABS), Ship Control System (SCS), Steering Gear Control System (SGCS), and Machinery Control System (MCS). Key service areas encompass remote and onsite technical support for system troubleshooting, verification and validation test execution, trade studies, design documentation development, software development and installation, operator and maintenance training delivery, and obsolescence management.
The SOW establishes strict non-personal services requirements with explicit guidance on contractor employee identification and compliance with government regulations on inherently governmental functions. Performance will occur primarily at the contractor's facility in Ayer, Massachusetts, with travel to government sites including Philadelphia, San Diego, Norfolk, and overseas locations in Japan and other countries; the government estimates 125 trips annually. Personnel must be U.S. citizens with appropriate security clearances (minimum Secret level), and the contractor must establish and maintain security protocols including compliance with NISPOM, controlled unclassified information handling per NIST SP-800-171, and operations security requirements. The contract includes extensive data requirements encompassing 54 contract data requirements lists (CDRLs) covering software documentation, technical specifications, test reports, training materials, and configuration management deliverables. The SOW specifies detailed labor categories with defined education and experience minimums across multiple engineering, technical, and support positions, with total base year hours of approximately 147,750 hours distributed across the labor categories listed.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| L3 Services IDIQ - Sources Sought.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
NSWCPD SOW-PWS Template Rev 45 Statement of Work (SOW) for for Ship Navigation, Steering Control and Machinery Control Systems
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 Code 50, which is responsible for surface vessels’ Navigation, Steering Control and Machinery Control Systems.
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
NSWCPD provides surface vessel Navigation, Steering Control and Machinery Control Systems subject matter expert (SME) and in-service engineering agent (ISEA) services for the Department of Defense (DoD). These services span all phases of ships’ lifecycles including capability-based assessments, material solutions analysis, technology maturation/risk reduction, engineering manufacturing/design, production/deployment, and operations/support. These services include trade studies, verification and validation (V&V), installation/installation oversight, technical documentation development, fleet technical support, and operator/maintainer training.
Specific systems under NSWCPD cognizance include, but are not limited to, Navigation Critical Distribution System (NCDS), Navigation Distribution System (NDS), Automated Bridge System (ABS), Ship Control System (SCS), Steering Gear Control System (SGCS), and Machinery Control System (MCS).
1.2 SCOPE OF WORK
Contractor shall provide engineering, training, technical publication development, program management, technical services, and other services relating to surface vessel Ship Navigation, Steering Control and Machinery Control Systems as tasked by the NSWCPD Contract Officer (KO) or as directed in Task Order Award on behalf of NSWCPD Department 50.
Contractor shall maintain and provide subject matter expertise for Ship Navigation, Steering Control and Machinery Control Systems.
Contractor’s engineering services shall include remote technical support (relating to system troubleshooting), onsite technical support (relating to system troubleshooting), onsite ship checks supporting ship installation drawing development, V&V test execution, and installation oversite support. Contractor’s engineering services to NSWCPD Department 50 also include support for, or direct development of, trade studies, system requirements, system designs, V&V test plans, V&V test execution, operations technical manual development, maintenance technical manual development, and technical data package development (preliminary ship installation drawings, installation wire connection lists, system interconnect diagrams, system signal flow diagrams and other items supporting system deployment on Navy’s surface vessels).
Contractor’s training services shall include operational, maintenance, and ISEA-support evolutions for systems supported by Contractor. Contractor shall conduct these evolutions at the Contactor’s facility, in Government facilities (to include Government’s other contracted facilities), and on surface vessels to train NSWCPD Department 50 personnel, regional maintenance center personnel, and fleet personnel to operate, maintain and support systems supported by Contractor.
Contractor’s technical publication development shall include creation and or update of technical publications directing the operation, maintenance or support systems supported by Contractor.
Contractor’s program management services shall include oversite, direction, and coordination of Contractor’s personnel in support of above tasking. Contractor’s program management services will also include emergent technology demonstrations, system change proposal preparations, estimate generation, meeting preparation, hosting program reviews, and coordinate resolution of resulting follow-up actions.
Contractor’s technical services shall include other mechanical, production, and electrical work associated with prototype development, onsite system troubleshooting, installation oversite support, and post-installation testing.
Contractor shall procure incidental materials and components as needed to support emergent troubleshooting efforts. Contractor’s other services will include administrational and other overhead tasks necessary to support NSWCPD task execution.
2.0 APPLICABLE DOCUMENTS
2.1 Configuration Management Standard EIA649B –[http://standards.sae.org/eia649b/]
2.2 MIL-HDBK-502, DEPARTMENT OF DEFENSE HANDBOOK: ACQUISITION LOGISTICS (30 MAY 1997) – [http://everyspec.com/MIL-HDBK/MIL-HDBK-0500-0599/MIL_HDBK_502_235/]
2.3 MIL-DTL-81927C, DETAIL SPECIFICATION: MANUALS, TECHNICAL: WORK PACKAGE STYLE, FORMAT, AND COMMON TECHNICAL CONTENT REQUIREMENTS; GENERAL SPECIFICATION (NOV 1997) -[http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-81927C_14024/]
2.4 MIL-STD-38784A (W/ CHANGE-1), DEPARTMENT OF DEFENSE STANDARD PRACTICE: GENERAL STYLE AND FORMAT REQUIREMENTS FOR TECHNICAL MANUALS (11-JUL-2016) -[http://everyspec.com/MIL-STD/MIL-STD-10000-and-Up/MIL-STD-38784A_CHG-1_55081/]
2.5 MIL-DTL-87269D, DETAIL SPECIFICATION: DATA BASE, REVISABLE – INTERACTIVE ELECTRONIC TECHNICAL MANUALS, FOR THE SUPPORT OF (30-JAN-2014) - [http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-87269D_49349/]
2.6 NAVSEA Technical Specification 9090-310G -[http://www.navsea.navy.mil/Portals/103/Documents/NSWC_Dahlgren/FiberOptics/Appendix_H_TS9090-310G_Approved_2015-2-12.pdf] The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.
3.0. REQUIREMENTS
3.1 Planning and Program Management Support
3.1.1 The contractor shall provide engineering and technical support to perform the following planning and execution functions for shipboard systems on US Navy Ships and Land Based Test Facilities (LBTF):
a) Assist in the preparation of and participation in program reviews and Configuration Control Board (CCB) meetings conducted by program activities, sponsors and contractors. (CDRL A012, A042)
b) Provide engineering and maintenance technical support services in support of the installation and validation of shipboard systems and methodologies. (CDRL A003, A019)
3.2 System Design and Integration Engineering
3.2.1 The contractor shall assist the Government with the assessment, design, and installation of shipboard systems on US Navy Ships and Land Based Test Facilities (LBTF) by supporting system modernization and new concept development which will include: Engineering algorithms, Logic trees (as they pertain to systems diagnostics and prognostics), Failure Mode, Effects and Criticality Analysis (FMECA), Expert systems, Verification and validation of software developed to support these new concepts. (CDRL A004, A005, A006, A007 A015, A016, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041)
3.2.2 The contractor shall perform analysis and technical studies and provide technical services in the area of shipboard systems engineering support. The contractor shall provide support to NSWCPD Software Support Activity (SSA) for developing, installing and functionally testing software for shipboard systems, including system Simulators, On Board Trainers (OBT) and Land Based Test Facilities (LBTF). Areas of particular involvement shall include:
a) Performing investigations and analysis of data, modernization of shipboard systems necessary to develop alteration packages to include Ship Change Documents (SCDs), Engineering Change Proposals (ECPs), SHIPALTs, and others, as appropriate. (CDRL A026)
b) Providing Original Equipment Manufacturer (OEM) engineering support to develop, update, and maintain shipboard system equipment specifications and design documents, and analyzing operational requirements. (CDRL A007, A009, A010, A011, A013, A014, A020)
c) Engineering support to develop Item Control Drawings (ICD) and Ship Installation Drawing (SID) packages to support ECP and SCDs providing system and equipment reliability, maintainability and availability data, and evaluating failure trending and analysis including Failure Mode, Effects and Criticality Analysis (FMECA) and Reliability and Maintainability studies for system components. (CDRL A022, A025, A026, A039, A040, A041)
d) Reviewing proposed engineering changes for impact on configuration, performance, reliability, maintainability, logistics support, safety, and life cycle costs. (CDRL A022, A025, A026, A039, A040, A041, A043, A045)
e) Support the redesign, modification, or alteration of hardware and software for system integration and improvements. (CDRL A022, A025, A026, A039, A040, A041)
f) Conducting systems engineering studies for shipboard systems. (CDRL A003)
g) Provide OEM engineering services and technical support to design, develop, and integrate technological improvements to shipboard systems. (CDRL A022, A025, A026, A039, A040, A041)
h) Provide OEM engineering support to develop, update, and maintain shipboard systems software specifications, design and requirements documentation, including concept papers, interface reviews, preliminary designs, detailed designs, design review board for system and interface requirements, system and software requirements analysis. (CDRL A022, A025, A026, A039, A040, A041)
i) Provide OEM engineering support to accomplish shipboard systems software deliveries and installations shipboard and at land based test or training sites, including software/hardware delivery, audit preparation, and configuration management. (CDRL A022, A025, A026, A039, A040, A041, A042)
3.3 Test and Evaluation Engineering
3.3.1 The contractor shall provide integration test support for verification of shipboard systems integration requirements. In addition, the contractor shall provide installation/validation support for installing and functionally testing shipboard systems alterations. (CDRL A004, A005, A006, A007 A015, A016, A019, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041, A044, A047, A048, A049, A050, A051, A052)
3.3.2 The contractor shall provide test and evaluation support to investigate Shipboard systems problems and isolate root cause. (CDRL A004, A005, A006, A007 A015, A016, A019, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041, A044, A047, A048, A049, A050, A051, A052)
This shall include:
a) Develop test and evaluation plans including:
a. Network integration plans
b. Systems installation validation
c. Verification plans
d. Environmental testing plans
b) Formulate testing methodology and develop test procedures for shipboard systems.
c) Conduct system integration testing locally and support testing at various integration labs.
d) Develop and perform configuration audits for shipboard, land based test and training facilities.
e) Coordinate testing as required for the ISEA with outside activities, commands and commercial labs as required.
f) Assist the ISEA to provide engineering services for the correction of shipboard systems discrepancies onboard US Navy ships and Land Based Test facilities.
3.4 Integrated Logistics Support
3.4.1 The contractor shall provide assistance in the development and updating of ILS packages, including, but not limiting to, technical manuals/electronic technical manuals in accordance with reference 2.6. (CDRL A007, A020, A021 A023, A025, A010, A011, A013)
3.4.2 Contractor shall maintain material for installation and shipboard support as part of contractor maintained supply system support. (CDRL A020)
3.4.3 Contractor shall provide obsolescence management support for OEM material. (CDRL A009)
3.5 System Installation Support
3.5.1 The contractor shall provide resources to ISEA in support of equipment installation, training, test, and evaluation of shipboard systems. (CDRL A002, A003) This support includes:
Assist in the development of installation test procedures, including system operability tests as well as the development and review of installation standards and practices.
Making ship visits to design prototype layout plans for ECP / SCD installation, mark up existing installation drawings / documents and capture information for development of new documents.
Provide SCD/SHIPALT/ECD support, including all associated documentation) for shipboard systems.
a. Conduct shipboard integration testing, verification and validation of signals and troubleshooting of systems.
b. Support development of both operator and maintainer training curriculum.
c. Conduct shipboard and classroom training for operators and maintainers.
d. Provide required drawing updates and associated documentation to reflect as built solution and insert as found conditions in the approved System Problem Improvement Report (SPIR) database.
3.6 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components
3.6.1 The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor may recommend a solution to include the impact on the contract price and delivery. The contractor shall not initiate any item redesign or incur any additional costs without the express, written authorization of the contracting officer.
3.7 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Contract Requirements
3.7.1 Contractor will provide engineering support to help in the proactive monitoring of pending technically obsolete components and manufacturing source availability issues. Standard navy metrics like the Material Readiness Data Base as well as commercial research methods and sources will apply.
3.7.2 Contractor will support with the analysis and resolution of DMSMS Remedy (Fleet feedback, distance support) tickets and requests.
3.7.3 Provide engineering, lab test and field support in the technical and logistic analysis and resolution of obsolescence and manufacturer availability or quality issues.
3.7.4 Assess and support the logistic documentation effort to support DMSMS efforts, including provisioning, maintenance documentation and planning and technical data packages.
3.8 Parts Obsolescence (N/A)
4.0 DATA REQUIREMENTS
4.1 Contract Status Report (CDRL A001)
4.2 Travel Report (CDRL A002)
4.3 Technical Report –Study Services (CDRL A003)
4.4 Computer Software End Product Items (CDRL A004)
4.5 Test Plans (CDRL A005)
4.6 Test Procedures (CDRL A006)
4.7 Product Drawings/Models and Associated Lists (CDRL A007)
4.8 Meeting Minutes (CDRL A008)
4.9 Diminishing manufacturing sources and material shortages (DMSMS) (CDRL A009)
4.10 Repairable Item Inspection Report (CDRL A010)
4.11 Repair Procedure (CDRL A011)
4.12 Weekly Meeting/Program Review Briefs (CDRL A012)
4.13. Material Status Report (CDRL A013)
4.14. Government Furnished Equipment Repair Status Report (CDRL A014)
4.15. Software Documentation (CDRL A015)
4.16. Software Development Summary Report (CDRL A016)
4.17. System / Subsystem Specification (SSS) (CDRL A017)
4.18. Key Events Schedule/ Plan Of Action And Milestones (POAM) (CDRL A018)
4.19. Test/Inspection Report (CDRL A019)
4.20. Parts Management Plan (CDRL A020)
4.21. Technical Manuals (Equipment/Components) – Commercial Off the Shelf (COTS)/Non-Commercial Off the Shelf (NON-COTS) (CDRL A021)
4.22. Failure Mode, Effects, And Criticality Analysis (FMECA) Report (CDRL A022)
4.23. Training Materials (CDRL A023)
4.24. Installation and Checkout (Inco) Spares List (CDRL A024)
4.25. Commercial Drawings and Associated Lists (CDRL A025)
4.26. Technical Information Report (CDRL A026)
4.27. Interface Design Description (IDD) (CDRL A027)
4.28. Software Requirements Specification (SRS) (CDRL A028)
4.29. Software Version Description (SVD) (CDRL A029)
4.30. Software Test Report (STR) (CDRL A030)
4.31. System Deficiency Report Data (SDR) (CDRL A031)
4.32. Software Product Specification (SPS) (CDRL A032)
4.33. Software Transition Plan (STRP) (CDRL A033)
4.34. Software User Manual (SUM) (CDRL A034)
4.35. Software Installation Plan (SIP) (CDRL A035)
4.36. Software Programmer’s Guide (SPG) (CDRL A036)
4.37. Software Design Description (SDD) (CDRL A037)
4.38. Software Development Plan (SDP) (CDRL A038)
4.39. Factory Acceptance Test Plan and Procedures (CDRL A039)
4.40. Safety Assessment Report (SAR) (CDRL A040)
4.41. Interface Control Document (ICD) (CDRL A041)
4.42. Contractor's Configuration Management Plan (CMP) (CDRL 042)
4.43. Engineering Change Proposal (ECP) (CDRL A043)
4.44. Hardware Design Document (HDD) (CDRL A044)
4.45. Technical & Management Work Plan (CDRL A045)
4.46. Management Plan (CDRL A046)
4.47. Electromagnetic Interference Test Report (EMITR) (CDRL A047)
4.48. Shock Test Extension Request (CDRL A048)
4.49. Shock Test Report (CDRL A049)
4.50. Hardware Requirements Document (HRD) (CDRL A050)
4.51. Software Requirements Document (SRD) (CDRL A051)
4.52. System Requirements Document (SRD) (CDRL A052)
4.53. Government Property Inventory Report Periodic / Monthly (CDRL A053
4.54. Government Property Inventory Report Final (CDRL A054)
5.0 SECURITY REQUIREMENTS
5.1 SECURITY TRAINING. The Contractor is responsible for completing all required Government mandated training to maintain security and network access to government sites and IT systems to include but not limited to: Antiterrorism Level 1 Awareness; Records Management in the DON: Everyone's Responsibility; Training and Readiness: The Active Shooter; NAVSEA Introduction to Controlled Unclassified Information; Operations Security (OPSEC); NAVSEA Counterintelligence Training; Privacy and Personally Identifiable Information (PII) Awareness Training; NAVSEA Physical Security training and Cybersecurity 101 Training. Certificates of successful completion shall be sent to the COR and as otherwise specified in the contract.
5.1.1 In accordance with the National Industrial Security Program Operating Manual (NISPOM) (37 CFR Part 117), Contractor personnel that require access to Department of Navy (DON) information systems and/or work on-site require an open investigation or favorable adjudicated Tier 3 by the Vetting Risk Operations Center (VROC). An interim clearance is granted by VROC and recorded in the Defense Information System for Security (DISS). An open or closed investigation with a favorable adjudication is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility, have made an unfavorable determination access will be denied. For Common Access Card (CAC) you must have an open investigation and/or a favorably adjudicated investigation. Interim security clearance are acceptable for a CAC. Access will be denied for anyone that has eligibility pending in DISS. Vetting through the National Crime Information Center, Sex Offender Registry, and the Terrorist screening database shall be process for a contractor that does not have a favorable adjudicated investigation.
5.1.2 Within 30 days after contract award, the contractor shall submit a list of all contractor personnel, including subcontractor employees, who will have access to DON information systems and/or work on-site at one of the NSWCPD sites to the appointed Contracting Officer Representative (COR) via email. The contractor shall provide each employee's first name, last name, contract number, the NSWCPD technical code, work location, whether or not the employee has a CAC and or Standard Access Control Badge (SACB), the systems the employee can access (i.e., NMCI, RDT&E), and the name of the Contractor's local point of contact, phone number and email address. Throughout the period of performance of the contract, the Contractor shall immediately provide any updated information to the COR when any Contractor personnel changes occur including substitutions or departures.
5.2 ON SITE WORK. Contractor personnel that require a badge to work on-site at one of the NSWCPD sites must provide an I-9 form to verify proof of citizenship. The I-9 form should be signed by the company Facility Security Officer or the company Human Resource Department. In addition to the I-9 form, Contractors shall also bring their birth certificate, current United States Passport or naturalization certificate and state issued ID to the NSWCPD Security Officer at the time of badge request to verify citizenship. Any contractor that has unfavorable information that has not been favorably adjudicated, by Department of Defense Central Adjudication Facility (DOD CAF) will not be issued a badge. Finally, contractors shall supply a copy of their OPSEC Training Certificate or other proof that the training has been completed.
5.2.1 In accordance with NSWCPD security protocol, contractor employees who hold dual citizenship will not be granted security clearance to our facilities.
5.3 DD254 REQUIREMENT. This effort may require access to classified information up to the Secret level. No classified data will be generated or stored by the Contractor. The Contractor is required to have and maintain a Secret clearance. The requirements of the attached DD Form 254 apply.
5.3.1 The contractor is required to maintain a Facility Security Clearance (FCL) in accordance with the DD254 to perform certain work under the contract. Although it is not required at time of award, it shall be obtained within 30 DAYS after award. Otherwise, the government will have no obligation to continue ordering work under the contract and may not exercise any of the available options.
5.3.2 The Contractor shall appoint a Facility Security Officer (FSO), who shall (1) be responsible for all security aspects of the work performed under this contract, (2) assure compliance with the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 117), and (3) assure compliance with any written instructions from the NSWCPD, Security Office.
5.3.3 The contractor shall forward signed copies of DD254s provided to subcontractors to the Naval Surface Warfare Center Philadelphia Division (NSWCPD), ATTN: Security.
5.3.4 The contractor shall direct the subcontractor to obtain approval, through the prime Contractor, for the public release of information received or generated by the sub through the prime Contractor.
5.3.5 The contractor shall submit the subcontractor request for public release through the technical point of contact identified on the DD254.
Additional information related to the facility clearance process can be obtained by visiting www.dss.mil or http://www.dss.mil/isec/pcl_index.htm.
5.4 OPERATIONS SECURITY (OPSEC)
5.4.1 The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. The NSWC Philadelphia Division's (NSWCPD) Critical Information List (CIL)/ CIIL (Critical Indicators and information list) will be provided on site, if warranted. Performance under this contract requires the contractor to adhere to OPSEC requirements, which may include the NSWCPD Contractor OPSEC Plan. When the NSWCPD Contractor OPSEC Plan is required, the contractor shall return acknowledgment of the plan within 15 days of receipt. During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCPD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCPD’s CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI) unless such FOCI has been appropriately mitigated through measures approved by the Defense Counterintelligence and Security Agency. Questions concerning these requirements shall be directed to the PCO.
5.4.2 CUI correspondence transmitted internally on the contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting Controlled Unclassified Information (CUI) in Non-federal Systems and Organizations.
Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.
5.4.3 NSWCPD’s CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to the PCO, and the COR who will forward the required to the NSWCPD Public Release Authority for review.
5.4.4 Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/compromise of government Classified or CI, Business Sensitive, Company Proprietary information related to this or other program must be immediately reported to the contractor's Facility Security Officer and Cognizant Security Office and/or the Naval Criminal Investigative Service, and the NSWC PD Security Division (Code 105).
5.4.5 This SOW has been reviewed against the requirements of SECNAVINST 4200.35. SAIRC controls are not required
5.5 RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED INFORMATION (CUI) All Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document. In accordance with DoDI 5200.48, CUI must be safeguarded to prevent Unauthorized Disclosure (UD). CUI export controlled technical information or other scientific, technical, and engineering information must be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR. Nonfederal information systems storing and processing CUI shall be protected per NIST SP-800-171, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and posting on social media websites (Facebook, Instagram, Twitter, LinkedIn, etc.) are prohibited. Destroy CUI associated with this contract by any of the following approved methods: A cross-cut shredder; a certified commercial destruction vendor; a central destruction facility; incineration; chemical decomposition; pulverizing, disintegration; or methods approved for classified destruction.
5.6 PLANNING, PROGRAMMING, BUDGETING AND EXECUTION (PPBE) DATA.
When contractor employees, in the performance of their duties, are exposed to Planning, Programming, Budgeting and Execution (PPBE) data, a Non-Disclosure Agreement (NDA) with all affected contactor personnel must be executed in coordination with the COR and PCO to ensure safeguarding disclosure of this data.
5.7 U-NNPI SECURITY REQUIREMENTS
5.7.1 Security Classification Guidance is as follows of portions of the tasking on this contract when invoked in the task order statement of work:
5.7.1.1 Contractor requires access to information and equipment classified at the Confidential National Security Information (NSI) level in order to provide industrial support services within facilities that actively support the Navy Nuclear Propulsion Program (NNPP).
5.7.1.2 All contractor personnel accessing classified information or classified material associated with the performance of work related to the resultant contract must be United States citizens and shall have and maintain at a minimum Confidential security clearance.
5.7.1.3 The Contractor is responsible for completing all required government mandated training to maintain security and network access to government sites and IT systems, as necessary to support.
5.8 U-NNPI
5.8.1 Purpose The Contractor hereby agrees that when provided documents (specifications, drawings, etc.) that are marked as containing NOFORN sensitive information that must be controlled pursuant to Federal law, the information contained therein and generated as part of the inquiry shall be used only for the purpose stated in the contract and shall in no case be transmitted outside the company (unless such transmittals comply with the detailed guidance of the contract) or to any foreign national within the company. While in use, the documents shall be protected from unauthorized observation and shall be kept secure so as to preclude access by anyone not having a legitimate need to view them. The documents shall not be copied unless done in conformance with the detailed guidance of the contract. All the documents shall be promptly returned in their entirety, unless authorized for proper disposal or retention, following completion of the contract.
5.9.2 Specific Requirements for Protecting U-NNPI
a) Only U.S. citizens who have a need to know required to execute the contract shall be allowed access to U-NNPI.
b) When not in direct control of an authorized individual, U-NNPI must be secured in a locked container (e.g., file cabinet, desk, safe). Access to the container must be such that only authorized persons can access it, and compromise of the container would be obvious at sight. Containers should have no labels that indicate the contents. If removed from the site, U-NNPI must remain in the personal possession of the individual. At no time should U-NNPI be left unsecured (e.g., in a home or automobile, or unattended in a motel room or sent with baggage).
c) U-NNPI documents will have the word NOFORN at the top and bottom of each page. The cover sheet will have the warning statement shown below. Documents originated in the course of work that reproduce, expand or modify marked information shall be marked and controlled in the same way as the original. Media such as video tapes, disks, etc., must be marked and controlled similar to the markings on the original information.
d) U-NNPI may not be processed on networked computers with outside access unless approved by CNO (N00N). If desired, the company may submit a proposal for processing NNPI on company computer systems. Personally owned computing systems, such as personal computers, laptops, personal digital assistants, and other portable electronic devices are not authorized for processing NNPI. Exceptions require the specific approval of the cognizant DAA and CNO (N00N).
e) U-NNPI may be faxed within the continental United States and Hawaii provided there is an authorized individual waiting to receive the document and properly control it. U-NNPI may not be faxed to facilities outside the continental United States, including military installations, unless encrypted by means approved by CNO (N00N).
f) U-NNPI may be sent within the continental United States and Hawaii via first class mail in a single opaque envelope that has no markings indicating the nature of the contents.
g) Documents containing U-NNPI shall be disposed of as classified material.
h) Report any attempts to elicit U-NNPI by unauthorized persons to the appropriate security personnel.
i) Report any compromises of U-NNPI to the appropriate security personnel. This includes intentional or unintentional public release via such methods as theft, improper disposal (e.g., material not shredded, disks lost), placement on Web site, transmission via email, or violation of the information system containing U-NNPI.
j) The only approved storage for U-NNPI is CDMS NOFORN.
6.0 PLACE OF PERFORMANCE
6.1 The primary place of performance under this IDIQ will be at the L3 facilities, located in Ayer, MA. Task Orders under this Contract may require travel in accordance with section 6.1.1 below. Any alternative places of performance will be determined at award of individual Task Orders.
6.1.1 Performance can occur at the following government sites:
Pittsfield, MA Philadelphia, PA Norfolk, VA San Diego, CA Bremerton, WA Washington, D.C.
Pearl Harbor, HI Mayport, FL Yokosuka, JA Portland, ME Sasebo, JA Bahrain, BAH
6.1.2 Government will provide the property identified in the GFP attachment.
6.1.3 The specific location(s) will be provided at time of award of the Contract. The Contractor shall provide a list of employees who require access to these areas, including standard security clearance information for each person, to the Contracting Officer Representative (COR) no later than three business days after the date of award. The work space provided to the Contractor personnel shall be identified by the Awardee, with appropriate signage listing the company name and individual Contractor employee name.
6.1.4 Access to Government buildings at Naval Surface Warfare Center Philadelphia Division is from 0600 to 1800 Monday through Friday, except Federal holidays. Normal work hours are from 0600 to 1800, Monday through Friday. Contractor employees shall be under Government oversight at all times. Government oversight requires that a Government employee be present in the same building/facility whenever Contractor employee(s) are performing work under this Contract. Contractor personnel are not allowed to access any Government buildings at NSWCPD outside the hours of 0600 to 1800 without the express approval of the Procuring Contracting Officer (PCO).
6.1.5 Reserved
6.1.6 Early Dismissal and Closure of Government Facilities
6.1.6.1 When a Government facility is closed and/or early dismissal of Federal employees is directed due to severe weather, security threat, or a facility related problem that prevents personnel from working, onsite Contractor personnel regularly assigned to work at that facility should follow the same reporting and/or departure directions given to Government personnel. The Contractor shall not direct charge to the contract for time off, but shall follow its own company policies regarding leave. Non-essential Contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal and during periods of inclement weather, onsite Contractors should monitor radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.
6.1.6.2 When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility related problem), on site Contractors will continue working established work hours or take leave in accordance with parent company policy. Those Contractors who take leave shall not direct charge the non-working hours to the Contract. Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, and closings in accordance with the FAR, applicable cost accounting standards, and company policy. Contractors shall follow their disclosed charging practices during the Contract period of performance, and shall not follow any verbal directions to the contrary. The PCO will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor's established accounting policy.
6.1.7 The contractor shall certify by email that each on-site contractor employee who will be resident at NSWCPD has completed both the Environmental Management System (EMS) Awareness training and has read the “Philadelphia Division Environmental Policy and Commitment” document within 30 days of commencing performance at NSWCPD.
6.1.8 In accordance with C-223-W002, ON-SITE SAFETY REQUIREMENTS (NAVSEA), the contractor shall certify by e-mail to Paul Breeden (paul.breeden@navy.mil) that on-site employees have read the “Philadelphia Division Environmental Policy and Commitment” and taken the EMS Awareness training within 30 days of commencing performance at NSWCPD. The e-mail shall include the employee name, work site, and contract number.
7.0 TRAVEL
7.1 The Contractor may be required to travel from the primary performance location when supporting this requirement. The estimated number of trips is 125.
The contractor shall be required to travel CONUS (any state in USA) and OCONUS (primarily Japan, and any country in Europe) to accomplish the tasks contained in this contract. Travel in support of this requirement is anticipated to include, but may not be limited to, the following alternate performance locations:
| CONUS/OCONUS |
| ORIGIN: |
| DESTINATION: |
| Number of Days Per Trip |
| Number of Trips |
| Number of People |
| CONUS |
| Ayers, MA |
| San Diego, CA |
| 4 |
| 125 |
| 1 |
7.2 The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be approved before travel occurs. Approval may be via email by the Contracting Officer (PCO), the Contacting Officer’s Representative (COR) or the fully executed Technical Instruction (TI) signed by the Contracting Officer.
7.2.1 In accordance with the TI instructions, before initiating any travel the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi/mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice
7.3 All travel shall be conducted in accordance with FAR 31.205-46, Travel Costs, and B-231-H001 Travel Cost (NAVSEA) and shall be pre-approved by the COR (CDRL A002).
7.4 Travel Costs
7.4.1 The current “maximum per diem” rates are set forth in the (i) Federal Travel Regulations for travel in the Continental United States; (ii) Joint Travel Regulations for Overseas Non-Foreign areas (e.g., Alaska, Hawaii, Guam, Puerto Rico, etc.); and (ii) Department of State (DOS) prescribed rates for foreign overseas locations.
8.0 GOVERNMENT FURNISHED PROPERTY
GFP is required for completion of tasks under this SOW. All Government Furnished Property is property of the U.S. Government and shall not be transferred to any individual or agency, public or private, without the express written approval of the originating Contracting Officer.
Accountability for Government Property under this task order shall be managed in accordance with FAR Part 45 and DFARS Part 245 as well as the Government Property clauses in the Task Order, regardless of whether the property is Contractor Acquired Property (CAP), GFP, or received directly from another commercial source as a deliverable from a Government issued contract.
Additional Government Property accountability requirements are outlined in the following Directives and Instructions and shall be adhered to as applicable:
· DODI 4161.02, Accountability & Management of Government Contract Property
· DoDM 4140.01, DoD Supply Chain Material Management Procedures: Material Returns, Retention and Disposition
· DODI 5000.64, Accountability & Management of DoD Equipment and Other Accountable Property
· OPNAVINST 4440.26B, Operating Materials & Supplies and Government Furnished Material Management
· SECNAVINST 5200.43A, Property Management
All GFP identified in Attachment A, Government Furnished Property. All GFP identified in Attachment A will be provided no later than 30 days after contract award.
8.1 Government Furnished Material (GFM) will be issued as needed and indicated on each Task Order (TO).
8.2 Reporting
The Contractor shall perform reporting functions and actions to maintain an accurate accounting of property. Receipt Reporting: DFARS 252.245-7005 “Management and Reporting of Government Property” requires the Contractor to report receipt of all GFP using the PIEE GFP Module.
8.3 Shipping Notification
FAR 52.245-1 requires the Contractor to report when GFP is returned to the Government. DFARS 252.245-7005 “Management and Reporting of Government Property” requires this notification be in the form of a shipment through the GFP Module in PIEE.
8.4 Inventory Reporting
FAR 52.245-1 requires the Contractor to periodically perform, record, and disclose physical inventory results. While the FAR clause does not define “periodically,” SECNAVINST 5200.43A requires on-hand inventory count reports to support property type specific inventory requirements as set forth in their respective governing instructions. The contractor shall provide an inventory report in accordance with CDRL X. The Government Property Inventory Report outlines the frequency of reporting based on property type per contract needs. If the contractor does not possess any GFP, the Government Property Inventory Report shall reflect no GFP on-hand as required on the reporting schedule.
The Contractor shall provide support within a reasonable time after the Government’s written request to support any Government audit in which GFP, or its related documentation, is requested as part of normal audit processes.
8.5 Lost, Damaged or Stolen GFP Reporting
FAR clause 52.245-1 requires the Contractor to investigate and report to the Government all incidents of property loss as soon as the facts become known. DFARS 252.245-7005 “Management and Reporting of Government Property” further requires the Contractor to report lost, damaged or stolen Government property using the Property Loss functionality within the PIEE GFP Module. The Contractor shall support the Government’s process to assign liability and document loss in support of lost, damaged or stolen GFP.
8.6 Excess Property Reporting
Per FAR 52.245-1, the Contractor shall promptly disclose and report Government property in its possession that is excess to contract performance.
8.7 Property Disposition
Government Property Distribution shall be in line with FAR 52.245-1(j) and DFARS 252.245-7005 “Management and Reporting of Government Property". The contractor shall provide a written notice to the Contracting Officer when property held under this contract has not been used in 100 calendar days. All General Equipment/assets provided as GFP shall be returned to the Government for disposition at the completion of its use unless otherwise directed in writing by the Contacting Officer or the Accountable Property Officer (dependent on who is administering the contract). The Contractor shall complete the plant clearance inventory schedule using the plant clearance capability of the GFP module of the PIEE to generate an electronic equivalent of the SF 1428, Inventory Disposal Schedule.
The contractor shall obtain PCO or plant clearance officer approval (dependent on who is administering the contract) prior to disposal of excess GFP/CAP after the contractor completes the plant clearance inventory schedule.
8.7.1 Property Disposition Instructions
Government Property Distribution shall be in line with FAR 52.245-1(j) and DFARS 252.245-7005 “Management and Reporting of Government Property". The contractor shall provide a written notice to the Contracting Officer when property held under this contract has not been used in 100 calendar days. All General Equipment/assets provided as GFP shall be returned to the Government for disposition at the completion of its use unless otherwise directed in writing by the Contacting Officer or the Accountable Property Officer (dependent on who is administering the contract). The Contractor shall complete the plant clearance inventory schedule using the plant clearance capability of the GFP module of the PIEE to generate an electronic equivalent of the SF 1428, Inventory Disposal Schedule.
The contractor shall obtain PCO or plant clearance officer approval (dependent on who is administering the contract) prior to disposal of excess GFP/CAP after the contractor completes the plant clearance inventory schedule.
8.7.2 Issuance of the DD 1149 “Requisition and Invoice/Shipping Document”
The contractor must obtain a DD1149 before removing any Government Furnished Property, including Plant, Property, and Equipment (PP&E) from NSWCPD premises for general use. For situations where the contractor picks up/replaces NSWCPD property for maintenance purposes, the contractor shall provide an equipment receipt, showing Manufacturer, Model/Part Number, Serial Number and Asset Number/Barcode, on their company letterhead to the COR. Any and all GFP returned to the Government shall include a DD 1149 to document transfer of liability back to the Government.
8.8 Property Closeout. IAW FAR 52.245-1, the Contractor shall promptly perform and report to the PCO or plant clearance officer (dependent on who is administering the contract) contract property closeout to include reporting, investigating and securing closure of all loss of Government property cases; physically inventorying all property upon termination or completion of this Contract/TO; and disposing of items at the time they are determined to be excess to contractual needs.
8.9 Property Tagging:
The contractor can either tag issued equipment or use the provided NSWCPD Plant property barcodes, or NMCI asset tags. If the contractor chooses to use their own tag, it shall not cover the NSWCPD barcode, or NMCI asset tag. The NSWCPD barcode, and or NMCI asset tag number, when provided shall be used on contractor inventory reports.
9.0 GOVERNMENT FURNISHED INFORMATION
9.1 Government Furnished Information (GFI) will be issued as needed and indicated on each Task Order (TO). GFI The government will provide the contractor with all pertinent information, including deadlines and government propriety data within fourteen (14) working days of request. This government furnished information (GFI) shall be returned to the government within thirty (30) days after completion of this task or with submission of the final report, unless the SME directs that it be destroyed.
10.0 PURCHASES
10.1 Only items directly used and incidental to the services for this Contract and for work within the scope of the Statement of Work, shall be purchased under the Other Direct Cost (ODC) line items. Purchases of an individual item that is valued above $10,000 shall be approved by the Contracting Officer prior to purchase by the Contractor.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .