MWStake - User contributions [en]

Charter

2025-02-03T17:22:45Z

Revansx:

<div class="toclimit-2" style="float:right;">__TOC__</div>
__NOEDITSECTION__
'''Charter''' (Articles of Incorporation) of MediaWiki Stakeholders' Group (MWStake).
: {{Note|Also see [[Bylaws]].}}

==Name, Location, and Applicable Law==
===The name of the corporation will be '''MediaWiki Stakeholders' Group''' (hereinafter "the Corporation").===
===The headquarters will be at '''146A East King St PMB 1003 Lancaster, PA 17602''', which may from time to time be changed by resolution of the board of directors.===
===The Corporation will be governed by the laws of the '''State of Pennsylvania''' and the '''United States of America'''.===
===The Corporation is registered as a 501(c)(6) Non-Profit Organization===
==Vision, Purpose, and Activities==
===The '''Vision''' of the corporation is to '''make MediaWiki the most effective open source knowledge sharing software'''.===
===The '''Purpose''' of the Corporation is to '''preserve and promote MediaWiki as open-source collaboration software for the benefit of all users'''.===
===The Corporation will engage in '''Activities''' to support this purpose:===
==== Contribute to the development of MediaWiki; ====
==== Maintain MediaWiki and its extensions; ====
==== Improve documentation for MediaWiki and its extensions; ====
==== Cooperate and liaison with the Wikimedia Foundation, Inc.; ====
==== Coordinate between MediaWiki developers, operators, and users; ====
==== Promote MediaWiki to the public; ====
==== Act as a patron and coordinator for international gatherings, conferences, hackathons, etc.; ====
==== Advocate on behalf of third-party users of MediaWiki; and ====
==== Foster best practices for MediaWiki and its users. ====
===The Corporation does not contemplate pecuniary gain or profit, incidental or otherwise.===

==Board of Directors==
{| class="wikitable sortable" style="margin-left:35px;"
|-
! Name !! Role
|-
| Bernhard Krabina || Member
|-
| Bryan Hilderbrand || Secretary
|-
| Cindy Cicalese || Member
|-
| Eric-Jan van Kakerken || Treasurer
|-
| Adam Shoreland || Member
|-
| Lex Sulzer || Member
|-
| Mark Hershberger || President
|-
| Markus Glaser || Member
|}

Charter

2025-02-03T17:20:00Z

Revansx:

<div class="toclimit-2" style="float:right;">__TOC__</div>
__NOEDITSECTION__
'''Charter''' (Articles of Incorporation) of MediaWiki Stakeholders' Group (MWStake).
: {{Note|Also see [[Bylaws]].}}

==Name, Location, and Applicable Law==
===The name of the corporation will be '''MediaWiki Stakeholders' Group''' (hereinafter "the Corporation").===
===The headquarters will be at '''146A East King St PMB 1003 Lancaster, PA 17602''', which may from time to time be changed by resolution of the board of directors.===

===The Corporation will be governed by the laws of the '''State of Pennsylvania''' and the '''United States of America'''.===

==Vision, Purpose, and Activities==
===The '''Vision''' of the corporation is to '''make MediaWiki the most effective open source knowledge sharing software'''.===
===The '''Purpose''' of the Corporation is to '''preserve and promote MediaWiki as open-source collaboration software for the benefit of all users'''.===
===The Corporation will engage in '''Activities''' to support this purpose:===
==== Contribute to the development of MediaWiki; ====
==== Maintain MediaWiki and its extensions; ====
==== Improve documentation for MediaWiki and its extensions; ====
==== Cooperate and liaison with the Wikimedia Foundation, Inc.; ====
==== Coordinate between MediaWiki developers, operators, and users; ====
==== Promote MediaWiki to the public; ====
==== Act as a patron and coordinator for international gatherings, conferences, hackathons, etc.; ====
==== Advocate on behalf of third-party users of MediaWiki; and ====
==== Foster best practices for MediaWiki and its users. ====
===The Corporation does not contemplate pecuniary gain or profit, incidental or otherwise.===

==Board of Directors==
{| class="wikitable sortable" style="margin-left:35px;"
|-
! Name !! Role
|-
| Bernhard Krabina || Member
|-
| Bryan Hilderbrand || Secretary
|-
| Cindy Cicalese || Member
|-
| Eric-Jan van Kakerken || Treasurer
|-
| Adam Shoreland || Member
|-
| Lex Sulzer || Member
|-
| Mark Hershberger || President
|-
| Markus Glaser || Member
|}

Electronic Work Instruction Management System (EWIMS)

2022-11-03T03:55:08Z

Revansx:

'''<big><big>Development of a Proof-Of-Concept Work Instruction Management System (WIMS) for NASA's ATF KMS</big></big>'''
==Background==
This document describes the work to be performed for a software pilot project at the NASA Glenn Research Center’s (GRC) Neil A. Armstrong Test Facility (ATF) in Sandusky, OH. The goal of this software pilot project is to show how the existing Mediawiki-based Knowledge Management System (KMS) at GRC-ATF can be enhanced to facilitate a transition from a paper-based work instruction performance process to an all-electronic (and specifically all-mediawiki-based) implementation of the existing work instruction development and execution processes. This pilot project requires the conversion of four (4) of NASA's existing Microsoft Word-based work instructions into the Mediawiki-based format and a demonstration that they can be successfully developed and executed entirely within the ATF KMS system using enhancements to be determined.

==Scope of Work==
All activities required to develop and test an all electronic wiki-based work instruction system that meets these requirements.

== Milestone planning ==
{| class="wikitable"
!Milestone
!Expected Duration
!Corresponding Date
|-
|Project Start
|*
|Nov. 15th, 2021
|-
|First release of the developed WIMS available for review and inspection by test
|120 hours
|Dec. 3rd, 2021
|-
|WIMS accepted and approved for integration into the existing NASA GRC ATF KMS
|120 hours
|Dec. 24th, 2021
|}

==Definitions==
{| class="wikitable"
!Term
!Definition
|-
|GRC ATF
|NASA Glenn Research Center's Armstrong Test Facility in Sandusky, Ohio
|-
|ATF KMS
|The Mediawiki-based Knowledge Management System at ATF
|-
|WIMS
|The 100% wiki-based "Work Instruction Management System"
|-
|WIMS Work Instruction Pages
|A class of pages generated in the ATF KMS by the WIMS that corresponds to an individual Work Instruction article that is defined, revised, and released in accordance with the procedure in Chapter 4 of NASA's GLP-H-8830.2 Rev E
|-
|WIMS As-Run Instance Pages
|A class of page generated in the ATF KMS by the WIMS that corresponds to a wiki page that is an instance of a WIMS Work Instruction that can be authorized, performed, and archived in accordance with the procedure in Chapter 5 of NASA's GLP-H-8830.2 Rev E
|}

