Data Architecture
Data Dictionary

For people who have a data architecture requirement, the purpose of this document is to introduce our TeamsWin Multimedia Data Dictionary. Our TeamsWin services supply tools for strategic thinking. One of the products of our service is a multimedia data dictionary that will satisfy many business and data architecture requirements.

Information Heavylifting - Business Intelligence

Data Architecture

Teamswin Database Services


TeamsWin Understanding

Our copyrighted TeamsWin understanding of strategic thinking is a new application of some old concepts from Navigation and Business Science. Our understanding of strategic thinking came to us in the form of a data model that (like navigation) uses the power of triangulation.


The Key – Business Models Already Exist

The key to that data model was developed in the mid 80’s before data modeling became popular. It recognizes that business models already exist in internal and external reports used by decision makers. Besides financial, sales and production reports, these reports include: maps, supplier catalogs, industry standards, and payrolls etc. The key recognizes that decision makers already navigate by transforming information into strategic order. It recognizes that business science already defines strategic order and the information needed for each type of decision.


Violates the basic rule of data modeling

One problem though, that key violates a basic rule of data modeling. The data modeler is required to let the businessman define the business model. This data modeling requirement works well for modeling functions, but it will never work for defining the “big picture” relationships used for navigating a business.



We use reports. We use internal and external reports like: payrolls, charts of accounts, trial balances, financial reports, sales reports, production reports, industry standards, and catalogs. Internal reports are usually called reports, but external reports can have names like: maps, catalogs, regulations, standards, and laws etc. Each report has its own architecture. The business model is hidden in these reports. The business model is an integration of many business models.


Report Architecture

Each report has its own architecture. The businessman has little or no control over that architecture. It is like each report is a separate language with words (information) defined by that reports’ context. The businessman uses his understanding of business science to integrate those architectures.


Business Science Architecture

Business science can be thought of as the language of integrating all these report languages.  A historical analogy would be the way the Hebrew language was used to integrate languages around the world. For whatever reason, Jews disbursed all around the world and learned the local language. Knowing both the local language and Hebrew, they could communicate. But, the key to that communication was thoughts not words.


Thoughts – Report Architecture

For this discussion lets say thoughts are words in context. In order to integrate the languages, the context must be retained. If we know the purpose for the report, we can easily relate its language to the common language of business science. Then we can easily “drill down” from the general language to the specific language. We can also easily “roll up” from the specific to the general. But, we can not easily “roll up” from one specific and “over” to another specific. To do that we would have to think in all the languages; which is not required to do business.


Our Understanding is a Data Model

Our TeamsWin understanding is a data model. At the time we validated our understanding, we found ten books on strategic planning. To understand strategic planning, we built a data model of the information in those ten books. Strategic plans define objectives and relationships between objectives. Plus (and probably more important) those definitions are based on the definitions of objects and relationships between objects.


A Data Model is a Dictionary

A product of a data model is a dictionary, and a product of a strategic plan is also a dictionary. With diagrams, pictures and maps, they are both multimedia, and they both define things. Plus, our inexpensive dictionaries include all the information from those reports in strategic order using the strategic entity called time period.


A Dictionary for a Data Architect

For your immediate purposes, think of it as an inexpensive data architecture service that will assist (and may eliminate the need for) your data architect. Our dictionary reflects changes to the business model in real time. New organization, new people, new products, processes and facilities update the business model as they happen, not when the architect is notified. Even new plans for changes to the business model are picked up as they are approved.


And, a Business and Data Architecture

For people who have a data or business architecture requirement, the purpose of this document is to introduce our TeamsWin Multimedia Data Dictionary. Our TeamsWin services and products are tools for strategic thinking. One of the products of our service is a multimedia data dictionary created by tapping information that resides in existing reports. See for more information and how we can do this for around $2.5K and keep it fresh as a strategic database for about $28K per year. This approach to business modeling is unique. Do not let the low price turn you away.

Phone: 208-295-7094

Cell: 208-304-4458


7087 Funkhouser ST

Bonners Ferry, Idaho 83805


Contact: Bob Pace, TeamsWin Chairman