Identity and ownership gate
One controlled machine, mold, article, cavity, sensor-chain and responsible-party baseline with missing fields visible.
Identity evidence does not select the design, prove signal validity or release a monitoring decision.G30
CAVITY PRESSURE / MEASUREMENT CHAIN
Cavity-pressure monitoring is accepted only when the sensor-to-decision chain is identified—not when a curve is merely visible.
Release one mold, cavity and channel relationship through controlled sensor, position, connection, electronics, measurement, decision-output and configured evidence. Keep every vendor example attributed and every actual capability project-specific.
ANSWER FIRST
Put the physical measurement chain and its permitted decision output in one evidence register.
Start with the exact mold, cavity and monitored question. Then map the proposed sensor relationship, signal path, acquisition channel, validity semantics, decision owner and configured evidence. A pressure label, curve or downstream status does not fill the gaps.
Build the fixed measurement-chain briefDo not merge
- Pressure definition and sensor-chain evidence
- Cavity map and installed channel mapping
- Visible curve and valid measurement
- Monitoring output and physical disposition
- Named vendor feature and project support
CAPABILITY BOUNDARY
This is a buyer evidence register, not a sensor, monitoring or control-system offer.
No cavity-pressure sensor, charge amplifier, monitor, data-acquisition package, Kistler/Priamus/RJG compatibility, OPC UA function, automatic good-part decision, quality prediction, closed-loop control, V/P switchover, per-cavity reject sorting, medical validation, zero-defect or scrap-reduction result is attributed to NEW ORIENTAL IMM.
No fixed measurement range, sample rate, threshold, monitoring window, calibration interval, accuracy, sensor position, trigger, sequence, setting, test method or result is supplied. Qualified project parties own every proposed value, method and release.
INTENT OWNERSHIP
Keep the measurement chain separate from eight adjacent decisions.
The same mold, cavity, pressure field or cycle may appear in several records, but each route owns a different procurement and acceptance question.
| Decision owner | Owns | Must stay separate |
|---|---|---|
| Cavity-pressure measurement and monitoring chain | One identified mold, cavity and channel relationship from proposed sensor principle and position through cabling, electronics, acquisition, measurement semantics, configured decision output and as-built evidence. | It does not select a sensor, prescribe a setting or prove part quality, automatic classification, control, reject handling, data integration or production release. |
| Injection, hydraulic and cavity-pressure comparison | Pressure name, physical location, maximum/set/measured status, injection-unit and screw identity, force basis, flow, shot and quotation comparability. | A correctly named cavity-pressure field does not identify a sensor chain, channel map, measurement validity, monitoring rule or accepted output action. |
| Clamp-force input guide | Projected area, approved cavity-pressure basis, pressure distribution, tool loads and project-specific margin for the separate clamp-demand review. | A clamp-force pressure basis does not release a cavity sensor, position, acquisition channel, monitoring window or measurement result. |
| Mold protection and low-pressure close | The configured mold-close travel window, monitoring method, reference or tolerance, response, recipe control and safe acceptance evidence. | Tool protection is not an in-cavity process measurement, part-quality decision, sensor-position rule or production-process control claim. |
| Mold identification and data interface | Mold, article, document and configuration identity; cavity map and active state; runtime data categories, permissions, counters and as-built data records. | A cavity map or pressure-valued data field does not prove the physical measurement chain, calibration evidence, signal validity or quality correlation. |
| IMM-to-MES data contract | The identified IMM/MES endpoints, jobs, cycles, datasets, field semantics, writes, reconciliation and evidence under the selected OPC 40077 release. | MES receipt or storage does not establish sensor placement, measurement validity, a monitoring decision or a physical disposition action. |
| Robot and handling-device interface | Configured machine/robot functions, data, part and reject states, physical integration, separate safety path, fault ownership and acceptance evidence. | A monitoring output does not prove successful gripping, part identity, per-cavity disposition, reject separation or robot compatibility. |
| FAT and SAT acceptance | Approved methods, conditions, instruments, samples, witnesses, observations, deviations, retest and project acceptance authority. | This checklist identifies evidence rows only; it is not a test method, challenge sequence, validation protocol or observed result. |
| Mold change and production startup | Qualified site procedures, recipe release, first-off inspection, deviation handling and authority to enter production after a change. | A released measurement-chain record does not authorize setup, threshold selection, process adjustment, sorting, restart or production. |
SOURCE STATUS / DO NOT TRANSFER
Separate named-vendor examples, interface releases, source drift and configured evidence.
Product pages identify questions; EUROMAP records identify adjacent data boundaries; the ISO record is deliberately excluded from the monitoring claim. Only configured project evidence releases an implementation.
| Layer | Source | Public status | May inform | Cannot release |
|---|---|---|---|---|
| Named first-party measurement examples | Kistler cavity-pressure and injection-molding sensor pages | Current first-party technical pages reviewed 1 August 2026; examples include direct, indirect and contactless sensor relationships | Candidate fields for sensor principle, installation relationship, location, signal chain and responsible selection evidence. | A universal sensor type, position, range, monitoring rule, result, compatibility or NEW ORIENTAL IMM capability. |
| Named first-party chain and output examples | Priamus sensors/electronics and process-monitoring pages | Current first-party product and technical pages reviewed 1 August 2026 | Questions for sensor/electronics identities, data availability and the distinction between display, interface and downstream disposition. | Priamus-specific sensitivity, intelligence, monitoring, control, interface, error-detection or per-cavity handling as a generic or supplier feature. |
| Named first-party output-level example | RJG CoPilot product page | Current first-party product page reviewed 1 August 2026 | A buyer question about whether the proposed output stops at display, alarm, hold, sorting request or control request. | Good/suspect classification, automatic switching, heat/cool control, medical validation, machine compatibility or any NEW ORIENTAL IMM function. |
| Robot data-handoff boundary | EUROMAP 79 dedicated page | Release Candidate 1.00.06, updated March 2024 | The separate downstream robot relationship for part tracking, basic quality data and configured handling states. | A sensor chain, final specification, safety signal, part-quality proof, reject separation or implemented robot interface. |
| EUROMAP overview drift record | EUROMAP OPC UA overview | Still lists EUROMAP 79 Release Candidate 1.00.00 published 8 November 2021; older than the dedicated page | A source-status warning requiring the dedicated page and overview labels to remain visible rather than silently normalized. | A claim that both public records show the same current EUROMAP 79 revision. |
| IMM-to-MES data boundary | EUROMAP 77 / OPC 40077 | Release 1.01 published 1 June 2020 | The separate destination data-contract questions when selected measurement fields are proposed for MES. | A node map, field implementation, write right, monitoring method, data quality or supplier OPC UA support. |
| Common-types boundary | EUROMAP 83 / OPC 40083 / VDMA 40083 | Release 1.03 published 1 June 2021 | The general-type layer beneath specific plastics and rubber machinery companion specifications. | A cavity-pressure monitoring model, endpoint, sensor implementation, interoperability or certification. |
| Adjacent ISO test method — excluded | ISO 294-4:2018 | Published, Edition 3, December 2018; last reviewed and confirmed in 2024; Stage 90.93 | Only that the public ISO record covers determination of molding and post-molding shrinkage of injection-molded thermoplastic test specimens. | A general cavity-pressure monitoring, sensor-selection, calibration, quality-correlation or acceptance standard. |
| Configured project record | Buyer, moldmaker, sensor/monitor parties, machine party and integrator evidence | Project-specific controlled evidence; not supplied by a vendor page or standard title | Actual identities, mapping, declared support, observations, limitations, deviations, output actions and as-built handover. | Any unobserved function, another mold, another cavity, another part or a universal performance or quality result. |
FIXED RFQ REGISTER / 18 FIELDS
Request the same eighteen evidence fields for every proposed measurement chain.
Record unknowns as open items. Do not populate them with a vendor example, a generic curve, a standard title, another mold's settings or an assumed quality decision.
| RFQ field | Record | Evidence to request |
|---|---|---|
| Project and measurement-chain boundary | Buyer decision, included mold/cavities, machine and monitoring scope, supplier and integrator work, site work and explicit exclusions | Approved scope diagram and responsibility matrix with unknown and disputed items retained as open actions |
| IMM/controller, mold, article and configuration identities | Exact machine/controller, mold, article, resin/process context and proposed configuration revisions | Controlled identity register tied to the offered and tested arrangement rather than a generic machine or product family |
| Mold revision, cavity map and active-cavity state | Mold revision, cavity identities and positions, enabled/disabled meanings, article relationship and change authority | Approved cavity map and current configuration record; no active state is inferred from cavity count alone |
| Monitored process or quality question and responsible owner | The exact process observation or quality question, decision purpose, owner, approved evidence basis and declared limitations | Buyer-approved requirement that does not presume a sensor location, correlation, automatic decision or production result |
| Proposed sensor principle, manufacturer and model | Candidate sensing principle and exact supplier/model identity, revision, declared application scope and selection owner | Controlled supplier documentation and project declaration; named vendor examples are not converted into a default choice |
| Direct, indirect or other measurement relationship | Whether the proposed signal is acquired through direct melt contact, an indirect force path or another identified relationship | Configuration drawing and responsible-party explanation retaining the physical measurement location and limitations |
| Cavity position, side and force-transmission geometry | Sensor or transmission location, mold side, cavity feature reference, associated ejector or contact geometry and ownership | Released mold drawing and installed/as-built reference without publishing a universal positioning rule |
| Sensor, cable, connector, junction and channel identities | Exact component and channel identifiers, revisions, physical relationships, replacements and supported/unsupported alternatives | Controlled bill, channel map and connection drawings supplied by responsible project parties |
| Amplifier, monitor, acquisition and software identities | Exact electronics, acquisition hardware, monitoring application and software/firmware revisions with party ownership | Configuration-specific declaration and as-offered baseline; no function is inferred from a product-family name |
| Range, unit, signal, overload and validity semantics | Project-required and proposed measurement range, displayed/recorded unit, signal meaning, overload state, quality/status and invalid-data handling | Controlled field dictionary and supplier evidence with values left open until the project parties approve them |
| Time base, cycle trigger and channel synchronization | Time reference, acquisition/recording basis, cycle association, trigger owner and channel/cavity alignment semantics | Configured timing and correlation record without a universal sample rate, trigger point or synchronization tolerance |
| Sensitivity, calibration, traceability and uncertainty evidence | Sensitivity source, calibration or verification records, traceability statement, uncertainty/limitation and responsible owner | Dated device- and chain-specific records; no calibration interval, method equivalence or accuracy is assumed |
| Reference run, part and correlation-study limitations | Reference mold/process state, selected parts, sample identity, study owner, compared characteristic and documented limitations | Approved project study record that never becomes a universal quality predictor or result for another condition |
| Monitoring characteristic, window and decision-rule ownership | Proposed curve feature or characteristic, reference/window concept, rule owner, approval status, access rights and change triggers | Controlled project declaration with every threshold and setting left for qualified review rather than supplied by this page |
| Configured output and action boundary | Whether the proposal ends at visualization, record, alarm, hold request, sorting request or control request, with denied actions explicit | Responsibility and functional matrix plus configured observation; an electronic request does not prove the physical outcome |
| IMM, robot and MES interface and write authority | Every proposed handoff, endpoint relationship, data direction, read/write/event authority, access boundary and failure owner | Separate interface registers and configured observations without implying OPC UA, robot compatibility or control permission |
| Configured FAT/SAT evidence and deviations | Selected identity, channel, signal-validity, cycle-correlation, output and failure observations; methods, conditions, witnesses, deviations and retest owner | Signed configuration-specific evidence linked to the complete acceptance programme rather than a universal test procedure |
| As-built mapping, retention, change control and revalidation | Final identities, channel/cavity mapping, revisions, supported/unsupported scope, retained data/evidence ownership, open deviations and recheck triggers | Released as-built index and change-control record retaining superseded versions and unresolved actions |
EVIDENCE RELEASE
Advance from identity to as-built evidence without turning the checklist into a monitoring procedure.
The buyer, moldmaker, sensor/monitor parties, machine party, integrator and site define the actual design, values, methods and safe conditions.
Measurement-chain applicability gate
Supplier-declared sensor relationship, components, measurement semantics, limitations, support and exclusions for the proposed configuration.
A named product page, signal or visible curve is not a calibration, accuracy, correlation or compatibility result.Configured decision-output gate
Approved decision purpose, output/action boundary, interface authority and project observations under identified conditions.
Display, alarm or electronic status does not prove part quality, sorting, control action or downstream disposition.As-built and revalidation gate
Final mapping, revisions, evidence retention, deviations, change owners and triggers to repeat the affected review.
Configured evidence applies only to the recorded chain, mold, cavities, process and decision boundary.PRIMARY SOURCES / BOUNDARY
Use named first-party measurement examples and official interface records without transferring capability.
Reviewed 1 August 2026. Kistler, Priamus and RJG remain attributed first-party examples of measurement-chain and output layers. The EUROMAP 79 dedicated page shows RC 1.00.06 while the overview still shows the older RC 1.00.00; EUROMAP 77 is Release 1.01 and EUROMAP 83 is Release 1.03. ISO 294-4:2018 concerns molding shrinkage of test specimens, not process-monitoring acceptance. None proves a NEW ORIENTAL IMM sensor, interface, monitoring, control, classification, compatibility, validation or result.
Cavity pressure
The current first-party technical page defines cavity pressure at the interior of the injection mold and describes pressure curves as inputs to process observation and monitoring.
Boundary: Kistler's good/bad, optimization, sustainability and quality-assurance statements remain attributed Kistler claims. They do not prove a generic method or any NEW ORIENTAL IMM offering or result.
Sensors for monitoring of the injection molding process
The current first-party page distinguishes direct, indirect and contactless cavity-pressure sensor examples and shows that selection and position depend on the mold and intended observation.
Boundary: Its sensor ranges, positioning guidance, switching examples, claimed benefits and quality predictions are vendor-specific and are not copied as specifications, settings or supplier capability.
Sensors & Electronics
The current first-party page shows that a measurement system includes sensors, connections, sensitivity information and downstream electronics rather than an isolated pressure label.
Boundary: Every Priamus component, sensitivity function, installation claim and control statement remains attributed to Priamus and does not transfer to another system or supplier.
Process Monitoring
The current first-party page distinguishes acquisition and visualization from interfaces, error-detection claims and downstream handling actions.
Boundary: Its error recognition, bad-part identification, per-cavity selection, OPC UA/XML and handling claims are named-vendor examples only and do not prove project support or physical disposition.
CoPilot Software
The current first-party product page provides a named example of different output levels, including monitoring, classification, machine connection and control-related product options.
Boundary: All good/suspect sorting, machine connection, heat/cool control, medical validation and regulatory statements remain RJG product claims and are not transferred to NEW ORIENTAL IMM.
EUROMAP 79 — IMM to Robot
The dedicated page identifies Release Candidate 1.00.06 as updated in March 2024 and lists part tracking and basic part-quality data among its data-exchange scope.
Boundary: EUROMAP 79 is a downstream robot data boundary. It does not define the cavity-pressure measurement chain, carry safety signals, prove part quality or establish an implementation.
Overview OPC UA Specifications
The overview identifies EUROMAP 77 Release 1.01, published 1 June 2020, while still listing the older EUROMAP 79 Release Candidate 1.00.00 from 8 November 2021.
Boundary: The older EUROMAP 79 overview entry is retained as source drift, not normalized into the dedicated page's later RC. EUROMAP 77 informs only the separate IMM-to-MES handoff.
EUROMAP 83 — General Types
The official page identifies Release 1.03 dated 1 June 2021 as identical to OPC 40083 Release 1.03 and VDMA 40083:2021-08.
Boundary: General types do not prove a cavity-pressure model, node, endpoint, interface, data quality, interoperability or supplier implementation.
ISO 294-4:2018 — Determination of moulding shrinkage
ISO's current public record identifies a published Edition 3 method, last reviewed and confirmed in 2024 at Stage 90.93, only for determining molding and post-molding shrinkage of injection-molded thermoplastic test specimens.
Boundary: This is not a general cavity-pressure process-monitoring, sensor-selection, calibration, quality-correlation or acceptance standard and is not presented as one.
BUYER QUESTIONS
Injection molding cavity-pressure measurement and process-monitoring FAQ
The answers keep measurement validity, vendor examples, interfaces, quality decisions and supplier capability inside separate evidence boundaries.
01Does a visible cavity-pressure curve prove part quality?+
No. The project still has to identify the mold, cavity, sensor relationship, complete channel, measurement validity, compared part characteristic, study limits and decision owner. A curve or status field alone is not a good-part decision or quality result.
02Which cavity-pressure sensor type and position should the buyer specify?+
This page supplies no default. Kistler's current first-party material shows direct, indirect and contactless examples and says selection and position depend on the mold and intended observation. Responsible project parties must document the proposed relationship and evidence for the actual mold.
03Are any Kistler, Priamus or RJG compatibility claims made for NEW ORIENTAL IMM?+
No. Those named first-party pages help identify measurement-chain and output-layer questions only. Compatibility, components, interfaces, services and supported functions remain open until configuration-specific evidence is received.
04Can an alarm or robot status be treated as proof that a reject was removed?+
No. Keep the monitoring output, robot data contract and physical part disposition separate. EUROMAP 79 provides a Release Candidate data-exchange boundary, not proof of gripping, identity, per-cavity sorting, safety or reject separation.
05Does OPC UA or MES receipt validate the measurement?+
No. EUROMAP 77 and 83 help frame separate data-contract and common-type questions. A received field does not establish sensor position, calibration, signal validity, correlation, write authority or a physical outcome.
06Is ISO 294-4:2018 a cavity-pressure monitoring acceptance standard?+
No. ISO's public abstract says it determines molding and post-molding shrinkage of injection-molded thermoplastic test specimens. It is retained as an explicit adjacent-method exclusion, not used to release this measurement chain.
07What belongs in the cavity-pressure monitoring RFQ?+
Include the project and configuration identities; cavity map; monitored question; sensor relationship and position; complete channel and electronics; measurement and timing semantics; sensitivity/calibration evidence; reference-study limitations; decision and output ownership; interface authority; configured FAT/SAT evidence; and as-built change control.
RFQ / CAVITY-PRESSURE MEASUREMENT CHAIN
Send the identified mold, cavities, channels and evidence requirements.
Attach the project and configuration identities; cavity map; monitored process or quality question; proposed sensor relationship and position; complete channel, electronics and software identities; measurement, timing, sensitivity and calibration evidence; reference-study limitations; decision and output ownership; IMM/robot/MES interface authority; configured FAT/SAT observations; deviations; as-built retention and revalidation triggers. Keep every unconfirmed sensor, compatibility, interface, automatic decision, control, value, method and result open.
Build the machine brief