Fiatech is an international community
of passionate stakeholders working
together to lead global development
and adoption of innovative practices
and technologies to realize the highest business value throughout the life
cycle of capital assets.
  • Membership 2016
  • Project Loss 2014
  • Call for Proposal 2018
  • Fiatech Outcomes
  • CETI2018
  • ETDP-2017
Previous Next
Interested in
becoming a member?

Membership Benefits + Online Application

Join our mailing list.

Receive News, info about webinars, conferences and technology projects.



This project established industry services that support the open publication and collaborative generation of reference data as well as provide a collaborative place for companies that are using and extending reference data.

Project Contacts

Project Manager: Robin Benjamins, Bechtel at This email address is being protected from spambots. You need JavaScript enabled to view it.

WIP Content Collaboration Coordinator: Ian Glendinning, DNV


Project Objectives

This project followed up on the business usage plans for ISO 15926 and iRING technology as established by the Camelot project. The following business needs were addressed by the Avalon project:

  • Define and deliver a scalable ISO 15926 WIP
  • Provide the industry with a wiki on the usages of ISO 15926 (content collaboration)
  • Establish source code management and repository for iRING technology


Objective: Define and Deliver an Scalable ISO 15926 WIP

Avalon defined the business usage requirements for architecture, protocols, organization, processes, and funding models that fulfill the work in progress (WIP) needs of an online ISO 15926 operational reference data service. Reference data definitions published in the service reference and/or extend the existing POSC Caesar Association's (PCA) Reference Data Service (RDS) reference data content.

The goals for the design of the scalable ISO 15926 WIP service were:
1. Develop and deliver WIP services that meet the scale, performance, availability, cost and time-to-market expectations of participant businesses.
2. Develop and deliver WIP processes and operational procedures that support the collaborative identification, definition and publishing of reference data in the above services and are consonant with those business expectations.
3. Develop and deliver cost and funding models that support the WIP operational needs as defined by the above deliverables.

The following points define the content creation requirements of the ISO 15926 WIP:
1. Content ownership remains with the creator of the content.
2. Created content must be contributed under acceptable license terms.
3. Acceptable licenses will be along open source lines (as determined by the project).
4. Base quality of content is determined by the content submitter.

Objective: Provide the Industry with a Wiki on the Usage of ISO 15926 (Content Collaboration)

