Knowledge Data Management in a Disconnected World 2019 STIP Working Meeting Kevin Athey Nuclear Weapons Information Program Lead Weapons Physics Design LLNL April 2019 Official Use Only OFFICIAL USE ONLY May be exempt from public
"Knowledge & Data Management in a Disconnected" is the property of its rightful owner. Permission is granted to
download and print the materials on this website for personal, non-commercial use only, and to display it
on your personal computer provided you do not modify the materials and that you retain all copyright
notices contained in the materials. By downloading content from our website, you accept the terms of this
agreement.
Presentation Transcript
01
Knowledge & Data Management in a Disconnected World 2019 STIP Working Meeting Kevin Athey
Nuclear Weapons Information Program Lead
Weapons Physics & Design LLNL April 2019 Official Use Only OFFICIAL USE ONLY
May be exempt from public release under the Freedom of Information Act (5 U.S.C 552), exemption and category:
Exemption 7 – Law Enforcement
Department of Energy review required before public release
Date: 04/19/2019
Name/org: Steve Wofford/WCI
Guidance: CG-SS-5 TCG-WPMU-3<br>
02
Official Use Only<br>
03
TID Reports Library – UCRL
Collection Ownership
Collection Move
Collection Metadata Curation
New Weapons & Complex Integration Leadership
Principal Associate Director (PAD) – Kim Budil
Principal Deputy PAD – Des Pilkington
ADAM Funding
Librarian for Nuclear Weapons Information Program LLNL Classified STI<br>
04
the fact or condition of knowing something with familiarity gained through experience or association
the fact or condition of having information or of being learned
the sum of what is known : the body of truth, information, and principles acquired by humankind
Early 1990’s began to capture important Nuclear Testing documentation
1990’s – Worked with Nuclear Weapons Information Group developing metadata for information sharing across Weapons Complex
Late 1990’s – Purchased Web based Document Management System
2002 – “Production” level scanning effort begins
2017 – Changed from Project to Program
Today
About 10 people - $1.06 M
Morphing into Knowledge Management Program
Archiving, Capture, & Availability Nuclear Weapons Information Program<br>
06
Knowledge in WCI — the sum of what is known What?
Data
Contours
Material Properties
Radiographs
Documents/Presentations
Physical & Digital
Source Code
Code Versions/Releases
Code Reviews
Relationships
Why?
Laws, Orders, & Treaties
Cost Savings Where?
Vaults & Repos
Electronic Systems
Our Heads
Who?
Everyone
When?
Capture
At creation
Use
Tomorrow
10 years
100 years
Destruction
Never
Depends<br>
07
Current Knowledge Landscape Disconnected Silos
Document Management System (DMS)
Virtual Test Library (VTL)
Reaction History Database
Windchill/ELM
NEPedia
Granta
WCI Portal
Atlassian Suite
LC File Systems/Storage
MarkLogic
Shared File Servers
Code Workflow Tools Where do I find all of the information available on a Test?
UGT
Cylinder
Hydro
Simulation
Code Model Where do I go for data? What is the Source of Truth?
Record’s Management
Document Control Where do I store/put data?<br>
08
Knowledge
Service Providers Knowledge Vision Granta Windchill Document/Records Management Workflows Single Access Point for Users Atlassian Suite NEPedia LC Storage/File Servers MarkLogic WCI Portal<br>
09
Current WCI Knowledge Efforts Nuclear Weapons Information Program
Data/Document Archiving and Accessibility
WCI Document Management System
Virtual Test Library
Conversion to dynamic application
Atmospheric Test Films
RadChem Database
Inputs/Outputs of Underground Testing
Reaction History Database
Analyzed Results of Underground Testing WCI Portal
Beta Deployment to Production
Data Provenance
Storing Experimental Results
Workflow Building
Code Testing/Build Results
Looking for more Use Cases & Feedback<br>
10
FAIR Data Findable
F1. (Meta)data are assigned a globally unique and persistent identifier
F2. Data are described with rich metadata (defined by R1 below)
F3. Metadata clearly and explicitly include the identifier of the data they describe
F4. (Meta)data are registered or indexed in a searchable resource
Accessible
A1. (Meta)data are retrievable by their identifier using a standardized communications protocol
A1.1 The protocol is open, free, and universally implementable
A1.2 The protocol allows for an authentication and authorization procedure, where necessary
A2. Metadata are accessible, even when the data are no longer available Interoperable
I1. (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.
I2. (Meta)data use vocabularies that follow FAIR principles
I3. (Meta)data include qualified references to other (meta)data
Reusable
R1. Meta(data) are richly described with a plurality of accurate and relevant attributes
R1.1. (Meta)data are released with a clear and accessible data usage license
R1.2. (Meta)data are associated with detailed provenance
R1.3. (Meta)data meet domain-relevant community standards<br>
11
Typical Workflow<br>
12
Suite Description Typical Workflow<br>
13
Suite Description<br>
14
FAIR for internal data – Changing Culture Unique Identifiers
Authors
Object
When
Large Datasets
Runs use 100+Gbs, multi day
Baselines
Frequency
10+Tbs
Long-Term Data Retention
Organization
Storage
Access<br>
15
Disclaimer
This document was prepared as an account of work sponsored by an agency of the United States government. Neither the United States government nor Lawrence Livermore National Security, LLC, nor any of their employees makes any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States government or Lawrence Livermore National Security, LLC. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States government or Lawrence Livermore National Security, LLC, and shall not be used for advertising or product endorsement purposes.<br>
