Aediles · The Suite
Twenty-seven modules. One record spine.
Two suites, one spine. The operator suite — sixteen modules — runs the waste business: waste management, waste removal, landfills and transfer stations, bins, residential pick-up, and industrial, commercial and residential cleanups, spill response among them. The municipal suite — eleven modules — carries the same work for towns: the waste programme and the wider municipal services a resident can check. Every module below is a working part of that spine, not a menu entry: records are created, walked through their states, evidenced, and closed — and the cards under this section are the live modules themselves, free to look at. Using them takes a connected wallet that holds AEDI.
The work these suites run: Cleaning Services · Waste & Recycling · Bin Rental & Depots · Composting · Industrial Services · Transfer Stations · Residential Pick-Up · Specialist Cleanup.
Run the operation
- Service Agreements — the commercial contract home: customer, site, services, rate basis and term, from draft to active to completed (suspended and cancelled states carried, not hidden).
- Dispatch & Hauling — drop, pull, swap and return jobs on one board: booked, scheduled, en route, on site, completed, verified — missed and cancelled carried as states, with the unit, the driver and the container on every job.
- Containers & Bin Inventory — every bin and unit the firm owns: in the yard, on rent, out for service, in repair — damaged and lost carried openly.
- Works Orders — the spine of the system: every job raised, scoped, scheduled, worked and completed, with its crew, due date and contract reference on the record.
- Municipal Fleet — the trucks and units: assignment, service-due dates and state, so the fleet’s position is one read, not a yard walk.
- Rentals & Servicing — rental bins, portable-toilet units and rental equipment placed at client sites and serviced on schedule; the module names what is due for service before the client has to ask.
The regulated record
- Scale Tickets & Tipping — gross, tare and net weight on every load, at the operator’s own station or a third-party scale. Tickets are evidence: voided with a reason, never deleted.
- Landfill & Transfer Facilities — the facility’s own operating record: cells, inspections, cover and leachate checks, consolidation and haul-outs, from scheduled to done to reviewed — a flagged state when something needs attention.
- Waste Manifests & Custody — the regulated chain on one record: generator, waste stream, TDG class, transporter and receiver, from issued through in transit and received to disposal confirmed and closed — discrepancies carried, never smoothed over. Manifests are evidence: voided with a reason, never deleted.
- Civic Contracts — the contracts the works run under: counterparty, value, term and state, from tendered to active to completed. This is the document a dispute is settled from. Contract records are voided with a reason, never deleted.
- Asset Inspections — inspections across every asset class, passed or failed with the outcome and the inspector on the record. A failed inspection stays standing until its re-inspection passes. Inspection records are voided with a reason, never deleted.
Service lines & collection
- Septic & Liquid Waste — pumping and liquid-waste services with the tank, the volume and the disposal reference on the record, and the next due date carried forward.
- Hydrovac & Drain Services — daylighting, flushing and drain work: booked to verified, with slurry volumes and disposal references.
- Pressure & Window Washing — exterior services run from the agreement: scheduled, in progress, completed, with the next due date set by the round.
- Snow & Sweeping Services — callouts and contract rounds: the trigger (the snowfall, the call) on the record beside the work.
- Residential Collection Routes — routes by area and service day: households, carts and agreements; a missed run is a state on the route, not a rumour.
- Cleaning Services — recurring cleaning and janitorial work, carried by frequency and next due date.
- Waste & Recycling — programmes by stream — garbage, organics, recycling, hazardous — running under contract, from draft to active to completed.
Cleanups, remediation & the specialist lines
- Spill Response — the incident timeline on one record: reported, responding, contained, cleanup, cleared, closed — the regulator notification and the disposal manifest referenced, an escalated state when the incident grows.
- Abatement Projects — asbestos and mould work run properly: assessment, containment, removal, clearance pending, cleared — the air result and the clearance reference on the record.
- Remediation & Consulting — contaminated-site work by phase: assessment, plan, execution, verification, closure — with the closure documentation reference the file ends on.
- Specialist Cleanup Services — the four specialist lines: graffiti removal (public-spaces rounds), biohazard cleanup and crime-scene cleanup (regulated handling on the manifest chain, insurer and authority references on the job), and flood & fire restoration (insurer-driven stages with extraction and drying logs).
- Recycling Operations — inbound streams received, processed, shipped and settled, each load tied to its scale ticket.
Cleanups run across six segments — industrial, commercial, public spaces, residential, work sites, and well & pipeline sites — and the segment rides on the dispatch, hydrovac, remediation and spill records themselves, so a cleanup is found by the segment it served.
The municipal tranche
- Water Systems — water systems and components, from identified to assessed to in service, with outages on the record.
- Stormwater & Flood Works — stormwater and flood projects by watercourse and area, from assessment through design and construction to complete.
- Sidewalk & Path Programs — programmes by segment, surface and length, run from planned through scheduled to completed; the trip-hazard list a council actually funds from.
- Community Halls & Facilities — hall and facility projects carried on the same works-order spine as the outdoor works.
How a job runs — two workflows, one spine
Work Order to Completed Inspection (the municipal workflow):
- The deal opens in CRM — the customer or the town, the work, the terms.
- The works order is raised and tasked — scoped, scheduled, crewed.
- An operator approves the run before it closes.
- The inspection closes the job — passed, or failed and standing until re-inspection.
- The receipt lands on the CCJV hub — the run written to the hub’s record, readable there.
A stormwater programme for the Town of Devon ran this chain end to end on this ERP — contract, works order, outfall, a failed grate inspection and its passing re-inspection, the invoice settled in core Accounting, the receipt on the hub. The modules above are the ones that carried it.
Service Contract to Settled Invoice (the operator workflow):
- The service agreement is signed — the customer, the site, the services, the rate basis.
- The container is placed and the pulls are scheduled — dispatch raises the drop and the pull jobs.
- The load is weighed — the scale ticket records gross, tare and net.
- The regulated stream is manifested — an operations lead verifies the manifest against the scale ticket before the invoice issues.
- The invoice is issued and settled in core Accounting, and the run’s receipt files to the vault.
A Devon transload yard ran this chain end to end on this ERP — agreement AG-2601, bin BIN-40-118 placed and pulled twice, ticket TKT-8841 closed at net 10,460 kg, manifest MAN-AB-2601 closed on disposal confirmation, and the invoice settled in core Accounting.
The hold: entry is 1 AEDI; each module is 1 AEDI per month; the full suite — all twenty-seven modules — is 28 AEDI held. A hold is a balance check: nothing is spent, transferred or locked. Every collaborator holds their own.
The cards below are Aediles’ own twenty-seven. Shared infrastructure, labelled as such: the CCJV core modules — CRM, HRM, Projects, Assets, Accounting, Calendar, IoT, Command Center and Workflows — run on the hub at ccjv.ca at 1 CJV per module. They are the shared platform under every sector ERP, not Aediles’ own modules.
Aediles Modules
The Aediles suite — free to look, hold AEDI to use
How work moves here: Proposed → Planned → In progress → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Identified → Assessed → In service → Under repair → Decommissioned
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Draft → Active → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Proposed → Planned → In progress → Complete
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Available → Assigned → In service → Under maintenance → Retired
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Scheduled → Due → Inspected → Passed → Failed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Assessed → Designed → In construction → Complete
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Draft → Tendered → Awarded → Active → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Raised → Scoped → Scheduled → In progress → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Reserved → Placed → Serviced → Returned
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Scheduled → In progress → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Draft → Active → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Booked → Scheduled → En Route → On Site → Completed → Verified
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: In Yard → On Rent → Out for Service → In Repair
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Open → Weighed → Closed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Scheduled → Done → Reviewed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Issued → In Transit → Received → Disposal Confirmed → Closed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Scheduled → In Progress → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Booked → Scheduled → On Site → Completed → Verified
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Scheduled → In Progress → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Called Out → In Progress → Completed → Verified
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Assessed → Contained → Removal → Clearance Pending → Cleared → Closed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Assessment → Plan → Execution → Verification → Closure
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Reported → Responding → Contained → Cleanup → Cleared → Closed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Received → Processed → Shipped → Settled
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Draft → Active → Completed
1 AEDI hold per month to use it — a balance check only; nothing is spent.
How work moves here: Called Out → Assessed → In Progress → Drying / Treatment → Completed → Verified
1 AEDI hold per month to use it — a balance check only; nothing is spent.
Shared infrastructure: this ERP also runs on the CCJV core modules — CRM, HRM, Projects, Assets, Accounting, Calendar, IoT, Command Center and Workflows — the same core every sector ERP in the fleet connects to. The modules above are Aediles’s own.
Every module in the Aediles ERP, one card each. Each module is a 1 AEDI hold per month — a balance check only; nothing is spent, transferred, or locked. Your cards show your own state: connect the wallet that holds your AEDI.