Attachment 0001 - Parts Management PWS.pdf

Performance Work Statement (PWS)

CADENAS PART Solution Software and Services

1 Introduction The DEVCOM Enterprise Product Data Management (ePDM) system is a Defense Business System (DBS) established to provide to a collaborative enterprise Knowledge Management and Information Technology (IT) Business Environment used for the management and publication of authoritative product data that enables and informs Future Force Modernization Enterprise, Acquisition and Readiness activities and decisions throughout the entire product life cycle. The ePDM Program Manager is responsible to establish provide governance and change management of data and business process capabilities provided by ePDM.

1.2 Background

Phase I of the ePDM implementation consisted of data migrations of technical data from multiple legacy systems. A subset of product data migrated into ePDM is 3D models for Aerospace and Defense specifications and standards defining define the parts, materials and processes used on weapons systems. Analysis of the CAD inventory migrated from legacy systems into ePDM has identified the existence of true duplicates (name and number) and functional (form, fit, function) duplicates. ePDM is able to identify true duplicates but requires a materiel solution capable indexing the current CAD inventory and performing similarity analysis to identify and address functional duplicates.

ePDM intends to deploy a parts management solution providing access to industry and Standards Development Organization (SDO) catalogs to serve as the basis of generating 3D geometry in the future. The solution will allow for creation of 3D geometry across multiple CAD authoring tools to be stored in centralized location. The solution must integrate with:

• The CAD authoring platforms utilized across DEVCOM

• The Windchill-based PLM system

Search and reporting capabilities of the solution will be used to perform text and similarity analysis to existing PLM part inventories to identify and address duplication.

1.3 Scope

Contract performance encompasses the delivery of commercial-off-the-shelf (COTS) software, product licensing, and professional services. Professional services include data analysis, support for product installation and configuration as well as product training.

2 General Requirements

This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort. The contractor shall be responsible for the manner and method in which this PWS is performed. The contractor shall be available to deliver services during hours consistent with government operations and remain flexible regarding hours to meet mission requirements. The contractor shall act professionally in all dealings with the government, and other contractors.

Personnel directly accessing ePDM information systems shall meet all requirements for information assurance certification IAW DoD 8570.01-M, DFARS 252.239.7001, and AR 25-2.

Contractor personnel will not be provided direct logical access to ePDM information systems.

All activities requiring logical access will be performed by ePDM appointed system administrators meeting the afore stated requirements.

Contractor services related to product installation and configuration will be performed virtually using Microsoft TEAMS or other government approved collaboration platform. Vendor personnel shall guide product installation and configuration based on written product documentation or verbal instruction as necessary. The ePDM system administrator has the discretion to pass screen control to vendor personnel to perform complex installation or configuration activities. Monitoring by the ePDM system administrators will be performed for the duration of those activities.

This is a firm-fixed-priced contract consisting of a Base Year and (4) option years.

The government shall not directly or indirectly provide supervision or control of contractor personnel. The supervision of contractor and sub-contractor personnel shall be the responsibility of the contractor.

Travel is not authorized. Any travel will be at no cost to the government, unless approved in writing by the contracting officer.

2.1 Government Facility Access

The government does not anticipate government facility access is required to execute this PWS.

Prior approval is required to access a government facility, the contractor shall provide an access request form package for all visiting personnel to the government, at least 48 hours prior to arrival. The contractor shall abide by all government facility access requirements not enumerated in this PWS.

2.2 Government Furnished Equipment

The nature of the services contained within this PWS does not require issuance of government furnished equipment.

2.3 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively administer the contract. The contractor shall respond to government requests for contractual actions in a timely fashion. The contractor shall have a point of contact between the government and contractor personnel assigned to support contracts or task orders.

2.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. Adding subcontractors shall be at no additional cost to the government. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the Procuring Contracting Officer (PCO) or Contracting Officer Representative (COR). Cross teaming may or may not be permitted.

2.5 Personal Services

The government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

2.6 Location and Hours of Work

Execution of this PWS does not required work to be performed at the government facility. All contractor services will be provided remotely. Core hours of work for this PWS is defined as from 0900 to 1500 Eastern Standard Time.

2.7 Hardware Platforms

The contractor shall be responsible to identify and provide detailed documentation pertaining to hardware platforms, processing and sizing requirements to ensure successful product installation and operation. The Army shall be responsible for the installation and configuration of hardware platforms.

3 Performance Requirements The contractor shall evaluate the ePDM hardware platforms and generate the appropriate licenses. The contractor shall assist in the installation, configuration and setup of the catalogs and software as necessary and oversee testing and validation of the software functionality. The contract shall validate connectivity for updates, integration with CAD, the Windchill-based PLM and other functions. The contract shall assist with workflow implementation and validation in support of 3D geometry requests and approvals. The contractor shall provide online support after the initial installation to ensure support after initial implementation.

