Incorporates all IDM components that are about the development, design and installation of electrical power and lighting systems.

Transcription

1 Electrical Engineering - Confluence 1 af :08 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jul 23, 2007 (view change) Labels: (None) Incorporates all IDM components that are about the development, design and installation of electrical power and lighting systems. Process Maps Electrical Engineering (PM) Exchange Requirements Exchange Electrical Model - Equipment (ER) Exchange Electrical Model - Space (ER) Exchange Electrical Model - Systems (ER)

2 Electrical Engineering - Confluence 2 af :08 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

3 Electrical Engineering (PM) - Confluence Information Delivery Manual (IDM) Electrical Engineering (PM) Added by kes, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: pm, er-exchange-hvac-model-equipment Electrical Engineering A - Process Maps (PM) Electrical engineering deals with the overall process of planning, designing, installing, commissioning, operating and maintaining electrical power systems for building projects. It deals with low voltage electrical installations from 12V (AC/DC) to 1000V (AC) or 1500 volts (DC) in accordance with IEC definitions. Electrical installations within scope of this process are considered to commence at a meter where the public utility supply terminates or at a transformer where voltage is stepped down to the low voltage range in scope. Incoming electrical supplies and distribution of electrical energy at higher voltages are considered to be out of scope of this process. The Electrical Engineering process is concerned with the distribution of power from an initial supply point to components and terminals where it is used to drive mechanical devices, converted to heat or light or made available through outlets to appliances that may be temporarily connected or disconnected from the power supply. This is considered to include the provision of distribution points at which a supply circuit may be split into multiple sub-circuits, protective devices and support devices such as cable tray, conduit, cable trunking etc. Whilst the Electrical Engineering process is concerned with the provision of power to heating elements and lighting fittings; it is not concerned with the requirements or actual provision of heat and light from such elements and fittings. Six main process stages are considered within the Electrical Engineering lifecycle. These are shown in the high level process map below as: Plan Electrical Systems Design Electrical Systems Install Electrical Systems Test and Commission Electrical Systems 1 af :11

4 Electrical Engineering (PM) - Confluence 2 af :11 5. Operate Electrical Systems 6. Maintain Electrical Systems

5 Electrical Engineering (PM) - Confluence 3 af :11 Process Overview Id Task Name Description Process Stage(s) 1 Task Plan Electrical Systems Outline Feasibility(2), Substantive Feasability(3) 2 Sub-Process (collapsed) Design Electrical Systems Outline conceptual design(4), Full conceptual design(5), Coordinated design and procurement(6) 3 Task Install Electrical Systems Production information(7). Construction(8) 4 Task Test and Commission Electtrical Systems Construction(8) 5 Task Operate Elements and Systems Operation and maintenance(9) 6 Task Maintain Elements and Systems Operation and maintenance(9) Note that this mappings splits the general project stage "Construction" between the Electrical stages "Install" and "Test and Commission". Role Overview The primary roles shown in the process model diagram (as "swimlanes") are defined as: Electrical Design Electrical Construction Facilities Management (in this case, concerned with the electrical engineering aspects of facilities management) Exchange Requirements The following Exchange Requirements describe the information need in the activities identified in this Process Map. Name er_exchange_electrical_model (programming) er_exchange_electrical_model (space) er_exchange_electrical_model (equipment) er_exchange_electrical_model (systems) Description No description available cyclical requirement cyclical requirement cyclical requirement Process Descriptions In this section, all of the processes shown in the diagram above are described. Plan Electrical Systems - ID:1 Type Name Task Plan Electrical Systems Documentation The objective of the planning activity is to: - prepare general outline of requirements (program or brief) and plan future action for the specific planning task concerned, - set up client organisation for programming (or briefing) - obtain program requirements (brief) from the client organisation, - appoint organisations to the project for carrying out work as appropriate to the specific planning task concerned. In this case, the planning activity is concerned with electrical systems. Design Electrical System - ID:2 Type Sub-Process (collapsed)

6 Electrical Engineering (PM) - Confluence 4 af :11 Name Design Electrical System Documentation The objective of the design activity for a project is the progressive development and refinement of the requirements expressed in the program (brief) and then to propose design solutions to those requirements including construction/installation methods, materials, technical solutions. Design solutions proposed should be validated against the provision of building codes and regulations for the specific location of the project and should be in accordance with sustainability criteria including environmental impact and service life. The cost of the design solutions proposed should be estimated and managed through the progressive development of a cost plan. In this case, the design activity is concerned with electrical systems. Install Electrical Systems - ID:3 Type Name Task Install Electrical Systems Documentation The objective of the construct or install activity for a project is to translate proposed design solutions into actual constructed or installed solutions for the project. This activity includes all actions necessary for: - provision of production information including specifications and schedules outlining quality and type of materials and goods required to achieve the objective and constraints applicable to project execution. - planning and scheduling work tasks, - procurement actions for materials, goods and services including tendering actions - execution of construction and installation tasks up to the point at which the work can be tested, commisioned, inspected and/or determined as complete. In this case, the activity is concerned with installation of electrical systems. Test and Commission Electrical Systems - ID:4 Type Name Task Test and Commission Electrical Systems Documentation The objective of the test, commisson and complete activity for a project is to: - provide for the testing of technical solutions to ensure that they will function with the required level of safety - set up technical solutions to operate according to the actual operating requirements of a project - ensure that construction or installation work has been properly executed and to remedy any defects - turn over project to the client of the clients operating agent In this case, the activity is concerned with testing, commissioning and completion of electrical systems. Operate Elements and Systems - ID:5 Type Name Documentation Task Operate Elements and Systems The objective of the operate elements and systems activity for a project is to perform those actions and adjustments required to ensure the normal day to day operation of a project. Maintain Elements and Systems - ID:6 Type Name Task Maintain Elements and Systems Documentation The objective of the maintain elements and systems activity for a project is to perform those actions and adjustments required to return elements and systems to a satisfactory state (physical or functional) for continued operation. The activity is concerned both with planned and unplanned maintenance activities and considers requirements that may be state (failure or imminent failure), time or condition based. A maintenance requirement is triggered by an event which may be caused by either: - the amount of time that has elapsed since the previous maintenance operation was carried out has reached the planned interval between maintenance operations, or - the date on which a maintenance operation is planned has arrived, or - the current operating condition of an element, group of elements or system as determined by the values of one or more parameters has reached a level at which maintenance is set to occur, or - an operational failure (either complete or partial) has occurred that requires a maintenance operation to correct. In the context of the above, maintenance is also considered to encompass replacement where an element has reached the end of its working life. Children Hide Children View in hierarchy Coordination Point Gateways (Information Delivery Manual (IDM)) Data Objects (Information Delivery Manual (IDM))

