The e-SCM Portal : a rapid implementation, a measurable rise in productivity, and an immediate return on investment.
Solid and direct feedback within an average of 4-6 months
The e-SCM intuitive user solution is user-centric and quick to master.
The interface engine facilitates the integration and data exchange with the ERP
Application architecture and hosting infrastructure
Methodology – Business Expertise
The e-SCM methodology : born from our experience and the reality of your “Business”
The project launch Prototype
- Train users in the basic concepts of e-SCM
- Define the data exchange processes
- Set out the specifications and functional configuration
- Define a roll-out plan and the perimeters of a Pilot project
Validation of core model on a Pilot testing project»
- Set up a working environment for a manageable “business” context
- Document the relevant configuration rules and validate best practice
- Ensure automated data feed procedures and data exchange
Deployment of e-SCM
- Approve the principles and the organisation of operational deployment
- Deploy the Portal in the other product divisions using the Core Model parameters
- Provide user support to all purchasers and suppliers
The methodology relies upon organisation and didactic tools tried and tested throughout each of our projects.
- The Quality Project lan defines the tasks and roles of the project team and schedules the implementation
- Business consultants run workshops designed to translate your internal processes with standard e-SCM configuration
- Technical documentation explains and specifies e-SCM data entry interfaces as well as export interfaces for updating the ERP
- The architectural study allows us to recommend the infrastructure of Extranet hosting and forecast the progression of the solution
- The administration console records the user roles and access rights of each internal or external user.
- The integration of elements of the graphic charter, as well a multilingual dictionary adapted to your own company jargon allow the personalization of the e-SCM interface.
- Handling by the end users is facilitated by functional documentation which recall best practice and the configured operating principles
- While providing assistance for deployment we can share best practices to enhance configuration and take use of e-SCM further.
- Skills are transferred to the purchasers who in turn tutor the suppliers in handling the solution in their own environment.
Our consultants’ expertise guides the implementation of e-SCM in your company in harmony with your organisation They are capable of taking initiative to structure and standardize your procedures of supply management.
- Functional Workshops : Define the configuration of processes linked to different types of purchase
- We work by analysing the differences between your expressed requirements and the standard functions of the solution. After analysis your requirements are examined in the context of the global structure of e-SCM
- Technical workshops are provided on how to catalog your data and define exchange rules with the ERP
- We have set up a series of interfaces to ensure the seamless synchronisation of data between the different environments.
- e-SCM administrative workshops : Manage all e-SCM rules, rights and processes with one console.
- Define role-based access on the Portal as well as milestones and parametres of supervision to send out alerts or messages at each step of the process.
ERP integration and data exchange
Our is a ‘non-intrusive’ solution based on SOA principles which interfaces with and integrates into transactional information systems.
e-SCM complète efficacement l’ERP pour la gestion des données opérationnelles et la traçabilité des évènements collaboratifs.
Data exchange principles between e-SCM and the ERP prevent any redundancy in the management of e-SCM reference data.
- The ERP has control of data right up until a supplier order is placed and retakes control as soon as production is completed.
- e-SCM feeds data into the ERP to update modifications validated during production monitoring.
Various kinds of data integration are possible :
- The data importation interfaces from the ERP to e-SCM :
- The importation of reference data for every new season (suppliers, collection catalogues, technical data, Incoterms…)
- Importation of P.O’s validated in the ERP/li>
- e-SCM export interfaces for updating the ERP
- The integration of data to modify supplier purchasing management data (quantity produced, milestone dates, mode of transportation…)
- The integration into the WMS of packing list data with unique packing references for a more effective monitoring of reception and warehouse inventory planning
- External data stream with freight forwarders and suppliers in particular.
- With freight forwarders : Via web services or file/doc interfaces to automate milestone monitoring and transportation dates
- With suppliers, for them to input e-SCM data into their own systems, and to input into e-SCM packing lists generated by their own internal production system
e-SCM data is available for download from different screens (confirmation, production, etc.) Data extraction is carried out in the background and the user is notified when download of the generated file is available.
Application software and hosting infrastructure
The design of the e-SCM solution is centred around 4 priorities :
- Its user-friendliness and intuitive ergonomy for use in Extranet and multilingual modes.
- The agility and versatility of configuration, managed by an administrative console.
- The reliability of data exchange to work in harmony with the existing information system.
- The robustness and scalability ensuring the availability of the solution.
The e-SCM Supplier Portal was designed on a robust application architecture which conforms to J2EE standards.
- The application architecture is built on an Open Source base, composed of the TomCat, MySQL or MariaDB, Open LADAP and Talend version Open Source applications.
- The development code is based on Java J2EE frameworks and has been optimised to run with the Firefox, Google Chrome and Edge browsers.
- The HTML code of the screens has been optimized to limit display time, even for use with a low-speed Extranet.
The sleek graphic charter offers light and spacious screens providing better visual comfort and optimisation of display time.
- All the screens are in ´responsive design’ and graphic objects are vectorized for a better portability in mobility
- It is possible to configure the zones and display-order on the main screens in order to adapt the content to actual needs and to facilitate use, ie. lists, detail, filters, advanced filters, fast entry, date popup.)
- The recommended deployment infrastructure is based on a server dedicated to the application web server, with a second for storing data.
The recommended deployment infrastructure is based on a server dedicated to the application web server, with a second for storing data.
Depending on the conclusions drawn from the architectural study and the operating rules defined with the DSI, the infrastructure can be partitioned onto different servers to optimize performance, or ensure an operational backup.