About this file

This Statement of Work (SOW) details NASA Langley Research Center's upgrade of its PTC Windchill PDMLink software system. The project involves upgrading to Windchill 13.0, Creo Parametric 10.0.4.0, and Creo View 11.0/11.1, with comprehensive requirements for system migration, performance tuning, and support. NASA will provide necessary hardware, operating systems, database infrastructure, and access, while the vendor (PTC) will manage the upgrade process, including system analysis, testing, validation, documentation, and weekend support.

Key project specifications include a 4-month performance period, on-site work at NASA Langley Research Center in Hampton, VA, and detailed vendor resource allocation: 214 PTC Project Managers, 586 PTC Consultants, 48 PTC Learning Architects, 374 PTC Master Architects, and 1 Weekend Support resource. The vendor must ensure system compatibility, migrate all data and metadata, perform performance tuning in two phases, provide comprehensive documentation, and support NASA's user acceptance testing. Specific technical requirements include upgrading to Windows Server 2019, Oracle 19c, and Java JDK 17, with strict data security and on-site work restrictions.

View the file

Other files for this federal contract opportunity

Other files attached to Parametric Technologies Corporation (PTC) Windchill Product Data Management (PDM) Link Upgrade, newest first.
File Type Posted
Justification for Other than Full and Open Competition (JOFOC) - Final_Redacted.pdf PDF
RFQ 80TECH25QA012 - PTC Windchill PDMLink Upgrade.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

80TECH25QA012

Attachment A

PTC Windchill PDMLink Upgrade

STATEMENT OF WORK

1. Background

NASA Langley Research Center (LaRC) is currently utilizing software products from Parametric Technologies Corporation (PTC), specifically Creo Parametric as the primary CAD tool for computer-aided design (CAD), and Windchill PDMLink for product data management (PDM) to store and manage LaRC CAD data and associated electronic media in support of NASA projects. Additionally, NASA is implementing Windchill Navigate in conjunction with Ping Federate and NASA Launchpad to facilitate Single Sign-On (SSO).

2. Objective/Requirements

NASA Langely Research Center (LaRC) shall provide the following to the vendor/contractor:

LaRC shall provide the vendor with access to Windchill and related systems, for the purpose of hardware and software evaluation and execution of the SOW.

LaRC shall provide hardware, operating systems, and general support for the PDMLink system and related environments.

LaRC shall provide Windows Server 2019 or newer according to Windchill 13.0 matrices.

NASA LaRC shall provide a supported Windchill 13.0 Database, Oracle 19c.

NASA LaRC shall provide Oracle JDK 17 64-bit or Amazon Corretto 17, since Java is no longer bundled with the Windchill software.

• If needed the Web Server version will need to be upgraded to a compatible version to support Windchill 13, either Apache 2.4 Servlet Engine 9.0 or IIS 10.0 / ESE 9.0.x on 2019 or 2022.

LaRC shall upgrade to Creo View 11.0 or 11.1 for clients or above prior to the starting the upgrade project to support Windchill 13.0.x

LaRC shall upgrade to Creo Parametric 10.0.4.0 or above prior to the starting the upgrade project to support Windchill 13.0.X

LaRC shall provide testing hardware for testing and validation of the system performance and configurations.

LaRC shall provide office space and internet access for the onsite PTC personnel.

LaRC shall NOT allow any system data to be transmitted offsite and will only allow on-site personnel to work with the system data. If remote access is required, NASA can provide VPN access with a 5week lead time.

LaRC will run WinDU, provide results to the vendor services, and work with the vendor’s Technical Support to resolve all upgrade mandatory issues, as possible, prior to project kickoff.

LaRC shall provide the following:

User Acceptance Testing (UAT) and rehearsal testing resources.

Cutover resources such as testers, infrastructure, and admins.

Customization code, provided prior to the start of the project.

LaRC shall be responsible for rapidly resolving decisions on data conflicts and other issues via governance. Delays in decisions can extend the timeline of the project and may require change control to extend the team.

LaRC shall ensure infrastructure hardware will be in place prior to the start of the project, based on PTC’s recommendations.

LaRC shall provide access to resource access to hardware, physical and OS level, at the start of the project.