7 Electrical Engineering (PM) - Confluence 5 af :11 Exchange Requirement Data Objects (Information Delivery Manual (IDM)) Stage 1 - Plan Electrical Systems (Information Delivery Manual (IDM)) Stage 2 - Design Electrical Systems (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

8 Coordination Point Gateways - Confluence 1 af :41 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 29, 2007 (view change) Labels: (None)

9 Coordination Point Gateways - Confluence 2 af :41 Coordination Point Gateways of Electrical Engineering (PM) The following Coordination Point Gateways are defined through the Electrical EngineeringProcess Map: Coordinate_plan Type Name Documentation Coordination Point Coordinate_plan Coordination and approval (or otherwise) of all planning work undertaken. Coordinate_design Type Name Documentation Coordination Point Coordinate_design Coordination and approval (or otherwise) of all design work undertaken. ** This coordination point may be considered as being synonymous with the 'Coordinate_coordinated_design' coordination point. Coordinate_program_design Type Name Documentation Coordination Point Coordinate_program_design Coordination and approval (or otherwise) of speculative design work undertaken at the programming stage. Coordinate_sketch_design Type Name Documentation Coordination Point Coordinate_sketch_design Coordination and approval (or otherwise) of design work undertaken at the sketch design stage. Coordinate_full_concept_design Type Coordination Point

10 Coordination Point Gateways - Confluence 3 af :41 Name Documentation Coordinate_full_concept_design Coordination and approval (or otherwise) of design work undertaken at the full concept design stage. Coordinate_coordinated_design Type Name Documentation Coordination Point Coordinate_coordinated_design Coordination and approval (or otherwise) of design work undertaken at the coordinated design stage. Coordinate_equipment_location Type Name Documentation Coordination Point Coordinate_equipment_location The purpose here is to represent a point at which the model of the electrical systems is brought together with equivalent models from other roles for coordination and approval. Coordination is concerned with ensuring that items of equipment are in proper spatial and functional relationship to each other taking into account their size and location in terms of space allocation and structural provision. For example: (1) major items of equipment applying a significant load on the structure need to have suitable structural support, (2) equipment requiring maintenance action should not have access restricted by other technical systems components, (3) visible items should be in appropriate locations for functional and aesthetic coordination. Coordinate_spaces_and_systems Type Name Documentation Coordination Point Coordinate_spaces The purpose here is to bring together information that is currently available about the spaces as required for the technical systems designs to ensure that requirements are coordinated and that space allocations as required are made. Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

11 Data Objects - Confluence 1 af :44 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 29, 2007 (view change) Labels: (None)

12 Data Objects - Confluence 2 af :44 Data Objects of Electrical Engineering (PM) The following data objects are defined through the Electrical EngineeringProcess Map: Electrical Requirements Type Name Documentation Data Object Electrical Requirements Requirements for the provision of electrical services. Previous Project Guidance Type Name Documentation Data Object Previous Project Guidance Previous projects of a similar nature from which guidance can be obtained on technical space requirements. Industry Technical Guidance Type Name Documentation Data Object Industry Technical Guidance Industry technical guidance from which guidance can be obtained on technical space requirements. Example: RIF transformer space curves Building Program Type Name Documentation Data Object Building Program This is the document that sets out what needs to be taken into account during the electrical design process. It does not set down data requirements but it does set down the overall expectations that the client has of the electrical engineer and therefore acts as a 'quality assurance' document. States the clients preferences.

13 Data Objects - Confluence 3 af :44 Space Regulations Type Name Documentation Data Object Space Regulations Local regulations on size and placement of technical spaces. Electrical Regulations Type Name Documentation Data Object Electrical Regulations Regulations on the provision, configuration, protection and usage of electrical systems and components. Equipment Data Type Name Documentation Data Object Equipment Data Technical, size and weight specifications for electrical components that may be obtained from external sources. Power Supply Requirements Type Name Documentation Data Object Power Supply Requirements Requirements for the provision of an electrical supply notified to the electrical utility supplier. Cost Data Type Name Documentation Data Object Cost Data Stored cost information from suppliers or other cost planning sources Task Data Type Data Object

14 Data Objects - Confluence 4 af :44 Name Documentation Task Data Stored information about operation and maintenance tasks that should be undertaken on systems and equipment, the skill expected to be able to undertake tasks, the expected frequency of tasks (enabling a proposed maintenance plan to be able to be derived). Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

15 Exchange Requirement Data Objects - Confluence 1 af :19 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 29, 2007 (view change) Labels: (None)

16 Exchange Requirement Data Objects - Confluence 2 af :19 Exchange Requirement Data Objects of Electrical Engineering (PM) The following Exchange Requirements are defined through the Electrical EngineeringProcess Map: er_exchange_electrical_model (programming) Type Name Documentation Data Object er_exchange_electrical_model (programming) Electrical model at the programming stage that can be added to overall building information model. Information at this stage is advisory based on speculative design. It includes the following advisory information provision: - overall size (area) of major technical spaces required, - minimum height requirement for technical spaces, - location of major technical spaces including constrained relationships to any other spaces that may be required for reasons of noise, safety, environmental considerations or other aspects, - required adjacency between major technical spaces considered to be in the vertical as well as in the horizontal plane; this may indicate the required strength of the adjacency (must be, should be, could be), - estimated electrical load for the project, - indications of major equipment items to be located in identified spaces and information that may impact on regulation processes (e.g.planning), - distribution methods available (e.g. 400/3/50, 415/3/50, 240/1/50, 110/1/60 etc.), - list of special spaces for which special design provisions may apply. er_exchange_electrical_model (space) Type Data Object Name er_exchange_electrical_model (space) ** applicable to design stages cyclically ** Documentation Exchange of information about technical spaces for electrical plant and equipment and how other spaces are grouped for system development and for proposed voltage drop zones. Used to coordinate with general zoning and spacing requirements with other roles. er_exchange_electrical_model (equipment) Type Data Object Name er_exchange_electrical_model (equipment) ** applicable to design stages cyclically ** Documentation Exchange of information about shape, size and location of electrical components. Electrical systems information can then be brought together with equivalent information from other roles to ensure that items of equipment are in

17 Exchange Requirement Data Objects - Confluence 3 af :19 proper spatial and functional relationship to each other taking into account their size and location in terms of space allocation and structural provision. Information provided for equipment includes all that provided for prior exchange requirements including spaces information with the addition of: - types of electrical component to to be used and sizes - allocation of type information to occurrences of electrical components - size of type and/or occurrence of electrical component - shape representation of electrical component (using an appropriate representation form that may be symbolic, 2D, 3D boundary representation etc.); the form of representation to be used and the extent of detail that is provided for the component may differ at different stages of the project. - location of occurrences of electrical components. er_exchange_electrical_model (systems) Type Data Object Name er_exchange_electrical_model (systems) ** applicable to design stages cyclically ** Documentation Exchange of information about configuration, size, location and technical data of electrical systems including both the components and the distribution elements. Electrical systems information can then be brought together with equivalent information from other roles to ensure that items of equipment are in proper spatial, functional and technical relationship to each other taking into account their size and location in terms of space allocation and structural provision. Information provided for systems includes all that provided for prior exchange requirements including spaces and components information with the addition of: - estimated or calculated loads for systems and for the project (the definition of estimate or calculation being dependent on project stage and the available technical detail to enable calculation to occur), - form of electrical distribution (e.g. 400/3/50, 415/3/50, 240/1/50, 110/1/60 etc.) - electrical requirements at components (voltage, current, phase and other common technical information) - simultaneous load diversity information required by the power supplier. - types of cable or busbar to be used and sizes - allocation of type information to occurrences of cable/busbar - types of cable carrier elements to be used and sizes - allocation of type information to occurrences of cable carriers - types of protection device and outlet to be used, sizes and technical data - allocation of type information to occurrences of protective device and outlet - allocation of components and distribution elements to circuits - distribution routes The extent of system information exchanged will vary depending on the project stage, (1) Sketch design is expected to include only major routes and information may be provided only in terms of the cable carrier elements used to provide an overall spatial contect. (2) Full concept design is expected to include information about sub-main distribution and may include final circuits. Relevant information about cables is expected together with load information. Technical data will be provided but this may not be sufficiently complete for specification and procurement. (3) Coordinated design will include all circuits and all relevant cable and conductor information including their connectivity and all associated detailed

18 Exchange Requirement Data Objects - Confluence 4 af :19 technical data required for specification and procurement. Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

19 Stage 2 - Design Electrical Systems - Confluence Information Delivery Manual (IDM) Stage 2 - Design Electrical Systems Added by kes, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: (None) 2: Design Electrical Systems Stage 2 of Electrical Engineering (PM) Design Electrical System - ID:2 Type Name Sub-Process (collapsed) Design Electrical System Documentation The objective of the design activity for a project is the progressive development and refinement of the requirements expressed in the program (brief) and then to propose design solutions to those requirements including construction/installation methods, materials, technical solutions. Design solutions proposed should be validated against the provision of building codes and regulations for the specific location of the project and should be in accordance with sustainability criteria including environmental impact and service life. The cost of the design solutions proposed should be estimated and managed through the progressive development of a cost plan. In this case, the design activity is concerned with electrical systems. 1 af :20

20 Stage 2 - Design Electrical Systems - Confluence 2 af :20 Process Overview In the following subsections each process element will be described in more detail.

21 Stage 2 - Design Electrical Systems - Confluence 3 af :20 Design Electrical Systems (Programming) - ID:2.1 Type Name Sub-Process (collapsed) Design Electrical Systems (Programming) The term "programming" is the process of developing a program. Programming includes the assessment of needs/requirements and delimitations/constraints. These are described as a program (e.g. in Norway usually according to Norwegian Standard NS3451). Delimitations can be physical (e.g. area type and size, space program), technical (e.g. number and type of outlets, or type of materials), time based (e.g. project progress) and financial (e.g. investment budget or LCC). The programming stage accounts for the client's assessment of the requirements to be met by the completed construction and forms the basis for determining the budget. Documentation For electrical engineering, the process includes determining: - space program requirements for electrical power systems to meet technical requirements - type of power system to be used (voltage, phasing etc.) - requirement for technical spaces - requirement for vertical distribution spaces - types of system that are relevant Specific requirements for Norwegian practice - Space program requirements use NS3451, down to level of whole system (e.g.lighting system) Design Electrical Systems (Sketch) - ID:2.2 Type Name Sub-Process (collapsed) Design Electrical Systems (Sketch) The term "sketch design" is the process of developing an interdisciplinary design where the propositions from the design team describe relevant alternative main principles and main system solutions (in Norway usually according to Norwegian Standard NS3451). The alternatives are presented with pros and cons. The design team's recommended design solutions for further study at the full concept stage are stated, along with proposed reports to be carried out at the full concept stage. Documentation For electrical design, this process includes determining: - estimate of load to determine incoming size - main vertical routes using indicated spaces - location, sizing and identification of technical spaces - specification of types of system and principles of operation. The result of sketch design is a model that defines technical spaces, vertical distribution routes, key horizontal routes using cable carriers to describe principal routing Costing for sketch design presentation is by high level aggregation element such as lighting overall. Specifics for Norwegian Practice - NS3451, Building element level of systems (down to level of whole system such as all lighting) - Costing uses NS3453 likely to be based on sq.m prices against known previous example buildings. NS3457 is standard table for building categories. Design Electrical Systems (Full Concept) - ID:2.3 Type Name Sub-Process (collapsed) Design Electrical Systems (Full Concept) Documentation The term "full concept design" is the process of developing an interdisciplinary design where the propositions from the design team describe a recommended solution (in Norway usually according to Norwegian Standard NS3451). At this stage all relevant principles and system solutions for all disciplines are stated, qualitatively and quantitatively. Estimated Life Cycle Cost (LCC) for the design shall be provided. All succeeding stages are in principle regarded as "production stages" (i.e. production drawings / models, the physical building, documentation). The full concept design level of detailing should be sufficient to avert later principle / system decisions with quality, progress or economic implications, unless a change is done in programming requirements. Further detailing and smaller changes of design solutions at later stages are considered to be normal and acceptable. Design Electrical Systems (Coordinated) - ID:2.4

22 Stage 2 - Design Electrical Systems - Confluence 4 af :20 Type Name Sub-Process (collapsed) Design Electrical Systems (Coordinated) Documentation The term "coordinated design" is the process of developing a detailed interdisciplinary coordinated design where design team deliverables include a building information model that contains characteristic product specification attributes (in Norway usually according to Norwegian Standard NS3420) suitable for a tender process, including supplementary demands for test procedures, component labeling, documentation etc. A number of additional reports may also be required (e.g. environmental issues reports, LCC according to Norwegian Standard NS3454, waste handling procedures, universal (handicapped friendly) design documentation etc). Children Hide Children View in hierarchy Stage Design Electrical Systems (Programming) (Information Delivery Manual (IDM)) Stage Design Electrical Systems (Design Stages) (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

23 Stage Design Electrical Systems (Programming) - Confluence Information Delivery Manual (IDM) Stage Design Electrical Systems (Programming) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: (None) 2.1: Design Electrical Systems (Programming) Stage 2.1 of Electrical Engineering (PM) : Child of Stage 2 - Design Electrical Systems Design Electrical Systems (Programming) - ID:2.1 Type Name Sub-Process (collapsed) Design Electrical Systems (Programming) The term "programming" is the process of developing a program. Programming includes the assessment of needs/requirements and delimitations/constraints. These are described as a program (e.g. in Norway usually according to Norwegian Standard NS3451). Delimitations can be physical (e.g. area type and size, space program), technical (e.g. number and type of outlets, or type of materials), time based (e.g. project progress) and financial (e.g. investment budget or LCC). The programming stage accounts for the client's assessment of the requirements to be met by the completed construction and forms the basis for determining the budget. Documentation For electrical engineering, the process includes determining: - space program requirements for electrical power systems to meet technical requirements 1 af :21

24 Stage Design Electrical Systems (Programming) - Confluence 2 af :21 - type of power system to be used (voltage, phasing etc.) - requirement for technical spaces - requirement for vertical distribution spaces - types of system that are relevant Specific requirements for Norwegian practice - Space program requirements use NS3451, down to level of whole system (e.g.lighting system)

25 Stage Design Electrical Systems (Programming) - Confluence 3 af :21

26 Stage Design Electrical Systems (Programming) - Confluence 4 af :21 Estimate Space Requirements for Technical Spaces - ID:2.1.1 Type Name Task Estimate Space Requirements for Technical Spaces Documentation Makes a preliminary estimate of the space required for major technical spaces to serve the electrical systems on a project. Major technical spaces are spaces that have a substantial impact on building consideration either in terms of their overall size or their structural implication (special floors etc.). Other (minor) technical spaces will be determined at the sketch design stage. Estimate of the space requirement may include height requirement (e.g. need for 5m height for the type of equipment being considered). Example: A major technical space could be for a diesel generator set, chiller/cooling tower plant, high voltage step down transformers, contributors to electrical provision such as windmills/turbines etc. The estimate is based on experience, knowledge of previous projects, industry guidance etc. Typically, it is determined on a factor based method that takes into account total space area and space function. Non indicated spaces such as circulation space, storage space etc. may be accounted for in total building space by further parameters. This can also be used in accounting for space required to accommodate further expansion that may be mandated by the space program. Define Special Spaces - ID:2.1.2 Type Name Task Define Special Spaces Documentation Special spaces are spaces that may require more detailed elaboration at the programming stage. Typically, they are spaces that have particular, detailed electrical requirements and are not represented as a space type within a libray of such types held by a client. Example: A 'Ship Simulation Room' at Tromso College is used to train ships officers by providing simulated views from the bridge of a ship. This space is modelled in detail even at the programming stage to enable consideration of the particular electrical design requirements of the space. Agree Location and Size of Technical Spaces - ID:2.1.3 Type Name Task Agree Location and Size of Technical Spaces Documentation Propose the location and size of major technical spaces - from previous process (not minor technical spaces). This should be based on the space requirements previously identified. Location of spaces includes the configuration relative to adjacent spaces in the case of there being any constraints or requirements as to room type X adjacent to room type Y. E.g. main distribution and transformer room should be adjacent to each other and both should be adjacent to a space containing a diesel generator set. Identify Incoming Distribution System Type - ID:2.1.4 Type Name Task Identify Incoming Distribution System Type Documentation Consider and identify the form of distribution in terms of voltage/cycles/phase. This may depend on electrical supply availability at a location, client requirements and other factors. May be particularly relevant for extensions to existing buildings where the electrical system is to extend that already used. Estimate Electrical Load - ID:2.1.5 Type Name Task Estimate Electrical Load Documentation For the project as proposed, make an estimate of the expected overall electrical load so that a preliminary estimate of the size of the incoming electrical supply can be made. Load includes estimates of: - power requirement including for elements with motors - lighting requirement - heating requirement - elevators, escalators and walkways Estimate Cost - ID:2.1.6

27 Stage Design Electrical Systems (Programming) - Confluence 5 af :21 Type Name Task Assess Cost Documentation For the project as proposed, make an assessment of the order of magnitude cost of the electrical systems. Order of magnitude costing will largely be based on cost information from previous projects. Specifics for Norwegian Practice - Costing uses NS3453 and is likely to be based on sq.m. prices against known previous example buildings. - NS3457 is standard table for building categories. Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

28 Stage Design Electrical Systems (Design Stages) - Confluence Information Delivery Manual (IDM) Stage Design Electrical Systems (Design Stages) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: (None) 2.2: Design Electrical Systems (Design Stages) Stage 2.2 of Electrical Engineering (PM) : Child of Stage 2 - Design Electrical Systems Design Electrical Systems (Sketch) - ID:2.2 Type Name Sub-Process (collapsed) Design Electrical Systems (Sketch) Documentation The term "sketch design" is the process of developing an interdisciplinary design where the propositions from the design team describe relevant alternative main principles and main system solutions (in Norway usually according to Norwegian Standard NS3451). The alternatives are presented with pros and cons. The design team's recommended design solutions for further study at the full concept stage are stated, along with proposed reports to be carried out at the full concept stage. For electrical design, this process includes determining: - estimate of load to determine incoming size - main vertical routes using indicated spaces 1 af :23

29 Stage Design Electrical Systems (Design Stages) - Confluence 2 af :23 - location, sizing and identification of technical spaces - specification of types of system and principles of operation. The result of sketch design is a model that defines technical spaces, vertical distribution routes, key horizontal routes using cable carriers to describe principal routing Costing for sketch design presentation is by high level aggregation element such as lighting overall. Specifics for Norwegian Practice - NS3451, Building element level of systems (down to level of whole system such as all lighting) - Costing uses NS3453 likely to be based on sq.m prices against known previous example buildings. NS3457 is standard table for building categories. Design Electrical Systems (Full Concept) - ID:2.3 Type Name Sub-Process (collapsed) Design Electrical Systems (Full Concept) Documentation The term "full concept design" is the process of developing an interdisciplinary design where the propositions from the design team describe a recommended solution (in Norway usually according to Norwegian Standard NS3451). At this stage all relevant principles and system solutions for all disciplines are stated, qualitatively and quantitatively. Estimated Life Cycle Cost (LCC) for the design shall be provided. All succeeding stages are in principle regarded as "production stages" (i.e. production drawings / models, the physical building, documentation). The full concept design level of detailing should be sufficient to avert later principle / system decisions with quality, progress or economic implications, unless a change is done in programming requirements. Further detailing and smaller changes of design solutions at later stages are considered to be normal and acceptable. *Design Electrical Systems (Coordinated) - ID:2.4 Type Name Sub-Process (collapsed) Design Electrical Systems (Coordinated) Documentation The term "coordinated design" is the process of developing a detailed interdisciplinary coordinated design where design team deliverables include a building information model that contains characteristic product specification attributes (in Norway usually according to Norwegian Standard NS3420) suitable for a tender process, including supplementary demands for test procedures, component labeling, documentation etc. A number of additional reports may also be required (e.g. environmental issues reports, LCC according to Norwegian Standard NS3454, waste handling procedures, universal (handicapped friendly) design documentation etc).

30 Stage Design Electrical Systems (Design Stages) - Confluence 3 af :23

31 Stage Design Electrical Systems (Design Stages) - Confluence 4 af :23 Estimate Space Requirements for Technical Spaces - ID:2.2.1 Type Name Task Estimate Space Requirements for Technical Spaces Documentation Estimate of the space required for technical spaces to serve the electrical systems on a project. Technical spaces include rooms e.g. transformer rooms/spaces, switch rooms etc. as well as vertical distribution spaces. This can include height requirement. This task also confirms the space requirement for the major technical spaces identified at the programming stage. The estimate of space requirement is based on experience, knowledge of previous projects, industry guidance etc. Zone Spaces Into Systems - ID:2.2.2 Type Name Task Zone spaces into systems Documentation Identify spaces and group them into zones within which all entities of a given class (or range of classes) are grouped together to belong to a particular system Example: All lighting in this space belongs to system ABC123 Propose Location and Size of Technical Spaces - ID:2.2.3 Type Name Task Propose Location and Size of Technical Spaces Documentation Propose and agree the location, shape and size of technical spaces. This should be based on the space requirements previously identified but should expand this requirement in terms of the geometry of the space. Location of spaces includes the configuration relative to adjacent spaces in the case of there being any constraints as to room type X adjacent to room type Y Estimate Voltage Drop Zones - ID:2.2.4 Type Name Task Estimate voltage drop zones Documentation Further breaks down spaces and zones to estimate whether the voltage drop for a system within the spaces/zones will be within the limits set by electrical regulations. This task also makes a preliminary assessment of requirements for the main distribution board, sub-main distribution boards, panels and motor control centers and their grouping from the main incoming supply. Final circuits from distribution boards are excluded from this task at this stage in the project development. Select And Locate Equipment - ID:2.2.5 Type Name Documentation Sub-Process (collapsed) Select and locate equipment For main items of equipment, select generic types and estimate their size, location and weight. Select And Size Distribution Routes - ID:2.2.6 Type Name Documentation Sub-Process (collapsed) Select and size distribution routes Selection of distribution method, estimate of load and diversity, routing and sizing of cables/busbars, specification of carrier types. Assign Operational Information - ID:2.2.7 Type Task

32 Stage Design Electrical Systems (Design Stages) - Confluence 5 af :23 Name Documentation Assign Operational Information Preliminary assignment of operating and maintenance data about the systems and distribution routes that forms the basis for later operating and maintenance instruction information. Estimate Cost - ID:2.2.8 Type Name Task Estimate Cost Documentation Estimate the cost of the proposed construction/installation at the current design stage Specifics for Norwegian Practice - NS3457 is standard table for building categories. Children Hide Children View in hierarchy Stage Select And Locate Equipment (Information Delivery Manual (IDM)) Stage Select And Size Distribution Routes (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

33 Stage Select And Locate Equipment - Confluence Information Delivery Manual (IDM) Stage Select And Locate Equipment Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: (None) 2.2.5: Select and Locate Equipment Stage of Electrical Engineering (PM) : Child of Stage Design Electrical Systems (Design Stages) Select And Locate Equipment - ID:2.2.5 Type Name Documentation Sub-Process (collapsed) Select and locate equipment For main items of equipment, select generic types and estimate their size, location and weight. 1 af :24

34 Stage Select And Locate Equipment - Confluence 2 af :24 Model distribution boards - ID:

35 Stage Select And Locate Equipment - Confluence 3 af :24 Type Name Documentation Task Model distribution boards Includes requirements for control panels, sub-main distribution boards, motor control centres and similar components. Model switching devices - ID: Type Name Documentation Task Model switching devices Provides information about switching devices (types and occurrences) used in electrical systems. Model protective devices - ID: Type Name Sub-Process (expanded) Model protective devices Documentation Includes fuses. MCBs etc. Initially design will focus on the whole protective device. As design progresses, more detail will be required in the protective device and information provided for the breaker unit and tripping unit. Model breaker unit - ID: Type Name Documentation Task Model breaker unit Provides information about breaker units in protective devices. Model tripping unit - ID: Type Name Documentation Task Model tripping unit Provides information about tripping units in protective devices. Model motors and generators - ID: Type Name Task Model motors and generators Documentation Identifies the location and load of motors and generators. For motors, a major requirement will be for driving mechanical equipment such as pumps, fans, chiller units and the like for which location information will be required from HVAC and piping processes. Model outlets - ID: Type Name Documentation Task Model outlets Provides information about power outlets (types and occurrences) used in electrical systems.

36 Stage Select And Locate Equipment - Confluence 4 af :24 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

37 Stage Select And Size Distribution Routes - Confluence Information Delivery Manual (IDM) Stage Select And Size Distribution Routes Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 28, 2007 (view change) Labels: (None) 2.2.6: Select And Size Distribution Routes Stage of Electrical Engineering (PM) : Child of Stage Design Electrical Systems (Design Stages) Select And Size Distribution Routes - ID:2.2.6 Type Name Documentation Sub-Process (collapsed) Select and size distribution routes Selection of distribution method, estimate of load and diversity, routing and sizing of cables/busbars, specification of carrier types. 1 af :26

38 Stage Select And Size Distribution Routes - Confluence 2 af :26

39 Stage Select And Size Distribution Routes - Confluence 3 af :26 Select Distribution Method - ID: Type Name Task Select distribution method Documentation Decide on the way in which electrical power will be distributed. During the sketch design stage, several alternative distribution methods may be proposed. The final choice of the distribution method is typically made at the full concept design stage. The distribution method will also determine the type of carrier (conduit, tray, trunking, ladder) to be used for the main distribution routes. Example: Distribution may be by busbar or cable. Decide Main Distribution Routes - ID: Type Name Task Decide main distribution routes Documentation Using spaces allocated to systems and voltage drop zones, decide distribution routes for cables. At sketch design stage, routes will focus on main cables and/or busbars from the main distribution board to sub-main distribution boards located throughout the project. At full concept and coordinated design stage, routes will include final circuits. Estimate Loads At Sub-Main Distribution Boards - ID: Type Name Documentation Task Estimate loads at sub-main distribution boards Estimate the load to be met at each sub-main distribution board. Sum Loads - ID: Type Name Task Sum loads Documentation Add the estimated loads progressively back to the incoming supply point. This will provide an estimated load on each section of the main distribution cable and a total estimated load which the incoming electrical supply is required to meet. Estimate Cable Size And Number Of Conductors - ID: Type Name Documentation Task Estimate cable size and number of conductors From the loads determined for the main distribution routes, estimate the required cable size and number of cables. Estimate Diversity Factor - ID: Type Name Task Estimate diversity factor Documentation Estimate a diversity factor for electrical supply that considers the expected maximum simultaneous load on the system given that not all power consuming equipment contributing to the total expected load is expected to be on at the same time.

40 Stage Select And Size Distribution Routes - Confluence 4 af :26 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

41 Exchange Electrical Model - Equipment (ER) - Confluence 1 af :53 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

42 Exchange Electrical Model - Equipment (ER) - Confluence 2 af :53 Exchange of information to enable coordination of equipment with other technical design role, building design and structural design. Please ensure that you have read the process mapping document 'pm_electrical_engineering' before proceeding with this exchange requirement. The scope of this exchange requirement is the exchange of information to enable coordination of equipment with other technical design role, building design and structural design. It includes the need for shape, size and location of components and also for weight to be included. This exchange requirement allows for the provision of information at various stages during the design process including outline conceptual or sketch design, full conceptual design and coordinated design. The information provided at each stage is essentially the same. However, the level of certainty regarding equipment and components used will increase at each stage allowing greater certainty in space provision. It is assumed that the information provisions outlined in the exchange requirement er_exchange_electrical_model (space) have been satisfied. This provides an initial assessment of spaces from the perspective of building design and electrical design as well as project details. Information provided through this exchange requirement includes: Electrical component type and size Note that, for the purposes of this exchange requirement, only those electrical components having significant size and requiring location within a technical space need to participate. Shape representation of electrical component type Weight of electrical component type Location and orientation of occurrences of electrical component type Information Requirements Precursor Context Electrical Equipment Description In this section all precursor related information needed to satisfy this Exchange Requirement will be described In this section all equipment related information needed to satisfy this Exchange Requirement will be described Results Type Information Requirements Actor Receiving Model Building model updated for component information. Shape and location of components may have been provided previously or may be specified through this exchange requirement. No content found for label(s) rs_er-exchange-electricalmodel-equipment.

43 Exchange Electrical Model - Equipment (ER) - Confluence 3 af :53 Referenced by This list shows all process maps which reference this specific ER. No content found for label(s) er-exchange-electrical-model-equipment. Children Hide Children View in hierarchy 0 - Precursor - Exchange Electrical Model - Equipment (ER) (Information Delivery Manual (IDM)) 0 - Result - Exchange Electrical Model - Equipment (ER) (Information Delivery Manual (IDM)) 1 - Electrical Equipment - Exchange Electrical Model - Equipment (ER) (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

44 0 - Precursor - Exchange Electrical Model - Equipment (ER) - Confluence 1 af :55 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 Labels: (None)

45 0 - Precursor - Exchange Electrical Model - Equipment (ER) - Confluence 2 af :55 Precursor Space For information, refer to: er_exchange_electrical_model(space) The provisions of the exchange requirement Exchange Electrical Model - Space must be satisfied. This includes: all context information provided through project details spatial structure elements (site, buildings, storeys, spaces) including suggested and accepted modifications to technical spaces Structure For information, refer to: er_exchange_structural_model(xxx) The provisions of the exchange requirement [Exchange Structural Model - XXX] must be satisfied so that the shape, size and location of structural members are available for reference and coordination. Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

46 0 - Result - Exchange Electrical Model - Equipment (ER) - Confluence 1 af :55 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

47 0 - Result - Exchange Electrical Model - Equipment (ER) - Confluence 2 af :55 Result type (FP/ ER/ Document/ PSet/ Specification etc.) Information Provided Actor Receiving Result Identifier Model Building model updated for component information. Shape and location of components may have been provided previously or may be specified through this exchange requirement. Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

48 1 - Electrical Equipment - Exchange Electrical Model - Equipment (ER) - Confluence 1 af :56 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

49 1 - Electrical Equipment - Exchange Electrical Model - Equipment (ER) - Confluence 2 af :56 Electrical Equipment In this section all electrical equipment realted information needed to satisfy the Exchange Electrical Model - Equipment will be described. Information Needed Man Opt Rec Actor Supplying Functional Part The owner history of the equipment must be asserted Building Design [Model Electrical Equipment (type, predefined_type) (FP)] For each item of electrical equipment or distribution point to be considered, general attributes of the equipment types and occurrences may be specified including: name to extend identification of the type or occurrence description that can be used for any further qualifying information The shape representation and placement for the electrical equipment or distribution point should be asserted. The shape representation of an item of electrical equipment is typically a representation map which is defined for the equipment type and then referenced for each occurrence. Each occurrence specifies its own placement. Within the representation map, the particular form of the shape representation may differ according to the life cycle stage as with flow segments. Generally, the representations selected for the flow fitting representation map will be either: Axis Representation Body Representation o Swept solid o CSG o Bounding box o Boundary representation (Brep) \ Note that since elements may have multiple shape representations, provision of shape representations of electrical systems at different lifecycle stages should be considered as cumulative and not as alternative. Equipment whose shape and location may need to be shared are suggested in the list below ElectricDistributionPoint ElectricFlowStorageDevice battery capacitorbank harmonicfilter inductorbank ups ElectricGenerator Building Design, [Product Manufacture], [Product Supply] Building Design, [Product Manufacture], [Product Supply] [Model Electrical Equipment (type, predefined_type) (FP))] [Model Electrical Equipment (type, predefined_type) (FP))]

50 1 - Electrical Equipment - Exchange Electrical Model - Equipment (ER) - Confluence 3 af :56 ElectricMotor Transformer Weight As well as the placement and shape of components, the weight of major items needs to be captured and communicated to ensure structural coordination. Thus, for each electrical component the following information should be provided. Information Needed Man Opt Rec The method of measurement used. This should be set to a value that is agreed to represent a weight value for coordination purposes. For instance, a value such as 'Structural Weight Coordination' might be used. The name of the weight quantity provided. This could be a name like 'Structural Weight'. Description of the weight quantity. Assign the weight quantity to the appropriate equipment item Actor Supplying Electrical Design Electrical Design Electrical Design Electrical Design Functional Part Define Quantity (FP) Define Quantity (FP) Define Quantity (FP) Define Quantity (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

51 Exchange Electrical Model - Space (ER) - Confluence 1 af :58 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

52 Exchange Electrical Model - Space (ER) - Confluence 2 af :58 Exchange of information about technical spaces for electrical plant and equipment. Used to coordinate with general zoning and spacing requirements with other roles. Please ensure that you have read the process mapping document 'pm_electrical_engineering' before proceeding with this exchange requirement. The scope of this exchange requirement is the exchange of information to enable provision of technical spaces, spaces in which electrical systems are configured into circuits and spaces or zones in which the maximum voltage drop across a circuit as set out in local regulations is not exceeded. The purpose of the exchange requirement is to enable coordination of electrical systems requirements with other technical systems requirements (notably HVAC and piping systems) and with building design with regard to the provision of space for the technical systems. This exchange requirement allows for the provision of information at various stages during the design process including outline conceptual or sketch design, full conceptual design and coordinated design. The information provided at each stage is essentially the same. However, the level of certainty regarding equipment and components used will increase at each stage allowing greater certainty in space provision. It is assumed that the information provisions outlined in the exchange requirement er_exchange_building_model (sketch) have been satisfied. This provides an initial assessment of spaces from the perspective of building design and project details. Information provided through this exchange requirement includes: Electrical component type and size Note that, for the purposes of this exchange requirement, only those electrical components having significant size and requiring location within a technical space need to participate. Shape representation of electrical component type Location and orientation of occurrences of electrical component type Proposed technical space specification with area, configuration and height Note that, at earlier stages of design, area and height only may be given; later stages of design may also propose a space configuration. Spaces in which electrical systems are located Grouping of spaces served by an identified system (electrical circuit) Grouping of spaces into zones where each zone represents a maximum distance from a distribution board without exceeding a maximum allowed voltage drop. Information may be optionally provided concerning material from which elements are constructed and their classification. Information Requirements Precursor Context Description In this section all precursor related information needed to satisfy this Exchange Requirement will be described

53 Exchange Electrical Model - Space (ER) - Confluence 3 af :58 Electrical Equipment Technical Spaces Circuit Space Group Voltage Drop Zone In this section all equipment related information needed to satisfy this Exchange Requirement will be described In this section all technical space related information needed to satisfy this Exchange Requirement will be described In this section all circuit space related information needed to satisfy this Exchange Requirement will be described In this section all voltage frop related information needed to satisfy this Exchange Requirement will be described Results Type Information Requirements Actor Receiving Building Design (RS) Model Building model updated for technical space information providing information to the Building Designer. The information shall also be provided for the Electrical and Piping Designers. Electrical Design (RS) Piping Design (RS) Referenced by This list shows all process maps which reference this specific ER. No content found for label(s) er-exchange-hvac-model-space. Children Hide Children View in hierarchy 0 - Precursor - Exchange Electrical Model - Space (ER) (Information Delivery Manual (IDM)) 1 - Electrical Equipment - Exchange Electrical Model - Space (ER) (Information Delivery Manual (IDM)) 2 - Technical Spaces - Exchange Electrical Model - Space (ER) (Information Delivery Manual (IDM)) 3 - Circuit Space Group - Exchange Electrical Model - Space (ER) (Information Delivery Manual (IDM)) 4 - Voltage Drop Zone - Exchange Electrical Model - Space (ER) (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

54 0 - Precursor - Exchange Electrical Model - Space (ER) - Confluence 1 af :59 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

55 0 - Precursor - Exchange Electrical Model - Space (ER) - Confluence 2 af :59 Precursor For information, refer to: er_exchange_building_model(sketch) The provisions of the exchange requirement [Exchange Building Model - Sketch]must be satisfied. This includes all context information provided through project details including: the name of the project and, optionally, the phase of work of the project the default units used throughout the project the world coordinate system the coordinate space dimension the precision used within the geometric representations true north relative to the world coordinate system different types and scales that can be used for representing stored shapes (symbols) where these have multiple representations (e.g. multi-view blocks) \ Additionally, the building information model provides the following information proposed by the building designer that is required for electrical systems design: spatial structure element s (site, buildings, storeys, spaces) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

56 1 - Electrical Equipment - Exchange Electrical Model - Space (ER) - Confluence 1 af :00 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None) Electrical Equipment

57 1 - Electrical Equipment - Exchange Electrical Model - Space (ER) - Confluence 2 af :00 In this section all electrical equipment realted information needed to satisfy the Exchange Electrical Model - Space will be described. Information Needed Man Opt Rec Actor Supplying Functional Part The owner history of the equipment must be asserted Building Design [Model Electrical Equipment (type, predefined_type) (FP)] For each item of electrical equipment or distribution point to be considered, general attributes of the equipment types and occurrences may be specified including: name to extend identification of the type or occurrence description that can be used for any further qualifying information The shape representation and placement for the electrical equipment or distribution point should be asserted. The shape representation of an item of electrical equipment is typically a representation map which is defined for the equipment type and then referenced for each occurrence. Each occurrence specifies its own placement. Within the representation map, the particular form of the shape representation may differ according to the life cycle stage as with flow segments. Generally, the representations selected for the flow fitting representation map will be either: Axis Representation Body Representation o Swept solid o CSG o Bounding box o Boundary representation (Brep) \ Note that since elements may have multiple shape representations, provision of shape representations of electrical systems at different lifecycle stages should be considered as cumulative and not as alternative. Components that may be located in technical spaces and that may impact on space provision are suggested in the list below ElectricDistributionPoint ElectricFlowStorageDevice battery capacitorbank harmonicfilter inductorbank ups ElectricGenerator ElectricMotor Transformer Building Design, [Product Manufacture], [Product Supply] Building Design, [Product Manufacture], [Product Supply] [Model Electrical Equipment (type, predefined_type) (FP))] [Model Electrical Equipment (type, predefined_type) (FP))]

58 1 - Electrical Equipment - Exchange Electrical Model - Space (ER) - Confluence 3 af :00 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

59 2 - Technical Spaces - Exchange Electrical Model - Space (ER) - Confluence 1 af :01 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None) Technical Spaces

