Life Cycle Mapping on "operational status"??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2025 05:48 AM
Talking with a client about switching from legacy status to life status we discovered some actions I can not understand the logic for.
In the Life Cycle Map table I see that some of the legacy fields are "Operational Status" that is mapped to "Configuration Item - Design -Build"
As far as I see it Operational Status is not part of the Life Cycle but are primarely used for when you set a server in maintanence mode (to avoid alerts from monitoring).
But the BR changes a server to Design Build when you switch Operational Status to Non-operational, even though the server is installed and in use.
The mapping is an OOB solution, but as I see it "operational Status" should not be mapped at all.
Can anyone clarify the logic behind that mapping?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-13-2025 04:07 AM
Hello Mathew,
I've seen your name under a few posts related to life cycle issues. Are you knowledgeable on the topic? And if so, could you perhaps take a look at the question I posted in Lifecycle synchronisation for Configuration Items without Assets?