LaRC shall provide current PDMLink hardware that is compatible for target system, based on the vendor’s hardware review recommendations.

Clone of source and target environments shall be made available prior to the start of every rehearsal.

The configuration of all environments needed for upgrade rehearsals shall be like systems.

The vendor shall only perform basic validation post each rehearsal and production upgrade. UAT activities will be performed by LaRC, the vendor shall provide support.

NASA LaRC shall make available the following while the vendor project team is working at NASA LaRC premises:

Security badges and clearance that may be necessary for the vendor’s personnel will be provided.

Suitable office space(s), office supplies, furniture, and access to telephone and internet.

Conference room facilities equipped with white board, telephone, and projector during workshop/training activities.

Access to computers, systems and related services and accessories as required for project planning, monitoring, documentation and reporting.

The vendor shall provide the following items listed below.

LINE PART NO. DESCRIPTION QTY.

1 CNS-PTCPJM-HC- PTC Project Manager 214 2 CNS-PTCIC-HC- PTC Consultant 586 3 ADT-PTCLA-HC- PTC Learning Architect 48 4 CNS-PTCMA-HC- PTC Master Architect 374 5 CNS-64101 Weekend Support 1

3. Project Management and Governance shall include:

Singular point of contact (POC) for planning, resource coordination, and project governance with respect to activities throughout the project lifecycle.

The POC shall:

Provide Project Planning, Communication and Execution Oversite Plan a Kickoff and Weekly Project Status Meetings

Plan weekly written project status reports and minutes.

Change management, delivery of services, and overall project management.

Shall formally document, maintain, and periodically report all system issues, risks and required resolutions to LaRC no less than biweekly.

Shall work with LaRC to develop, document, maintain, and provide upgrade strategies, schedules and test plans.

The POC and Technical Support Department shall work with LaRC’s IT

Support Service Contractor for extended support for issues related to all upgrades.

Shall provide a list of personnel needed to access the facilities or systems four weeks prior to any onsite activity.

4. System Analysis and Setup shall include:

Shall document in detail any required software and/or hardware acquisitions and submit such requirements a minimum of eight weeks prior to scheduling the onsite activities.

The vendor shall ensure that all hardware and software versions and upgraded environments are supported within the appropriate PTC compatibility matrices.

The vendor shall create a development environment for testing and other needs for the completion of this upgrade. All development environments shall be created on NASA LaRC supplied equipment. PTC shall document all steps required to create any development environments. Any development environments for this activity shall be separate from the NASA existing Windchill systems.

3. System Cleanup shall include:

The vendor shall support credential scanning of upgraded system using the standard NASA tools. Support includes mitigation of all Critical, High, Medium, and Low findings, within the scope supported issues.

The vendor shall provide patching if it is required for the Windchill Migration Tools, the LaRC IT Support Services Contractor will apply the appropriate patches. PTC shall identify, document, provide, and support fixes and patches to resolve issues identified within the Windchill environment and its related systems during the upgrade engagement. NASA LaRC will be responsible for production data cleanup, but PTC shall provide support, as required.

The vendor shall avoid transferring any obsolete, unneeded, or unused environment settings, parameters, structures, rules, or configuration files related to the Windchill environment into the upgraded version of PDMLink.

In other words, the upgraded environment shall only have the Out-Of-The Box (OOTB) settings for all areas except where NASA LaRC’s existing customization or procedural requirements otherwise require. The statement above does not in any way refer to CAD data, metadata, or other LaRC-generated or stored electronic media within PDMLink.

The vendor shall ensure the integrity of all data and as necessary provide repairs and patches required to resolve data integrity issues.

The vendor shall ensure that all references to former server names, locations, and domains are updated to reflect current server names, locations, and domains or are removed from the Windchill application, LDAP, and database systems and environments. NOTE: Change of domain during upgrade is not a supported capability

The vendor shall demonstrate the PTC Windchill Rehost Utility is properly configured with OOTB PTCprovided ANT scripts or supported alternative (as outlined in the Windchill Rehost Utility Guide), works as intended, and is fully functional without the need for additional customizations or manual manipulations of system names, settings, and other variables.

