Define Compliance and Security Requirements

Depending on your industry, compliance and regulatory guidelines may impact your project. These may include:

• Restrictions on what you're able to do
• Mandates on things you have to do

ThingWorx Navigate can help your organization be compliant. For example, ThingWorx Navigate 9.3+ introduces the ability to require an e-signature on Change Request Tasks.

Meet with regulatory or quality assurance teams to understand any restrictions or mandates. Document and share those requirements with the team members who will implement ThingWorx Navigate.

ThingWorx Navigate uses the existing security of Windchill to control access to data. However, you need to decide how users will authenticate. Discuss authentication with your admin, IT lead, project sponsor, and stakeholders involved in security at your company. Depending on your current IT practices, the size of your company, and other security needs, you might choose:

• Single sign-on (SSO)
• Windchill Authentication
• Another method

Your decision about authentication will affect project costs, timeline, and the skills you need. Configuring SSO requires specific skills and experience. PTC offers a service to help you configure SSO (learn more in the services listed below). If you use the service, PTC will help you create an SSO pre-production environment for ThingWorx Navigate.

If you're planning to build a custom app, consider any additional security requirements unique to your company. Think about security for your infrastructure, servers, firewalls, etc. You'll plan for user access and permissions later.

Finally, document all your security requirements and include them as part of your project plan. This resource will help speed up installation and configuration later.