This is one of 4620 IT projects that we have successfully completed with our customers.How can we support you?
Replacement process delivery stop from legacy system for logistics service providers
Brief description
New customer applications are implemented on Google Cloud Platform (GCP). To replace a process in the central application (legacy system), delivery stop files in CSV format or cancellation notifications should be received by the 'Lobster_data' middleware for shipment orders that have already been notified. For each individual order, another in-house system is requested using API to check whether this order service can be booked. After receiving record-level feedback, receipt files are generated in CSV format for specific clients and made available for distribution.
Supplement
The new 'delivery stop' process to be implemented replaces the process in the legacy system, thereby achieving consolidation with comparable processes of other existing in-house applications that request the same API. If the delivery stop is successfully booked in the system requested by 'Lobster_data', it stores the relevant information in the defined message format in a dedicated Kafka topic. This serves consuming systems such as the shipment order system, which represents a holistic view of the shipment orders, as an input source for delivery stop orders for notifications. PTA handles the file transformation part in the middleware 'Lobster_data'.
Subject description
A notification is an advance notice for the delivery or collection of a shipment. The processing of notifications is a highly critical business function. In the event of a failure, there is a risk of immediate, significant financial and possibly reputational damage. Therefore, there are corresponding requirements for the resilience of the applications involved. If a customer of a shipment order wants to stop delivery, he sends a file with one or more delivery stop orders or, alternatively, a cancellation notification for each shipment order. After evaluating the feasibility of the delivery stop, if successful, the associated information for exchange in the sense of Event Driven Architecture (EDA) will be published as a technical event in a Kafka topic. After processing the data for consolidated information in the shipment order system, the updated shipment order business object is made available to the customers in the group.
Overview
- Industries traffic / transport / logistics
- Specialist tasks data analysis, digitalization, EDI, eletronic data exchange, interfaces, Migration, order processing
- DV tasks Migration
- System environment Client/Server, Cloud Computing, Middleware
- Procedure model Kanban
- Development/ test tools Microsoft Edge Browser, Notepad++, Postman Rest Client,
- Operating systems Windows 10
- Standard software JIRA
Project start18.06.2024
Contact
PTA GmbH Head Office
Weberstraße 2-4
D-68165 Mannheim
© Copyright 2024 PTA GmbH | All rights reserved | Imprint | Privacy | Legal notice | Values & Code of Conduct
