FIGURE 9-1 Level and Content of Documentation Effort As scope and complexity increase, level of effort increases as the realization of desired operational capability matures. Approaching documentation this way quantifies it and makes it more acceptable or at least palatable to administrative and management counterparts. It also enhances the ability to manage and control projects, to assess their status and provide milestones for progress reporting and payment. If internal labor is used, and proper account- ing for expenditures and transfers between work in progress and completed categories. KEY DOCUMENTS AND THEIR SOURCES There are two classes of documentation: design reference information and application or project specific. Design reference documents in- clude such things as official AES, ANSI, IEEE, ITU, SMPTE, or other standards; product brochures, architects and engineer's specifica- tions, construction or building codes; and Federal Communications Commission (FCC) rules. Sources of these documents include the various organizations that exist for the purpose of sponsoring stand- ards development and dissemination: manufacturers, software pub- lishers or their representatives, and various regulatory authorities. Product- or application-specific documentation includes documents received from or provided by equipment and software suppliers, 9 ESTABLISHING AND MAINTAINING RECORDS and documents created by, or for the enterprise, specific to the application. Application- or project-specific documents include a project descrip- tion, cost estimate, functional and operational requirements, topology map, list of equipment and services, specifications, and maintenance and operational policies and procedures. Structured properly, these basic documents include budget and schedule information, which can be used to support regular status reviews and reports. It is also wise to develop and maintain some form of a long-range strategic plan, or technology plan. Depending on practice and customs of the particular enterprise, 