Research Data Management Framework: Capability Maturity Guide



Similar documents
P3M3 Portfolio Management Self-Assessment

CAPABILITY MATURITY MODEL & ASSESSMENT

Procurement Programmes & Projects P3M3 v2.1 Self-Assessment Instructions and Questionnaire. P3M3 Project Management Self-Assessment

THE BRITISH LIBRARY. Unlocking The Value. The British Library s Collection Metadata Strategy Page 1 of 8

Information Management

Research Data Management Guide

PORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3)

IT Service Management

Maturity Model. March Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce

Internal Audit. Audit of HRIS: A Human Resources Management Enabler

The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements.

LIBER Case Study: University of Oxford Research Data Management Infrastructure

Software Engineering: Analysis and Design - CSE3308

FINANCIAL MANAGEMENT MATURITY MODEL

How the Information Governance Reference Model (IGRM) Complements ARMA International s Generally Accepted Recordkeeping Principles (GARP )

Digital Continuity to Support Forensic Readiness

Office of the Auditor General AUDIT OF IT GOVERNANCE. Tabled at Audit Committee March 12, 2015

OpenAIRE Research Data Management Briefing paper

Camber Quality Assurance (QA) Approach

Survey of Canadian and International Data Management Initiatives. By Diego Argáez and Kathleen Shearer

Digital Continuity Plan

University Reviews: Exploring a New and Coordinated Approach

PROCESS IMPROVEMENT CAPABILITY MATURITY MODEL

Family Evaluation Framework overview & introduction

Generally Accepted Recordkeeping Principles How Does Your Program Measure Up?

Project Management Office Best Practices

A Report on The Capability Maturity Model

PMOs. White Paper For more papers on PMOs see:

Anatomy of an Enterprise Software Delivery Project

Reaching CMM Levels 2 and 3 with the Rational Unified Process

Transition Guidelines: Managing legacy data and information. November 2013 v.1.0

Workshop agenda. Data Quality Metrics and IT Governance. Today s purpose. Icebreaker. Audience Contract. Today s Purpose

Contents. viii. 4 Service Design processes 57. List of figures. List of tables. OGC s foreword. Chief Architect s foreword. Preface.

IT Governance: framework and case study. 22 September 2010

Statewide Education and Training Services. Position Paper. Draft for Consultation 1 July 2013

Best Value toolkit: Information management

Generally Accepted Recordkeeping Principles

Telephone Call Centres

Delivering peace of mind in outsourcing

IBM InfoSphere Information Server Ready to Launch for SAP Applications

Meeting the Challenges of Database Management. White Paper. Page 1

Management of Business Support Service Contracts

A Capability Maturity Model for Scientific Data Management

The Challenges of Database Management

Service Road Map for ANDS Core Infrastructure and Applications Programs

Strategic Communications Audits

Intelligent Customer Function (ICF)

Trustworthy Computing Spring 2006

CODE OF PRACTICE FOR ASSESSMENT OF COMPETENCE IN RELATION TO PAY

ICT Benchmarking: Better Practice Roadmap

Customer requirements. Asset management planning Inspection and assessment Route asset planning Annual work plans Contracting strategy

Applying ITIL v3 Best Practices

STAGE 1 COMPETENCY STANDARD FOR ENGINEERING ASSOCIATE

ENTERPRISE RISK MANAGEMENT FRAMEWORK

MINISTRY OF HIGHER EDUCATION, OMAN COLLEGES OF APPLIED SCIENCES STRATEGIC PLAN-PHASE

Master data deployment and management in a global ERP implementation

Practice Guide. Selecting, Using, and Creating Maturity Models: A Tool for Assurance and Consulting Engagements

Embedding Digital Continuity in Information Management

Developing and Managing Internal Budgets. top-down. embed. hasing variation. allocation. forecasting. bottom-up

Guide to the National Safety and Quality Health Service Standards for health service organisation boards

Organisational Change Management Maturity

Capital Adequacy: Advanced Measurement Approaches to Operational Risk

ITIL AND COBIT EXPLAINED

Checklist for a Data Management Plan draft

MANAGING THE SOFTWARE PUBLISHER AUDIT PROCESS

Research Data Management

The Strategic Management Maturity Model TM

