Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:35:10 UTC

SIE.3:5 - Archetypal Grounding

SIE.3:5.1 - Reuse for Provider Availability

The receiving interface returns separately attributed provider quantities. Its questions are “How much is on hand now?” and “How much can this provider promise under its reservation and time-horizon rules?”

An available model already distinguishes both measures, their provider, unit, observation time, and relevant horizon. The integrator checks the following cases:

CaseRequired model interpretation
Provider A reports 12 on hand; provider B reports 9 available to promise.Two qualified quantities with distinct measure meanings.
Both values happen to equal 12.Numerical equality does not remove the difference between the measures.
The provider changes the promise horizon.The horizon remains part of the promise meaning used by the receiver.

The model represents these cases and has suitable access and maintenance conditions. The completed result references that edition for the two questions. It supplies no common quantity formed by adding the values; that operation would require a separately justified receiving meaning.

SIE.3:5.2 - Extend an Inspection Model

A constructed product-definition and inspection integration asks: “What observation concerns requirement Q for feature F in configuration R?” The source model already describes the feature and its requirement, but represents no actual observation.

Model contentDevelopment and case
Existing feature and requirementReuse their qualified definitions and configuration applicability.
ObservationAdd the actual observation as distinct from its plan and the requirement being checked.
Observation relationState which configured feature and applicable requirement it concerns.
Unit and timeExpress the interpretation required for this observation and question.
CounterexamplesA planned inspection is not an observation; an observation of another configuration does not answer this question.

The domain participants confirm those distinctions and identify any unresolved source-specific interpretation. The module can then supply SIE.4 and SIE.7 with the required meanings. In an AP242/QIF installation, its actual profiles, configuration relations, and inspection meanings must come from the qualified source results; the constructed model above is the working example, not a claim about a particular exchange’s conformance.