Phoenix FAQs

Who are Kraken IM?

Kraken IM is a specialist information management company. We develop software that helps organisations:

  • Reduce the cost of capturing supply chain information by making it digital
  • Minimise delays and overruns by surfacing critical supplier information early
  • Track engineering, quality, and carbon footprint data to support the energy transition and net zero goals

We are active contributors to the development of the CFIHOS standard. One of our directors, Ian, sits on the CFIHOS Steering Committee. We are recognised leaders in educating, implementing, and integrating CFIHOS, and our software supports it by default.

Beyond CFIHOS, we have extended the standard to align with other frameworks such as ISO 14224, EPIM, ISO 19650, EN 15804, and PCA. This enables our users to apply CFIHOS in combination with other widely used standards. Phoenix includes a subset of these mappings for reference.

To learn more, visit our blog or contact us.

What is CFIHOS and why is it important?

CFIHOS (Capital Facilities Information Handover Specification, pronounced “see-foss”) is an industry standard for structuring and exchanging project information across the lifecycle of a facility. It provides a consistent approach for operators, contractors, equipment manufacturers, and suppliers.

Its key objectives are to:

  • Ensure that operators receive the information needed to run, maintain, and eventually decommission a facility
  • Enable information to be shared easily between users and systems
  • Allow information to be located and retrieved quickly when required

By standardising data requirements, CFIHOS reduces the cost of generating handover information and improves consistency across the supply chain.

What is Phoenix?

Phoenix is a modern web application designed as a central hub for engineering RDLs. It brings together the latest version of the RDL in an accessible, easy-to-navigate format.

Key features include:

  • RDL browser Explore the Reference Data Library (RDL) to see the class-specific requirements for tags and equipment.
  • Excel templates Download structured templates containing class attributes and associated entity attributes.
  • Powerful search Quickly find the exact data you need, no digging through documents and spreadsheets.

Visit the templates page to get started.

Is Phoenix free to use?

Yes. The CFIHOS version of Phoenix is available free of charge. The only requirement is that you do not modify the Excel templates without contacting us.

What Phoenix is not

Phoenix is not a substitute for a full CFIHOS implementation. It is designed as a communication and learning tool, making it easier to view the RDL and understand data requirements for specific classes. For full adoption, users should still refer to the RDL and official CFIHOS guides.

Can I use Phoenix with my own RDL or custom templates?

Yes. Phoenix can be configured to display any reference data library and to generate templates based on your requirements. If you are interested in a custom deployment, please get in touch.

If you would like to unlock and edit the Excel templates without license restrictions, contact us to discuss options.

How do I use the Excel data templates?

Each template is based on the version of the CFIHOS class library shown on the title page. They include sample data (which can be deleted) along with class and entity-specific attributes. For tag classes, some optional connection data is also included. Note that the templates are not exhaustive for project handover.

To use them:

  1. Enter data Open the “CFIHOS Data Template” tab and fill in values in the relevant fields. Some cells include validation rules aligned with the CFIHOS RDL.
  2. Generate datasheet view Open the “CFIHOS Data Sheet” tab and select the relevant entry from the dropdown menu (highlighted). The sheet will automatically update with the corresponding data.

If you use Halcyon, templates can be loaded directly. If you use the Halcyon Excel add-in, you can validate template contents, compare against master data, and run automated document checks.

Why are there separate templates for tags and equipment?

Facility information involves both the functional definition (operating requirements) and the physical definition (the equipment that fulfils those requirements).

  • Tag (functional) data Defines the technical design requirements, e.g., the maximum design pressure of a pump. These are typically specified by design engineers.
  • Equipment (physical) data Defines the actual characteristics of the device, e.g., type, weight, and dimensions of the pump. These are usually provided by suppliers or OEMs.

In CFIHOS, tags and equipment are distinct entities with potentially different originators. To achieve complete facility information, both sets of templates are required.