representatives have an opportunity to gain exposure to potential suppliers and assess their ability to perform. A preliminary release, sometimes called version 1.0, is considered the first example of final documentation. It should include all the docu- ments deemed to be appropriate and necessary for accounting, pur- chasing, installation, test and acceptance, operations, administration, maintenance, and change procedures. Each document created specif- ically for the project should contain a reference section where specific third party documents, standards, construction codes, regulatory, and other references are noted. The preliminary release should in- clude updated and extended versions of all documents included in the first draft. Equipment, facilities, and services should be as detailed as possible, and at a minimum include quantity, part number, or other reference identification to be used by accounting when auditing and paying one-time or recurring charges. One important document in the preliminary release is a formal test plan and acceptance form. This document should be in a state of completion SO it can be used to verify physical, functional, and per- formance characteristics of equipment, software, facilities, and ser- vices provided by third parties in fulfillment of purchase orders and accepted proposals. The test plan acceptance form should have matured through the RFP and contract process with each third party. Exceptions or conditions related to acceptance should be docu- mented and any agreement to waive or delay performance as agreed in any contract should be within the context of the test plan. The documentation should be carefully managed during the con- struction, test, and acceptance phase. This involves attention to phys- ical details such as cable, patch panel, and rack label details as well as configuration parameters. For example, IP address and phone number details should be checked and double-checked from the time they are planned until final check-off on the completed docu- mentation