User:Revansx/GRC Code H Digital Transformation Implementation Plan Submission

From MWStake
Jump to navigation Jump to search

In conjunction with the development of the Digital Transformation Implementation Plan, directorates are asked to submit synopses of DT activities in their respective areas by October 18, 2021. Please provide any DT activities from your directorate that fall within the three categories described below, to include those managed and/or funded at the enterprise level. Please also include a POC for each entry.

Information can be provided in any format and be returned either through the DSM SharePoint folder or by email to [[1]].

Your assistance with this effort is much appreciated. If you have any questions, please do not hesitate to contact Anne Rowland via Teams or email.

Digital Transformation activities at GRC-ATF completed in CY 2021-2022 and prior

Activities that were completed in CY 2021 or ongoing activities that were initiated in CY 2021.

Digital Transformation projects in work and completed as of CY 2021

# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
1 Establish a Web 3.0 Knowledge Management (KM) application platform that is internally maintainable and will fully serve all Code H Digital Transformation (DT) Operational Knowledge Management needs for the next decade and beyond.
Ref: KMS Overview Charts.pptx
Definitions/Clarification:
  • We define "Web 3.0" as the Semantic Web per W3C
  • We define an "application platform" as an online browser-based resource per AP-NASA-HNBK-001 v2.4 that is accessible to all agency users.
  • We use the term "internally maintainable" to refer to the collective skills, competencies, and availability of our organization's core staff. In other words; for us, by us.
  • We define "Knowledge Management" as the organization's ability to "efficiently get the right information to the right people at the right time" which, at NASA ATF, implies proper handling of all records (per GLPR-1441.1) in all stages of the record lifecycle - record creation; Active record usability, Inactive record accessibility; record dispositioning, re-purposing, Destruction and/or archiving.
  • We define "Operational" Knowledge Management to mean: the act of digitally transforming all organizational processes as electronic workflows within the KM application such that the KM aspects of each task are accomplished within an integrated, accessible, monitorable, manageable electronic workflow.
  • We define "our KM needs for the next decade and beyond" to mean; our ability to comply with OMB's 2019 Memo M-19-20 (Transition to Electronic Records) in a way that enables us to continuously improve our efficiency and effectiveness in achieving our mission* for the Agency. We seek to not only comply with this digital transformation mandate, but to do so in a way that empowers our users to efficiently create “knowledge” in the normal course of their daily work; and enables them to easily find, share and act upon that knowledge in ways that will measurably improve the quality of our current and future business objectives.
The ATF Mission - The Neil A. Armstrong Test Facility (ATF) provides unique world-class test facilities which are available for use by NASA, other Governmental agencies, and the private sector. We provide full service facility and test system preparation for complex and innovative research and flight programs. Our facilities can simulate the conditions of the upper atmosphere, deep space, planetary, lunar environments, and cryogenics. Our staff assures safe, effective, responsive and reliable performance of research, development, and qualification testing at ATF to accomplish the mission of NASA, other Governmental agencies, and the private sector. 		The Web 3.0 KM application platform shall conform to the following criteria:
  1. Shall be certified for use as an CUI/SBU repository of NIST MODERATE data for the organization
  2. Shall use LaunchPad for user authentication via SAML/ADFS
  3. Shall use NAMS for "Role-based" authorizations within the application
  4. Shall meet or exceeds all design principles defined in NASA's Applications Programming Handbook (AP-NASA-HDBK-001 v2.4) [1] with special attention to:
    • AP-NASA-HDBK-001 Section 4.3.1.1 - Strive for vendor independence through the use of open source software
    • AP-NASA-HDBK-001 Section 4.3.1.2 - Prefer Open Source Software
  5. Shall only use highly-reputable, well-documented open source software [2]
  6. Runs on Agency supported "Platform as a Service" [3]
  7. All functionality is available through well-documented RESTFUL APIs [4]
  8. Configuration management using safe (idempotent [5]) deployment automation
  9. User Interface shall be a "wiki" [6]
  10. Shall be capable of storing wiki data with "semantics" [7] resulting in RDF/OWL data representations of the data accessible to other features of the wiki.
  11. Shall enable users to organize file uploads as nested file structures
  12. Shall enable the organization to implement all organizational processes as integrated multi-user/multi-instance electronic workflows that incorporate all aspects of knowledge management as the work is being done.

