Managing Close-out Package
As you may recall from the previous post, Closeout packages are collection of all deliverables from the first 3 phases. Let’s go through the steps of Closeout package - note that you don’t have to follow the order of these steps. Another useful tip, collect and compile these Closeout package data as you work through the project, instead of waiting to the end of the project.
Update design with as-built information. The as-built drawing and information shows the final locations and settings of DAS electronics, antennas, cable routing etc. Have the Design vendor also update the iBwave file with final composition of head-end electronics as well as antennas and devices on the floor.
Collect all design deliverables: Store all design information in one common repository so that the designs can be easily found.
Collect & organize all test results: compile and organize all test results at one place - this will include sweep and PIM test data for coaxial cable, OTDR and optical loss test data, CW commissioning data that shows calculated vs. measures data.
Create hardware summary: this step is optional, but good practice. From usability perspective, it’s best to do it in a spreadsheet. Idea is when there is a problem, you want to find out the source of the problem very quickly. In a large deployment, this can complement the engineering documents.
Place contextual map & label at head-end: this can be very helpful for a big campus deployment. Any mall you go to you will see maps that show “You are here”. Contextual map and label is also you-are-here-type map for the DAS head-end. For example, some large stadium DAS roll-out when it’s not unusual to have 50+ racks and it’s easy to get lost. This map can be very handy at that point.
Create FUI card for maintenance. FUI stands for Frequently Used Information. 90% of COP fills up with test results. However, that 10% of information can become most crucial when you want to quickly resolve an issue. For example, gate code to get in, URL & access credentials to get on data controller, how many remotes in the system, where are they located, etc. Idea of the FUI card is to make crucial data easily accessible.
Another optional good practice is posting logical diagrams on the walls in the head-end room. We have posted logical diagrams at some DAS head-ends, so that when we go there it can provide quick visual guide to the whole DAS landscape. If posting on the wall is a problem, you can leave a small USB drive in the head-end room with the close-out package for future maintenance vendor.
Related Posts:
Carrier RF Source Installation
Setting up a Maintenance Program
To download a template DAS project management workbook, please contact us.
