| RACI |
RACI stands for Responsible, Accountable, Consulted, and Informed. A RACI diagram is used to describe the roles and responsibilities of various teams or people in delivering a project. It is especially useful in clarifying roles and responsibilities in cross functional/cross Agency projects and initiatives. |
|
Random Access Memory (RAM) |
The main system memory in a computer, used for the OS, application programs, and data. |
| Reasonable Access |
Reasonable access means there are no significant geographical, economic or social barriers created by the government to limit access by citizens. |
| Recordkeeping |
Recordkeeping is the act of making and keeping records. |
| Recordkeeping Meta Data |
Recordkeeping metadata is information describing the context, content and structure of records and their management through time. |
| Recordkeeping Systems |
A recordkeeping system is the interaction of technology, people, principles, methods, processes and information systems that capture, maintain and provide access to records over time. |
| Record(s) |
A record is recorded information in any form, including data in computer systems created or received and maintained by an organization or person in the transaction of business or the conduct of affairs and kept as evidence of such activity. (Aust. Standard AS4390))
Records are information objects that document business activities and transactions. To be regarded as evidence a record must be complete. |
| Records Continuum |
The records continuum is the whole extent of a record's existence. Recordkeeping across the continuum requires a consistent and coherent regime of management processes from the time of the creation of records (and before creation in the design of recordkeeping systems), through to the on going preservation and use of records as archives. |
| Records Lifecycle |
The records lifecycle is the model of records management and archival management which describes the stages through which a record is said to pass during its "life", often using "birth to death" analogies. |
| Records Management |
Records management is the corporate function of managing records to meet operational business needs, accountability requirement and community expectations. Records management includes the systematic capture, control, maintenance, distribution, access and control of records. Records management is primarily concerned with capturing complete, accurate and reliable evidence of organisational activity for current business purposes. |
| Records Retention |
Records retention describes the act of the keeping of records for as long as they have administrative, business, legislative and/or cultural value. |
| Records System |
Electronic systems or applications used for creating, maintaining, controlling and storing records. |
| Referencer |
One of the possible Roles of an Information Asset. It describes information from a source outside the agency which is referenced by its ID. Only the ID is stored locally so the agency only refers to information from the source using the ID and does not update the information asset itself.
(See also "Role") |
| Reliable Records |
Reliable records may be trusted as credible evidence of the transactions they document. |
| Replace |
A Generic Asset Management Action for an asset based on its positioning in each of the grid models of the Queensland Government ICT Portfolio Assessment Methodology. This delineates an asset with limited life. Although it may have a high current business impact, it is in poor technical condition and will not be able to offer business value in the future.
(See also "Asset Management Strategy") |
| Request for Change |
A means of proposing a modification to the current specification of the product. It is one type of Project Issue. See Change Request. |
| Request For Information (RFI) |
An RFI is a formal notice to suppliers indicating that information is being sought as to the goods, services and/or equipment that may be available to meet a specified need. An RFI is used by agencies to assess the capability of the market to meet a specified need and to assist in selecting a short-list of the most suitable suppliers. |
| Request for Offer (RFO) |
An RFO is a formal notice to suppliers indicating that proposals/solutions (incorporating the provision of goods, services and equipment) are being sought to meet a detailed specification of agency requirements. An RFO is used by agencies to select the supplier most able to meet the specified need. |
| Request for Comment (RFC) |
An Information Standard is issued as a Request for Comment (RFC) so that there can be consultation on the working draft. |
| Requirement |
A need arising from an agency's business activity, or from support of business activity, where such activity is intended to fulfil the purpose of the agency as defined by legislation, central agency requirements or ministerial direction.
Importantly requirements within the Information Architecture are derived from the Business Architecture of an agency or government. Examples included: Maritime safety strategies required under the Transport Operations (Maritime Safety) Act 1994 to assist in managing maritime transport operations, The state wide digital cadastral dataset required under the Survey and Mapping Infrastructure Act 2003 to support the effective identification and valuation of land and The list of registered Nurses required by the Nursing Act 1992 to ensure integrity of the health profession. |
| Requirements |
A description of the user’s needs and a statement of detailed product objectives that describes the features and functions and performance constraints to be delivered in the product. The requirements provide the basis for accepting the product. Also referred to as Specification. |
| Research/Explore |
A Generic Asset Management Action for an asset based on its positioning in each of the grid models of the Queensland Government ICT Portfolio Assessment Methodology. This action would be considered for an asset in good technical condition with low costs but which has question marks over its future value to the organisation.
(See also "Asset Management Strategy") |
| Residual Risk |
The remaining level of risk after all risk treatment measures have been taken. |
| Resource Dependency |
A dependency between tasks in which the tasks share the same resources and therefore cannot be worked on simultaneously. Resource dependent tasks can be scheduled at the same time but are limited by the availability of the shared resources. |
| Resource Levelling |
Resource levelling is the part of the scheduling process in which the start and end dates of tasks are driven by resource limitations (e.g. limited availability of resources or difficult-to-manage resource levels). Among the scheduling objectives, is to ensure that resources are not overburdened (don’t schedule more resources for a period than are available) and that (as much as possible) there are not significant peaks and valleys in the resource schedule. There are two outcomes from resource levelling - a) if there is affixed end-date, additional resources may need to be allocated; or b) if the end-date is not fixed, but resources are fixed, the duration may need to be extended. |
| Resource Management Approach |
Description of the resource requirements for the program, competing demands identification and how they will be managed. |
| Resource(s) |
Any tangible support such as, a person, tool, supply item or facility used in the performance of a project. |
| Resources Description Framework (RDF) |
RDF integrates a variety of web-based metadata activities including sitemaps, content ratings, stream channel definitions, search engine data collection (web crawling), digital library collections, and distributed authoring, using XML as an interchange syntax that provides a model for describing resources. |
| Responsibility |
Refers to ownership or obligation for the performance or completion of tasks (i.e. who is charged with doing something on behalf of another). Responsibility may be delegated to others but the delegation does not eliminate responsibility. |
| Retire Stage |
The final stage of the Asset Lifecycle when the asset is no longer useful (in its current state) to the organisation. At this stage a decision must be made as to the asset’s future.
(See also "Asset Lifecycle") |
| Retrievability |
A dimension in the assessment of the Technical Condition of an Information Asset in the Queensland Government ICT Portfolio Assessment Methodology. It deals with the degree to which an Information Asset can be identified, located and made accessible by certain business areas, and is dependent on the extent to which processes and procedures are defined and consistently applied to the management of an Information Asset.
(See also "ICT Portfolio Assessment Methodology") |
| Reviewer |
A person asked to review a product which is the subject of a Quality Review. |
| Risk |
An event that poses a negative threat (or potential positive opportunity) which might affect the course of the program or project. |
| Risk Analysis |
A systematic use of available information to determine the likelihood if specified events and their consequences. |
| Risk Assessment |
An evaluation of system assets and their vulnerabilities to threats, including potential losses that may result from threats. |
| Risk Avoidance |
Not becoming involved in a risk situation by ceasing the activity or process. |
| Risk Budget |
An amount of money set aside at Project Planning stage to allow risk mitigation strategies to be undertaken that may cost money but which are considered worthwhile. |
| Risk Control |
The provision of appropriate policies, procedures and standards of protection to avoid or minimise identified risks. |
| Risk Exposure |
Risk exposure is the product of the Likelihood and Consequence and is the rating that provides the key factor on which risk management decisions are made. The classifications of risk exposure include: unacceptable; critical; significant; minor; and area of concern. |
| Risk Identification |
The process of determining possible outcomes or occurrences associated with an activity, why these might occur and how. |
| Risk Level |
The level of risk calculated as a function of likelihood and consequence. |
| Risk Log |
A document/tool which provides identification, estimation, impact evaluation and counter-measures for all risks to the project. It should be created during the start-up of the program or project and updated during the life of the program/project. Also called 'Risk Register'. |
| Risk Management |
The identification, selection and adoption of countermeasures justified by the identified risks to assets in terms of their potential impact upon services if failure occurs, and the reduction of those risks to an acceptable level. |
| Risk Management Approach |
The systematic application of policies and practices to the tasks of identifying, analysing, assessing, treating and monitoring risk. How the program and project will establish and maintain an effective risk management regime. |
| Risk Reduction |
See "Future Risk Reduction" |
| Risk Retention |
Retaining the responsibility for loss. |
| Risk Tollerance Line |
The risk tolerance line is the difference between risks that can be accepted or for which suitable actions have been planned, and risks that are considered serious enough to require referral to the next higher level of project authority. |
| Risk Treatment |
Selection and implementation of appropriate management options for dealing with identified risk. |
| Risk Transfer |
Shifting the responsibility for loss to another party. |
| Role |
A particular set of responsibilities and accountabilities that may be allocated to one or more individuals. In some circumstances, roles may be merged together as long as there is no conflict of interest. Some roles can only be owned by a single individual.
(See also "Role (in the context of Information Assets)"). |
| Role (in the context of Information Assets) |
The role of the agency with reference to its operations in regard to the Information Asset.
The possible roles are:
- creator;
- referencer;
- acquirer;
- modifier; and
- aggregator.
|