A structure is a set of elements organized together.

Structures make it possible to represent the various entities of your system and their relationships according to their type, and thus manage and track your equipment in its actual context.
For example, to know the number of work orders concerning a given entity or view the cost distribution among various entities.

 

A structure can be:

• hierarchical: an element can contain, supervise, or interfere with several others, but can only have one parent in the structure.
• network: each element can be connected to several other elements in the same network. The link between two elements in a network can be quantified.

CARL Source offers you several standard structures which cannot be deleted.

 

Hierarchical structures

General classification

• Principal: This is the most commonly used representation in the application. It reflects the target organization for maintenance and asset management activities. See Structure point.
• Location: This is for representing the topology of the premises: regions, departments, etc. See Structure point.
• Function: This makes it possible to group equipment items according to their use or their functional role; see Structure point.
• Asset: This is the basic technical structure. An asset may be composed of several other items. It can be replaced, repaired, and stopped. See Asset.
• Family: This is for categorizing items. See Family.

 

Classification of location

The solution is enhanced in the FACILITY business context.
In this case, points may be created via the Location function and organized in a manner suited to identification and mapping for real estate asset management.

Each of the structures shown below can lead to an additional tab being displayed on the equipment tree structure screen. This is done by entering a position (sequence number) in the Accessibility section of the corresponding Structure sheet.
For example, Position = 6 for the Site structure will enable a tab in the sixth position that displays the list of sites at the first level of the tree structure.

Items or functions can be attached as children of the points in this classification:

• Site: Structure to be used if the assets are distributed between a number of sites. Points of this type may be attached to location points.
• Building: Where applicable, buildings are attached to a parent point identified as a site.
• Floor: As default, points representing floors are placed one level beneath buildings.
• Zone: Points corresponding to a zone define an area of rooms within a floor.
• Room: Points corresponding to rooms are at the lowest level of this classification. A room may be attached to a zone, a floor or directly to a building.

 

Structures for characterizing elements

• Reading point: For tracking the values of a setting on an asset. It can feed into or be fed by one or more other reading points. See Reading point.
• Item: This is generally a consumable to be ordered or to be stored. A template is also a special type of item. See Item.

 

Networks

Unlike a hierarchical structure, which is accompanied by an object typology, a network structure is only intended to create links.

• Parts list: This structure is used to describe the composition of templates in reference to items or other templates. For example, a metering pump consists of one intake valve, one delivery valve, one membrane assembly D.93G, one urgent repair annual kit, one sealing bellows, two unit blades, etc.
• Custom parts list: Description of the composition as template/item of an asset. This composition is initialized for each asset based on that of its template, but can be changed in the event of specificities.
• Links between reading points: These links are used to describe the feed to a reading point from one or more others. For example, an hourly meter can feed into a consumption meter with a coefficient corresponding to the quantity consumed in one hour of operation.

 

Joins

Joins define the possible links between different structures.

In the case of a network, there will automatically be a possible join between two elements of the same structure.

Links with other structures are also possible.
For example, a location point can have not only another location point as its child, but also a main point or an asset.

 

Example

For your own needs, you can create, for example:

• a hierarchical structure of electronic addresses,
• a network corresponding to your electrical conversion and power supply system.