- Resilience capacity for mainframe applications
- Self-installation z/OS workflow
- Informative content to save a rich source of events, such as a movie of the real evolution of our IS
For any organization to succeed in implementing this software is dependent upon the resilience of staff in the face of frequent organizational changes of the information system and in their work. It can manage the continuous-flow deliveries or cascade deliveries.
Globally this product manages back end process powered by z/OS. The interface could be improved in terms of the MMI/HMI. For example, with monitoring, the graphic view of the evolution of the IS.
Conceptually this system is based on a centralized vision. An improvement axis should exist to help you open your system and to decentralizing it. Converge a unified HMI for, and propose, more analyses and opportunities for the graphical analysis of the content of data included in repositories.
We've had issues with the stability of the genotype, the repository integrity.
It's OK, but it could be better with an incremental approach.
They are serious and display empathy.
It's complex because it depends upon your development architecture. Also, it's reached the limits of automation and freedom given to end users.
You need to think why you want to use an application configuration management system and if it matches with your development objectives.