superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Packaging lets you bring together all of the individual elements (JCL, PROC, PARM, Programs, Schedules, Documentation etc.) (components) required for the change into one cohesive group (i.e., the "package"). This allows the change to be reviewed and approved as a single entity, rather then trying to review and approve all of the elements on a one-to-one basis.
Once a package has been created, and doesn't require any further modifications, then that package is cast, which serves two purposes:
1. The Authorized Change approvers can now make their approval/denial vote based on the contents of the package.
2. The package is readied to be promoted to the next stage of the change process.
As far as the CCID, that's a rather site-specific issue. It can provide a link, as in my current shop, to a same-named Change ID Number in the Change Management system. It can be used to group changes together for a specific project, or a specific group. In the last shop I worked in that used Endevor, the ccid remained constant, and indicated the budget code id for the department. |
|
