Smart data and documents

About

EqHub serves as a single, controlled, central source of vendor documentation

With EqHub, suppliers provide information ONLY ONCE. This significantly reduces their delivery work per project and gives them a competitive edge owing to lower documentation costs. Contractors can greatly reduce efforts tied information expediting and compliation, maintaining timely deliveries.

EqHub provides:

  • Extensive and dynamic catalogue with product data, documents and drawings
  • Open access to data and full traceability of changes
  • Clearly specified and up-to-date requirements for each product class and registered data
  • Verification of information
  • Compliance with latest industry standards and regulations
✓  Decommissioning
✓  Development
Exploration
✓  Operations
Pre-award

Benefits

Communication and collaboration are simplified since only one central data archive available will be available and accessible at any time.

Improved work efficiency.

Optimised inventories.

Shortened data delivery schedules.

Reduced documentation volumes.

Achieved regulatory compliance.

Mitigated risks.

Saved time and resources.


Guides and information

Documents

The Guides and information section represents the set of documents regarding the EqHub New Generation. If you require any other document, please contact support@eqhub.no.

For operators

EqHub for operators

For equipment suppliers

Registering products in EqHub

Creating products assembly

How to get access to EqHub

For verifiers

Basic things to know – Verification

Verification checklist

Information material

What is EqHub (full version)

Introduction to EqHub

EqHub new generation onboarding (video)

Product statuses in EqHub

Service levels

API

API step-by-step guide

API Basic things to know (video)

Access and authentication

Getting started with Entra ID

Company Super Users: User Management (video)


Eqhub Norm

Structured, unified, up-to-date requirements for providing equipment information based on the following standards: NORSOK Z-018, NORSOK Z-CR-002, NORSOK D-001, DNVRP-0101, DNV-OS-E101, POSC Caesar (PCA RDL), ISO 15926, UNSPSC, CFIHOS.

What is EqHub Norm?

Access Service


SPIR

SPIR is a collaborative platform between operators, contractors and suppliers, to ensure efficient data flow, governance and transparency between all entities in the SPIR process.

What is SPIR?


FAQ

How do we get access to EqHub?

If your company is already registered to Collabor8 services:

If your company is new to Collabor8 services:

  • Contact Support (support@eqhub.no). They will help you onboard your company and set up the Company Super User(s).

Is there a subscription fee?

No, EqHub is free of charge. The continous development and operational costs of EqHub are covered by the operators on the NCS.

I’ve registered my company in EqHub, can you provide evidence of this registration?

A Certifiate of Registration will be provided on request. In addition, you can download and use any of the emblems below at your own discretion.

  

How is the information entered into EqHub verified/quality assured?

If needed, the information entered into EqHub goes through a detailed verification process carried out by a certified verifier.

Can manufacturers register product information at their own discretion and initiative?

Yes, they can – And they are encouraged to do so. The main incentive for doing so is that this can make product information available for both buyers and/or agents.

Will the data be deleted if my company deregister from EqHub?

Typically, any registered information tied to product and equipment, including its metadata and documents, will not be deleted from EqHub following a company’s deregistration.

Do you need to sign up for Magnet JQS in order to use EqHub?

No you don’t. However, signing up for Magnet JQS provides the opportunity to directly reference and link your company’s products in EqHub to your page in Magnet JQS.

For more informasjon about Magnet JQS, visit Offshore Qualific’s website: Offshore Qualific.

How does EqHub accommodate current and future industry trends?

EqHub will always strive to proactively accommodate industry needs and requirements.

 

What is Microsoft Entra ID?

Microsoft Entra ID is Microsoft’s cloud product to enable users to enter any application or resource with their identity, regardless of where they are or what device they use. It enables Offshore Norge to deliver secure access services via the internet.

Learn more from our step-by-step guide.

Can I append users to my own company in EqHub?

Yes. This activity can be done by your designated Company Super User(s) in EqHub or Support (support@eqhub.no).

To assign a Company Super User on your company’s behalf, please contact Support (support@eqhub.no).

Learn more from our step-by-step guide.

I have lost my write access to EqHub, why?

By 14 June 2023, all companies with write accesses to specific manufacturers (brands) those permissions suspended.

Write access privileges, to your own and other company/manufacturer’s brands will be accommodated and set-up by support@eqhub.no on request. Write accesses will be assigned to the users you specify.

It is important to ensure that any privilege and representation of any brand is accurate and that it relates to current needs.

My company has single-sign-on (SSO) today, will we keep this access type in the new EqHub?

It depends. If you alredy have SSO towards other Collabor8 services (e.g. Hello, Virtual Inventory, Loop, Critical, Magnet JQS, etc.) you will retain your authentication and access type. All companies with existing SSO will be supported in the establishment and set-up of federation (SSO) against Collabor8, on demand and by request.

Is there an API for the service?

Yes, there is a REST API.

Technical documentation can be found here (requires self-registration and sign-up):

https://portal-apis-test-vi.collabor8.no/apis (Test)
https://portal-apis-vi.collabor8.no/apis (Production)

If you want to use or explore our APIs, please fill in our order form and submit it to support@eqhub.no.

Please also note that there are typical screening requirements for API access requests. These are:

  • The requestor is, or works on behalf of, any operator, Manufacturer or agent registered in EqHub
  • The requestor is able to provide a reasonable justification for the intended use of the API.