STAGE 1 COMPETENCY STANDARD FOR PROFESSIONAL ENGINEER

The DAM Maturity Model

DATA QUALITY MATURITY

Strategic Action #13 Open Government by Design

Data Management Maturity Model. Overview

NATIONAL COMPETENCY STANDARDS FOR QUANTITY SURVEYORS - CONSTRUCTION ECONOMISTS

Engineering Standards in Support of

Balance collections with retention for each customer. Decision Analytics for debt management in telecommunications

Standard 1. Governance for Safety and Quality in Health Service Organisations. Safety and Quality Improvement Guide

INTEGRATING RECORDS MANAGEMENT

Before you begin. Topic 1: Research planning requirements 1. Topic 2: Develop human resource strategic plan 37

RESEARCH DATA MANAGEMENT POLICY

POSITION DETAILS. Centre for Higher Education Development (CHED)

Queensland recordkeeping metadata standard and guideline

Implementing Enterprise Information Governance: A Practical Approach

Successful Implementation of Enterprise-Wide Information Governance

Qlik UKI Consulting Services Catalogue

National Statistics Code of Practice Protocol on Data Management, Documentation and Preservation

RECORDKEEPING MATURITY MODEL

Comparison table showing 2015 accreditation standards for specialist medical programs and professional development programs against the 2010 standards

The Capability Maturity Model for Software, Version 1.1

Outline of a Research Data Management Policy for Australian Universities / Institutions

IT Portfolio Management

Lecture 8 About Quality and Quality Management Systems

Achieving a Step Change in Digital Preservation Capability

Quality management/change management: two sides of the same coin?

Transcription:

ANDS Guides Research Data Management Framework: Capability Maturity Guide Introduction The outline set out below shows five levels of attainment or maturity which institutions may achieve in managing their research data. Organisations can use it as a guide to assessing their current level of attainment and identifying areas where they may wish to concentrate in the future. In this way the model can serve as a form of gap analysis. This is an adaptation of the well-known Capability Maturity Model (CMM) which was originally applied to software development. This has subsequently been developed into the Capability Maturity Model Integration 1 (CMMI) and applied to other areas of business activity. Given the breadth of activities and processes involved in the Framework, it is unlikely that any organisation will demonstrate consistent levels of attainment across the four major areas of Organisational policies and procedures, IT infrastructure, Support services and Managing metadata. Furthermore, it is up to each organisation to decide where on the model it wants to be: not all organisations will seek to attain Level 5 (Optimised). Who should read this This guide is intended for practitioners within research organisations who have responsibility for some aspects of research data infrastructure provision. Future ANDS activity related to the provision of top-down, coordinated research data infrastructure is planned. Level 1 - The Initial Level At Level 1, the organisation does not provide a stable environment to support research data management. Expertise is likely to be concentrated within a few individuals, and successes are likely to be due to their efforts rather than to proven processes. It may prove difficult, therefore, to repeat successes. Co-ordination and cohesion across the various groups (e.g. research office, IT, library, records office, research areas) associated with research data management is patchy, if non-existent. Policies and procedures may not exist at all, or if they do, may be out of date, not address datarelated issues, be inconsistently applied or not include compliance measures. IT infrastructure is disorganized and inadequate to support research data storage and management. Expertise is held by only a few individuals who are unable to cope with demand. (cont. p3) 1 CMMI Product Team, CMMO for Services, Version 1.3, November 2010. Software Engineering Process Management Program. http://www.sei.cmu.edu (downloaded 8 December, 2010). ands.org.au 1

