Middleware Optimization API: Rentman and Optiflow Integration
Budget: $30 – $250 USD
Project Title: Fix and Cleanup of Middleware Between Rentman and Optiflow
Project Description:
We have a middleware system that connects Rentman (https://api.rentman.net/) with Optiflow (https://developer.conundra.eu/). This middleware, hosted at optiflowtest.luxonos.nl, facilitates the synchronization of transport orders between the two systems. We have 1 issue and want to clean-up the project for future maintenance.
Current Workflow:
1. Transport orders from Rentman are imported into Optiflow via a cron job.
2. Optiflow calculates the optimal route, and once "released," the cron job exports the planned route back to Rentman.
3. This process works, but with a critical issue:
Issue:
Currently, the export from Optiflow to Rentman is not limited to released schedules. Instead, it always sends the most recent planning whenever the cron job runs, regardless of its status. This causes two problems:
• Manual adjustments in Rentman (after the Optiflow planning has been imported) are overwritten every time the cron job runs.
• Any unreleased changes in Optiflow are sent prematurely to Rentman.
Required Fixes:
1. Improve the Optiflow-to-Rentman export so that only released schedules within a specific time window are processed. Optiflow has released an update that supports this feature (documentation: https://release.redoc.ly). The cron job should only pick up schedules that have been released since the last cron job run.
2. Optimize and clean up the middleware at optiflowtest.luxonos.nl.
o The current middleware is a modified copy of a warehouse system because many features were already build in that system (but are not needed in this system)
o The unnecessary code should be removed, leaving only the essential functionality.
o The best approach could be to first fix the main (1) issue and then rebuild the middleware step by step while using the existing system as a reference.
o The goal is a simpler, more maintainable system.
Requirements:
• Modify the export process to follow the new release-based time window system from Optiflow.
• Clean up the middleware by removing unused warehouse-related functionality.
• Ensure that the final system is lean, efficient, and maintainable.
• No documentation exists for the current middleware, so the developer must analyze and extract the necessary parts from optiflowtest.luxonos.nl.
• Proper logging should be implemented to track cronjob executions and data transfers.
• Documentation should be written in order to make maintenance in the future easier.
Skills Required:
• Strong experience with PHP and backend development.
• Experience working with APIs (Rentman & Optiflow).
• Understanding of cron jobs and scheduling processes.
• Ability to analyze existing code and refactor it efficiently.
• Familiarity with debugging and logging to track system behavior.
Deliverables:
• A fully functional export process that respects Optiflow's release and time window constraints.
• A cleaned-up middleware that only contains the necessary functionality.
• Proper documentation/comments to ensure maintainability.
We’d love to hear how you’d approach this project and your estimated timeline and price!
Project Description:
We have a middleware system that connects Rentman (https://api.rentman.net/) with Optiflow (https://developer.conundra.eu/). This middleware, hosted at optiflowtest.luxonos.nl, facilitates the synchronization of transport orders between the two systems. We have 1 issue and want to clean-up the project for future maintenance.
Current Workflow:
1. Transport orders from Rentman are imported into Optiflow via a cron job.
2. Optiflow calculates the optimal route, and once "released," the cron job exports the planned route back to Rentman.
3. This process works, but with a critical issue:
Issue:
Currently, the export from Optiflow to Rentman is not limited to released schedules. Instead, it always sends the most recent planning whenever the cron job runs, regardless of its status. This causes two problems:
• Manual adjustments in Rentman (after the Optiflow planning has been imported) are overwritten every time the cron job runs.
• Any unreleased changes in Optiflow are sent prematurely to Rentman.
Required Fixes:
1. Improve the Optiflow-to-Rentman export so that only released schedules within a specific time window are processed. Optiflow has released an update that supports this feature (documentation: https://release.redoc.ly). The cron job should only pick up schedules that have been released since the last cron job run.
2. Optimize and clean up the middleware at optiflowtest.luxonos.nl.
o The current middleware is a modified copy of a warehouse system because many features were already build in that system (but are not needed in this system)
o The unnecessary code should be removed, leaving only the essential functionality.
o The best approach could be to first fix the main (1) issue and then rebuild the middleware step by step while using the existing system as a reference.
o The goal is a simpler, more maintainable system.
Requirements:
• Modify the export process to follow the new release-based time window system from Optiflow.
• Clean up the middleware by removing unused warehouse-related functionality.
• Ensure that the final system is lean, efficient, and maintainable.
• No documentation exists for the current middleware, so the developer must analyze and extract the necessary parts from optiflowtest.luxonos.nl.
• Proper logging should be implemented to track cronjob executions and data transfers.
• Documentation should be written in order to make maintenance in the future easier.
Skills Required:
• Strong experience with PHP and backend development.
• Experience working with APIs (Rentman & Optiflow).
• Understanding of cron jobs and scheduling processes.
• Ability to analyze existing code and refactor it efficiently.
• Familiarity with debugging and logging to track system behavior.
Deliverables:
• A fully functional export process that respects Optiflow's release and time window constraints.
• A cleaned-up middleware that only contains the necessary functionality.
• Proper documentation/comments to ensure maintainability.
We’d love to hear how you’d approach this project and your estimated timeline and price!