==Applicable Documents==
{| class="wikitable"
!Document ID
!Document Title
!Revision
!Date
|-
|NASA GLP-H-8830.2
|ATF KMS Managed Work Instruction Development and Execution
|E (Draft)
|2021-10-19
|}

==Reference Documents==
{| class="wikitable"
!Document ID
!Document Title
!Hazardous/Non-hazardous
!Revision
!Date
|-
|NASA GRC-ATF PBISP-037
|Chamber Top Cap Operation
|Non-hazardous
|2
|2017-05-16
|-
|NASA GRC-ATF PBISP-043
|Spray Chamber Personnel Entry
|Hazardous
|6
|2017-05-02
|-
|NASA GRC-ATF PBSPF-029
|Low Oxygen Monitoring System
|Non-hazardous
|2
|2015-12-23
|-
|NASA GRC-ATF PBSPF-229
|VTC Low Oxygen Monitoring
|Non-hazardous
|1
|2017-06-29
|}

==Requirements==
{| class="wikitable"
!<big>'''1.0'''</big>
! colspan="2" |<big>'''Architecture Requirements'''</big>
|-
!'''#'''
!'''Requirement'''
!'''Rationale'''
|-
|1.1
|'''Mediawiki Version -''' The WIMS shall be able to be implemented entirely on the existing ATF KMS Server running MediaWiki 1.34.4
|''Rationale: The ATF KMS is currently using a custom 34.x branch of Meza [1]''
''[1] https://www.mediawiki.org/wiki/Meza''
|-
|1.2
|'''No loss of existing functionality -''' The WIMS shall not result in the loss of any existing functionality of the ATF KMS
|''Rationale: Many features of the ATF KMS that are not presently relevant to the WIMS project are essential to other capabilities of the ATF KMS.''
|-
|1.3
|'''Extension Criteria -''' The WIMS shall only introduce new extensions that are from well-established developers and maintainers and have an existing list of enterprise users
|''Rationale: NASA seeks to minimize the likelihood of becoming critically dependent on an extension that is not actively supported by the MediaWiki community.''
|-
|1.4
|'''WIMS Implementation Page Categories''' - All wiki pages created by the pilot project relating to the implementation of the WIMS requirements (i.e. Forms, Templates, Properties, Dashboards, etc..) shall be added to a MediaWiki category named "Tool - WIMS"
|''Rationale - It is necessary to be able to identify all pages that are part of the WIMS project''
|-
|1.5
|'''WIMS User Content Page Categories''' - All wiki pages generated by the WIMS shall be added to Mediawiki categories according to their type (Work Instruction, As-Run Instance, Deviation, Step Performed, etc..).
|''Rationale - It is necessary to be able to identify all pages that are generated by the WIMS project based on what they are to the WIMS.''
|-
!<big>'''2.0'''</big>
! colspan="2" |'''Work Instruction Requirements'''
|-
!'''#'''
!'''Requirement'''
!'''Rationale'''
|-
|2.1
|'''Define Work Instructions''' - The WIMS shall enable users to define Work Instructions in the WIMS in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Users need to be able to generate and maintain the list of work instructions as data in the WIMS.''
|-
|2.2
|'''Develop Revisions of Work Instructions''' - The WIMS shall enable users to develop work instructions in the WIMS as wiki articles in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Users need to be able to develop revisions of work instructions in the WIMS that can be released and performed.''
|-
|2.3
|'''Release Revisions of Work Instructions''' - .The WIMS shall allow users to release revisions of defined and developed work instructions to be performed multiple times.
|''Rationale - User should only get the latest approved revision of a work instruction.''
|-
|2.4
|'''Generate As-Run Instances''' - The WIMS shall be able to generate an "As-Run" instance of "released" revisions of Work Instructions
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to perform work instructions multiple times.''
|-
|2.5
|'''Semantically Queryable properties of the WIMS''' - The WIMS shall make the following aspects of work instructions available as semantically queryable properties:
Work Instructions Revisions:

#Title
#Revision
#Revision Date
#Owner
#Approving Signatories

As-Run Instance Pages of Work Instructions:

#Work Instruction Revision based on
#Creation date
#Approval to Proceed data
#Section Start Approval data
#Section Completion data
#Step performance data (who and when, and value when applicable)
#Per-Step Deviation text (when supplied)
#Per-Step Deviation Authorization status
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to search, list and organize work instructions and all as-run instances of work-instructions as queryable semantic data.''
|-
|2.6
|'''Track As-Run Instances''' - The WIMS shall be able to track the existence and status of each As-Run instance of a work instruction that is performed.
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to track the when work instructions are performed and what the status is.''
|-
|2.7
|'''As-Run Certification of the Document''' - The WIMS As-Run Instance Pages shall be capable of displaying the "Certification of the Document" information of which it is an instance in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the As-Run instance they are using is the latest authorized version of the work instruction.''
|-
|2.8
|'''As-Run "Approval to Proceed"''' - The WIMS As-Run Instance Pages shall be capable of allowing users to fill out the "Approval to Proceed" section of the work instruction in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the As-Run instance they are performing has been authorized to be performed.''
|-
|2.9
|'''As-Run "Section Start Approval"''' - For WIMS As-Run Instance Pages that are approved to proceed, the WIMS As-Run Instance Pages shall be capable of allowing users to fill out the "Section Start Approval" page in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the sections of the As-Run instance they are performing are authorized to be performed.''
|-
|2.10
|'''As-Run "Section Completion"''' - For WIMS As-Run Instance Pages that have sections to perform indicated, the WIMS As-Run Instance Pages shall be capable of allowing users to indicate completion of a section in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to indicate when a section has been completed.''
|-
|2.11
|'''As-Run "Indication of Step Performance" Traceability''' - The WIMS As-Run Instance Pages shall be capable of having steps defined where the performer is required to indicate completion of the step in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - It is common that procedures require the performer to indicate completion of the step.''
|-
|2.12
|'''As-Run "Indication of Step Performance with Field Input"''' '''Traceability''' - The WIMS As-Run Instance Pages shall be capable of having steps defined where the performer is required to supply an alphanumeric data value at the time of performance as a prerequisite to being able to indicate completion of the step in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Sometimes procedures require the performer to capture data as part of the execution of the step.''
|-
!'''<big>3.0</big>'''
! colspan="2" |'''<big>As-Run Step Deviation Requirements</big>'''
|-
!'''#'''
!'''Requirement Text'''
!'''Rationale'''
|-
|3.1
|'''Per-step deviation state''' - For all steps, the WIMS shall '''track''' the deviation status of each step as being in one of the following 3 states:

#No deviation
#Unconfirmed deviation
#Confirmed deviation
|''Rationale - the system needs to know the deviation state of every step in order to ensure correct performance of the work instruction.''
|-
|3.2
|'''Defining deviations''' - For all steps, the WIMS shall '''allow''' users to create and edit deviation text for any step that has not been indicated as performed.
|''Rationale - Sometimes performers must deviate from the written procedure and need a way to capture the scope and details of the deviation.''
|-
|3.3
|'''Effect of editing deviations''' - For all steps, the WIMS shall set the deviation status any step to "Unconfirmed deviation" upon the creation or updating of deviation text for that step
|''Rationale - We can't allow steps to be performed with unconfirmed deviation text.''
|-
|3.4
|'''Required states for step performance -''' For all steps, the WIMS shall only allow users to indicate performance of a step that is in the "No deviation" or "Confirmed deviation" state.
|''Rationale - We can't allow steps to be performed with unconfirmed deviation text.''
|-
|3.5
|'''Confirmation of deviation''' '''text''' - For steps with deviation text, the WIMS shall '''require''' a user to manually set the deviation status to "Confirmed deviation".
|''Rationale - When deviations occur, it is essential to provide a way for the deviation to be approved separately from the act of authoring the deviation text''
|}