Research Data Management Framework: Capability Maturity Guide Level 1 Initial Level 2 Development Level 3 Defined Level 4 Managed Level 5 Optimised disorganised & ad hoc under development standardised, communicated managed, measured Focus is on continuous improvement Institutional policies & procedures procedures may be undeveloped, not up to date, and/or inconsistent. developed & harmonised. promulgated & absorbed into behaviours. procedures accepted as part of the culture & subject to audit. subject to review & improvement. IT infrastructure IT infrastructure provision is patchy, disorganised & poorly publicised. Funds are invested in technology & skills. defined. established, defined & documented. Management shows active support. Facilities are welldefined & communicated, standardised &integrated. Funding adapted to need. Management actively engaged. Documentation kept up to date. Concerted efforts to maintain, update & publicise infrastructure. Metrics & feedback used to optimise Support services Training is ad hoc, curation & preservation services are disorganised, data management planning is unsupported & other services inconsistent & poorly publicised Investment in skills. Services identified & staffed. defined. Documentation & training developed. Active participation in training & widespread availability of Widespread take up of Curation & preservation acknowledged as critical to the institutional mission. Customer feedback used extensively to update & improve Managing metadata Metadata management is chaotic & understood by only a few. defined & skills developed. established, defined & documented. standardised & integrated. Metadata applied to new datasets & shared externally. Metadata quality metrics collected. All datasets described & metadata shared. Continuous improvement applied to processes & capabilities. Metadata applied to key datasets & shared externally. ands.org.au 2

Support services are ad hoc, with training largely unavailable, data management planning is unsupported, partly because the issue has not been dealt with through the development of policies and procedures, standards are undefined, curation and preservation services are disorganised, and other services are inconsistent (if not nonexistent) and largely unknown. Metadata management is chaotic & understood only by unsupported individuals. It is regarded as low priority by the organisation, so that institutional and area responsibilities for it are undefined and resources to support it are inadequate. Few, if any, attempts are made to share metadata externally and its role in potentially supporting institutional administrative activities is unexplored. Those directly involved in research projects, however, may be adept at meeting the metadata needs of their own research, but they are unsupported by institution-wide services which may help them to provide better metadata services to support data sharing and re-use. Level 2 - The Development Level At Level 2, the organisation has moved on from ad hoc processes, as the role of research data management is increasingly recognized as an important aspect of the organisation s business. There is a more systematic approach to research data management, with some attempts at coordination across the various areas involved (e.g. research office, IT, library, records office, research areas). All aspects of research data management are being developed, with assigned responsibilities, trained staff and improved resourcing. The institution is moving from being reactive to being proactive, but still has some way to go. Policies and procedures: Key to moving from Level 1 to Level 2 is development of a research data management policy. This should define responsibilities, provide definitions and set out expected behaviours around the creation, storage and management of data, while reflecting the requirements of the Australian Code for the Responsible Conduct of Research. Other related policies should also have been developed, updated and/or harmonized with the research data management policy. Relevant procedures should be in place for each policy. While the policy and procedures exist at Level 2, they have still to be institutionalized. Instead, there is reliance on a central person or group to understand the issues and implement procedures reliably and consistently. IT infrastructure: Reaching Level 2 means that the organisation has recognized the need for IT infrastructure provisioning and IT equipment. in place, responsibilities are defined, training has been delivered to staff immediately engaged with the IT infrastructure, funding needs have been assessed and budgets readjusted. Institutional needs for storage of research data, and its accompanying metadata, have been recognized and procedures put in place to ensure that all researchers have access to persistent storage for their data, whether it has been created in-house or imported from elsewhere. Data storage may be in-house, shared with another institution or outsourced. Processes and tools have been put into place to manage identities, authentication and access, and to ensure that licence conditions for shared data are met. Tools are available to meet researcher needs for analysis, visualization and collaboration, even if these have not yet been widely publicized. There is periodic monitoring and evaluation of processes and the organisation can respond to periods of stress in a systematic rather than ad hoc fashion. Support At Level 2, the organisation has a wide range of support services in place. These include services which publicise the need for and importance of research data management and provide training to data creators, curators and specialists working in data centres. Training activities are starting to be supported by web pages linking to internal policies, procedures, templates and facilities, as well as external sources of information. Data curation and preservation services are well under way, and data is starting to be assessed for longer-term retention. ands.org.au 3

