CONCEPT
Fields | Type | Description | Purpose |
---|---|---|---|
ID (Concept identifier) | M | on_standby | GRAMMAR |
Concept name | M | On Standby | GRAMMAR |
Concept type | M | status | GRAMMAR |
|
|
|
|
Also known as | O | On; Not Off; Power On; Ready to work; standby; With power; Engine on; Power supply on; idle; | TIC Description |
Definition | M | If the main power supply and all subject systems are ready to operate (do the job it has been designed for) in less than 2 seconds but any (at least one) of them is not currently ready then TRUE else FALSE | TIC Description |
Further Detail | O | On Standby is a special type of On status where the subject is not currently ready but almost. If off is TRUE then on_standby has to be FALSE | TIC Description |
Required Information | M | SUBJECT; OBSERVED PROPERTY and VALUE | TIC Description |
SUBJECT |
| #CHE; #STS; #SC; #RTG; #RMG; #TT; #FKL; #Gate; #Terminal; #MC; #TOS ; #Luminary |
|
POINT OF MEASUREMENT |
| #input;#internal_in ; #internal_out ;#output #schedule; #planning; #estimated; #actual; #performed |
|
OBSERVED PROPERTY |
| #status; #counter; #duration; #timer; #totaltimer #energy; #startevent; #startcounter; #endevent; #endcounter; #distance; |
|
Value |
| TRUE; FALSE; real number; integer |
|
Related standards | O |
| TIC Description |
Related TIC 4.0 definition | O | #off; #on_standby | TIC Description |
Example | M | che_on_status: TRUE = the Container Handler Equipment is ready to operate or do its job properly in less than 2 seconds because the power, the control and all of its systems are able to be ready on time but currently is not. che_spreader_on_status: TRUE = the Spreader of the Container Handler Equipment is ready to operate properly (lock-unlock-expand-contract) in less than 2 seconds but currently is not. che_engine_on_status: FALSE = the Engine of the Container Handler Equipment is not ready to generate the power to the CHE working properly in less than 2 seconds but currently is not. | TIC Description |
Example in the context of the grammar | M | An RTG with the Engine and control On but the drivers off and the cabin gate open che_engine_on_status: TRUE; che_drivers_on_status: FALSE; che_control_on_status: TRUE; che_cabingateopen_status: TRUE; che_on_status: TRUE; che_on_standby_status: TRUE | TIC Description |
Link to one or more operational processes | M | Any CHE load or discharge operation. | TIC Description |
Search tags | M | #OFF; #Off; #off; #ON; #On; #on; #standby; #running; #working | Technical |
Version / Date | M | TIC_Q4_2020 / 15.09.2020 | Technical |
Internal TIC Version | M | definition technical group | Technical |
M = Mandatory
O = Optional
OLD PROPOSAL
ID | 37 |
Name | CHE Activity On |
Abbreviation | che.activity.on.command||request||feedback||action.status||counter||timer||energy||distance |
Category | |
Also known as | On; Running; Power On; Engine On |
Definition | IF (CHE_Activity_Off.status : False) then True else False |
Further Detail | CHE_Activity_On is the opposite of CHE_Activity_Off, when a CHE is not off is on, it doesn't give any extra information. If main power supply is available in less than 2 seconds then true else false. CHE_Activity_Working and CHE_Activity_Working_Idle is under ON, so a machine that is ON only can be Working or Idle. CHE_Activity_On is the contrary of CHE_Activity_Off |
Required | |
Related standards | |
Related TIC 4.0 definition |
HEADER
Identifies the message in origin, destination, time and unique reference (use this link for more information)
Mandatory | Header message timestamp; Header message identifier; Header sender identifier; Header time; Header time start; Header time end |
Optional | (Header topic; Header identifier) |
SUBJECT
Defines the perimeter and id of the subject (usually defined as a process) (use this link for more information)
Default | Identifier (Abbreviation, Definition, Long definition); Class (Abbreviation, Definition, Long definition, Suitable) |
Suitable | Name; Number; Family; Subsystem (Abbreviation, Definition, Long definition, Suitable, Examples) |
POINT OF MEASUREMENT
It defines wherein the process (step, place or time) the observed property of the concept is measured (use this link for more information)
Default | IN; Request; Feedback; OUT (scheduled; planning; estimated, calculated; actual; verified) |
Optional | Control (from where) |
OBSERVED PROPERTY
It is the magnitude of the concept (units, volume, weight, energy, time, etc.) (use this link for more information)
Default | Status; %; Speed; Counter; Distance; Timer; Energy; Average; … |
Suitable | Specify units when they are different than the International System |
Units | True/False |
Draws
(optional) add some draws to explain the concept
Diagrams
(optional) add some process diagram which concept belongs
Attached documents
(optional) add some document to explain the concept
Examples
Human
1.20191205 12:00 London-Gate03 move “get_in” “out=result” actual boxes “1”
2.20191205 12:06 London-TZ01 move “occupied” in actual boxes “1”
3.20191205 12:18 London-SC74 move “in” actual boxes “1” (waiting for orders)
4.20191205 12:22 London-SC74 move “Lock” actual boxes “1”
5.20191205 12:22 London-TZ01 move out actual boxes “1”
6.20191205 12:32 London-Yard_A-34B56 move “occupied” in actual boxes “1”
JSON:
XML:
MQTT:
Created by | Edited by | Review / Approve | Published |