Need for an Implementation Package when creating a Change Package?

I'm looking for some detailed information why it is considered good practice to include an Implementation Package (IP Document) when creating a Change Package in eB. In 15.2.2 is was necessary to have the IP in order to navigate between the Change Request and the Markup (prototype). That is no longer the case in 15.4.1

I've created a Change Package that contains a CR and a Work Order but received some feedback that it is a good idea to include an IP as well. Why?

Thanks!

Parents
  • Hi Patrick, I think what you may be referring to is a 'Compound object'.   We dont have an 'Implementation Package' we have a compound change package that Ameren may have named "Implementation Package"  Can you check with Kelly on this too see how it was created.

    Thanks

    -Derek

    i.e. If you go to Sys Admin you will see that there is a section called “Compound Objects”.

    Create a new Object and then find the objects you need to create in the package and drag and drop them into the package.



Reply
  • Hi Patrick, I think what you may be referring to is a 'Compound object'.   We dont have an 'Implementation Package' we have a compound change package that Ameren may have named "Implementation Package"  Can you check with Kelly on this too see how it was created.

    Thanks

    -Derek

    i.e. If you go to Sys Admin you will see that there is a section called “Compound Objects”.

    Create a new Object and then find the objects you need to create in the package and drag and drop them into the package.



Children