==Government Furnished Equipment==

#'''NASA Document GRC-H-8830.2 Rev E''' - NASA will provide the project with an electronic copy of ATF's internal ISO procedure for developing and executing work instructions: GLP-H-8830.2 Rev E. This document will provide the project with a complete specification of all aspects of developing and executing work instructions at ATF.
#'''VirtualBox image file of the current ATF KMS wiki server -''' NASA will provide the project with a single ISO image file that can be booted from Oracle's Virtual Box virtual machine software. The image file will be a completely functional and stand-alone version of the NASA KM Wiki Server that the project can use as the starting point for the deliverables
#'''Software Version Description of the ATF KMS''' from the VirtualBox image file of the NASA ATF KMS provided.
#'''Four (4) MS Word-based ATF Work Instructions Files''' - See Reference Documents Section
#

==Project Deliverables==

#'''VirtualBox image file of an upgraded NASA KM Server with WIMS capability -''' The project will provide NASA with a single ISO image file that can booted from Oracle's Virtual Box virtual machine software. The image file will be a completely functional and stand-alone version of the NASA KM Project that the project shall use as the starting point for the deliverable
#'''Verification by Demonstration of all project requirements''' - The project shall provide a demonstration to NASA to verify that all of the requirements of the project are met.
#'''Document describing any changes that were made the ATF KMS Server''' - The project shall provide NASA with a document that describes any intentional changes that were made to the ATF KMS server during the work of the project. This document shall include the following sections:
##'''Server enhancements'''
###packages updated
###packages added
###package configurations created or modified
##'''Mediawiki enhancements'''
###extensions updated
###extensions added
###extension configurations created of modified
###any modifications to the core configuration
##'''Forms, Templates, Categories, Properties'''
###New Forms, Templates, Categories, Properties
###Modified Forms, Templates, Categories, Properties
##'''Main namespace content'''
###New Main namespace content
###Modified Main namespace content
##'''All other wiki content'''
=Phase 1 Verification=
{| class="wikitable"
|'''#'''
|'''Requirement text'''
|'''Implementation in Stand-alone WIMS'''
|'''Implementation comment'''
|'''NASA Response'''
|-
|1
|Architecture Requirements
|
|
|
|-
|1.1
|Mediawiki Version
|Will be a Stand-alone wiki running MediaWiki 1.35.x
|See <nowiki>https://wims.wikibase.nl/</nowiki>
|Accept
|-
|1.2
|No loss of existing functionality
|Stand-alone, so not integrated with ATF KMS
|
|Concur
|-
|1.3
|Extension Criteria
|Possibly an extension will be needed for the as-run instances to work smoothely.
|No new extensions were created for WIMS specifically, but it does use extensions that are included in Open CSP. Also there is some JS and CSS that has now been added to MediaWiki:Common.css/js, which could be added to an extension later
|All extensions and add-ons listed in the WIMS Special:Version page need to have links to mw.o extension pages with links to code repos accessible to the public
|-
|1.4
|WIMS Implementation Page Categories
|Yes, or identifiable in other practical way.
|The pages are marked using Template:Wims page, which sets the property Class="ocspwi module page"
|Accept and ask why Categories are not used
|-
|1.5
|WIMS User Content Page Categories
|Yes, or identifiable in other practical way.
|User content has the Class property with values "Work instruction draft", "Published work instruction", "Run work instruction", "Work instruction deviation". To be discussed: how to deal with images that are uploaded through VE in Work instruction drafts or deviations? NASA has a solution which they can share
|NASA recommends using the SimpleBatchUpload Extension [1] and taking advanatge of the "add prefix to upload filename" option and use a gloablly set variable (like WIMS) and the page ID to create a filename prefix that is guaranteed to be unique for the page it is being uploaded to (i.e. the Procedure) [1] <nowiki>https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload</nowiki>
|-
|2
|Work Instruction Requirements
|
|
|
|-
|2.1
|Define Work Instructions
|Users will be able to generate and maintain the list of work instructions as data in the WIMS. Uncertain whether fully in accordance with GRC-H-8830.2 Rev E requirements.
|To create a new work instruction go to Draft Work Instructions and create a new draft. From there you will have the option to publish a new revision.
|Accept
|-
|2.2
|Develop Revisions of Work Instructions
|Work instructions can be created, edited, reviewed and released.
|Draft work instructions can be edited. A draft can be released by publishing a new revision.
|Accept
|-
|2.3
|Release Revisions of Work Instructions
|On approval, work instructions are copied to a separate namespace that only contains approved work instructions.
|Draft work instructions are in the "Draft" namespace, published revisions are in the "Published" namespace and run instances and deviations are in the "Run" namespace.
|Obsolete revisions or revisions superceeded by newer revisions must not be available to run
|-
|2.4
|Generate As-Run Instances
|Yes
|Can be created from a published work instruction
|Accept
|-
|2.5
|Semantically Queryable properties of the WIMS
|Yes
|Yes, the most important properties are Class, ID, Revision number, Revision tweak, Revision (a combination of number and tweak), Title. New ones can be added.
|Unclear - need to see scratch query examples of:
1) Steps performed in Run Instance X of proc Y
2) Steps not performed in Run Instance X of proc Y
|-
|2.6
|Track As-Run Instances
|Yes
|A published work instruction shows a list of as-run instances created from that work instruction.
|Accept
|-
|2.7
|As-Run Certification of the Document
|No, only after integration with ATF KMS.
|
|Concur
|-
|2.8
|As-Run "Approval to Proceed"
|Yes
|Creating a run instance is considered to be the approval to proceed
|Not acceptable - the authorization to proceed section is a critical aspect of our work instruction execution process which is well defined and well-documented in our 8830.2 Rev E document
|-
|2.9
|As-Run "Section Start Approval"
|Yes
|The "Work instruction section approval" template can be inserted in a draft and will show an approve button in run instances
|Accept
|-
|2.1
|As-Run "Section Completion"
|Yes
|The "Work instruction section approval" template will show a complete button after the section has been approved
|Request that both the start and completion approvals are both maintained independantly - as it is right now 'complete' replaces 'start' and we need to see both.
|-
|2.11
|As-Run "Indication of Step Performance" Traceability
|Yes
|Changes are stored in a separate parameter for each input field. These values are stored in a slot. See "Tools" > "Slots" to view slot values. The templates currently don't display these values anywhere.
|Our ISO process requires that auditors be able to see who performed each step .. And per 2.5 above all of the "as-run step performance" data needs to be queriable properties.. Once 2.5 is fulfilled, displaying data relating to the step performance should be straight-forward
|-
|2.12
|As-Run "Indication of Step Performance with Field Input" Traceability
|Yes
|See 2.11
|See 2.11 response
|-
|3
|As-Run Step Deviation Requirements
|
|
|
|-
|3.1
|Per-step deviation state
|Yes
|The steps show when they have a deviation through changing the color of the icon
|Our ISO process requires that auditors be able to see any deviations in the as-run copy. Having to click a link to see the deviation in a new page is ok for collecting the deviation text, but the deviation text needs to appear in the as-run document
|-
|3.2
|Defining deviations
|Yes
|Deviations can be added to each step through the "!" icon. They can also be edited.
|If deviations are going to be captured in a sepereate page, then the deviation page needs to include more context in order for users writing and reviewing the deviation to undertand the deviation text (not just a cryptic reference to a step id. This should include at a minimum, WI ID, WI Title, WI Revision, As-Run Creation Date, and As-Run Page ID
|-
|3.3
|Effect of editing deviations
|Yes
|To be discussed
|As stated in the requirement - For all steps, the WIMS shall set the deviation status any step to "Unconfirmed deviation" upon the creation or updating of deviation text for that step
|-
|3.4
|Required states for step performance
|Yes
|To be discussed
|As stated in the requirement - For all steps, the WIMS shall only allow users to indicate performance of a step that is in the "No deviation" or "Confirmed deviation" state.
|-
|3.5
|Confirmation of deviation text
|Yes
|To be discussed notes from meeting 14 jan: when creating a new deviation it should initially be "unconfirmed". Multiple users should be able to confirm a deviation (for example by clicking a button on the deviation page). After the first confirmation, the deviation should not be editable. There should be some kind of visual indication of the confirmation status in the run work instruction (perhaps change the icon color), also when we deviation is added after the step completion.
|Notes from meeting 14 jan to be implemented in accordance with stated requirmeents for 3.2 through 3.5
|-
| colspan="5" |'''Other Notes'''
|-
|
|
|
|
|some checkboxes don't ever display a green notification
|-
|
|
|
|
|request that check boxes immediately notify that they are working on something - rather than wait for the Saved Successfully popup
|-
|
|
|
|
|signatory name, date and time need to be captured and displayed (when they have been provided) as data - currently signature, date and time fields are not able to be captured via the wiki
|-
|
|
|
|
|nasa needs to provide a signatory input requirement
|-
|
|
|
|
|in lieu of a proper signatory input type, the work instructions need to be updated to include at least basic text entry fields for signatories and date and time
|-
|
|
|
|
|input text fields need to indicate when they are performed as empty - possibly enable/disable
|}

