Business Process Explorer
InteractiveC22 Systems · Interactive process flows across ProDev, Sales, Support, and the full end-to-end lifecycle. Click any node to explore people, tools, and gaps. Derived from 20 stakeholder interviews.
Full pipeline from Omer's glass ideation through production and documentation. ~18-month cycle targeting April Milan release. Red edges mark broken handoffs.
Departments:
Departments Glass R&D Product Development Production Documentation Sales Support Finance Fulfillment Change Management
Indicators Has gap(s) Informal handoff Broken handoff
Object Model (Entity-Relationship Diagram)
How Bocci's core business objects connect — the data architecture that would underpin an ontology layer. See The Ontology Playbook for the full strategic framework.
erDiagram
PRODUCT {
string sku PK
string product_family
string lifecycle_stage
string glass_type
decimal base_price
string brand
}
COMPONENT {
string component_id PK
string material_type
int lead_time_days
decimal unit_cost
int current_stock
}
SUPPLIER {
string supplier_id PK
string name
int avg_lead_time_days
string payment_terms
}
CUSTOMER {
string customer_id PK
string name
string type
string channel
decimal lifetime_order_value
}
SALES_ORDER {
string order_id PK
date order_date
string status
decimal total_value
string channel
}
WORK_ORDER {
string work_order_id PK
string status
int quantity
date due_date
string priority
}
SUPPORT_TICKET {
string ticket_id PK
string subject
string status
string category
int resolution_time_hrs
}
CHANGE_EVENT {
string change_id PK
string change_type
string status
string confidence
date change_date
}
SHIPMENT {
string shipment_id PK
string destination
string tracking_number
date estimated_arrival
}
PRODUCT ||--o{ COMPONENT : "composed of"
COMPONENT }o--o{ SUPPLIER : "sourced from"
CUSTOMER ||--o{ SALES_ORDER : "places"
SALES_ORDER ||--o{ WORK_ORDER : "triggers"
WORK_ORDER }o--|| PRODUCT : "produces"
WORK_ORDER }o--o{ COMPONENT : "consumes"
SALES_ORDER ||--o{ SHIPMENT : "fulfilled by"
CUSTOMER ||--o{ SUPPORT_TICKET : "submits"
SUPPORT_TICKET }o--o| PRODUCT : "relates to"
SUPPORT_TICKET }o--o| SALES_ORDER : "references"
CHANGE_EVENT }o--o{ PRODUCT : "affects" Source System Mapping & Gaps
| Object | Primary Source | Key Gaps |
|---|---|---|
| Product | NetSuite | No lifecycle stage. No unified catalog. |
| Component | NetSuite | No quality tracking. |
| Supplier | NetSuite | No quality rating. No alt-supplier mapping. |
| Customer | None (no CRM) | No unified identity. Split across Hiver, NetSuite, Shopify. |
| Sales Order | NetSuite | Craft orders manually re-entered. |
| Work Order | NetSuite | No barcode scanning. Data drift. |
| Support Ticket | Hiver | Not linked to products or orders. |
| Change Event | Change Ledger (Notion) | Only 6 backfilled entries. Not operational. |
Related Artifacts
Strategy & Findings
Full discovery findings, systemic themes, ranked improvements, and phased roadmap.
→Product Development Lifecycle
Detailed narrative of each ProDev stage with people, tools, and gap analysis.
→Sales & Support Workflows
Direct sales, dealer sales, and support processes with CRM gap analysis.
→