Single database Schneider Electric product developing for CIS countries. API

 
 
 
 
 
 
 

Task:

Creation of a unified database of product of Schneider Electric for the CIS market and API design of access for partners..

Read more 
 
 

Goals:

  • Consolidation and processing of data from different sources (global database (France), the base of the file storage directory, SAP services company, CSV/XLS file-download);
  • RAEC integration;
  • Classifying with ETIM;
  • Development of a documented API to access the unified database;
  • Create training material for integration with the service;
  • Service authorization by the key;
  • Statistics module for database.

Schneider Electric has more than 100 product lines, more than 500 categories and over 50 000 items, information about them is stored in 7 different systems scattered around the world.

Data collection schema

The main problems faced by partners of Schneider Electric, trying to find information on products:

  • There is no centralized database;
  • Image, description and features stored in different databases;
  • Access to databases is restricted to partners;
  • There is no single API for accessing;
  • There is no possibility of integrating with services;
 

Schneider Electric appealed to us for help in creating a single database that would contain information about all 50 000 names of products:

  1. Reference/article;
  2. Technical details;
  3. Category;
  4. Images;
  5. CAD-drawings;
  6. Documentation sheets, Certificates;
  7. Datasheets and promo;
  8. Logistic information - stock status and quantity.

And to develop a mechanism for access by partners and suppliers.

Architecture development

Going deep in process, decompose into small parts. A single database that combines multiple sources of data we call OPS. API provides a machine interface, using it to interact with database servers.

Process schema

Prepare the interaction with the information donors:

  • Parsing by specific schedule from European databases (Global OPS, Ecat, etc);
  • Download from SAP logistics data;
  • Load information from CSV and XLS file;
  • Download of the classifications ETIM from RAEC;
  • The ETIM* codes mapping with existing products;
    *ETIM - international standard for the description of electrical goods. The 5th and 6th edition.
The principle of filling the item card

Programming. Open API. Pitfalls.

Such projects are very interesting for our programmers:

  • sophisticated interaction with many data sources,
  • design custom API for partners,
  • generation of products with the correlation of different types of information,
  • download the accompanying files (images, certificates, pdf brochures, CAD drawings).

The main task of the service - providing full information to partners. Developing API to interact with our system. Give partners a choice: implement two methods for XML and JSON.

Interaction with the database
Examples of JSON and XML requests

Facing with non-trivial problems:

  1. Service Global OPS falls under a massive parsing;
  2. Uploads from SAP are not correct;
  3. Loading of files - files are different, the duplication of information.

Developing the following solutions:

  1. Make data collection portional - requests pick up to 100-500 records, this avoids the breakage of the connection;
  2. Our programmers have dealt with the problem by writing additional processor uploads from SAP;
  3. Develop a unique label for the item duplicates removed.

 

Update

All the information in the API OPS must be not only complete, but also up-to-date. This customizable periodic updates from existing sources. When checking analyze the existing data - compare by date and completeness of the content.

Validating and loading data
Starting. Load test

Database services must withstand enormous loads when thousands of connections and uploads. The administrator debugs the system:

The administrator debugs the system Conducting load tests: connection, discharge, channel capacity
API documentation

For such services, focused on the use for partners, it is important to provide detailed and clear documentation.
To do this, we are describing in each command query examples:

Docs example

We don't just write detailed documentation, but went further and developed a clear how-to for a quick start of work with our service. After reading this document, even an inexperienced programmer can quickly integrate the power of the Schneider Electric service to your online store or online catalog. Examples for the most common tasks such as :

  • how to upload products catalog Schneider electric on the site;
  • loading of the goods (the description - the name and properties);
  • download images to products;
  • download images;
  • download documents for goods;
  • documents upload;
  • updates to products / images / documents;
How-to documentation example

Developing web service for the data downoad.

Using the database API OPS Schneider Electric partners can easily fill their services, such as online stores, catalogs, applications for designers, updated and extended information on products Schneider Electric. But not all partners are striving to fill their services. Some need information on specific rereferences (articles).
For their convenience, we have developed a web service, where the partner, having the key, can easily obtain information on required products and virtual them in any convenient format such as PDF, XLS, XML.

Web page

Information is the key of business. Summary.

This service does not have competitors Schneider Electric. It gives a significant business advantage. Partners can easily get information and integrates API OPS in their portals, online stores, catalogs. With this approach it is easier to provide equipment that is easier to sell, easier to use.

Explore another case

Subscribe for cases updates

When we will prepare new interesting case – we will send you a detailed letter. Subscribe here!
Теперь вы подписаны на обновления кейсов.