Electronic Work Instruction Management System (EWIMS)

2022-11-03T03:48:45Z

Revansx: /* Reference Documents */

Electronic Work Instruction Management System (EWIMS)

2022-11-03T03:42:30Z

Revansx:

Electronic Work Instruction Management System (EWIMS)

2022-11-03T03:40:23Z

Revansx:

Electronic Work Instruction Management System (EWIMS)

2022-11-03T03:39:27Z

Revansx: Created page with "'''<big><big>Development of a Proof-Of-Concept Work Instruction Management System (WIMS) for NASA's ATF KMS</big></big>''' ---- {{TOC | align=left | clear=left }} ==Background..."

'''<big><big>Development of a Proof-Of-Concept Work Instruction Management System (WIMS) for NASA's ATF KMS</big></big>'''
----
{{TOC | align=left | clear=left }}
==Background==
This document describes the work to be performed for a software pilot project at the NASA Glenn Research Center’s (GRC) Neil A. Armstrong Test Facility (ATF) in Sandusky, OH. The goal of this software pilot project is to show how the existing Mediawiki-based Knowledge Management System (KMS) at GRC-ATF can be enhanced to facilitate a transition from a paper-based work instruction performance process to an all-electronic (and specifically all-mediawiki-based) implementation of the existing work instruction development and execution processes. This pilot project requires the conversion of four (4) of NASA's existing Microsoft Word-based work instructions into the Mediawiki-based format and a demonstration that they can be successfully developed and executed entirely within the ATF KMS system using enhancements to be determined.

==Scope of Work==
All activities required to develop and test an all electronic wiki-based work instruction system that meets these requirements.

== Milestone planning ==
{| class="wikitable"
!Milestone
!Expected Duration
!Corresponding Date
|-
|Project Start
|*
|Nov. 15th, 2021
|-
|First release of the developed WIMS available for review and inspection by test
|120 hours
|Dec. 3rd, 2021
|-
|WIMS accepted and approved for integration into the existing NASA GRC ATF KMS
|120 hours
|Dec. 24th, 2021
|}

==Definitions==
{| class="wikitable"
!Term
!Definition
|-
|GRC ATF
|NASA Glenn Research Center's Armstrong Test Facility in Sandusky, Ohio
|-
|ATF KMS
|The Mediawiki-based Knowledge Management System at ATF
|-
|WIMS
|The 100% wiki-based "Work Instruction Management System"
|-
|WIMS Work Instruction Pages
|A class of pages generated in the ATF KMS by the WIMS that corresponds to an individual Work Instruction article that is defined, revised, and released in accordance with the procedure in Chapter 4 of NASA's GLP-H-8830.2 Rev E
|-
|WIMS As-Run Instance Pages
|A class of page generated in the ATF KMS by the WIMS that corresponds to a wiki page that is an instance of a WIMS Work Instruction that can be authorized, performed, and archived in accordance with the procedure in Chapter 5 of NASA's GLP-H-8830.2 Rev E
|}

==Applicable Documents==
{| class="wikitable"
!Document ID
!Document Title
!Revision
!Date
|-
|NASA GLP-H-8830.2
|ATF KMS Managed Work Instruction Development and Execution
|E (Draft)
|2021-10-19
|}

