Kommunikationsgerät | |
Communications Appliance | |
Appareil de communications |
Item | SPF | XML | Change | Description | IFC2x3 to IFC4 4.0.0.0 |
---|---|---|---|---|
IfcCommunicationsAppliance | ADDED | IFC4 Addendum 1 4.0.1.0 | ||
IfcCommunicationsAppliance | ||||
HasCoverings | ADDED | IFC4x2 Candidate 4.2.0.0 | ||
IfcCommunicationsAppliance | ||||
PositionedRelativeTo | ADDED | IFC4x3_RC3 to IFC4x3_RC4 | ||
IfcCommunicationsAppliance | ||||
HasSurfaceFeatures | ADDED |
A communications appliance transmits and receives electronic or digital information as data or sound.
Communication appliances may be fixed in place or may be able to be moved from one space to another. Communication appliances require an electrical supply that may be supplied either by an electrical circuit or provided from a local battery source.
HISTORY New entity in IFC4
# | Attribute | Type | Cardinality | Description | G |
---|---|---|---|---|---|
9 | PredefinedType | IfcCommunicationsApplianceTypeEnum | ? | X |
Rule | Description |
---|---|
CorrectPredefinedType | Either the PredefinedType attribute is unset (e.g. because an IfcCommunicationsApplianceType is associated), or the inherited attribute ObjectType shall be provided, if the PredefinedType is set to USERDEFINED. |
CorrectTypeAssigned | Either there is no communications appliance type object associated, i.e. the IsTypedBy inverse relationship is not provided, or the associated type object has to be of type IfcCommunicationsApplianceType. |
# | Attribute | Type | Cardinality | Description | G |
---|---|---|---|---|---|
IfcRoot | |||||
1 | GlobalId | IfcGloballyUniqueId | Assignment of a globally unique identifier within the entire software world. | X | |
2 | OwnerHistory | IfcOwnerHistory | ? |
Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,
NOTE only the last modification in stored - either as addition, deletion or modification. IFC4 CHANGE The attribute has been changed to be OPTIONAL. | X |
3 | Name | IfcLabel | ? | Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule. | X |
4 | Description | IfcText | ? | Optional description, provided for exchanging informative comments. | X |
IfcObjectDefinition | |||||
HasAssignments | IfcRelAssigns @RelatedObjects | S[0:?] | Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups. | X | |
Nests | IfcRelNests @RelatedObjects | S[0:1] | References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only).
IFC4 CHANGE The inverse attribute datatype has been added and separated from Decomposes defined at IfcObjectDefinition. | X | |
IsNestedBy | IfcRelNests @RelatingObject | S[0:?] | References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types).
IFC4 CHANGE The inverse attribute datatype has been added and separated from IsDecomposedBy defined at IfcObjectDefinition. | X | |
HasContext | IfcRelDeclares @RelatedDefinitions | S[0:1] | References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object.
IFC4 CHANGE The inverse attribute datatype has been added. | X | |
IsDecomposedBy | IfcRelAggregates @RelatingObject | S[0:?] | References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts).
IFC4 CHANGE The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates. | X | |
Decomposes | IfcRelAggregates @RelatedObjects | S[0:1] | References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only).
IFC4 CHANGE The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates. | X | |
HasAssociations | IfcRelAssociates @RelatedObjects | S[0:?] | Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification. | X | |
IfcObject | |||||
5 | ObjectType | IfcLabel | ? | The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute PredefinedType is set to USERDEFINED. | X |
IsDeclaredBy | IfcRelDefinesByObject @RelatedObjects | S[0:1] | Link to the relationship object pointing to the declaring object that provides the object definitions for this object occurrence. The declaring object has to be part of an object type decomposition. The associated IfcObject, or its subtypes, contains the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.
IFC4 CHANGE New inverse relationship, change made with upward compatibility for file based exchange. | X | |
Declares | IfcRelDefinesByObject @RelatingObject | S[0:?] | Link to the relationship object pointing to the reflected object(s) that receives the object definitions. The reflected object has to be part of an object occurrence decomposition. The associated IfcObject, or its subtypes, provides the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.
IFC4 CHANGE New inverse relationship, change made with upward compatibility for file based exchange. | X | |
IsTypedBy | IfcRelDefinesByType @RelatedObjects | S[0:1] | Set of relationships to the object type that provides the type definitions for this object occurrence. The then associated IfcTypeObject, or its subtypes, contains the specific information (or type, or style), that is common to all instances of IfcObject, or its subtypes, referring to the same type.
IFC4 CHANGE New inverse relationship, the link to IfcRelDefinesByType had previously be included in the inverse relationship IfcRelDefines. Change made with upward compatibility for file based exchange. | X | |
IsDefinedBy | IfcRelDefinesByProperties @RelatedObjects | S[0:?] | Set of relationships to property set definitions attached to this object. Those statically or dynamically defined properties contain alphanumeric information content that further defines the object.
IFC4 CHANGE The data type has been changed from IfcRelDefines to IfcRelDefinesByProperties with upward compatibility for file based exchange. | X | |
IfcProduct | |||||
6 | ObjectPlacement | IfcObjectPlacement | ? | Placement of the product in space, the placement can either be absolute (relative to the world coordinate system), relative (relative to the object placement of another product), or constraint (e.g. relative to grid axes). It is determined by the various subtypes of IfcObjectPlacement, which includes the axis placement information to determine the transformation for the object coordinate system. | X |
7 | Representation | IfcProductRepresentation | ? | Reference to the representations of the product, being either a representation (IfcProductRepresentation) or as a special case a shape representations (IfcProductDefinitionShape). The product definition shape provides for multiple geometric representations of the shape property of the object within the same object coordinate system, defined by the object placement. | X |
ReferencedBy | IfcRelAssignsToProduct @RelatingProduct | S[0:?] | Reference to the IfcRelAssignsToProduct relationship, by which other products, processes, controls, resources or actors (as subtypes of IfcObjectDefinition) can be related to this product. | X | |
PositionedRelativeTo | IfcRelPositions @RelatedProducts | S[0:?] | X | ||
ReferencedInStructures | IfcRelReferencedInSpatialStructure @RelatedElements | S[0:?] | X | ||
IfcElement | |||||
8 | Tag | IfcIdentifier | ? | The tag (or label) identifier at the particular instance of a product, e.g. the serial number, or the position number. It is the identifier at the occurrence level. | X |
FillsVoids | IfcRelFillsElement @RelatedBuildingElement | S[0:1] | Reference to the IfcRelFillsElement Relationship that puts the element as a filling into the opening created within another element. | X | |
ConnectedTo | IfcRelConnectsElements @RelatingElement | S[0:?] | Reference to the element connection relationship. The relationship then refers to the other element to which this element is connected to. | X | |
IsInterferedByElements | IfcRelInterferesElements @RelatedElement | S[0:?] | Reference to the interference relationship to indicate the element that is interfered. The relationship, if provided, indicates that this element has an interference with one or many other elements.
NOTE There is no indication of precedence between IsInterferedByElements and InterferesElements. IFC4 CHANGE New inverse relationship. | X | |
InterferesElements | IfcRelInterferesElements @RelatingElement | S[0:?] | Reference to the interference relationship to indicate the element that interferes. The relationship, if provided, indicates that this element has an interference with one or many other elements.
NOTE There is no indication of precedence between IsInterferedByElements and InterferesElements. IFC4 CHANGE New inverse relationship. | X | |
HasProjections | IfcRelProjectsElement @RelatingElement | S[0:?] | Projection relationship that adds a feature (using a Boolean union) to the IfcBuildingElement. | X | |
HasOpenings | IfcRelVoidsElement @RelatingBuildingElement | S[0:?] | Reference to the IfcRelVoidsElement relationship that creates an opening in an element. An element can incorporate zero-to-many openings. For each opening, that voids the element, a new relationship IfcRelVoidsElement is generated. | X | |
IsConnectionRealization | IfcRelConnectsWithRealizingElements @RealizingElements | S[0:?] | Reference to the connection relationship with realizing element. The relationship, if provided, assigns this element as the realizing element to the connection, which provides the physical manifestation of the connection relationship. | X | |
ProvidesBoundaries | IfcRelSpaceBoundary @RelatedBuildingElement | S[0:?] | Reference to space boundaries by virtue of the objectified relationship IfcRelSpaceBoundary. It defines the concept of an element bounding spaces. | X | |
ConnectedFrom | IfcRelConnectsElements @RelatedElement | S[0:?] | Reference to the element connection relationship. The relationship then refers to the other element that is connected to this element. | X | |
ContainedInStructure | IfcRelContainedInSpatialStructure @RelatedElements | S[0:1] | Containment relationship to the spatial structure element, to which the element is primarily associated. This containment relationship has to be hierachical, i.e. an element may only be assigned directly to zero or one spatial structure. | X | |
HasCoverings | IfcRelCoversBldgElements @RelatingBuildingElement | S[0:?] | Reference to IfcCovering by virtue of the objectified relationship IfcRelCoversBldgElement. It defines the concept of an element having coverings associated. | X | |
HasSurfaceFeatures | IfcRelAdheresToElement @RelatingElement | S[0:?] | Reference to the IfcRelAdheresToElement relationship that adheres a IfcSurfaceFeature to an element. An element can incorporate zero-to-many surface features in one relationship. | X | |
IfcDistributionElement | |||||
HasPorts | IfcRelConnectsPortToElement @RelatedElement | S[0:?] | Reference to the element to port connection relationship. The relationship then refers to the port which is contained in this element.
IFC4 CHANGE The inverse attribute is deprecated. Relationship to ports, contained within the IfcDistributionElement is now realized by the inverse relationship NestedBy referencing IfcRelNests. | X | |
IfcDistributionFlowElement | |||||
HasControlElements | IfcRelFlowControlElements @RelatingFlowElement | S[0:1] | Reference to the relationship object that relates control elements. | X | |
IfcFlowTerminal | |||||
IfcCommunicationsAppliance | |||||
9 | PredefinedType | IfcCommunicationsApplianceTypeEnum | ? | X |
Object Typing
The Object Typing concept template applies to this entity as shown in Table 419.
| ||||
Table 419 — IfcCommunicationsAppliance Object Typing |
Property Sets for Objects
The Property Sets for Objects concept template applies to this entity as shown in Table 420.
| ||||||||||||||||
Table 420 — IfcCommunicationsAppliance Property Sets for Objects |
Quantity Sets
The Quantity Sets concept template applies to this entity as shown in Table 421.
| ||||
Table 421 — IfcCommunicationsAppliance Quantity Sets |
Material
The Material Constituent Set concept template applies to this entity as shown in Table 422.
| ||
Table 422 — IfcCommunicationsAppliance Material Constituent Set |
Composition
The Aggregation concept template applies to this entity as shown in Table 423.
Table 423 — IfcCommunicationsAppliance Aggregation |
Port
The Port Nesting concept template applies to this entity as shown in Table 424.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Table 424 — IfcCommunicationsAppliance Port Nesting |
<?xml version="1.0" encoding="utf-8"?>
<ConceptRoot xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" uuid="1f07c996-ef97-4370-af35-6472a6f286c6" name="IfcCommunicationsAppliance" applicableRootEntity="IfcCommunicationsAppliance">
<Applicability>
<Template ref="4ad6d03f-c18c-46ee-b181-33528263892b" />
<TemplateRules operator="and">
</TemplateRules>
</Applicability>
<Concepts>
<Concept uuid="d7c86ab9-7807-4542-aa9c-e14124616095" name="Object Typing">
<Template ref="35a2e10e-20df-40f4-ab2f-dacf0a6744f4" />
<TemplateRules operator="and">
<TemplateRule Parameters="RelatingType[Type]='IfcCommunicationsApplianceType'" />
</TemplateRules>
</Concept>
<Concept uuid="5153da9d-adb8-42d4-8bb0-d4bf8ff803a3" name="Property Sets for Objects">
<Template ref="f74255a6-0c0e-4f31-84ad-24981db62461" />
<TemplateRules operator="and">
<TemplateRule Parameters="PsetName[Value]='Pset_CommunicationsApplianceTypeCommon'" />
</TemplateRules>
</Concept>
<Concept uuid="6ff336dc-e433-4be4-9dfd-8ee28e0f7142" name="Quantity Sets">
<Template ref="6652398e-6579-4460-8cb4-26295acfacc7" />
<TemplateRules operator="and">
<TemplateRule Parameters="QsetName[Value]='Qto_CommunicationsApplianceBaseQuantities'" />
</TemplateRules>
</Concept>
<Concept uuid="fcb98d2a-cd0b-453a-a93c-e17c349d94b8" name="Material">
<Template ref="d96f7f7d-e742-4db8-9b5d-18a36a6df884" />
<TemplateRules operator="and">
<TemplateRule Description="Material from which the casing is constructed." />
</TemplateRules>
</Concept>
<Concept uuid="84c445ca-c976-499d-baa0-5a26f1283e50" name="Composition">
<Template ref="02eefcc6-b26c-4f20-9c7c-c30ae74eb9a9" />
<TemplateRules operator="and">
<TemplateRule Description="Computers may be aggregated into audio-visual components such as displays, cameras, speakers, or microphones." />
</TemplateRules>
</Concept>
<Concept uuid="31a71e63-9870-401c-b851-aae248b1b357" name="Port">
<Template ref="bafc93b7-d0e2-42d8-84cf-5da20ee1480a" />
<TemplateRules operator="and">
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='ANTENNA' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="Electromagnetic waves." Parameters="PredefinedType[Value]='ANTENNA' AND PortName[Value]='Radio' AND SystemType[Value]='SIGNAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="The modulated analog signal in a circuit, such as a cable connected to a modem." Parameters="PredefinedType[Value]='ANTENNA' AND PortName[Value]='Signal' AND SystemType[Value]='SIGNAL' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='COMPUTER' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="A network connection, may be wired or wireless (implicit antenna), such as a cable connected from a data outlet jack or from a router communications appliance. While communication is bidirectional, the router-end is considered to be the source." Parameters="PredefinedType[Value]='COMPUTER' AND PortName[Value]='Network' AND SystemType[Value]='DATA' AND Flow[Value]='SINK'" />
<TemplateRule Description="A device connection such as USB or serial, which may connect to equipment such as a building automation controller." Parameters="PredefinedType[Value]='COMPUTER' AND PortName[Value]='Device' AND SystemType[Value]='CONTROL' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Audio/video output, such as a cable connected to a display, which may be aggregated into separate channels." Parameters="PredefinedType[Value]='COMPUTER' AND PortName[Value]='Display' AND SystemType[Value]='AUDIOVISUAL' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='FAX' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="Telephone connection." Parameters="PredefinedType[Value]='FAX' AND PortName[Value]='Phone' AND SystemType[Value]='TELEPHONE' AND Flow[Value]='SINK'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='MODEM' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="Modulated analog signal, typically a cable connecting from a communications junction box or an antenna." Parameters="PredefinedType[Value]='MODEM' AND PortName[Value]='Signal' AND SystemType[Value]='SIGNAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="Internet data network." Parameters="PredefinedType[Value]='MODEM' AND PortName[Value]='Internet' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Television modulated signal." Parameters="PredefinedType[Value]='MODEM' AND PortName[Value]='Television' AND SystemType[Value]='TV' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Telephone communications." Parameters="PredefinedType[Value]='MODEM' AND PortName[Value]='Telephone' AND SystemType[Value]='TELEPHONE' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='PRINTER' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="A network connection, may be wired or wireless." Parameters="PredefinedType[Value]='PRINTER' AND PortName[Value]='Network' AND SystemType[Value]='DATA' AND Flow[Value]='SINK'" />
<TemplateRule Description="Telephone connection for fax support." Parameters="PredefinedType[Value]='PRINTER' AND PortName[Value]='Phone' AND SystemType[Value]='TELEPHONE' AND Flow[Value]='SINK'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='REPEATER' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="The receiving signal." Parameters="PredefinedType[Value]='REPEATER' AND PortName[Value]='Input' AND SystemType[Value]='SIGNAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="The transmitted amplified signal." Parameters="PredefinedType[Value]='REPEATER' AND PortName[Value]='Output' AND SystemType[Value]='SIGNAL' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="Receives electrical power." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Power' AND SystemType[Value]='ELECTRICAL' AND Flow[Value]='SINK'" />
<TemplateRule Description="Uplink from another network, such as a cable connected to another router or modem accessing the Internet." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Uplink' AND SystemType[Value]='DATA' AND Flow[Value]='SINK'" />
<TemplateRule Description="A wireless access point." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='WiFi' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#1' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#2' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#3' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#4' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#5' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#6' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#7' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
<TemplateRule Description="A network link to a routed device such as a cable connecting to a computer." Parameters="PredefinedType[Value]='ROUTER' AND PortName[Value]='Link#8' AND SystemType[Value]='DATA' AND Flow[Value]='SOURCE'" />
</TemplateRules>
</Concept>
</Concepts>
</ConceptRoot>
<xs:element name="IfcCommunicationsAppliance" type="ifc:IfcCommunicationsAppliance" substitutionGroup="ifc:IfcFlowTerminal" nillable="true"/>
<xs:complexType name="IfcCommunicationsAppliance">
<xs:complexContent>
<xs:extension base="ifc:IfcFlowTerminal">
<xs:attribute name="PredefinedType" type="ifc:IfcCommunicationsApplianceTypeEnum" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
ENTITY IfcCommunicationsAppliance
SUBTYPE OF (IfcFlowTerminal);
PredefinedType : OPTIONAL IfcCommunicationsApplianceTypeEnum;
WHERE
CorrectPredefinedType : NOT(EXISTS(PredefinedType)) OR
(PredefinedType <> IfcCommunicationsApplianceTypeEnum.USERDEFINED) OR
((PredefinedType = IfcCommunicationsApplianceTypeEnum.USERDEFINED) AND EXISTS (SELF\IfcObject.ObjectType));
CorrectTypeAssigned : (SIZEOF(IsTypedBy) = 0) OR
('IFCELECTRICALDOMAIN.IfcCommunicationsApplianceType' IN TYPEOF(SELF\IfcObject.IsTypedBy[1].RelatingType));
END_ENTITY;