Metadata management. The organisation recognizes the need for comprehensive metadata to underpin good research data management. It recognises the benefits that this can bring to both research and the administrative requirements of the organisation, in addition to meeting any external requirements (as from funders, for example). Standards are identified for both object-level (technical) and collection-level metadata records. Tools are developed to support the automatic collection of metadata from various instruments. in place to identify new datasets for administrative purposes as well as sharing with other entities, such as Research Data Australia. Some metadata records are created and shared with Research Data Australia and/or other portals. Level 3 - The Defined Level Level 3 organizations typically understand the business meaning of research data (e.g. as an asset) and have a stated policy that data is treated as an organisational asset. This is reflected in an emphasis on skills development, improved communications, the establishment of standard processes and an increase in consistency across the organisation. typically described more rigorously and more widely adopted. Policies and procedures: Moving to Level 3 shows that the organisation is taking responsibility not just for having policies and procedures in place, but for implementing change processes to ensure that these are widely understood and put into practice. Responsibility for the implementation of appropriate procedures is devolved outwards from a central few as more individuals become engaged in implementation of procedures and understand their benefits. Policies are enforced and testing is done to ensure that requirements are being met. IT infrastructure: Management actively supports data IT Infrastructure and ensures it is coordinated and publicised across the organisation. IT infrastructure needs are coordinated with capital expenditure planning and with technology transition planning. IT support roles are more specialised than in Level 2, although some staff may enact multiple roles. Some use is made of data support tools, but not consistently across the organisation. IT facilities are more standardised and some formal testing of facilities and services is done. Support services: All services are now fully supported financially. They are well developed, documented and publicized. Training is regarded as a normal part of induction, for graduate students as well as new staff in relevant areas. Checks are made to verify that the services are meeting the requirements of the user community. Metadata management: While data is recognized as an organizational asset, having high quality metadata is recognized as being critical to good data management. Metadata records are created for all newly identified datasets and shared with Research Data Australia and/or other portals. Automatic collection of metadata from instrumentation is improved in terms of both accuracy and content relevance, and processes are developed to align object-level and collection-level metadata. Linkages are in place between the various systems from which metadata can be gathered so that information is only collected once. Level 4 - The Managed Level At Level 4, senior administrators recognize research data as an organizational asset. This implies that it is treated in the same way as other assets (personnel, finance, buildings, equipment, etc) and subject to audit. Audit measures are both quantitative and qualitative, ensuring that there is a focus on both efficiency and effectiveness. There is consistent coordination between those responsible for policies and procedures, IT infrastructure provision, support services and metadata management. ands.org.au 4

Policies and procedures: Policies which have an impact on research data management have now been absorbed into the organizational culture and are consistent across all areas. Procedures are fully understood and implemented. Compliance is audited. IT infrastructure: Management views data as a key organisational asset and supports IT infrastructure through targeted support and value-adding of data assets. IT infrastructure costs and planning are integrated with other asset-based planning systems across the organisation. There is a clear separation of specialised IT support roles. Data support tools are largely standardised across the organisation and regular measures of their effectiveness and value are captured. Formal, automated testing of facilities, services and data quality is performed. Support services: There has been widespread take up of services across the organisation. Curation and preservation are acknowledged as critical to the institutional mission, and supported accordingly. Some auditing is undertaken. Metadata management: Metadata is accepted as a key aspect of effective research data management and advanced tools are in place to manage it. The institution is now in a position to know what data exists and where it is located, and to use this information for internal administrative processes, such as research reporting or researcher profiles. All datasets are fully described, allowing this information to be available across disciplines. Metadata is routinely contributed to Research Data Australia and/or other portals. Metadata is audited to assess quality and availability. Level 5 - The Optimizing Level The Level 5 organization uses the policies, procedures, practices, services and facilities already developed as the basis for continual improvement. Policies and procedures: policies subject to review and improvement in order to ensure that external requirements and internal needs are being met. IT infrastructure: Management optimises the IT infrastructure evolved in previous Levels through continuous focus on management and improvement of data assets. Automatically captured metrics and audit findings are used to maintain service quality and drive change in rapidly changing technology support areas. Individual IT support roles enact well publicised technology transition and process improvement plans. Use of data support tools is driven by measures of effectiveness. All aspects of data IT infrastructure facilities and services are monitored through highly visible automated testing and feedback systems. Support services: Customer feedback forms the basis of updating and continuous improvement of Metadata management: Metadata provides the basis for rapid discovery of data in all disciplines, both within the institution and beyond. Continuous improvement is applied to processes & capabilities. Further information ANDS Guide to Creating a Data Management Framework http://ands.org.au/guides/dmframework/data-management-framework.html and linked pages. This_work_is_licensed_under_a_Creative_Commons_Attribution_3.0_Australia_License._August_2011 ands.org.au 5