==Reference Documents==
{| class="wikitable"
!Document ID
!Document Title
!Hazardous/Non-hazardous
!Revision
!Date
|-
|PBISP-037
|Chamber Top Cap Operation
|Non-hazardous
|2
|2017-05-16
|-
|PBISP-043
|Spray Chamber Personnel Entry
|Hazardous
|6
|2017-05-02
|-
|PBSPF-029
|Low Oxygen Monitoring System
|Non-hazardous
|2
|2015-12-23
|-
|PBSPF-229
|VTC Low Oxygen Monitoring
|Non-hazardous
|1
|2017-06-29
|}

==Requirements==
{| class="wikitable"
!<big>'''1.0'''</big>
! colspan="2" |<big>'''Architecture Requirements'''</big>
|-
!'''#'''
!'''Requirement'''
!'''Rationale'''
|-
|1.1
|'''Mediawiki Version -''' The WIMS shall be able to be implemented entirely on the existing ATF KMS Server running MediaWiki 1.34.4
|''Rationale: The ATF KMS is currently using a custom 34.x branch of Meza [1]''
''[1] https://www.mediawiki.org/wiki/Meza''
|-
|1.2
|'''No loss of existing functionality -''' The WIMS shall not result in the loss of any existing functionality of the ATF KMS
|''Rationale: Many features of the ATF KMS that are not presently relevant to the WIMS project are essential to other capabilities of the ATF KMS.''
|-
|1.3
|'''Extension Criteria -''' The WIMS shall only introduce new extensions that are from well-established developers and maintainers and have an existing list of enterprise users
|''Rationale: NASA seeks to minimize the likelihood of becoming critically dependent on an extension that is not actively supported by the MediaWiki community.''
|-
|1.4
|'''WIMS Implementation Page Categories''' - All wiki pages created by the pilot project relating to the implementation of the WIMS requirements (i.e. Forms, Templates, Properties, Dashboards, etc..) shall be added to a MediaWiki category named "Tool - WIMS"
|''Rationale - It is necessary to be able to identify all pages that are part of the WIMS project''
|-
|1.5
|'''WIMS User Content Page Categories''' - All wiki pages generated by the WIMS shall be added to Mediawiki categories according to their type (Work Instruction, As-Run Instance, Deviation, Step Performed, etc..).
|''Rationale - It is necessary to be able to identify all pages that are generated by the WIMS project based on what they are to the WIMS.''
|-
!<big>'''2.0'''</big>
! colspan="2" |'''Work Instruction Requirements'''
|-
!'''#'''
!'''Requirement'''
!'''Rationale'''
|-
|2.1
|'''Define Work Instructions''' - The WIMS shall enable users to define Work Instructions in the WIMS in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Users need to be able to generate and maintain the list of work instructions as data in the WIMS.''
|-
|2.2
|'''Develop Revisions of Work Instructions''' - The WIMS shall enable users to develop work instructions in the WIMS as wiki articles in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Users need to be able to develop revisions of work instructions in the WIMS that can be released and performed.''
|-
|2.3
|'''Release Revisions of Work Instructions''' - .The WIMS shall allow users to release revisions of defined and developed work instructions to be performed multiple times.
|''Rationale - User should only get the latest approved revision of a work instruction.''
|-
|2.4
|'''Generate As-Run Instances''' - The WIMS shall be able to generate an "As-Run" instance of "released" revisions of Work Instructions
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to perform work instructions multiple times.''
|-
|2.5
|'''Semantically Queryable properties of the WIMS''' - The WIMS shall make the following aspects of work instructions available as semantically queryable properties:
Work Instructions Revisions:

#Title
#Revision
#Revision Date
#Owner
#Approving Signatories

As-Run Instance Pages of Work Instructions:

#Work Instruction Revision based on
#Creation date
#Approval to Proceed data
#Section Start Approval data
#Section Completion data
#Step performance data (who and when, and value when applicable)
#Per-Step Deviation text (when supplied)
#Per-Step Deviation Authorization status
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to search, list and organize work instructions and all as-run instances of work-instructions as queryable semantic data.''
|-
|2.6
|'''Track As-Run Instances''' - The WIMS shall be able to track the existence and status of each As-Run instance of a work instruction that is performed.
|''Rationale - It is one of the primary goals of the WIMS to provide a wiki-based system that allows users to track the when work instructions are performed and what the status is.''
|-
|2.7
|'''As-Run Certification of the Document''' - The WIMS As-Run Instance Pages shall be capable of displaying the "Certification of the Document" information of which it is an instance in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the As-Run instance they are using is the latest authorized version of the work instruction.''
|-
|2.8
|'''As-Run "Approval to Proceed"''' - The WIMS As-Run Instance Pages shall be capable of allowing users to fill out the "Approval to Proceed" section of the work instruction in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the As-Run instance they are performing has been authorized to be performed.''
|-
|2.9
|'''As-Run "Section Start Approval"''' - For WIMS As-Run Instance Pages that are approved to proceed, the WIMS As-Run Instance Pages shall be capable of allowing users to fill out the "Section Start Approval" page in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to verify that the sections of the As-Run instance they are performing are authorized to be performed.''
|-
|2.10
|'''As-Run "Section Completion"''' - For WIMS As-Run Instance Pages that have sections to perform indicated, the WIMS As-Run Instance Pages shall be capable of allowing users to indicate completion of a section in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - performers need to be able to indicate when a section has been completed.''
|-
|2.11
|'''As-Run "Indication of Step Performance" Traceability''' - The WIMS As-Run Instance Pages shall be capable of having steps defined where the performer is required to indicate completion of the step in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - It is common that procedures require the performer to indicate completion of the step.''
|-
|2.12
|'''As-Run "Indication of Step Performance with Field Input"''' '''Traceability''' - The WIMS As-Run Instance Pages shall be capable of having steps defined where the performer is required to supply an alphanumeric data value at the time of performance as a prerequisite to being able to indicate completion of the step in accordance with NASA GRC-H-8830.2 Rev E.
|''Rationale - Sometimes procedures require the performer to capture data as part of the execution of the step.''
|-
!'''<big>3.0</big>'''
! colspan="2" |'''<big>As-Run Step Deviation Requirements</big>'''
|-
!'''#'''
!'''Requirement Text'''
!'''Rationale'''
|-
|3.1
|'''Per-step deviation state''' - For all steps, the WIMS shall '''track''' the deviation status of each step as being in one of the following 3 states:

#No deviation
#Unconfirmed deviation
#Confirmed deviation
|''Rationale - the system needs to know the deviation state of every step in order to ensure correct performance of the work instruction.''
|-
|3.2
|'''Defining deviations''' - For all steps, the WIMS shall '''allow''' users to create and edit deviation text for any step that has not been indicated as performed.
|''Rationale - Sometimes performers must deviate from the written procedure and need a way to capture the scope and details of the deviation.''
|-
|3.3
|'''Effect of editing deviations''' - For all steps, the WIMS shall set the deviation status any step to "Unconfirmed deviation" upon the creation or updating of deviation text for that step
|''Rationale - We can't allow steps to be performed with unconfirmed deviation text.''
|-
|3.4
|'''Required states for step performance -''' For all steps, the WIMS shall only allow users to indicate performance of a step that is in the "No deviation" or "Confirmed deviation" state.
|''Rationale - We can't allow steps to be performed with unconfirmed deviation text.''
|-
|3.5
|'''Confirmation of deviation''' '''text''' - For steps with deviation text, the WIMS shall '''require''' a user to manually set the deviation status to "Confirmed deviation".
|''Rationale - When deviations occur, it is essential to provide a way for the deviation to be approved separately from the act of authoring the deviation text''
|}

