Assets ​

Creating Assets ​

Selecting the "+" plus button on an Argonaut Location on the Asset page displays the following entry Asset entry dialog.

• Asset name field must be unique within the direct parent location
• Location determines the Asset's Calendar
• Asset Type is required for mapping the Asset Codes to the raw numeric machine code
• Cycle Time is the ideal time (in seconds) for this asset to produce 1 part.

Creating Asset Types ​

Asset Types can be created by selecting the "+" plus button from the Assets page. The Asset Type Name field allows for a common name to be set.

Asset Failure Codes ​

Selecting the "Fault Codes" tab displays configurable Fault codes, "Intervention Codes" displays configurable Manual Intervention codes, and selecting "Warning Codes" displays configurable Warning codes.

Asset codes can either be entered one-by-one using the "Add Asset Code" button, or in bulk by copying data from a Spreadsheet program and pasting the values into the table. Clicking the "Clear Asset Codes" button removes all the asset codes on the page for the particular tab being viewed. The delete button on each code can be used to individually remove a code & description if desired.

State Codes ​

Selecting the "State Codes" tab displays configuarble State codes. The "Core State" tab show special state codes used by Argonaut to build reports that take meaning into consideration. For example, the Constraint report understands that fault and intervention mean that a station is down, vs a cycling state which indicate that the station is running as expected. Additional state labels can be created by using the "Add Data Label" menu selection. All properties (Code, Description & Color) are able to be set.

The value chosen for the color is used when reporting on the state.

FIS Data ​

Monitoring Data in Argonaut is expected to be stored on-change. Each piece of FIS data requires a valid date/time, an Asset to track data to, a Data Label, and a numeric value representing the value to store. The date/time value must be in UTC time and not include an offset (it will be truncated if provided). The Asset must be a valid asset, where the asset could represent anything FIS data can be tracked to.

The Data Label is a pre-configured identification of the type of information being recorded. There are 4 FIS Data Label Types in Argonaut (counter, code, state & scalar).

• Data Labels
  • Good Count counter
    • The number of good material created at this asset
    • Note: The number can be a rolling increment, or a literal count. Which is used depends on the timing data property defined when collected
  • Bad Count counter
    • The number of bad material created at this asset
    • Note: The number can be a rolling increment, or a literal count. Which is used depends on the timing data property defined when collected
  • Machine Fault code
    • Describes the most root-fault of a particular fault event. The number is the machine code for the type of fault thrown
  • Manual Intervention code
    • Describes the most root-manual-intervention of a particular intervention event. The number is the machine code for the type of intervention thrown
  • Warning code
    • Describes a recordable warning event. The number is the machine code for the type of warning issued
  • Asset State state
    • Used by most reports to represent core state changes to an Asset.
    • Note: Al core state must be configured per Asset type in order to be identified by the report

Calendars ​

FIS Data is post-processed to handle assigning productive status and shift/event data. These configurations come from the Calendar assigned to the Asset's configured location. In the event of a moving Asset (like an AGV), the asset's configured location is not expected to change, but rather be at a higher level location encompasing the travel of the asset.