Your mission is to build an information asset register

Designing an information asset register (IAR) sounds easy. But as soon as you start, a number of questions emerge.

What are the business drivers?

Compliance requirements? Findability problems? Privacy and Data Protection? Operational efficiency? Best practice?

No matter what the major driver is, there are multiple reasons for needing an IAR. Which suggests that multiple stakeholders with an interest in your project will emerge over time. It makes good business sense to incorporate all of their requirements into the design of your IAR, unless you want to have competing registers.

Using relational database software like a.k.a. software makes the task so much easier, because you start with a simple design and build in additional requirements over time.  At any point you can expand the design to meet everybody’s needs.

Over many years Synercon has helped clients designing information asset registers, from the very simple to more complex models . Here are some examples of how we have incorporated multiple requirements into a coherent data model .

Identification and ownership requirements

•  Identifying information assets
• Categorizing information assets
• Documenting ownership of the information assets
• Understanding who creates and uses the information assets, and how they are used.

Linking information assets to mandates and master data

• Identifying and linking information assets to mandates: legislation, standards, policies that impact how the asset is managed.
• Identifying and linking assets to taxonomies and data catalogs used to classify information assets.

Understanding the business value of the assets to the organization

• Linking to business function
• Understanding the business purpose
• Assessing the business value
• Identifying intellectual property
• Identifying public sector information

Managing the liabilities and risks associated with information assets

• Protecting privacy protected records
• Identifying vital records and intellectual property
• Controlling access

Ensuring digital information continuity through business and technology changes

• Identifying supporting applications and their dependencies
• Migrating information through technology upgrades

Managing the growth in volume of digital information

• Reducing redundancy and duplication
• Managing locations and storage
• Linking to retention and disposal rules

Ensuring ongoing governance of the information asset register

•  Recording and auditing changes
• Managing the approval and review process