N5523626Q0102_RFQ.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3

AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

Created On:

28 Jul 2026, 16:32 PM Greenwich Mean Time

Section A - Solicitation/Contract Form

SWRMC FUSION Support Services Follow-on

N5523626Q0102

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

BASE YR- SUPPORT SERVICES

Provide Southwest Regional Maintenance Center (SWRMC) with support services in accordance with (IAW) the Statement of Work (SOW) contained in Section C.

0001AA

Provide SWRMC with support services IAW the SOW contained in Section C.

Pricing Arrangement: Firm Fixed Price

1,666 Hours

BASE YR- SUPPORT SERVICES (TRAVEL) COST

0002AA BASE YR- SUPPORT SERVICES (TRAVEL) COST

Pricing Arrangement: Firm Fixed Price

1 Lot

OY1 - SUPPORT SERVICES

Provide SWRMC with support services IAW the SOW contained in Section C.

1001AA

OY1 - SUPPORT SERVICES

Provide SWRMC with support services IAW the SOW contained in Section C.

Pricing Arrangement: Firm Fixed Price

1,666 Hours

OY1 - SUPPORT SERVICES (TRAVEL) COST

1002AA OY1 - SUPPORT SERVICES (TRAVEL) COST

Pricing Arrangement: Firm Fixed Price

1 Lot

OY2 - SUPPORT SERVICES

Provide SWRMC with support services IAW the SOW contained in Section C.

OY2 - SUPPORT SERVICES

2001AA Provide SWRMC with support services IAW the SOW contained in Section C.

Pricing Arrangement: Firm Fixed Price

1,666 Hours

OY2 - SUPPORT SERVICES (TRAVEL) COST

2002AA OY2 - SUPPORT SERVICES (TRAVEL) COST

Pricing Arrangement: Firm Fixed Price

1 Lot

Section C - Description/Specifications/Statement of Work

STATEMENT OF WORK

FUSION SUPPORT

1.0 Scope

The objective of this task order is to obtain system analysis, software and system engineering and analysis, development, application and customization, and technical writing services to assist the Southwest Regional Maintenance Center (SWMRC), Mid Atlantic Regional Maintenance Center (MARMC) & Naval Surface Warfare Center (NSWC) Dahlgren Division with carrying out its duties and responsibilities to manage and track ship repairs and associate contracts, purchases, funds administration and related metrics using the NAVSEA Fusion Suite of applications. The project's capabilities resolve pervasive communication, management, and administrative challenges.

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to the work within this Task Order.

Software Engineering Institute's Capability Maturity Model Integration Process

12207.0 IEEE Standard for Information Technology - Software Life Cycle Processes Department of Defense Federal Information Security Management Act (FISMA) guidance SECNAVINST 5239.3C, Department of the Navy Information Assurance Policy OPNAVINST 5239.1C, Navy Information Assurance Program OPNAVINST F3300.53C, (Series), Navy Antiterrorism Program DoD Instruction, 5200.02, Personnel Security Program SECNAV Manual, M-5510.30C, DON Personnel Security Program DOD Regulations, 5300.2-R, Personnel Security Program SECNAVINST 5510.30 (Series), Department of Navy Personnel Security Program SECNAVINST 5510.36 (Series), Department of Navy Information Security Program DOD Manual, 5220.22-M, National Industry Security Program Operating Manual (NISPOM) DOD Instruction, 8500.01, Cybersecurity DOD 5220.22-M (Series), National Industrial Security Program Operating Manual (NISPOM) National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298 DOD 5205.02 (Series), DOD Operations Security (OPSEC) Program OPNAVINST 3432.1 (Series), DON Operations Security SPAWARINST 3432.1 (Series), Operations Security Policy

3.0 TECHNICAL REQUIREMENTS

3.1 Customer Support & Administration Services

3.1.1 Atlassian Ecosystem Administration: Confluence and Jira

The contractor shall provide comprehensive support in administering both Confluence and Jira within the unclassified NAVSEA Fusion environment.

