Represents a quality check you perform on your product, for example pH, fat content, moisture, or fill weight. In the Excel template, checks are registered on the What you check sheet.
A check defines a code for a quality result. The results themselves are submitted as readings, in the same way as values of What you measure.
Use What you check for results about the product, and What you measure for conditions such as temperatures and pressures.
The Check object
{
"code": "ph",
"name": "pH",
"unit": null,
"valueType": 0,
"plausibleMin": 0,
"plausibleMax": 14
}
Fields
| Field | Type | Description | Example |
|---|---|---|---|
code |
string | Unique business code of the check. Readings, machines, and product limits refer to it. | "ph" |
name |
string | Human-readable name of the check. | "pH" |
unit |
string or null | Unit of the results. | null |
valueType |
integer | Kind of value, as a number. See Kinds of value. | 0 |
plausibleMin |
number or null | Lowest result that is plausible. Results below it are kept, but marked as suspect. | 0 |
plausibleMax |
number or null | Highest result that is plausible. Results above it are kept, but marked as suspect. | 14 |
Important
code must be unique across checks, measurements, setpoints, and the other codes Pulse uses for values. A code that is already used for something else is refused.
If you leave out valueType, it is 0 (continuous). A check has no reading interval: each result is recorded when it is taken.
Where checks are used
-
Readings: quality results are submitted as readings with the check's code as
measurement. -
Machines and sensors: a machine's
measuresfield can name a check, for example an in-line pH sensor. - Product limits: a product limit can set the allowed range of a check for a product.
Register checks before production lines and machines, because machines can name the checks they perform.
Reserved codes
Some codes are used by Pulse itself, for example for yield, OEE, and quality percentages that Pulse calculates, and for the analysis of incoming lots (incoming-fat, incoming-protein, incoming-ph, incoming-brix). These codes are not returned by this resource. Do not use them for your own checks: a code that is already in use is refused.
API resource
| Resource | Base path |
|---|---|
Check |
/manufacturing/food-beverage/v1/checks |
API methods
Create a check
POST /manufacturing/food-beverage/v1/checks/insert
Creates a new check and returns its Pulse identifier.
Request
POST /manufacturing/food-beverage/v1/checks/insert
Content-Type: application/json
{
"code": "ph",
"name": "pH",
"valueType": 0,
"plausibleMin": 0,
"plausibleMax": 14
}
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
code |
string | yes | Unique business code of the check. |
name |
string | yes | Human-readable name of the check. |
unit |
string or null | no | Unit of the results. |
valueType |
integer | no | Kind of value, as a number. Default: 0 (continuous). |
plausibleMin |
number or null | no | Lowest plausible result. |
plausibleMax |
number or null | no | Highest plausible result. |
Update a check
PUT /manufacturing/food-beverage/v1/checks/update
Updates an existing check. The check must already exist.
An update replaces all fields. Fields you leave out are removed, and valueType returns to 0 (continuous). To change only some fields, use patch.
Request
PUT /manufacturing/food-beverage/v1/checks/update
Content-Type: application/json
{
"code": "ph",
"name": "pH value",
"valueType": 0,
"plausibleMin": 0,
"plausibleMax": 14
}
Parameters
The parameters are the same as for creating a check. code identifies the check to update.
Patch a check
PATCH /manufacturing/food-beverage/v1/checks/patch
Partially updates an existing check.
The fields to update are supplied in the properties object. The check is identified by its business code, which cannot be changed. Fields you leave out keep their current values. To remove a value, send it as null.
Request
PATCH /manufacturing/food-beverage/v1/checks/patch
Content-Type: application/json
{
"properties": {
"code": "ph",
"plausibleMin": 2
}
}
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
properties |
object | yes | Fields included in the partial update. |
properties.code |
string | yes | Business code of the check to update. |
properties.name |
string | no | New name. |
properties.unit |
string or null | no | New unit, or null to remove it. |
properties.valueType |
integer | no | New kind of value, as a number. |
properties.plausibleMin |
number or null | no | New lowest plausible result, or null to remove it. |
properties.plausibleMax |
number or null | no | New highest plausible result, or null to remove it. |
Retrieve a check
GET /manufacturing/food-beverage/v1/checks/select
Returns the check identified by its business code. If no check has this code, the response is empty.
Request
GET /manufacturing/food-beverage/v1/checks/select?id=ph
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id |
string | yes | Business code of the check to retrieve. |
List checks
GET /manufacturing/food-beverage/v1/checks/query
Returns checks matching the supplied filters.
Request
GET /manufacturing/food-beverage/v1/checks/query?codes=ph
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
codes |
string or array of strings | no | Limits results to checks with the specified business codes. |
Delete a check
DELETE /manufacturing/food-beverage/v1/checks/delete
Deletes the check identified by its business code. If no check has this code, nothing happens.
Request
DELETE /manufacturing/food-beverage/v1/checks/delete?id=ph
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id |
string | yes | Business code of the check to delete. |