DE19917003A1 - Computerized data measuring and handling system for measuring contours of workpieces has data structuring and importance evaluation steps - Google Patents

Abstract

The measuring station is connected to a PC (Personal Computer) which is in turn connected to a data preparation module (160), which changes raw data to structured data. A further stage assesses whether the data is of the correct format for reception and suitable for recording. If the answer is YES (ja), the data is fed directly to an import and data processing circuit in the data memory bank (164). If the answer is NO (nein), the data is passed to a data fine processing stage (162) before being fed into the memory bank.

Description

The invention relates to a method for measuring a plurality of components each having features of interest at least one component group using at least one Measuring station, the data comprising by measuring each one Measured data obtained component, in electronic form, and for Providing the measurement data in a component and feature-related form enabling electronic evaluation.

In the course of developing components, such as Vehicle components and their individual parts usually have to be many individual components (test objects) in different development and Measuring the production status with regard to features of interest become. Even when setting up a component production for example to optimize the tools used for manufacturing Test-made components are measured. Even after finished Development and finished manufacturing are often for example for quality monitoring, components with regard to features of interest can be measured. With all of these measurements usually results in a large number of measurement results. Even if that Measurement results are available in electronic form (computer files), see above the individual measurement results would be extremely difficult to access because the Measurement results, if the measuring station used has any data in electrical form, conventionally in a variety of individual files were provided. Therefore, one primarily has with printed measurement files filed in folders, which at least a cursory visual search for older measurement results permitted, provided that at a later point in time recourse to older ones  Measurement results were of interest. A combination of different Measurement results, for example for statistical evaluation or Representation of a development of manufacturing tolerances or the like but was based on both possibly on different Scattered files as well, usually based on different folders scattered measurement protocol printouts with only one extremely high expenditure is possible and is therefore often avoided in practice. If at all, one that has arisen over a longer period of time Evaluation including measurement results was done, this was Evaluation in operational practice often only on measurement results of one certain functional area of the company (e.g. development) limited because access to measurement results from other operational Functional areas, such as sample construction and manufacturing, only was possible with great effort.

In contrast, it is an object of the present invention to provide a measurement data information system and a method of the type mentioned at the outset, which make the measurement data more accessible for evaluation. To solve this problem, it is proposed with regard to the method that the method comprises the following steps:

• - Determination of those of interest to be measured on the components Characteristics,
• - Measuring the components using the measuring station with regard to features of interest,
• - Providing the measurement results in electronic form in at least a database-compatible data structure, especially in a Database that provides electronic access to the measurement results for individual features of interest of individual components.

According to the measurement results in electronic form in provided at least one database-compatible data structure, the one electronic access to the measurement results for individual interested  Features of individual components allows, so that even later Time still related to components and features based on previous measurement results can be used. This is also a link between mutually corresponding features for different components, for example, components of different manufacturing states, as well as different, mutually associated characteristics of different components (for example the diameter of a pin of a component and the Diameter of an opening in another component that the pin should record) possible.

If we are talking about a database-compatible data structure, then so this term means either a data structure by means of which the Measurement results can be imported into a database, or a Database itself or its physical files in which one of the Database management system assigned to the database in the Stores database-containing collection of data. At the end of The method according to the invention can therefore be a database and its Database files are available or just one or more files that the Measurement results contain in a form that that of a database assigned database management system access the measurement data and can import into the database and its database files.

The at least one database-compatible data structure is preferably based (the at least one file for import into a database or the Database itself with its database files) on the relational or object-oriented data model. This enables the data to be relative can be accessed easily and flexibly and that the database too can be easily expanded at a later date. The request from Data from such a database is comparatively simple because for Such databases are usually easy to use (descriptive) Query languages, for example the query language SQL (Structured Query Language), which are available versus procedural  Query languages for hierarchical databases are much more flexible. A relational or object-oriented database is especially then also Particularly advantageous if the database is still being set up it is not finally clear what kind of evaluations at all Basis of the measurement results to be recorded in the database should be carried out. Would you like a hierarchical database choose, it could be that at a later date turns out that the selected database structure for now evaluations of interest is poorly suited and long search times conditionally.

At least one database-compatible data structure can be a table structure or object structure, each of which corresponds to a table row or a Object corresponding data record a certain measured component contains a clearly identifying component key. On the Component key can quickly access the assigned data record become.

It is proposed that at least one database-compatible data structure comprises a table structure, each of which a table row Table structure corresponding record only one measured value of a certain feature of a certain component and one the feature contains uniquely identifying feature keys. If here from Measured values is mentioned, this also includes the possibility that in the Data record also includes a range of measured values. On the Feature key can quickly open in conjunction with the component key the measurement result for a certain characteristic of a certain component be accessed. For example, at least one table structure be provided in which in each table line the component key and Feature key as part of a certain feature of a certain Component uniquely identifying key are included.  

It is extremely useful if the key is as far as possible Use of labels such as those used in everyday business Drawing number of a drawing on which the component is based. In the example, the key would uniquely identify the component identify the underlying drawing number. Furthermore, the Key the component unambiguously according to the state of development or / and Identify manufacturing status.

In the event that several measuring stations are available or around the Possibility of using multiple measuring stations in the future The key can be used to measure the component clearly identify the measuring station used. It can also be expedient that the key also the measurement conditions during of the survey uniquely identified. For example, it may be desired be a certain component under different measuring conditions, for example different temperatures, to measure changes between. Determine measurement conditions (to about the To determine the thermal expansion of a component).

As a rule, different, possibly separate component groups are used measure assigned components. A component group can have several include similar components (test items).

For the later evaluation of the measurement data, it is useful if in the Database-compatible data structure setpoints or / and tolerances or / and Information on the dimension of the respective measured value and / or information on the Date of the measurement process and / or details of at least one at the Survey involved person and / or details of the measurement prevailing measurement conditions are recorded.

