Benefits of Shared Libraries

When the xStream libraries reside on a network, they support consistent and centralized data management. Specific, quality-checked data is stored in libraries on a local or wide area network of PCs. This data is not accessible directly through xStream, so it remains controlled.

Once the data is placed on a network, users 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 the Library check box in Output Control is cleared, or data in Output Control is modified, the library remains connected but becomes inactive. When the library is inactive, none of its data is applied to the model. To synchronize the Output Control data with the connected library again, select the Library check box in Output Control.

This custom library approach lends itself naturally to project-specific libraries. Each project can have requirements that depend on project scope and the end customer. Data for each project can be assembled into separate libraries, allowing faster and more accurate transfer of controlled data and desired reporting formats to engineers.

Maintaining a network library allows commonly used data to be controlled, which is helpful in environments where quality control requirements are strict.