Services for this contract will be executed in three phases:

• Product installation, configuration and setup

• Configuration of indexing in support of duplication reporting and analysis

• Cutover Phase – Commercial Catalogs: Move to Production environment

3.1 Parts Management Software Products and Licensing

The contractor shall provide licensing for the following software and product catalogs:

3.2 Product installation, configuration and setup

Deliverables:

• Installation, configuration, and setup of PARTsolutions software and catalogs.

• Integration with CREO and SolidWorks CAD software.

• Integration with Windchill PLM and attribute mapping.

• Ability to freely export existing 3D catalog models from PARTsolutions into CAD applications with appropriate attribute data.

Task Items:

1. Install Software:

a. License server software (Windows server 2019+)

b. Application Server component (Windows server 2019+)

c. SQL connection to “Link Database”

Parts Management Software Product Quantity PARTsolutions Professional with

• CAD Interface

• Named User

PARTsolutions Professional with

• View Only

• Named User

CADENAS PARTsolutions manufacturers catalogs 30

ASME B18 Digital Fastener Catalog

• Annual License

SAE Digital Fastener Catalog

• Annual License

AIA/NAS Digital Fastener Catalog

• Annual License

2. Setup integrations on Windchill Development Server (should always test COTS in test/dev first):

a. PLM (Windchill) Search queries uploaded to server (XML or JSP) & User credentials.

b. Confirm account connectivity and privileges.

3. Install initial Parts catalog(s) & define process to add additional catalogs as required.

4. Base configuration of CAD - Export and interface test, base part numbering/naming.

a. CREO (typically tested prior to PDM connection - workspace)

b. SolidWorks (typically tested prior to PDM connection - workspace)

5. PLM/PDM configuration

a. CREO integration

b. Second CAD linking (SolidWorks)

c. Attribute mapping – Writing attributes from catalog.

d. Release rules etc. if applicable.

6. Export configuration for each CAD

a. Start Part

b. Attribute mapping CAD & PDM

c. Layer configurations.

d. Assemblies, subparts

e. Materials, etc.

7. Install PARTsolutions client (CAD/Viewer)

a. Test connection to license server.

b. Test connection to application server.

c. Configure basic client-side configurations in application server.

d. Define initial PARTsolutions roles and export rules. (if applicable)

8. Initiate testing clients.

9. Edit settings based on feedback.

10. Test configuration changes (customer confirmation prior to moving to phase 2)

11. Project Management (ongoing through project)

3.3 Configuration of indexing in support of duplication reporting and analysis Deliverables:

• Initially Index up to 10,000 existing company parts into PARTsolutions software and nightly update indexing for new parts to be added.

• Search and find up to 10,000 existing company parts in PARTsolutions software.

• Open indexed/searched parts from Windchill via PARTsolutions software into CREO and

SolidWorks.

Task Items:

1. Install Software:

a. Server – see COTS – Ensure PLMS modules are included/installed

b. Worker PC(s) (Windows OS with CAD)

i. Worker PC is used if no neutral (. stp, .step) CAD file formats exist. If neutral formats are already available, a Worker PC will not be needed.

c. SQL connection to “Link Database”

2. Setup calls to Windchill Production Server (This is Always indexed from live environment.

This is READ ONLY)

a. Run simple query pipeline to confirm – using sample from CSV*

b. Set up SQL fields for attribute index mapping (approx. 20)

3. Install initial Parts catalog(s) & define process to add additional catalogs as required.

4. Base configuration of CAD PDMproxy settings.

a. CREO connection

b. SolidWorks connection

5. Sample pipelines to test setup.

a. Evaluate data with team.

b. Tweak and develop final pipeline(s)

i. This will take multiple iterations and modifications before complete.

6. Index no more than 10,000 items from CREO/SolidWorks part files (Release state undefined or unknown currently) (NOTE: Release state may reduce file count; family table instances may increase final count)

7. Configure PARTsolutions client (CAD/Viewer)

a. Setup client-side configurations / Enhance with COTS

b. Client configurations (Server) Add Index reliant settings for indexed data.

8. Enable catalog (indexed) access for production users.

a. Added to user role.

b. Transfer rules edited to enable opening Windchill parts in CREO & SW sessions.

9. Add night update (dynamic index) data released in last 24 hours.

10. Project Management (ongoing through project)

4 Intellectual Property

Army shall retain ownership of all proprietary data provided to and used by the contractor in support of this service. The contractor shall have no rights in this data and shall not be permitted to use, release to others, reproduce, distribute, or publish this data without express written permission.

Army shall retain the rights to redistribute native and neutral CAD files generated using the PARTsolutions recipe file format which the supplier libraries are based.