A Supplier Perspective

When everyone involved in infrastructure projects describes plant equipment differently, sales processes slow down, costs go up, and customers get frustrated.

Your sales engineers probably spend an inordinate amount of time reading datasheets sent by prospects for inquiry, proposing which equipment will meet their needs, and translating relevant detail about your products onto prospects’ datasheets. This requires the expertise of an experienced engineer, as every customer’s data requirements and standard definitions of products are different – and can change over time.

Equally important, when new or retrofitted facilities that include your products are handed over to owners/operators, you need to provide them – or their EPCs – with detailed information about these products, including maintenance and operations information.  Because product definitions and descriptions vary across organizations involved in the infrastructure lifecycle, your customers must engage in costly data translation efforts.

A universal data standard can vastly simplify and accelerate data sharing.

ISO 15926 solves data interchange problems by creating a standard way to describe plant information that IT systems can understand, as well as industry-specific reference data.  Data interoperability solutions such as iRING protocols, which are based on ISO 15926, are acting as a “universal translator” so that equipment suppliers, software vendors, and operators collaborating on large capital projects can automatically transfer information in real time between heterogeneous applications without the need for costly, error-prone data interpretation and translation. Data can be shared accurately and effortlessly throughout the entire asset lifecycle – from design, construction, handover, and commissioning to operations, maintenance, and eventual decommissioning – all while retaining its original meaning.

How will you benefit?

When both OEMs and their customers use ISO 15926-compliant software, product data will be instantly interpreted – correctly and in context – as it moves between their respective systems via data sheets. Because the meaning of each data value will travel with the data itself, software on the receiving end will know what each value is and route it to the appropriate spot on the sales engineer’s datasheet. In other words, each party will see a data sheet “in their own language.”

The potential benefits are huge – especially for OEMs. You’ll gain:

  • More time to sell: With a worldwide, standard way to describe plant equipment and the automation of repetitive tasks, sales engineers will spend far less time translating data and responding to information requests – and more time closing deals. This will also allow you to participate in more bids faster and at a lower cost.
  • More accurate datasheets: By taking the manual, human element out of datasheet creation and translation, you’ll see fewer errors and have happier customers.
  • More control over information handover and what’s publicly available:  You’ll be able to control and tailor the information you provide to different participants in the asset lifecycle – quickly and easily. For example, you’ll be able to provide design engineers with information to help them answer, “Is it the correct equipment?” and “How big is it?” And you’ll be able to provide operators with details about how to keep products up and running – and fix it if it breaks. With ISO 15926-enabled software, much of this information can even be supplied through original datasheets.