TIC 4.0
Interlock
- Francisco Blanquer Jaraiz
- Luisa Kempf
- Jan Willem Houwers
CONCEPT
Fields | Type | Description | Purpose |
|---|---|---|---|
ID (Concept identifier) | M | interlock | GRAMMAR |
Concept name | M | Interlock | GRAMMAR |
Concept type | M | status | GRAMMAR |
Also known as | O | condition, flag, stop, system information, process information | TIC Description |
Definition | M | Interlock conditions are defined as a way to prevent something from happening in a system. | TIC Description |
Further Detail | O | source: What is an Interlock? - RealPars Non-safe (process) interlock: gives information informations about system process status that prevents incorrect operation or possible damage to the process or equipment. Safe interlock: gives information about system process status that prevents possible damage or death to people operating that process or equipment. A mechanical interlock is an interlock that is physically connected to another device to prevent unintended actions. An electrical interlock is an interlock that is used to restrict current flow between two or more devices. A logical interlock has an instruction or variable which has to be true to allow a result. Logical interlocks are useful when the devices are not easily connected electrically or mechanically. This is the most common interlock used by TIC 4.0 and are related to the software of the equipment control system. It becomes more attention in full automated systems. | TIC Description |
Required Information | M | SUBJECT; OBSERVED PROPERTY and VALUE | TIC Description |
SUBJECT | M | GRAMMAR | |
POINT OF MEASUREMENT | O | ioutput estimated; actual; performed | GRAMMAR |
OBSERVED PROPERTY | M | status; duration; counter; timer; totalcounter; totaltimer | GRAMMAR |
Value | M | tic40codeid | GRAMMAR |
Related standards | O | J1939 | TIC Description |
Related TIC 4.0 definition | O | https://tic40.atlassian.net/l/c/pBWAiKtghttps://tic40.atlassian.net/l/c/sHgs2815 https://tic40.atlassian.net/l/c/jCkb1RZA ErrorMessage https://tic40.atlassian.net/l/c/GRD7muAHhttps://tic40.atlassian.net/l/c/sWjfo1T1 | TIC Description |
Example | M | Waiting for clearance (areas in which containers “handover” from one CHE to another): che.health.healthy.status.boolean : TRUE che.health.fault.status.boolean : FALSE che.health.interlock.status.boolean: TRUE che.health.interlock.status.tic40codeid: 1.2.2.4765 che.health.interlock.status.tic40codename: che.hoist.hoisting.clearance che.health.interlock.status.description: Waiting for clearance che.health.interlock.status.timer.seconds: 356 che.health.warning.status.boolean: TRUE ASCs with SC handover areas can be secured with safety light barriers and sensors for detection of SCs moving inside this area. In a normal case, the SC requests access to the area, enters the area after entry access is permitted, the area is then occupied by the SC and the ASC is not allowed to move in the same area (process interlock). It happens, that sensors are not detecting SC going out (caused by wheather condition or dirty reflectors). The system lock the ACS transferpoint waiting for clearance, but after a while this ends up in a warning (interlock gets longer than expected) but without any error. | TIC Description |
Example in the context of the grammar | M | Waiting for clearance (handover areas) in JSON format: {
"che": [
{
"id": "",
"name": "",
"health": [
{
"id": "",
"name": "",
"number": 0,
"type": "",
"family": "",
"brand": "",
"model": "",
"source": "",
"softwareid": "",
"location": "",
"healthy": {
"status": [
{
"value": true,
"type": "operational",
"pom": "output",
"pomt": "actual",
"timestamp": "2021-11-19T16:06:54.891Z"
}
],
"level": [
{
"value": "100",
"type": "component",
"unit": "percentage",
"pom": "output",
"pomt": "actual",
"timestamp": "2021-11-19T16:06:54.891Z"
}
]
},
"interlock": {
"status": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "output",
"pomt": "actual",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": true,
"description": "Waiting for clearance",
}
],
"duration": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "output",
"pomt": "actual",
"unit": "second",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": 1,
"description": "Waiting for clearance",
}
],
"counter": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "output",
"pomt": "actual",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": 32,
"starttimestamp": "2021-11-19T16:05:54.892Z",
"endtimestamp": "2021-11-19T16:06:54.892Z",
"description": "Waiting for clearance",
}
],
"totalcounter": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "ioutput",
"pomt": "actual",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": 347,
"description": "Waiting for clearance",
}
],
"timer": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "output",
"pomt": "actual",
"unit": "second",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": 63,
"starttimestamp": "2021-11-19T16:05:54.892Z",
"endtimestamp": "2021-11-19T16:06:54.892Z",
"description": "Waiting for clearance",
}
],
"totaltimer": [
{
"tic40codeid": "1.2.2",
"tic40codename": "che.hoist.hoisting",
"pom": "output",
"pomt": "actual",
"unit": "hour",
"timestamp": "2021-11-19T16:06:54.892Z",
"value": 4.32,
"description": "Waiting for clearance",
}
]
}
}
]
}
]
} | TIC Description |
Link to one or more operational processes | M |
| TIC Description |
Search tags | M |
| Technical |
Version / Date | M | 2022.003 - 15/01/2022 | Technical |
Internal TIC Version | M | 2021213 | Technical |
M = Mandatory
O = Optional
Created by | Edited by | Review / Approve | Published |
@Francisco Blanquer Jaraiz 2021-11-15 | @Francisco Blanquer Jaraiz 2021-12-13 |
|
|
|
| @Luisa Kempf Dec 15, 2021 |
|
|
|
|
|
© Copyright - TIC 4.0 All rights reserved | Design web by Fundación Valenciaport