==Government Furnished Equipment==

#'''NASA Document GRC-H-8830.2 Rev E''' - NASA will provide the project with an electronic copy of ATF's internal ISO procedure for developing and executing work instructions: GLP-H-8830.2 Rev E. This document will provide the project with a complete specification of all aspects of developing and executing work instructions at ATF.
#'''VirtualBox image file of the current ATF KMS wiki server -''' NASA will provide the project with a single ISO image file that can be booted from Oracle's Virtual Box virtual machine software. The image file will be a completely functional and stand-alone version of the NASA KM Wiki Server that the project can use as the starting point for the deliverables
#'''Software Version Description of the ATF KMS''' from the VirtualBox image file of the NASA ATF KMS provided.
#'''Four (4) MS Word-based ATF Work Instructions Files''' - See Reference Documents Section
#

==Project Deliverables==

#'''VirtualBox image file of an upgraded NASA KM Server with WIMS capability -''' The project will provide NASA with a single ISO image file that can booted from Oracle's Virtual Box virtual machine software. The image file will be a completely functional and stand-alone version of the NASA KM Project that the project shall use as the starting point for the deliverable
#'''Verification by Demonstration of all project requirements''' - The project shall provide a demonstration to NASA to verify that all of the requirements of the project are met.
#'''Document describing any changes that were made the ATF KMS Server''' - The project shall provide NASA with a document that describes any intentional changes that were made to the ATF KMS server during the work of the project. This document shall include the following sections:
##'''Server enhancements'''
###packages updated
###packages added
###package configurations created or modified
##'''Mediawiki enhancements'''
###extensions updated
###extensions added
###extension configurations created of modified
###any modifications to the core configuration
##'''Forms, Templates, Categories, Properties'''
###New Forms, Templates, Categories, Properties
###Modified Forms, Templates, Categories, Properties
##'''Main namespace content'''
###New Main namespace content
###Modified Main namespace content
##'''All other wiki content'''

{{Refs}}
<references />

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

2022-09-10T13:10:45Z

