Recipe and task modelling
Approved structures, parameters, revision handling, and the relationship between a recipe and its execution.
Service
MES and digital execution
Design and build the software that runs the work.
GTMI delivers recipe structures, operator applications and production records, with the equipment and enterprise interfaces they need.
For manufacturing, quality, and digital teams planning a new execution system or extending an existing platform.
- 01
Define
Recipes, tasks, parameters
- 02
Execute
Operator steps, equipment data
- 03
Record
Entries, signatures, exceptions
- 04
Review
Approvals, controlled outputs
The product scope can include execution, records, and interfaces. Process approval and validation acceptance belong to the client.
What GTMI takes on
MES delivery, from definition to production
GTMI designs and builds manufacturing applications, extends existing applications and connects them to equipment and enterprise systems. You can commission requirements and architecture, or continue through implementation, testing and deployment. The engineering scope can use Ignition, React, PostgreSQL and OPC UA for manufacturing applications and integration. The assessment and application design help you decide whether to extend the existing system or replace a component, and which workflow to implement first. For a named packaged MES, discuss the product and required role first so we can confirm the platform fit.
Operator applications
Work instructions, data entry, equipment values, exception handling, and screens suited to production use.
Records and review
Electronic signatures, audit history, review steps, and controlled outputs shaped by the agreed requirements.
Production interfaces
Equipment capture, ERP transactions, quality records, and label services with documented ownership.
The delivery work
Recipe control and operator execution
The design keeps approved process definitions separate from the record of work performed. Recipe structures hold tasks, parameters, and revisions. Operator screens guide execution and capture entries, equipment values, signatures, and exceptions. GTMI develops these parts together so that a completed record can be traced to the definition used at the time. We review the design with the people who execute and approve the work.
Build, test, and prepare the release
Implementation can include Ignition applications, React interfaces, PostgreSQL storage, and OPC UA connectivity, according to the existing environment. Testing covers workflow behaviour and the interfaces that affect the record. For regulated delivery, requirements and release evidence follow the agreed validation strategy. GTMI also prepares deployment instructions, configuration ownership, and the support information needed for the application to enter service.
Execution deliverables
- Requirements and application architecture
- Recipe structures and operator workflows
- Implemented interfaces and tested execution paths
- Release evidence and support handover
Platforms
- Ignition
- Critical Manufacturing
- React
- PostgreSQL
- ISA-88
- ISA-95
Illustrative example: fictional manufacturing data
An instruction, an entry and an exception
An operator is assembling a fictional bracket order. The workflow shows the instruction revision, captures the count and holds a shortage for review.
Show the instruction
WI-DEMO-07, revision 03, is the released instruction assumed for this example. The record retains that revision when work begins.
Enter the count
The instruction calls for 12 components. The operator enters 11; the workflow flags the missing component.
Record the exception
One component missing. The operator records the reason and sends it for supervisor review.
Keep the state visible
The record remains in progress. The operator can see that review is pending; the unresolved shortage prevents completion.
- Instruction used
- WI-DEMO-07, revision 03
- Required / entered
- 12 / 11 components
- Exception
- One component missing
- Review state
- Pending supervisor review
- Record state
- In progress
A workflow design makes the instruction, required entries and unresolved work visible. Process owners can use it to assess the operator steps and review rules before implementation.
Working together
Application design and delivery
Engage GTMI for a requirements and architecture package, or continue through build, testing, and release preparation.
Design package
A requirements and architecture package, with decisions and dependencies recorded for your delivery team.
Application delivery
Hands-on implementation through agreed build, test, and deployment stages, with client reviews at defined points.
Where next
Define the engagement
Scope the application work
Tell us which instruction, entry or production record needs to change. We can scope an application assessment, a first operator workflow or implementation within an existing platform. A short description is sufficient; an existing record or backlog can follow later.