Establish a wiki site to support the collaboration of companies that are implementing and using ISO 15926. The established wiki will support the need for ad-hoc collaboration meetings to work through extensions to ISO 15926 reference data and to work through questions that are typical of initial users of the standard and iRING technology. The scope of the wiki will include technology, modeling, and mapping subjects as well references to the PCA wiki ( for the balance of information on ISO 15926.

Click to Enlarge

Objective: Establish a Source Code Management and Repository for iRING Technology

Establish a source code repository to manage the evolution of the iRING specifications, software, documentation, and download site ( This objective will also establish the iRING Software Control Board (ISCB) and its governance to provide oversight management of the iRING open source products.

Member Project Participants

AspenTech, AVEVA, Bechtel, Bentley Systems, BP, Chevron Energy Technology, Consolidated Contractors Company (CCC), Det Norske Veritas (DNV), Dow Chemical, Emerson Process Management, Fluor, Hatch, Intergraph, Noumenon, NRX Global, Zachry

FIATECH members who would like to participate in this project should contact Robin Benjamins.


Collaborating Organizations



Project Status

Project Execution

The Avalon project execution method is based on a “zero funding model” approach. All resources and other contributions to Avalon are considered to be “in-kind” by the project participants.

Project Timeframe

The Avalon project kickoff is June 10th, 2009 and will end on November 20th, 2009. The Avalon project will schedule presentations and demonstrations for key industry events in 2010 such as Daratech, POSC Caesar, and FIATECH conferences.

Project Reporting

Reporting of project status will be to project participants and to their sponsoring management.

Project Dependencies

Avalon will depend on the following external deliverables for its success:

Work Teams

Avalon will have four focus areas that will be lead by the following teams:

  1. ISO 15926 WIP Service Team
  2. ISO 15926 Wiki Implementation and Usage Team (content collaboration)
  3. iRING Software Control Board

Once a work breakdown structure is established for Avalon, the project participants will be asked to resource these teams in their area of interest. The existing Camelot project participants, that have been and are actively working on Camelot source code, will be automatically nominated to the iRING Software Control Board. The Camelot participants that meet this criteria are Bechtel, CCC, Hatch, TCS and Zachry.

Project Meetings

The Avalon project will meet every Wednesday on a regular basis starting June 10th. Meeting times will be set at 7:30 AM ET (GMT-5). The Avalon project team’s expected global distribution is extended from GMT-6 (Houston) to GMT+10 (Brisbane). Note that the first kickoff meeting is scheduled for June 3rd, 7:00 AM ET. Ad-hoc meetings will be scheduled by sub team activities on an as needed basis.

There are no planned face to face meetings or working sessions for the Avalon Project. All meetings will be facilitated by web and telephone conferencing.

Project Deliverables

  1. Identified service provider for scalable 24/7/365 hosting of WIP Global Sandbox along with ad-hoc Community Sandboxes and application hosting for iRING RDS/WIP Editor
  2. Processes and procedures for 24/7/365 operational support of hosting servers and network infrastructure
  3. Processes and procedures for 8/5 administrative support for host services
  4. Processes and procedures for 8/5 administrative support for content registration
  5. Processes and procedures for 8/5 abuse evaluation and response
  6. Cost and funding model for items 1 through 5 above
  7. Platform neutral iRING protocol definition document
  8. Processes and procedure for the management of quality (which is via status assigned by self identified authorities) and the “mode” transitions from read-write to immutability
  9. Processes and procedures for work flows within the service
  10. Processes and procedures for reference data usage
  11. Verification framework for minimum syntactical/structural quality
  12. Information model that implements the processes and procedures of Avalon
  13. ISO 15926 “Implementation and Usage” Wiki
  14. iRING software control board – ISCB (Camelot stakeholder approval)
  15. iRING open source code management service
  16. iRING specification documentation
  17. iRING bug tracking service
  18. iRING enhancement tracking service
  19. iRING RDS/WIP Editor enhancement to support Global Sandbox submission process

Architecture of the ISO 15926 WIP

The reference data repositories of the ISO 15926 WIP will consist of two types: one or more Community Sandboxes and a single Global Sandbox. The role of both of these Sandbox types is to host ISO 15926 reference data extensions. The key differentiator between these two types of Sandboxes is the access modes and access scopes. Note that the physical repositories that make up the ISO 15926 WIP are distributed and are not intended to be in a single data repository.

Community Sandbox

A Community Sandbox is created by one or more individuals or one or more companies needing a space to develop work-in-progress extensions to ISO 15926. The physical location of a Community Sandbox is determined by the owner(s) of the community. The lifetime of a Community Sandbox is determined by the community owner(s) but is considered temporary or non-enduring.

Click to Enlarge

Communities are considered private with self managed membership for read-only and read-write access. Possible locations for a Community Sandbox are:

  • Within a company’s network (behind the firewall)
  • In a company’s DMZ (exposed to the internet)
  • In a company’s DMZ and allowing public read-only access
  • Hosted in the ISO 15926 WIP service
  • Hosted in the ISO 15926 WIP service and allowing public read-only access

Community Sandboxes are inherently read-write to the community. The content in a Community Sandbox is considered volatile from a programmatic dependency point of view. The volatility is managed by the community.

A “trust” can be established between two or more communities. A trust is enabled by one community allowing public read-only access of its work-in-progress content and another community forms an interest or a dependency on its content. Due to the volatile nature of Community Sandbox content, it is recommended that trusts be used to discover work-in-progress extensions which would then form inter-community collaborations to promote the content to an immutable state.

Global Sandbox

A single Global Sandbox will exist in the ISO 15926 WIP service. The Global Sandbox content will have public read-only access and have read-write access to non-programmatic dependent aspects such as status and other metadata. This restriction establishes an immutable characteristic on the programmatically dependant aspects of the content. Content is entered into the Global Sandbox via a submission process and interface. Once the content is entered, the immutability mode applies.

The lifetime of the Global Sandbox is forever. At the discretion of the content owner, the content can be raised in standardization levels via requests for certification from authoritative bodies. Once content is in a life cycle for certification and as soon as it appears in a certification body’s ISO 15926 compliant endpoint, the content same content in the Global Sandbox will be terminated and statues accordingly. A certification request is subject to the ownership rules and policies of the certifying body.

The roles, responsibilities, and processes of the certification bodies are outside the scope of Avalon.

If the owner of the content determines that a submission is in error or needs revision, the owner can status the content but cannot change the programmatic dependant aspects. Through the status and metadata properties associated to the content, the owner can form a relationship to a new submission which is considered to be the correction or revision of the content.

Each Sandbox type will include an instance of the RDS/WIP Editor and associated web services to manage both content and metadata. The RDS/WIP Editor will be extended by the Avalon project to include submission and metadata management functionality.

Request for Certification

At any point in the lifetime of content, anyone can make a request for certification to various certification bodies. The process and costs of certification are outside the scope of Avalon. The licensing terms allow certification agencies to publish certification assessments in their own services or in this service at their own discretion. In either case, those certification assessments can be about definitions in this service, their services or other services. If certification assessments are published in this service, they fall under the licensing terms discussed above - in other words, certification assessments published in this service are treated no differently to any other content.


Click to Enlarge


Click to Enlarge

Related Industry Research



Web Pages

WIP Content Collaboration Wiki

IDS-ADI Web Page

Informational Brochures

ISO 15926 Executive Overview

ISO 15926 ROI for Project Managers

ISO 15926 ROI for O&M

ISO 15926 ROI for IT Managers



iRINGUserGroup is an open online community of users, companies, and organizations who use, are considering using, or are developing or deploying iRING protocols. The iRINGUserGroup is also responsible for the management, enhancement, and maintenance of iRINGTools and iRINGSandbox.

Visit Site