Условие:
WHAT NEEDS TO BE DONE
Draw up a contextual diagram reflecting the ERP-system architecture and its users, upload to Google Drive, share it to be available for all and send us the link.
COMMENTS CLARIFYING THE ASSIGNMENT
There is an ERP-platform consisting of a back-office for managing travel products and business products along with a front-office element offering the entire search&book workflow for the end user, booking management and reporting functionality. The platform is used by tour operators (incl. Destination Management Companies (DMCs)), travel agencies, tourism content suppliers, corporate customers and individual travellers. Tour operators have the option to manage static content displayed on the frontend via a CMS solution.
The back- and front-office parts communicate with one another via an API, but share a common database. The back-office functionality is partially available via the front-office. The back-office contains API integrations to various external payment gateways, currency conversion plugins, CRMs and financial tools, a reporting module and is also connected to one of the key platform entities — travel supplier API aggregator ‘GP Travel Hub’. It works as a standalone solution bringing together over 80 supplier APIs (for hotels, transfers, flights, cruises, car rentals and other products, including connections to major GDSs).
The platform API can be made available to partner companies for creating their own custom front-offices and exporting the needed data into their own systems.
The back- and front-office solutions can be configured for the needs of each tour operator via Super Admin modules by CSM or Support Specialists (these are unavailable to the customers).