II.D.iii. Attachment SOW N6660425Q0433.pdf

STATEMENT OF WORK (SOW)

SOLIDWORKS PRODUCT DATA MANAGEMENT (PDM) PROFESSIONAL

SOLUTION IMPLEMENTATION AND TRAINING

1. BACKGROUND

NUWC Newport is in the process of procuring a centralized SOLIDWORKS Product Data

Management (PDM) Professional solution for the base. This 3D parametric design software is used to design all sorts of products that support NUWC technical focus areas. Additionally, SolidWorks Product Data Management (PDM) solutions provide an easy way for designers to collaborate on product designs without worrying about version control or data loss. This software can store CAD models and supporting documents—anything from emails to images—in an indexed central repository that tracks versions and automates workflows. This reduces time spent searching for data and eliminates the duplication of effort. It would also control access to our data, so the right users have access to the right files at the right time.

NUWC Newport is in the process of procuring a centralized SOLIDWORKS Product Data

Management (PDM) Professional solution for the base. This 3D parametric design software is used to design all sorts of products that support NUWC technical focus areas. Additionally, SolidWorks Product Data Management (PDM) solutions provide an easy way for designers to collaborate on product designs without worrying about version control or data loss. This software can store CAD models and supporting documents—anything from emails to images—in an indexed central repository that tracks versions and automates workflows. This reduces time spent searching for data and eliminates the duplication of effort. It would also control access to our data, so the right users have access to the right files at the right time.

1.1 Places of Performance: ASECC Lab, NUWCDIVNPT, Newport, RI 02841

1.2 Authorized Users: NUWCDIVNPT Codes 10, 15, 25, 34, 45, 70 & 85

1.3 Sponsors: NUWCDIVNPT Code 00X

1.4 Types of Funding: 219

2. SCOPE

The contractor shall implementation a centralized SOLIDWORKS PDM Professional vaults for seven departments, with each department having its own vaults, in a single server, multiple vaults configuration, migration of data from three existing PDM vaults to their respective new

SOLIDWORKS PDM Professional vaults and provides PDM admins and user-interface training. Note: NUWC NPT will provide the server infrastructure to which the PDM vaults will be mounted. These activities will take place onboard Naval Station Newport in RI and the

Purvis Systems Inc in Middletown, Rhode Island contracting site whose data has to be migrated to centralized vault.

Normal business hours are defined as an established 8-hour work period between the hours of 7:00 A.M. and 5:00 P.M., Monday through Friday, excluding weekends and holidays.

The Contractor shall provide a Subject Matter Expert (SME) for the implementation of the centralized PDM and the migration of data from existing PDM vaults to the centralized vaults.

The Contractor shall provide estimate based on the number of hours required to execute the installation, data migration, data loading, post service support and training. No additional cost will be allowed once contract has been agreed by both parties.

3.0 REQUIREMENTS

All services performed under this Statement of Work (SOW) shall be accomplished by

Solidworks approved reseller. A list of individuals requiring access to job sites shall be provided to NUWCDIVNPT Security Office prior to the start of any work. The Contractor shall maintain current SolidWorks licenses configuration. The contractor shall implement the latest version of SolidWorks PDM Pro.

3.1. INSTALLATION OF SOLIDWORKS PDM PRO ON UNCLASSIFIED

NETWORK

The following activities shall be completed by the contractor for the installation of

SOLIDWORKS PDM Pro on the unclassified network:

3.1.1. Install SOLIDWORKS PDM Professional on low-side VMs or hardware provided by NUWC Newport.

3.1.2. Install Microsoft SQL (Standard or better) on low-side server hardware.

3.1.3. Build base vault configuration for codes 10, 15, 25, 34, 45, 70 & 85.

3.1.4. Assess backup and recovery procedures with IT.

3.1.5. Access control shall be implemented for all the vaults

NOTE: 100 SOLIDWORKS PDM PRO licenses will be allotted among the codes.

3.2. INSTALLATION OF SOLIDWORKS PDM PRO ON CLASSIFIED NETWORK

The following activities shall be completed by the contractor for the installation of

SOLIDWORKS PDM Pro on the classified network:

3.2.1 Install SOLIDWORKS PDM Professional on low-side VMs or hardware provided by NUWC Newport.