This support extends beyond the creation and management of Confluence spaces to encompass advanced Jira administration, including workflow design, project integration, sophisticated scripting, and direct manipulation of the Jira database and object structures. The combined support for Confluence and Jira will ensure a seamless, efficient operational environment tailored to the specific needs of SWRMC, MARMC & NSWC Dalgren.

Key Responsibilities:

Confluence and Jira Space Design: Create Confluence spaces with a structured approach, incorporating appropriate templates, and unique layouts using a wide variety of macros for enhanced multimedia, tables, and custom navigation displays. Similarly, design and manage Jira projects to support SWRMC, MARMC & NSWC Dalgren workflows, ensuring alignment with operational processes and requirements.

Advanced Scripting and Workflow Customization: Utilize ScriptRunner for Jira to develop sophisticated scripts that extend the platform's capabilities, including automating workflows, creating custom functions, and enhancing user interactions within Jira. Leverage deep knowledge of the Jira database and object structures to tailor functionalities to SWRMC, MARMC & NSWC Dalgren's specific operational needs.

Project Integration and User Requirements: Actively engage in project integration efforts, translating customer requirements and challenges into detailed specifications for both Confluence and Jira. Ensure that the administration and customization of these platforms fully support project integration, user requirements, and overall customer support.

Security and Permissions Management: Facilitate end-user engagement with space groups and permissions in Confluence, alongside similar roles and permissions configurations in Jira, to support diverse use cases while maintaining platform integrity and data security.

Data Management and Migration: Efficiently export and import space content across different Confluence environments. Apply similar principles to Jira for the migration of projects, workflows, and configurations between environments, ensuring data integrity and consistency.

Collaborative Solution Development: Participate in meetings with developers, project management, and technical working groups to understand workload priorities, share status updates, and collaborate on solutions. Represent technical subject matter expertise in both Confluence and Jira, facilitating a collaborative approach to solution development across SWRMC, MARMC & NSWC Dalgren projects.

Knowledge Sharing and Continuous Learning: Share lessons learned with the project team and across SWRMC, MARMC & NSWC Dalgren initiatives, participating in knowledge-sharing meetings to enhance the collective understanding and effective use of the Atlassian ecosystem.

Through this comprehensive approach, the contractor will ensure that SWRMC, MARMC & NSWC Dalgren benefits from a fully integrated, highly customized Atlassian ecosystem that supports its unique operational requirements and enhances its project management and collaboration capabilities.

3.1.2 Integrated Operations Support

The contractor will play a pivotal role in assisting SWRMC, MARMC & NSWC Dalgren's diverse operational areas--including waterfront operations, contracts, finance, safety, and procurement--in leveraging a unified platform comprising Jira, Confluence, and Power BI for comprehensive tracking, management, and reporting of their activities. This integrated approach is designed to streamline workflows, enhance data visibility, and support decision-making across the organization.

Core Support Activities:

Customized Engagement: Work closely with departments across SWRMC, MARMC & NSWC Dalgren to understand their unique operational needs and tailor the Atlassian ecosystem (Jira and Confluence) and Power BI functionalities to create a cohesive solution that supports their work processes, from project tracking to financial reporting and safety oversight.

Issue Resolution and User Support: Respond to user inquiries and troubleshoot issues by managing trouble tickets through Jira. This includes adhering to ITIL principles within customer response SOPs, ensuring timely and effective resolution of challenges encountered by users in their day-to-day use of the integrated solutions.

Technical Escalation: When necessary, escalate complex or critical issues to NAVSEA Fusion customer support, ensuring that technical challenges requiring DevOps intervention are addressed promptly to minimize disruption to SWRMC, MARMC & NSWC Dalgren operations.

Continuous Feedback Loop: Provide weekly status reports summarizing customer interactions, issues resolved, and ongoing support activities. This ensures transparency and continuous communication with stakeholders regarding the support process and system enhancements.

Collaborative Solution Development: Engage regularly with developers, project management, and technical working groups to align on operational priorities, share updates, and collaborate on the development of solutions that meet the evolving needs of SWRMC, MARMC & NSWC Dalgren.