60 2 - Technical Spaces - Exchange Electrical Model - Space (ER) - Confluence 2 af :01 In this section all technical spaces related information needed to satisfy the [*Exchange Electrical Model Model - Space*] will be described. For electrical design, technical spaces are spaces that have as their primary purpose the housing of electrical or other technical equipment. Technical spaces are subject to 'negotiation' between the building designer and technical designers. It is therefore expected that suggestions made by the electrical designer will be applied in the building model through quantities rather than by making changes to space configuration provided. Thus, for a space that is a technical space, the following information should be defined.: Information Needed Man Opt Rec Identify the method of measurement used. This should be set to a value that is agreed to represent a suggestion made by the technical designer. For instance, a value such as 'Technical Space Reconciliation' might be used The name of the area quantity to be suggested. This could be a name like 'Technical Space Area'. Description for the area quantity. _A value should be asserted for the description and should take the form indicating that the quantity being described is a suggestion Assign the quantity to the space Actor Supplying Electrical Design Electrical Design Electrical Design Electrical Design Functional Part Define Quantity (FP) Define Quantity (FP) Define Quantity (FP) Define Quantity (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

61 3 - Circuit Space Group - Exchange Electrical Model - Space (ER) - Confluence 1 af :02 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 Labels: (None) Circuit Space Group

62 3 - Circuit Space Group - Exchange Electrical Model - Space (ER) - Confluence 2 af :02 In this section all circuit space group related information needed to satisfy the [*Exchange Electrical Model Model - Space*] will be described. For spaces that are to be grouped as being within the scope of a single electrical system (electrical circuit), each individual space should be identified and the group that they belong to should be named and identified. For the group, the following information should be provided: Information Needed Man Opt Rec Actor Supplying Functional Part Name of the group for the system (electrical circuit) that is expected to serve it Electrical Design Description of the purpose of the group Electrical Design Assigns To Group (FP) Assigns To Group (FP) The object type of the group should be set to 'Circuit Space Group' (or other designation agreed for the purpose). Electrical Design Assigns To Group (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

63 4 - Voltage Drop Zone - Exchange Electrical Model - Space (ER) - Confluence 1 af :02 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None) Voltage Drop Zone

64 4 - Voltage Drop Zone - Exchange Electrical Model - Space (ER) - Confluence 2 af :02 In this section all voltage drop zone related information needed to satisfy the [*Exchange Electrical Model Model - Space*] will be described. For spaces that are to be grouped as being within the scope of a voltage drop zone, each individual space should be identified and the group that they belong to should be named and identified. For the zone group, the following information should be provided: Information Needed Man Opt Rec Actor Supplying Functional Part Name of the zone Electrical Design Assigns To Group (FP) Description of the zone Electrical Design Assigns To Group (FP) The object type of the group should be set to 'Voltage Drop' (or other designation agreed for the purpose). Electrical Design Assigns To Group (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

65 Exchange Electrical Model - Systems (ER) - Confluence 1 af :04 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

66 Exchange Electrical Model - Systems (ER) - Confluence 2 af :04 Exchange of information about electrical systems (circuits), their distribution, connection, switching, protection etc. Please ensure that you have read the process mapping document 'pm_electrical_engineering' before proceeding with this exchange requirement. This exchange requirement describes the information to be provided about electrical systems. It allows for the provision of information at various stages during the design process including: Representation of components and their relation to spatial structures (sites, buildings and spaces) without connection to systems Representations that connect terminal and components using simple line based connection or logical connection (indication of connection between items without physical representation) at early design stages that enable routing, terminal and component location information to be exchanged; Full 3D shape representations at detailed design stages that enable coordination between different building services systems, between services and structure and between services and the building construction elements. Information items that may be required about electrical systems include: System name Terminal type, size, location, orientation, and electrical characteristics. Control (switchgear) size, location, orientation, and electrical characteristics Component type, size, location, orientation, and electrical characteristics Appliance type size, location, orientation and electrical characteristics Cable and conductor section size, shape, location, and electrical characteristics Cable carrier (conduit, tray, trunking, ladder) section size, shape, location, orientation and related cables Cable carrier fitting type, size, location Shape of elements Occurrences of types of terminal, switchgear, component, appliance, cable, conductor and cable carrier Reference to other technical components requiring and electrical supply Connections between elements in the electrical system Material from which elements are constructed Classification of elements Information Requirements Context Description Precursor Flow Segments Flow Fittings In this section all precursor related information needed to satisfy this Exchange Requirement will be described In this section all flow segment related information needed to satisfy this Exchange Requirement will be described In this section all flow fitting related information needed to satisfy this Exchange Requirement will be described

67 Exchange Electrical Model - Systems (ER) - Confluence 3 af :04 Electrical Equipment Ports System-Space Relationship System Base Properties In this section all equipment related information needed to satisfy this Exchange Requirement will be described In this section all port related information needed to satisfy this Exchange Requirement will be described In this section all system-space relationship information needed to satisfy this Exchange Requirement will be described In this section all system related information needed to satisfy this Exchange Requirement will be described In this section all electrical base properties needed to satisfy this Exchange Requirement will be described Results Type Information Requirements Actor Receiving Model Electrical system model No content found for label(s) rs_er-exchange-electrical-model-systems. Referenced by This list shows all process maps which reference this specific ER. No content found for label(s) er-exchange-electrical-model-systems. Children Hide Children View in hierarchy 0 - Precursor - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 0 - Result - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 1 - Flow Segments - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 2 - Flow Fittings - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 4 - Ports - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 5 - System-Space Relationship - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 6 - System - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) 7 - Base Properties - Exchange Electrical Model - Systems (ER) (Information Delivery Manual (IDM)) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

68 0 - Precursor - Exchange Electrical Model - Systems (ER) - Confluence 1 af :04 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 Labels: (None)

69 0 - Precursor - Exchange Electrical Model - Systems (ER) - Confluence 2 af :04 Precursor Equipment For information, refer to: er_exchange_electrical_model(equipment) The provisions of the exchange requirement Exchange Electrical Model - Equipment must be satisfied. This includes: all context information provided through project details spatial structure elements (site, buildings, storeys, spaces) including suggested and accepted modifications to technical spaces coordinated placement of major components (minor components not requiring structural coordination are considered to be selected and placed through this exchange requirement) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

70 0 - Result - Exchange Electrical Model - Systems (ER) - Confluence 1 af :05 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 Labels: (None)

71 0 - Result - Exchange Electrical Model - Systems (ER) - Confluence 2 af :05 Result type (FP/ ER/ Document/ PSet/ Specification etc.) Model Information Provided Actor Receiving Result Identifier Electrical system model Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

72 1 - Flow Segments - Exchange Electrical Model - Systems (ER) - Confluence 1 af :06 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 Labels: (None)

73 1 - Flow Segments - Exchange Electrical Model - Systems (ER) - Confluence 2 af :06 Flow Segments In this section all flow segment related information needed to satisfy the Exchange Electrical Model - Systems will be described. Generally for Flow Segments Information Needed Man Opt Rec Actor Supplying Functional Part The owner history of the segment Name to extend identification of the type or occurrence Description that can be used for any further qualifying information Where information about an electrical system is to be exchanged as part of the building model specification, the placement and shape representation should be asserted. For an electrical system, the principal shape representation to be used may differ at particular stages in the project life cycle. Shape representations as used should have values for representation identifier and representation type attributes set as given in the functional part. For early design stages, line based representation may be used as defined by the Axis Representation in the functional part. For electrical systems, the flow segments may exist but not be shown as having a physical representation Electrical Design Electrical Design Electrical Design Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] OR [Model Flow Segment (CableCarrier, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] OR [Model Flow Segment (CableCarrier, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] OR [Model Flow Segment (CableCarrier, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] OR [Model Flow Segment (CableCarrier, PredefinedType) (FP)]

74 1 - Flow Segments - Exchange Electrical Model - Systems (ER) - Confluence 3 af :06 in which case the representation to be used should be as defined by the Logical Representation in the functional part. For detailed design stages, Body Representation may be used. These may be assigned to the type using mapped representations or to the occurrence as 'own' shape representations. In an exchange of ductwork information, the forms of body representation used should be clearly indicated to the receiving system as being: Swept solid CSG Bounding box Boundary representation (Brep) \ Note that since elements may have multiple shape representations, provision of shape representations at different lifecycle stages should be considered as cumulative and not as alternative. Cable Properties Specification of properties that may be assigned through property sets as defined in the functional part. For flow segments, properties may be defined either for the segment type or the segment occurrence or for both (although definition for both is not expected in practice). Properties specified should include the following. Information Needed Man Opt Rec Actor Supplying Functional Part Cross section area of the cable Electrical Design Nominal length of the cable Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] Nominal width of the cable or, in the case of a circular cross section, the diameter Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] Nominal height of the cable Electrical Design Normal operating temperature for the cable Electrical Design Maximum operating temperature for the cable Electrical Design The material from which the insulation is constructed Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)]

75 1 - Flow Segments - Exchange Electrical Model - Systems (ER) - Confluence 4 af :06 Color code used on cable Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] Conductor Properties Note that specification of conductor properties may not occur until later design stages on a project. Specification of properties that may be assigned through property sets as defined in the functional part. For flow segments, properties may be defined either for the segment type or the segment occurrence or for both (although definition for both is not expected in practice). Properties specified may include: Information Needed Man Opt Rec Actor Supplying Functional Part Cross section area of the conductor Electrical Design Nominal length of the conductor Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] Type of function for which the conductor is intended (phase, neutral, ground etc.) Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] The phase identification used when the function of the conductor is a phase Electrical Design Material from which the conductor is constructed e.g. Aluminium or Copper Electrical Design Material from which the insulation sheath of the conductor is constructed Electrical Design Maximum operating temperature for the conductor Electrical Design Indication of whether the sheath is fire resistant (= TRUE) or not (= FALSE) Electrical Design Color code used on sheath Electrical Design [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] [Model Flow Segment (Cable, PredefinedType) (FP)] Cable Carrier Properties Note that specification of cable carrier properties may occur at earlier design stages of a project to specify distribution route. Specification of properties that may be assigned through property sets as defined in the functional part. For flow segments, properties may be defined either for the segment type or the segment occurrence or for both (although definition for both is not expected in practice). Properties specified should include the following.

76 1 - Flow Segments - Exchange Electrical Model - Systems (ER) - Confluence 5 af :06 Information Needed Man Opt Rec Actor Supplying Functional Part Nominal length of the carrier segment Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Nominal width of the carrier segment Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Nominal height of the carrier segment Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Configuration (for cable ladder segments) Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Presence of a cover (for cable tray segments) Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Number of internal compartments (for cable trunking segments) Electrical Design [Model Flow Segment (CableCarrier, PredefinedType) (FP)] Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

77 2 - Flow Fittings - Exchange Electrical Model - Systems (ER) - Confluence 1 af :07 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 (view change) Labels: (None)

