Get Started with Kepware+

Start by documenting your current architecture. Think about how different parts of your organization flow together. Next, document the architecture that supports your organization’s manufacturing operations, including hardware, software, and network materials. With the assistance of a controls engineer and manufacturing IT, gather at a minimum the following information:

• Directional data flow
• Data sources and destinations
• Networking status
• Install locations

Understanding and ensuring that basic system requirements for Kepware+ are met as early as possible is vital to preventing fundamental technical or system issues as the project progresses. System requirements to plan for include:

• Kepware+ Edge Agent
• Kepware+ Web Interface
• Access Kepware Servers
• Network Requirements
• Kepware Server UA Gateway
• Kepware+ Security

PTC’s Customer Success teams conduct a planning workshop with the customer to discuss the strategy, configuration best practices, optimization guidance, and deployment plan. The following will be addressed in the meeting:

• Identify Kepware+ Adoption Strategy
  • Will this be a new installation or upgrade?
    • Based on the total license footprint, how many servers require upgrading (to a newer version) versus a net-new install? How many servers are running older versions of KEPServerEX?
    • Are licenses being run on other connectivity or white-label software in scope for conversion to the new standard?
  • Discuss the configuration and deployment best practices
    • Kepware project configuration
      • Driver configuration
      • Plugin configuration
      • Server interface configuration
    • Networking requirements such as firewall allowances, port configuration, IP whitelisting, etc.
  • What is the strategy for installing the new instances of Kepware?
    • Is there a standard minimum version that should be used?
    • Where is this documented?
  • What is the strategy for upgrading older instances of Kepware?
  • When and how will licensing be applied?
    • New installations
    • Existing installations that need new licenses applied
    • Existing installations that need support renewals applied
  • When will Kepware be connected to the cloud-based configuration tool?
  • Determine how many Kepware+ agents will be required
  • Determine your Kepware Server access strategy
    • Configuration access
    • Data access
    • Local users and/or active directory
  • How will Kepware be supported in your environment?
    • For example, is there a triage contact (primary owner) for assessing support needs, license deployment, etc.?
  • Discuss eLearning or virtual instructor-led training to understand design considerations and best practices
• Identify Implementation Managers
  • Who will oversee the implementation?
  • Will there be a single Administrator or a team of Administrators? Are these site-based, location-specific, etc.?

As you strive to enhance your internal training and adoption processes, it is crucial to identify and address the specific needs of various stakeholders. By understanding and documenting the requirements of both administrators and end-users, we can ensure a smooth transition and effective knowledge transfer. Here are some key areas to focus on:

• Identify administrator needs (controlling granular settings, standardized configuration elements, naming/verbiage mandates, etc.)
• Identify end-user needs (day-to-day tasks or interactions, change management protocols, etc.)
• Document PTC-provided training assets vs. customer-specific documentation that may augment out-of-the-box training based on standards established by the stakeholder team