Represent technical and operational expertise in discussions to guide the refinement and expansion of the integrated solution.

Knowledge Sharing and Improvement: Actively participate in SWRMC, MARMC & NSWC Dalgren -wide meetings to share lessons learned and best practices gleaned from supporting the integrated Jira, Confluence, and Power BI solution. Facilitate a culture of continuous learning and improvement, encouraging feedback from all RMC users to drive enhancements to the platform and support services.

Through dedicated support and collaboration, the contractor will ensure that SWRMC, MARMC & NSWC Dalgren's critical departments have the tools and support needed to efficiently track, manage, and report their workflows within a unified platform. This integrated solution will not only streamline operational processes but also enhance data-driven decision-making across the organization.

3.2 Project Integration Services

The contractor shall provide advanced project integration services to facilitate seamless interoperability between the SWRMC's operational platforms.

A primary focus will be the establishment of robust, bidirectional communication between the Jira database and the Navy Maintenance Database (NMD), as well as ensuring detailed integration with the Ship Maintenance Data Improvement Initiative (SMDII) database. These efforts are critical for enhancing data sharing, analysis, and decision-making processes within SWRMC, MARMC & NSWC Dalgren operations.

NMD Integration

Design: Collaborate with the NMD team to outline a comprehensive design that enables efficient, bidirectional data exchange between Jira and NMD. This will involve identifying key data elements, mapping data flows, and determining security protocols to safeguard sensitive information.

Prototyping: Develop a prototype to demonstrate the feasibility of the designed integration, allowing for preliminary testing and feedback from stakeholders. This phase will focus on establishing a minimum viable product (MVP) that showcases the core functionality of the integration.

Coding and Implementation: Proceed with the full-scale coding of the integration based on the approved prototype. This will include the development of custom scripts, application programming interfaces (APIs), and other necessary components to ensure a seamless and secure data exchange.

Testing and Validation: Conduct thorough testing of the integration, including unit testing, integration testing, and user acceptance testing (UAT) to ensure reliability, security, and user satisfaction.

SMDII Integration

Design: Engage with the SMDII team to design an integration solution that provides SMDII with fine-grained access to all relevant database elements within Jira. This design phase will prioritize data integrity, access control, and scalability to accommodate future needs.

Prototyping: Develop a prototype to validate the design concepts, focusing on the secure and efficient access to Jira's database elements by the SMDII system. This prototype will serve as a basis for stakeholder feedback and subsequent adjustments.

Coding and Implementation: Execute the coding phase based on the validated prototype, emphasizing secure access protocols and efficient data handling to support SMDII's analytical and operational requirements.

Testing and Validation: Implement a comprehensive testing strategy to ensure the integration meets all functional requirements, security standards, and performance benchmarks, culminating in a UAT to confirm the integration's effectiveness and user satisfaction.

Continuous Collaboration and Support

Throughout all stages of the NMD and SMDII integration projects, the contractor shall:Facilitate ongoing planning and review meetings using Atlassian Confluence and Jira to ensure alignment with project goals, timelines, and quality standards.

Conduct monthly status meetings and provide detailed monthly status reports to all stakeholders, highlighting progress, challenges, and next steps.

Participate actively in weekly meetings with developers, government project management, and technical working groups to align on workload priorities, share updates, and collaborate on solution development.

Share lessons learned with the project team and across SWRMC, MARMC & NSWC Dalgren, fostering a culture of continuous improvement and knowledge sharing.

This revised section underscores the contractor's role in bridging SWRMC, MARMC & NSWC Dalgren key databases, enhancing data interoperability, and supporting decision-making processes through strategic integration initiatives.

3.3 User Manuals, Training, and Project Documentation

