Food & Beverage overview – Pulse

The Food & Beverage model represents manufacturing processes such as dairy, beverages, bakery, meat processing, and prepared foods.

It covers production structure, traceability, bulk processing, production runs, resource use, measurements, cleaning, maintenance, quality, and operational events.

What is specific to this model

When integrating Food & Beverage production, pay particular attention to:

Batch and lot traceability for incoming materials, bulk production, and finished product.
Process measurements and settings such as temperature, pressure, pH, fill weight, and equipment setpoints.
Resource use for ingredients, packaging, chemicals, utilities, Labor, equipment, and other production inputs.
Production output and losses including good output, waste, downgraded product, and rejects.
Supplier and lot context where incoming-material differences may affect production results.
Production-line time accounting for breakdowns, micro-stops, waiting, maintenance, and other non-running states.
Cleaning and changeovers between products, including expected and actual cleaning duration.
Maintenance and quality through work orders, maintenance resource use, holds, and customer complaints.

Integration

Food & Beverage supports the standard Pulse integration options described in Getting started.

For Food & Beverage-specific guidance:

Integration flow

Diagram 1

The exact submission order depends on the source system and the records being integrated. Referenced records must exist before records that depend on them.

Before you begin

You need:

The API base URL assigned to your Pulse environment.
A valid API token.
Access to the source data you want to submit.

See Authentication and First API request.

Map source data to the Food & Beverage domain model

Start by identifying how records from the source system map to the Food & Beverage resources.

Required integration data

Pulse distinguishes between the minimum data needed to start producing useful analysis and the broader data required for a complete Food & Beverage deployment.

At minimum, a pilot should provide:

sites, production lines, products, shifts, and crews;
runs with start and end times;
output by quality;
consumption with quantities and units;
enough populated business context to compare runs meaningfully.

A complete deployment requires additional production, line time, maintenance, cleaning, quality, and planning data depending on the configured scope.

Master data

See Master data.

Definitions and rules

Define the measurements, specifications, classifications, and operational rules referenced by production data:

See Definitions and rules.

Production activities

Map the production and traceability lifecycle:

See Production activities.

Operational data

Submit what actually happened during production:

See Operational data.

Maintenance and quality

Submit maintenance and customer-quality records:

See Maintenance and quality.

Business codes

Food & Beverage API requests and references use business codes rather than numeric identifiers.

For example:

{
  "code": "L01-260810-002",
  "line": "LINE001",
  "product": "PRD001"
}

LINE001 and PRD001 are the business codes of the referenced Production line and Product.

The same convention is used throughout the Food & Beverage API.

Timestamps

Use ISO 8601 timestamps with an explicit UTC offset where a date and time is required.