For how long will API egacy points be supported?

Idefinitely, as long as they are in demand and in use.

How to reset the password on the API portal?

If you have forgotten your password, select “forgotten password”, whereafter you specify your e-mail to which password reset instructionc will be sent.

The API platform is separate from the Offshore Norge Material Management product portfolio. Does It require another credential?

Offshore Norge uses the same API platform for all our API services, namely Azure APIM.

Data model changes, are there any?

Yes, and EqHub provides backward compatibility endpoints (legacy endpoints)) which provides both legacy and new data according to a legacy data structure. All new endpoints will support the new structure.

#API #endpoint

Data model changes regarding EqHub IDs, TEK, TEK-C, SPC, SPC-C, are there any?

Yes, and EqHub provides backward compatibility endpoints (legacy endpoints)) which provides both legacy and new data according to a legacy data structure. All new endpoints will support the new structure.

#API #endpoint

Are there any other noteworthy changes to the numbering system of EqHub IDs?

All historical EqHub IDs will retain their unique sequence number, without prefixes, in the following fashion AAA-NNNNNNNN or NNNNNNNN (e.g., TEK-00025250 or 00025250, respectively). Any EqHub ID generated in the new solution will be generated in the following fashion NNNNNNNNN (e.g., “100000029”).

#API #endpoint

Which mapping rules, if any, with regards to API exchanges and data transformation should I be aware of? (Part 1)

Definition of Item Uniqueness
Unique item – an item that has a unique combination of “Manufacturer name” and “Manufacturer part number” pair in the system.

EqHub (legacy)  is based on prefixes:

1st prefix type: ‘Standard’
TEK – unique item, does not consist of other items.
TEK-C – a unique assembly that consists of only TEK- numbers (unique items), which in the legacy version also includes values in the ‘components’ property.

2nd prefix type: ‘Special’
SPC – not a unique item, does not consist of other items.
SPC-C – not unique item, consists of one SPC item and any other items, which in the legacy version also includes values in the ‘components’ property.

EqHub (new generation)  is based on properties:

isUnique: boolean – defines if item is unique or not (e.g., unique combination of [Manufacturer] + [partno].
type: ‘product’, ‘assembly’ – defines if it is a standalone product or a combination of several.

Which mapping rules, if any, with regards to API exchanges and data transformation should I be aware of? (Part 2)

Syntax mapping(s):

Between Legacy and New Generation

EqHub (legacy) EqHub (new generation)
TEK type: ‘Standard’ type: ‘product’ isUnique: true
TEK-C type: ‘Standard’ type: ‘assembly’ isUnique: true
SPC type: ‘Special’ type: ‘product’ isUnique: false
SPC-C type: ‘Special’ type: ‘assembly’ isUnique: false

API mapping(s):

From Legacy to New Generation

EqHub (legacy) EqHub (New Generation)
TEK type: ‘Standard’ type: ‘product’ isUnique: true
TEK-C type: ‘Standard’ type: ‘assembly’ isUnique: true
SPC type: ‘Special’ type: ‘product’ isUnique: false
SPC-C type: ‘Special’ type: ‘assembly’ isUnique:false

From New Generation to Legacy:

EqHub (New Generation) EqHub (legacy)
type: ‘product’, isUnique: true type: ‘Standard’ components: null/empty
type: ‘assembly’, isUnique: true type: ‘Standard’ components: is not null/empty
type: ‘product’, isUnique: false type: ‘Special’ components: null/empty
type: ‘assembly’, isUnique: false type: ‘Special’ components: is not null/empty

 

When creating assemblies, are there any constraints tied to associating various EqHub IDs depending on their type and/or previous connections?

The only constraint is that any assembly can only be assembled of product revisions that have been verified with the verification status “approved”. Other than that, registrants must be able to decide what their respective assemblies consist of.

EqHub IDs for assemblies no longer have TEK-C or SPC-C prefixes; what are the consequences of that?

All historical assemblies are still identifiable with or without these historical prefixes, and it is still possible to detect parts of an assembly through “components” filed in the historical structure or “assemblyComponents” in the new structure. Exploring all trees where a product/assembly participates will be possible. The actual assembly components (e.g., children) will still carry the “type” “Standard” or “Special” in the old structure presentation (legacy API endpoints).

EqHub IDs no longer have TEK or SPC prefixes, what are the consequences of that?

All existing EqHub IDs (with or without these prefixes are still identifiable by their unique sequence numbers (e.g., TEK-00782572 can still be found by searching for either “TEK-00782572”, “00782572” or “782572”).

Historically, and in short, an EqHub ID with a “TEK” prefix was defined as “standard” products registered with a unique combination of “Manufacturer name” + “partno” (e.g., ROSEMOUNT + 3051S2CD3A2E15A1KC1I1L4M5)), and those with an “SPC” prefix were defined as “special” products with non-unique combinations of “Manufacturer name + partno (e.g. subsequent registrations of already registered “ROSEMOUNT+3051S2CD3A2E15A1KC1I1L4M5” would be defined as a part number being not unique.

#API #endpoint

Will new API endpoints be a part of future development if needed?

Going forward, additional endpoints, and enrichment of existing endpoints, will be developed according to industry demands



Support

Contact information

Support

Monday – Friday (08:00 – 16:00)
+47 23 26 13 94 / support@eqhub.no