The Contractor shall continue to advance the development and refinement of comprehensive user guides, Standard Operating Procedures (SOPs), and robust training support for the Fusion platform tailored to SWRMC, MARMC & NSWC Dalgren personnel. This initiative will include the creation, maintenance, and enhancement of user guides, the development and delivery of targeted training materials, and the execution of training facilitation and management functionssuch as course scheduling, participant tracking, and systematic capture and analysis of feedback surveys. Additionally, the Contractor is responsible for maintaining accurate and up-to-date project documentation for all SWRMC, MARMC & NSWC Dalgren NAVSEA Fusion Jira projects, ensuring materials reflect the latest platform capabilities and user requirements.

Key initiatives for the upcoming period will focus on:

Enhanced User Guides and SOPs: Continually develop and update user guides for critical functionalities within the Fusion platform, incorporating the latest features and integrating user feedback to ensure maximum utility.

Dynamic Training Material Production: Produce and regularly refresh training materials to cover key elements of the program's technical documentation and system operations, including the introduction of new systems or training topics as required.

Ongoing Training Material Review: Periodically review all training materials to ensure they remain aligned with the latest technical requirements and operational best practices.

Comprehensive Program Documentation: Create and maintain extensive program documentation, including lesson plans, instructor guides, and visual aids, to support a structured training program. This effort will include updating annotated flowcharts that detail workflows within SWRMC, MARMC & NSWC Dalgren Jira projects, comprehensive descriptions of all custom fields, and thorough explanations of custom scripts used within these projects.

Developer's Guide Creation: Generate a detailed Developer's Guide aimed at future developers to facilitate the maintenance, modification, and enhancement of Jira projects, scripts, and workflows. In addition to the guide, the contractor shall train SWRMC, MARMC & NSWC Dalgren personnel on developer duties in accordance with the Developer Guide. This guide will serve as a critical resource for ensuring the sustainability and adaptability of the Fusion platform, providing clear, step-by-step instructions and best practices for system development and customization.

Training Assessment and Feedback Analysis: Document attendance and meticulously evaluate assessments and feedback for all training activities, leveraging this information to refine training methods and content for enhanced effectiveness.

Curriculum Development and Training Methodology: Assess and select the most effective training methodologies, iterating on and expanding the curriculum to meet emerging needs. This includes adopting innovative training technologies and approaches to improve learner engagement and outcomes.

Collaborative Curriculum Excellence: Collaborate closely with the engineering team and internal stakeholders to design, develop, enhance, and maintain the curriculum, ensuring it meets participants' learning needs and maximizes success rates.

Documentation and Visualization Enhancements: Update project documentation with revised annotated flowcharts of SWRMC, MARMC & NSWC Dalgren Jira workflows, detailed descriptions of all custom fields, and annotated explanations of custom scripts, providing clear and accessible support for system users and developers.

This updated section aims to enhance the training and documentation framework with a focus on adaptability, comprehensive support for both users and developers, and ensuring SWRMC, MARMC & NSWC Dalgren personnel are fully equipped to leverage the Fusion platform to its utmost potential.

3.4 Systems Analysis

The contractor shall continue to deliver premier systems analysis services to SWRMC, MARMC & NSWC Dalgren and all RMC users, focusing on refining and expanding the capabilities for tracking and managing ship repair efforts more effectively. The service enhancements for the upcoming period will emphasize the integration and optimization of processes within NAVSEA Fusion Jira, ensuring that workflows are closely aligned with the Joint Fleet Maintenance Manual (JFMM) process, SWRMC, MARMC & NSWC Dalgren procedures, and best practices in project and material management.

Key initiatives will include:

Jira Workflows for Ship Repair Tracking: Developing and refining Jira workflows specifically tailored to mirror the JFMM process. This will involve a comprehensive review and analysis of existing workflows, with modifications to enhance tracking precision, transparency, and accountability in ship repair projects.

Government Furnished Materials (GFM) Tracking: Implementing and optimizing Jira workflows to manage and track Government Furnished Materials in accordance with established SWRMC, MARMC & NSWC Dalgren processes. The contractor will ensure that all GFM tracking is seamlessly integrated with ship repair workflows, providing a unified view of materials, their status, and their impact on project timelines.