References:

  1. https://sharepoint.msfc.nasa.gov/sites/ap/standards/.../AP-Handbook-v2.4.pdf
  2. https://dodcio.defense.gov/Open-Source-Software-FAQ/
  3. https://www.grc.nasa.gov/ocio/pages/computing/platform-as-a-service
  4. https://restfulapi.net/
  5. https://www.w3.org/TR/ws-gloss/#defs
  6. http://wiki.org/wiki.cgi?WhatIsWiki
  7. https://www.w3.org/standards/semanticweb/
 Identify a set of software elements that are mutually exclusive and collectively exhaustive in successfully implementing the requirements
Status: Milestone Complete
  1. RedHat/Centos Linux
  2. Apache
  3. Haproxy
  4. PHP
  5. MySQL
  6. Mediawiki
  7. Semantic Mediawiki
  8. Python
  9. Ansible
  10. Mediawiki Extensions as needed
  11. ImageMagick
  12. SimpleSAMLphp
  13. OpenSSL
  14. more [1]

References:

  1. https://wiki.grc.nasa.gov/pbgeneral/Special:Version
 Demonstrate that the solution is maintainable by the organization within budget and resource constraints for the full life-cycle of the project
Status: Milestone Complete
  • RHEL7 PaaS via GRC Code VM00
  • Meza - Mediawiki E-Z Administration via Ansible [1,2]

References:

  1. https://www.mediawiki.org/wiki/Meza
  2. https://github.com/enterprisemediawiki/meza
 Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
