I am looking into this. And its two fold.
(1) As architects its important that we provide all down stream teams with the information they need to understand how the whole solution hangs together and what their part is. For the Service Introduction (SI) function that means providing them with a view point (diagrams and information) that aids them in understanding what to expect as part of the project. In my experience its often seen that the lack of early SI engagement is what stops projects going live. So what do I need to provide to provide a consistent viewpoint to SI of the changes that are happening and reduces their operational effort in onboarding changes? One metric for realization there.
As their information ends up in the CSDM format and I used TOGAF (on this project, but that could be Archimate in other organisations) how does what I present help them.
(2) When doing change of an existing area I want to know what the As-Is looks like, so I can create the To-Be with operational efficiency and maximum accuracy - two metrics for realisation there. Thus I need data out of ServiceNow into my EA tool (in this case Orbus iServer). As ServiceNow and EA use different models how when I do imports of Service Now data what TOGAF elements do I populate these with?