78 2 - Flow Fittings - Exchange Electrical Model - Systems (ER) - Confluence 2 af :07 Flow Fittings In this section all flow fitting related information needed to satisfy the Exchange Electrical Model - Systems will be described. Cable Carrier Information Needed Man Opt Rec Actor Supplying Functional Part The owner history of the fitting Name to extend identification of the type or occurrence Description that can be used for any further qualifying information Where information about fitting shape is to be exchanged as part of the building model specification, the placement and shape representation should be asserted. Shape representation is typically a representation map which is defined for the <entity> type and then referenced for each occurrence. Each occurrence specifies its own placement. Within the representation map, the particular form of the shape representation may differ according to the life cycle stage. Generally, the representations selected for the flow fitting representation map will follow the representations selected for flow segments being either: Axis Representation Body Representation o Swept solid o CSG o Bounding box o Boundary representation (Brep) \ Note that since elements may have multiple shape representations, provision of shape representations at different lifecycle stages should be considered as cumulative and not as alternative. Electrical Design Electrical Design Electrical Design Electrical Design [Model Flow Fitting (CableCarrier, PredefinedType) (FP)] [Model Flow Fitting (CableCarrier, PredefinedType) (FP)] [Model Flow Fitting (CableCarrier, PredefinedType) (FP)] [Model Flow Fitting (CableCarrier, PredefinedType) (FP)] Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

79 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) - Confluence 1 af :08 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 10, 2007 (view change) Labels: (None)

80 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) - Confluence 2 af :08 Electrical Equipment In this section all electrical equipment realted information needed to satisfy the Exchange Electrical Model - Systems will be described. Information Needed Man Opt Rec Actor Supplying Functional Part The owner history of the equipment must be asserted Electrical Design [Model Electrical Equipment (type, predefined_type) (FP)] For each item of electrical equipment or distribution point to be considered, general attributes of the equipment types and occurrences may be specified including: name to extend identification of the type or occurrence description that can be used for any further qualifying information Where information about equipment shape is to be exchanged as part of the building model specification, the placement and shape representation should be asserted. The shape representation of an item of electrical equipment is typically a representation map which is defined for the equipment type and then referenced for each occurrence. Each occurrence specifies its own placement. Within the representation map, the particular form of the shape representation may differ according to the life cycle stage as with flow segments. Generally, the representations selected for the flow fitting representation map will follow the representations selected for flow segments being either: Axis Representation Body Representation o Swept solid o CSG o Bounding box o Boundary representation (Brep) \ Note that since elements may have multiple shape representations, provision of shape representations of electrical systems at different lifecycle stages should be considered as cumulative and not as alternative. Electrical Design, [Product Manufacture], [Product Supply] Electrical Design, [Product Manufacture], [Product Supply] [Model Electrical Equipment (type, predefined_type) (FP))] [Model Electrical Equipment (type, predefined_type) (FP))] Equipment Properties Information Needed Man Opt Rec Actor Supplying Functional Part

81 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) - Confluence 3 af :08 Specification of properties that may be assigned through property sets as defined in the functional part. For electrical equipment, properties will generally be defined for the equipment type. Properties specified vary according to the equipment type. Refer to the functional part for further details. Note that particular equipment types and their properties are identified through the specification of parameters within the functional part as shown. Note that although lamp type is specified as a type of electrical equipment, lamps do not participate in this exchange requirement since the electrical system connects to the light fixture and not to the lamp. Electrical Design [Model Electrical Equipment (type, predefined_type) (FP)] ElectricalAppliance computer directwaterheater dishwasher electriccooker electricheater facsimile freestandingfan freezer fridge_freezer handdryer indirectwaterheater microwave photocopier printer refrigerator radiantheater scanner telephone tumbledryer tv vendingmachine washingmachine waterheater watercooler ElectricFlowStorageDevice battery capacitorbank harmonicfilter inductorbank ups ElectricGenerator currently must be specified as user defined ElectricHeater electricpointheater electriccableheater electricmatheater ElectricMotor dc induction

82 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) - Confluence 4 af :08 polyphase reluctancesynchronous synchronous ElectricTimeControl timeclock timedelay relay LightFixture pointsource directionsource Outlet audiovisualoutle communicationsoutlet poweroutlet ProtectiveDevice fusedisconnector circuitbreaker earthfailuredevice residualcurrentcircuitbreaker residualcurrentswitch varistor SwitchingDevice contactor emergencystop starter switchdisconnector toggleswitch Transformer current frequency voltage Note that, at early design stages, equipment items used in other systems may also be applied in the context of an electrical system where such items of equipment require the provision of electrical power or control. The detailed design of such equipment will show that cabling is to a motor or some other intermediate equipment item that falls within the general definition of electrical equipment above. However, to allow for early design requirements, it is recommended that the following equipment items are also considered for inclusion: Boiler Chiller Compressor

83 3 - Electrical Equipment - Exchange Electrical Model - Systems (ER) - Confluence 5 af :08 Condensor CoolingTower Damper EvaporativeCooler Evaporator Fan Filter HeatExchanger Humidifier Pump SanitaryTerminal SpaceHeater UnitaryEquipment Valve For further information on predefined types of these equipment items that may have electrical connections, refer to functional parts for modeling ventilation or piping equipment. Distribution Board (Point) Properties Information Needed Man Opt Rec Actor Supplying Functional Part An electric distribution board (or distribution point) is a particular form of electrical equipment that is generally created by the aggregation of a number of other electrical components. Specification of properties that may be assigned through property sets as defined in the functional part. Electrical Design, [Product Manufacture], [Product Supply] [Model Electrical Distribution Point (function) (FP)] Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

84 4 - Ports - Exchange Electrical Model - Systems (ER) - Confluence 1 af :08 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 (view change) Labels: (None)

85 4 - Ports - Exchange Electrical Model - Systems (ER) - Confluence 2 af :08 Ports In this section all port related information needed to satisfy the Exchange Electrical Model - Systems will be described. A port is a logical mechanism that is used to enable an element to connect to another element. A distribution port is a type of port that is used for connecting together distribution flow elements such as electrical elements. A distribution element may have one or more points at which it connects to other elements. A distribution port is located at a point where a connection can occur. The location of the port is determined in the context of the local coordinate system of the element to which it belongs. A port is defined as belonging to a particular element through a port to element connection relationship. Generally for Ports The information that is captured concerning a distribution port includes the following. Information Needed Man Opt Rec Actor Supplying Functional Part Port name and description Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] Placement of the port in the context of the local coordinate system of the element to which it belongs Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] Shape representation of the port; for a distribution system this would typically be a point. Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] Relationship between the port and the element for which it provides a connection opportunity Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] Direction of flow through the port Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)]

86 4 - Ports - Exchange Electrical Model - Systems (ER) - Confluence 3 af :08 Properties Additional properties that should be defined for ports are as follows. Information Needed Man Opt Rec Actor Supplying Functional Part The number of the port in the context of the element Electrical Design The type of connection made at the port Electrical Design [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] [Model Distribution Port (cable) (FP)] OR [Model Distribution Port (cable carrier) (FP)] Connection A connection describes the connected relationship made between two ports. Information Needed Man Opt Rec For connections made between ports, the values of flow direction for each port must match. If the flow direction of the relating port is a SOURCE (outgoing), the flow direction of the related port must be SINK (incoming). If the flow direction of the relating port is SOURCEANDSINK, the flow direction of the related port must also be SOURCEANDSINK Actor Supplying Electrical Design Functional Part Connect Ports (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

87 5 - System-Space Relationship - Exchange Electrical Model - Systems (ER) - Confluence 1 af :09 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 (view change) Labels: (None)

88 5 - System-Space Relationship - Exchange Electrical Model - Systems (ER) - Confluence 2 af :09 System-Space Relationship In this section all system-space relationship information needed to satisfy the Exchange Electrical Model - Systems will be described. Information Needed Man Opt Rec Describe the connection relationship between a system and a spatial structure element (in which the system may have a connection with one or more different spatial structure elements). Spatial structure elements include sites, buildings, building storeys and individual spaces. A system may be related to as many spatial structure elements as required by specifying multiple system/spatial structure element relationships. Actor Supplying Electrical Design Functional Part Services Building (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

89 6 - System - Exchange Electrical Model - Systems (ER) - Confluence 1 af :09 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 Labels: (None)

90 6 - System - Exchange Electrical Model - Systems (ER) - Confluence 2 af :09 System In this section all system related information needed to satisfy the Exchange Electrical Model - Systems will be described. Provides the information concerning systems where a system is a grouping of elements. In the context of a distribution system, all of the elements that are grouped to form the system should be known type of distribution element. As well as enabling the description of complete systems, this functional part enables the grouping of elements into subsystems. Note that the shape representation of a system is derived from the shape representation of the elements that are grouped together within the system. The system itself has no 'own' shape representation. The information required for a system is as below. Information Needed Man Opt Rec Actor Supplying Functional Part Name of the system Electrical Design Model System (FP) Description of the system Electrical Design Model System (FP) Elements that are grouped together to form the system Electrical Design Model System (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

91 7 - Base Properties - Exchange Electrical Model - Systems (ER) - Confluence 1 af :10 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Feb 11, 2007 Labels: (None)

92 7 - Base Properties - Exchange Electrical Model - Systems (ER) - Confluence 2 af :10 Base Properties In this section all base property related information needed to satisfy the Exchange Electrical Model - Systems will be described. Describes information about the basic electrical properties of an electrical component, flow segment or circuit that is required. Note that electrical base properties should only be applied to an electrical distribution element, an electrical distribution element type or an electrical circuit. However, electrical base properties may also be applied at early design to an element that requires an electrical supply to (for example) a motor but where the motor is not specified as a separate object. An example of this might be where the HVAC engineer could specify power requirement, voltage, phase and frequency for an air handling unit without specifying the fan motor used. Properties required are as below. Information Needed Man Opt Rec Actor Supplying Functional Part Type of electrical current applied Electrical Design Define Electrical Base Properties (FP) Input electrical potential Electrical Design Define Electrical Base Properties (FP) Nominal frequency of input voltage wave form Electrical Design Define Electrical Base Properties (FP) Full load electrical current requirements Electrical Design Define Electrical Base Properties (FP) Minimum current carrying capacity of the electrical circuit Electrical Design Define Electrical Base Properties (FP) Maximum power input of the electrical device Electrical Design Define Electrical Base Properties (FP) Actual electrical input power of the electrical device at its rated capacity Electrical Design Define Electrical Base Properties (FP) Relative phase of input conductors Electrical Design Define Electrical Base Properties (FP) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

93 Assigns To Group (FP) - Confluence 1 af :30 Information Delivery Manual (IDM) Added by Brendan McFarlane, last edited by Brendan McFarlane on Sep 27, 2006 (view change) Labels: (None)

94 Assigns To Group (FP) - Confluence 2 af :30 Overview Describes a grouping relationship in which the parent object (the group) is made from the assignment of a set of other objects. Grouping allows for any arbitrary collection of objects to be brought together into a designated, named group. Objects can still act independently of the group or can be operated upon within the context of the whole group. An object can belong to more than one group concurrently. For instance, it may belong to one group that is a system, to a second group for cost scheduling purposes, and to a third group for scheduling purposes. Certain specific types of group are defined within the IFC model. These include: Asset Condition Inventory Structural load group Structural result group System Electrical Circuit (type of system) Zone In a group assignment relationship, the group is referred to as the 'relating group' whilst the assigned objects are referred to as the 'related objects'. There is always exactly one relating group and there may be one or many related objects. An object may be assigned only once to each group in which it participates. The group assignment relationship is described at a high level in the IFC model as between an occurrence of IfcGroup and occurrences of IfcObject. Practically, the relationship will be between instances of subtypes of IfcObject and these inherit the relationship. With exchange requirements that call upon the use of this functional part, reference to the type of group to which objects are assigned may be defined using a parameter as: fp_assigns_to_group () -> describes an arbitrary collection of objects into a named group fp_assigns_to_group (system) -> describes the assignment of objects to a system group fp_assigns_to_group (asset) -> describes the assignment of objects to an identified asset group etc. Use of the parameter recognizes that certain rules may apply to the collection of objects into particular group types.

95 Assigns To Group (FP) - Confluence 3 af :30 Results Declares the assignment of a collection of objects into a group Description Entity/Pset/Functional Part MAN REC OPT Create the group to which entities will be related and the entities. Note that groups are modeled explicitly elsewhere. Set the occurrence of the group in the relationship IfcGroup Set the occurrences of the child entities in the relationship IfcObject <child subtypes> Assert the attributes of the relationship Assert the parent relationship IfcRelAssignsToGroup.RelatingGroup -> IfcGroup Assert the child relationship IfcRelAssignsToGroup.RelatedObjects -> IfcObject Assert the type of related objects from the predefined list if required This value can be used to identify the parent supertype of related objects as e.g. product, group, process, control etc. If the related objects have mixed supertypes, then the value.notdefined. should be used. Assert the identity of the relationship Assert the owner history of the relationship IfcRelAssignsToGroup.RelatedObjectsType -> IfcObjectTypeEnum IfcRelAssignsToGroup.GlobalId -> IfcGloballyUniqueId IfcRelAssignsToGroup.OwnerHistory -> fp_apply_owner_history Specify a name of the relationship IfcRelAssignsToGroup.Name Specify a description of the relationship IfcRelAssignsToGroup.Description IFC Entities Required IfcGroup IfcObject IfcRelationsip IfcRelAssigns IfcRelAssignsToGroup IfcRoot IFC Datatypes Required IfcGloballyUniqueId IfcLabel IfcObjectTypeEnum IfcText

96 Assigns To Group (FP) - Confluence 4 af :30 IFC Functions Required - IFC Property Sets Required - IDM Functional Parts Required fp_apply_owner_history EXPRESS-G

97 Assigns To Group (FP) - Confluence 5 af :30 EXPRESS Schema SCHEMA FP_ASSIGNS_TO_GROUP; TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcObjectTypeEnum = ENUMERATION OF (PRODUCT, PROCESS, CONTROL, RESOURCE, ACTOR, GROUP, PROJECT, NOTDEFINED); END_TYPE; ENTITY IfcObject ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ObjectType : OPTIONAL IfcLabel; INVERSE HasAssignments : SET OF IfcRelAssigns FOR RelatedObjects; WHERE WR1 : SIZEOF(QUERY(temp <* IsDefinedBy 'IFC2X2_FINAL.IFCRELDEFINESBYTYPE' IN TYPEOF(temp))) <= 1; ENTITY IfcRoot ABSTRACT SUPERTYPE OF (ONEOF(IfcObject, IfcRelationship)); GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId; ENTITY IfcRelAssigns ABSTRACT SUPERTYPE SUBTYPE OF(IfcRelationship); RelatedObjects : SET [1:?] OF IfcObject; RelatedObjectsType : OPTIONAL IfcObjectTypeEnum; WHERE WR1 : IfcCorrectObjectAssignment(RelatedObjectsType, RelatedObjects);

98 Assigns To Group (FP) - Confluence 6 af :30 ENTITY IfcGroup SUBTYPE OF(IfcObject); INVERSE IsGroupedBy : IfcRelAssignsToGroup FOR RelatingGroup; ENTITY IfcRelAssignsToGroup SUBTYPE OF(IfcRelAssigns); RelatingGroup : IfcGroup; WHERE WR1 : SIZEOF(QUERY(Temp <* SELF\IfcRelAssigns.RelatedObjects RelatingGroup :=: Temp)) = 0; ENTITY IfcRelationship SUBTYPE OF(IfcRoot); ENTITY fp_apply_owner_history; END_SCHEMA; Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

99 Define Electrical Base Properties (FP) - Confluence 1 af :24 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 29, 2007 (view change) Labels: (None)

100 Define Electrical Base Properties (FP) - Confluence 2 af :24 Overview Provides information about the basic electrical properties of an electrical component, flow segment or circuit. Whilst electrical base properties are created as a property set definition in IFC and can therefore be formally be applied to any subtype of IfcObject, there is a practical informal proposition that identifies that electrical base properties can only be applied to an electrical distribution element, an electrical distribution element type or an electrical circuit. Electrical base properties may also be applied at early design to an element that requires an electrical supply to (for example) a motor but where the motor is not specified as a separate object. An example of this might be where the HVAC engineer could specify power requirement, voltage, phase and frequency for an air handling unit without specifying the fan motor used. Electrical base properties should be used when a minimum electrical specification is required. This is particularly useful for other than electrical engineers to provide a set of requirements to an electrical engineer. When a detailed specification of electrical properties is required, relevant property sets such as Pset_EectricalDeviceCommon, Pset_ElectricalCircuit should be used (or should be added in addition; in which case, properties referenced in both a property set and the electrical base properties definition should be exactly equivalent). Results Returns a set of electrical base properties and identifies the object(s) for which the properties are defined.. Define mandatory electrical base properties Description Entity/Pset/Functional Part MAN REC OPT Set the Input electrical potential (voltage) IfcElectricalBaseProperties.InputVoltage::IfcElectricVoltageMeasure Set the nominal frequency of input voltage wave form For basic electrical supplies, the frequency value is anticipated to be 50Hz or 60Hz for an alternating current supply. IfcElectricalBaseProperties.InputFrequency:: Set the relative phase of input conductors IfcElectricalBaseProperties.InputPhase::INTEGER

101 Define Electrical Base Properties (FP) - Confluence 3 af :24 For basic electrical supplies, the phase value is expected to be 1 or 3. Define optional electrical base properties Set the type of electrical current applied IfcElectricalBaseProperties.ElectricCurrentType::IfcElectricCurrentEnum The value is specified as either alternating, direct or user defined from the predefined list. Set the full load electrical current requirements. IfcElectricalBaseProperties.FullLoadCurrent::IfcElectricCurrentMeasure Set the minimum current carrying capacity of the electrical circuit IfcElectricalBaseProperties.MinimumCircuitCurrent::IfcElectricCurrentMeasure Set the maximum power input of the electrical device. IfcElectricalBaseProperties.MaximumPowerInput::IfcPowerMeasure Set the actual electrical input power of the electrical device at its rated capacity IfcElectricalBaseProperties.RatedPowerInput::IfcPowerMeasure Assert general attributes for the electrical base properties Assert the owner history of the electrical base properties IfcElectricalBaseProperties.OwnerHistory::fp_apply_owner_history Set a name to the collection of electrical base properties IfcElectricalBaseProperties.Name::IfcLabel Provide a description of the collection of electrical base properties IfcElectricalBaseProperties.Description::IfcText

102 Define Electrical Base Properties (FP) - Confluence 4 af :24 Define the properties for the object. Electrical baseproperties may be defined either for type or occurrence objects. It is an informal proposition of this functional part that electrical base properties should only be defined for types or occurrences of electrical distribution elements or for systems or for other distribution elements that may be assigned an electrical supply without specification of an intervening electrical element. Electrical base properties should not be defined for other elements. Define the distribution element type to which the electrical base properties apply. fp_define_by_type Define the distribution element occurrence to which the electrical base properties apply. fp_define_by_properties IFC Entities Required IfcDistributionElement IfcDistributionElementType IfcDistributionFlowElement IfcDistributionFlowElementType IfcElectricalBaseProperties IfcElectricalCircuit IfcElement IfcElementType IfcEnergyProperties IfcGroup IfcObject IfcProduct IfcPropertyDefinition IfcPropertySetDefinition IfcRoot IfcSystem IfcTypeObject

103 Define Electrical Base Properties (FP) - Confluence 5 af :24 IfcTypeProduct IFC Datatypes Required IfcElectricCurrentEnum IfcElectricCurrentMeasure IfcElectricVoltageMeasure IfcEnergySequenceEnum IfcFrequencyMeasure IfcGloballyUniqueId IfcIdentifier IfcLabel IfcObjectTypeEnum IfcPowerMeasure IfcText IFC Functions Required - IFC Property Sets Required - IDM Functional Parts Required fp_apply_owner_history fp_define_by_properties fp_define_by_type fp_map_representation fp_place_object fp_represent_product EXPRESS-G EXPRESS Schema

104 Define Electrical Base Properties (FP) - Confluence 6 af :24 SCHEMA FP_DEFINE_ELECTRICAL_BASE_PROPERTIES; TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcIdentifier = STRING; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcElectricCurrentMeasure = REAL; END_TYPE; TYPE IfcElectricVoltageMeasure = REAL; END_TYPE; TYPE IfcFrequencyMeasure = REAL; END_TYPE; TYPE IfcPowerMeasure = REAL; END_TYPE; TYPE IfcElectricCurrentEnum = ENUMERATION OF (ALTERNATING, DIRECT, NOTDEFINED); END_TYPE; TYPE IfcEnergySequenceEnum = ENUMERATION OF (PRIMARY, SECONDARY, TERTIARY, AUXILIARY, USERDEFINED, NOTDEFINED); END_TYPE; ENTITY IfcProduct ABSTRACT SUPERTYPE SUBTYPE OF(IfcObject); ObjectPlacement : OPTIONAL fp_place_object; Representation : OPTIONAL fp_represent_product; WHERE WR1 : (EXISTS(Representation) AND EXISTS(ObjectPlacement)) OR (EXISTS(Representation) AND (NOT('IFC2X2_FINAL.IFCPRODUCTDEFINITIONSHAPE' IN TYPEOF(Representation)))) OR (NOT(EXISTS(Representation)));

105 Define Electrical Base Properties (FP) - Confluence 7 af :24 ENTITY IfcObject ABSTRACT SUPERTYPE OF (ONEOF(IfcGroup, IfcProduct)) SUBTYPE OF(IfcRoot); ObjectType : OPTIONAL IfcLabel; WHERE WR1 : SIZEOF(QUERY(temp <* IsDefinedBy 'IFC2X2_FINAL.IFCRELDEFINESBYTYPE' IN TYPEOF(temp))) <= 1; ENTITY IfcRoot ABSTRACT SUPERTYPE OF (ONEOF(IfcObject, IfcPropertyDefinition)); GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId; ENTITY IfcPropertyDefinition ABSTRACT SUPERTYPE OF (ONEOF(IfcPropertySetDefinition, IfcTypeObject)) SUBTYPE OF(IfcRoot); ENTITY IfcPropertySetDefinition ABSTRACT SUPERTYPE SUBTYPE OF(IfcPropertyDefinition); INVERSE DefinesType : SET [0:1] OF IfcTypeObject FOR HasPropertySets; ENTITY IfcTypeObject SUBTYPE OF(IfcPropertyDefinition); ApplicableOccurrence : OPTIONAL IfcLabel; HasPropertySets : OPTIONAL LIST [1:?] OF IfcPropertySetDefinition; WHERE WR1 : EXISTS(SELF\IfcRoot.Name); ENTITY IfcTypeProduct SUBTYPE OF(IfcTypeObject); Tag : OPTIONAL IfcLabel; RepresentationMaps : SET [1:?] OF fp_map_representation; WHERE WR41 : NOT(EXISTS(SELF\IfcTypeObject.ObjectTypeOf[1])) OR (SIZEOF(QUERY(temp <* SELF\IfcTypeObject.ObjectTypeOf[1].RelatedObjects NOT('IFC2X2_FINAL.IFCPRODUCT' IN TYPEOF(temp))) ) = 0); ENTITY IfcElementType

106 Define Electrical Base Properties (FP) - Confluence 8 af :24 ABSTRACT SUPERTYPE SUBTYPE OF(IfcTypeProduct); ElementType : OPTIONAL IfcLabel; ENTITY IfcDistributionElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcElementType); ENTITY IfcDistributionFlowElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcDistributionElementType); ENTITY IfcGroup SUBTYPE OF(IfcObject); ENTITY IfcSystem SUBTYPE OF(IfcGroup); WHERE WR1 : SIZEOF (QUERY (temp <* SELF\IfcGroup.IsGroupedBy.RelatedObjects NOT('IFC2X2_FINAL.IFCELEMENT' IN TYPEOF(temp)))) = 0; ENTITY IfcElement ABSTRACT SUPERTYPE SUBTYPE OF(IfcProduct); Tag : OPTIONAL IfcIdentifier; ENTITY IfcDistributionElement SUBTYPE OF(IfcElement); ENTITY IfcDistributionFlowElement SUBTYPE OF(IfcDistributionElement); ENTITY IfcEnergyProperties SUBTYPE OF(IfcPropertySetDefinition); EnergySequence : OPTIONAL IfcEnergySequenceEnum; UserDefinedEnergySequence : OPTIONAL IfcLabel; ENTITY IfcElectricalBaseProperties SUBTYPE OF(IfcEnergyProperties); ElectricCurrentType : OPTIONAL IfcElectricCurrentEnum; InputVoltage : IfcElectricVoltageMeasure; InputFrequency : IfcFrequencyMeasure; FullLoadCurrent : OPTIONAL IfcElectricCurrentMeasure; MinimumCircuitCurrent : OPTIONAL IfcElectricCurrentMeasure;

107 Define Electrical Base Properties (FP) - Confluence 9 af :24 MaximumPowerInput : OPTIONAL IfcPowerMeasure; RatedPowerInput : OPTIONAL IfcPowerMeasure; InputPhase : INTEGER; ENTITY IfcElectricalCircuit SUBTYPE OF(IfcSystem); ENTITY fp_map_representation; ENTITY fp_apply_owner_history; ENTITY fp_place_object; ENTITY fp_represent_product; ENTITY fp_define_by_type; ENTITY fp_define_by_properties; END_SCHEMA; Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

108 Define Quantity (FP) - Confluence 1 af :12 Information Delivery Manual (IDM) Added by Jeffrey Wix, last edited by Jeffrey Wix on Jan 29, 2007 (view change) Labels: (None)

109 Define Quantity (FP) - Confluence 2 af :12 Overview Provides the means by which a quantity that is defined by a method of measurement may be defined for an object. 'Methods of measurement' are frequently used as the basis on which elements may be measured for inclusion in cost or progress submissions. They may include sets of rules that determine how the measurement should be established and the units of measure in which it should be expressed. The rules may be developed from some abstract concepts of measurement rather than actual values (such as length, area etc.) that might otherwise be physically associated with an object or that might be derived through knowledge of the geometric representation of an object. For example, consider a straight section of pipework with a 90? bend at one end and a square tee at the other end. The actual length of the pipe section (as cut and fitted) is measured as the distance between each physical end. In geometric terms, it is normally measured as shown; that is the length of piping between the end of the bend to which it is connected and the end of the tee to which it is connected. The actual fitting elements can also be determined as being a tee and a bend. A method of measurement might however set a rule that the length should be measured as the distance between the ends of the section of pipe if they were projected to a point at which they would meet with an adjacent section of pipe. This would mean that the measured length would be greater than the actual length but would be considered satisfactory under the rules of the method of measurement for costing. A further rule might be that instead of determining the type of each fitting, all fittings would be treated as being the same (called a 'counted fitting' in this example). The information presented in this functional part includes: Method of measurement to be used for quantity definition Name and (if required) description of the quantity to be measured Named physical quantities with values and units appropriately set Additional discriminator, quality and usage attributes for complex quantities comprising sets of values Specification of objects for which the quantities are defined. Results Specification of quantities for objects according to a defined method of measurement. Define the physical quantity to be used Description Entity/Pset/Functional Part MAN REC OPT If the physical quantity being measured is a simple quantity, then one of the following must be asserted:

110 Define Quantity (FP) - Confluence 3 af :12 Note that a simple quantity is a single unit of measure and IfcQauntityXXX (where XXX is the extended name as shown) is a subtype of IfcPhysicalSimpleQuantity) A count of a number of items IfcQuantityCount.CountValue::IfcCountMeasure A measure of length IfcQuantityLength.LengthValue::IfcLengthMeasure A measure of area IfcQuantityArea.AreaValue::IfcAreaMeasure A measure of volume IfcQuantityVolume.VolumeValue::IfcVolumeMeasure A measure of weight IfcQuantityWeight.WeightValue::IfcWeightMeasure A measure of time IfcQuantityTime.TimeValue::IfcTimeMeasure If the physical quantity being measured is a complex quantity: Where a complex quantity is a set of simple quantities that all apply to a given component or aspect of the element. Determine the set of physical quantities to be assigned using the simple quantity specifications above. IfcPhysicalComplexQuantity.HasQuantities::IfcPhysicalSimpleQuantity Identify the discrimination used to distinguish the complex quantity. IfcPhysicalComplexQuantity.Discrimination::IfcLabel

