There is not a catch-all, complete checklist that applies to every situation. However, an internal one should be developed as part of the roll-out that accounts for your business specificities and key milestones. What to check will vary, but the questions below are an example of what could be asked:
Communicate with affected administrators and end-users about when the solution will become available and how to find training and support. Follow the Communication Plan previously developed in Kickoff Your Implementation.
End-users should discuss workload concerns with their managers if the implementation affects other deadlines. Communicate any downtime to stakeholders and distribute updated documentation on accessing training material and reporting problems. To reduce the impact, implementation often occurs near or over the weekend.
Ensure end-users know the following:
Distribute documentation to end-users and technical support. If your organization has a central hub for training resources, upload the documentation there or share links to useful standard Kepware documentation.
This documentation is critical for supporting Kepware+ on an ongoing basis. It will explain how previous tailoring or customizations worked and how end users can achieve the same result(s) with out-of-the-box functionality.
Additional documentation could include proprietary information on site-specific configurations and settings or explanations for following or omitting certain best practices, depending on the customer's discretion.
Servers that have already been installed, upgraded, or migrated according to the implementation plan should now be moved to production. This may mean targeting the servers with production applications like Manufacturing Execution Systems and Plant Historians or turning on internal data publishing utilities such as database or web output.
Work with stakeholders to ensure that network connections are successful and data flows appropriately, according to the steps taken in the earlier Access, Install, and Configure Software objective.