ARCHITECTURE
The system is made of a central repository where all the measures collected locally are store in the same database. The central repository is feeded daily by each local db trough xml files. As soon as the files are transferred by PM4Data into the destination folder, an importing procedure add the rows of each file into the central database. The local owners decide what to transfer to central repository, according to central quality department.
The xml file has a structure that refers to several local data structure that can be managed also by the central system:
The main data blocks are referred to:
- DATE AND TIME OF ACQUISITION: date and time of the measure value detection
- MEASURE INFORMATION: information of the measure
- PROCEDURE INFORMATION: procedure in the local database that include the measure
- LOCATION INFORMATION: location where the measure value has been detected
- PRODUCT INFORMATION: product on wich the measure value has been detected
- SURVEY INFORMATION: all the values of the collection
- TOOL INFORMATION: information of tool used in the value detection
- CORRECTIVE ACTION INFORMATION: all the corrective action managed by the local
Not all the fields are strictly necessary for the capabilities calculation, the mandatory ones are tagged in yellow:
Those fields are necessary to present in the central SPC platform interfaces the capabilities for each MEASURE CODE. All the other information are optional and can be collected only if the local quality system is actually managing them. The main pivot of the capability calculation is the MEASURE CODE. That code is defined by the local system and can be used in: - Several machines - Several procedures - Several product codes It means that it is possible to have more than one product, procedure and machine involved in a single capability calculation, that depends on how the local system send data to the central SPC. It’s important that every measure code share the same target value, max value and min value, measurement unit.