Library.Reference:6.2 - Interpret levels, layers and scales through their relations
A level is relative to an identified relation and subject. Nested system constituents can support system-composition levels; constituent Methods can support Method-composition levels. Classification, refinement, abstraction, authority and time answer other questions even when a source also calls their positions levels. The depth of a composition depends on the selected whole. A taxonomic child is a narrower kind, whereas a constituent supplies a contribution to a whole.
An account of functional layers groups contributions by what they do and explains how their results connect. Planning and tracking can be functional layers in a control design. Delivery, support and development can be functional groupings in an operating arrangement. Several modules or people can contribute to one layer, and one module or person can contribute to several layers. Use a layered account when this grouping helps explain the required result; it does not require a matching organization of physical components or teams.
This gives a qualified answer to “are management levels functional layers?” A source can be grouping functions, composing organizational units, allocating decision rights or comparing horizons. Delivery, support and development performed by one team can be described functionally. If that team is a constituent of a firm under the applicable system-composition conditions, its system relation remains available as well. A manager’s authority and planning horizon require their own account. The word management chooses none of these relations in advance.
“Method level” similarly needs its local meaning. It can concern a constituent Method, a narrower family, a model’s abstraction level or the order in which an explanation introduces topics. Models of one Method can occupy different abstraction levels under the B.5.MR comparison below. For a relation between Methods, first establish their identities; FPF A.3.1:4.8 then asks which semantics are retained, what is narrowed or strengthened and what action or result changes. More detailed description alone does not settle this comparison. Teaching one topic before another can make an explanation usable without making the earlier topic a constituent or execution stage of every later Method.
Use a qualified expression where it affects what the reader can infer or do.
| Meaning needed here | Wording for the reader |
|---|---|
| Position under the stated system composition | system-composition level; system level when clear |
| Position in an admitted Method composition | Method-composition level |
| Contributions grouped by function and their connections | functional layer |
| Modules organized through their interfaces | modular level; module/interface level |
| Relative position established by comparing the answers admitted by models | level of model abstraction |
| Detail shown or omitted in a representation | level of detail |
| Position among narrower or broader kinds | taxonomic level; specialization |
| The temporal quantity being compared | timescale; update period; planning horizon |
| Who may change an identified choice or commitment | decision authority |
Keep a source’s well-defined term. For example, the ISA-95 account in OPC 10030 §4.2.3 uses activity levels. Recover that activity relation rather than automatically replacing levels with layers. FPF C.30.STRAT:4.2 gives the local functional-layer/modular-level distinction and the other meanings to recover. A spatial or temporal “scale” does not automatically identify a Scale in a measurement model. State the quantity, unit and comparison required by the present measurement claim.
One Russian word, «управление», can become speed control in a drive specification, team management in a staffing plan, or governance in a charter that allocates decision rights. Identify the operation or authority in the passage before choosing the English term; FPF E.10:9.8 and C.43 retain their different uses. When translating into another natural language, carry the subject, relation, conditions and example first, then choose the locally useful expression. Keep a qualified phrase or explained source term if one target word would merge action-changing meanings. Revisit a translation when it changes which contribution is selected, composed, authorized or revised.
Model refinement and model abstraction compare models answering the same inquiry. First recover what each asserts: for example, which system constructions or Method performances it admits. Establish how an answer expressed in one model is interpreted in the other. Under that interpretation, a refinement admits at least one answer and every answer it admits satisfies the earlier model’s assertions. Read the relation in the reverse direction for abstraction. These tests permit equivalent models. Call one model more concrete and the other more abstract only when an answer admitted by the latter is excluded by the former. B.5.MR, Compare Models by Refinement and Abstraction gives the construction and comparison.
To refine a model, establish a determination that it leaves open, obtain the grounds for fixing it and check feasibility and preservation of the earlier assertions. To construct an abstraction, identify the conclusion needed for the receiving work and select determinations that can be left open. Check that the original model has an admitted answer and that each of its answers satisfies the resulting model under the chosen interpretation. Then check the needed conclusion over all answers admitted by the abstraction. Identify a lost conclusion and its missing premise when there is one; no conclusion need be lost for the inquiry. Removing a local restriction does not establish that the rule works in new disciplines: that applicability needs their subject grounds.
Levels of model abstraction are relative positions in such a comparison. In the L0–L4 convention, L0 fixes an individual entity or occurrence, L1 retains local recurring conditions, L2 retains disciplinary rules, L3 retains transdisciplinary principles under their warranted interpretations, and L4 retains foundational formal or computational constructions. Unknown properties of an identified individual can remain open. Moving from L0 towards L4 is abstraction, and the reverse direction is refinement, when the compared models establish the corresponding relation. Intermediate positions can be useful; adopting a rule unchanged can leave models equivalent. A position name or a different language does not prove a strict step.
Core, DPFs and LPFs supply models that can participate in these comparisons; the publications themselves do not occupy fixed ranks. A DPF can supply a disciplinary model used to develop a local model, and a local observation can expose a defect in that disciplinary model. Establish the actual assertions and relation at each transition.
For a model to conform to a metamodel, it must satisfy that metamodel’s conventions. When a decision or handover depends on several models, use C.37.MM to recover their governing conventions and test the conclusion they support together. To decide which expressions a language admits, how they can be read or which entity a designation picks out, use E.5.2.L. The same language can express different commitments. A.2 governs a separate question about the system assigned a role.
For a connected account of epistemes, descriptions, models, views, expressions, notation and publication, read C.2.1:4.0. It explains when these names concern the same individual and which additional relations a use needs. Its :4.0.13 helps choose what to establish when the task concerns changed claims, interpretation, viewpoint conformance or publication availability.
Library.Reference:6.2.1 - Reason about the types used to model a domain
Take the subject of the present inquiry as your point of reference. Name it and what you need to establish, explain or do. If a decision depends on the answer, identify that decision. “The rules for issuing a release in this laboratory” is more informative than “one level up.” To move, name the next subject and the relation you intend to follow. A record may direct you to the rule used to produce it, to the work it represents or to the episteme that states the rule. Check the issuing practice, the interpretation of the record or the content of that episteme, respectively. These transitions license different inferences. Stop when the result answers the inquiry or supports the intended action. When you change the question, identify the new point of reference.
A model can describe the work done on a particular occasion. A different inquiry asks what a discipline counts as work, which types it uses to represent it and what follows from those choices. Here the domain’s own types and relations become the objects of reasoning. This is metamodeling. Identify what is being modeled and what the practitioner needs to do with it.
Keep the words appropriate to the job. The design office may need a rule about a type of joint. The workshop may need the identifier of one defective unit. With the same product and people, an editor can ask whether a passage still teaches a repeatable check or merely records one use. Add the one distinction that changes the recipient’s decision. F.19:4.3.1, keeping what a passage claims and teaches.
An abstract model can be expressed clearly, while a passage about one individual can leave its assertion unrecoverable. To examine a complaint that wording is too abstract, first establish the intended use from the request and the material available to the recipient. An unresolved purpose prevents a sufficiency judgement for that purpose; it does not by itself make a clear assertion unintelligible. Keep a passage’s local function distinct from the larger explanation requested.
Then recover the assertion or operation the recipient needs. A precise term helps when its definition and use are available; an unexplained label can fail as readily as an ordinary umbrella word. Keep ordinary wording when the connected explanation supplies its meaning. If supported clarification reveals the same model assertions, the model has not thereby become more concrete. If an assertion, premise, derivation or way of performing the instruction is missing, obtain that content through the subject Method. Explanation Design, Reference:3 follows the whole explanatory attempt and returns supported content and its limits. F.19:4.3 carries it into the wording and repeats local recovery. Use B.5.MR when the repair changes a model’s assertions and the refinement or abstraction relation matters. The text’s production history need not be known to find the missing content.
Use the discipline as the point of reference when the question concerns how a field works. C.20 identifies the discipline as a whole of knowledge and reproducible practice. An episteme can state its rules or model a situation. Identify the subject of the claim and what establishes the claim. A rule may be stated directly in an authoritative policy or expressed in a model. Use the source needed for the question at hand. A reusable ontic can settle identity or relations needed by several uses. For a local application, often the existing field rule and a particular model provide enough. FPF C.20:4.1 · FPF E.24.PUB:4
A project provides a local setting for applying or adapting types. Name the work or plan, the object being considered and why it matters to the inquiry or action. In systems engineering, the system-of-interest is the product whose intended use gives the cooperation of creators its purpose. The cooperation can take the form of an extended enterprise. The system-in-hand is the system being investigated or changed for the immediate work. The same system can qualify in both respects. A temporary project can help realize a product while working on another system such as a test facility. Its current subject can also be a Method or an episteme. FPF A.1.STM:4.1 · FPF A.15.6:4.1a
A testing discipline can teach a metamodel of the types used in testing. A particular project can adopt or adapt those types for its own tools, work and records. The project may select one of several disciplinary practices, narrow the conditions, or use another name for the same role. To identify the metamodel, name the types or modeling rules being modeled. The same disciplinary type can appear in several project models, and different metamodels can serve different questions about it.
| Scope of the account | Distinction used to reason | What to do with it |
|---|---|---|
| Transdisciplinary reasoning about the types and methods used in a field | A Method is a reusable way of doing something. Work is a particular performance. A description can represent either. | Identify which claim matters to the receiving work. Recover the method and its conditions for a claim about how to obtain a result. For a claim about performance, establish which work took place and on what object. |
| A discipline’s domain metamodel | A testing discipline distinguishes a test procedure, a test run and a verdict on the item tested. | Specify what must be observed, under which test conditions, and how those observations warrant a verdict. |
| The local practice and metamodel of a named project or organization | A project may use “inspection” for both the procedure and a signed record. Its types and rules can be recovered from the local practice and the data schema. | Establish how a record identifies a run, who may issue the verdict and whether the schema preserves the distinction the decision requires. |
| A particular situation (model of the case) | A record describes a run on an identified item under stated conditions. | Decide what that run establishes about that item. If the record refers to a different configuration, check which grounds carry over before applying the verdict. |
Choose the relation that supports the inference. Classifying a domain type requires grounds for applying the higher-order distinction to that type. To establish that one type specializes another, show that meeting the narrower criterion also meets the broader one within scope. This can follow from the definitions. In a deliberately closed finite domain, checking every candidate can establish the inclusion for that domain. To infer something about a subject from its model, establish what the representation preserves. An existing kind criterion can be used at either scope. An ontic can coordinate the identity and direct relation rules that several uses need together. These distinctions allow a transdisciplinary method to be performed on a particular case. FPF C.3.1:4 · FPF C.39.WA:4.3 · FPF E.24:4
When the result you need is a new or revised method, the whole job is methodological synthesis. Use existing concepts where they suffice. If sources use a consequential term differently, establish what each usage supports. Preserve a warranted difference or identify the claim that still lacks evidence. For a method of checking proofs, distinguish the argument from the record of a checker run. Establish which version the record covers, follow the inference from the premises under the stated calculus and verify that it reaches the claimed conclusion. If the version or extent of checking is unknown, obtain a result tied to that argument or check it directly before relying on the verdict. The same service may also need a conceptual synthesis of what “checked” means in both systems for subsequent audits. A supported account of their agreement or difference can settle that inquiry. FPF F.0.2:4.6 · FPF C.39
Use general distinctions in local speech. A heading, a form or a checklist can carry a domain type without displaying its transdisciplinary name. Check what the field accepts, which relation the entry asserts and what action that licenses. An empty field can mean “unknown,” “not applicable,” or “no observation required”; establish which meaning the local rule gives it before acting on it. Explain the distinction explicitly when teaching it or repairing a disagreement. A practitioner may work it out on paper, in conversation or with a software agent. The recipient needs a usable instruction or conclusion in the vocabulary of the receiving work.
For instance, a maintenance form has a box labeled “ready.” The team enters the date a unit was adjusted. The release authority needs a verdict on operation within tolerance. The date can document an intervention. To decide on release, identify the unit after adjustment, obtain the required measurements and apply the applicable acceptance rule. If a separate authorized test has already done this, retrieve its verdict. A revised form may point to that verdict. Changing the heading cannot supply the measurement or the authority. One agent can design the form, another carry out the test and a third use the result.
To practise constructing or challenging a mapping, use an unfamiliar case and identify the judgement the learner must contribute. A supplied problem statement can support an exercise in checking its grounds or selecting a method. An exercise in framing the problem must leave that choice open. Inspect the brief, working record and available help to establish what the learner supplied. A record of an earlier attempt can show that choice. For the design of the exercise see E.8:4.2.1.3. For the different question of acquiring a capability through inquiry, a demonstration, a description or supported practice see E.23.CDI:4.2.1.
Ask for a usable conclusion in local terms and the grounds for it. Change one local condition and observe which inference the learner retains, revises or leaves open. For an individual, establish who made the consequential choice. For a human–AI team, examine the division of work. For a software agent, identify its configuration and tools. Performance on this task provides evidence about the action observed. Claims about learning or durable transfer need evidence appropriate to the holder.