Nternational repair information s

Дата канвертавання22.04.2016
Памер22.45 Kb.




IRIS was developed middle of the ‘80s by Sony to return field service data back to factories. 1989 standardisation between Sony Japan (ISIS) and Sony Europe.

1993 standardisation with other Japanese manufacturers for gathering data from overseas.

1992 start in UK by BREMA members.

1994 start in France (Simavelec) and in Holland (FIAR)

1994/95 start throughout Europe by EACEM (European Association for Consumer Electronics Manufacturers), including regular official code maintenance.

2002 EACEM merged into EICTA (European Information, Communications and Consumer Electronics Industry Technology Association), 2009 EICTA renamed to DIGITALEUROPE

In most European countries, IRIS has become the official or the ‘de facto’ repair data coding standard for Brown goods.

Content of IRIS

IRIS uses coded data to transport repair and service information.

First part is called Symptom Area and includes description about the set’s malfunction or customer’s complaint and the condition where the problem of the product occurred. It requires no specific technician know-how to be filled out.

(Condition code + Symptom code + Extended code)

Second part of IRIS code is called Diagnosis Area and includes information’s from the technician to describe where the defect was located, and the actions that were taken to repair the set (Section- & (optionally) PCB code / + Part Reference(s) + Defect code(s) + Repair code(s) + Repair Flag + (optionally) No fault found code)

Why coding data

To solve the European difficulties of different countries, different languages and different types of organisations.

To support computerised repair administration at workshops with Electronic Data Interchange (EDI) between Servicers and Manufacturers.

For simplified warranty reporting from workshops with different manufacturers.

For faster warranty claim handling with result of quicker cost settlement.

To gather experience and know-how and allow quick and correct cost estimation.

Coded Repair data are the key information to speed up the Product Quality Improvement Cycle at manufacturers including development of efficient service tools.

For which direction

Feed back to Design & Production, Quality Assurance and Warranty administration

Feed forward to the field by Bulletins & Repair Tips, Troubleshooting help, On-line ‘Knowledge base’

How to transport

The EICTA Claim File data format is developed to transport all necessary information by simple batch file. It includes all relevant information about the repaired product, the sales dealer, end-user, the warranty conditions, all IRIS data like symptom and diagnosis, used spare parts, claimed cost of different cost types, exchanged product data, shipping and transfer data, administration data, free text data, feedback from manufacturer as bi-directional transaction.

Where to find

At www.DIGITALEUROPE.org (Partners & Links) for Brown Goods & at www.CECED.org

(E-Business) for White Goods. Combined multi language search tool at www.iriscode.org

Condition code
Symptom Code

Coded by 1 + 3 digit to describe the problem of the unit
Byte 1: Under which circumstances? (condition)

Byte 2: Which main function group? (area of problem)

Byte 3: Which type of malfunction? (type of problem)
Byte 4: Which malfunction exactly? (problem specification)
The Symptom code should describe the problem as it can be perceived by any of the five senses, based on simple questions which the enduser can answer, like:

“What exactly did you (or did you not) see, hear, feel, smell, taste,….?”

Does this phenomenon occur all the time, or under certain conditions?

Symptom code numbers are structured in a matrix for problem type and problem area

Section code

This 3 digit code indicates in which area of the set the intervention(s) was (were) performed.

Defect Code

This 2 digit code specifies the type of defect(s) that was (were) found by the technician.

Repair Code

This 2 digit code identifies the actions performed by the technician.

Spare Part number

Is the order number of the replaced part (s). Input based on official part order number at manufacturer’s service manual. Especially when no parts are used all IRIS codes becomes more important.

Part reference

Is the position reference of the part (necessary if same part number is used at different locations). / Sometimes it is printed at the PCB’s part position / Free text input. Especially for actions without parts like adjustment and re-soldering the input of part reference is most important.

PCB Code

Is the name of the printed circuit board, where the component is located. Free text input.

No Fault found Code

This 3 digit code is optional to be used by specialist services to describe any (external) reason that causes a claim without real defect cause at the set. Input at section code field.

Extended Codes

This 3 digit code is optional to be used by specialist services to describe more details under which conditions the problem happens and to specify the related location, accessory, connections, program types or operation modes. Input at section code field.

Parts Flag

It indicates the part of the real cause for the problem or the most important symptom or IRIS line.


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка