Background:
The IGH (Pressure Group of the Data Network for Household Technology) was founded in 1994 by ten companies in the household technology industry. The goal of the association is to develop an improved infrastructure for cross-company data communication in the Swiss household technology industry. 68 dealers and manufacturers in the household technology industry and the Swiss-Liechtenstein building technology association suissetec are now members of IGH. The contributions model of the IGH consists of a one-off admission fee of CHF 8,000 and an annual subscription of CHF 4,000.
As a virtually totally member-financed association, the IGH sees itself as obliged to handle the resources at its disposal in a frugal manner. The currently five-strong management board works in an honorary capacity. The management and the tasks of the secretariat have been outsourced to Apex Solutions AG as mandates, so that only effective costs are incurred here too, depending on project tasks. Should, for example, additional personnel resources be required within the scope of projects, external project partners are called in.
The Swiss household technology industry:
The household technology industry consists of the main areas of plumbing, heating, ventilation, air-conditioning and electrical engineering. The sales volume on the Swiss market is over CHF 2.5 billion for the plumbing and heating segments alone. The industry is characterised by a three-pronged sales market with manufacturers, dealers and fitters. Without the electrical engineering sector, which has not been represented in the IGH so far, market events are currently determined at manufacturer level by approximately 20 companies. The manufacturers mainly sell their products via 60 large trading companies. The fitters, which number approximately 5,500 to 6,000 companies, are predominantly small companies. The fitters’ clients are mostly architects or planners who manage new building or refurbishment projects.
DataExpert provides integration components for intercompany data exchange. The system can be used for communication between both fitters and dealers and between dealers and manufacturers (see Fig. 3.1).

Fig. 3.1: Integration with DataExpert
DataExpert is based on a customer-based client component and a provider-based server component. DataExpert transports data between the trading partners and the order is still processed in the sectoral solutions or ERP systems of trading partners.
Business perspective:
The three-pronged sales market with manufacturers, traders and fitters plays a key role in the household technology industry. The manufacturers produce the products required on the market and provide detailed technical product information. Dealers also play a key role, as the high number of fitters places considerable demands on logistics and customer care. Due to geographical proximity and long-standing contacts, many fitters have built up permanent links with dealers. A change in the roles and functions of the individual players through the solution is so far unforeseeable.
Process view:
In an ideal world, a project in the household technology industry usually starts with a call for tenders with respect to a new building or refurbishment project by an architect or planner. As the next step, one or several fitters’ enterprises prepare a bid as a rule. If need be, these companies access information from the appropriate product catalogues and often already obtain offers from dealers. If a fitter is awarded the contract by the planner, it submits an order to the dealer in question and then receives an order confirmation. When the order is called up for delivery, the fitter finally receives a delivery note and an invoice. The entire process is shown in Fig. 3.2.
As a rule, dealers and fitters exchange the messages stated in Fig. 3.2. Individual messages, such as the order call-off, may be omitted depending on the situation. Traditionally only fax, telephone or letter are used to communicate. Thus, media breaks occur, which lead to high processing costs, reduced data quality and long throughput times due to multiple entries, increased error probability and time-wasting.
DataExpert rectifies these inefficiencies by defining standards for all stated business messages and their electronic exchange. The process sequence is not changed by DataExpert. The roles of provider and customer are laid down in such a way that the system can be used between both fitter (customer) and dealer (provider) and between dealer (customer) and manufacturer (provider).
The data exchange between planner/architect (customer) and fitter (provider) is handled using SIA451 and not via DataExpert. SIA451 is a data format recommendation from CRB (Swiss Head Office for Building Rationalisation) for specifications and bids in the building industry.
Application view:
DataExpert is largely based on the existing system components. The actual order processing operation and data storage are still carried out in the sectoral solutions or ERP systems. These systems communicate with the DataExpert components implemented at providers’ and customers’ premises. DataExpert carries out the validation and transfer of documents. A possibility for interplay between DataExpert and providers’ and customers’ application systems is shown in Fig. 3.3.
DataExpert consists of a server component which is installed at providers’ premises and a client component which is installed at clients’ premises, thereby creating a decentralised client server architecture where customer and provider can communicate with each other directly. A third party is not integrated into the transaction process.
Communication is based on Web services which are installed at the provider’s premises on a Microsoft IIS web server with ASP.net. The main client-based element is the method library DE_Transfer, which validates documents and calls up web services. DE_Transfer can be addressed via .net or COM? interfaces from the client’s application systems. DE_Treansfer provides the following methods for client applications:
Table 3.1: DE_Transfer methods which can be retrieved from customer applications

The WriteBizMsg method is called up to send a message to a provider. The message is transferred in XML format from the application to DE_Transfer. DE_Transfer validates the message and calls up the web service of the corresponding provider via SOAP (Simple Object Access Protocol). The message is stored in the server’s upload directory under a clear file name assigned by DataExpert .
To receive messages from a provider, a list of all messages which exist in the server’s download directory and are addressed to the relevant customer is first of all requested with the GetBizMsgList method. The list is transferred in XML format to the user’s application. By calling up the ReadBizMsg method, a specific message is then downloaded and also transferred to the customer application in XML format.
The DE_Transfer is also used by the provider in addition to the IIS web server and web services. Here it is used to read out the messages received from the web server’s upload directory and to file outgoing messages in the download directory.
Authentication:
DataExpert is designed in such as way as to only allow customers to initiate a data transfer. Whenever a method is called up, both the customer’s and provider’s identity is authenticated
When calling up a dataExpert method by means of a customer application, verification is first carried out based on the DataExpert client’s configuration file. User name and password as well as the user’s rights are automatically checked by the client. When the web services are then called up by the provider, an XML stream is transferred to the server, which contains customer ID and password. Before a customer’s message is saved on the server or a provider’s message is sent, identity and authorisation of the customer are checked by the server.
The administration of user and partner data is possible via special interfaces, via which configuration data can be accessed.
XML data standard
As none of the analysed standards fulfilled the requirements of IGH, its own SML system was defined for the DataExpert catalogues and business messages. The DataExpert catalogue standard is based on the Win_Expert catalogue standard and supplements this with additional product information. Providers are given the possibility to adjust the SML message system to a certain extent, with a few exceptions, in that data fields can be declared either as mandatory fields or optional fields. The system can load customer applications via the ReadSchema method.
Technical view:
Fig. 3.4 shows a possible system architecture for DataExpert. The web services are called up on the provider’s server via SOAP (Simple Object Access Protocol). If an X.509 certificate is available on the provider’s server, the SOAP messages can be transferred via an encrypted https connection. The X.509 certificate contains the provider’s PublicKey and information about the supported encryption process. By installing firewalls, the integrity of application systems is guaranteed.
The deployed .NET technology restricts the operating system environment to Windows systems. Owing to the dominance of Windows systems in the household technology industry, this is not seen as a problem and has tended to make integration into the existing system environment easier.

Fig. 3.4: Example of the system architecture of the DataExpert solution
As far as hardware is concerned, the client requires a Pentium 90 and at least 96 MB RAM. For the server, a Pentium 133 with at least 256 MB RAM is recommended. As DataExpert only provides communication and integration components, differing hardware requirements may exist due to the sectoral solutions or ERP systems used.