Every result has a story.
Keep the context.

Before-test MES validation can determine whether a unit may proceed. After-test exchange sends the configured result and identity information. The application provides file-based integration and IP-based MES; advanced request/response workflows are configured separately in Data Link.

MES configuration Inside the software

Enlarge

TCP Raw and HTTP/HTTPS MES

In the IP-based MES workspace, configure the before/after message contract, endpoint, payload template, accepted response and timeout. HTTP requests also use the relevant URL, method and content type. Identity fields can include the barcode, model, machine, station, line, operator and timestamp.

Use manual trials and TX/RX previews to check the actual message and reply. A connected socket or an HTTP response alone is not the same as the MES business rule accepting the unit.

File-based MES defines how the station reads or writes a production record through configured folders. CSV/TXT content, filename patterns, timing and validation rules make the exchange meaningful to both systems.

Interlocking before the test

Configure the supported file-existence, text/line-content or CSV lookup check for the scanned identity. Review file age, timeout and network-failure behaviour, then use the rule trial to inspect accepted and rejected cases.

Commission the integration with accepted, rejected, missing and malformed files. Agree when an upstream file is complete and how repeated or delayed output is reconciled by the receiving system.

The separately licensed Data Link workspace is under Test Sequence. Define reusable connections and requests, configure authentication and payloads, map response values into variables and decide which response means success.

1. Before testing

   Fetch or validate external values and make the mapped information available to the supported production workflow.

2. During the sequence

   Invoke a configured Data Link operation where the test needs an external request or decision.

3. After testing

   Upload the configured result and retain delivery evidence for review or recovery.

Run request trials before assigning them to production. Before/after integration depends on the plan arrangement; shared-master plans are not supported for those Data Link assignments. Required report and cleanup completion also affect result-upload readiness.

Local storage, a shared-folder write and an external upload can fail for different reasons. Review the relevant report/delivery status and logs to determine which stage needs recovery. Data Link delivery records and outbox controls provide evidence for incomplete exchange.

• Test delayed replies, rejected responses and disconnected endpoints.
• Verify write access using the Windows account that will run the station.
• Check recovery after an interrupted delivery or application restart.
• Agree how the receiving system recognises repeated delivery of the same run.

A repeatable run identifier can support duplicate handling when the receiving service implements the same contract. Retrying a delivery does not by itself guarantee exactly-once processing. Configured report or delivery holds must be resolved before the affected next-test path can continue.

Use barcode history to inspect recorded attempts and available attachments. Production reports and the KPI dashboard provide model, date, result and the available barcode, plan, flow or shift context for narrowing an investigation.

KPI dashboard Inside the software

Enlarge

Choose the required fields and retention locations during setup. A dashboard can only analyse records that the station has actually retained.

Cycle Time Audit identifies controllable waits in the PASS cycle and supports reviewed changes with a recorded reason. It separates the timing configuration from the actual production evidence used to accept a change.

1. Review the baseline

   Inspect the selected flow and controllable waits. Choose changes that preserve the required product and instrument settling behaviour.

2. Save a trial

   Edit the relevant timing values, record the reason and use SAVE TRIAL.

3. Run the validation

   Run the trial from the production Testing workspace. Three consecutive PASS runs are required before production approval.

4. Apply or restore

   Use APPLY PRODUCTION after successful validation, or RESTORE PASS to return to the last passing configuration as appropriate.

Configured wait reduction is not a promised throughput gain. Compare actual cycle and handling records, and review measurement stability and failure behaviour before accepting the new timing.

The licensed Quality Alerts workflow connects notification accounts and recipient groups with model policies, severity and message templates. Configure schedules, cooldowns, recovery notifications and escalation to match the process.

Available attachments and delivery/outbox evidence help recipients investigate the event. Review failed delivery and retry status so an attempted notification is not mistaken for confirmed communication.