As part of the determination of the components to be measured features of interest can include at least one list of features from  features to be measured for the individual components. This can be the case, for example, in a meeting of responsible persons involved functional areas of a company take place to the course of the To determine measurements. In the course of drawing up the lists of characteristics can also make appointments for naming conventions for Data files and with regard to a systematic numbering of DUTs take place. Information can be entered in the database-compatible data structure to the list of features on which the respective measurement is based or / and the list of characteristics can be included.

It is particularly advantageous if the measuring station in a database-compatible data structure suitable for import into a database provides so that the measurement results with little effort in terms intermediate processing or the like in the database (in particular a relational or object-oriented database) can be imported. The import can be done by the measuring station itself if the measuring station even the database holds. The import data provided by the measuring station However, data structures can also be processed electronically (using Data carriers, such as floppy disks or data tapes, or via a Computer network) to a computer holding the database and imported into the database there. Does the measuring station keep the database, So the measuring station can also directly into the measurement results Write database.

Especially when using conventional measuring stations (e.g. Coordinate measuring stations), it may be that the measuring station Source data containing the measurement results in a data model of used database not in the appropriate structure or in a provide a structure that is generally not database-compatible. An example of a For example, a data structure that is not database-compatible is a format-free, in unstructured file, such as a text file, from the information  without interpreting clue words (keywords) or the like are not accessible.

For such a situation, it is proposed that user data from the Automated and electronic source data in the least a database-compatible data structure can be transferred. In the database-compatible data structure can in turn be the one used Act database itself and its database files or to a Import into the database serving data structure, by means of which the user data into the database (especially a relational or object-oriented Database) can be imported. The import is preferably also done automated, for example using appropriate import functionalities a database management system managing the database.

It may be that the source data in addition to the user data of interest contain residual data of no interest. It is suggested only that Transfer user data into the database-compatible data structure. A the Restructuring of the source data to the at least one database-compatible Software structure implementing data structure can in the course of Restructuring the user data of interest from the source data extract.

It has already been indicated that the source data from the measuring station in a file that is not database-compatible, possibly format-free (e.g. a Text file) can be provided. In such a case, the User data by means of information signs or information words (one could also use Speak keywords). The user data can also be arranged at defined positions, either at defined positions absolute positions within the file or relative positions in relation for information signs or information words. You can also use the data identify with information that relates to related user data obtain and information related to the user data  contain. For example, a one Feature number assigned to component feature can be used. So you could use the feature number assigned to a component feature Identification of the measurement result measured for this characteristic use by assigning the feature number to a specific predefined location in the file, for example at a specific location in a file line writes. This characteristic number then represents one Indicative data value, on the one hand the associated measurement result marks so that this can be found from the file, and on the other hand Provides additional information about this measurement result, namely which one Feature the measurement result belongs to.

It may be that the measuring station for each component measured File containing measurement results for the features of interest provides. In such a case, it is preferred that an automated Most of the files provided are processed in one go at least one that contains the useful data for several components to generate database-compatible data structures. Preferably at least a database-compatible data structure generates the user data for several Contains components. Database-compatible data structures can be created that only contain user data for one component. The processing can for example in the course of a so-called batch processing (batch Processing). The associated batch files are preferred or batch programs also created automatically. As part of the Batch processing can be used to create existing programs String manipulation are used, for example within programming tool available for the UNIX operating system AWK or the tool GAWK for the DOS operating system, which is in the Part of the GNU project of the "Free Software Foundation". But it is also possible to use a specially programmed software application use that the extraction of the user data from the source data and their  Transfer to the at least one database-compatible data structure (possibly File) takes over.

The file may have a common structure Conventional printed measurement reports are based on the measured Component or / and the measurement process or / and the component group related data containing file header and a the measurement results containing the body of the file. It is proposed that the Source data useful data are transferred into at least one table structure, in their table rows, the measured component is unique identifying component key is included, at least based in part on data taken from the file header. Is preferred at least one table structure is provided, one in each of the lines Measurement result for a certain characteristic of a certain component is included and in which the component key is assigned by a characteristic attribute a key that uniquely identifies the characteristic is added, wherein the feature attribute is at least partially from the body of the file extracted data is based.

In the previous statements, the term "feature" denotes so to speak the smallest unit of interest for which exactly one Measurement result or possibly a measurement result range is measured, for example, the diameter of a particular pin on one Component. The height of this cone is within the scope of this nomenclature independent characteristic, as well as the diameter of the pin or the respective dimensions of other similar pins on Component. One can then simply use the characteristic as a characteristic attribute assigned identification, for example a characteristic number, use.

One of the file lines in which the Measurement data value for the characteristic is contained within the file body,  assigned number or address can be used. Such Approach is appropriate, for example, if one Characteristic identification, in particular characteristic number, several Measurement results are assigned, for example because a component has certain has multiple measuring configurations and objects, all of which the same feature number is assigned, or because of a design or an object of the component with regard to several, not independent marked sizes is to be characterized. Examples of that here The mentioned configurations and objects of a component are cones, Recesses and the like, which are provided multiple times on a component can be, for example, in terms of depth or height on the one hand and diameter can be characterized on the other hand. These like Objects or designs can be shared Characteristic name, possibly feature number, be marked so that this characteristic designation for the identification of the individual measurement results is no longer available.

In addition to identifying these "unique features" via the as Characteristic attribute line number used or line address exists also the possibility of becoming a parent Feature numbering of associated individual features and the corresponding count together with the parent Characteristic description (possibly characteristic number) as characteristic attribute use.

It is preferred that the measurement of the components at least partially automated. The measuring station can be a coordinate Act measuring station, which, for example, by means of an XYZ measuring head Components scanned for the features of interest. But it is also possible, the respective component according to other measuring principles, for example optically to use measuring station. The components can also be based on other properties and parameters,  for example according to their weight, their surface roughness etc., be measured using an appropriate measuring station.

