The Metal & Machining domain model represents discrete manufacturing processes such as turning, milling, grinding, welding, heat treatment, inspection, and subcontracted production.
It covers production structure, jobs and routing, machines and tooling, material traceability, dimensional measurements, resource use, maintenance, quality, and operational events.
What is specific to this model
When integrating Metal & Machining production, pay particular attention to:
- Jobs and operations as the central production context.
- Routing and planning for describing how a part is expected to move through production and which resources are planned for production work.
- Parts and features for representing manufactured items and the characteristics that are inspected or measured.
- Feature measurements for dimensional and quality measurements associated with individual pieces and operations.
- Machines, tools, fixtures, and gauges used during machining and inspection.
- Material traceability through heats, suppliers, certificates, and actual material consumption.
- Tool traceability and tool life through tool batches, usage, and tool changes.
- Machine states for recording production, setup, downtime, and other operating conditions.
- Inspection and nonconformance for recording quality checks and deviations.
- Subcontracted operations performed outside the organization.
- Maintenance and customer quality through maintenance records, nonconformances, and complaints.
Integration
Metal & Machining supports the standard Pulse integration options described in Getting started.
For Metal & Machining-specific guidance:
All supported integration options use the same Metal & Machining domain model and its documented resources and relationships.
Integration flow
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 tenant.
- A valid authentication token.
- Access to the source data you want to submit.
See Authentication and First API request.
Map source data to the Metal & Machining domain model
Start by identifying how records from the source system map to the Metal & Machining resources.
Required integration data
Pulse distinguishes between the minimum data needed to start producing useful analysis and the broader data required for a complete Metal & Machining deployment.
At minimum, a pilot should provide:
- Plants, Work centres, and Machines so production structure and Machine activity can be grouped and analyzed;
- Jobs and Operations with routing sequence, Machine, quantity, and start and end times;
- Machine states so Machine time can be accounted for;
- enough populated business context to compare Machines, Jobs, and production periods meaningfully.
For richer analysis, provide Routing for production standards and efficiency, and Output for good production, rework, downgrade, and scrap quantities.
A complete deployment requires additional planning, material traceability, measurements, resource consumption, tooling, maintenance, and quality data depending on the configured scope.
Master data
Register relatively stable business records such as:
- Plants
- Work centres
- Machines
- Tools
- Fixtures
- Gauges
- Parts
- Features
- Programs
- Materials
- Suppliers
- Customers
- Shifts
- Crews
- Tool batches
See Master data.
Definitions and rules
Define measurements, expected values, classifications, and reasons referenced by production data:
Planning and production
Map the production lifecycle and expected process:
Materials and traceability
Map material traceability records such as:
See Materials and traceability.
Operational data
Submit what actually happened during production:
See Operational data.
Maintenance and quality
Submit maintenance and quality-related records:
Resource identity
Metal & Machining resources use documented business identifiers to identify records and relationships.
Some resources may use a single business code, while others may use a documented combination of business fields.
Use the identifier documented for each resource when creating references or retrieving existing records. Do not use internal Pulse identifiers.
Timestamps
Use ISO 8601 timestamps with an explicit UTC offset where a date and time is required.
For example:
2026-08-10T22:00:00+02:00
Validate the integration
Before submitting data:
- Confirm required referenced records exist.
- Use supported enum values.
- Use the documented business identifiers.
- Use valid timestamps.
- Use the documented quantity and unit fields.
- Inspect API responses before submitting dependent records.
See Validation and Troubleshooting.
Metal & Machining integration areas
| Area | Purpose |
|---|---|
| Master data | Stable business records such as plants, work centres, machines, tooling, parts, materials, and organizational context. |
| Definitions and rules | Measurement definitions, expected values, classifications, and reason codes used by other records. |
| Planning and production | Jobs, routing, operations, plans, production steps, subcontracting, treatments, and inspections. |
| Materials and traceability | Material heats, certificates, and certificate plans. |
| Operational data | Feature measurements, readings, output, consumption, machine states, events, and tool changes. |
| Maintenance and quality | Maintenance, nonconformances, and complaints. |
Recommended next steps
- Complete Authentication.
- Send the First API request.
- Review the Metal & Machining domain model.
- Follow the end-to-end Metal & Machining scenario.
- Use the API reference to inspect resource paths and operations.