ide the dollar amount due and payable for use of that circuit or facility. The word service is usually included somewhere in the in- voice, but what's being paid for in reality is the right to use a specific 9 ESTABLISHING AND MAINTAINING RECORDS facility or circuit. If a service is what is actually being billed, there should be a service description or tariff reference identification enab- ling differentiation between service and right to use of a circuit or facility. Another example of existing documentation is a circuit identification tag affixed to a wire, cable, patch panel, or network termination point. If these basics do not exist, or cannot be found easily, it would be wise and prudent to request your accounting department and a representative of each service provider establish them. Existing equipment used in connection with circuits and facilities is owned by the service provider or by the service user. If the service user owns it, then the accounting department should maintain a list of physical assets. If the service provider owns it, it's likely it appears as a separate item on an invoice along with the monthly charge, or a separate invoice altogether. If an expansion or retraction of an existing network is undertaken, it's opportune and prudent to insist on similar documentation. You can bet the big issue will be "Who does it?" Another safe bet is when you know what hits the fan, it may be difficult or next to impossible to get it done when it's needed most. Like combustion engines need oil and oil filters for long-term, trouble-free operation, content transport networks need documentation for availability, reliability, and robust, error-free operation. LEVEL OF EFFORT The level of effort required depends on the size and complexity of the project and the amount of time available or devoted to documenta- tion during the active life of the project. There are two extremes, and obviously an inbetween for all possibilities. Documentation usually begins with a sketch following a bright idea. If carried th