The method according to the invention is then particularly expedient applicable when components (e.g. vehicle components or / and Parts of vehicle components) in various development and Manufacturing conditions are measured. By comparing Measurement results for various development and manufacturing conditions can provide important conclusions for further development or / and for a Optimization and quality assurance of manufacturing can be gained.

As already mentioned, the invention further relates to a measurement data information system. A measurement data information system according to the invention comprises:

• - A computer arrangement with at least one assigned Mass storage,
• - One using the method described above obtained database with at least one on the mass storage held database file, the measurement results for a plurality of components each having features of interest contains at least one component group,
• - A database running on the computer arrangement managing database management system,
• - At least one for access to measurement data and / or for evaluation of measurement data or / and for the visualization of measurement data or / and Measurement data evaluations serving on the computer arrangement running database application.

The invention is described below using exemplary embodiments reference to the following diagrams and illustrations explained.  

Fig. 1 and

Fig. 2 show a flow chart useful for illustrating the inventive method of an embodiment.

FIG. 3 shows one possibility of how the information flow between different operational functional areas can be provided within the scope of the implementation of the method of FIGS. 1 and 2.

FIG. 4 shows a section of a list of features that was drawn up as part of the method of FIGS. 1 and 2.

Fig. 5 shows an example of a numbering Bauteilprüflingen in a case that a plurality of sample groups each having a plurality of components to be performed characterized by a specific drawing number component type.

FIG. 6 shows a table in which examples of possible naming conventions for source files generated by the measuring station generated, each containing the measuring data for a measured component, are shown.

FIG. 7 shows a source file printout with information on the component and the source file header containing the measurement process and the first part of a source file body containing the measurement results.

Fig. 8 is a diagram showing how the data contained in the signals generated by the measuring station source files can be classified.

Fig. 9 shows in an overview diagram as in generated by the measuring station used source files of user data contained in a database can be transferred.

Fig. 10 shows the relations between four database tables (measurement data, feature lists, equipment list, master data) of a part of the embodiment of Figs. 1 and 2 relational database used.

. Figs. 11 to 14 show in several flowcharts can be done as the data processing of the payload data contained in the source data corresponding to FIG. 7 to be imported into the database used by means for generating import files (files structure).

Fig. 15 shows a table that represents a l obtained, for example, by the process of Fig. 1 to 14, the relational data model of the database used corresponding measurement data import file.

FIG. 16 shows a measurement data database table that was generated by importing several measurement data import files in the manner of FIG. 15.

Fig. 17 is a obtained by importing multiple master data import files master data database table shows.

FIG. 18 shows a section of a feature list database table that was generated by manual or automated transfer of feature lists in the manner of FIG. 4.

Fig. 19 shows a measurement data information system schematically shows, based on the by the method of Fig. 1 and 2 obtained database and this database (database) which, together with a related database management system.

Fig. 20, the automatic generation illustrated by import files from the source files by means of a string serving for manipulation programming tool and this controlling batch programs.

Fig. 21 through Fig. 25 show an example of the program code of the batch programs.

The possible flow of the method according to the invention is shown in the flow chart of FIGS . 1 and 2. First, the individual components to be measured (test objects) are determined, the components being determined according to the component type (possibly identified by a drawing number of a construction drawing on which the component is based) are (step 110 ), and possibly according to the state of development (step 112 ) and possibly according to the state of manufacture (step 114 ) of the components. If only one development state and / or only one production state is assigned to the component type, steps 112 and 114 can of course be omitted. It may also be the case that a drawing number on which the component is based identifies the component type and the state of development, so that steps 110 and 112 coincide in this respect.

After the steps mentioned, the components are determined to a certain extent in addition to the component type and possibly also the development status and possibly also the production status. In step 116 , it is now determined how many test objects of this component type are to be measured and a test object identification that individualizes the individual test objects is defined. It is also necessary to determine which features are to be measured for the test objects, whereby different features may be of interest for different development states and / or different manufacturing states for components of a component type. This can be done in a step 118 if this has not yet been done in connection with steps 110 to 114 . A list of features is expedient, in which the features to be measured are specified and ideally explained in more detail. As an example, reference is made to FIG. 4, which shows an extract from a list of features which shows the features to be measured on a primary flywheel of a two-mass flywheel assigned to a vehicle friction clutch for the production states "raw", "after welding" and " after machining ".

If several measuring stations are available, it must be determined which measuring station is to be used for which test objects (step 120 ). If necessary, the measurement conditions for the measurements can be specified in this context, provided there is scope. For example, it could be of interest to carry out measurements under different, specifically set measuring conditions, for example different temperatures. From this, interesting conclusions could be drawn about the behavior of the components under changing environmental conditions, for example about the thermal behavior of the components.

If the test objects have not yet been manufactured, they have to be manufactured for the measurement (step 122 ). If the test objects are available, the measurements can be carried out on the test objects (step 124 ), the measurements preferably being carried out on the basis of the feature list assigned to the component type of the test object.

The measurement results are provided in electronic form by the respective measurement station (step 126 ). According to the invention, the measurement results are transferred to a database, possibly together with associated information (step 128 ). The transfer can take place directly in the course of providing the measurement results in electronic form, for example if the measuring station or a computer assigned to the measuring station itself holds the database, so that the measuring station can accordingly write data directly into the database. As a rule, however, the measuring station will provide the measurement results in the form of files, the content of which - as far as is of interest - has yet to be transferred to the database. The files provided by the measuring station can be structured in such a way that the user data of interest can be imported into the database directly using these files. In this case, the files provided by the measuring station can be referred to as "import files". In the following, however, it is assumed that the measuring station provides files that are not database-compatible or do not correspond to the data model of the database used, so that the data given by the measuring station or the measuring stations must be restructured for the import into the database, whereby if necessary, the user data of interest is extracted from the files of the measuring stations which also do not yet contain any residual data. The files provided by the measuring station or measuring stations and not suitable for direct import into the database are referred to below as "source files".

