<p>Extensions and Modifications of Proteus Schema for IIMM Instrumentation Model</p><p>0.1 2015-10-27 Manfred Theißen, AixCAPE initial version</p><p>This document describes a proposal for extending Proteus schema in order to support the new IIMM instrumentation model.</p><p>New Element: <ProcessControlLoop>  top-level element in <PlantModel>  <ProcessControlRequirements> in the <ProcesControlLoop> are assigned via <Association> elements (cf. InstrumentLoop in Proteus 3.6.0) </p><p>Example:</p><p><ProcessControlLoop ID = "PCL1314" TagName = "1314"> <Association Type = "is a collection including" ItemID = "PCR_1314L"/> <Association Type = "is a collection including" ItemID = "PCR_P1314C"/> </ProcessControlLoop></p><p>New Element: <ProcessControlRequirement>  top-level element in <PlantModel>, even if part of a <ProcessControlLoop></p><p> <ProcessControlRequirements> are optionally assigned to a <ProcesControlLoop> via an <Association> elements (cf. InstrumentLoop in Proteus 3.6.0; redundancy accepted for now for consistency with Proteus 3.6.0)</p><p> ProcessControlFunction:</p><p> o subclass of ProcessControlRequirement</p><p> o no schema class required (RDL reference sufficient)</p><p>Example:</p><p><ProcessControlRequirement ID = "PCR_1314L" TagName = "P1314L"> <!--TODO: Graphics: bubble with inner deco --> <!--TODO: Ports: probably need classifications --> <Association Type = "is part of" ItemID = "PCL1314"/> ... </ProcessControlRequirement></p><p>New Elements: <ActingProcessControlRequirement>, <SensingProcessControlRequirement>  children of < ProcessControlRequirement></p><p> <ActingAssembly>/<SensingAssembly> are assigned via <Association> (Multiplicity <SensingAssembly>-<SensingProcessControlRequirement> is 1..*. Hence, assigning <SensingAssembly> as XML children will not work in general.)</p><p>Existing Element: <SignalLine>  As many objects in the conceptual model are not necessarily represented in a PID graphics, there is a mismatch between the associations of <SignalLine> as indicated in the conceptual model and the shapes that are connected by the drawing of a <SignalLine>. </p><p> Use <SignalLine> (incl. <Connection>) as described in Proteus 3.6.0</p><p> In addition: give conceptual associations.  Existing association types are not well documented, but probably none fits.Thus added:</p><p> o “has logical start”/”is logical start of”</p><p> o “has logical end”/”is logical end of”</p><p> Direction of <SignalLine> should match information flow where applicable.</p><p>Example:</p><p><SignalLine ID = "SL_P1314C_1"> <Association Type = "has logical start" ItemID = "PCR_P1314C"/> <Association Type = "has logical end" ItemID = "PCF_U1313"/> ...</p><p>New Elements: <ActingAssembly>, <SensingAssembly>  Top-level elements in <PlantModel></p><p> Assignment to <ActingProcessControlRequirement>/<SensingProcessControlRequirement> via <Association> with type “fulfills”/”is fulfilled by”</p><p> Assignment of parts via <Association> with type “is an assembly including” (optionally with RDF reference, e.g., to identify the “DetectingElement” or the “Transmitter” independent from the type of the referenced object)</p><p><SensingAssembly ID = "SA_PT1314C " TagName = "PT1314C"> <Association Type = "fulfills" ItemID = "SPCR_PT1314C"/> <Association Type = "is an assembly including" ItemID = "SPCR_PT1314C"/> </SensingAssembly></p><p>Graphics  In principle, graphical representations for all objects above are optional; thus, PlantItem is an adequate XSD type for all of them</p><p> Details of graphics depend on the underlying standard; they should be covered by the existing schema elements</p>