111 Define Quantity (FP) - Confluence 4 af :12 Examples of discriminations are 'layer', 'steel bar diameter' etc. Indicate a quality of the quantities that are grouped under the complex quantity IfcPhysicalComplexQuantity.Quality::IfcLabel Indicate a usage type of the quantities that are grouped under the complex quantity IfcPhysicalComplexQuantity.Usage::IfcLabel Assert the name of the physical quantity This could be a name like 'gross area' (to distinguish it from the a 'net area') IfcQuantityXXX.Name::IfcLabel OR IfcPhysicalComplexQuantity.Name::IfcLabel Describe the physical quantity as required IfcQuantityXXX.Description::IfcLabel OR IfcPhysicalComplexQuantity. Description::IfcLabel Select the unit of measure in which the physical quantity is to be asserted. _If no unit of measure is to be assigned, then this attribute should not be asserted. Otherwise, it must be asserted. _ IfcQuantityXXX.Unit::fp_unit OR IfcPhysicalComplexQuantity. Unit::fp_unit Identify the method of measurement to be used Set the method of measurement to be used for measuring the quantity to be defined. IfcElementQuantity.MethodOfMeasurement::IfcLabel

112 Define Quantity (FP) - Confluence 5 af :12 The method of measurement will typically be defined as a set of measurement rules for use in a particular place. For instance, measurement of areas in the US might be measured according to the BOMA method whilst quantities for costing in the UK could be measured according to SMM6 (6th edition of the Standard Method of Measurement) Identify the quantities to be measured Assert the name of the quantity to be measured. This could be a name like 'Buildable Area'. Alternatively, it could be a more complete name that could be used as part of a description within a bill of quantities. IfcElementQuantity.Name::IfcLabel Describe the quantity to be measured. This is an optional value that can be used. In the example above, the buildable area might be described as being 'the maximum area of a site on which a building or buildings might be placed'. Descriptions can be used to further enhance information in bills of quantities. IfcElementQuantity.Description::IfcLabel Assign the quantity Set the physical quantity to the element quantity. IFC Entities Required IfcElementQuantity IfcPhysicalQuantity IfcPhysicalQuantity may be a set of simple and complex quantities. At IfcPhysicalComplexQuantity least one quantity that is either an IfcPhysicalSimpleQuantity (using IfcPhysicalSimpleQuantity IfcQuantityXXX subtypes) or an IfcPhysicalComplexQuantity must be IfcPropertyDefinition asserted. IfcPropertySetDefinition IfcElementQuantity.Quantities::IfcPhysicalQuantity

113 Define Quantity (FP) - Confluence 6 af :12 IfcQuantityArea IfcQuantityCount IfcQuantityLength IfcQuantityTime IfcQuantityVolume IfcQuantityWeight IfcRoot IFC Datatypes Required IfcAreaMeasure IfcCountMeasure IfcGloballyUniqueId IfcLabel IfcLengthMeasure IfcMassMeasure IfcText IfcTimeMeasure IfcVolumeMeasure IFC Functions Required - IFC Property Sets Required - IDM Functional Parts Required fp_apply_owner_history fp_define_by_properties fp_unit EXPRESS-G EXPRESS Schema

114 Define Quantity (FP) - Confluence 7 af :12 SCHEMA FP_DEFINE_QUANTITY; TYPE IfcAreaMeasure = REAL; END_TYPE; TYPE IfcCountMeasure = NUMBER; END_TYPE; TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcLengthMeasure = REAL; END_TYPE; TYPE IfcMassMeasure = REAL; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcTimeMeasure = REAL; END_TYPE; TYPE IfcVolumeMeasure = REAL; END_TYPE; ENTITY IfcRoot ABSTRACT SUPERTYPE; GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId; ENTITY IfcPropertyDefinition ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ENTITY IfcPropertySetDefinition ABSTRACT SUPERTYPE SUBTYPE OF(IfcPropertyDefinition); ENTITY IfcElementQuantity SUBTYPE OF(IfcPropertySetDefinition);

115 Define Quantity (FP) - Confluence 8 af :12 MethodOfMeasurement : OPTIONAL IfcLabel; Quantities : SET [1:?] OF IfcPhysicalQuantity; ENTITY IfcPhysicalQuantity ABSTRACT SUPERTYPE OF (ONEOF(IfcPhysicalComplexQuantity, IfcPhysicalSimpleQuantity)); Name : IfcLabel; Description : OPTIONAL IfcText; INVERSE PartOfComplex : SET [0:1] OF IfcPhysicalComplexQuantity FOR HasQuantities; ENTITY IfcPhysicalComplexQuantity SUBTYPE OF(IfcPhysicalQuantity); HasQuantities : SET [1:?] OF IfcPhysicalQuantity; Discrimination : IfcLabel; Quality : OPTIONAL IfcLabel; Usage : OPTIONAL IfcLabel; WHERE WR21 : SIZEOF(QUERY(temp <* HasQuantities SELF :=: temp)) = 0; ENTITY IfcPhysicalSimpleQuantity ABSTRACT SUPERTYPE OF (ONEOF(IfcQuantityArea, IfcQuantityCount, IfcQuantityLength, IfcQuantityTime, IfcQuantityVolume, IfcQuantityWeight)) SUBTYPE OF(IfcPhysicalQuantity); Unit : OPTIONAL fp_unit; ENTITY IfcQuantityArea SUBTYPE OF(IfcPhysicalSimpleQuantity); AreaValue : IfcAreaMeasure; WHERE WR21 : NOT(EXISTS(SELF\IfcPhysicalSimpleQuantity.Unit)) OR (SELF\IfcPhysicalSimpleQuantity.Unit.UnitType = IfcUnitEnum.AREAUNIT); WR22 : AreaValue >= 0; ENTITY IfcQuantityCount SUBTYPE OF(IfcPhysicalSimpleQuantity); CountValue : IfcCountMeasure; WHERE WR1 : CountValue >= 0; ENTITY IfcQuantityLength SUBTYPE OF(IfcPhysicalSimpleQuantity); LengthValue : IfcLengthMeasure; WHERE WR21 : NOT(EXISTS(SELF\IfcPhysicalSimpleQuantity.Unit)) OR (SELF\IfcPhysicalSimpleQuantity.Unit.UnitType = IfcUnitEnum.LENGTHUNIT); WR22 : LengthValue >= 0;

116 Define Quantity (FP) - Confluence 9 af :12 ENTITY IfcQuantityTime SUBTYPE OF(IfcPhysicalSimpleQuantity); TimeValue : IfcTimeMeasure; WHERE WR21 : NOT(EXISTS(SELF\IfcPhysicalSimpleQuantity.Unit)) OR (SELF\IfcPhysicalSimpleQuantity.Unit.UnitType = IfcUnitEnum.TIMEUNIT); WR22 : TimeValue >= 0; ENTITY IfcQuantityVolume SUBTYPE OF(IfcPhysicalSimpleQuantity); VolumeValue : IfcVolumeMeasure; WHERE WR21 : NOT(EXISTS(SELF\IfcPhysicalSimpleQuantity.Unit)) OR (SELF\IfcPhysicalSimpleQuantity.Unit.UnitType = IfcUnitEnum.VOLUMEUNIT); WR22 : VolumeValue >= 0; ENTITY IfcQuantityWeight SUBTYPE OF(IfcPhysicalSimpleQuantity); WeightValue : IfcMassMeasure; WHERE WR21 : NOT(EXISTS(SELF\IfcPhysicalSimpleQuantity.Unit)) OR (SELF\IfcPhysicalSimpleQuantity.Unit.UnitType = IfcUnitEnum.MASSUNIT); WR22 : WeightValue >= 0; ENTITY fp_apply_owner_history; ENTITY fp_define_by_properties; ENTITY fp_unit; END_SCHEMA; Examples of Quantities Example 1: Setting the length of electrical cables In the example, cables and cores are geometrical represented as a simple line in the drawing. These are intended to signify connections between components and do not necessarily represent actual routes that cables/cores would actually take. Each electrical connection occurrence is here modelled as an IfcFlowSegment that is defined by type as a cable segment. In the example, particular properties of the segment are not elaborated. The occurrences here reference the cable route 1>2>3 in the diagram.

