The unique value of this platform is what's inside each use case: a consistent ontology of value leaks, root causes, enablers, KPIs, and strategic goals — all connected with influence scores that have been validated across the entire corpus. That structured analysis is what you can't get from a chat prompt, a slide deck, or a static report.
The seven dimensions described on this page are the navigation system on top of that ontology — different ways to slice the library so you can find the structured content from many angles. Same use case, many entry points.
Once you understand the navigation, you can ask the corpus questions a flat list could never answer: cross-departmental patterns, role-specific views, advantage-focused portfolios, metric-driven roadmaps. That's where the multi-dimensional tagging earns its keep.
One thing to know up front: the same word can legitimately mean different things in different dimensions. If you've poked around the browse filters and noticed that Quality appears as a Department, a Function, a Competitive Advantage, and a Stakeholder Group — same word, four places — that's not a mistake. The Quality department is an organizational team. The Quality function is the work, and lots of people outside the Quality department do quality work every day. The Quality advantage is what a brand is built on. The Quality stakeholder is whoever has skin in the game. All true simultaneously.
The seven dimensions
Home Department
Who owns this use case organizationally?
Each use case has one home — the department that would lead it on a real plant floor. A use case about closing the loop on quality CAPAs lives in Quality. A use case about predictive maintenance lives in Maintenance. Even when work cuts across many groups, somebody owns it.
e.g. Quality, Maintenance, Operational Excellence, Plant Manager
Associated Function
What kind of work is this, regardless of who owns it?
Functions cut across departments. A Quality department use case might also touch the IT & Data Analytics function, the Operations function, and the HR & Workforce function. Filtering by function shows you everything in the corpus that does this kind of work, no matter which department happens to own it.
e.g. Quality Assurance, Operations Management, IT & Data Analytics
Industry
Where does this apply?
Most use cases apply broadly across manufacturing — and that's the default. Industry filters narrow you to use cases with industry-specific patterns: regulated pharmaceuticals, high-mix discrete production, continuous process. If you're in food & beverage, you can surface the use cases shaped by FDA, allergen control, and shelf-life logic without sifting through everything else.
e.g. Automotive, Aerospace, Food & Beverage, Pharmaceuticals
Competitive Advantage
What strategic outcome does this create?
This is the "why bother" lens. A Quality department use case might create a Cost advantage (less scrap), a Reliability advantage (consistent output), a Quality advantage (better defect rates), and Strong Customer Relationships — all at once. Filter by advantage when you're trying to build a business case framed around outcomes leadership cares about.
e.g. Cost Advantage, Quality Advantage, Reliability, Innovation
CESMII Smart Manufacturing Area
Which Smart Manufacturing pillar does this primarily address?
CESMII's six SM areas — Strategy & Leadership, Excellence & Culture, Data-Driven Processes, System Infrastructure & Integration, Workforce Optimization, Supply Chain Resilience & Agility — provide a framework that maps cleanly to digital transformation roadmaps. Use this dimension when you're aligning use cases to a formal SM program or transformation strategy.
e.g. Manufacturing Excellence & Culture, Data-Driven Processes
Stakeholder Group
Whose work is affected?
Stakeholders are the roles that feel the use case's impact — operators, supervisors, plant managers, maintenance technicians, the executive team. A Quality department use case might have Quality as the stakeholder, but a use case owned by Quality could have Operators or Supervisors as the primary stakeholder if that's whose daily work changes.
e.g. Operators, Plant Manager, Maintenance Tech, Executive
KPI / Key Metric
Which performance metric does this move?
Every use case is connected to one or more KPIs it influences — OEE, First-Pass Yield, MTBF, On-Time Delivery, whatever's actually being measured. Filter by KPI when you have a number you're trying to move and you want to see every use case the corpus says affects it.
e.g. OEE, First-Pass Yield, MTBF, On-Time Delivery
A worked example: one use case, seven views
Let's take a real use case from the platform: the Real-Time Quality Accountability Dashboard. Here's how it shows up across all seven dimensions:
Home Department | Quality Owned by the Quality team. |
Associated Functions (7) | Quality Assurance · Operations Management · Production Management · IT & Data Analytics · HR & Workforce · Continuous Improvement · Executive Leadership Touches seven functions — a Quality dept use case isn't only Quality work. |
Industry | Cross-industry Applies broadly across manufacturing. |
Competitive Advantages (4) | Cost Advantage · Reliability · Quality Advantage · Strong Customer Relationships Creates four distinct strategic outcomes — useful when framing the business case. |
CESMII SM Area | Manufacturing Excellence & Culture Notice it isn't Data-Driven Processes — the platform classifies it primarily as a culture-and-discipline use case, even though there's a dashboard involved. |
Stakeholder Group | Quality Quality team is the role most directly affected. |
Key Metrics | Quality-related KPIs (defect rate, first-pass yield, etc.) Connected to multiple performance metrics. |
That single use case appears in every one of these filters. If you're a Quality manager looking for accountability tooling, you find it under your department. If you're an OpEx leader looking at culture-and-discipline initiatives, you find it under the CESMII Excellence & Culture filter. If you're a CFO building a Cost-advantage portfolio, you find it under Competitive Advantage. If you're an executive tracking Quality-related KPIs, you find it via the metric.
Same use case, four totally different paths to discovery. None of them is "more correct" than the others — they each represent a real way someone might be trying to find this content.
How to use this
The shortcut for everyday use:
- Start broad, narrow with multiple filters. Pick two or three dimensions that match how you're thinking about the problem — e.g., "Maintenance department + Reliability advantage + OEE metric" — and let the intersection do the work.
- Use Function when Department is too narrow. If "Quality department" isn't finding what you want, try "Quality Assurance function" — same topic, broader net.
- Use Stakeholder Group when you're thinking role-first. Operators care about different things than Plant Managers, even when the underlying work is related. Filter to the role you're building for.
- Use CESMII Area when aligning to a transformation program. If your roadmap is organized around the SM framework, this dimension snaps the corpus to it cleanly.
The takeaway
The seven dimensions can feel like overlap at first — but they're each answering a different question, and every use case has a legitimate identity in all seven. Once you stop fighting that and start using it, the corpus becomes a much more powerful tool: cross-departmental pattern recognition, role-specific filtering, KPI-anchored roadmaps, and CESMII alignment all become single-click views of the same content.
The structured ontology underneath — the value leak, root cause, enabler, KPI, and goal chain inside each use case — is where the platform's real differentiation lives. The dimensions are how you find it.
When in doubt, look at the small ? next to each filter heading. Those tooltips are the short version of this page.