Enterprise Architecture Executive Handbook - U.S. Coast Guard

Management Controls
CGEA Configuration Management Plan
The Configuration Management (CM) Plan describes the process of identifying, collecting, reviewing,
and implementing changes to published CGEA products in a systematic and controlled manner. As the
doctrine for keeping the evolving information products under management and change control, the plan
contributes to satisfying quality assurance parameters and communicating changes. The CM plan also
documents the process for controlling and recording changes that are made to the CGEA throughout the
architecture product life cycle. See the CGEA CM Plan document for complete details on the
configuration management schedule, change requests, review and approval process, versioning, content
changing and dating, and verification of CGEA products.
CGEA Change Request Process
All changes to the CGEA must be reviewed and approved by the appropriate approval authorities (product
owners, EAB, PSB) prior to the publication of the official version of the CGEA. This occurs
approximately four weeks prior to any new release. The configuration manager is responsible for
managing the change requests as product stakeholders submit them.
Minor changes, such as content edits, can be forwarded to and handled directly by each product’s assigned
product manager. The product manager then submits these changes to the product owner for approval.
In addition, C4&IT sponsors may submit requests for major changes to C4&IT products or standards to
the EAB and the PSB, depending on the type of request. More information about C4&IT governance, the
EAB, and the PSB is provided in the Governance Services section, p. 37.
Product Release Schedule
The CGEA Program plans to refresh and release a new version of CGEA on an annual basis. However,
that schedule is subject to change based on mandates, management requirements, and resource allocations.
Further, change requests that are time sensitive, as dictated by management or stakeholder requirements,
may be made between releases as long as appropriate configuration management processes are followed.
All other changes are done according to the scheduled release of the CGEA.
28