Contract Elements Tracking: Expanding Jira's capabilities to include detailed tracking of contract elements such as Contract Line Item Numbers (CLINs), Repair Cost Changes (RCCs), CLIN modifications, and de-obligations. The contractor shall develop customized Jira fields, screens, and reports to manage these elements effectively, ensuring all stakeholders have up-to-date access to contract statuses and financials.

Stakeholder Engagement and Requirements Gathering: Engaging with Subject Matter Experts (SMEs) from across the RMC community to continually assess and understand the evolving needs related to ship repair, contractor management, financial management, and procurement. This will include regular meetings to gather requirements, feedback, and to identify areas for process improvement.

Solution Development and Documentation: Creating, modifying, and testing projects in NAVSEA Fusion Jira, along with comprehensive documentation on the NAVSEA Fusion Wiki. The contractor will focus on developing solutions that address the specific needs of the RMC community, emphasizing user-friendly designs and efficient problem-solving.

Training and Adoption Support: Providing briefing materials, conducting briefings as required for all stakeholders and users, and actively participating in meetings to support the adoption of developed products and the NAVSEA Fusion Jira projects. The contractor shall also assist RMC personnel in planning and executing the adoption of these tools, ensuring smooth transition and effective utilization.

Monitoring and Continuous Improvement: Regularly monitoring the adoption and effectiveness of implemented solutions, participating in required meetings to ascertain ongoing requirements, and identifying potential challenges with the use of Fusion Jira for ship repair management. The contractor will be committed to continuous improvement, leveraging feedback and performance data to make iterative enhancements to systems and processes.

This comprehensive approach aims to not only maintain but significantly improve the tracking and management of ship repair efforts, ensuring SWRMC, MARMC & NSWC Dalgren and its stakeholders have the tools and information needed to excel in their mission-critical tasks.

3.5 Enhanced Data Visualization through Jira and PowerBI Integration

The contractor shall specialize in enhancing SWRMC, MARMC & NSWC Dalgren's data visualization capabilities by integrating Jira with PowerBI, focusing on converting the rich datasets within Jira into visually engaging and easily interpretable information for management decision-making. This initiative aims to streamline the process of data analysis, enabling swift and informed decisions based on real-time data insights.

Key Initiatives

Jira and PowerBI Seamless Integration: Implement a direct integration between Jira and PowerBI to automate the flow of data into PowerBI dashboards. This integration will facilitate the generation of real-time analytics, offering a live view of operational metrics, project statuses, and other critical data points directly impacting SWRMC, MARMC & NSWC Dalgren's objectives.

Custom Dashboard Development: Design custom PowerBI dashboards that are tailored to the specific needs of SWRMC management. These dashboards will focus on presenting complex data in an accessible format, highlighting key performance indicators (KPIs), trends, and potential bottlenecks. The goal is to provide at-a-glance insights that can guide strategic decisions and operational adjustments.

Data Visualization Enhancements: Utilize PowerBI's advanced data visualization tools to create dynamic reports and interactive dashboards. These enhancements will allow SWRMC, MARMC & NSWC Dalgren management to drill down into the specifics of ship repair projects, resource allocations, and workflow efficiencies, facilitating a deeper understanding of the underlying data.

Predictive Analysis Features: Leverage PowerBI's predictive analytics capabilities to forecast future trends based on historical data from Jira. This will enable SWRMC, MARMC & NSWC Dalgren to anticipate challenges and opportunities, planning more effectively for future demands and resource allocations.

Through this dedicated approach to integrating Jira with PowerBI, the contractor will empower SWRMC with the tools and insights needed to make data-driven decisions efficiently. The emphasis on this streamlined, focused integration ensures that SWRMC, MARMC & NSWC Dalgren can capitalize on its existing datasets within Jira, enhancing operational visibility and strategic planning capabilities without the need for extensive technical support or continuous technological adjustments.

3.6 SAFETY AND ENVIRONMENTAL REQUIREMENTS

The contractor shall comply with applicable document SWRMCINST 51008 and OPNAV M-5100.23. These requirements shall be incorporated into the Contractor's Safety and Health Program.

