once a vendor has been qualified and achieves an acceptable performance track record, day- to-day, week-to-week, and other periodic changes can be accommo- dated with routine procedures. 9 ESTABLISHING AND MAINTAINING RECORDS Changes to the final release should be considered carefully, and only made for a significant change in operations and/ or other business requirements. Extending coverage to a new location changes in cap- acity outside the scope of moves, adds, and changes should be staged and documented with a similar process as used in managing the Preliminary Release during construction, test, and acceptance. Depending on the extent of the change and it's impact on operations, existing documentation can be updated and released as a new release after all the changes are complete and operations are stabilized. MAJOR CHANGES Major changes are caused by obsolescence, or outright growth of the business beyond the capability of the preceding design. Occasionally, new regulations bring on unavoidable and sometimes major change. Mergers and acquisitions followed by integration of operations and functions of previously independent entities can cause changes con- sidered major. For whatever reasons, usually consensus of engineer- ing, operations, and finance functions can determine the nature of the change and recommend a path that may require new or greatly revised documentation. Major changes in the way an entity does business are usually associ- ated with some larger, overriding, and far-reaching event of strategic significance. This event takes on a new name and persona unique and appropriate to the circumstances. As the new circumstances stabilize and the path becomes clear, the implications for existing equipment, software, facilities, and services become clear and planning and design work takes shape to support the new state of the changed entity. This page intentionally left blank ACCEPTING DELIVERED EQUIPMENT AND SERVICES Acceptance of goods and services is the second and last opportunity to "sign here (pre