Reading

Records a measured value captured at a specific point in time.

For example, a temperature sensor can record the product temperature in a vessel, or a checkweigher can record the weight of an individual package.

Readings can describe production resources and activities such as lines, machines, vessels, runs, batches, and lots.

The Reading object

{
  "subject": "EQ003",
  "measure": "product-temp-holding",
  "value": 74.2,
  "sensor": "EQ003-TT-HOLD",
  "at": "2026-08-10T22:11:00+02:00"
}

Fields

Choosing the subject

subject identifies the object or production activity that the measured value describes.

Typical subjects include:

• Production line
• Machine
• Vessel
• Run
• Batch
• Lot

For example:

{
  "subject": "EQ003",
  "measure": "product-temp-holding",
  "value": 74.2,
  "sensor": "EQ003-TT-HOLD",
  "at": "2026-08-10T22:11:00+02:00"
}

A Run-level reading could instead use:

{
  "subject": "L01-260810-002",
  "measure": "fill-weight",
  "value": 128.4,
  "sensor": "EQ010-H06",
  "at": "2026-08-10T22:11:02+02:00"
}

Attach the Reading to the subject the value actually describes.

For example, a Vessel temperature should use the Vessel as its subject rather than the Production line it supplies.

Sensors

Use sensor when the source of the measurement needs to be preserved or when several measurement points can report the same Measurement for the same subject.

For example:

{
  "subject": "EQ003",
  "measure": "product-temp",
  "value": 74.2,
  "sensor": "EQ003-TT-01",
  "at": "2026-08-10T22:11:00+02:00"
}

and:

{
  "subject": "EQ003",
  "measure": "product-temp",
  "value": 74.4,
  "sensor": "EQ003-TT-02",
  "at": "2026-08-10T22:11:00+02:00"
}

represent two different Readings because sensor is part of the composite key.

If no sensor needs to be distinguished, sensor can be omitted.

Individual pack weights

For individual pack weights, sensor can identify the filling head or measurement point that produced each Reading:

{
  "subject": "L01-260810-002",
  "measure": "fill-weight",
  "value": 128.4,
  "sensor": "EQ010-H06",
  "at": "2026-08-10T22:11:02+02:00"
}

Keeping the individual values and their sensor codes preserves the variation needed to compare filling heads and detect systematic overfill, underfill, or instability.

Value type

The Measurement definition determines how value is interpreted.

Examples include:

{
  "value": 74.2
}

for a numeric Measurement,

{
  "value": true
}

for a Boolean Measurement, or:

{
  "value": "high"
}

for a categorical Measurement.

Values must be compatible with the Measurement's declared value type.

Plausibility

Numeric Measurements can define plausible bounds through minValue and maxValue.

When a Reading falls outside those bounds, Pulse retains the submitted value but marks it as bad-quality data internally.

This allows suspicious measurements to remain traceable rather than being silently discarded.

Measurements and settings

Readings contain values that were actually measured.

Commanded or configured values are submitted separately through Setting.

Measured value  → Reading
Commanded value → Setting

Reference protection

A resource, production activity, or registered sensor referenced by an existing Reading cannot be deleted while the Reading still references it.

API resource

Resource	Base path
Reading	/manufacturing/food-beverage/v1/readings

API methods

Submit a reading

POST /manufacturing/food-beverage/v1/readings/insert

Records one measured value.

Request

POST /manufacturing/food-beverage/v1/readings/insert
Content-Type: application/json

{
  "subject": "EQ003",
  "measure": "product-temp-holding",
  "value": 74.2,
  "sensor": "EQ003-TT-HOLD",
  "at": "2026-08-10T22:11:00+02:00"
}

Parameters

Parameter	Type	Required	Description
subject	string	yes	Business code of the measured resource or production activity.
measure	string	yes	Business code of the Measurement.
value	number, string, or boolean	yes	Captured value.
sensor	string or null	no	Registered measurement-source code.
at	string	yes	Date and time when the value was captured.

Update a reading

PUT /manufacturing/food-beverage/v1/readings/update

Updates the value of an existing Reading.

The Reading is identified by subject, measure, sensor, and at.

Request

PUT /manufacturing/food-beverage/v1/readings/update
Content-Type: application/json

{
  "subject": "EQ003",
  "measure": "product-temp-holding",
  "value": 74.6,
  "sensor": "EQ003-TT-HOLD",
  "at": "2026-08-10T22:11:00+02:00"
}

Patch a reading

PATCH /manufacturing/food-beverage/v1/readings/patch

Partially updates an existing Reading.

properties.subject, properties.measure, and properties.at are required to identify the Reading.

When the Reading has a sensor, include properties.sensor as part of the key.

PATCH changes the Reading's value; the composite key itself remains unchanged.

Request

PATCH /manufacturing/food-beverage/v1/readings/patch
Content-Type: application/json

{
  "properties": {
    "subject": "EQ003",
    "measure": "product-temp-holding",
    "sensor": "EQ003-TT-HOLD",
    "at": "2026-08-10T22:11:00+02:00",
    "value": 74.6
  }
}

Parameters

Parameter	Type	Required	Description
properties	object	yes	Fields included in the partial update.
properties.subject	string	yes	Subject business code identifying the Reading.
properties.measure	string	yes	Measurement business code identifying the Reading.
properties.sensor	string or null	conditional	Sensor component of the Reading key. Include it when the Reading has a sensor.
properties.at	string	yes	Timestamp identifying the Reading.
properties.value	number, string, or boolean	no	New measured value.

Retrieve a reading

GET /manufacturing/food-beverage/v1/readings/select

Returns the Reading identified by its composite business key.

Request

GET /manufacturing/food-beverage/v1/readings/select?subject=EQ003&measure=product-temp-holding&sensor=EQ003-TT-HOLD&at=2026-08-10T22:11:00%2B02:00

Query parameters

Parameter	Type	Required	Description
subject	string	yes	Business code of the measured subject.
measure	string	yes	Business code of the Measurement.
sensor	string	no	Sensor component of the Reading key.
at	string	yes	Date and time of the Reading.

Example response

{
  "subject": "EQ003",
  "measure": "product-temp-holding",
  "value": 74.2,
  "sensor": "EQ003-TT-HOLD",
  "at": "2026-08-10T22:11:00+02:00"
}

List readings

GET /manufacturing/food-beverage/v1/readings/query

Returns Readings matching the supplied filters.

Request

GET /manufacturing/food-beverage/v1/readings/query?subjects=EQ003&measures=product-temp-holding

Query parameters

Parameter	Type	Required	Description
subjects	string or array of strings	no	Limits results to the specified subject business codes.
measures	string or array of strings	no	Limits results to the specified Measurements.
sensors	string or array of strings	no	Limits results to the specified sensor codes.
from	string	no	Limits results to Readings captured at or after the specified date and time.
to	string	no	Limits results to Readings captured at or before the specified date and time.

Multiple values can be supplied by repeating the query parameter:

GET /manufacturing/food-beverage/v1/readings/query?sensors=EQ003-TT-01&sensors=EQ003-TT-02

Delete a reading

DELETE /manufacturing/food-beverage/v1/readings/delete

Deletes the Reading identified by its composite business key.

Request

DELETE /manufacturing/food-beverage/v1/readings/delete?subject=EQ003&measure=product-temp-holding&sensor=EQ003-TT-HOLD&at=2026-08-10T22:11:00%2B02:00

Query parameters

Parameter	Type	Required	Description
subject	string	yes	Business code of the measured subject.
measure	string	yes	Business code of the Measurement.
sensor	string	no	Sensor component of the Reading key.
at	string	yes	Date and time of the Reading.