AMIGO Wiki
AI Managed Implementation Governance Office - Documentation
Introduction
Key Relationship
Important Field Dependencies
Object | Usage Notes | Visibility | Filter & Search Criteria -- | -- | -- | -- Hyperlink to Portfolio | Parent | | Hyperlink to Project | Child | | | | |Available features
The following features have been implemented for a few important relationships as we assign them to create these Objects within the AMIGO platform. The below image shows the Highlights Panel on the record page of the Object function, where the action buttons are present.
Add Object Dependencies
You get the objects through the scope because we’re determining objects via scope management and defining the scope of objects that are going to be in scope for our program. And then you see object dependencies there. Click on the Add Object Dependencies button to add it to the Object.
Add Predecessor
A predecessor object is used to help formulate the sequence in which data from these objects need to migrate during data migration. This kind of help builds that sequence of when you’re doing your initial planning of how these things would migrate in a sequence. Using the Add Predecessor button users can add predecessor objects associated with the Object function.
Add Successor
The successor object also determines which objects would follow in a sequence from a given object. helps so much what we did with our business process flows. If you remember that lesson, we’re doing something similar with the object flows. This is just helping us start to build the maps, the cutover strategies, and how we’re going to migrate information once we start doing our cutover planning. Using the Add Successor button users can add Successor objects associated with the Object function.
RACI Chart
Using the RACI Chart, the users can define who’s responsible, who’s accountable, who needs to be consulted, and who needs to be informed about this object. And this is pretty important because we want to be able to make sure that we are governing these objects so they don’t get out of control that they are creating things that are not necessarily objects and that we have a common understanding of what an object is within our program.
Take Action
In AMIGO, we have an object approval workflow and what we’re trying to do is govern the number of objects that we have and make sure that the appropriate understanding and definition of objects for your program are documented. And that is a program leadership or some kind of approval board is approving the types of objects you’re going to have for your program. And we followed a standard in the process of approval. You can reject, you can approve, and then you can have objects be auto-approved if the timer expires.
Using the Take Action button can perform the above-mentioned action. Users can take action only after RACI Chart is added.