K92 Fuel Management Dashboard

1. Project Overview
Development and improvement of the K92 Fuel Management Dashboard.
MST will provide the existing dashboard reference.
MST will provide the wireframe/design requirements.
MST will provide the existing business logic and requirements.

The developer will primarily be responsible for:
Coding
Integration
Testing
UAT corrections
Deployment
Documentation

This project is based on existing dashboard functionality and experience.
This is not a completely new system design project.

2. Dashboard Functions
Current fuel levels.
Historical fuel levels.
Daily fuel usage.
Opening fuel readings.
Closing fuel readings.
Fuel deliveries where applicable.
Fuel issues/consumption where applicable.
Daily fuel reconciliation.
MFN vs SmartFill fuel-level comparison.
Midnight opening and closing comparison.
Fuel variance identification.
Historical fuel usage trends.
Required KPIs.
Dashboard summary.
Reporting.
Export functionality where required.

3. Reconciliation and Validation
Implement the reconciliation logic provided by MST.
Validate opening fuel balance.
Validate fuel deliveries.
Validate fuel issues/consumption.
Validate closing fuel balance.
Calculate and display required variances.
Identify reconciliation exceptions.
Validate dashboard calculations against source data.
Test historical data and calculations.
Correct identified data or calculation issues.

4. Proposed Development Hours
MST's initial working estimate is based on our previous experience developing and working with the K92 dashboard.
Dashboard Framework & Updates – 12 hours.
Fuel Data Integration – 10 hours.
Fuel Levels & Historical Data – 10 hours.
Fuel Deliveries – 8 hours.
Fuel Issues / Consumption – 8 hours.
Daily Fuel Reconciliation – 10 hours.
MFN / SmartFill Comparison – 8 hours.
KPI & Variance Reporting – 7 hours.
Reporting & Export – 6 hours.
Testing / UAT – 8 hours.
Deployment & Documentation – 4 hours.

Total Proposed MST Working Estimate – 91 productive hours.
The 91 hours are a working estimate and not an automatic allocation of billable hours.
The freelancer must provide their own estimated hours against the same development areas.
Any significant difference from the MST estimate should be explained and technically justified.

5. Development Responsibility
Coding.
Data/API integration.
Dashboard development.
Reconciliation logic.
Data validation.
Testing and QA.
UAT corrections.
Deployment.
Documentation.
Source-code handover.

6. Timeline
Maximum delivery period – 4 weeks.
Weekly progress updates required.
Weekly working demonstrations required.
Development milestones must be clearly defined.
Milestone payments will be linked to completed and accepted work.

7. Budget
Indicative project budget – AUD 4,000–5,000.
Expected development rate – AUD 40–50 per productive development hour.
Proposed MST working estimate – approximately 91 productive hours.
Freelancer to provide:
Total estimated hours.
AUD hourly rate.
Cost per milestone.
Total project cost.
Resources required.
4-week delivery plan.

8. MST Provides
Existing dashboard reference.
Wireframe/design requirements.
Existing business logic.
Data requirements.
API/data access.
Reconciliation requirements.
KPI requirements.
Technical direction.
Testing and acceptance requirements.

9. Resource Requirement
A 6-person development team is not required.
The freelancer should propose the minimum practical resources required.
The proposed resources should be sufficient to complete the defined scope within 4 weeks.
Additional resources should only be proposed where technically justified.

10. Ownership
MST will own the source code.
MST will own the project documentation.
MST will own scripts and database structures developed for the project.
Source code must be progressively committed to an MST-controlled repository.

MST must have access to the source code throughout development.
All project data and API credentials must remain confidential.
Full source-code handover is required upon completion.