Controlled product data

The problem with uncontrolled data

A product fact, such as a rating range, an input window or a cooling method, appears in many places: the website, datasheets, proposals, drawings and rating plates. When each is edited separately, they drift apart, and a buyer cannot tell which is correct. Invitrona aims to keep product facts in one controlled source and to draw every document from it.

How product data is organised

Products are organised from family to class to configuration. The website and datasheets describe classes, named by their title and rating band, for example servo voltage stabilizers up to 500 kVA. A proposal describes a specific configuration for a specific requirement. Each level carries the facts that belong to it:

• Class level: typical rating range, supply arrangement, construction and cooling
• Configuration level: the rating, input range, options and protections for the agreed duty
• Unit level: serial identity and the records of the unit as built; see unit and batch traceability

Typical values and stated conditions

Class pages state typical ranges, not guarantees for every configuration. A value that depends on a condition is shown with that condition, for example an output voltage for a three-phase configuration. The value that applies to a supplied unit is the one in its approved configuration and documents.

Ownership and revision

Each product record carries an owner, a source, a revision and a review date. When a fact changes, the record is revised and the documents drawn from it are updated together. Superseded documents are withdrawn from normal use.

Model identifiers

Products are described by class and rating band rather than model code. Model, configuration, serial number, batch and revision are kept as distinct identifiers so that each can be referred to without ambiguity.

Figures on this website

The class pages on this website give typical ranges for each product class. They are written as ranges and typical values so that they are not read as a promise for every unit, and the conditions that qualify a value are shown beside it. When a figure is revised, the class page, the datasheet and the guides that refer to it are updated together, and the page's revision changes.

Questions you can ask

• Which values in the proposal differ from the class datasheet, and why?
• Under which conditions does each performance value apply?
• Which revision of the datasheet does the proposal refer to?

What this means for a buyer

The figures you read on a product page, a datasheet and a proposal should agree. Where a proposal states a different value for your configuration, it does so explicitly, with the condition that applies. If you find a conflict between two documents, report it through the enquiry form; the controlled source decides which is correct and the other is corrected.