Zachman
Template : Zachman Framework Template
To understand the value of the Zachman Framework, let’s look at a real-world example from the wind industry. And by connecting the what, how, where, who, when, and why, organisations can create a more consistent foundation for digital transformation, data governance, and enterprise architecture.
Remember, we are dealing with Six perspectives with Six interrogatives. It is a a classification matrix, not a sequence of steps
Imagine we want to describe a wind turbine lifecycle. A wind turbine is not just a physical asset. It is a combination of engineering knowledge, manufacturing processes, suppliers, service activities, operational data, and business decisions.
Different stakeholders see the same turbine from different perspectives.
A business executive sees a wind farm as an investment that must deliver energy production, revenue, and long-term value.
An engineering team sees the turbine as a complex product consisting of components such as blades, gearbox, generator, tower, sensors, and control systems.
A service organisation sees it as an asset that requires inspections, spare parts, maintenance plans, and corrective actions.
An IT team sees it as a collection of systems generating and consuming data across platforms such as ERP, PLM, IoT platforms, and analytics solutions.
The Zachman Framework helps connect these perspectives by asking six fundamental questions.
What: The information and things that matter
What are the key business entities?
Examples:
- Wind turbine
- Wind farm
- Component
- Supplier
- Customer
- Service order
- Maintenance activity
- Sensor measurement
- Spare part
At the enterprise level, this defines the information landscape and ensures that everyone has a shared understanding of important concepts.
For example, when the organisation refers to a “turbine,” does everyone mean the same thing? Does it include the physical asset, the engineering design, the installed unit, or the operational system representation?
How: The processes that create value
How does the enterprise operate?
Examples:
- Product design and engineering
- Manufacturing
- Installation
- Commissioning
- Service and maintenance
- Spare parts management
- Energy production monitoring
- Warranty management
These processes describe how the organisation creates, operates, and maintains wind energy assets.
Where: Locations and distribution
Where does activity happen?
Examples:
- Engineering offices
- Manufacturing facilities
- Supplier locations
- Construction sites
- Wind farms
- Offshore service bases
- Cloud platforms and data centres
A wind turbine may be designed in one country, manufactured in another, installed offshore, and monitored globally through digital platforms.
Who: Roles and responsibilities
Who is responsible?
Examples:
- Product Owner
- Engineering Lead
- Service Manager
- Asset Owner
- Data Owner
- Data Steward
- Supplier Manager
- Operations Team
This perspective is critical because ownership determines accountability.
For example, who owns the definition of a turbine component? Engineering may own the technical definition, while Service owns the maintenance perspective. Without clear ownership, conflicting definitions emerge.
When: Events and timing
When do activities occur?
Examples:
- Design milestones
- Production schedules
- Installation dates
- Service intervals
- Condition monitoring events
- Failure events
- Warranty periods
Timing is especially important in the wind industry because asset lifecycle decisions depend on historical data and operational events.
Why: Business motivation and objectives
Why does the enterprise perform these activities?
Examples:
- Maximise energy production
- Reduce downtime
- Improve reliability
- Optimise maintenance costs
- Meet regulatory requirements
- Increase customer satisfaction
- Improve sustainability
The purpose connects architecture decisions back to business outcomes.
Leave a Reply