Data Provenance in the Additive Manufacturing (AM) Thread Additive Manufacturing Business Model Workshop Day 2 Outbrief 31 May 2018

Workshop Objective To identify measures that secure data transmissions such as technical data package (TDP) sharing and data transfer amongst AM machines within the digital infrastructure. The group will explore the cyber security solution, including Blockchain technology and its capabilities to verify and record digital transactions, and its application in contracting and property ownership.

Data Provenance in the AM Thread … it’s all about CODIFYING TRUST in the supply chain…. there has to be a common trust vector backing up the data or all the advantages of Additive Manufacturing go away Understanding when Blockchain makes sense (or similar technologies, ex Graph database) Trusting ANYONE around to fab anything all around the world Trusted Data Transfer (up and down the supply chain) USE CASES: Classified AM Components AM Ordinance Scenario AM Design Process Lifecycle - Auditability, IP & Sustainability

Data Provenance in the AM Thread Objectives (Day 2): In-briefs Adapting Blockchain Technology for AM NCMS, Moog, +5 services SoW InfraTrack Use Case Deep-Dive Action Plans Success is defined as: Integrity of the data is proven Proving the data is accurate

Executive Summary: Use Case #1 Data Provenance in the AM Thread Executive Summary: Use Case #1 Process from CAD design (.prt file) to physical part involves multiple intermediate formats Process spreads across multiple networks, organizations, 100s of printers, air gaps, etc A change upstream (.prt for example) invalidates all derived files (.stl, .gcode) Three sub-use cases Parent file changes (.PRT), ensure derived files are not used to print New make/model of printer added. Ensure previous .gcode file not used on new printer Mishap with system involving part. Ensure full auditability back to original design

Data Provenance in the AM Thread Use Case #2: AM Large Metal Ordnance Surge capability enabled by AM TDP delivered from government to many vendors to meet a surge need in a validated and expanded industrial base. Also expands the potential for a reliable source of supply enabled by AM as an alternative source of manufacturing. Today: 2 vendors fabricating large ordinances in metal AM, each at capacity and only producing a small quantity Surge: 50 vendors to fabricate, both DoD and DoD commercial suppliers Part 1 – Assessment for Blockchain Opportunities Phase 1 – Validate the Data through the TDP Workflow Verify the Data is correctly received (send a valid file from an invalid sender) Phase 2 – Validate the Data through Part Fabrication Part 2 – Print the parts at scale with multiple data sources Stressing the System: Configuration Management, Red-cell & White-hat testing self-validating = autonomously secured ---- what IF! Identify phases of workflow to support TDP-to-print to validate transactions Determine all transactions where blockchain should be applied

Data Provenance in the AM Thread Post-AM Workshop Effort: Next Steps Demonstrate these use cases collaborate with the other existing efforts NATO project CTMA project ….

Additive Manufacturing Business Model Workshop Day 1 Outbrief Securing AM via Blockchain, et.al 30 May 2018

OVERVIEW of Blockchain Best definition is wikipedia - blockchain chains blocks of data together using cryptography *using math" --- ledger = puts the data in the ledger which is the effective chaining of the data together…. Why do you do a ledger? IBM wants you to use their blockchain because it's going to be up on their CLOUD and that's where they get the revenue. You DON’T have to share the whole ledger to get all the good that a blockchain offers.

Day 1 Accomplishments “Everything we're talking here is CODIFYING TRUST in the supply chain…. there has to be a common trust vector or all the advantages of Additive Manufacturing goes away.” Understanding when blockchain makes sense (or similar technologies, ex Graph database) USE CASES: Trusting ANYONE around to fab anything all around the world Trusted Data Transfer (up and down the supply chain) Classified AM Components AM Ordinance Scenario AM Design Process Lifecycle - Auditability, IP & Sustainability

How it works / When to use it Sharing data between parties via transactions Intermediary between the parties Recording the transactions Fundamental transactions

Considerations for Blockchain for AM

Barriers The technology itself is not the barrier… …but business cases and ROI in AM are still being defined. Barriers we identified are: Integration / Adaptation Governance for DoD applications Interoperability across DoD, OEM, global allies and partners Cultural Workforce Development / Training Define capability needs specific to AM Standard TDP workflows through supply base … more tomorrow

Day 2 2 Actionable Scenarios we can Execute