3.6.1 OCCUPATIONAL NEAR-MISHAP/INJURY/ILLNESS REPORTING AND DART RATE

The contractor shall verbally report all near-mishaps, incidents, injuries, and illnesses of support personnel related to the performance of this contract to SWRMC ESH Department Management and the COR immediately upon becoming aware of such an incident. An initial incident report utilizing the NAVSEA Standard Item 009-74 form shall be provided to these same parties within eight (8) working hours of the incident. A final incident report of the same format, complete with root-cause analysis, shall be provided promptly after incident investigation has been completed.

The contractor shall provide an OSHA 300A report initially and annually thereafter to the SWRMC ESH Department and the COR. The report shall include Total Case Incident Rate (TCIR); and Days Away, Restricted, and Transfer (DART) rate data, along with hours worked for SWRMC during the annual period.

3.6.2 MISHAP PREVENTION AND ACCIDENT/INCIDENT INVESTIGATION

The contractor shall participate in SWRMC mishap prevention programs and processes as they relate to support contractor personnel under this contract. The contractor shall support accident, incident, near-miss, and/or property damage critiques and investigations related to the performance of this contract, or when the contractor is witness to any accident, incident, near-miss, and/or property damage that SWRMC is critiquing and/or investigating. This includes interviews, support contractor personnel statements, photographs, and any other processes involved/included in the critique and/or investigation.

3.6.3 OCCUPATIONAL INJURY/ILLNESS DOCUMENTATION

The contractor shall maintain all records, documentation and reporting requirements associated with injuries and illnesses of contractor personnel related to the performance of this contract, as required by OSHA 29 CFR 1904, Recording and Reporting Occupational Injuries and Illnesses.

3.7 EMERGENCY ACTION PLAN

For all emergencies, SWRMC personnel will follow SWRMCINST 3440.4 Emergency Action Plan (EAP).

4.0. GOVERNMENT FURNISHED PROPERTY

A government furnished laptop shall be provided. The laptop shall initially be located at the government facility. Due to potential world-wide pandemic, work during telework shall be performed in accordance with SWRMC policy and guidance if as needed.

5.0 DATA DELIVERABLES

See Exhibit A - Contract Data Requirement List (CDRL)

6.0 OTHER

6.1 Security

6.1.1 The contractor shall ensure all support contractor personnel shall be able to access Navy installations with a Common Access Card (CAC) within sixty (60) calendar days of contract award or date of hire. Any exceptions shall require written concurrence by both the applicable Department management personnel and the COR.

6.1.2 Contractor employees must accomplish all training requirements as mandated by DOD, Navy, and SWRMC within the timeframe promulgated at the time of the training requirement. These requirements must be accomplished by all contractor employees, whether or not they possess a CAC or have access to NMCI/Navy computer-based training modules. The contractor must comply with changes and updates to training requirements by keeping support personnel in compliance with the most current instructions. Current training requirements include the following (subject to change):

Initial Orientation (Required once contractor checks in to SWRMC, One-Time Requirement) DON Records Management (DOR-RM-010-1.2) (Yearly Requirement) DOD Cyber Awareness Challenge (DOD-IAA-V16.0) (Yearly Requirement) DON Annual Privacy Training (DOD-PRIV-1.0) SWRMC Annual Security Refresher (Yearly Requirement) NCIS Counter-Intelligence Awareness Briefing (Yearly Requirement) Operation Security (Yearly Requirement) DoD Mandatory Controlled Unclassified Information (CUI) (Yearly Requirement) DON Derivative Classification (If SIPR is Required, Yearly Requirement)

6.1.3 The contractor shall comply with the security directives used regarding the protection of Controlled Unclassified Information (CUI), DoDI

5200.48 CUI. The contractor may receive unclassified informational materials from the Government that are marked as Controlled Unclassified Information (CUI). This information is not authorized for release to the general public. Pertinent information is to be released only to contractor personnel who have a need to know for the purpose of contract execution or as directed by associated document markings or distribution statements.

