Data Readiness Assessment

1. ACCESSIBILITY: The data can be accessed by a repeatable, automatic method*

Data is accessible from the internet as it is generated (can be streamed or micro batched to the cloud)Data is captured and stored as it is generated but requires capabilities for transferData can’t be retrieved in an automated fashion due to technical (e.g., unconnected devices) or policy (e.g., security/cloud policies not in place) issues

Accessibility Action

ACTION NEEDED:

{accessibilityAction}

ACTION NEEDED:

{accessibilityAction}

ACTION NEEDED:

Get IT buy-in to address policy issues
Evaluate infrastructure and security needs

2. FORMAT/PROTOCOL/SCHEMA: The data is in a consistent, readable format for ingestion into analytic applications*

Data is defined and structured in a way that your modeling application can supportData is structured in a manner that is not currently supported, and drivers to make it usable do not existNo consistent, defined, or documented structure (e.g., manually entered on a spreadsheet or proprietary format)

Format/Protocol/Schema Action

ACTION NEEDED:

{formatprotocolschemaAction}

ACTION NEEDED:

{formatprotocolschemaAction}

ACTION NEEDED:

{formatprotocolschemaAction}

3. LABELING: The data can be tied to physical sources involved in production*

Data is clearly associated with a well defined asset hierarchy (e.g., machine, product, component, line, etc.)The physical sources of the data are partially labeled or labeled manually. Naming conventions are inconsistent or multiple conventions are usedPhysical source information for data is unavailable or not captured. Labels and metadata do not exist

Labeling Action

ACTION NEEDED:

{labelingAction}

ACTION NEEDED:

{labelingAction}

ACTION NEEDED:

{labelingAction}

4. DATA RELATABILITY: There is a systematic method for joining data sources*

Time stamps or serialization exist, enabling the data to be connected with other sources and with the ability to describe how business logic moves through the platformTime stamps can be inferred or data contains partial serial number elements, but only partial visibility into material flow through the platformNo consistency in time stamps or serialization of the data

Data Relatability Action

ACTION NEEDED:

{dataRelatabilityAction}

ACTION NEEDED:

{dataRelatabilityAction}

ACTION NEEDED:

{dataRelatabilityAction}

5. PROCESS ALIGNMENT: Resources are available for mapping data to processes and physical sources*

Personnel who understand the data’s relationship to production processes are availablePersonnel not available but documentation exists on process-data relationshipsPersonnel who understand the data-process relationships are not available, and documentation does not exist

Process Alignment Action

ACTION NEEDED:

{processAlignmentAction}

ACTION NEEDED:

{processAlignmentAction}

ACTION NEEDED:

{processAlignmentAction}

6. SECURITY: All data sources can be securely connected to the cloud for management, transformation, and analysis*

Security on data endpoints is centrally controlled and access credentials are strong. Software updates are routinely applied and the latest versions of encryption technology are available for data transferSecurity on data endpoints is maintained outside of corporate/central oversight. Software updates may be behind. Secrets need to be rotated manuallyData source includes software past End of Life or has no ability to be updated. No or trivially weak encryption for data out of source. No authentication or widely shared weak secrets present

Security Action

ACTION NEEDED:

{securityAction}

ACTION NEEDED:

Apply relevant software updates
Review and document encryption risks
Draft SOP so manual handling/rotation of secrets can be done securely

ACTION NEEDED:

{securityAction}

Name*

First NameLast Name

Email*

example@example.com

Lead Sub Source

Assess Your Data Now: