When the Arrow libraries are placed on a network, powerful data management procedures can be implemented. Specific, quality-checked data can be entered into libraries located on a local or wide area network of PC's. This data is not accessible to the end users through AFT Arrow itself, so it is guarded data.

Once the data is placed on a network, users can connect to the library in the Library Browser. Users can connect to as many libraries as they want.

If the user connects to a library with these files and selects to be connected to any of these control files, the model will inherit the control formatting specified in the control files. This means that special report layouts, special graphical representations and colors, and other special controls can be decided upon by the library constructor, and those control features can be loaded into local models by end users. This is highly useful for creating customized reports for certain customers or project requirements.

By way of example, assume the Output Control content was specified as coming from the "Colorado Springs Office Library" library.

If you uncheck the Library checkbox or change certain data in the Output Control window, the library will remain connected but change to an inactive state. When the library is inactive, none of its data transfers to the model. To bring the Output Control data back into sync with the connected library, recheck the Library check box in Output Control.

This entire custom library concept lends itself naturally to the idea of specific project libraries. Each project has differing requirements that depend on the nature of the project and the end customer. Data for each project can be assembled into separate libraries, allowing faster and more accurate transmission of the controlled data and desired reporting formats to engineers.

Maintaining a network library allows commonly-used data to be controlled, which may be helpful in instances where quality control is strict.