Fuel Management Dashboard Development (SJ)-2
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
Fuel Management Dashboard – Development Scope (SJ)
1. Project Overview
* The development covers 1 site and 1 fuel tank only.
* This is not a new system being designed from scratch.
* MST already has experience developing similar dashboard functionality.
* MST will provide the existing dashboard reference, wireframe, architecture, APIs, business logic and functional requirements.
* The developer is primarily required for coding, integration, testing and deployment.
2. MST Will Provide
* Existing dashboard reference.
* Dashboard wireframe/design.
* Solution architecture.
* Functional requirements.
* Business logic.
* Required API access.
* Data mapping.
* Common identifier between the two data sources.
* Reporting requirements.
* Testing/acceptance requirements.
* Technical direction.
3. Developer Responsibility
* Front-end development.
* Back-end development where required.
* API integration.
* Data processing and matching.
* Dashboard functionality.
* Reporting and automated email functionality.
* User administration.
* Testing and corrections.
* Deployment.
* Documentation and source-code handover.
Development responsibility:
Coding → Integration → Testing → Deployment → Documentation
4. API and Data Requirements
Only 2 API integrations are required.
Fuel Management API
Will provide:
* Current fuel level.
* Historical fuel levels.
* Fuel deliveries.
* Fuel issues/dispensing transactions.
* Daily fuel reconciliation.
* Dates, times and quantities.
* Vehicle/asset identifier required for matching.
Asset & Vehicle Details API
Will provide:
* Asset/vehicle details.
* Asset/vehicle type.
* Odometer.
* Distance travelled.
* Asset/vehicle identifier.
Data Matching
* The two APIs will be linked using a common identifier.
* Fuel transactions will be matched to the corresponding vehicle/asset.
* The combined dashboard data will include:
Fuel Issued → Vehicle/Asset → Asset Type → Odometer → Distance Travelled
5. Dashboard Functions
1. Dashboard Framework – 12 hours
* Follow MST-provided wireframe.
* 1 site and 1 fuel tank.
* Dashboard cards, tables and charts.
* Date/time filtering.
* Responsive browser display.
2. Fuel Management API Integration – 10 hours
* Connect required API endpoints.
* Retrieve and process fuel data.
3. Fuel Levels – 10 hours
* Current level.
* Historical levels.
* Tank capacity and percentage full where required.
* Level trends.
4. Fuel Deliveries – 8 hours
* Delivery date/time.
* Delivered quantity.
* Historical deliveries.
* Search/filtering.
5. Fuel Issues – 8 hours
* Transaction date/time.
* Quantity issued.
* Vehicle/asset identifier.
* Historical transactions.
* Search/filtering.
6. Asset & Vehicle Details API Integration – 9 hours
* Vehicle/asset details.
* Asset type.
* Odometer.
* Distance travelled.
7. Fuel and Asset Data Matching – 9 hours
* Match fuel transactions to the correct vehicle/asset using the common identifier.
8. Daily Fuel Reconciliation – 7 hours
* Reconciliation data supplied through the Fuel Management API.
* Historical reconciliation.
* Date filtering.
* Variance/exception display where required.
* MST will provide the reconciliation logic.
9. Reporting & Automated Email – 9 hours
* Fuel reports.
* Delivery reports.
* Reconciliation reports.
* Asset/vehicle reports where required.
* Excel/PDF export where required.
* Automated email reports.
10. User Administration – 5 hours
* User login.
* User administration.
* Role-based access.
11. Final QA/UAT – 4 hours
* API testing.
* Data-matching testing.
* Dashboard testing.
* UAT corrections.
12. Deployment & Documentation – 4 hours
* Production deployment.
* Source-code handover.
* Technical and deployment documentation.
Current MST working estimate: approximately 95 productive development hours.
6. Development Hours
* Expected development range: 80–125 productive hours.
* Current MST working estimate: approximately 95 productive hours.
* MST's estimate is based on our own experience developing similar dashboard functionality.
* The estimate also reflects the limited scope of 1 site and 1 fuel tank.
* The freelancer must provide their own estimated hours against the same components.
* Any significant difference from MST's estimate must be technically explained.
7. Timeline
* Maximum delivery period: 4 weeks.
* The 4 weeks represent the delivery window, not automatically 4 full weeks of billable development hours.
* Daily progress visibility required.
* Weekly working demonstrations required.
Indicative sequence:
* Week 1 – Dashboard framework and Fuel Management API.
* Week 2 – Fuel levels, deliveries and issues.
* Week 3 – Asset & Vehicle API, data matching and reconciliation.
* Week 4 – Reporting, automated email, users, QA/UAT and deployment.
8. Commercial Framework
* Indicative project budget: AUD 4,000–5,000.
* Expected development rate: AUD 40–50 per productive hour.
* Expected development range: 80–125 productive hours.
* Current MST estimate: approximately 95 productive hours.
* Final cost will be based on approved productive hours and agreed hourly rate.
* The developer should propose the minimum practical resources required.
* A 6-person development team is not required.
9. Quotation Requirements
Please quote against the development components above and provide:
* Coding hours.
* Integration hours.
* Testing/QA hours.
* Deployment/documentation hours.
* Total productive hours.
* AUD hourly rate.
* Cost per milestone.
* Total project cost in AUD.
* Number of resources required.
* 4-week delivery plan.
* Assumptions or items requiring clarification.
The final comparison will be:
MST Estimated Hours → Freelancer Hours → Variance → AUD Rate → Milestone Cost → Total Cost
10. Ownership and Delivery
* MST will own all source code, scripts, database structures and project documentation.
* Source code must be progressively committed to an MST-controlled repository.
* MST must have access to the source code throughout development.
* No subcontracting without MST approval.
* MST/customer information and API credentials must remain confidential.
* Code must be maintainable and documented.
MST provides:
Architecture → Wireframe → Reference Dashboard → API Access → Business Logic → Data Mapping → Functional Requirements → Technical Direction
Developer provides:
Coding → Integration → Testing → Deployment → Documentation
1. Project Overview
* The development covers 1 site and 1 fuel tank only.
* This is not a new system being designed from scratch.
* MST already has experience developing similar dashboard functionality.
* MST will provide the existing dashboard reference, wireframe, architecture, APIs, business logic and functional requirements.
* The developer is primarily required for coding, integration, testing and deployment.
2. MST Will Provide
* Existing dashboard reference.
* Dashboard wireframe/design.
* Solution architecture.
* Functional requirements.
* Business logic.
* Required API access.
* Data mapping.
* Common identifier between the two data sources.
* Reporting requirements.
* Testing/acceptance requirements.
* Technical direction.
3. Developer Responsibility
* Front-end development.
* Back-end development where required.
* API integration.
* Data processing and matching.
* Dashboard functionality.
* Reporting and automated email functionality.
* User administration.
* Testing and corrections.
* Deployment.
* Documentation and source-code handover.
Development responsibility:
Coding → Integration → Testing → Deployment → Documentation
4. API and Data Requirements
Only 2 API integrations are required.
Fuel Management API
Will provide:
* Current fuel level.
* Historical fuel levels.
* Fuel deliveries.
* Fuel issues/dispensing transactions.
* Daily fuel reconciliation.
* Dates, times and quantities.
* Vehicle/asset identifier required for matching.
Asset & Vehicle Details API
Will provide:
* Asset/vehicle details.
* Asset/vehicle type.
* Odometer.
* Distance travelled.
* Asset/vehicle identifier.
Data Matching
* The two APIs will be linked using a common identifier.
* Fuel transactions will be matched to the corresponding vehicle/asset.
* The combined dashboard data will include:
Fuel Issued → Vehicle/Asset → Asset Type → Odometer → Distance Travelled
5. Dashboard Functions
1. Dashboard Framework – 12 hours
* Follow MST-provided wireframe.
* 1 site and 1 fuel tank.
* Dashboard cards, tables and charts.
* Date/time filtering.
* Responsive browser display.
2. Fuel Management API Integration – 10 hours
* Connect required API endpoints.
* Retrieve and process fuel data.
3. Fuel Levels – 10 hours
* Current level.
* Historical levels.
* Tank capacity and percentage full where required.
* Level trends.
4. Fuel Deliveries – 8 hours
* Delivery date/time.
* Delivered quantity.
* Historical deliveries.
* Search/filtering.
5. Fuel Issues – 8 hours
* Transaction date/time.
* Quantity issued.
* Vehicle/asset identifier.
* Historical transactions.
* Search/filtering.
6. Asset & Vehicle Details API Integration – 9 hours
* Vehicle/asset details.
* Asset type.
* Odometer.
* Distance travelled.
7. Fuel and Asset Data Matching – 9 hours
* Match fuel transactions to the correct vehicle/asset using the common identifier.
8. Daily Fuel Reconciliation – 7 hours
* Reconciliation data supplied through the Fuel Management API.
* Historical reconciliation.
* Date filtering.
* Variance/exception display where required.
* MST will provide the reconciliation logic.
9. Reporting & Automated Email – 9 hours
* Fuel reports.
* Delivery reports.
* Reconciliation reports.
* Asset/vehicle reports where required.
* Excel/PDF export where required.
* Automated email reports.
10. User Administration – 5 hours
* User login.
* User administration.
* Role-based access.
11. Final QA/UAT – 4 hours
* API testing.
* Data-matching testing.
* Dashboard testing.
* UAT corrections.
12. Deployment & Documentation – 4 hours
* Production deployment.
* Source-code handover.
* Technical and deployment documentation.
Current MST working estimate: approximately 95 productive development hours.
6. Development Hours
* Expected development range: 80–125 productive hours.
* Current MST working estimate: approximately 95 productive hours.
* MST's estimate is based on our own experience developing similar dashboard functionality.
* The estimate also reflects the limited scope of 1 site and 1 fuel tank.
* The freelancer must provide their own estimated hours against the same components.
* Any significant difference from MST's estimate must be technically explained.
7. Timeline
* Maximum delivery period: 4 weeks.
* The 4 weeks represent the delivery window, not automatically 4 full weeks of billable development hours.
* Daily progress visibility required.
* Weekly working demonstrations required.
Indicative sequence:
* Week 1 – Dashboard framework and Fuel Management API.
* Week 2 – Fuel levels, deliveries and issues.
* Week 3 – Asset & Vehicle API, data matching and reconciliation.
* Week 4 – Reporting, automated email, users, QA/UAT and deployment.
8. Commercial Framework
* Indicative project budget: AUD 4,000–5,000.
* Expected development rate: AUD 40–50 per productive hour.
* Expected development range: 80–125 productive hours.
* Current MST estimate: approximately 95 productive hours.
* Final cost will be based on approved productive hours and agreed hourly rate.
* The developer should propose the minimum practical resources required.
* A 6-person development team is not required.
9. Quotation Requirements
Please quote against the development components above and provide:
* Coding hours.
* Integration hours.
* Testing/QA hours.
* Deployment/documentation hours.
* Total productive hours.
* AUD hourly rate.
* Cost per milestone.
* Total project cost in AUD.
* Number of resources required.
* 4-week delivery plan.
* Assumptions or items requiring clarification.
The final comparison will be:
MST Estimated Hours → Freelancer Hours → Variance → AUD Rate → Milestone Cost → Total Cost
10. Ownership and Delivery
* MST will own all source code, scripts, database structures and project documentation.
* Source code must be progressively committed to an MST-controlled repository.
* MST must have access to the source code throughout development.
* No subcontracting without MST approval.
* MST/customer information and API credentials must remain confidential.
* Code must be maintainable and documented.
MST provides:
Architecture → Wireframe → Reference Dashboard → API Access → Business Logic → Data Mapping → Functional Requirements → Technical Direction
Developer provides:
Coding → Integration → Testing → Deployment → Documentation
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.