Revansx:

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 [[Mailto:anne.rowland@nasa.gov|anne.rowland@nasa.gov]].

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''
{| class="wikitable"
|-
!'''<big>#</big>'''
! style="width: 25%" |DT Objectives achieved in 2021 or earlier
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |Status
|-
|'''<big>1</big>'''
|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: [[:File:PBGENERAL9410-New KMS Charts.pptx|'''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.

*Ref: https://workforce.grc.nasa.gov/orgmanual/default.asp#H
|The Web 3.0 KM application platform shall conform to the following criteria:

#Shall be certified for use as an CUI/SBU repository of NIST MODERATE data for the organization
#Shall use LaunchPad for user authentication via SAML/ADFS
#Shall use NAMS for "Role-based" authorizations within the application
#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
#Shall only use highly-reputable, well-documented open source software [2]
#Runs on Agency supported "Platform as a Service" [3]
#All functionality is available through well-documented RESTFUL APIs [4]
#Configuration management using safe (idempotent [5]) deployment automation
#User Interface shall be a "wiki" [6]
#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.
#Shall enable users to organize file uploads as nested file structures
#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:

#[https://sharepoint.msfc.nasa.gov/sites/ap/standards/_layouts/15/WopiFrame.aspx?sourcedoc=%7bEDFA7F9B-C5F2-4E2A-8E2C-869675D71DD7%7d&file=AP%20Handbook%20v2.4.pdf https://sharepoint.msfc.nasa.gov/sites/ap/standards/.../AP-Handbook-v2.4.pdf]
#https://dodcio.defense.gov/Open-Source-Software-FAQ/
#https://www.grc.nasa.gov/ocio/pages/computing/platform-as-a-service
#https://restfulapi.net/
#https://www.w3.org/TR/ws-gloss/#defs
#http://wiki.org/wiki.cgi?WhatIsWiki
#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

#RedHat/Centos Linux
#Apache
#Haproxy
#PHP
#MySQL
#Mediawiki
#Semantic Mediawiki
#Python
#Ansible
#Mediawiki Extensions as needed
#ImageMagick
#SimpleSAMLphp
#OpenSSL
#more [1]

References:

#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:

#https://www.mediawiki.org/wiki/Meza
#https://github.com/enterprisemediawiki/meza
|Milestone Status:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>2</big>'''
|'''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:

#Allow users to define and manage documents with properties in a semantic database
#Allow users to easily view the list of defined documents and their statuss
#Allow users to easily view and download authorized copies of released documents
#Allows users to develop revisions to defined documents and submit them for version control
#Allow users to submit, and track Change Requests to existing documents
#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

*[[sbu-ptc:Checksheets|PTC Checksheets]]
*[[sbu-sec:Checksheets|SEC Checksheets]]
*[https://wiki.grc.nasa.gov/sbu-pcs/Checksheets PBS Checksheets]
*[[sbu-htf:Checksheets|HTF Checksheets]]
*[[sbu-neat:Checksheets|NEAT Checksheets]]
|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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>3</big>'''
|'''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:

#Allows users to '''define''' '''a list of systems''' with properties in a semantic database
#Allow users to '''easily view''' the list of systems
#Allow users to define the '''hazards''' of the system, any countermeasures required and track their verification as required
#Allow users to define any '''software''' used in the system
#Allow users to define any '''MTE''' used in the system
#Allow users to define the '''requirements''' of the system
#Allow users to capture the '''inventory''' of the system
#Allow users to capture the '''lessons learned''' of the system
#Allow users to capture, track and resolve '''nonconformances''' in the system
#Allow users to '''upload files''' that are specific to the system
#Allow users to capture '''meeting notes''' relating to the systems
#Allow users to define the '''operator training requirements (OTRs)'''
#Allow users to '''graphically define the processes''' of the system
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>4</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new MOCs with properties in the semantic database
#Users can easily '''View''' and '''Edit''' each MOC
#The system will '''List''' and '''Sort''' MOCs based on status
#The system will facilitate all '''PSM requirements''' of MOCs
#Users can easily upload '''files''' relating to MOCs
#Users can easily add and status '''actions''' relating to MOCs
#Users can easily capture meeting '''notes''' related to MOCs
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>5</big>'''
|'''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:

#Users can '''Create''' and '''Submit''' new processes with properties in the semantic database
#User can easily '''View''' and '''Edit''' individual BPMN Processes
#Users can easily '''List''' and '''Sort''' all defined BPMN Processes
#Users can develop BPMN compliant process in a '''graphical editor'''
#Users can easily upload '''files''' relating to BPMN Processes
#Users can easily add and status '''actions''' relating to BPMN Processes
#Users can easily capture meeting '''notes''' related to BPMN Processes
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>6</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Test Inquiries with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Test Inquiries
#Users can easily '''List''' and '''Sort''' all defined Test Inquiries
#Users can easily upload '''files''' relating to Test Inquiries
#Users can easily add and status '''actions''' relating to Test Inquires
#Users can easily capture meeting '''notes''' related to Test Inquiries
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>7</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Facility and Customer Projects and Tests with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Facility and Customer Projects and Tests
#Users can easily '''List''' and '''Sort''' all defined Facility and Customer Projects and Tests
#Users can easily upload '''files''' relating to Facility and Customer Projects and Tests
#Users can easily add and status '''actions''' relating to Facility and Customer Projects and Tests
#Users can easily capture meeting '''notes''' related to Facility and Customer Projects and Tests
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>8</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Records with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Records
#Users can easily '''List''' and '''Sort''' all defined Records
#Users can easily upload '''files''' relating to Records
#Users can easily add and status '''actions''' relating to Records
#Users can easily capture meeting '''notes''' related to Records
#All '''changes''' to Records are version controlled and tracked
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#Users can easily '''Create''' and '''Submit''' new Facility Operational State Assertions with properties in the semantic database
#Users can easily '''List''' all defined Facility Operational State Assertions
#All '''changes''' to Records are version controlled and tracked
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#Users can easily '''Create''' and '''Submit''' new Working Groups with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Working Groups
#Users can easily '''List''' and '''Sort''' all defined Working Groups
#Users can easily upload '''files''' relating to Working Groups
#Users can easily add and status '''actions''' relating to Working Groups
#Users can easily capture meeting '''notes''' related to Working Groups
#All '''changes''' to Working Groups are version controlled and tracked
#Users can easily develop '''graphical processes''' defined by the Working Group
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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

#The Server shall automate the distribution of common content from a central site to multiple destination sites
#The Server shall automate the protection of content distributed on each site
#The Server shall automate the creation of notifications based on conditions defined in wiki content
#The Server shall automate the sending of notifications that are requested
#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:

#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
#Transition scripts to NASA github [1]

----References:

#<nowiki>https://github.com/nasa/grc-atf-kms-tools</nowiki>
|}

*

==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.'''
{| class="wikitable"
|-
!'''<big>#</big>'''
! style="width: 25%" |Planned DT Objectives to meet in 2022-2023
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |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:

#All physical (paper and mixed-media) records in the HTF Library are optically scanned to meet NARA standards
#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:

#Complete
#Incomplete

Forward Work:

#Complete Milestone 2
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#'''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.
#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.
#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.
#'''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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#data from the NASA property database is nightly synchronized with the ATF KMS
#ATF users can tag property with various meta-data that will allow it to be associated with specific Facility Systems
#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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

# Users can easily '''Create''' and '''Submit''' new Risks with properties available as semantic data
# Users can easily '''View''' and '''Edit''' individual Risks
#Users can easily '''List''' and '''Sort''' all defined Risks
|
|
|Milestone Status:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

# All ATF KMS '''Core Template namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Form namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Property namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Category namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Content namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# 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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#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+.'''
{| class="wikitable"
|-
!'''<big>#</big>'''
! style="width: 25%" |Planned DT Objectives to meet in 2024 and beyond
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |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:'''
{| class="wikitable" style="all: unset;"
|'''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: [[:File:PBGENERAL9410-New KMS Charts.pptx|'''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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|}

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

2022-09-10T13:09:53Z

Revansx: Created page with "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..."

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 [[Mailto:anne.rowland@nasa.gov|anne.rowland@nasa.gov]].

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''
{| class="zTblATFstd1"
|-
!'''<big>#</big>'''
! style="width: 25%" |DT Objectives achieved in 2021 or earlier
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |Status
|-
|'''<big>1</big>'''
|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: [[:File:PBGENERAL9410-New KMS Charts.pptx|'''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.

*Ref: https://workforce.grc.nasa.gov/orgmanual/default.asp#H
|The Web 3.0 KM application platform shall conform to the following criteria:

#Shall be certified for use as an CUI/SBU repository of NIST MODERATE data for the organization
#Shall use LaunchPad for user authentication via SAML/ADFS
#Shall use NAMS for "Role-based" authorizations within the application
#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
#Shall only use highly-reputable, well-documented open source software [2]
#Runs on Agency supported "Platform as a Service" [3]
#All functionality is available through well-documented RESTFUL APIs [4]
#Configuration management using safe (idempotent [5]) deployment automation
#User Interface shall be a "wiki" [6]
#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.
#Shall enable users to organize file uploads as nested file structures
#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:

#[https://sharepoint.msfc.nasa.gov/sites/ap/standards/_layouts/15/WopiFrame.aspx?sourcedoc=%7bEDFA7F9B-C5F2-4E2A-8E2C-869675D71DD7%7d&file=AP%20Handbook%20v2.4.pdf https://sharepoint.msfc.nasa.gov/sites/ap/standards/.../AP-Handbook-v2.4.pdf]
#https://dodcio.defense.gov/Open-Source-Software-FAQ/
#https://www.grc.nasa.gov/ocio/pages/computing/platform-as-a-service
#https://restfulapi.net/
#https://www.w3.org/TR/ws-gloss/#defs
#http://wiki.org/wiki.cgi?WhatIsWiki
#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

#RedHat/Centos Linux
#Apache
#Haproxy
#PHP
#MySQL
#Mediawiki
#Semantic Mediawiki
#Python
#Ansible
#Mediawiki Extensions as needed
#ImageMagick
#SimpleSAMLphp
#OpenSSL
#more [1]

References:

#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:

#https://www.mediawiki.org/wiki/Meza
#https://github.com/enterprisemediawiki/meza
|Milestone Status:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>2</big>'''
|'''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:

#Allow users to define and manage documents with properties in a semantic database
#Allow users to easily view the list of defined documents and their statuss
#Allow users to easily view and download authorized copies of released documents
#Allows users to develop revisions to defined documents and submit them for version control
#Allow users to submit, and track Change Requests to existing documents
#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

*[[sbu-ptc:Checksheets|PTC Checksheets]]
*[[sbu-sec:Checksheets|SEC Checksheets]]
*[https://wiki.grc.nasa.gov/sbu-pcs/Checksheets PBS Checksheets]
*[[sbu-htf:Checksheets|HTF Checksheets]]
*[[sbu-neat:Checksheets|NEAT Checksheets]]
|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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>3</big>'''
|'''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:

#Allows users to '''define''' '''a list of systems''' with properties in a semantic database
#Allow users to '''easily view''' the list of systems
#Allow users to define the '''hazards''' of the system, any countermeasures required and track their verification as required
#Allow users to define any '''software''' used in the system
#Allow users to define any '''MTE''' used in the system
#Allow users to define the '''requirements''' of the system
#Allow users to capture the '''inventory''' of the system
#Allow users to capture the '''lessons learned''' of the system
#Allow users to capture, track and resolve '''nonconformances''' in the system
#Allow users to '''upload files''' that are specific to the system
#Allow users to capture '''meeting notes''' relating to the systems
#Allow users to define the '''operator training requirements (OTRs)'''
#Allow users to '''graphically define the processes''' of the system
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>4</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new MOCs with properties in the semantic database
#Users can easily '''View''' and '''Edit''' each MOC
#The system will '''List''' and '''Sort''' MOCs based on status
#The system will facilitate all '''PSM requirements''' of MOCs
#Users can easily upload '''files''' relating to MOCs
#Users can easily add and status '''actions''' relating to MOCs
#Users can easily capture meeting '''notes''' related to MOCs
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>5</big>'''
|'''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:

#Users can '''Create''' and '''Submit''' new processes with properties in the semantic database
#User can easily '''View''' and '''Edit''' individual BPMN Processes
#Users can easily '''List''' and '''Sort''' all defined BPMN Processes
#Users can develop BPMN compliant process in a '''graphical editor'''
#Users can easily upload '''files''' relating to BPMN Processes
#Users can easily add and status '''actions''' relating to BPMN Processes
#Users can easily capture meeting '''notes''' related to BPMN Processes
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>6</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Test Inquiries with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Test Inquiries
#Users can easily '''List''' and '''Sort''' all defined Test Inquiries
#Users can easily upload '''files''' relating to Test Inquiries
#Users can easily add and status '''actions''' relating to Test Inquires
#Users can easily capture meeting '''notes''' related to Test Inquiries
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>7</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Facility and Customer Projects and Tests with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Facility and Customer Projects and Tests
#Users can easily '''List''' and '''Sort''' all defined Facility and Customer Projects and Tests
#Users can easily upload '''files''' relating to Facility and Customer Projects and Tests
#Users can easily add and status '''actions''' relating to Facility and Customer Projects and Tests
#Users can easily capture meeting '''notes''' related to Facility and Customer Projects and Tests
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!DT Objectives achieved in 2021 or earlier
!Success Criteria
!Milestone 1
!Milestone 2
!Status
|-
|'''<big>8</big>'''
|'''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:

#Users can easily '''Create''' and '''Submit''' new Records with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Records
#Users can easily '''List''' and '''Sort''' all defined Records
#Users can easily upload '''files''' relating to Records
#Users can easily add and status '''actions''' relating to Records
#Users can easily capture meeting '''notes''' related to Records
#All '''changes''' to Records are version controlled and tracked
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#Users can easily '''Create''' and '''Submit''' new Facility Operational State Assertions with properties in the semantic database
#Users can easily '''List''' all defined Facility Operational State Assertions
#All '''changes''' to Records are version controlled and tracked
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#Users can easily '''Create''' and '''Submit''' new Working Groups with properties in the semantic database
#Users can easily '''View''' and '''Edit''' individual Working Groups
#Users can easily '''List''' and '''Sort''' all defined Working Groups
#Users can easily upload '''files''' relating to Working Groups
#Users can easily add and status '''actions''' relating to Working Groups
#Users can easily capture meeting '''notes''' related to Working Groups
#All '''changes''' to Working Groups are version controlled and tracked
#Users can easily develop '''graphical processes''' defined by the Working Group
#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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

#The Server shall automate the distribution of common content from a central site to multiple destination sites
#The Server shall automate the protection of content distributed on each site
#The Server shall automate the creation of notifications based on conditions defined in wiki content
#The Server shall automate the sending of notifications that are requested
#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:

#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:

#Complete
#Complete

Forward Work:

#Maintain
#Develop supporting BMS Documents
#Provide Training
#Transition scripts to NASA github [1]

----References:

#<nowiki>https://github.com/nasa/grc-atf-kms-tools</nowiki>
|}

*

==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.'''
{| class="zTblATFstd1"
|-
!'''<big>#</big>'''
! style="width: 25%" |Planned DT Objectives to meet in 2022-2023
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |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:

#All physical (paper and mixed-media) records in the HTF Library are optically scanned to meet NARA standards
#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:

#Complete
#Incomplete

Forward Work:

#Complete Milestone 2
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#'''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.
#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.
#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.
#'''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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

#data from the NASA property database is nightly synchronized with the ATF KMS
#ATF users can tag property with various meta-data that will allow it to be associated with specific Facility Systems
#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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

# Users can easily '''Create''' and '''Submit''' new Risks with properties available as semantic data
# Users can easily '''View''' and '''Edit''' individual Risks
#Users can easily '''List''' and '''Sort''' all defined Risks
|
|
|Milestone Status:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|-
!'''<big>#</big>'''
!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:

# All ATF KMS '''Core Template namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Form namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Property namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Category namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# All ATF KMS '''Core Content namespace pages''' are intrinsically maintained and obtained from https://code.nasa.gov
# 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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#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+.'''
{| class="zTblATFstd1"
|-
!'''<big>#</big>'''
! style="width: 25%" |Planned DT Objectives to meet in 2024 and beyond
! style="width: 25%" |Success Criteria
! style="width: 16%" |Milestone 1
! style="width: 16%" |Milestone 2
! style="width: 16%" |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:'''
{| class="wikitable" style="all: unset;"
|'''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: [[:File:PBGENERAL9410-New KMS Charts.pptx|'''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:

#Incomplete
#Incomplete

Forward Work:

#Complete Milestones
#Develop supporting BMS Documents
#Provide Training
|}

User:Revansx

2022-09-10T13:09:38Z

Revansx: Created page with "* User:Revansx/GRC Code H Digital Transformation Implementation Plan Submission"

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

File:The Wiki as a Mcluhan Effect of Media Tetrad.PNG

2022-09-02T16:16:37Z

Revansx:

Ref: https://en.wikipedia.org/wiki/Tetrad_of_media_effects

File:The Wiki as a Mcluhan Effect of Media Tetrad.PNG

2022-09-02T16:14:44Z

Revansx: