Electronic Fault Information System
EB Engineering Services ECU takes the next decisive step in the offboard solutions area: We offer you our service competency for the complete data handling of ECUs. The ideal linking of ECUs with the ultra-large databases (ULDB) world and the resulting client/server architectures.
- Reference project (1): Project prerequisites and architecture
- Reference project (2): Description of the individual work steps
- Innovative fault correction: Case-based reasoning
Reference project (2): Description of the individual work steps
The project environment as an overview:
EB Engineering Services ECU developed the system together with a renowned OEM customer as a an engineering service. This system is used for the electronic acquisition of fault information from testing systems in vehicle production and its combination with manually acquired causes. In this project, EB, with a team of approximately ten employees, in close technical cooperation with the customer, undertook the conception, the design, the implementation, the test and the roll-out of the system. In addition, EB is responsible for the training, maintenance and parts of productive operation of the system.
An ideal client/server solution
The aim of this project is the consolidation, standardization and improvement of existing database systems and their user interfaces. Data gathered, both manually and electronically, during the production and the reworking of faults and fault causes form the basis for an improved fault elimination process and a sophisticated statistical concept. For this purpose, the process, the type and the scope of the data to be collected, and a concept for supporting the process using an appropriate IT infrastructure, was specified in conjunction with the customer.
The provision of consistent data records is a central prerequisite for gathering statistics. During test system programming, testing steps and their results were previously entered with arbitrary text. A goal in this project was the uniform coding of the outputs using a common meta-language.
Distributed web application based on the Java 2 Enterprise Edition (J2EE) standard
The application for entering fault causes should not cause any additional license costs on client computers at fault-correcting workplaces. Furthermore, the maintenance and installation effort should be made centrally and kept as low as possible. Consequently, the application for entering fault causes, and thus the associated integrated administration tool, should be implemented as a distributed Web application (thin client, display using a standard Web browser). The distributed Web application was implemented based on the Java 2 Enterprise Edition (J2EE) standard and has a four tier architecture, where tiers II and III are not separated from the Application Server’s viewpoint. The IBM WebSphere Web Application Server (WAS) V6.0 Network Deployment (ND) is used as J2EE server.
The data from the testing systems and the fault cause are stored in an Oracle database system that forms the central element for system input. The connection of many third-party systems (provision of vehicle master data, testing systems) and the import of their data made the design of the logical and physical data model fairly complex.
The advantages of this EB system developed in close cooperation with the customer are:
- Migration from previously seven self-contained database solutions to a single system (replacement of obsolete systems and licence cost savings)
- Introduction of a standardized cross-factory and cross-line fault elimination process (symptoms and causes) for production
- Provision of systems that provide comparability with regard to the reporting and fault statistics of production locations (turntable production)
- Time saving thanks to the faster (fault) cause acquisition and search
- Scaling up of previous IT infrastructure to higher data volumes (> 500 GB database size)
EB Engineering Services ECU takes the next decisive step in the offboard solutions area: We offer you our service competency for the complete data handling of ECUs. The ideal linking of ECUs with the ultra-large databases world and the resulting client/server architectures.
- Reference project (1): Project prerequisites and architecture
- Reference project (2): Description of the individual work steps
- Innovative fault correction: Case-based reasoning
Reference Project (2): Description of the Individual Work Steps
The project environment as an overview:
EB Engineering Services ECU developed the system together with a renowned OEM customer as a an engineering service. This system is used for the electronic acquisition of fault information from testing systems in vehicle production and its combination with manually acquired causes. In this project, EB, with a team of approximately ten employees, in close technical cooperation with the customer, undertook the conception, the design, the implementation, the test and the roll-out of the system. In addition, EB is responsible for the training, maintenance and parts of productive operation of the system.
An Ideal Client / Server Solution
The aim of this project is the consolidation, standardization and improvement of existing database systems and their user interfaces. Data gathered, both manually and electronically, during the production and the reworking of faults and fault causes form the basis for an improved fault elimination process and a sophisticated statistical concept. For this purpose, the process, the type and the scope of the data to be collected, and a concept for supporting the process using an appropriate IT infrastructure, was specified in conjunction with the customer.
The provision of consistent data records is a central prerequisite for gathering statistics. During test system programming, testing steps and their results were previously entered with arbitrary text. A goal in this project was the uniform coding of the outputs using a common meta-language.
Distributed Web Application Based on the Java 2 Enterprise Edition (J2EE) Standard
The application for entering fault causes should not cause any additional license costs on client computers at fault-correcting workplaces. Furthermore, the maintenance and installation effort should be made centrally and kept as low as possible. Consequently, the application for entering fault causes, and thus the associated integrated administration tool, should be implemented as a distributed Web application (thin client, display using a standard Web browser). The distributed Web application was implemented based on the Java 2 Enterprise Edition (J2EE) standard and has a four tier architecture, where tiers II and III are not separated from the Application Server’s viewpoint. The IBM WebSphere Web Application Server (WAS) V6.0 Network Deployment (ND) is used as J2EE server.
The data from the testing systems and the fault cause are stored in an Oracle database system that forms the central element for system input. The connection of many third-party systems (provision of vehicle master data, testing systems) and the import of their data made the design of the logical and physical data model fairly complex.
The advantages of this EB system developed in close cooperation with the customer are:
- Migration from previously seven self-contained database solutions to a single system (replacement of obsolete systems and licence cost savings)
- Introduction of a standardized cross-factory and cross-line fault elimination process (symptoms and causes) for production
- Provision of systems that provide comparability with regard to the reporting and fault statistics of production locations (turntable production)
- Time saving thanks to the faster (fault) cause acquisition and search
- Scaling up of previous IT infrastructure to higher data volumes (> 500 GB database size)
EB Engineering Services ECU takes the next decisive step in the offboard solutions area: We offer you our service competency for the complete data handling of ECUs. The ideal linking of ECUs with the ultra-large databases world and the resulting client/server architectures.
- Reference project (1): Project prerequisites and architecture
- Reference project (2): Description of the individual work steps
- Innovative fault correction: Case-based reasoning
Reference Project (2): Description of the Individual Work Steps
The project environment as an overview:
EB Engineering Services ECU developed the system together with a renowned OEM customer as a an engineering service. This system is used for the electronic acquisition of fault information from testing systems in vehicle production and its combination with manually acquired causes. In this project, EB, with a team of approximately ten employees, in close technical cooperation with the customer, undertook the conception, the design, the implementation, the test and the roll-out of the system. In addition, EB is responsible for the training, maintenance and parts of productive operation of the system.
An Ideal Client / Server Solution
The aim of this project is the consolidation, standardization and improvement of existing database systems and their user interfaces. Data gathered, both manually and electronically, during the production and the reworking of faults and fault causes form the basis for an improved fault elimination process and a sophisticated statistical concept. For this purpose, the process, the type and the scope of the data to be collected, and a concept for supporting the process using an appropriate IT infrastructure, was specified in conjunction with the customer.
The provision of consistent data records is a central prerequisite for gathering statistics. During test system programming, testing steps and their results were previously entered with arbitrary text. A goal in this project was the uniform coding of the outputs using a common meta-language.
Distributed Web Application Based on the Java 2 Enterprise Edition (J2EE) Standard
The application for entering fault causes should not cause any additional license costs on client computers at fault-correcting workplaces. Furthermore, the maintenance and installation effort should be made centrally and kept as low as possible. Consequently, the application for entering fault causes, and thus the associated integrated administration tool, should be implemented as a distributed Web application (thin client, display using a standard Web browser). The distributed Web application was implemented based on the Java 2 Enterprise Edition (J2EE) standard and has a four tier architecture, where tiers II and III are not separated from the Application Server’s viewpoint. The IBM WebSphere Web Application Server (WAS) V6.0 Network Deployment (ND) is used as J2EE server.
The data from the testing systems and the fault cause are stored in an Oracle database system that forms the central element for system input. The connection of many third-party systems (provision of vehicle master data, testing systems) and the import of their data made the design of the logical and physical data model fairly complex.
The advantages of this EB system developed in close cooperation with the customer are:
- Migration from previously seven self-contained database solutions to a single system (replacement of obsolete systems and licence cost savings)
- Introduction of a standardized cross-factory and cross-line fault elimination process (symptoms and causes) for production
- Provision of systems that provide comparability with regard to the reporting and fault statistics of production locations (turntable production)
- Time saving thanks to the faster (fault) cause acquisition and search
- Scaling up of previous IT infrastructure to higher data volumes (> 500 GB database size)