Operating Model
A reference view of the cooperative federation, the reporting and integration ecosystem, and the role-based management surfaces that DJ Co-Ops served. This page is informational; it does not modify workspace state.
Cooperative Network
The DJ Co-Ops platform federated cooperative purchasing across three states. Each named cooperative represented a regional buying group whose member school districts shared USDA Foods entitlement, processing arrangements, and distribution logistics. SCVdata's stewardship covered all three states.
Historical Footprint
The production federation included 19+ sub-cooperatives across the three states. The lists below preserve the v0.1.7 demo's historical reference.
- Super Coop (SUPER) Demo anchor
- Best Coop
- Four C's
- CUTE
- Dance Coop
- Doctor Coop
- Gold Rush Unified Buyers
- Inland Empire
- PIP
- San Gabriel
- SCOPE
- EPC
- MEC
- EPC-PMS
- EPC-PMS-NH
- GLC
- MOR
- SPARC
- MEGS
Snapshot reflects the preserved July 2008 master directory. Federation structure evolved over the platform's 25-year operating history. Cooperative and group labels reflect the preserved platform's federation structure; the demo's synthetic transactional data uses a compact cross-state district set across California, Ohio, and Michigan (14 CA / 3 OH / 3 MI) for clarity.
Active Demo Workspace
The three root cooperatives currently loaded in the demo workspace, with live district memberships derived from entities.districts[*].cooperativeId via relationships.cooperativeToDistricts.
Reporting & Integration Map
Commodity reporting reached DJ Co-Ops from many directions. K12 Foodservice — the dominant third-party tracking platform in K-12 foodservice — delivered nightly transaction feeds. ProcessorLink, Lunchline, and direct food processor / food distributor channels each had their own conventions. The system reconciled all of them into a single canonical view.
| Channel | Type | Role in the operating model |
|---|---|---|
| K12 Foodservice | Third-party tracking platform | Nightly commodity transaction feeds into the production system. |
| ProcessorLink | Third-party tracking platform | Manufacturer-abbreviation translation mapping for the parallel third-party tracker. |
| Lunchline | Third-party tracking platform | Planning references for an additional integration path. |
| Don Lee Farms | Direct food processor channel | Direct food processor reporting feed outside the dominant third-party ecosystem. |
| Gold Star | Direct food distributor channel | Food distributor invoice and RA-level reporting format. |
SCVdata's role included understanding these uneven data sources well enough to support practical reconciliation and reporting workflows across all of them. See Volume Rebate Reconciliation for the workflow that exercises this layer.
Role-Based Workspaces
The DJ Co-Ops platform served four distinct user audiences with four different management surfaces. Each surface hid most of the system's operational complexity from its user — school districts didn't need to understand truck routing; food distributors didn't need to understand entitlement adjustments; admins didn't need to manually reconcile rebate exceptions. SCVdata's stewardship preserved and improved this role-appropriate visibility throughout the engagement.
What a school district nutrition services director saw. The annual operating cycle drove the surface: enter annual orders in February, monitor entitlement consumption through the school year, receive delivery and order-confirmation reports, respond to volume discount offerings. The portal exposed what the school district could control, hid everything else.
What a food distributor's account team saw. Aggregated school district demand, quarterly truck capacity, delivery commitments, and sales/velocity reporting requirements. The workspace operated against board-approved hard caps and reporting cadences without exposing school-district-level entitlement detail that wasn't theirs to manage.
What the co-op administrator saw day-to-day. Co-op operations oversight, entitlement exposure monitoring, exception triage, annual-cycle progress, and board reporting. The Admin Console was the surface where SCVdata's stewardship was most visible: catching exceptions before they became board questions.
A specialized admin function. The seasonal cadence of volume rebate reconciliation was a credibility test every year: take incoming velocity reports in incompatible formats, reconcile against RA numbers and school district orders, resolve exceptions, and produce per-school-district rebate payouts on schedule. The full reconciliation loop is what made the rebate season the operational keystone of the platform.
See the Home page for direct workspace entry points, or the individual module pages for each workspace's modules.