Service Management

With Service Management the maintenance of the very different Services is enabled. Enterprise Architects uses its Meta model to automatically registers the relationships of Objects, Attributes, Knowledge Functions, Apps & Information Systems, and Messages and Services/APIs in which case the Service Maintenance/App Factory team can manage the different Services & APIs, Messages, and Apps/Applications in an easy way after the Data Mapping has been performed. They can use the generated messages of the Data Mapping  and use them for developing Services & APIs have

Problems and Solutions

Service Management (and App Management) is often a problem. Because of the speed of developing the messages (see Transition Delivery/Data Management) often the number of messages and services/APIs explodes resulting in the fact that it is easier to define new messages than reuse and extend the old ones. This, of course, results in an uncontrollable Application Service Lifecycle.

With the Enterprise Architects approach the delivery of the different components is automatically stored in the meta database. Special tools help to access these components and maintain them.

Tools to support Service Management

The following tools support Service Management:

Advantages of the Enterprise Architects approach

1. With the Enterprise Architects approach and tools the generated messages can easily be used to define and build the Services and APIs, while the Knowledge Functions, the different Objects, and the defined Services/APIs and the Apps an Applications using them are automatically related to each other
2. The Services can be directly executed (DME or Direct Model Execution) and are ready to integrate them in Actionable Knowledge Functions as components in a (micro)flow defining the no-code internal logic of the App(lication)s together with Business RuleSets
3. The SAFe™ Core Values are safeguarded and improved as follows
   • Alignment
   • Built-in Quality
   • Transparency
   • Program Execution