Device (dev)
The Device-Entity stores information about a machine or instrument (i.e. equipment, tool, machine, car, truck etc.). Devices can be reserved to processes like projects (1:n realtion) through the devprj entity.
Database level
The entity's attributes are shown below. Mandatory fields are marked with a red star:
Name | Type | Label | Description |
|---|---|---|---|
form* | String | Respresents the entity form. Will always be "dev". | |
dev_categ* | String | Represents a device category to which the device belongs (i.e. "equipment", "cars", "trucks" ). | |
dev_categ_text* | String | Represents a device category to which the device belongs (i.e. "equipment", "cars", "trucks" ). | |
dev_name* | String | Respresents the device name (i.e. "Building Phoenix"). | |
dev_nr* | String | Respresents the device number. | |
dev_model_name* | String | The name of the organisation within new contact person is employeed. | |
dev_model_nr* | String | Model number of the device. | |
dev_manufacturer* | String | The name of company which is the producer. | |
dev_end | Date | The date on which the use of the device ceases. The date the device will be scrapped. | |
dev_start | Date | The date on which the use of the device begins. | |
dev_price | Number | The aquisition price of the device. | |
dev_next_insp | Date | The date on which the next inspection is scheduled. | |
dev_next_rev | Date | The date on which the next revizion is scheduled. |
QEE classes level:
The class representing the device is QEEDev.
Inherits from: QEEObject.
REST level
The endpoints dealing with devices are:
xrDev (GET, POST, PUT, DELETE)
xrDevs (GET, PUT, DELETE)