117 Define Quantity (FP) - Confluence 10 af :12 Measurement of the flow segment may be undertaken in various ways. For this example, two measurement are shown. Measurement A is taken in the direct line with allowance made for drop at each point. Measurement B is taken from point 1, rising up and then travelling orthogonally across the space to the mid point and then to the light where it drops to 2. This is repeated to connect to 3. For the purposes of the example, method of measurement A is shown as MoM-A with a length value of 5m for each part (i.e. two flow segments sharing the same quantity measurement). #100 = IFCOWNERHISTORY (... ); #200 = IFCORGANIZATION ($,'IAI',$,$,$); #300 = IFCSIUNIT (.LENGTHUNIT.,$,.METRE.,#301); #301 = IFCDIMENSIONALEXPONENTS (1,0,0,0,0,0,0); #500 = IFCFLOWSEGMENT ('gabcdeghijklmnopqrst500',#100,'cable Segment',$,$,$,$,$); #501 = IFCFLOWSEGMENT ('gabcdeghijklmnopqrst501',#100,'cable Segment',$,$,$,$,$); #600 = IFCELEMENTQUANTITY ('gabcdeghijklmnopqrst600',#100,$,$,'mom-a',(#601)); #601 = IFCQUANTITYLENGTH ('Cable length','most direct route',#300,5.0); #700 = IFCRELDEFINESBYPROPERTIES ('gabcdeghijklmnopqrst700',#100,$,$,(#500,#501),#600); Method of measurement B is shown as MoM-B with a length value of 6.4m for the first segment and 6.7m for the second segment. #100 = IFCOWNERHISTORY (... ); #200 = IFCORGANIZATION ($,'IAI',$,$,$); #300 = IFCSIUNIT (.LENGTHUNIT.,$,.METRE.,#301); #301 = IFCDIMENSIONALEXPONENTS (1,0,0,0,0,0,0); #500 = IFCFLOWSEGMENT ('gabcdeghijklmnopqrst500',#100,'cable Segment',$,$,$,$,$); #501 = IFCFLOWSEGMENT ('gabcdeghijklmnopqrst501',#100,'cable Segment',$,$,$,$,$); #600 = IFCELEMENTQUANTITY ('gabcdeghijklmnopqrst600',#100,$,$,'mom-a',(#601)); #601 = IFCQUANTITYLENGTH ('Cable length','most direct route',#300,6.4); #610 = IFCELEMENTQUANTITY ('gabcdeghijklmnopqrst610',#100,$,$,'mom-a',(#611)); #611 = IFCQUANTITYLENGTH ('Cable length','most direct route',#300,6.7); #700 = IFCRELDEFINESBYPROPERTIES ('gabcdeghijklmnopqrst700',#100,$,$,(#500),#600); #701 = IFCRELDEFINESBYPROPERTIES ('gabcdeghijklmnopqrst701',#100,$,$,(#501),#610); Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

118 Model Distribution Port (FP) - Confluence 1 af :27 Information Delivery Manual (IDM) Added by Brendan McFarlane, last edited by Brendan McFarlane on Sep 18, 2006 (view change) Labels: (None)

119 Model Distribution Port (FP) - Confluence 2 af :27 Provides information concerning distribution ports. A port is a logical mechanism that is used to enable an element to connect to another element. A distribution port is a type of port that is used for connecting together distribution flow elements such as ductwork elements, pipework elements and electrical distribution elements. A distribution element may have one or more points at which it connects to other elements. A distribution port is located at a point where a connection can occur. The location of the port is determined in the context of the local coordinate system of the element to which it belongs. A port is defined as belonging to a particular element through a port to element connection relationship. The information that is captured concerning a distribution port includes: Specification of port name and description if required Placement of the port in the context of the local coordinate system of the element to which it belongs The port may be assigned a shape representation; for a distribution system this would typically be a point. Specification of the relationship between the port and the element for which it provides a connection opportunity The direction of flow through the port The number of the port in the context of the element The type of connection made at the port Note that in use, the port will be defined according to the type of system in which it is used. This usage defines properties (within particular property sets) that can be applied. The type of system may be set as a parameter in the exchange requirement by: fp_model_distribution_port [duct] fp_model_distribution_port [pipe] fp_model_distribution_port [cable] fp_model_distribution_port [cablecarrier]

120 Model Distribution Port (FP) - Confluence 3 af :27 Results Model of ports and identification of the element to which ports belong Description Entity/Pset/Functional Part MAN REC OPT Determine the element to which the port is assigned This will be a subtype of IfcDistributionElement IfcElement (subtype) Model the port occurrence Set the global unique identifier IfcDoorStyle.GlobalId -> IfcGloballyUniqueId

121 Model Distribution Port (FP) - Confluence 4 af :27 Apply the owner history IfcDoorStyle.OwnerHistory -> fp_apply_owner_history Specify a name for the distribution port IfcDistributionPort.Name Specify a description for the distribution port IfcDistributionPort.Description Place the port in the context of the element Assign the flow direction of the distribution port Flow through a port may be defined as outward from the element (SOURCE), inward to the element (SINK), either outward or inward (SOURCEANDSINK) or left as not defined. Although this attribute is optional in the IFC model, it is recommended that it should be asserted. IfcDistributionPort.ObjectPlacement -> fp_place_object IfcDistributionPort.FlowDirection -> IfcFlowDirectionEnum Establish the port connection relationship Make the port into the relating port of a connects port to element relationship Make the element into the related element of a connects port to element relationship IfcRelConnectsPortToElement.RelatingPort -> IfcDistributionPort IfcRelConnectsPortToElement.RelatedElement -> IfcElement (subtype) For a port in a ductwork element, set values in the property set Pset_ DistributionPortDuct as indicated below. Set the value for the port number The port number is defined in the context of the element according to local usage. For instance, for a tee element, the inlet port will be numbered 1, the outlet port will be numbered 2 and the branch distribution port will be numbered 3. Set the connection type of the port The connection type defines the method by which the connection is made. Pset_DistributionPortDuct.PortNumber -> IfcPropertySingleValue Pset_DistributionPortDuct.ConnectionType -> IfcPropertyEnumeratedValue For a port in a pipework element, set values in the property set Pset_ DistributionPortPipe as indicated below. Set the value for the port number The port number is defined in the context of the element according to local usage. For instance, for a tee element, the inlet port will be numbered 1, the outlet port will be numbered 2 and the branch distribution port will be numbered 3. Set the connection type of the port The connection type defines the method by which the connection is made. Pset_DistributionPortPipe.PortNumber -> IfcPropertySingleValue Pset_DistributionPortPipe.ConnectionType -> IfcPropertyEnumeratedValue

122 Model Distribution Port (FP) - Confluence 5 af :27 For a port in an electrical distribution element, set values in the property set Pset_ DistributionPortCable as indicated below. Set the value for the port number The port number is defined in the context of the element according to local usage. For instance, for a tee element, the inlet port will be numbered 1, the outlet port will be numbered 2 and the branch distribution port will be numbered 3. Set the connection type of the port The connection type defines the method by which the connection is made. Pset_DistributionPortCable.PortNumber -> IfcPropertySingleValue Pset_DistributionPortCable.ConnectionType -> IfcPropertyEnumeratedValue Define the port to which the properties apply fp_define_by_properties IFC Entities Required IfcDistributionPort IfcElement IfcObject IfcPort IfcProduct IfcRelationship IfcRelConnects IfcRelConnectsPortToElement IfcRoot IFC Datatypes Required IfcFlowDirectionEnum IfcGloballyUniqueId IfcIdentifier IfcLabel IfcText IFC Functions Required - IFC Property Sets Required Pset_DistributionPortDuct Pset_DistributionPortPipe IDM Functional Parts Required fp_apply_owner_history fp_define_by_properties fp_place_object fp_represent_product EXPRESS-G

123 Model Distribution Port (FP) - Confluence 6 af :27

124 Model Distribution Port (FP) - Confluence 7 af :27 EXPRESS Schema SCHEMA FP_MODEL_DISTRIBUTION_PORT; TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcIdentifier = STRING; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcFlowDirectionEnum = ENUMERATION OF (SOURCE, SINK, SOURCEANDSINK, NOTDEFINED); END_TYPE; ENTITY IfcProduct ABSTRACT SUPERTYPE OF (ONEOF(IfcElement, IfcPort)) SUBTYPE OF(IfcObject); ObjectPlacement : OPTIONAL fp_place_object; Representation : OPTIONAL fp_represent_product; WHERE WR1 : (EXISTS(Representation) AND EXISTS(ObjectPlacement)) OR (EXISTS(Representation) AND (NOT('IFC2X2_FINAL.IFCPRODUCTDEFINITIONSHAPE' IN TYPEOF(Representation)))) OR (NOT(EXISTS(Representation))); ENTITY IfcObject ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ObjectType : OPTIONAL IfcLabel; WHERE WR1 : SIZEOF(QUERY(temp <* IsDefinedBy 'IFC2X2_FINAL.IFCRELDEFINESBYTYPE' IN TYPEOF(temp))) <= 1; ENTITY IfcRoot ABSTRACT SUPERTYPE OF (ONEOF(IfcObject, IfcRelationship)); GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId;

125 Model Distribution Port (FP) - Confluence 8 af :27 ENTITY IfcRelationship ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ENTITY IfcRelConnects ABSTRACT SUPERTYPE SUBTYPE OF(IfcRelationship); ENTITY IfcElement ABSTRACT SUPERTYPE SUBTYPE OF(IfcProduct); Tag : OPTIONAL IfcIdentifier; INVERSE HasPorts : SET OF IfcRelConnectsPortToElement FOR RelatedElement; ENTITY IfcRelConnectsPortToElement SUBTYPE OF(IfcRelConnects); RelatingPort : IfcPort; RelatedElement : IfcElement; ENTITY IfcPort ABSTRACT SUPERTYPE SUBTYPE OF(IfcProduct); INVERSE ContainedIn : IfcRelConnectsPortToElement FOR RelatingPort; ENTITY fp_apply_owner_history; ENTITY fp_place_object; ENTITY fp_represent_product; ENTITY IfcDistributionPort SUBTYPE OF(IfcPort); FlowDirection : OPTIONAL IfcFlowDirectionEnum; ENTITY fp_define_by_properties; END_SCHEMA;

126 Model Distribution Port (FP) - Confluence 9 af :27 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

127 Model Electrical Equipment (FP) - Confluence 1 af :31 Information Delivery Manual (IDM) Added by Janice Wix, last edited by Janice Wix on Feb 01, 2007 (view change) Labels: (None)

128 Model Electrical Equipment (FP) - Confluence 2 af :31 Overview This functional part describes the information required to describe an item of equipment used in an electrical system. All such items are types of flow element (IfcDistributionFlowElement) within the IFC model. Electrical equipment may be described generally as any item of plant or equipment that forms part of an electrical or other cabled system and that performs some action other than that of purely distributing the medium (electricity, communication signals etc.) through the system (for which flow segments and flow fittings are used). The types of equipment concerned include: Equipment Type Subtype Electrical appliances FlowTerminal ElectricalAppliance Electric heaters FlowTerminal ElectricHeater Generators EnergyConversionDevice ElectricGenerator Light fixtures FlowTerminal LightFixture Motors EnergyConversionDevice ElectricMotor Outlet points FlowTerminal Outlet Protective devices FlowController ProtectiveDevice Storage devices FlowStorageDevice ElectricFlowStorageDevice Switches FlowController SwitchingDevice Time controller FlowController ElectricTimeControl Transformers EnergyConversionDevice Transformer Note that references to type and subtype in the above list are given in the form that they are shown in the IFC model but without the prefix 'Ifc' or the suffix 'Type'. To convert the names back to the form that they have in the IFC model, the prefix and suffix values must be returned e.g. FlowTerminal :: IfcFlowTerminalType Outlet :: IfcOutletType The information presented in this functional part enables: extension of a basic building model through the provision of size and location information provision of weight information for the structural engineer provision of performance information for analysis

129 Model Electrical Equipment (FP) - Confluence 3 af :31 This information includes: Specification of equipment name and description if required Shape representations of the equipment Identification of the type to which an equipment occurrence conforms The material from which the equipment is constructed The weight of the equipment In addition, performance information for occurrences of equipment of particular types as indicated in the list above may be provided. Specification of the performance information that may be required is given in the tables below. Note that the particular type of equipment to be used, and that therefore defines the performance information requirement, can be set as a parameter in the exchange requirement by: fp_model_electrical_equipment[type, Unknown macro: {predefined_type} ] For instance, for an electrical outlet, reference to the relevant items within this functional part from the exchange requirement would be by specifying: fp_model_electrical_equipment[outlet, PowerOutlet] Results Model of electrical equipment occurrence(s) including shape representation and other basic information Model the equipment type Description Entity/Pset/Functional Part MAN REC OPT Select the type of equipment to be modeled The following are the selections available within the model. Each of these is a functional subtype of IfcDistributionFlowElementType (flow terminal, flow moving device etc. as shown in the Overview list). Further reference generally to these types is shown below as Ifc<Functional>Type. IfcElectricalApplianceType IfcElectricFlowStorageDeviceType IfcElectricGeneratorType IfcElectricHeaterType IfcElectricMotorType IfcElectricTimeControlType

130 Model Electrical Equipment (FP) - Confluence 4 af :31 IfcLightFixtureType IfcOutletType IfcProtectiveDeviceType IfcSwitchingDeviceType IfcTransformerType IfcUnitaryEquipmentType Note that, at early design stages, equipment items used in other systems may also be applied in the context of an electrical system where such items of equipment require the provision of electrical power or control. The detailed design of such equipment will show that cabling is to a motor or some other intermediate equipment item that falls within the general definition of electrical equipment above. However, to allow for early design requirements, it is recommended that the following equipment items are also considered for inclusion: IfcBoilerType IfcChillerType IfcCompressorType IfcCondensorType IfcCoolingTowerType IfcDamperType IfcEvaporativeCoolerType IfcEvaporatorType IfcFanType IfcFilterType IfcHeatExchangerType IfcHumidifierType IfcPumpType IfcSanitaryTerminalType IfcSpaceHeaterType IfcValveType Set the specific type of the equipment being used (floor, roof, landing etc.) Ifc<Functional>Type.PredefinedType If the value of the predefined type identifier is set to USERDEFINED, then establish the value that the user wishes to set. IfcElementType.ElementType

131 Model Electrical Equipment (FP) - Confluence 5 af :31 Generally, the shape representation of equipment will be defined as a representation map which is assigned to the type. This is so that the shape representation for the distribution equipment type is defined once but can be used by multiple occurrences of the same type. fp_map_representation Provision of a representation map is normally optional within the model but should be asserted for building model exchange. Equipment can also be directly modeled as occurrences without having to specify a type. However, it is not recommended that this approach is used. Assert general attributes for the type Set the global unique identifier Ifc<Functional>Type.GlobalId::IfcGloballyUniqueId Assert the owner history of the equipment type Ifc<Functional>Type.OwnerHistory::fp_apply_owner_history Specify a name of the equipment type Ifc<Functional>Type.Name Specify a description of the equipment type Ifc<Functional>Type.Description Model the equipment occurrence Establish the placement of the origin fp_place_object

132 Model Electrical Equipment (FP) - Confluence 6 af :31 point of the equipment occurrence Define the shape representation for the equipment occurrence Note that an equipment occurrence may have several representations. These are contained in the representation map which is represented as a mapped item for the occurrence. fp_represent_product Establish Properties For each equipment type, the value of type properties within property sets may be defined. Information on relevant property sets for the various types is given in the extension tables below. For each equipment occurrence, the value of occurrence properties within property sets may be defined. Information on relevant property sets for the various occurrences is given in the extension tables below. Define type and occurrence Define the type of equipment to which the equipment occurrence conforms fp_define_by_type

133 Model Electrical Equipment (FP) - Confluence 7 af :31 Refer to the list given in the Overview section for further information. Define the property set for the equipment occurrence fp_define_by_properties Assert general attributes for the occurrence Set the global unique identifier Ifc<Occurrence>.GlobalId::IfcGloballyUniqueId Assert the owner history of the equipment occurrence Ifc<Occurrence>.OwnerHistory::fp_apply_owner_history Set a name to the equipment occurrence Ifc<Occurrence>.Name::IfcLabel Provide a description of the equipment occurrence Ifc<Occurrence>.Description::IfcText Extend occurrence information Define the material from which the equipment is constructed fp_associate_material Add information about the weight of the equipment occurrence according to the particular method of measurement applied in the local usage. fp_apply_quantity[weight]

134 Model Electrical Equipment (FP) - Confluence 8 af :31 Classify the equipment occurrence according to the selected classification approach fp_associate_classification IFC Entities Required IfcDistributionElement IfcDistributionElementType IfcDistributionFlowElement IfcDistributionFlowElementType IfcElectricApplianceType IfcElectricFlowStorageDeviceType IfcElectricGeneratorType IfcElectricHeaterType IfcElectricMotorType IfcElectricTimeControlType IfcElement IfcElementType IfcEnergyConversionDevice IfcEnergyConversionDeviceType IfcFlowController IfcFlowControllerType IfcFlowMeterType IfcFlowStorageDevice IfcFlowStorageDeviceType IfcFlowTerminal IfcFlowTerminalType IfcLightFixtureType IfcObject IfcOutletType? IfcProduct IfcPropertyDefinition IfcPropertySetDefinition IfcPropertySet IfcProtectiveDeviceType IfcRoot IfcSwitchingDeviceType IfcTransformerType

135 Model Electrical Equipment (FP) - Confluence 9 af :31 IfcTypeObject IfcTypeProduct IFC Datatypes Required IfcGloballyUniqueId IfcIdentifier IfcLabel IfcText IfcElectricApplianceTypeEnum IfcElectricFlowStorageDeviceTypeEnum IfcElectricGeneratorTypeEnum IfcElectricHeaterTypeEnum IfcElectricMotorTypeEnum IfcElectricTimeControlTypeEnum IfcFlowMeterTypeEnum IfcLightFixtureTypeEnum IfcOutletTypeEnum IfcProtectiveDeviceTypeEnum IfcSwitchingDeviceTypeEnum IfcTransformerTypeEnum IFC Functions Required - IFC Property Sets Required - IDM Functional Parts Required fp_apply_owner_history fp_define_by_type fp_define_by_properties fp_map_representation fp_place_object fp_property fp_represent_product

