recent human resources systems that also contain physical plant information are likely candi- dates. Now we come to the point where it may be necessary (in fact it is almost certain) that some type of application-specific software may be required to capture details of communications circuits, equipment, facilities, and services. This is one of the bitter pills often ignored, outsourced, shoved aside, or put into a category of hoping it will go away. If you haven't read Chapter 9 on establishing and maintaining records, it goes into great detail about what should be done, how to get it done, and elaborates in some detail about the critical nature and value of good records. If some sort of system exists, it may be satisfactory. What is needed is an application that can import existing files and is easy to maintain, either from an automatic link to other files and systems, or manually. The output of the system will be used as a reference for the invoice validation function and support other communications cost management functions such as monthly reports, online directory, capacity planning, annual business plan development, and long range strategic planning. Table 11-3 shows the information needed for circuits and facilities. The information should be collected from documents and then phys- ically verified from tags and labels on terminal blocks and patch panels where available. In the case of virtual circuits and facilities, access to configuration screens on equipment and systems will be necessary to confirm existence and status. Resources Required It is possible to outsource invoice validation. There are businesses that are in the business of conducting what they call an audit and then using this information to support validation. They also perform other functions such as order administration-new service orders, moves, PRACTICAL IP AND TELECOM FOR BROADCAST ENGINEERING AND OPERATIONS TABLE 11-3 Site: Address: Main Number: Contact: Circuits and Facilities Carrier Status Inbound Trunks Main Number Hunt Group In Li