Electronic Data Interchange EDI

Project Background Diebold-Nixdorf (DN) has requested that FirstLink (FL) implement Electronic Data Interchange (EDI) integration in order to automate the creation, update, and resolution of preventive maintenance (PM) and break-fix tickets between DN and FL. In order to automate that stream of data, however, FL also needs to integrate with the master ticket system, RazorSync, through their existing Application Program Interface (API). Project Scope Implement fault-tolerant integration between FirstLink and DN (EDI) Implement fault-tolerant integration between FirstLink and RazorSync (API) Implement business logic to direct and monitor the flow of messages between the three parties, handle errors, and log messages for reconciliation and reporting High-Level Requirements According to the EDI Guide from DN, these are the basic communications messages to and from DN: • Vendor Activities to DN o Send Acknowledgement o Send Acceptance o Send Rejection o Send Commit o Send Arrived o Send Closed o Handle DN Error o Handle DN Success • Vendor Activities from DN o Receive assignment o Receive reassignment o Receive cancellation o Receive latest activity update According to the API documentation from RazorSync, these are the basic API functions. For each API, there are three possible calls: create, get, and update • Address API • Customer API • Work Order API • Service Request API • Service Item API Deliverables Following are the functions that need to be developed to interface between FL and DN: • Receive tickets from DN via EDI • Update tickets from DN via EDI • Receive tickets from DN via Excel • Update tickets from DN via Excel • Send ticket updates to DN via EDI • Handle DN success/error responses • Send success/error response to DN via EDI • Search, retrieve tickets? Following are the functions that need to be developed to interface between FL and RazorSync: • Create, Get, Update Address to Razor via API • Create, Get, Update Customer to Razor via API • Create, Get, Update Work Order to Razor via API • Create, Get, Update Service Request to Razor via API • Create, Get, Update Service Item to Razor via API • Receive ticket updates from Razor via API • Create tickets to Razor via Excel • Update tickets to Razor via Excel • Handle Razor success/error responses • Search, retrieve tickets? In addition to the EDI and API calls, implement business logic to direct and monitor the messages between the three parties, including error-handling (email notifications), transaction metering (for future billing), and message logging (for reconciliation and reporting). Must speak good English and we need this rushed ASAP.