T
Terra/ AcmeAcme · West Campus
Portfolio
2 programs live · 2 coming online · all data scoped to its program — nothing intermingles
One Terra · two programs
Each program is its own self-contained area
Operational waste (Sara's team) and Construction & Demolition (Jordan's team) run on the same Terra platform but have completely separate data, pages, and workflows. Click into a program to enter it. Hazardous and E-waste come online next.
Programs
Click any row to enter that program
- OOperational wasteLiveRecurring hauler invoices · MSW, recycling, organics across WC sitesTeam: Acme Sustainability — Operations · Oct 2025 – Jan 20269invoices182tons70.9%diversion8open flags
- CConstruction & demolitionLivePer-haul weight tickets · concrete, metal, drywall, mixed C&D across capital projectsTeam: Acme Sustainability — Capital Projects · Aug 2025 – Feb 202616tickets218tons62.8%diversion9open flags
- HHazardous wasteComing soonManifests + cradle-to-grave tracking · RCRA / DOT compliant disposalTeam: Acme Sustainability — EHS · Q3 2026 onboarding
- EE-wasteComing soonAsset-tracked electronics · R2-certified downstream chain of custodyTeam: Acme Sustainability — IT · Q4 2026 onboarding
Why programs are separate
Daily users only see their world
- · Different teams (Sara's ops vs Jordan's C&D) have different daily workflows
- · Different source events (recurring invoices vs per-haul tickets)
- · Different aggregation envelopes (sites/months vs projects)
- · Different exports (Sphera ESG vs LEED MR-2 packets)
- · Different rule sets, different facilities, different vocabularies
Why one Terra
The unified pitch sits here, on this screen
- · One contract, one login, one design system across all programs
- · Acme-wide ESG rollups feed Sphera from a single source of truth
- · One ingestion engine, one rules engine — different configurations per program
- · New programs (haz, e-waste) onboard as new entries here, no parallel procurement
- · Auditors see one platform, one trail, one vendor