The contractor shall take proper safeguards to ensure that any such material received will be properly protected from unauthorized or inadvertent disclosure. If there are any questions regarding the requirements for protection or the release of CUI, the contractor shall refer those questions to the

ACO."

6.2 Operations Security (OPSEC)

6.2.1 "Critical Information (CI) is an adversary's target of choice. Seemingly harmless UNCLASSIFIED data combined with other conversations, presentations, e-mails or documents could reveal classified information. Personnel will employ proper Operations Security (OPSEC) and protect Critical Information." DO NOT DISCUSS CRITICAL INFORMATION WITH PERSONS WHO DO NOT HAVE AN OFFICIAL "NEED TO

KNOW"

6.2.2 All contractor personnel assigned to this contract must adhere to, and comply with applicable Operations Security (OPSEC) measures in accordance with DoD Directive 5205.02 Operations Security Program. The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. For a full list of SWRMC's Critical Information, see SWRMC Critical Information List, SWRMCNOTE 5510 of August 29, 2022

6.3 Place of Performance

This effort is anticipated to be performed on-site, primarily in the San Diego region at SWRMC located on Naval Station San Diego.

6.4 Travel

Three (3) CONUS trips are anticipated under this purchase order.

Requirements SWRMC C300 FUSION Support Services Follow-on

Additional Regulation or Supplemental Clauses Incorporated by Full Text

C-202-H001 ADDITIONAL DEFINITIONS--BASIC (Oct 2018)

(a) Department means the Department of the Navy.

(b) Commander, Naval Sea Systems Command means the Commander of the Naval Sea Systems Command of the Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National Stock Number (NSN) respectively which shall be defined as follows:

(1) . The number assigned to each approved Item Identification under the National Item Identification Number (NIIN) Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit nonsignificant number.

(2) . The National Stock Number (NSN) for an item of supply consists of the applicable National Stock Number (NSN) four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

(Endof Text)

C-204-H002 IMPLEMENTATION OF ENHANCED SECURITY CONTROLS ON SELECT

DEFENSE INDUSTRIAL BASE PARTNER NETWORKS

(Sep 2024)

1. System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor's facility.

The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government's review of the SSPs at the Contractor's facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government.

The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor's facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor's site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days' notice to the Contractor.

2. Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 2) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b) (2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.

e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM);

and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3. Cyber Incident Response

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs /Instructions_for_Submitting_Media.docx. In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

4. Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

5. NCIS/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

