10 Lessons Learned After 10 Years of Administering a PTC Integrity System
The PTC Integrity product has gone by many names over the past decade or so:
- MKS Source
- MKS Integrity Manager
- PTC Integrity
- PTC Integrity Lifecycle Manager (ILM)
- PTC Integrity Application Lifecycle Manager (ALM)
- PTC Windchill RV&S (Requirements Validation & Source)
But regardless of what your organization calls it, it remains a flexible and powerful
development tool that supports:
- Software Source Control
- Requirements Management
- Change Management
- Revision Control
- Build Management
- Test Management
- Software Deployment
- …plus the detailed metrics and reporting dashboards to support all of the above.
"But like most powerful tools, there is a corresponding level of technical complexity that comes along with the ability to perform all of the sophisticated functionality in the above list. Thus, while the tool is very versatile, it can also be challenging to administer."
In our experience, however, once the system’s core architecture is well understood, the
steps necessary to keep it tuned and operational become far less daunting. To help
demystify some of the challenges PTC System Administrators often face when attempting
to keep PTC Integrity humming along (so that your organization’s Designers, Developers,
and Release Managers can also remain as productive as possible), Pinnacle has compiled
the following short list of PTC Integrity Tips and Tricks.
While every organization’s architecture will vary somewhat, the following guidelines can
help maximize your PTC Integrity system’s uptime and reduce the amount of stress
experienced by both your Integrity user base as well as your Operations team.
<CONTINUE READING>
