Introduction
...
Alternatively one could choose to define capability using the architectural unification approach POLDAT
- Process (business processes)
- Organisation (structures)
- Location (Geographical information)
- Data (models, life cycles, security etc)
- Application (software, security, interoperability etc)
- Technology (infrastructure)
...
We can now start to see that as we weave through the different parts of the organisation we need to ask the following questions (to help define the nature and characteristics of a capability)
So in actual fact, the goal is delivered through a set of POLDATs that execute in defined manner
| Info |
|---|
| What this reveals is that within industry sectors capabilities can be defined based upon delivering certain goals. Organisations may then trade, acquire or partner with other organisations based upon the mutual understanding of those capabilities. The implementation is irrelevant for this is not what we are measuring, we are measuring strengths and weaknesses using something like POLDAT or TEPIDOIL attributes. |
...