If your company is new to Collabor8 services – Please complete the Signup form (goto: https://collabor8.no/services/eqhub/#sign-up).

For companies already registered – Please contact Support (mailto: support@eqhub.no )

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

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.

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

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.

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.

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.

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

Yes, there is a REST API.

Techincal 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 are interested in using or exploring our APIs, please fill in our order form and submit to support@eqhub.no

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

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

Technical documentation can be found in our swaggers, here:

• EqHub API documentation (requires sign-up) (goto:https://portal-apis-vi.collabor8.no/apis)
• If you are interested in using or exploring 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:

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

Hello provides consolidated user accounts management and user authentication services across the service portfolio, and enables Offshore Norge to deliver secure access services via the internet.

If you or your company is alreay a user of other Collabor8 services (e.g. Hello, Virtual Inventory, Loop, Critical, Magnet JQS, etc.) you already have at least one designated Hello Administrator in your organisation.

If you are new to Hello, please contact Support to set-up an administrator.

How to sign up for Hello account – https://www.youtube.com/watch?v=9fCS38W3VeI
How to sign in to EqHub (Norway) – https://www.youtube.com/watch?v=xUjtgF5dgnI

Yes. This activity can be done by your designated Company Super User(s) in EqHub, and will typically be coordinated between this user and your designated Hello Administrators to ensure authentication.

To assign a Company Super User on your company’s behalf, please contact Support.

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 which you specify.

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

Single sign-on (SSO) and fedeation services will typically be accommodated when the requesting company can justify demand as well as meet other typical technical requirements, including the willingness to cover administrative costs. To learn more, read our  federation requirements, or contact support@eqhub.no.

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.

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.

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

If you have forgotten your password, select «forgotten password,» whereafter you specify your email to which password reset instructions will be sent.

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

Yes. EqHub products data is now based on a new Requirements Library (EqHub Norm), which supports multiple standards.

The data model follows these principles:

• Add more information about requirements used for product data creation and product information maintenance, which will help track a requirement change to notify suppliers (data providers) about it in the future, e.g., when additional documents/properties are added/amended
• Simplify and improve the representation of EqHub IDs based on experience and demands e.g., change ‘Special’ and ‘Standard’ types to isUnique attribute

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.

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”).

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.

Syntax mapping(s):

Between Legacy and New Generation

API mapping(s):

From Legacy to New Generation

From New Generation to Legacy:

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.

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).

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.

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