Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ardiadminguide:template [2017/01/17 00:09] optrix |
ardiadminguide:template [2018/12/18 02:44] (current) optrix |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| Any asset that uses the 'Air Temperature Sensor' type now will automatically include these properties. This makes it much easier to set up a system with recurring parts. | Any asset that uses the 'Air Temperature Sensor' type now will automatically include these properties. This makes it much easier to set up a system with recurring parts. | ||
| - | If you had a specific //model// of temperature sensor that you regularly use around the plant, you could even go a step further and make a sub-tag of 'Air Temperature Sensor' for the model, then both the appearance of the item and add media (such as photographs, specification sheets and manuals) to that tag. | + | If you had a specific //model// of temperature sensor that you regularly use around the plant, you could even go a step further and make a sub-type of 'Air Temperature Sensor' for the model, then both the appearance of the item and add media (such as photographs, specification sheets and manuals) to your new type. |
| Then, when you tagged any asset as that model sensor, it would inherit the media from the //direct// type, plus the temperature measurement and calibration date properties from the //indirect// type. | Then, when you tagged any asset as that model sensor, it would inherit the media from the //direct// type, plus the temperature measurement and calibration date properties from the //indirect// type. | ||
| - | ===Suggested Templates=== | + | ===Suggested Types=== |
| If you have a number of different types of media, and you're measuring the same property on more than one of them (ie. **water pressure** vs **air pressure**), then we suggest creating a different type //for each instrument and media type//. | If you have a number of different types of media, and you're measuring the same property on more than one of them (ie. **water pressure** vs **air pressure**), then we suggest creating a different type //for each instrument and media type//. | ||
| Line 37: | Line 37: | ||
| </WRAP> | </WRAP> | ||
| - | Although this is a little time-consuming during setup, it allows you to add new sensors to your ARDI system extremely quickly. | + | Although this is a little time-consuming during setup, it allows you to add new sensors to your ARDI system extremely quickly. For larger systems, it's a time-saving technique. |
| ===Media=== | ===Media=== | ||
| Line 43: | Line 43: | ||
| As well as [[properties|properties]] and [[alerts|alerts]], [[media|media]] is also inherited. | As well as [[properties|properties]] and [[alerts|alerts]], [[media|media]] is also inherited. | ||
| - | Adding documentation - such as instruction manuals or work instructions - to a tag distributes that media to all sub-objects. This makes administering your documents much easier - a single change to one asset feeds through to all of the sub-assets that share the tag. | + | Adding documentation - such as instruction manuals or work instructions - to a type distributes that media to all sub-objects. This makes administering your documents much easier - a single change to one asset feeds through to all of the sub-assets that share the type. |
| ===License Issues=== | ===License Issues=== | ||
| - | Note that types do not count to your [[ardiadmin:active asset total]] unless they have properties attached. | + | Note that types do not count to your [[ardiadminguide:active_elements|active element]] count unless they have properties attached. |