Data management and governance is a key part of trustworthy, transparent data-centric manufacturing. Any insights will be dependent on the data used and so for auditing purposes it is essential that the data be managed and governed appropriately. In many manufacturing settings, especially those with safety concerns there will be a minimum requirement to keep data for a certain length of time. To be most effective, organisations should have consistent data management and governance implemented. We have therefore provided a template for data management based on the Microsoft Team Data Science data definitions.
Good data management includes:
what data to collect,
how to collect the correct data,
assessing the quality of the data,
where and how to store data,
who will access the data and how,
what metadata or schema will be used to ensure information about the data is kept.
As well as successful identification and implementation of the above, it is also necessary to record the information. Typically, this is done using a data management plan but most available resources are long documents that are difficult to follow (although they do contain all the relevant information). We have attempted to streamline these documents and include an element of version control in the process.
A good data management strategy will also identify those that are responsible for the data and its governance. At the University of Sheffield (and beyond) there are Data Stewards that support and advocate for good data management and a network that aims to provide support across all groups. The AMRC is part of the Data Steward Network at TUoS.
The FAIR principles aim to support the use of computers to work with data and are therefore important to manufacturing. The FAIR principles for data are that the data should be:
Findable - machine readable metadata should be used for automatic discovery. If no one knows the data exist, they can't use it.
Accessible - once the data is found they need to know how to access it, this may be through authorisation. Metadata should remain accessible.
Interoperable - the data will need to operate within different systems and applications. The extent of interoperability will depend on the context, but organisations would normally want data to operate through their own systems at least.
Reusable - Metadata and data should be well described so that others can reproduce the data and its findings or use it in different settings.
Making machine readable metadata can be a challenge, although our research into ontology design and implementation will make this easier.
We have produced a template to help produce your data strategy and implement data management.
We have also provided a data dictionary template designed for the AMRC to provide further information on individual datasets. The data dictionaries describe the contents of a data set, usually with an Excel sheet or with details on a data schema (for database management systems).
The data dictionary should contain a description of each column (data stream) in the dataset (database), including what the data stream is, a short description, type of data, some key values such as minimum or maximum. Any information that is required to understand the data set should be included while remaining concise.
The data dictionary should be used to define a common data language for any data created.