4. Upgrade Execution shall include:

The vendor shall upgrade and verify the current PDMLink system design according to the process used by the NASA LaRC Engineering Directorate (ED) Engineering Review and Release Process including the configuration of system templates such as but not limited to lifecycle scheme, workflows, user access control rules, customizations, and container setup. LaRC will implement a manual load to simulate production. No other customizations or integrations are in scope.

The vendor shall execute the upgrade and necessary rehearsals for all PDMLink environments and related systems.

The vendor shall provide documentation of the upgrade to accurately reflect the final configuration, including any relevant guidance (e.g., instructions, processes, or procedures). Where possible, PTC may provide standard documented guidance. If the guidance is available online, PTC should include the reference and a PDF version of the documentation as it exists at the time of use. Contractor shall explicitly document any enhancements or deviations from the standard documentation as an addendum, with any relevant guidance modifications necessary to support future troubleshooting and issue resolution.

The vendor shall formally document and provide all issues and resolutions related to the upgrade process with the goal that NASA LaRC could identify, troubleshoot, and resolve the same or similar issues post-go live.

The vendor shall document and provide the installation process, reinstallation, and transfer of all existing Windchill customizations to the upgraded environment and ensure proper functionality and performance for each.

The vendor shall ensure that all data, metadata, and other associated data are migrated to the upgraded systems.

The vendor shall migrate all data, content and metadata, shall have the ability to be successfully opened, regenerated, modified, saved, and checked-in to the upgraded PDMLink system.

The vendor shall ensure that upgraded Production and Backup systems are near exact duplicates of one another based upon most recent re-host data available, excluding system host names.

Upon completion of the upgrade the vendor shall ensure that all Windchill systems and related environments are fully synchronized, operational, and functioning correctly, including existing business configurations/functionalities, complete EDR process and number of CAD workers and publishing Queues. PTC shall ensure that Publishing is fully functional and publishing properly for the PDMLink environments, including CreoView and EDR process.

The vendor shall develop and provide documentation needed for NASA LaRC to perform periodic routine disaster recovery backups and rehosting from the production server to the backup server specific to NASA LaRC’s systems, without assistance from PTC’s technical support. PTC may be required to validate the disaster recovery test via a live scenario.

The vendor shall conduct basic validation of the upgraded environment.

The vendor shall work with NASA LaRC to develop, document, and provide a test and validation plan and execute the test and validation plans for final acceptance, with support from PTC.

The vendor shall complete performance tuning and apply performance enhancing settings, changes, and other steps required to meet or exceed the performance of the existing production environment as well as other requirements outlined in section 2.6, Performance Tuning.

The vendor shall generate performance tuning documentation and provide to NASA LaRC.

The vendor shall provide a complete and logically structured zip file containing all documentation, relevant information, software, code, patches, configuration, or other data files needed to complete the activities and requirements outlined within this SOW.

The vendor shall apply all security, maintenance patches and updates needed to ensure that Windchill and its related systems are current with the latest software builds available at the time of task completion.

i. As part of the upgrade the vendor shall ensure the publishing software environment be upgraded to support the Windchill environment if needed. The vendor shall ensure the following:

The publishing software is installed and configured on NASA LaRC supplied hardware for the Production and Backup systems and are running and fully functioning for all required data types including existing customizations.

Publishing falls within the necessary compatibility matrices.

Publishing is performance tuned and meets the required publishing demands of the user base.

Publishing can operate under a production load from the EDR process. This will ensure multiple publishing jobs are processed from the EDR system without hindering an EDR promotion request from completing.

5. Performance Tuning shall include:

The vendor shall document and provide all steps, phases, settings, issues, recommendations, and other essential data required to thoroughly evaluate and perform system tuning of the entire PDMLink environment for both Phases. The PTC Windchill Configuration Assistant (WCA) will be used for all performance analysis.

6. The vendor shall record all phases of the project:

1. Phase 1 “Go-Live” Performance Tuning The vendor shall use WCA to provide optimal settings for LaRC PDMLink system.

The vendor shall work with NASA LaRC to understand, develop, and document the LaRC PDMLink performance needs.

