CSU Information Assets: Identification Guide
CSU Information Assets: Identification Guide
ENTERPRISE ARCHITECTURE
Identification Guide
Version 1.0 - January 2015
Page | 1 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Document Control
Version Author Issue Date Revisions
1.0 Colleen 01/12/2014 First version.
Middleton
Acknowledgements
This Document was based on the Queensland Government ICT Planning Methodology which is part
of the Queensland Government Enterprise Architecture (QGEA) 2.0 developed and updated by the
ICT Policy & Coordination Office and Queensland Government Chief Information Office (QGCIO).
Contents
1. Purpose of this Document .............................................................................................................. 3
2. Reference Materials ........................................................................................................................ 3
3. Information Asset Definition........................................................................................................... 3
4. Information Asset vs Data Asset ..................................................................................................... 3
5. Information Asset Identification ..................................................................................................... 4
6. Special Considerations .................................................................................................................... 4
6.1 Electronic Document and Records Management System (eDRMS) ....................................... 4
6.2 Web Content Management Systems (WCMS) ........................................................................ 4
6.2.1 Static web content .......................................................................................................... 4
6.2.2 Dynamic web content ..................................................................................................... 4
7. Classification of an Information Asset ............................................................................................ 5
8. Registration of an Information Asset .............................................................................................. 6
9. Appendix A - Information Asset Identification Assessment ........................................................... 7
10. Appendix B – Relationship between Information and Data Assets .............................................. 10
Page | 2 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
2. Reference Materials
The following reference materials may be useful in providing additional context to the content of
this document:
“An identifiable collection of data stored in any manner and recognised as having value for
the purpose of enabling an agency to perform its business functions, thereby satisfying a
recognised agency requirement.”
Information assets are generally first identified during the analysis step within the ICT Planning
activities (including Strategic Sub Plans and ISIP submissions).
DIT Technology Project teams are responsible for the management and delivery of ICT-related
enterprise projects. Where information is within scope, the identification of information assets will
be necessary, typically in the analysis and design phases.
“An information asset is an identified collection of data which may include data that is also
independently recognised as a data asset. For example the information asset General Ledger
includes recognized data assets such as Ledger Fund Code, Ledger Organisation Code.”
Another view of the comparison between an Information and Data Asset is available in Appendix B.
Page | 3 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
With reference to CSU’s definition of an information asset (3), the following list is a guide to
identifying individual information assets.
An information asset is a logical concept.
An information asset should be named using nouns.
Asset name = Subject noun (typically singular) + Format noun (inherently a collection, group
or plural)
An information asset is named independently of any system or application.
An information asset should be named using common business terminology of the agency.
An information asset has value if it is actively used by a business or decision making process
or exhibits a lifecycle.
An information asset is defined at a level of detail that allows its constituent parts to be
managed usefully as a single unit.
Reference information sources are not considered to be an information asset of the agency.
An information asset that is exchanged, received or commissioned externally should be
identified as an information asset of both CSU and the external organisation.
Information present in two different content types results in two information assets.
An information asset should represent a collection of information.
An information asset should be recorded if the status of the information set remains
unclear.
Refer to Appendix A for an assessment checklist to assist the identification of an information asset.
6. Special Considerations
For the purpose of ICT Planning and ICT Baseline methodologies an eDRMS is considered to contain
information about the tracking of files and documents. The contents of any documents / files it holds
are to be dealt with as separate assets. Recommendation is to identify eDRMS as containing
information assets such as “Business Records Repository” or “File and Records Inventory” (or similar
name as per business area terminology).
This approach is also recommended for other similar pure catalogue, tracking or inventory systems
such as library cataloguing.
Page | 4 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Page | 5 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Registration of an information asset provides organisational visibility of the asset to enable the
University to further support and leverage the asset by optimising availability and contribution to
the broader organisational information collection.
To register assets on the CSU information registers, contact the Enterprise Architect (Information).
Page | 6 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Question Response
Proposed Information Asset
Brief Description
Question No Yes
1a Is the information used as input or output of a business process?
1b Is the information used in a decision making process?
1c Is the information used to evaluate a rule or condition?
1d Is the information subject to a typical information lifecycle (plan, create,
store, access, use, maintain, archive, dispose).
1e Is the information received from an external agency or source and
exchanged on a regular basis?
If the answer to any one of the questions in step 1 is ‘Yes’, a potential information asset has been
identified, go to step 2. If the answer is No to all questions 1a-1e you have probably identified an
information reference that need not be reported or registered.
2b Is the information part of an existing information asset? No - Identify other information that
comprise the asset, record this in
the asset description. Then go to
question 2c.
2c Does the information asset manifest as a single content No - Separate information asset by
type? i.e. Transactional, Analytical, Authored, Publication content type, then return to
Step 1.
Page | 7 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Question Instructions
3a Is the information asset named correctly using subject No - Revise the name of the information
noun(s) and format noun? asset to reflect the subject content of the
asset and its primary form. Then
continue.
Page | 8 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Question No Yes
4a Is the information asset mapped to more than one primary domain?
4b Was the information asset’s primary domain difficult to isolate from one or
more of its secondary domains?
4c Were more than three (3) potential secondary domains identified for the
information asset?
4d Is the information asset classified using domains in different information
archetypes within the information portfolio framework?
4e Is the information asset classified by its form rather than its content?
If the answer to any one of the questions in step 4 is Yes, the granularity of the information asset
may be an issue. Confirm that the information asset defined is not too broad or narrow in terms of its
scope. If changes are made to the information asset, return to Step 1.
Otherwise, your have identified and classified your information asset.
Page | 9 v1.0
DIVISION OF INFORMATION TECHNOLOGY
ENTERPRISE ARCHITECTURE
Characteristics of the
Description
Top Down
At a level to match business objective and that At a level that recognises the different
Granularity
allows its component parts to be managed ‘things’ that combine to deliver on the At a level that identifies the electronic data that
usefully as a single unit: required information asset represents the business ‘thing’
too broad, will not have enough detail Bottom Up
too fine, will have thousands of assets At a level required by business function
Context
Top Down
ICT Asset Register
Informed by business objective including Expands on rules about ‘things’ that form part of Expands further on rules about ‘things’ to enable
information asset ie. mandatory attributes,
Rules
Page | 10 v1.0