DSC Project Home

Data Standards


Member Login

aecXML

Architecture Engineering & Construction XML
IAI - AEC working group


Sponsor

International Alliance for Interoperability (www.iai-na.org)          (USA)

Web Site

http://www.iai-na.org/aecxml/mission.php

How to Obtain

http://www.iai-na.org/aecxml/mission.php

Contact

Domain Chair:   Edward F. (Ted) Smith, EFSmith@arcomnet.com 
Technical Chair: Yimin Zhu, zhuy@fiu.edu, (305) 348 3517 

Usage 

ifcXML compatible file or message electronic data exchange for a broad range of information and documents associated with the AEC industry.  

Scope

The information represented in the aecXML domain may be resources such as contract and project documents (Request for Proposal (RFP), Request for Quotation (RFQ), Request for Information (RFI), drawings, specifications, addenda, bulletins, change orders, contracts, building codes, purchase orders), attributes, materials & parts (catalog items, custom manufactured items, assemblies, materials), products, equipment; meta data such as organizations, professionals, participants; or activities such as proposals, projects, design, estimating, scheduling and construction.

Infrastructure working group: The purpose of the Infrastructure Working Group is to enhance communication across the various shareholders in the lifecycle of an Infrastructure facility which might include roads, bridges, airports, ports, railroads, bikeways, dams, channels, flood control structures, land development sites, storm sewers, water distribution systems and sanitary sewers.  See also landXML.

Building performance and analysis working group:  The purpose of the Building Performance & Analysis (BPA) Working Group is to streamline communication across the various shareholders in the lifecycle of a facility which might include energy, health, transportation, and resource use issues.  See also gbXML

Characteristics

See Interoperability tutorial for further detail about the terms used below.

Domain

commercial + industrial buildings

Standard Type

deFacto

Standards Process

Standardize then Implement

Intellectual Property (IP)

Open, royalty-free XML schemas

Cost of one interface

unknown at this time

File Format

XML

Focus

Usage-driven with defined exchanges.

Scope

Multiple Domain - See scope statement above.  Also intended to be based on ifcXML

Scalability

Unknown

Extensibility

Those based on IFCs and are dynamically extensible

Model Content

Mixed.  IFC offers broad shallow framework.  Domain areas covered by landXML and gbXML are deeper.

Usage

Primary usage is exchange files or messages associated with specific transactions, e.g., with request for quotes, quotations or purchase orders

Exchange Content

IFC uses the data model + data approach

Data model approach

intended to use ifcXML which uses an domain-abstract data model approach

Benefits

TBD

Status & Plans

Restarting in 2005,  draft schemas and working groups identified for landXML and gbXML

Software

Computer-aided design (CAD), estimating, project management, scheduling, document management 

Deployment Status

None currently identified.

Limitations

Not yet commercially demonstrated

Additional Resources

aecXML Framework R1.doc: the structure of the aecXML work

aecXML Schema Development Process R1.doc: the approach for defining a new aecXML schema

aecXML Use Case Template R1.doc: the proper context for the XML model

aecXML Schema Acceptance Criteria R2.doc: the classifications of schema and guidelines applied to schema

aecXML Schema Style Guidelines R2.doc: the formatting and stylistic guidelines for submitted XML schema

© 2005 FIATECH. All rights reserved