The vendor shall provide LaRC with OOTB and custom performance settings where necessary. These settings shall be based on the LaRC current hardware/software configurations, configurations from initial assessments, and any additional settings required to provide the best possible system performance. These settings shall address the PDM/Windchill Servers, Client Workstations, as well as other systems, sub-systems, or environments required for PDM/Windchill to function as intended and at a performance level suitable to NASA LaRC.

The vendor shall optimize the performance of the Windchill system including software and hardware as defined in the SOW.

The vendor shall perform all upgrades and tuning within the test environment to the outlined specifications before integration within the production environment.

2. Phase 2 “Go-Live” Performance Tuning:

The vendor shall develop and provide documentation for all test criteria, system settings, evaluations, and findings throughout the upgrade of PDMLink. This information will be archived and referenceable if NASA LaRC experiences a performance-related system issue and contacts the PTC technical team for assistance.

The vendor’s technical support shall provide system tuning up to 90 days after the go-live date on the production environment. PTC shall thoroughly complete, repeat, and document all performance tuning steps performed during this Phase.

The vendor shall reassess, supply, suggest, and modify the current hardware and software configurations to optimize system performance.

The vendor shall provide LaRC with updated and custom settings where needed or specified. These settings shall be based on the current hardware and software configurations at the time of evaluation and tuning. These settings shall address the PDM/Windchill Servers, Client Workstations, and related subsystems or environments required for PDM/Windchill and NASA’s necessary customizations to function as intended and at a performance level suitable to NASA LaRC.

The vendor shall ensure that all performance tuning adjustments to systems setting is documented and included with the requirements.

The vendor shall develop and provide a user’s guide documenting performance tuning and monitoring for the PDMLink System Administrators.

7. Testing and Validation shall include:

The vendor shall provide support to NASA LaRC who is responsible for the test planning, user testing, validation, and acceptance of this upgrade.

The vendor shall notify NASA LaRC on completion and validation that the

Upgrade was successful and requesting that UAT commence.

o LaRC shall formulate, develop, document, provide, and execute a test plan to meet the system needs.

o LaRC shall provide resources to execute the UA.

o LaRC shall be responsible for documenting and providing any system issues identified through UAT and capture results for each test performed.

The vendor shall be responsible resolving issues identified through UAT.

8. Documentation shall include:

Documentation shall be developed, modified, and provided to NASA LaRC by the vendor and include, but not be limited to the following types of information and requirements. The vendor shall propose documentation format with approval from LaRC.

All documentation shall have a logical flow and be complete in context.

All process steps shall be listed in order so that NASA LaRC could produce the same outcome by following the documented steps and information.

Custom code (if any) developed for the purpose of this upgrade shall be well documented, commented and provided to NASA LaRC. All final documentation shall be provided at close of contract.

9. Weekend Support shall include:

The vendor shall provide Support Services – Upgrade and Migration Weekend

Support The vendor shall provide a Support Engineer who will be assigned to

NASA LaRC to support your unique weekend activities. PTC support will be available over the weekend through a mobile phone.

The Support Engineer shall contact LaRC to request information needed for the service engagement to familiarize themselves with LaRC’s IT environment and project plan as well as scoping the potential support assistance before the weekend activities start.

During the weekend, the Support Engineer shall contact LaRC to confirm progress at least once a day. LaRC shall have the opportunity to contact the vendor with support inquiries from Friday 8pm (local time) until Sunday 8pm (local time).

Upon completion of the Upgrade & Migration Weekend Support, the vendor shall assess and close cases by priority.

10. Characteristics, Scope, and Specs

The vendor shall provide the following items listed below:

LINE PART NO. DESCRIPTION QTY.

1 CNS-PTCPJM-HC- PTC Project Manager 214 2 CNS-PTCIC-HC- PTC Consultant 586 3 ADT-PTCLA-HC- PTC Learning Architect 48 4 CNS-PTCMA-HC- PTC Master Architect 374 5 CNS-64101 Weekend Support 1

11. Place of Performance NASA Langley Research Center

1 NASA Drive Hampton, VA 23666

12. Period of Performance

The period of performance of this order shall be for a period of 4 months from the order effective date.

File details come from the government source that posted it. Updated .