EuroSpec. Documentation. Manual Data-exchange. Explanation of Appendix data-exchange (Excel document)

Transcription

1 EuroSpec Documentation Manual Data-exchange Explanation of Appendix data-exchange (Excel document) EuroSpec Page 1 Specification for air conditioning Date: December 2013 of Railway Vehicles

2 Manual Data-exchange Draft edition Original language: English SNCF-MOBILITES, Rail Delivery Group (RDG), Deutsche Bahn (DB), Nederlandse Spoorwegen (NS), Danske Statsbaner (DSB), Österreichische Bundesbahnen (ÖBB), Schweizerische Bundesbahnen (SBB) Paris, London, Munich (München), Utrecht, Kopenhagen (København), Vienna (Wien), Bern July 2017 Photo Cover Page: SNCF EuroSpec Page 2 Documentation explanation to Appendix (Draft)

3 Table of Contents 1 Purpose Basis for the data model Description of Tables Table 1: Delivery statistics Table 2: Bill of Material (BOM) Table 4: Part master data Table 5a: Document master data Table 5: Part - Document relation Table Description of the Attributes (field titles) used in the tables Glossar how to deliver How to Handle changes Data model (the tables itself) references... 9 EuroSpec Page 3 Documentation explanation to Appendix (Draft)

4 This manual is an explanation of Appendix: Exchange model of BOMs and technical documents. The Appendix is part of EuroSpec Documentation (V2), paragraph 'Drawings and description of the vehicle and its components' EuroSpec Documentation (as published on 1 PURPOSE In railway business, the customer requires, as part of a contract, technical documents in a certain form. In order to support co-operation and effective exchange of information between customers, suppliers and partners, it is necessary to have the document exchange requirements precisely defined. (EN , ) Most railway operating companies use for the management of their documentation a computer based system that requires the information in an exact and specific data model to link the material data with the document data and the dedicated document. For an efficient and safe maintenance of the vehicles and its components it is of great importance to find quickly and reliably the correct documents and related information. The data model is designed to ensure the exchange of documentation (within the meaning of Eurospec Documentation 4) between computerized databases with the goal of as less data lost as possible. It includes always the delivery statistics, the bill of material, the document data and the referred documents. The Goal of this data model is, that it can be used along the hole supply chain and to ensure an easy and safe import/export into/out of PLM-Systems. It shall make the hole process of purchasing the right part for the right reason more comfortable and safe for all involved. These requirements have been drawn up in order to accommodate: the large variety of users; ease of transfer of information and related documents; This data model is based on the EN and the FSF The working group of Eurospec Documentation elaborated, simplified an enhanced the model. In the description of the tables you can find the reference to the EN and the FSF It should enable the participating companies to automatically exchange computer based data. 2 BASIS FOR THE DATA MODEL Starting point for the exchange model is the principle that the design of a train is represented by the physical decomposition of the train to its lowest part necessary to maintain the train during its complete lifetime. This decomposition is called the (engineering) Bill of Material, the BOM. Each level/part in this structure needs to be specified. This specification consist of features (meta data) and/or documents that are linked to the part and/or its position in the structure. Each document needs to be linked to the level it describes. Eg. the drawing of the complete assembly of the bogie needs to be linked to part for the complete bogie, and the production drawing for the wheelset axle needs to be linked to the part for the bare axle. This whole set of data can be addressed to as the as designed configuration of the train EuroSpec Page 4 Documentation explanation to Appendix (Draft)

5 The exchange model is designed in such a way that it can enable the supplier of the data to break down the configuration out of his own data systems into logical tables and enables the receiver of the data to rebuild the configuration in his own data systems, without loss of information 3 DESCRIPTION OF TABLES As explained in paragraph 2, the data of the configuration is split into different tables in order to exchange the data in an electronic way. In this paragraph these tables will be explained in more detail. Note: If there is a (ID #) in the field definition then this is a reference to the ID in that table 3.1 Table 1: Delivery statistics This table contains the delivery statistics for each data delivery. Purpose is to enable the receiver to check the completeness of the data 3.2 Table 2: Bill of Material (BOM) This table contains the information to build the bill of materials (actually: the bill of parts within the terminology of this document). It is based on the so called parent-child relations of the parts (defined in table 4a and 4b). This means that each line of the database consists of the part number of that position (the child) and the part number of the part it belongs to (the parent). Each child then can be the parent for a deeper level in the structure, until the lowest level in the structure is reached. So the highest part in the structure is only a parent (top item) and the lowest parts are only children. In this way the structure can be built to a complete tree. At a certain level, the list of subordinated children are also often referred to as the parts list for an assembly (the parent). In figure X the relation in a simple parent-child table is shown graphically. Figure 1 parent-child relation EuroSpec Page 5 Documentation explanation to Appendix (Draft)

6 The BOM also contains all the information that is specific to a certain position in the structure (to the specific use of a part in the structure). For example the classification according to EN : the classification for a bolt will be different depending its position in the BOM. Used in the car body the coding will be A and used in the running gear the coding will be E. This in contrast to the information that is specific for the part itself, which can be found in table Table 4: Part master data This table contains all the relevant meta data for each part that is used in the BOM (table2). Purpose of the meta data is to uniquely identify and specify a part. Each part can only have one occurrence in the table. Furthermore each part in these tables should have at least one occurrence in the BOM (table 2), meaning that there cannot be a part that is not part of the BOM. 3.4 Table 5: Material Document relation This table contains all the relevant data to link the documents defined in table 5a to the parts defined in table 4a and 4b. The relation can be a n-to-n relation, meaning that a document can be linked to several parts and a part can have several documents linked to it.( n:n(or n:m) means 'many-to-many'; each row in table 5 (a document) can reference many rows in table 4 (part), and each row in table 4 (part) can reference many rows in table 5(documents) 3.5 Table 5a: Document master data This table contains all the relevant meta data for each unique document that is linked to a part in the BOM. Purpose of the meta data is to uniquely identify a document. Each document can only have one occurrence in the table. Furthermore each document in this table should have at least one occurrence in table 5b, meaning that there cannot be a document without a link to a part. Explanation about final customer identification 3.6 Table 6: Text records This table contains all the relevant data to link text messages to parts in table 4a and 4b and/or certain positions in the BOM (table 2). 4 DESCRIPTION OF THE ATTRIBUTES (FIELD TITLES) USED IN THE TABLES In each table the first line shall contain the identifiers of the fields. In this paragraph all the identifiers are explained in more details. EuroSpec Page 6 Documentation explanation to Appendix (Draft)

7 Since a lot of data sets can be transferred, the type of record and the contents of the fields shall be clearly indicated. It is recommended to separate the records with a line break (values 13 and 10 in ISO/IEC ) and to separate the fields with tabulators (value 09 in ISO/IEC ) and send the data in the character set specified in the field "character set" in the shipment statistic. Empty fields are specified as empty character strings. A special indicator for empty fields shall be agreed between the contracting parties ID: The ID number is unique within a table. Each record of a data file shall be unique relating to the marked primary key fields in all the tables. Therefore, it shall be ensured that when this data is transferred to other partie it stays unique.\ Field Name (Feature): This field contains the name of the ID in English language. Field description (Feature definition): This field contains the designation of the Field Name in English language. It shall describe the Field Name of the appropriate field. Remarks: This field is for any additional text information. (value) nomenclature what to enter in the fields: Data Type: to define the type of the data. C=alphanumerical, D=date and/or time, N=numerical Data Length: It is the length of the data in number of character encoding. Link to EN15016 and FSF460-29: to refer to the number of the ID of field number of EN15016 or FSF for each ID of this standard. Note: The link should be the ID and the table number. 5 GLOSSAR SI: System International The International System of Units is the modern form of the metric system, and is the most widely used system of measurement. It comprises a coherent system of units of measurement built on seven base units. It defines twenty-two named units, and includes many more unnamed coherent derived units. The system also establishes a set of twenty prefixes to the unit names and unit symbols that may be used when specifying multiples and fractions of the units. Part Unique identification of a part. It is used for a spare part, spare, service part, repair part, or replacement part. It is an interchangeable part that is kept in an inventory and used for the repair or replacement of failed units. Item An item represents a record to define a part (a software or hardware) on the bill of materials. Assembly Number of part fitted together to perform a specific function. BOM Bill Of Material: presentation of the constituents in a product structure with the possibility to adapt the level of decomposition to actual need. It is a list of the raw materials, sub-assemblies, intermediate assemblies, sub-components, parts to manufacture an end product. A BOM is used for communication between manufacturing partners, or confined to a single manufacturing plant. A BOM can define products as they are designed (engineering bill of materials), as they are ordered (sales bill of materials), as they are built (manufacturing bill of materials), or as they are maintained (service bill of materials or pseudo bill of material). The BOM is also known as the formula, recipe, or ingredients list. In this standard, as BOM we mean the engineering bill of materials. EuroSpec Page 7 Documentation explanation to Appendix (Draft)

8 Manufacturer Entity that makes a good through a process involving raw materials, components, or assemblies. Such goods may be used for manufacturing other, more complex products, such as rolling stock. OEM Original Equipment Manufacturer (OEM) is a company that makes a part or subsystem that is used in another company's end product. For example, if manufacturer A makes power cords that are used on computers made by manufacturer B, manufacturer A is the OEM. Supplier In this standard, the supplier is the contract partner for the receiver of the data model. Customer The customer is the contract partner for the one who delivers the data model. Final customer The customer at the end of the chain. Figure 2 supplier-customer relation 6 HOW TO DELIVER The data model is to be delivered as a csv-file with all the documents referenced. The data storage medium is to be defined due to the delivered data volume. The data exchange can also be handled via an interface between the system of the supplier and the system of the costumer The used separator has to be a character that is only used as separator and not as other character in the delivered data. 7 HOW TO HANDLE CHANGES Within the purchasing project of new rolling stock, the configuration information will not be delivered in one time, and there also will be changes to the configuration during the project. Therefor it is necessary to define the way in which addition and/or changes in the information need to be delivered. When there is a change, or an addition to a certain part of the BOM, the complete structure of that part of the BOM needs to be delivered for the new situation, including the changed and non-changed parts. In order to determine which part of the BOM is EuroSpec Page 8 Documentation explanation to Appendix (Draft)

9 involved, it needs to be investigated upwards and downwards to the point where the changed has damped. In this way the complete existing part of the BOM can be replaced by the new part of the BOM based on the format of table 2. Furthermore for all new parts, documents en there relation the information should be delivered through the tables 4a, 4b, 5a, 5b and 6. These tables only need to contain the new information. When there are changes in the parts or document master data, only the tables with the changed information need to be delivered in order to replace the existing information for the new information. 8 DATA MODEL (THE TABLES ITSELF) See separate document 9 REFERENCES FSF 460 EuroSpec Page 9 Documentation explanation to Appendix (Draft)

10 EuroSpec EuroSpec stands for European Specifications for railway rolling stock. The activity is an initiative of several European train operating companies (TOC). The main focus is on trains consisting of self-propelled carriages, using electricity as the motive power (EMU). SNCF-MOBILITES, Rail Delivery Group (RDG), Deutsche Bahn (DB), Nederlandse Spoorwegen (NS), Danske Statsbaner (DSB), Österreichische Bundesbahnen (ÖBB), Schweizerische Bundesbahnen (SBB) Paris, London, Munich (München), Utrecht, Kopenhagen (København), Vienna (Wien), Bern June 2015