It should also be pointed out that the order of the process steps of the flow diagram of FIGS . 1 and 2 can be changed, if appropriate, and that different process steps can also be carried out simultaneously. The process of FIGS. 1 and 2 may be part of an overall development and / or Fertigungsoptimierungs- and / or quality assurance procedure. Within a company, various functional areas can be involved in the implementation of the method, such as development, prototype construction and production. These operating areas can have their own measuring capacities ready, or a separate service department carrying out the measurements can be provided, which can then be understood as a separate functional area. For the process to run smoothly, it is expedient if a coordinated exchange of information between the functional areas involved is ensured with regard to the measurement attempts, which can be achieved by appropriate organizational measures. Fig. 3 shows an example of how the flow of information can take place between the functional areas. In the example, an administrator is provided who coordinates the exchange of information between functional areas. In the example, it is assumed that the measurement data are transmitted from the measurement stations by remote data transmission to a data processing computer, where the data are processed and imported into the database. Data preparation and data import is made easier by the fact that unique feature identifications (feature numbering), unique part numbering (test item numbering) and a naming convention that facilitates access to the source files are provided.

An example of a test specimen numbering for several series of measurements for the same component type, identified by a drawing number, each with a plurality of test specimens (100 test specimens each for test series 1 and 2) is shown in the table in FIG. 5. In the example, the test items are numbered consecutively across the test series, with the measurements for the test series taking place according to different lists of characteristics. It goes without saying that the test objects to be measured are clearly identified by their test object number, by affixing or stamping the number on the test object so that confusion is impossible.

In the exemplary embodiment considered here, the at least one measuring station provides exactly one source file for each test specimen measured. An expedient naming convention in the event that a file name can have a maximum of eight characters from the operating system is shown in the table in FIG. 6. It is preferred that the information implicitly contained in the file name, for example about the state of manufacture, is also contained in the source file itself, in order to simplify the further processing of the data. Basically, it is not necessary to include this information contained in the file name itself in the respective source file, since this information is extracted from the source file and extracted for the import into the database during the extraction of the user data of interest and its restructuring User data can be added. It is also conceivable that during the restructuring, missing information is queried by a person performing / monitoring the restructuring by a restructuring program and added to the extracted useful data.

It is assumed in the following that the at least one measuring station provides the measurement data in the form of simple text files in each case the measurement data for source data containing only one measured test object. Fig. 7 shows an example of a printout of such a source file. It is the measurement protocol of a Zeiss coordinate measuring station. The data of the source file can be divided as shown in Fig. 8. The source files, referred to below as protocols consist of a file or log header 130 and a file or protocol hull 132 in FIG. 7, only a few, located 130 subsequent lines of which are shown in the file header. The file header and the body of the file each contain useful data 134 and 136, respectively, and residual data that are not of interest for further evaluation, such as derived sizes 138 , comment lines 140 , outline characters and text formatting control characters, such as the one line end control character CARRIAGE RETURN.

The protocol header user data is so-called "master data", which contains superordinate information relating to the individual test specimen, the test specimen type, the measurement process, etc. In the example of FIG. 7, the following master data are included in the file header 130 : drawing number 1234, development status A, modification date of the technical drawing November 24, 1997, the examiner who carried out the measurement (name PXXX. J), the date (September 17, 1997), on which the measurement was carried out, the test specimen number identifying the test specimen (PART NR 1001), the production status (raw), the list of characteristics on which the measurement is based (LIST 1001) and a machine number identifying the measuring station (MNR 1001).

The file contains many details that are no longer of interest for further processing, since not only the measured values of interest are logged, but also the approaching of the positions to be scanned onto the test specimen by means of the scanning head of the coordinate measuring station. The only useful data of long-term interest in the fuselage section shown are contained in the lines identified by arrows 150 and 152 , which will be discussed in more detail below. The lines are divided into columns, which are indicated at the end of the log header with a respective column name. The column ADR contains a line count of the measuring routine of the measuring station, with a line counter generally being assigned several successive lines. Line 150 is the third line to line counter 10 and can be identified by address 10.03 in body 132 . Line 152 is the first line to line counter 11 and can be identified by address 11.01.

Other columns of interest in the body of the file 132 are the following: The column BEZ contains the characteristic number assigned to a respective measured value from the characteristic list on which the measurement is based. It is striking that lines 150 and 152 each contain the same characteristic number 38 . This is because, in the exemplary embodiment, the feature number designates an object to be measured or a design of the respective test object to be measured, for example a pin or an opening for which several measurement results are obtained, such as the height and diameter of the pin or the depth and diameter the opening. The "individual features" corresponding to exactly one measured value can be identified via the address, in the example the addresses 10.03 and 11.01. As far as unambiguous, the individual features could also be identified via the information contained in the SY column, which indicates the dimension of the respective measured value.

The column ACTUAL DIMENSION contains the measured value (actual value) for the respective individual characteristic. The NOMINAL DIMENSION column contains the target value, for example the value for the size in question, which is actually provided according to the design drawing on which the component is based. The columns O.TOL and U.TOL indicate an upper and a lower tolerance value. The tolerance deviation is contained in the ABW column. However, this is a derived variable that can be determined from the information ISTMASS, NENNMASS O.TOL and U.TOL and is not part of the useful data if the data is classified according to FIG. 8.

