Build overview
21 modules and go-live itemsThe last module, the Document Register, went live on 03.09.
Where it runs
CloudflareRebuilt automatically on every change. Production is defined but not created yet.
Checks
- Automated tests2,154
- Browser tests17
- Typecheck5 of 5
All of these run on every change before it can merge.
Pull requests merged per week
Weeks start on SundayEach point is one week. The busiest week, starting 30 August, finished offline capture, the document register and CI. The last week runs only to 17.09.
At a glance
Pull requests merged since the project started on 07.07
Merged since the last update on 19.07
Plants sharing one app, with plant colours fixed on every screen
Modules
Production actuals, plan versus actual, and when each plant last sent batch data.
One ticket per truckload, keyed by plant and batch number. Separate views for drivers, facilitators and supervisors.
Imported from the Schedule Master with its customer and site registries. Includes daily orders, weekly forecast and logistics trips. Edits to Excel-owned fields go through change requests.
The app accepts the live SQL feed, but the plant side is not switched on yet. Batch report upload stays as the fallback.
Imports Schedule, Staff, Fleet, Article and QC lab results, plus batch reports. Each import is previewed before it is committed, and flagged rows go to an exceptions queue.
One note per pour, linked to its schedule entry. The customer signs on screen and a signed PDF is stored.
Six gates per project. A load can only be dispatched for an approved project.
Daily checklists, which block dispatch when failed or missing, plus fault reports and the maintenance log.
A request list anyone can add to, with one person deciding.
Delivery sites on a map, sized by m³. Where the map tiles are hosted is still open (D14).
Cube samples through 7, 14 and 28 days, and the engineer decides pass or fail. Also lab result import, certificates, QC reports and the cube mold ledger.
The hardware exists but the software is not built yet. Driver taps feed the delivery timeline today, and GPS will fill the same fields.
Stock movements, with an alert when a material runs low.
DN125 pipeline register. The pump bucket quantity is still to be confirmed (D13).
The day-end operational report and the document register.
Incident reports come out as PDFs. Site surveys carry photos and a signature, and a submitted survey clears its project gate.
The office can see which tablets and phones have not synced.
Staff and asset registers, passport and visa expiry alerts at 60 and 30 days, and user accounts.
Decided: signed delivery notes are kept for one year, with a local backup (D23). Not built yet.
The database, file storage and user accounts for the team still need to be set up.
Device set-up, training for each role, then a first run with live loads.
Schedule module
The latest Schedule, Overview and Map improvements are merged into production. PowerMix Schedule runs as its own platform today — SharePoint Excel through Power Automate to Cloudflare — and the next major step is to fold it into the RMX OP APP alongside the rest of operations.
Schedule
Delivery planning by day, week and month, with the order detail behind each row.
Overview
Delivered volumes per plant, with a quarterly heat map in 100 m³ bands.
Map
Delivery sites with lot boundaries and labels where they exist.
Approved access
Cloudflare authentication, with Developer, Scheduler, Operations and Viewer roles.
On screen
Recreated, loopingWhat matters for the team
Latest improvementsClearer delivery reporting
Overview uses a single Filter button and one Delivered bar per plant. The quarterly heat map shows daily volumes in 100 m³ bands, on hover on desktop and on tap on mobile. Charts follow both themes.
Better schedule visibility
Today, Tomorrow, This Week, This Month and custom dates, according to role. Fridays and holidays entered in Excel column B display clearly without affecting delivery totals, analytics or map markers.
Useful details, connected to Map
Orders carry project time, site, survey, mix design, grade, cube test, delivery method, pump operator and volume, with contact details where the role permits. Select a delivery site and confirm to open its matching map location.
Improved location coverage
Schedule-linked markers include lot boundaries and labels where available. Island mapping covers Thilafushi, Gulhi Falhu and Villingili, plus a dedicated MPL Thilafushi Port location.
Excel remains the source of truth
Publish chainThe automated flow publishes schedule changes without anyone editing the application, and the dashboard refreshes every 60 seconds once imported data becomes available. Each user sees the views and details their role allows; a Viewer response leaves out Contact and Remarks.
Where we are heading
PowerMix Schedule → RMX OP APP01 · Team feedback
Check schedule details, holidays and map locations on your usual device, and tell us anything missing or wrong.
02 · Integration planning
Define how Schedule fits into the RMX OP APP: navigation, data flow and access permissions.
03 · Test and rollout
Test the integrated experience before an approved rollout to the main app.
If an older screen appears
Close and reopen the installed app, or do one hard refresh.
Integration is the stated direction, not completed work. Scope, timing and rollout will be confirmed separately. Release dates and test results come from the September handover; live deployment was not rechecked for this briefing.
Admin module
Staff and document records for both plants are now held in linked SharePoint registers. The workbook import is complete, missing staff details have been filled in, and every document view follows one layout.
Staff register
LiveOne register for both plants. Staff codes link each person to their document records.
Document register
LiveA separate view for each document type, alongside All Items and Renewal Due.
Consistent views
6 savedThe same staff-first layout across every view, with document details following.
Workbook import
TestedA reusable manual flow passed validation and a live run: 284 entries added, 40 existing entries preserved.
On screen
Recreated, loopingFrom Excel sheets to a working register
Preparation → import → remindersExtract and reconcile
Staff and document details were spread across Excel sheets and tedious to cross-check. The relevant data was pulled out, matched by staff code with name checks, and conflicting values reviewed. The original workbook data, formulas and formatting were preserved, and unknown details left blank.
Make the data usable
One structured import table of 324 rows covering staff profiles and document types. That prepared table is the only input the import flow reads.
Validate, then import
Power Automate resolves each staff code to its SharePoint record, standardises the document-type labels and checks for an existing entry. The live run created 284 missing entries and skipped the 40 that were already there.
Check renewals every day
A second flow reads the current records with expiry dates, selects those overdue or due within 30 days, builds a table and sends the reminder when there are matches. An Excel correction has to reach SharePoint before a reminder can use it.
How an Excel update is applied
Four steps, run by hand- Update the verified details in the source workbook and keep the document import table aligned with the approved changes.
- Save the updated import workbook in SharePoint under General → Admin → Admin Imports.
- Start the bulk-import flow with Run Import off to validate without writing anything.
- Review the result, then switch Run Import on to create the missing records.
What we need from Admin
NextComplete staff photos
Some are already in the Staff Register. Finish the rest and populate the Image column in Staff Documents.
Complete the register rows
Fill the details and file links that are still missing, from verified documents.
Monitor the scheduled reminder
A reminder email has been received. Confirm the regular 08:00 delivery and follow up on the renewals listed.
Agree how existing records change
The import adds new records only. Decide how an approved change to an existing record gets applied.
Group membership
The SharePoint group holds 10 people: one owner and nine members. Individual list permissions and PowerMix app roles have not been checked here, and the names are not reproduced on this page.
Two Admin flows
Staff Documents Bulk Import, started by hand. Document Renewal Check, scheduled daily. Both were visibly enabled in the captured flow list.
Reminder delivery
A reminder email was received on 18.09 at 12:28 AM. That confirms receipt; it does not establish that the 08:00 scheduled run sent that particular message.
Scope of this work
This covers the verified SharePoint Admin work. Integration with the wider PowerMix app, the asset registers, user accounts and the 60-day alerts is separate and not established by it.
What happened to each item from 19.07
Then → nowDaily checklists & fault reports
- A truck with a failed or missing checklist cannot be dispatched until the Readymix Supervisor clears it.
- Fault and incident reports produce PDFs, and the maintenance log is live.
Plant adapter (SQL Server)
- 13.09: decided to pull batch data live from the plant SQL Server. Proven on the Hulhumalé plant PC.
- 14.09: the app now accepts rows from each plant under its own plant-locked key.
- To do: the plant PC must send rows instead of only writing CSV. Then Malé.
GPS tracking
- The delivery timeline runs on driver taps, time-stamped by the server. GPS will write into the same timeline.
Master sheets
- Schedule (with customers and sites), Staff, Fleet, Article and QC lab results import through the preview-and-confirm wizard.
- Excel stays the master, and changes to its fields go through change requests.
- Open: reconciling the fleet register.
Admin module
- Staff and asset registers, passport and visa expiry alerts, and user management.
- The SharePoint registers went live on 18.09 — the briefing is further up this page.
Digital forms as PDFs, with signatures
- Delivery notes, faults, incidents, surveys and QC certificates all come out as PDFs from one document service.
- Signatures are taken on screen in the app. DocuSign or ZohoSign is only needed if customers ask for a third-party signing trail.
UI / UX
- A new visual style with light and dark themes, and form labels that screen readers and taps pick up.
- Plant colours are the same on every screen: coral for Malé, blue for Hulhumalé.
Using the app in the field
One app · three kinds of deviceEach person sees only what their role allows. A Project Facilitator, for example, sees only the loads for their assigned sites.
Office · web
Supervisors, admin, QC and stores use it for schedule, imports, the dashboard, reports and approvals.
Tablet
Project Facilitators and surveyors use it for loads at their sites, delivery notes with customer signatures, and site surveys.
Phone
Drivers use it for the daily truck checklist and the delivery timeline.
-
Phone
Before the shift
Driver- Submit the daily checklist for the truck. Any driver can do this, and their name is recorded.
- A failed or missing checklist blocks the truck until the Readymix Supervisor clears it.
-
Web
Dispatch
Readymix SupervisorPlant Operator- Loads go out only for approved projects and cleared trucks.
- Batch data comes from the plant, through the live feed or a batch report upload.
-
Phone
On the road
Driver- Tap each stage of the trip. The server records the time, so nobody types it.
-
Tablet
After the pour
Project Facilitator- Raise one delivery note for the whole pour and pick the schedule entry it served.
- The customer signs on the tablet, and the signed PDF is stored and listed in the register.
-
Tablet
Surveys, faults, incidents
SurveyorFacilitatorDrivers & operators- A site survey takes photos and a signature, even with no signal. Submitting it clears the project gate.
- Fault and incident reports are filed from the field and saved as PDFs.
-
Web
Quality
QC Engineer- Cube samples are tracked through 7, 14 and 28 days. The engineer records pass or fail; the app never decides.
-
Web
End of day
SupervisorsManagement- Review the day-end report and plan versus actual. Sync Health shows any device that has not sent its work.
- The operational day follows Maldives time (UTC+5), and the week starts on Sunday.
Working without signal
Tablets & phones- Daily checklists
- Site surveys, including photos and signature
Saved on the device and sent once signal returns.
- Opening your list of loads and orders
- Delivery notes, fault and incident reports, and everything else
- Keep the app open to send. Saved work only goes out while the app is open, because iPads do not send in the background.
- On iPad, add the app to the Home Screen (Share → Add to Home Screen). Otherwise Safari may clear saved work.
- Check the Queue. It shows what is waiting, what was sent and what needs attention. If a form is refused, fix it and resend it. Nothing is lost.
- Watch the storage warning. The device warns before it runs out of space for photos.
What we need from the team
Needed before go-liveAt Hulhumalé, switch the batch watcher from only writing CSV to sending rows to the app. Then set up the same agent on Malé’s own SQL Server.
Plant / ITConfirm mixer batch capacity: 1.0 m³ nominal, about 0.92 m³ actual per cycle.
PlantConfirm that the Project Facilitator role fully covers the Foreman role. The app already works that way.
OperationsConfirm the pump bucket quantity for the DN125 pipeline catalogue.
Pipeline / plantDecide where the delivery map’s tiles are hosted.
Management / ITSigned delivery notes are kept for one year with a local backup. Three questions are still open:
- Does the same period apply to QC reports, faults, incidents and surveys?
- From what date does the year run?
- How is a note checked against the local backup before it is deleted?
Define how PowerMix Schedule fits into the RMX OP APP: navigation, data flow and access permissions, then a rollout plan.
Management / ITReconcile the fleet register, so truck codes and their aliases match.
FleetComplete the Staff Master and the SharePoint registers before go-live: codes, roles, site assignments, photos and the document details. The expiry alerts depend on them.
AdminNext steps
From finished modules to the fieldLive plant feed
Switch on Hulhumalé, then Malé.
App side doneSchedule into the app
Fold PowerMix Schedule into the RMX OP APP, once scope and access are agreed.
Direction agreedProduction environment
Create the database and file storage, and set up user accounts for the team.
PlannedField pilot
Set up tablets and phones (on iPads, add the app to the Home Screen), train each role, then run with live loads.
PlannedGPS
Connect the trackers to the delivery timeline.
PlannedMore offline work
Make delivery notes and fault reports work without signal, and let people open their list of loads with no connection.
Planned