2 Internal Document Configuration Management using the ATF KMS (see #1 above)
ATF seeks to provide its users with a fully-featured Document Management System within the ATF KMS. 		The ATF KMS must be able to provide the following functionality:
  1. Allow users to define and manage documents with properties in a semantic database
  2. Allow users to easily view the list of defined documents and their statuss
  3. Allow users to easily view and download authorized copies of released documents
  4. Allows users to develop revisions to defined documents and submit them for version control
  5. Allow users to submit, and track Change Requests to existing documents
  6. Allow documents to be authorized by multiple users as required by BMS processes
 Establish a base tool for document management in the ATF KMS and migrate management of all existing Internal Work Instruction documents (Checksheets, Procedures, etc..) to the ATF KMS including all historical files.
Status: Completed 		Develop BMS processes and train users how to use the system to maintain existing documents and to define and develop new documents.
Status: Completed
  • See CRs for all Sites
 Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
3 Systems Management at ATF using the ATF KMS (see #1 above)
ATF seeks to implement a Systems Management Policy at ATF that enables Facility Managers to perform an inventory of the various different systems in their domains and assign ATF staff to manage those systems according to a station-wide policy. This approach to systems management will enable managing and reporting compliance to all policies as real-time data available to all stakeholders. 		The ATF KMS must be able to provide the following functionality:
  1. Allows users to define a list of systems with properties in a semantic database
  2. Allow users to easily view the list of systems
  3. Allow users to define the hazards of the system, any countermeasures required and track their verification as required
  4. Allow users to define any software used in the system
  5. Allow users to define any MTE used in the system
  6. Allow users to define the requirements of the system
  7. Allow users to capture the inventory of the system
  8. Allow users to capture the lessons learned of the system
  9. Allow users to capture, track and resolve nonconformances in the system
  10. Allow users to upload files that are specific to the system
  11. Allow users to capture meeting notes relating to the systems
  12. Allow users to define the operator training requirements (OTRs)
  13. Allow users to graphically define the processes of the system
  14. All changes to Systems are version controlled and tracked
 Establish a base tool for system management in the ATF KMS and generate systems lists for each major test facility at ATF
  • See Systems lists for each site
 Work with facility managers to assign system managers and work with system managers to ttrain them on how to document and manage their systems using these tools
  • See System Pages on each site
 Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
4 Process Safety Management (PSM) Management of Change (MOC) using the ATF KMS (see #1 above)
ATF seeks to empower all Test Facilities to more easily meet the PSM MOC requirements by providing a dedicated knowledge management based electronic workflow for the performing MOC at ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new MOCs with properties in the semantic database
  2. Users can easily View and Edit each MOC
  3. The system will List and Sort MOCs based on status
  4. The system will facilitate all PSM requirements of MOCs
  5. Users can easily upload files relating to MOCs
  6. Users can easily add and status actions relating to MOCs
  7. Users can easily capture meeting notes related to MOCs
  8. All changes to MOCs are version controlled and tracked
 Establish a base tool for PSM Management of Change in the ATF KMS that includes a dashboard for users to view and manage the MOCs
Ref: MOC Dashboard at PTC 		Pilot the use of the MOC tool at a facility and validate functionality with feedback from the MOC process owners and users.
Ref: MOC Documentation from PTC 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
5 Graphical BPMN Process development of the ATF processes (see #1 above)
ATF seeks to empower all users to more easily develop and maintain the various business processes used at ATF by providing a dedicated knowledge management based electronic workflow for the designing processes at ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can Create and Submit new processes with properties in the semantic database
  2. User can easily View and Edit individual BPMN Processes
  3. Users can easily List and Sort all defined BPMN Processes
  4. Users can develop BPMN compliant process in a graphical editor
  5. Users can easily upload files relating to BPMN Processes
  6. Users can easily add and status actions relating to BPMN Processes
  7. Users can easily capture meeting notes related to BPMN Processes
  8. All changes to developed BPMN processes are version controlled and tracked
 Establish a base tool for Graphical BPMN Process development in the ATF KMS that includes a dashboard for users to view and manage the processes
Ref: Process Dashboard in each ATF KMS wiki 		Pilot the use of the BPMN process tool on various ATF processes and validate functionality with feedback from the process owners and users.
Ref: Process Dashboard in each ATF KMS wiki 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
6 Customer Test Inquiry Tracking in the ATF KMS (see #1 above)
ATF seeks to empower all Test Managers to more easily capture and track the potential business inquiries that ATF responds to by providing a dedicated knowledge management based electronic workflow for customer test inquiries at ATF. The tool will be increasingly valuable to management over time in analyzing the types of inquires received and why work did or did not come to ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new Test Inquiries with properties in the semantic database
  2. Users can easily View and Edit individual Test Inquiries
  3. Users can easily List and Sort all defined Test Inquiries
  4. Users can easily upload files relating to Test Inquiries
  5. Users can easily add and status actions relating to Test Inquires
  6. Users can easily capture meeting notes related to Test Inquiries
  7. All changes to Test Inquiries are version controlled and tracked
 Establish a base tool for Test Inquiry creation in the ATF KMS that includes a dashboard for users to view and manage the Inquiries
Ref: Test Inquiry Dashboard in each ATF KMS wiki 		Pilot the use of the Test Inquiry tool with various ATF Test Managers and validate functionality with feedback from the process owners and users.
Ref: Test Inquiry Dashboard in each ATF KMS wiki 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
7 Define and Track Facility and Customer Projects and Tests (see #1 above)
ATF seeks to empower all Test Managers to more easily capture and track the various work that is performed at ATF by providing a dedicated knowledge management based electronic workflow for Facility Project and Customer Tests at ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new Facility and Customer Projects and Tests with properties in the semantic database
  2. Users can easily View and Edit individual Facility and Customer Projects and Tests
  3. Users can easily List and Sort all defined Facility and Customer Projects and Tests
  4. Users can easily upload files relating to Facility and Customer Projects and Tests
  5. Users can easily add and status actions relating to Facility and Customer Projects and Tests
  6. Users can easily capture meeting notes related to Facility and Customer Projects and Tests
  7. All changes to Facility and Customer Projects and Tests are version controlled and tracked
 Establish a base tool for Facility and Customer Projects and Tests creation in the ATF KMS that includes a dashboard for users to view and manage the Facility and Customer Projects and Tests
Ref: Facility and Customer Projects and Test Dashboards in each ATF KMS wiki 		Pilot the use of the Facility and Customer Projects and Tests tool with various ATF Test Managers and validate functionality with feedback from the process owners and users.
Ref: Facility and Customer Projects and Test Dashboards in each ATF KMS wiki 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
8 Digital Conversion and Management of all Legacy Records in the ATF Libraries (see #1 above)
ATF seeks to empower all Record Managers at ATF to more easily transition to all-electronic records handling at ATF by providing a dedicated knowledge management based electronic workflow for Records Management at ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new Records with properties in the semantic database
  2. Users can easily View and Edit individual Records
  3. Users can easily List and Sort all defined Records
  4. Users can easily upload files relating to Records
  5. Users can easily add and status actions relating to Records
  6. Users can easily capture meeting notes related to Records
  7. All changes to Records are version controlled and tracked
  8. Users can perform complex queries of Records using a dedicated search tool
 Establish a base tool for Record creation in the ATF KMS that includes a dashboard for users to view and manage the Records in the ATF KMS
Ref: XAR Tool in each ATF KMS wiki 		Pilot the use of the Records tool with various ATF Libraries and validate functionality with feedback from the ATF Records Liaison Officer (RLO) and other users.
Ref: XAR Tool in each ATF KMS wiki 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
9 Facility Light Operations and notification Management
ATF seeks to empower all Facilities to better communicate the status of their test activities to all ATF staff by providing a dedicated knowledge management based Facility Light Status Management system for ATF. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new Facility Operational State Assertions with properties in the semantic database
  2. Users can easily List all defined Facility Operational State Assertions
  3. All changes to Records are version controlled and tracked
  4. The ATF KMS shall send a standardized notification to all ATF Staff upon creation of a new Light Status Assertion
 Establish a base tool for creating Facility Operational State Assertions in the ATF KMS that includes a dashboard for users to view and manage the Facility Operational State Assertions in the ATF KMS
Ref: Light Status Tool in each ATF KMS wikis 		Pilot the use of the Facility Operational State Assertion tool with a specific ATF Test Site and validate functionality with feedback from the ATF Test Managers, Operations Staff and Station Management.
Ref: Light Status Tool in each ATF KMS wikis 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
10 Working Group Knowledge Management
ATF seeks to empower all of the various groups of users at ATF to better manage and communicate the status of their actions and plans by providing a dedicated knowledge management based Working Group tool for all ATF users to use. 		The ATF KMS must be able to provide the following functionality:
  1. Users can easily Create and Submit new Working Groups with properties in the semantic database
  2. Users can easily View and Edit individual Working Groups
  3. Users can easily List and Sort all defined Working Groups
  4. Users can easily upload files relating to Working Groups
  5. Users can easily add and status actions relating to Working Groups
  6. Users can easily capture meeting notes related to Working Groups
  7. All changes to Working Groups are version controlled and tracked
  8. Users can easily develop graphical processes defined by the Working Group
  9. Users can easily create a Gantt Chart for Work Group related project management
 Establish a base tool for creating and using Working Groups in the ATF KMS that includes a dashboard for each Working Group that allows users to view and manage all of the information captured in each Working Group
Ref: List of Working Groups in each ATF KMS wikis 		Pilot the use of the Working Group tool with specific working groups at ATF and validate the usefulness and functionality of the tools.
Ref: List of Working Groups in each ATF KMS wikis 		Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
# DT Objectives achieved in 2021 or earlier Success Criteria Milestone 1 Milestone 2 Status
11 Automate routine and repetitive tasks on the server (see #1 above)
ATF seeks to automate all of the basic system housekeeping and notification handling as needed to make the ATF KMS as friendly, efficient and effective as possible. 		Repetitive, well-defined tasks that are integral to KM management and the digital transformation of workflows must be implemented as idempotent server scripts run either on a schedule or as-needed
  1. The Server shall automate the distribution of common content from a central site to multiple destination sites
  2. The Server shall automate the protection of content distributed on each site
  3. The Server shall automate the creation of notifications based on conditions defined in wiki content
  4. The Server shall automate the sending of notifications that are requested
  5. The Server shall automate the synchronization of data across wikis
 Use existing open-source libraries designed to utilize MediaWiki's API functionality in conjunction with an efficient programming language for data processing
Status: Milestone Complete
  • Mwclient [1]
  • Python
  • Additional libraries as needed

References:

  1. https://github.com/mwclient/mwclient
 Generate building block scripts that, when used in combination, can implement all necessary functions for all-electronic workflows
Status: Milestone Complete
  • The dissemination of KM tools from the KM development site to the production wikis are managed by a page transfer script and image transfer script
  • The dissemination of facility operational status and safety information is managed by a script to create notifications, a script to send them, and a script to sync data across wikis
  • The archival of documents on schedule is handled by a script that saves an article as a PDF to a specified file folder, and another script that manages the archive scheduling
  • Traditional directory structures can be imported into the KM using a folder import / file upload script
  • The current KM software version description can be saved as a page that retains the software history
  • Metrology data is synced with the LTID database nightly so that calibration information is available to all, rather than only the calibration POC
 Milestone Status:
  1. Complete
  2. Complete

Forward Work:

  1. Maintain
  2. Develop supporting BMS Documents
  3. Provide Training
  4. Transition scripts to NASA github [1]
References:
  1. https://github.com/nasa/grc-atf-kms-tools

Digital Transformation activities at GRC-ATF planned for CY 2022-2023

Activities that will be completed in CY 2022 – 2023 or ongoing activities that will be initiated in CY 2022 – 2023.

# Planned DT Objectives to meet in 2022-2023 Success Criteria Milestone 1 Milestone 2 Status
1 Digital conversion of all physical (paper and mixed-media) records in the HTF Library
ATF seeks to digitize all of our existing paper records in the HTF Library 		The digital conversion of all physical records in the HTF Library will be successful when:
  1. All physical (paper and mixed-media) records in the HTF Library are optically scanned to meet NARA standards
  2. All optically scanned HTF records from the HTF library are uploaded to the ATF KMS HTF Wiki Records Management Tool
 Ensure that all known HTF Library Records are defined in the ATF KMS HTF Wiki Have all HTF physical records optically scanned and uploaded to the ATF KMS HTF Records Management System
 Milestone Status:
  1. Complete
  2. Incomplete

Forward Work:

  1. Complete Milestone 2
  2. Develop supporting BMS Documents
  3. Provide Training
# Planned DT Objectives to meet in 2022-2023 Success Criteria Milestone 1 Milestone 2 Status
2 All-Electronic Work Instructions
ATF seeks to eliminate the use of paper from the process of authorizing and performing all work instructions at ATF by providing a dedicated knowledge management based electronic workflow for all Work Instructions at ATF. 		The digital transformation of ATF work instructions will be successful when:
  1. Subscription-based, WiFi and Cellular enabled Tablets are obtained from Code V that meet all of the requirements defined in the ATF Work Instruction Management System (WIMS) Project Plan for field electronics.
  2. A comprehensive WiFi/Cellular coverage survey is performed across the entire ATF campus and includes building and structure interiors and shows that there is sufficient wireless coverage to facilitate connection to the NASA network from authorized field electronics.
  3. The WIMS is developed and is proven to effectively meet all of the requirements defined in the ATF Work Instruction Management System (WIMS) Project Plan.
  4. Conversion of all active pre-existing work instructions at ATF
 A pilot project to develop the WIMS and convert a set of 4 pre-existing ATF paper work instructions is successful. All existing paper-based work instructions are successfully converted to the WIMS and validated by their use in the ATF KMS by TFOME. Milestone Status:
  1. Incomplete
  2. Incomplete

Forward Work:

  1. Complete Milestones
  2. Develop supporting BMS Documents
  3. Provide Training
# Planned DT Objectives to meet in 2022-2023 Success Criteria Milestone 1 Milestone 2 Status
3 Develop System Inventory Management Tools
ATF seeks to integrate the data already available in the NASA property system with additional data that is uniquely in the ATF KMS relating the how, where and why various equipment has been used. 		The digital transformation of System Inventory management will be successful when:
  1. data from the NASA property database is nightly synchronized with the ATF KMS
  2. ATF users can tag property with various meta-data that will allow it to be associated with specific Facility Systems
  3. ATF users can tag property with various meta-data that will allow it to be associated with specific Facility Projects and Tests
 Establish an Interconnection agreement with the GRC Property team to allow the ATF KMS to stay synchronized with the data in the NASA property database relating to Code H users. A pilot project to have a facility system manager use the facility system inventory management tool tag inventory as relating to their system and capture other system use related context as appropriate. Milestone Status:
  1. Incomplete
  2. Incomplete

Forward Work:

  1. Complete Milestones
  2. Develop supporting BMS Documents
  3. Provide Training
# Planned DT Objectives to meet in 2022-2023 Success Criteria Milestone 1 Milestone 2 Status
4 Develop a Risk Management System for ATF and RPT
ATF seeks to add Risk Management to its suite of Knowledge Management Tools. The approach will partner with the Agency's Rocket Propulsion Test (RPT) Project and will meet all of the Risk Management requirements of the NASA, GRC, ATF, and RPT. 		The ATF KMS based RMS will be successful when it has met the following success criteria:
  1. Users can easily Create and Submit new Risks with properties available as semantic data
  2. Users can easily View and Edit individual Risks
  3. Users can easily List and Sort all defined Risks
 Milestone Status:
  1. Incomplete
  2. Incomplete

Forward Work:

  1. Complete Milestones
  2. Develop supporting BMS Documents
  3. Provide Training
# Planned DT Objectives to meet in 2022-2023 Success Criteria Milestone 1 Milestone 2 Status
5 Establish ATF KMS Project on "code.nasa.gov"
ATF seeks to make the ATF KMS project a publicly available project using NASA's https://code.nasa.gov initiative. 		This Objective will be successful when it has met the following success criteria:
  1. All ATF KMS Core Template namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
  2. All ATF KMS Core Form namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
  3. All ATF KMS Core Property namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
  4. All ATF KMS Core Category namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
  5. All ATF KMS Core Content namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
  6. All ATF KMS Core Mediawiki namespace pages are intrinsically maintained and obtained from https://code.nasa.gov
 Establish a community standard method of using github.com as a repo for Mediawiki page content Demonstrate that the ATF KMS is using github as the repository for its core kms content in the ATF KMS pbs-kms-dev wiki. Milestone Status:
  1. Incomplete
  2. Incomplete

Forward Work:

  1. Complete Milestones
  2. Develop supporting BMS Documents
  3. Provide Training


Digital Transformation activities at GRC-ATF planned for CY 2024 and beyond

Activities that will be completed in CY 2024+ or ongoing activities that will be initiated in CY 2024+.

# Planned DT Objectives to meet in 2024 and beyond Success Criteria Milestone 1 Milestone 2 Status
1 Implementation of Natural Language Processing (NLP) to perform ad-hoc queries on-demand in the ATF KMS
By establishing a Web 3.0 (Semantic Web) compliant Knowledge Management application server at ATF and digitally transforming many of the key processes used by ATF staff to perform their work, ATF has already done the hardest part of achieving an NLP capability; namely, the task of "Ontologizing" all of the essential concepts relating to work at ATF and defining the Taxonomies of the data products produced by these tools. The result is a real-time, ever-growing "Knowledge Graph" of all of the "knowledge" created in the ATF KMS system during the normal course of work by users using these tools. The last few steps to achieving an NLP capability should be straight-forward once the tools and methods are identified and integrated into the ATF KMS system.


Simplified Definitions:

Ontology Defines relationships between types of things
Taxonomy Classifies things into Categories
Knowledge Graph An instantiation of an Ontology
Synonyms Substitute words that can be used to represent the same or similar things

Ref: KMS Overview Charts.pptx

The ATF KMS system provides the correct answers to the following questions when asked:
  • What tests have been performed at <Facility X> by <Cusomer Y> this year?
  • What tests are planned for next year?
  • How many hours of Yellow Light Operations were conducted at Facility X in the past year?
  • Which Work Instructions have the greatest likelihood of nonconformances when run?
 Develop the ability to do facet analysis of the ATF KMS Knowledge Graph using its "triplestore"
  • Expose ATF KMS knowledge graph triplestore to Neo4J (or something like Neo4J)
  • Translate the Ontologies and Taxonomies defined in the ATF KMS to Neo4J (or something like Neo4J)
  • Develop a base set of Synonyms that map natural language expressions (i.e. "Last Year", "at ATF", etc.. ) to facet/SPARL query constructors.
 Develop a wiki front-end for Neo4J (or something like Neo4J) Milestone Status:
  1. Incomplete
  2. Incomplete

Forward Work:

  1. Complete Milestones
  2. Develop supporting BMS Documents
  3. Provide Training


Retrieved from "https://mwstake.org/w/index.php?title=User:Revansx/GRC_Code_H_Digital_Transformation_Implementation_Plan_Submission&oldid=3154"