(End of Text)

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (Oct 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as "protected information". File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

(End of Text)

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019) (Jan 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

(End of Text)

C-223-W002 ON-SITE SAFETY REQUIREMENTS (NAVSEA) (OCT 2018) (Oct 2018)

(a) The contractor shall ensure that each contractor employee reads any necessary safety documents within 30 days of commencing performance at any Government facility. Required safety documents can be obtained from the respective safety office. Contractors shall notify the Safety office points of contact below to report completion of the required training via email. The email shall include the contractor employee's name, work site, and contract number.

(b) It is expected that contractor employees will have received training from their employer on hazards associated with the areas in which they will be working and know what to do in order to protect themselves. Contractors are required to adhere to the requirements of 29 CFR 1910, 29 CFR 1926 and applicable state and local requirements while in Government spaces. The contractor shall ensure that all on-site contractor work at the Government facility is in accordance with any local safety instructions as provided via the COR. The contractor shall report all work-related injuries/illnesses that occurred while working at the Government site to the COR.

(c) Contractors whose employees perform work within Government spaces in excess of 1000 hours per calendar quarter during a calendar year shall submit the data elements on OSHA Form 300A, Summary of Work Related Injuries and Illnesses, for those employees to the safety office via the COR by 15 January for the previous calendar year, even if no work related injuries or , illnesses occurred. If a contractor's injury/illness rates are above the Bureau of Labor Statistics industry standards, a safety assessment may be performed by the Safety Office to determine if any administrative or engineering controls can be utilized to prevent further injuries/illnesses, or if any additional Personal Protective Equipment or training will be required.

(d) Any contractor employee exhibiting unsafe behavior may be removed from the Government site. Such removal shall not relieve the contractor from meeting its contractual obligations and shall not be considered an excusable delay as defined in FAR 52.249-14.

(e) The Safety Office points of contacts are as follows:

Environmental Safety &Health Department Head Keith M. Boyer Code 106

(619) 556-2948 keith.m.boyer2.civ@us.navy.mil

(End of Text)

C-228-H002 MINIMUM INSURANCE REQUIREMENTS (NAVSEA) (JAN 2019) (Jan 2019)

(a) In accordance with the clause(s) of this contract entitled "Insurance--Work On a Government Installation" (FAR 52.228-5) and "Liability and Insurance" (DFARS 252.217-7012), as applicable, the Contractor shall procure and maintain insurance, of at least the kinds and minimum amounts set forth below:

(i) Workers' compensation and employer's liability coverage shall be at least $100,000, except as provided in FAR 28.307- 2(a), if applicable

(ii) Bodily injury liability insurance coverage shall be written on the comprehensive form of policy of at least $500,000 per occurrence.

(iii) Automobile liability policies covering automobiles operated in the United States shall provide coverage of at least $200,000 per person and $500,000 per occurrence for bodily injury and $20,000 per occurrence for property damage. The amount of liability coverage on other policies shall be commensurate with any legal requirements of the locality and sufficient to meet normal and customary claims.

(b) To be approved by the Contracting Officer, insurance certificates must include the following cancellation policy statement: Prior to cancellation or material change in coverage, the contractor shall give 30 days written notice to the Contracting Officer.

(c) Physical work cannot begin until the insurance certificate has been approved by the Contracting Officer. Failure to provide an acceptable insurance certificate will not remove the contractor's responsibility to meet the delivery requirements outlined in Section F and FAR 52.211-11, Liquidated Damages - Supplies, Services, or Research and Development, if applicable.

(End of Text)

Section D - Packaging and Marking

Section E - Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

0001AA

Inspection and Acceptance Location

Both Destination Instructions: Acceptance and Inspection will be conducted in accordance with contract terms and conditions.

DoDAAC: N55236 CountryCode: USA

SOUTHWEST REGIONAL MAINT CENTER

3755 BRINSER STREET SUITE 1, SAN DIEGO CA 92136-5205

SAN DIEGO, CA 92136-5205

UNITED STATES

Andrew Castor, COR Email: andrew.s.castor2.civ@us.navy.mil Telephone: (619) 556-0848

0002AA

Inspection and Acceptance Location

Both Destination Instructions: Acceptance and Inspection will be conducted in accordance with contract terms and conditions.

DoDAAC: N55236 CountryCode: USA

SOUTHWEST REGIONAL MAINT CENTER

3755 BRINSER STREET SUITE 1, SAN DIEGO CA 92136-5205

SAN DIEGO, CA 92136-5205

UNITED STATES

Andrew Castor, COR Email: andrew.s.castor2.civ@us.navy.mil Telephone: (619) 556-0848

1001AA

Inspection and Acceptance Location

Both Destination Instructions: Acceptance and Inspection will be conducted in accordance with contract terms and conditions.

DoDAAC: N55236 CountryCode: USA

SOUTHWEST REGIONAL MAINT CENTER

3755 BRINSER STREET SUITE 1, SAN DIEGO CA 92136-5205

SAN DIEGO, CA 92136-5205

UNITED STATES

Andrew Castor, COR Email: andrew.s.castor2.civ@us.navy.mil Telephone: (619) 556-0848

1002AA

Inspection and Acceptance Location

Both Destination Instructions: Acceptance and Inspection will be conducted in accordance with contract terms and conditions.

DoDAAC: N55236 CountryCode: USA

SOUTHWEST REGIONAL MAINT CENTER

3755 BRINSER STREET SUITE 1, SAN DIEGO CA 92136-5205

SAN DIEGO, CA 92136-5205

UNITED STATES

Andrew Castor, COR…