3.2.2 Install Microsoft SQL (Standard or better) on low-side server hardware.

3.2.3. Build base vault configuration for codes 10, 15, 25, 34, 45, 70 & 85.

3.2.4. Assess backup and recovery procedures with IT.

3.2.5. Access control shall be implemented for all the vaults

NOTE: 25 SOLIDWORKS PDM PRO licenses will be allotted among the codes.

3.3. EXISTING SOLIDWORKS PDM DATA MIGRATION

The contractor shall perform the following tasks in lieu of data migration:

3.3.1. Existing SOLIDWORKS PDMs from Code 15, 34 and 84 shall be migrated to the unclassified server.

3.3.2. All data shall be upgraded to be compatible with the latest PDM version

3.3.3. Any additional changes shall be completed as need

3.3.4. Testing shall be completed to ensure all migrated files operate normally

3.4. SOLIDWORKS DATA LOADING

The contractor shall work with NUWC NPT designated personnel to complete data loading for codes 10, 15, 25, 34, 45, 70, and 85. This shall be done through in-person workshop.

Note: Code 15 is using SOLIDWORKS WorkGroup PDM and the workshop should consider best practices and techniques for extracting latest data version form SOLIDWORKS

WorkGroup PDM.

3.5. POST SERVICE SUPPORT

There shall be 90 days post service support. This support shall address any of the following:

3.5.1 Additional configuration tweaks

3.5.2. Additional software mentoring

3.5.3. Additional software installations

3.5.4. Fixing issues not identified during installation

3.6. SOLIDWORKS ELECTRICAL

3.6.1 The Contractor shall install SOLIDWORKS Electrical with all their associated libraries.

3.6.2. The contractor shall integrate SOLIDWORKS Electrical add-in with PDM

PRO

3.7. SOLIDWORKS PDM PRO ADMIN AND USER-INTERFACE TRAININGS

3.7.1 The contractors shall conduct SOLIDWORKS PDM Pro admin training for 14 admins (Two admin per code).

3.7.2. The contractors shall conduct SOLIDWORKS PDM Pro user-interface training for 150 users. This class shall be instructor-led and conducted in a cohort format with acceptable instructor/users’ ratio.

3.8. IMPORTANT TIMELINES

3.8.1 The implementation shall be completed within EIGHT weeks after the contract award and detailed final reports should be handed over to Technical POC one week after implementation. Implementation needs to be completed in the period of 01 May 2025 to 30 June 2025.

3.8.2 Training of the 14 PDM Professional vaults administrators shall be completed within EIGHT weeks after contract award. The Course curriculum shall be approved by NUWC Newport technical POC before delivering of the class.

Training needs to be completed in the period of 01 July 2025 to 30 August 2025.

Deliverable: The contractor shall deliver ------ CDRL 001

3.8.3. PDM Professional User Interface training shall be completed for 150 users before

August 31st, 2025. The in-person training format shall be in the form of cohort, design with acceptable instructor/students’ class size that foster more individualized attention for the attendees. The Course curriculum shall be approved by NUWC Newport technical POC before delivering of the class.

Deliverable: The contractor shall deliver ------ CDRL 002

3.8.4. The Training Completion Status Report shall include the contract/task order number, contactor instructor name, specific training course title and identification number, and completion date for all contractor employees asserting training completion.

Deliverable: The contractor shall deliver ------- CDRL 003

4.0. Summary of Tasks

CLIN 0001 Setup/implementation of PDM Professional Vaults – Unclassified network

Mode of execution: in-person or virtual

Qty 7

CLIN 0002 Setup/implementation of PDM Professional Vaults – Classified network

Mode of execution: in-person

CLIN 0003 Relocation of data and mentoring from three existing PDM vaults to new PDM vaults.

Mode of execution: in-person

Qty 1

CLIN 0004 SOLIDWORKS Electrical integration add-in for PDM Pro

Mode of execution: in-person or virtual

Qty 1

CLIN 0005 Provision of Training Credit for 14 PDM Professional vaults administrators.

Mode of delivery: in-person

Qty 14

CLIN 0006 Provision of Training Credit for 150 would be PDM Professional vaults users.

Qty 150

CLIN 0007 Provision of Training Credits for SOLIDWORKS Electrical integration add-in for

PDM Pro

5.0.ADMINISTRATIVE RESPONSIBILITIES

