skip navigation
home
home events projects resources news join about
home

FIATECH Projects

Data Standards Project Home

Data Standards Aligned with the Roadmap

Participants

 

faqs
sitemap
contacts
Member login

aecXML

aecXML is updating its program of work and procedures. This page will be updated in October with input from the new aecXML Committee.

aecXML is an XML-based language used to represent information in the Architecture, Engineering, and Construction (AEC) industry. It is intended to be used as an XML namespace and to facilitate information exchange of AEC data on the Internet.

Formal Name

aecXML

Common Name

aecXML

Definition

Standardization of the eXtensible Markup Language (XML), an interoperable computer language, for use in the Architecture, Engineering, and Construction (AEC) industry.

Scope

Projects, documents, materials, parts, organizations, professionals, or software.

Projects

Design, construction, decommissioning, operations & maintenance, and facility management.

Documents

Request for Proposal (RFP), Request for Quotation (RFQ), Request for Information (RFI), drawings, specifications, addenda, bulletins, change orders, contracts, building codes, purchase orders

Materials and parts

Items from a catalog, custom manufactured items, assemblies, materials

Organizations

Standards bodies, government agencies

Professionals

Engineers, architects, contractors, suppliers, specialties

Software

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

Current Status

IAI recommended standard.

  • Focus on AEC-specific documents and messages
  • Use ifcXML as a existing library of building objects
  • Use ebXML as an existing library of core eCommerce objects
  • Concentrate on the payload of messages rather than the transaction framework
  • Use a use-case driven approach

Sponsoring Organization

International Alliance for Interoperability (IAI)

  • An alliance of organizations within the construction and facilities management industries dedicated to improving processes within the industry through defining the use and sharing of information.
  • Includes architects, engineers, contractors, owners, facility managers, manufacturers, software vendors, information providers, government agencies, research laboratories, universities, etc.
  • Currently 9 chapters: Australasia, France, the German Speaking countries, Japan, Korea, North America, the Nordic countries, Singapore and the United Kingdom.

Sponsoring Country

U.S.

Web Page

http://www.iai-na.org/technical/aecxmldomain_report.php

Example Applications

None currently identified.

Vendor Information/Commercial Implementations

None currently identified.

Potential Business Benefits

  • Contain AEC-specific information: aecXML focuses on AEC-specific transactions to avoid duplicating work already in an established standard
  • Represent a transfer or message: aecXML is a standardized means of communicating information in a business transaction, not a repository for holding it (e.g. IFCs)
  • Between existing automated systems: aecXML takes an evolutionary approach it automates pressing needs for data transfer needs between existing software systems -- such as transfers between existing order and invoicing systems or between an existing architectural and estimating package
  • Of a limited amount of information: aecXML is focused on relatively light payloads for facilitating specific eBusiness transfers. AEC industries can achieve process improvements with a very focused transfer
  • For a key purpose: The aecXML projects are chosen based on what is specifically needed to make a key business process, such as purchase orders and payment applications in an AEC environment
  • Provide a foundation for the shared project model
  • In an underserved sector: The aecXML projects are complementary to existing software packages
    (Source: http://www.iai-na.org/aecxml/2001_12_aecXML_DomainSummary_r5.doc)

Shortcomings

  • A single XML file cannot contain all of the information for a project. XML is simply used for information exchange only.
  • The schemas being developed are specifically for the AEC industry. This may bring about various incompatible standards should any cross-industry interoperability be needed.

Future Development

  • The ifcXML effort will attempt to combine the efforts of aecXML with other XML efforts into a single schema: Building Construction Extensible Markup Language (bcXML), Building Lifecycle Interoperable Software (BLIS) XML, etc.
  • This schema will likely be based on the Industry Foundation Classes Version 2x

Additional Source of Industrial Guidance