Access to support during and after implementation is crucial for a smooth user introduction to the solution. Quickly addressing and resolving issues can help avoid downtime.
While anyone can request support, having one or two initial internal contacts for triaging queries is advisable if broader visibility is necessary across your organization. To get support for PTC Kepware products, create a case in the MyKepware portal. For setup instructions, refer to Setup Your Support Account. If front-line Kepware staff cannot resolve an issue, you can seek help through the PTC Knowledge Base, PTC Community, My PTC Support, and PTC Technical Support. For urgent assistance with specific problems, call the PTC Customer Care Center with your case number. You will need to scroll to the “Contact” section on this page to see the phone number for PTC Customer Care for your region. Technical Support can assist with the following issues:
Kepware+ site administrators can open support cases directly with PTC eSupport. When opening a case, include:
Search the PTC Knowledge Base for information about PTC products and solutions. Knowledge Base results will be displayed in the Case Logger based on keywords entered during the case creation process. If the displayed results do not resolve your issue, you can continue with the case creation process.
The Knowledge Base includes:
On the PTC Community site, you can access information on using Kepware+, follow discussions initiated by other customers, or start your own topic. A community expert will respond and assist you.
While anyone can browse the community, creating a basic PTC account is necessary to post topics or reply to others. To do this, choose the "Basic" tab on the "Create New PTC eSupport Account" page. Please note that this account is separate from your Kepware account. Refer to Setup Your Support Account for additional instructions.
Your application support team must be readily available to resolve issues during and immediately after deployment. They should also know how to reach Technical Support if necessary. Ideally, the architect(s) and developer(s) who built the solution can help if needed.
If your application runs 24 hours per day, seven days per week, one to two employees should be reachable outside of regular business hours in case of emergencies. However, thorough testing before deployment significantly reduces the likelihood of emergencies, instilling confidence and preparedness in the team.
The Hypercare period, typically lasting 7-14 days, is a time of focused commitment. It ends when the application functions as expected, and developers may address ongoing bugs or minor fixes later. This period is crucial for ensuring the application's smooth operation.
Post-implementation, the team that set up Kepware+ will hand over the live solution to your designated support organization. This team must be trained and ready to assist Kepware users with any issues. After the transfer, avoid modifying the production application directly. Instead, make changes to the development server, test them, and once approved, publish them to production. Update the documentation with these changes accordingly.