136 Model Electrical Equipment (FP) - Confluence 10 af :31 EXPRESS Schema SCHEMA FP_MODEL_ELECTRICAL_EQUIPMENT; TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcIdentifier = STRING; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcElectricApplianceTypeEnum = ENUMERATION OF (COMPUTER, DIRECTWATERHEATER, DISHWASHER, ELECTRICCOOKER, ELECTRICHEATER, FACSIMILE, FREESTANDINGFAN, FREEZER, FRIDGE_FREEZER, HANDDRYER, INDIRECTWATERHEATER, MICROWAVE, PHOTOCOPIER, PRINTER, REFRIGERATOR, RADIANTHEATER, SCANNER, TELEPHONE, TUMBLEDRYER, TV, VENDINGMACHINE, WASHINGMACHINE, WATERHEATER, WATERCOOLER, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcElectricFlowStorageDeviceTypeEnum = ENUMERATION OF (BATTERY, CAPACITORBANK, HARMONICFILTER, INDUCTORBANK,

137 Model Electrical Equipment (FP) - Confluence 11 af :31 UPS, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcElectricGeneratorTypeEnum = ENUMERATION OF (USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcElectricHeaterTypeEnum = ENUMERATION OF (ELECTRICPOINTHEATER, ELECTRICCABLEHEATER, ELECTRICMATHEATER, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcElectricMotorTypeEnum = ENUMERATION OF (DC, INDUCTION, POLYPHASE, RELUCTANCESYNCHRONOUS, SYNCHRONOUS, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcElectricTimeControlTypeEnum = ENUMERATION OF (TIMECLOCK, TIMEDELAY, RELAY, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcFlowMeterTypeEnum = ENUMERATION OF (ELECTRICMETER, ENERGYMETER, FLOWMETER, GASMETER, OILMETER, WATERMETER, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcLightFixtureTypeEnum = ENUMERATION OF (POINTSOURCE, DIRECTIONSOURCE, USERDEFINED, NOTDEFINED);

138 Model Electrical Equipment (FP) - Confluence 12 af :31 END_TYPE; TYPE IfcOutletTypeEnum = ENUMERATION OF (AUDIOVISUALOUTLET, COMMUNICATIONSOUTLET, POWEROUTLET, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcProtectiveDeviceTypeEnum = ENUMERATION OF (FUSEDISCONNECTOR, CIRCUITBREAKER, EARTHFAILUREDEVICE, RESIDUALCURRENTCIRCUITBREAKER, RESIDUALCURRENTSWITCH, VARISTOR, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcSwitchingDeviceTypeEnum = ENUMERATION OF (CONTACTOR, EMERGENCYSTOP, STARTER, SWITCHDISCONNECTOR, TOGGLESWITCH, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcTransformerTypeEnum = ENUMERATION OF (CURRENT, FREQUENCY, VOLTAGE, USERDEFINED, NOTDEFINED); END_TYPE; ENTITY IfcProduct ABSTRACT SUPERTYPE SUBTYPE OF(IfcObject); ObjectPlacement : OPTIONAL fp_place_object; Representation : OPTIONAL fp_represent_product; WHERE WR1 : (EXISTS(Representation) AND EXISTS(ObjectPlacement)) OR (EXISTS(Representation) AND (NOT('IFC2X2_FINAL.IFCPRODUCTDEFINITIONSHAPE' IN TYPEOF(Representation)))) OR (NOT(EXISTS(Representation))); ENTITY IfcObject

139 Model Electrical Equipment (FP) - Confluence 13 af :31 ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ObjectType : OPTIONAL IfcLabel; WHERE WR1 : SIZEOF(QUERY(temp <* IsDefinedBy 'IFC2X2_FINAL.IFCRELDEFINESBYTYPE' IN TYPEOF(temp))) <= 1; ENTITY IfcRoot ABSTRACT SUPERTYPE OF (ONEOF(IfcObject, IfcPropertyDefinition)); GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId; ENTITY IfcPropertyDefinition ABSTRACT SUPERTYPE OF (ONEOF(IfcPropertySetDefinition, IfcTypeObject)) SUBTYPE OF(IfcRoot); ENTITY IfcPropertySetDefinition ABSTRACT SUPERTYPE SUBTYPE OF(IfcPropertyDefinition); INVERSE DefinesType : SET [0:1] OF IfcTypeObject FOR HasPropertySets; ENTITY IfcPropertySet SUBTYPE OF(IfcPropertySetDefinition); HasProperties : SET [1:?] OF fp_property; WHERE WR31 : EXISTS(SELF\IfcRoot.Name); WR32 : IfcUniquePropertyName(HasProperties); ENTITY IfcElement ABSTRACT SUPERTYPE SUBTYPE OF(IfcProduct); Tag : OPTIONAL IfcIdentifier; ENTITY IfcDistributionElement SUBTYPE OF(IfcElement); ENTITY IfcDistributionFlowElement SUPERTYPE OF (ONEOF(IfcEnergyConversionDevice, IfcFlowController, IfcFlowStorageDevice, IfcFlowTerminal)) SUBTYPE OF(IfcDistributionElement);

140 Model Electrical Equipment (FP) - Confluence 14 af :31 ENTITY IfcEnergyConversionDevice SUBTYPE OF(IfcDistributionFlowElement); ENTITY IfcFlowController SUBTYPE OF(IfcDistributionFlowElement); ENTITY IfcFlowStorageDevice SUBTYPE OF(IfcDistributionFlowElement); ENTITY IfcFlowTerminal SUBTYPE OF(IfcDistributionFlowElement); ENTITY IfcTypeObject SUBTYPE OF(IfcPropertyDefinition); ApplicableOccurrence : OPTIONAL IfcLabel; HasPropertySets : OPTIONAL LIST [1:?] OF IfcPropertySetDefinition; WHERE WR1 : EXISTS(SELF\IfcRoot.Name); ENTITY IfcTypeProduct SUBTYPE OF(IfcTypeObject); Tag : OPTIONAL IfcLabel; RepresentationMaps : OPTIONAL SET [1:?] OF fp_map_representation; WHERE WR41 : NOT(EXISTS(SELF\IfcTypeObject.ObjectTypeOf[1])) OR (SIZEOF(QUERY(temp <* SELF\IfcTypeObject.ObjectTypeOf[1].RelatedObjects NOT('IFC2X2_FINAL.IFCPRODUCT' IN TYPEOF(temp))) ) = 0); ENTITY IfcElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcTypeProduct); ElementType : OPTIONAL IfcLabel; ENTITY IfcDistributionElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcElementType); ENTITY IfcDistributionFlowElementType ABSTRACT SUPERTYPE OF (ONEOF(IfcEnergyConversionDeviceType, IfcFlowControllerType, IfcFlowStorageDeviceType, IfcFlowTerminalType)) SUBTYPE OF(IfcDistributionElementType); ENTITY IfcEnergyConversionDeviceType

141 Model Electrical Equipment (FP) - Confluence 15 af :31 ABSTRACT SUPERTYPE OF (ONEOF(IfcElectricGeneratorType, IfcElectricMotorType, IfcTransformerType)) SUBTYPE OF(IfcDistributionFlowElementType); ENTITY IfcElectricGeneratorType SUBTYPE OF(IfcEnergyConversionDeviceType); PredefinedType : IfcElectricGeneratorTypeEnum; ENTITY IfcElectricMotorType SUBTYPE OF(IfcEnergyConversionDeviceType); PredefinedType : IfcElectricMotorTypeEnum; ENTITY IfcTransformerType SUBTYPE OF(IfcEnergyConversionDeviceType); PredefinedType : IfcTransformerTypeEnum; ENTITY IfcFlowControllerType ABSTRACT SUPERTYPE OF (ONEOF(IfcElectricTimeControlType, IfcFlowMeterType, IfcProtectiveDeviceType, IfcSwitchingDeviceType)) SUBTYPE OF(IfcDistributionFlowElementType); ENTITY IfcElectricTimeControlType SUBTYPE OF(IfcFlowControllerType); PredefinedType : IfcElectricTimeControlTypeEnum; ENTITY IfcFlowMeterType SUBTYPE OF(IfcFlowControllerType); PredefinedType : IfcFlowMeterTypeEnum; ENTITY IfcProtectiveDeviceType SUBTYPE OF(IfcFlowControllerType); PredefinedType : IfcProtectiveDeviceTypeEnum; ENTITY IfcSwitchingDeviceType SUBTYPE OF(IfcFlowControllerType); PredefinedType : IfcSwitchingDeviceTypeEnum; ENTITY IfcFlowStorageDeviceType ABSTRACT SUPERTYPE SUBTYPE OF(IfcDistributionFlowElementType); ENTITY IfcElectricFlowStorageDeviceType SUBTYPE OF(IfcFlowStorageDeviceType); PredefinedType : IfcElectricFlowStorageDeviceTypeEnum;

142 Model Electrical Equipment (FP) - Confluence 16 af :31 ENTITY IfcFlowTerminalType ABSTRACT SUPERTYPE OF (ONEOF(IfcElectricApplianceType, IfcElectricHeaterType, IfcLampType, IfcLightFixtureType, IfcOutletType)) SUBTYPE OF(IfcDistributionFlowElementType); ENTITY IfcElectricApplianceType SUBTYPE OF(IfcFlowTerminalType); PredefinedType : IfcElectricApplianceTypeEnum; ENTITY IfcElectricHeaterType SUBTYPE OF(IfcFlowTerminalType); PredefinedType : IfcElectricHeaterTypeEnum; ENTITY IfcLightFixtureType SUBTYPE OF(IfcFlowTerminalType); PredefinedType : IfcLightFixtureTypeEnum; ENTITY IfcOutletType SUBTYPE OF(IfcFlowTerminalType); PredefinedType : IfcOutletTypeEnum; ENTITY fp_apply_owner_history; ENTITY fp_map_representation; ENTITY fp_place_object; ENTITY fp_represent_product; ENTITY fp_property; ENTITY fp_define_by_type; ENTITY fp_define_by_properties; END_SCHEMA;

143 Model Electrical Equipment (FP) - Confluence 17 af :31 Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

144 Model Flow Fitting (FP) - Confluence 1 af :28 Information Delivery Manual (IDM) Added by Brendan McFarlane, last edited by Brendan McFarlane on Sep 15, 2006 (view change) Labels: (None)

145 Model Flow Fitting (FP) - Confluence 2 af :28 Provides the information concerning flow fittings. A flow fitting is an element of a distribution system at which there is a change in the flow characteristics of the medium being distributed. A flow fitting may have one or more entry ports and one or more exit ports. All flow fittings are types of flow element (IfcDistributionFlowElement) within the IFC model. The types of fitting contained within IFC include: Service Cable transport Communications systems Controls systems Electrical systems Oil/gas systems Water systems Ventilation systems IfcFlowSegmentType subtype IfcCableCarrierFittingType IfcCableFittingType IfcCableFittingType IfcCableFittingType IfcPipeFittingType IfcPipeFittingType IfcDuctFittingType The information presented in this functional part enables: extension of a basic building model through the provision of size and location information provision of weight information for the structural engineer provision of performance information for analysis This information includes: Specification of fitting name and description if required Shape representations of the fitting Identification of the type to which a fitting occurrence conforms The material from which the fitting is constructed In addition, performance information for occurrences of fittings of particular types as indicated in the list above may be provided. Specification of the performance information that may be required is given in the tables below. Note that the particular type of fitting to be used, and that therefore defines the performance information requirement, can be set as a parameter in the exchange requirement by:

146 Model Flow Fitting (FP) - Confluence 3 af :28 fp_model_flow_fitting \[type, {predefined_type}\] For instance, for a pipe fitting, reference to the relevant items within this functional part from the exchange requirement would be by specifying: fp_model_flow_fitting \[Pipe, Bend\] Results Model of flow fitting occurrence(s) including shape representation and other basic information Model the fitting type Description Entity/Pset/Functional Part MAN REC OPT Select the type of fitting to be modeled The following are the selections available within the model. Each of these is a functional subtype of IfcFlowFittingType (as shown in the Overview list). Further reference generally to these types is shown below as Ifc<Functional>Type. IfcCableCarrierFittingType IfcDuctFittingType IfcPipeFittingType Set the specific type of the fitting being used Ifc<Functional>Type.PredefinedType If the value of the predefined type identifier is set to USERDEFINED, then establish the value that the user wishes to set. Generally, the shape representation of equipment will be defined as a representation map which is assigned to the type. This is so that the shape representation for the equipment type is defined once but can be used by multiple occurrences of the same type. Provision of a representation map is normally optional within the model but should be asserted for building model exchange. IfcElementType.ElementType fp_map_representation NOTE Equipment can also be directly modeled as occurrences without having to specify a type. However, it is not recommended that this approach is used. Assert general attributes for the type

147 Model Flow Fitting (FP) - Confluence 4 af :28 Set the global unique identifier Ifc<Functional>Type.GlobalId -> IfcGloballyUniqueId Assert the owner history of the fitting type Ifc<Functional>Type.OwnerHistory -> fp_apply_owner_history Specify a name of the fitting type Ifc<Functional>Type.Name -> IfcLabel Specify a description of the fitting type Ifc<Functional>Type.Description -> IfcText Model the fitting occurrence Establish the placement of the origin point of the fitting occurrence Ifc<Occurrence>.ObjectPlacement -> fp_place_object Define the shape representation for the fitting occurrence Note that an equipment occurrence may have several representations. These are contained in the representation map which is represented as a mapped item for the occurrence. Ifc<Occurrence>.Representation -> fp_represent_product Establish Properties For each fitting type, the value of type properties within property sets may be defined. Information on relevant property sets for the various types is given in the extension tables below. For each fitting occurrence, the value of occurrence properties within property sets may be defined. Information on relevant property sets for the various occurrences is given in the extension tables below. fp_property fp_property Define type and occurrence Define the type of fitting to which the fitting occurrence conforms Refer to the list given in the Overview section for further information. fp_define_by_type Define the property set for the fitting occurrence fp_define_by_properties Assert general attributes for the occurrence Set the global unique identifier Ifc<Occurrence>.GlobalId -> IfcGloballyUniqueId Assert the owner history of the fitting occurrence Ifc<Occurrence>.OwnerHistory -> fp_apply_owner_history Set a name to the fitting occurrence Ifc<Occurrence>.Name -> IfcLabel Provide a description of the fitting occurrence Ifc<Occurrence>.Description -> IfcText

148 Model Flow Fitting (FP) - Confluence 5 af :28 Extend occurrence information Define the material from which the fitting is constructed fp_associate_material Classify the fitting occurrence according to the selected classification approach fp_associate_classification Description Entity/Pset/Functional Part MAN REC OPT For duct fittings Set the following values within the property set Pset_DuctFittingTypeCommon IfcDuctFittingType (ALL TYPES) Subtype of fitting (i.e., 5-gore, pleated, stamped, etc.) Pset_DuctFittingTypeCommon.Subtype -> IfcText Material from which the duct fitting is constructed. Note that this property may be used if the material is not associated with that segment through the functional part fp_associates_material. The thickness of the duct fitting material Only applicable if the material is not separately asserted. Pressure classification as defined by the authority having jurisdiction (e.g., SMACNA, etc.). Weight per unit length. Only applicable if the weight is not separately defined through fp_apply_quantity[weight] Allowable maximum and minimum working pressure (relative to ambient pressure). Allowable maximum and minimum temperature. The nominal width or diameter (if circular) of a duct fitting or, in the case of a circular cross section, the diameter. The nominal height of the fitting. The end-style treatment of the duct fitting manufactured. If the list contains only one value, then this end-style applies to all ports. For more than one value in the list, the end-style value applies to the port that corresponds to the list index. The following suggested items should be utilized whenever possible for correlation with port enumerations: ANGLE BEADEDSLEEVE Pset_DuctFittingTypeCommon.Material -> IfcMaterial Pset_DuctFittingTypeCommon.MaterialThickness -> IfcPositiveLengthMeasure Pset_DuctFittingTypeCommon.PressureClass -> IfcPressureMeasure Pset_DuctFittingTypeCommon.UnitWeight -> IfcMassPerLengthMeasure Pset_DuctFittingTypeCommon.PressureRange -> IfcPressureMeasure Pset_DuctFittingTypeCommon.TemperatureRange -> IfcThermodynamicTemperatureMeasure Pset_DuctFittingTypeCommon.NominalDiameterOrWidth -> IfcPositiveLengthMeasure Pset_DuctFittingTypeCommonNominalHeight -> IfcPositiveLengthMeasure Pset_DuctFittingTypeCommon.EndStyleTreatment -> IfcText

149 Model Flow Fitting (FP) - Confluence 6 af :28 BRAZED COMPRESSION CRIMP DRAWBAND DRIVESLIP FLANGED OUTSIDESLEEVE SLIPON SOLDERED SSLIP STANDINGSEAM SWEDGE WELDED NONE Description Entity/Pset/Functional Part MAN REC OPT For pipe fittings Set the following values within the property set Pset_PipeFittingTypeCommon Subtype of fitting The following suggested items should be utilized whenever possible for consistency across applications: BEND_15DEGREE Changes the direction of flow through 15 degrees. BEND_22_5DEGREE Changes the direction of flow through 22.5 degrees. BEND_25DEGREE Changes the direction of flow through 25 degrees. BEND_30DEGREE Changes the direction of flow through 30 degrees. BEND_45DEGREE Changes the direction of flow through 45 degrees. BEND_67DEGREE Changes the direction of flow through 67 degrees. BEND_76DEGREE Changes the direction of flow through 76 degrees. BEND_87_5DEGREE Changes the direction of flow through 87.5 degrees. BEND_90DEGREE Changes the direction of flow through 90 degrees. IfcPipeFittingType (ALL TYPES) Pset_PipeFittingTypeCommon.Subtype -> IfcText

150 Model Flow Fitting (FP) - Confluence 7 af :28 BEND_135DEGREE Changes the direction of flow through 135 degrees. BEND_180DEGREE Changes the direction of flow through 180 degrees. JUNCTION_CROSS_SQUARE Branch fitting with two opposing branches that are swept in the direction of the main flow. JUNCTION_CROSS_SWEEP Branch fitting with two swept opposing branches at right angles to the main flow. JUNCTION_TEE_SQUARE Branch fitting in which the branch is at an angle of 90 degrees to the main pipe. JUNCTION_TEE_SWEEP Branch fitting in which the branch is curved through 90 degrees to join a main pipe tangentially. JUNCTION_TEE_TWINBEND Symmetrical pipe fitting in which two short radius bends curve through 90 degree to form a single pipe. JUNCTION_TEE_TWINELBOW Symmetrical pipe fitting in which two elbows curve through 90 degree to form a single pipe. JUNCTION_TEE_Y Branch fitting in the shape of a letter Y. OBSTRUCTION_CAP Device fixed onto the end of a pipe or pipe fitting to close it. OBSTRUCTION_PLUG Device fixed into the end of a pipe or pipe fitting to close it. Material from which the pipe fitting is constructed. Note that this property may be used if the material is not associated with that fitting through the functional part fp_associates_material. Pset_PipeFittingTypeCommon.Material -> IfcMaterial The working pressure of the medium in the pipe Pset_PipeFittingTypeCommon.PressureClass -> IfcPressureMeasure Weight per unit length. Only applicable if the weight is not separately defined through fp_apply_quantity[weight] Allowable maximum and minimum working pressure (relative to ambient pressure). Pset_PipeFittingTypeCommon.UnitWeight -> IfcMassPerLengthMeasure Pset_PipeFittingTypeCommon.PressureRange -> IfcPressureMeasure

151 Model Flow Fitting (FP) - Confluence 8 af :28 Allowable maximum and minimum temperature. The nominal diameter of the pipe fitting. If the list contains only one value, then this nominal diameter applies to all ports. For more than value in the list, the nominal diameter value applies to the port that corresponds to the list index The actual inner diameter of the pipe. Refer to NominalDiameter for comments about interpretation of multiple items in the list. The actual outer diameter of the pipe. Refer to NominalDiameter for comments about interpretation of multiple items in the list. The end-style treatment of the pipe fitting manufactured. If the list contains only one value, then this end-style applies to all ports. For more than one value in the list, the end-style value applies to the port that corresponds to the list index. The following suggested items should be utilized whenever possible for correlation with port enumerations: FLANGED GROOVED THREADED NONE The factor that determines the pressure loss due to friction through the fitting. Pset_PipeFittingTypeCommon.TemperatureRange Pset_DuctFittingTypeCommon.TemperatureRange -> IfcThermodynamicTemperatureMeasure Pset_PipeFittingTypeCommon.NominalDiameter -> IfcPositiveLengthMeasure Pset_PipeFittingTypeCommon.InnerDiameter -> IfcPositiveLengthMeasure Pset_PipeFittingTypeCommon.OuterDiameter -> IfcPositiveLengthMeasure Pset_PipeFittingTypeCommon.EndStyleTreatment -> IfcText Pset_PipeFittingTypeCommon.FittingLossFactor -> IfcReal Description Entity/Pset /Functional Part MAN REC OPT For cable carrier fittings Cable carriers are conduit, ladder, tray and trunking and have properties defined as below. No specific property sets are developed for cable carrier fittings at this stage. All properties of such fittings should be derived from the cable carrier segments to which they are connected. IFC Entities Required IfcCableCarrierFittingType IfcCableFittingType IfcDistributionElement

152 Model Flow Fitting (FP) - Confluence 9 af :28 IfcDistributionElementType IfcDistributionFlowElement IfcDistributionFlowElementType IfcDuctFittingType IfcElement IfcElementType IfcFlowSegment IfcFlowSegmentType IfcObject IfcPipeFittingType IfcProduct IfcPropertyDefinition IfcPropertySetDefinition IfcPropertySet IfcRoot IfcTypeObject IfcTypeProduct IFC Datatypes Required IfcGloballyUniqueId IfcIdentifier IfcLabel IfcText IfcCableCarrierFittingTypeEnum IfcCableFittingTypeEnum IfcDuctFittingTypeEnum IfcPipeFittingTypeEnum IFC Functions Required - IFC Property Sets Required Pset_DuctFittingTypeCommon Pset_PipeFittingTypeCommon IDM Functional Parts Required fp_apply_owner_history fp_assigns_to_group

153 Model Flow Fitting (FP) - Confluence 10 af :28 fp_connects_ports fp_define_by_properties fp_define_by_type fp_map_representation fp_place_object fp_property fp_represent_product EXPRESS-G

154 Model Flow Fitting (FP) - Confluence 11 af :28 EXPRESS Schema SCHEMA FP_MODEL_FLOW_FITTING;

155 Model Flow Fitting (FP) - Confluence 12 af :28 TYPE IfcGloballyUniqueId = STRING (22) FIXED; END_TYPE; TYPE IfcIdentifier = STRING; END_TYPE; TYPE IfcLabel = STRING; END_TYPE; TYPE IfcText = STRING; END_TYPE; TYPE IfcCableCarrierFittingTypeEnum = ENUMERATION OF (BEND, CROSS, REDUCER, TEE, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcDuctFittingTypeEnum = ENUMERATION OF (BEND, CONNECTOR, ENTRY, EXIT, JUNCTION, OBSTRUCTION, TRANSITION, USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcJunctionBoxTypeEnum = ENUMERATION OF (USERDEFINED, NOTDEFINED); END_TYPE; TYPE IfcPipeFittingTypeEnum = ENUMERATION OF (BEND, CONNECTOR, ENTRY, EXIT, JUNCTION, OBSTRUCTION, TRANSITION, USERDEFINED, NOTDEFINED); END_TYPE; ENTITY IfcProduct

156 Model Flow Fitting (FP) - Confluence 13 af :28 ABSTRACT SUPERTYPE SUBTYPE OF(IfcObject); ObjectPlacement : OPTIONAL fp_place_object; Representation : OPTIONAL fp_represent_product; WHERE WR1 : (EXISTS(Representation) AND EXISTS(ObjectPlacement)) OR (EXISTS(Representation) AND (NOT('IFC2X2_FINAL.IFCPRODUCTDEFINITIONSHAPE' IN TYPEOF(Representation)))) OR (NOT(EXISTS(Representation))); ENTITY IfcObject ABSTRACT SUPERTYPE SUBTYPE OF(IfcRoot); ObjectType : OPTIONAL IfcLabel; WHERE WR1 : SIZEOF(QUERY(temp <* IsDefinedBy 'IFC2X2_FINAL.IFCRELDEFINESBYTYPE' IN TYPEOF(temp))) <= 1; ENTITY IfcRoot ABSTRACT SUPERTYPE OF (ONEOF(IfcObject, IfcPropertyDefinition)); GlobalId : IfcGloballyUniqueId; Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; OwnerHistory : fp_apply_owner_history; UNIQUE UR1 : GlobalId; ENTITY IfcPropertyDefinition ABSTRACT SUPERTYPE OF (ONEOF(IfcPropertySetDefinition, IfcTypeObject)) SUBTYPE OF(IfcRoot); ENTITY IfcPropertySetDefinition ABSTRACT SUPERTYPE SUBTYPE OF(IfcPropertyDefinition); INVERSE DefinesType : SET [0:1] OF IfcTypeObject FOR HasPropertySets; ENTITY IfcPropertySet SUBTYPE OF(IfcPropertySetDefinition); HasProperties : SET [1:?] OF fp_property; WHERE WR31 : EXISTS(SELF\IfcRoot.Name); WR32 : IfcUniquePropertyName(HasProperties); ENTITY fp_property;

157 Model Flow Fitting (FP) - Confluence 14 af :28 ENTITY IfcTypeObject SUBTYPE OF(IfcPropertyDefinition); ApplicableOccurrence : OPTIONAL IfcLabel; HasPropertySets : OPTIONAL LIST [1:?] OF IfcPropertySetDefinition; WHERE WR1 : EXISTS(SELF\IfcRoot.Name); ENTITY IfcTypeProduct SUBTYPE OF(IfcTypeObject); Tag : OPTIONAL IfcLabel; RepresentationMaps : SET [1:?] OF fp_map_representation; WHERE WR41 : NOT(EXISTS(SELF\IfcTypeObject.ObjectTypeOf[1])) OR (SIZEOF(QUERY(temp <* SELF\IfcTypeObject.ObjectTypeOf[1].RelatedObjects NOT('IFC2X2_FINAL.IFCPRODUCT' IN TYPEOF(temp))) ) = 0); ENTITY IfcElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcTypeProduct); ElementType : OPTIONAL IfcLabel; ENTITY IfcDistributionElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcElementType); ENTITY IfcDistributionFlowElementType ABSTRACT SUPERTYPE SUBTYPE OF(IfcDistributionElementType); ENTITY IfcFlowFittingType ABSTRACT SUPERTYPE OF (ONEOF(IfcCableCarrierFittingType, IfcDuctFittingType, IfcJunctionBoxType, IfcPipeFittingType)) SUBTYPE OF(IfcDistributionFlowElementType); ENTITY IfcCableCarrierFittingType SUBTYPE OF(IfcFlowFittingType); PredefinedType : IfcCableCarrierFittingTypeEnum; WHERE WR1 : (PredefinedType <> IfcCableCarrierFittingTypeEnum.USERDEFINED) OR ((PredefinedType = IfcCableCarrierFittingTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcElementType.ElementType)); ENTITY IfcDuctFittingType SUBTYPE OF(IfcFlowFittingType); PredefinedType : IfcDuctFittingTypeEnum; WHERE

158 Model Flow Fitting (FP) - Confluence 15 af :28 WR2 : (PredefinedType <> IfcDuctFittingTypeEnum.USERDEFINED) OR ((PredefinedType = IfcDuctFittingTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcObject.ObjectType)); ENTITY IfcJunctionBoxType SUBTYPE OF(IfcFlowFittingType); PredefinedType : IfcJunctionBoxTypeEnum; ENTITY IfcPipeFittingType SUBTYPE OF(IfcFlowFittingType); PredefinedType : IfcPipeFittingTypeEnum; WHERE WR1 : (PredefinedType <> IfcPipeFittingTypeEnum.USERDEFINED) OR ((PredefinedType = IfcPipeFittingTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcObject.ObjectType)); ENTITY fp_map_representation; ENTITY fp_apply_owner_history; ENTITY IfcElement ABSTRACT SUPERTYPE SUBTYPE OF(IfcProduct); Tag : OPTIONAL IfcIdentifier; ENTITY IfcDistributionElement SUBTYPE OF(IfcElement); ENTITY IfcDistributionFlowElement SUBTYPE OF(IfcDistributionElement); ENTITY IfcFlowFitting SUBTYPE OF(IfcDistributionFlowElement); ENTITY fp_place_object; ENTITY fp_represent_product; ENTITY fp_define_by_type; ENTITY fp_define_by_properties;

159 Model Flow Fitting (FP) - Confluence 16 af :28 ENTITY fp_connect_ports; ENTITY fp_assigns_to_group; END_SCHEMA; Powered by Atlassian Confluence, the Enterprise Wiki. (Version: Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators

160 Model Flow Segment (FP) - Confluence 1 af :29 Information Delivery Manual (IDM) Added by Brendan McFarlane, last edited by Jeffrey Wix on Sep 15, 2006 (view change) Labels: (None)

161 Model Flow Segment (FP) - Confluence 2 af :29 Provides the information concerning flow segments. A flow segment is an element of a distribution system in which there is a single port at which the medium being distributed enters the segment and a single port at which the medium leaves the segment. The sole purpose of a flow segment is to enable the medium being distributed to pass from the entry port to the exit port. It is typically contiguous (i.e. there are no breaks along its length) and straight (although the path of a flow segment may be a curve rather than a straight line). In certain cases, this last definition of flow along a curved path may mean that a decision needs to be taken regarding whether an element is a flow segment or a flow fitting. This is a decision that must be taken by the user. All flow segments are types of flow element (IfcDistributionFlowElement) within the IFC model. The types of segment contained within IFC include: Service Cable transport Communications systems Controls systems Electrical systems Oil/gas systems Water systems Ventilation systems IfcFlowSegmentType subtype IfcCableCarrierSegmentType IfcCableSegmentType IfcCableSegmentType IfcCableSegmentType IfcPipeSegmentType IfcPipeSegmentType IfcDuctSegmentType The information presented in this functional part enables: extension of a basic building model through the provision of size and location information provision of weight information for the structural engineer provision of performance information for analysis This information includes: Specification of segment name and description if required Shape representations of the segment Identification of the type to which a segment occurrence conforms The material from which the segment is constructed The weight of the equipment In addition, performance information for occurrences of segments of particular types as indicated in the list above may be provided. Note that the particular type of segment to be used, and that therefore defines the performance information requirement, can be set as a parameter in the exchange

162 Model Flow Segment (FP) - Confluence 3 af :29 requirement by: fp_model_flow_segment [type, {predefined_type}] For instance, for a cable segment, reference to the relevant items within this functional part from the exchange requirement would be by specifying: fp_model_flow_segment [Cable, Conductor] Results Model of flow segment occurrence(s) including shape representation and other basic information Model the segment type Description Entity/Pset/Functional Part MAN REC OPT Select the type of segment to be modeled The following are the selections available within the model. Each of these is a functional subtype of IfcFlowSegmentType (as shown in the Overview list). Further reference generally to these types is shown below as Ifc<Functional>Type. IfcCableSegmentType IfcCableCarrierSegmentType IfcDuctSegmentType IfcPipeSegmentType Set the specific type of the segment being used Ifc<Functional>Type.PredefinedType If the value of the predefined type identifier is set to USERDEFINED, then establish the value that the user wishes to set. In certain cases, the shape representation may be be a representation map assigned to the segment type in which case the representation map will be created using one or more of the shape representations given for the segment occurrence below. This is for cases where the shape representation for the segment type may be defined once and used by multiple occurrences of the same type. IfcElementType.ElementType fp_map_representation Assert general attributes for the type

163 Model Flow Segment (FP) - Confluence 4 af :29 Set the global unique identifier Ifc<Functional>Type.GlobalId à IfcGloballyUniqueId Assert the owner history of the equipment type Ifc<Functional>Type.OwnerHistory à fp_apply_owner_history Specify a name of the segment type Ifc<Functional>Type.Name Specify a description of the segment type Ifc<Functional>Type.Description Model the segment occurrence Establish the placement of the origin point of the segment occurrence Generally, the shape representation of a segment will be defined for the occurrence rather than the type. Various forms of shape representation are possible and an occurrence may have several shape representations. In determining which shape representations should be supported for a flow segment, it is important to be aware of the capabilities of any system which may expect to receive and use shape representations provided. This is to ensure that the shape representation(s) given are supported by receiving systems. Axis Representation The segment axis is represented by a two-dimensional open curve. The segment axis is used to apply the segment length parameter to the segment geometry. In case of a straight segment, the set of items shall include a single geometric representation item of type IfcPolyline. In the case of a curved segment, the set of items shall include a single geometric representation item of type IfcTrimmedCurve. The curve shall have a BasisCurve of type IfcCircle. Body Representation The body of the IfcFlowSegment may be defined using SweptSolid representation for segments without clippings. fp_place_object fp_represent_product Use the following attribute values: IfcShapeRepresentation.RepresentationIdentifier à 'Axis' IfcShapeRepresentation.RepresentationType à 'GeometricSet' Use the following attribute values: IfcShapeRepresentation.RepresentationIdentifier à 'Body' IfcShapeRepresentation.RepresentationType à 'SweptSolid' The standard geometric representation (for body) of IfcFlowSegment is defined using the swept solid representation. The following additional constraints apply to the swept solid representation: Solid: IfcExtrudedAreaSolid is required, Profile: IfcArbitraryProfileDef shall be supported.

164 Model Flow Segment (FP) - Confluence 5 af :29 Extrusion: The profile shall be extruded along the segment axis, i.e., in the direction of the x-axis of the coordinate system of local placement. The extrusion axis shall be perpendicular to the swept profile, i.e. pointing into the direction of the x-axis of the Position of the IfcExtrudedAreaSolid. The profile of a segment is described in plane perpendicular to the extrusion axis. The profile is defined by the IfcArbitraryProfileDef (excluding its subtypes). The profile is given with all segment connections already resolved and is always perpendicular to the segment axis. The segment also has a single, unchanged profile. Body Representation The body of the IfcFlowSegment may be defined using CSG representation for segments with clippings. Body Representation The body of the IfcFlowSegment may be defined using a bounding box. B-Rep Representation The solid representation of the IfcFlowSegment may be defined using a boundary representation. The faceted B-Rep capabilities (with or without voids) shall be supported for B-Rep representation. Logical Representation Whilst not properly a shape representation, a logical connection may be made between certain elements using one or more realizing elements that do not have a shape represent but that need to be asserted with a logical representation. This is particularly relevant for cable segments between electrical devices. Use the following attribute values: IfcShapeRepresentation.RepresentationIdentifier à 'Body' IfcShapeRepresentation.RepresentationType à 'CSG' The advanced geometric representation (for body) of IfcFlowSegment is defined using the CSG representation. The following additional constraints apply to the swept solid representation: Solid: see body representation above Profile: see body representation above Extrusion: see body representation above Boolean result: IfcBooleanClippingResult shall be supported, allowing for Boolean differences between the swept solid (here IfcExtrudedAreaSolid) and one or several IfcHalfSpaceSolid. Use the following attribute values: IfcShapeRepresentation.RepresentationIdentifier à 'Body' IfcShapeRepresentation.RepresentationType à 'BoundingBox' Use the following attribute values: IfcShapeRepresentation.RepresentationIdentifier à 'Brep' IfcShapeRepresentation.RepresentationType à 'Brep' fp_connect_logical

165 Model Flow Segment (FP) - Confluence 6 af :29 Establish Properties For each segment type, the value of type properties within property sets may be defined. Information on relevant property sets for the various types is given in the extension tables below. For each segment occurrence, the value of occurrence properties within property sets may be defined. Information on relevant property sets for the various occurrences is given in the extension tables below. fp_property fp_property Define type and occurrence Define the type of segment to which the segment occurrence conforms Refer to the list given in the Overview section for further information. fp_define_by_type Define the property set for the segment occurrence fp_define_by_properties Extend occurrence information Define the material from which the segment is constructed fp_associate_material Add information about the weight of the segment occurrence according to the particular method of measurement applied in the local usage. Classify the segment occurrence according to the selected classification approach fp_apply_quantity[weight] fp_associate_classification IFC Entities Required IfcCableCarrierSegmentType IfcCableSegmentType IfcDistributionElement IfcDistributionElementType IfcDistributionFlowElement IfcDistributionFlowElementType IfcDuctSegmentType IfcElement IfcElementType

166 Model Flow Segment (FP) - Confluence 7 af :29 IfcFlowSegment IfcFlowSegmentType IfcObject IfcPipeSegmentType IfcProduct IfcPropertyDefinition IfcPropertySetDefinition IfcPropertySet IfcRoot IfcTypeObject IfcTypeProduct IFC Datatypes Required IfcGloballyUniqueId IfcIdentifier IfcLabel IfcText IfcCableCarrierSegmentTypeEnum IfcCableSegmentTypeEnum IfcDuctSegmentTypeEnum IfcPipeSegmentTypeEnum IFC Functions Required - IFC Property Sets Required Pset_CableSegmentTypeCableSegment Pset_CableSegmentTypeConductorSegment Pset_CableCarrierSegmentTypeCableLadderSegment Pset_CableCarrierSegmentTypeCableTraySegment Pset_CableCarrierSegmentTypeCableTrunkingSegment Pset_CableCarrierSegmentTypeConduitSegment Pset_DuctSegmentTypeCommon Pset_PipeSegmentTypeCommon Pset_PipeSegmentTypeGutter IDM Functional Parts Required fp_apply_owner_history

167 Model Flow Segment (FP) - Confluence 8 af :29 fp_assigns_to_group fp_connect_logical fp_connect_ports fp_define_by_properties fp_define_by_type fp_map_representation fp_place_object fp_property fp_represent_product EXPRESS-G

168 Model Flow Segment (FP) - Confluence 9 af :29 EXPRESS Schema