5.1 PROGRESS REPORTS

The Contractor shall provide bi-weekly status reports of work accomplished (CDRL 004), to include routine taskings and percentage complete to date (100% implementation is completed after two months)

The Contractor designated SME will keep a detailed record of all tasks completed and report it to the Technical POC bi-weekly.

6.0. GOVERNMENT FURNISHED INFORMATION (GFI)

1 NUWCDIVNPTINST 5500.4 Security Manual Series

2 NUWC NEWPORT DIVISION VISITOR REQUEST INFORMATION

7.0.ADDITIONAL INFORMATION

7.1. CONTRACTOR ACCESS AND USE OF PREMISES

The Contractor shall ensure that Contractor personnel:

7.1.1. Are familiar with and obey the local regulations of NUWCDIVNPT while on-site.

7.1.2. Stay within the limits of the work and avenues of ingress and egress.

7.1.3. Do not enter restricted areas unless required to do so and until cleared for such entry.

7.1.4. The Contractor’s equipment shall be conspicuously marked for identification.

7.1.5. Additionally, all vehicles are subject to an inspection upon entrance into the base. When Security Force Protection Conditions are higher than normal, all commercial vehicles are inspected prior to entry into the base.

8.0 PERFORMANCE STANDARDS

8.1 GENERAL

The work shall meet or exceed the standards set forth below and in other parts of this contract.

Deviations from these standards require specific approval in writing from the Contracting Officer

(KO) on a case-by-case basis.

8.2 ON-TIME PERFORMANCE

All work shall be performed on scheduled or completed within the specified timeframes.

8.3 CONTRACTOR KEY PERSONNEL

The Contractor shall designate a Contract Project Manager in writing and provide the name and contact information to the Technical POC. The Contract Project Manager is considered essential to the work being performed under this Contract. Before removing, replacing, or diverting the

Contract Project Manager, the Contractor shall (1) notify the CO two weeks in advance and (2) submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this Contract.

The Contractor shall adhere to the submitted staffing plan and subcontracting plan that was submitted prior to award as part of the Bid proposal. Contractor shall submit staffing/subcontractor plan that provides sufficient numbers of staff at the various levels of expertise to ensure all scheduled and unscheduled services are performed and conditions are maintained to avoid any disruption to the tenant. Any changes to the proposed staffing levels, qualifications of proposed staff or key personnel, or the areas of expertise or disciplines of the proposed staff shall be submitted for review and approval from the Technical POC.

9 SECURITY CLEARANCES

Prior to any labor hours being charged on task, the Contractor shall ensure their personnel have obtained and can maintain favorable background investigations at the appropriate level(s) for access level required..

9.2 PROGRAM PROTECTION

SECURITY: All Contractor personnel shall adhere to the Security provisions of 32 CFR Part 117

– National Industrial Security Program Operating Manual (NISPOM) and the security requirements of the attached DD254. While performing work at a Government Facility, Contractor personnel shall comply with the security regulations of the host facility. Applicable

FAR, DFARS, NMCARS clauses, and NAVSEA text shall be adhered to in the performance of this contract. Security incidents shall be promptly reported through the companies Facility

Security Officer (FSO), to the Contracting Officer’s Representative (COR), Technical Point of

Contact (TPOC), and the Cognizant Security Office to NUWCDIVNPT Security.

9.3 OPERATIONS SECURITY (OPSEC)

OPSEC is a process that identifies critical information to determine if friendly actions can be observed by adversary intelligence systems, determines if information obtained by adversaries could be interpreted to be useful to them, and then executes selected measures that eliminate or reduce adversary exploitation of friendly critical information.

The Contractor shall develop and implement, and update and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract.

The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The Contractor developed OPSEC program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with

National Security Presidential Memorandum (NSPM) 28, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Government sites, the contractor shall: comply with all OPSEC instructions and policies; include OPSEC as part of its ongoing security awareness program and take all required Agency training; Be responsive to the Supporting OPSEC Manager on a non-interference basis; and Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Organization and contractor in support of the mission.

9.4 ELECTRONIC SPILLAGE

Electronic Spillage (ES) is defined as a situation where information of higher classification than a system is authorized to process is introduced into that system, intentionally or otherwise. If a

Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the

Government for ES remediation will be charged to the Contractor.