According to the exemplary embodiment of the present invention described here, the useful data are to be transferred from a plurality of source files in the manner of FIG. 7 into a database in order to be able to access the individual measurement results in relation to features and components. In the exemplary embodiment described here, it is provided that the user data are imported into a relational database. A suitable database is, for example, the Microsoft Access database developed by Microsoft. It is not possible to import the source files as text files directly into this database. For the import into this database, the user data must be brought into a structure corresponding to the relational data model. For this purpose, the user data are transferred to correspondingly structured import files (also called structure files) that correspond to the relational database model. The data preparation can take place, for example, as indicated schematically in FIG. 9. The source files are transmitted by remote data transmission or by means of portable data carriers to a computer (PC) on which the data preparation (block 160 ) of the source files takes place to structure files and on which the database program used preferably also runs. It could be that after the source files have been processed into structure files (import files), they cannot be imported into the database immediately, for example because individual information is missing in individual source files or certain specifications have not been met. In this case, fine data processing (block 162 ) can also take place, for example using a spreadsheet program. The importable import files are then imported into the database (block 164 ).

The type and structure as well as the number of import files to be created depends on the database system used (for example Microsoft Access) and the structure of the database. In the exemplary embodiment, it is assumed that the relational database comprises four database tables (entities), which are indicated schematically in FIG. 10. The database table "measurement data", designated 160 , is based on the user data from the body of the file and has the columns drawing number ZNr, test item number TNr, development status EZSt, production status FZSt, measuring station MNr, address in the body of the file (formed from the line number, for example the addresses 10.03 and 11.011, feature list number lIST characteristic number BEZ, dimension SY, measured actual size, setpoint nOMINAL MASS, upper tolerance O.TOL and lower tolerance U.TOL. the 167-designated database table "master data" includes, in addition to the columns ZNr, part no, EZSt, FZST, MNr four further columns, which include the name of the inspector (PRFNAM), the date of the measurement (PFRDAT), the update date of the technical drawing (AENDAT), the date of the import of the prepared data record into the database (IMPDAT) and the sum of the source data Specify the data records read out (IMPSTZ) The database table "Characteristics lists" designated with 168 gives the respective characteristics list in its columns n number (LIST), the number of the respective characteristic (BEZ), a description of the characteristic (BES) and any comments (BEM) on the characteristics. The database table "machine list" designated with 169 contains in one column the measuring station numbers (machine numbers MNr) assigned to the measuring stations and in the MCD column a company-internal identification of the respective measuring station. In the exemplary embodiment described here, the data to be transferred to the tables "feature lists" and "machine list" are manually imported into the database. An essentially automated process is therefore provided only for the restructuring and import of the measurement data and the master data.

The data contained in the individual table rows of the database tables are uniquely identified by a respective unique primary key, which consists of the attributes shown in bold and underlined in FIG. 10. For the measurement data table, the primary key (ZNr, TNr, EZSt, FZSt, MNr, ADR) is the primary key (ZNr, TNr, EZSt, FZSt, MNr), for the table "Master data", for the table "Feature lists" Primary key (LIST, BEZ) and the primary key (MNr) is provided for the "Machine list" table.

It is noticeable that the primary key of the table "master data" as Foreign key is contained in the primary key of the "Measurement data" table. The tables are based on the relational data model linked, and relationships between the tables are specified.

The database tables are normalized Database tables that of the first normal form, second normal form, third Normal form and Boyce-Codd's normal form are sufficient. Both normal forms mentioned are terms from theory relational databases. The ones expressed by these normal forms Normalizations are used to avoid redundancies and Anomalies in the database.

In the exemplary embodiment described below with reference to FIGS. 11 to 14, the useful data contained in the file header 130 and in the file body 132 for a plurality of source files are converted into a common master data import file and a common measured data import file, the master data import file being the one in FIG 10 contains the master data table 167 of FIG. 10 and the measurement data import file contains the data to be imported into the measurement data table 166 of FIG. 10. The structure of the import files corresponds to the assigned database table, i.e. they are organized as tables with the same columns as the respective database table. One possibility of how the data preparation of method step 160 of the flowchart of FIG. 9 can be carried out is given in FIGS . 11 to 14.

Fig. 11 shows the overall flow of data processing. If the flowcharts are understood as procedures or programs, FIG. 11 shows the main procedure or the main program which calls two sub-procedures or sub-programs shown in FIGS . 12 to 14 several times.

According to the main procedure, it is provided that a master data import file and a measurement data import file are first created or, if such files already exist, opened (step 170 ). A first source file is then opened (step 172 ). The master data is then read from the log header and written to the master data import file (step 174 ). Step 174 represents the flowchart or the sub-procedure of FIGS . 12 and 13, which will be explained separately.

The measurement data are then read from the log body and written to the measurement data import file (step 176 ). Step 176 represents the flow chart or sub-procedure of FIG. 14.

After step 176 has been completed , all user data are read from the source file so that the source file can be closed (step 178 ). If not all source files have been processed, the process returns to step 172 , in which the next source file is opened. Steps 174 , 176 and 178 are then repeated.

If, on the other hand, it is determined in 180 that all source files have been processed, the import files are then closed (step 182 ) and the process in FIG. 11 is ended. The import files can now be imported into the database (step 164 in FIG. 9), possibly after a data processing (step 162 in FIG. 9).

The reading out of the master data from the file header (protocol header) can be carried out, for example, as illustrated in FIGS. 12 and 13. The readout depends on how the master data is contained and identified in the file header. In the example ( FIG. 7), the useful data (master data) of interest in the file header are identified by keywords that can also be referred to as hint words and are recorded in a predetermined order in the file header, with the keywords and the associated information in separate, immediately successive lines in the file header 130 are included. The information associated with the keywords, such as the number (1234) associated with the KEY (drawing number) keyword, is thus immediately below the keyword in the line following the line of the keyword. It can be the case that the positions of the respective keyword and the associated data are specified within the relevant line. However, this is not mandatory. It could therefore be that the positions of the keywords and the associated data fluctuate from source file to source file, for example because different data are recorded in the log header for different components. Nevertheless, due to the convention that the data belonging to the keyword is contained in a position clearly defined by the keyword in the following line, the master data can be uniquely identified in the log header and taken from it.

The reading of the master data begins with an internal counter being initialized to the value zero (step 184 ). The first line, that is to say the data up to the first CARRIAGE RETURN, is then read from the currently open source file (step 186 ). A keyword defined by the counter is then searched for in the line read (step 188 ). The first time through this process step 188 , this is the first keyword from the keywords ZEICH to ADR, that is the keyword ZEICH. If this keyword is not contained in the line, the next line is read from the source file (step 186 ) and the search step 188 is repeated. If, on the other hand, it is found in 190 that the keyword is contained, it is examined in 192 whether it is the keyword ADR, that is to say the last keyword. The last key word ADR indicates that the file header has been completely processed so that the master data read from the source file are stored in the master data import file (step 194 ) and the routine of FIGS. 12 and 13 is exited.

If, on the other hand, the keyword found in the line read in step 186 (line A) is not the keyword ADR, the internal counter j is increased by 1 and the next line is read out from the source file (step 196 ). According to the convention given above, the data associated with the keyword found are contained in this line (line B) at a position defined by the position of the keyword in line A. This master data is then read from line B in step 198 and stored in a field defined by the internal counter j in an output line. This output line corresponds to a table line in the master data import file organized as a table.

In step 200 , the next keyword is then searched for in line A, ie the keyword STATUS during the first pass. If it is found in 202 that this keyword is not contained in line A, this means that the line (line A) read in step 186 has been completed. The process therefore returns to step 186 , in which the next line is read from the source file, which in turn is referred to as line A below.

If, on the other hand, the next keyword (the keyword STATUS during the first run) was found in the line, the internal counter is increased by 1 in step 204 . In step 206 , the master data associated with the keyword found are then read out from the currently valid line B and stored in the associated field of the output line.

The rest of the process depends on whether row A has now been completed. If it is determined in 208 that this is the case, the process returns to step 186 and the next line is read as line A from the source file. On the other hand, if the currently valid line A has not yet been completed, the process returns to step 200 , in which the next keyword in the line is searched for.

Depending on how many lines the protocol header has and how many keywords and associated data are contained, the line containing the keyword ADR (line identified by arrow 131 in FIG. 7) is finally read out from the file header 130 during a specific execution of step 186 . The flowchart of FIGS . 12 and 13 is based on the premise that the key word ADR is the last key word, which only indicates the end of the file head, to which no data to be read out from the file head are assigned and which is the only key word in one line of the file head. This keyword is then found in 188 and the decisions YES in 190 and YES in 192 lead to step 194 , in which the finished output line is written into the master data import file. The procedure is then exited without closing the source file.

This is followed by reading the measurement data from the log body and writing it to the measurement data import file (step 176 , cf. FIG. 14). Immediately after entering the routine of FIG. 14, the decision in 210 is "NO"; the source file does not end immediately after the processing of the log header has ended. In step 212 , the next line is then read from the source file, now from the body 132 . The content of the BEZ column of this row is then read in step 214 . In step 216 , it is then checked whether the data read from the BEZ column represents a non-zero numerical value. If this is not the case, it means that the line read in 212 does not contain any user data to be extracted. The process then returns to decision 210 . If, on the other hand, the data read out is a non-zero numerical value (only numerical values greater than zero occur), this means that the line read in 212 contains useful data to be extracted. Then the data contained in the columns ADR, SY, actual size, nominal dimension, and O.TOL U.TOL be read in 218, which together with the read in step 214 from the column BEZ, the characteristic number data indicating the user data of this line. In step 220 , the user data SY, ISTMASS, NENNMASS, O.TOL and U.TOL are then stored in the respectively assigned fields of an output line together with the keywords ZEICH,. . . Master data belonging to the MNR from the protocol header, which were passed to routine 176 by routine 174 via the main routine of FIG. 11 and with the attribute ADR, which together with the master data form the primary key of the measurement data database table 166 . The ADR attribute specifies the "address" of the data within the log body and consists of the line counter read from the ADR column from the log body, supplemented by an index that identifies the lines belonging to the same line counter. The formation of the attribute ADR is not specified in steps 218 and 220 of FIG. 14. In step 218 , after reading out the data from the row, it is determined whether there is a numerical value in the column ADR. If this is the case, this numerical value is supplemented by the index 01, the numerical value and the index being separated by a dot. In the case of line 152 in FIG. 7, the attribute 11.01 is thus formed.

If, on the other hand, the ADR column does not contain a numerical value, this means that the currently processed file body line is assigned to the same line counter as the line processed immediately before it. An internal counter defining the row index is then incremented and a corresponding attribute is formed. In the case of line 150 in FIG. 7, this is line attribute 10.03.

The output line thus formed corresponds to a table line in the measurement data database 166 . The output line is then stored in 220 in the measurement data import file. The process then returns to decision 210 . If the source file has not yet ended, the procedure is repeated as described. If, however, the source file has ended, the sub-procedure 176 is exited. The source file is then processed and is closed in step 178 of the main procedure.

At the end of the procedure in FIG. 11, there is a master data import file and a measurement data import file which contain all the useful data contained in the source files in a form suitable for import into the database. An example of the measurement data import file is shown in FIG. 15. The first two lines after the heading line of this table contain the user data from lines 150 and 152 of the source file in FIG. 7 and the primary key which uniquely identifies this user data. If one speaks of one-to-one here, then this should express that there is a one-to-one relationship between the primary key and the associated other data of the respective table row. This means that a specific data record is assigned to the primary key, to which no other primary key refers. Only one primary key is assigned to each data record.

FIG. 16 shows a database table corresponding to the measurement data database table 166 of FIG. 10, which was built up by importing several import files of the type shown in FIG. 15. The measurement data database table contains the measurement results for different component types, different development states and for different production states. As a rule, the table will contain the measurement results for several component test specimens of a component type.

FIG. 17 shows an extract from a database table corresponding to the master data database table 167 in FIG. 10. The master data taken from the source file of FIG. 7 are included in the table line following the title line.

An excerpt from the feature list database table 168 of FIG. 10 is shown in FIG. 18. The table section shows part of the data imported from the feature list 1001 into the database table. This list of features was the basis of the measurement, the measurement data of which is contained in the source file shown in FIG. 7. The feature number 38 occurring in lines 150 and 152 of the source file of FIG. 7 is explained in more detail in the table line identified by arrow 230 .

A reproduction of an example for the database table "machine list" 169 of FIG. 10 can be dispensed with, since this table only assigns a company-internal identification MCD to the measuring station numbers MNr.

It is easily possible to structure the database differently. For example, it could be useful to specify the nominal dimensions and tolerances to keep a separate database table, so that the measurement data table would only contain the pure measurement data. There are basically many Possibilities like a database according to the relational data model can be structured.

The database containing the measurement data enables a large number of different evaluations on the basis of the measurement data, and in particular different individual measurement results can also be easily linked. A measurement data information system 240 which enables such an evaluation is shown in FIG. 19. It comprises a database 242 formed by the database, which in the exemplary embodiment under consideration comprises database tables 166 , 167 , 168 and 169 . The database is managed by a database management system DBMS 244 , which has a functionality 246 for importing data into the database. The database management system also provides an interface for one or more user programs 248 . A user program enables the aforementioned evaluations of the measurement data, as well as a visualization of the measurement data and the evaluation results. It is particularly expedient if the user program 148 enables statistical evaluations. The user program can run on the same computer as the database programs. However, it is also possible for the database programs to run on a server which is accessed by assigned clients. A database system distributed over several computers in a network could also be used.

It should also be mentioned that the data preparation from the source files to the import files (step 160 of FIG. 9) can also be carried out using the UNIX programming tool AWK or the DOS software GAWK of the GNU project of the "Free Software Foundation". These programs, which are suitable for the manipulation of character strings, make it possible to do without substantial re-coding of character string manipulation procedures.

An embodiment based on the GAWK tool for the DOS Operating system is given below. The ones to be processed Source files must be in a "Measured data" directory. The GAWK Program (GAWK.EXE) operates programs EDITBAT.AWK and CONVERT. AWK, and the operating system MS-DOS sets programs EDITBAT.AT and KONVERT.BAT um.

The program KONVERT.AWK is started once by the batch processing program "KONVERT.BAT" in order to prepare exactly one source file. So that several source files are processed one after the other and their user data are written to assigned import files, in the event that the source files have a systematic name structure, repeated calls to the data processing programs can be automated. For each data processing session, a batch processing program called "master batch" can be edited, which calls the processing programs KONVERT.BAT and KONVERT.AWK as many times as there are source files to be processed. The programming of the master batch batch processing program can also be automated based on the systematic naming of the source files. The programs EDITBAT.BAT and EDITBAT.AWK can be used for this, which have so many command lines of the type
CALL CONVERT [Name Root] [File Counter] in the master batch program generate how source files are to be processed in a session. The calling master batch batch program is given a name of the type

[Name stem] _ALL.BAT.

This batch processing program is generated for each processing session and controls the processing of the source file to be processed in the session. Fig. 20 illustrates the flow for data processing. The EDITBAT.BAT program calls up individual information about the existing source files that have to be entered manually. The requested information on the name master and the counter of the first or last source file are made available to the EDITBAT.AWK program. The program uses the user information to create the master batch program of the type [name stem] _ALL. BAT that converts the programs. Controls BAT and KONVERT.AWK. The content of the master batch program could be, for example, excerpts:

CALL CONVERT PROH1001;
CALL CONVERT PROH1002;
CALL CONVERT PROH1003.

The master batch program containing these commands would have the name PROH_ALL.BAT. Of course, the programs KONVERT.BAT and KONVERT.AWK can also be called up manually, as indicated as an option at the end of the flowchart in FIG. 20.

Every call of the program KONVERT.BAT, be it by a Call command in the master batch program or by a manual Call, causes the respective source file to be restructured using the actual preparation program "KONVERT.AWK". The Command line "CALL KONVERT PROH1001" from the master batch program activates the manipulation program via the "KONVERT.BAT" program "KONVERT.AWK" to prepare the source file "PROH1001.TXT".

If, for example, 25 source files are prepared, 26 database-compatible import files (structure files) are created. In contrast to the exemplary embodiment in FIGS . 11 to 14, in the exemplary embodiment based on the GAWK tool, a separate measurement data import file is generated for each source file. The master data taken from the 25 source files, on the other hand, are transferred to a common master data import file. The structures of the various measurement data import files and the master data import file correspond to the structure of the measurement data import file and the master data import file of the exemplary embodiment in FIGS . 11 to 14. As far as any data required for the structure of the import files is missing in the source files, the import files become supplemented with fields based on user information during the data preparation session so that the import files are structurally identical to database tables 166 , 167 , 168 and 169 .

An example of how the above-mentioned batch processing programs "EDITBAT.BAT", "EDITBAT.AWK", "KONVERT.BAT" and "KONVERT.AWK" could be encoded is shown in FIGS . 21 to 25. No further explanation is required, since the coding is immediately understandable for the programmer familiar with the GAWK tool or the UNIX operating system on the basis of the preceding explanations.

In summary, the invention relates to a method for measuring a A plurality of each having several features of interest Components of at least one component group using at least one Measuring station, which provides measurement data in electronic form, and for Providing the measurement data in a component and feature-related form enabling electronic evaluation. It is suggested that Measurement data in electronic form in at least one database-compatible To provide data structure that electronic access to the Measurement results for individual features of interest of individual components enables. The invention further relates to a based on database-compatible data structure of a measurement data information system.

Claims (26)

1. A method for measuring a plurality of components of at least one component group, each having a number of features of interest, using at least one measuring station which provides data, including measurement data obtained by measuring a respective component, in electronic form, and for providing the measurement data in one component - and feature-related electronic evaluation enabling form, comprising the steps:

• - definition ( 118 ) of the features of interest to be measured in the components,
• Measuring ( 124 ) the components by means of the measuring station with regard to the features of interest,
• - Providing ( 126 , 128 ) the measurement results in electronic form in at least one database-compatible data structure, in particular in a database ( 166 , 167 , 168 , 169 ; 242 ), which enables electronic access to the measurement results for individual characteristics of individual components that are of interest.

2. The method according to claim 1, characterized in that the at least one database-compatible data structure ( 166 , 167 , 168 , 169 ) is based on the relational or object-oriented data model. 3. The method according to claim 2, characterized in that at least one database-compatible data structure of a table structure or object structure, each of which corresponds to a table line or a data record corresponding to an object a specific one measured component a clearly identifying component key (ZNr, TNr, EZSt, TZSt) contains.   4. The method according to claim 3, characterized in that at least one database-compatible data structure is a table structure comprises, each a table row of this table structure corresponding data set only one measured value of a certain one Characteristic of a certain component and the characteristic clearly identifying characteristic key (ZNr, TNr, EZSt, FZSt, ADR) contains. 5. The method according to claim 4, characterized in that at least one table structure is provided in which in each Table line of the component key and the characteristic key as parts of a certain feature of a certain component is unique identifying key (ZNr, TNr, EZSt, FZSt, MNr, ADR) are included. 6. The method according to any one of claims 3 to 5, characterized characterized that the key the component after underlying drawing number (ZNr) or / and State of development (EZSt) and / or state of manufacture (FZSt) clearly identified. 7. The method according to any one of claims 3 to 6, characterized characterized in that the key is used for the measurement of the Component used measuring station (MNr) and / or the measuring conditions clearly identified. 8. The method according to any one of claims 3 to 5, characterized characterized in that a component group several similar components includes. 9. The method according to any one of the preceding claims, characterized characterized that target values in the database-compatible data structure  or / and tolerances or / and information on the dimension of the respective Measured value or / and information on the date of the measuring process or / and Information on at least one person involved in the measurement or / and information on the prevailing during the measurement Measurement conditions are recorded. 10. The method according to any one of the preceding claims, characterized in that at least one list of features of features to be measured in the individual components is set up before the measurement ( 118 ) and in the database-compatible data structure information on the respective measurement underlying feature list and / or the feature list itself be included. 11. The method according to any one of the preceding claims, characterized characterized in that the measuring station the measurement results in a database-compatible, suitable for import into a database Provides data structure and the measurement results in a database, especially relational or object-oriented database, imported become. 12. The method according to any one of claims 1 to 11, characterized characterized in that the measuring station the measurement results in a Database, especially relational or object-oriented Database, writes. 13. The method according to any one of claims 1 to 10, characterized characterized in that the measuring station containing the measurement results Source data in a data model of the database used not corresponding structure or in a generally not provides a database-compatible structure.   14. The method according to claim 13, characterized in that user data from the source data is automated and transferred electronically into the at least one database-compatible data structure ( 160 , 164 ). 15. The method according to claim 14, characterized in that the user data are imported into a database, in particular a relational or object-oriented database, by means of the at least one database-compatible data structure ( 160 , 164 ). 16. The method according to claim 14 or 15, characterized in that the source data contain user data of interest ( 134 , 136 ) and non-interesting residual data ( 138 , 140 ), of which only the user data are transferred to the database-compatible data structure. 17. The method according to claim 16, characterized in that the Source data from the measuring station in a possibly format-free file, if necessary Text file, in which the user data is provided by Notice data, possibly notice signs or notice words, are marked and / or in which the user data are defined Positions are arranged. 18. The method according to any one of claims 13 to 17, characterized characterized in that the measuring station for each measured component File containing measurement results for the characteristics of interest provides. 19. The method according to claim 14 and claim 18, characterized characterized in that to generate the at least one that Database-compatible user data for several components Data structure automates a majority of the files provided processed in one go, preferably in such a way that  at least one database-compatible data structure is generated which Contains user data for several components. 20. The method according to claim 18 or 19, characterized in that the file comprises a file header ( 130 ) containing data relating to the measured component and / or the measurement process and / or the component group and a file body ( 132 ) containing the measurement results. 21. The method according to claim 20 and claim 3, characterized in that useful data is transferred from the source data into at least one table structure ( FIG. 15), in the table rows of which a component key that uniquely identifies the measured component is recorded, which at least partially relates to the component File header ( 130 ) data extracted. 22. The method according to claim 21, characterized in that at least one table structure ( Fig. 15) is provided, in the rows of which a measurement result for a particular feature of a particular component is contained and in which the component key is unique to the feature by a feature attribute identifying key is supplemented, the feature attribute being based at least in part on data taken from the file body ( 132 ). 23. The method according to any one of the preceding claims, characterized characterized in that the measurement of the components at least partially automated. 24. The method according to any one of the preceding claims, characterized characterized in that the measuring station is a coordinate measuring station.   25. The method according to any one of the preceding claims, characterized characterized in that components, especially vehicle components or / and parts of vehicle components, in different Development and manufacturing conditions are measured. 26. Measurement data information system, comprising:

• a computer arrangement with at least one assigned mass storage device,
• a database ( 242 ) obtained by application of the method according to one of claims 1 to 25 with at least one database file held on the mass storage device, which contains measurement results for a plurality of components of at least one component group each having several features of interest,
• a database management system ( 244 ) running on the computer arrangement and managing the database,
• - At least one database application ( 248 ), which is used to access measurement data and / or to evaluate measurement data and / or to visualize measurement data and / or to evaluate measurement data, is running on the computer arrangement.