GLoW Roadmap

Common knowledge is about your experience and what you know.
Critical knowledge is about your expertise and how you think.

This project is being carried out under the aegis of the 
Truth Beauty and Goodness Commission.

Introduction

What is the Global Library of Wisdom (GLoW)?

GLoW is a digital knowledge base that has been specifically curated to contain data that is categorized as wisdom. Wisdom in this case pertains to what is commonly referred to as best practices, and their opposite, bad practices.

The Global Library of Wisdom:

• Has a goal.
• Has specific inputs.
• Has specific outputs.
• Uses resources.
• Has a number of activities that are performed in some order.
• Creates value for the user.

There are three main types of GLoW processes:

1. Management processes: these are the processes that govern the operation of GLoW and are usually administrative in nature, such as regular backups and process documentation maintenance.
2. Editorial processes: these are the processes that constitute the core business of GLoW, and deal primarily with the production and control of content and its input into the GLoW knowledge base.
3. Supporting processes: these are the processes that support the core operational processes. These supporting processes usually have to do with the creation and maintenance of specialized tools used by the other processes, such as the New Content Submittal Form.

What is the purpose of the Global Library of Wisdom?

The purpose of GLoW is to make accessible to the public a curated collection of well structured and highly focused wisdom relating to planetary management best practices, and bad practices, oriented towards the eventual achievement of planetary Light and Life status.

Documentation for the Global Library of Wisdom.

The result of business process modeling is a collection of documents of various types. Some are long, some are short, some are graphical, and most are text. It is important to keep these documents well structured and concise, using plain language. The style used is less important. While they are generally technical in nature, the documents must nonetheless be user friendly for the people who will use them. The documents follow the hierarchy indicated below.

The GLoW business process model consists of the following core documents which are located at: [LINK TO DOCUMENT REPOSITORY]

This Roadmap document that you are now reading is part of these core documents, and it explains the main concepts and reasons for modeling the GLoW system, its associated resources, and how to maintain them.

• GLoW Diagrams 
  A xxxx file containing various diagrams that are used to visually map out the GLoW process. These diagrams use the Business Process Modeling Notation 2.0 (BPMN). This is a high level document which only provides an outline of the process in a graphical format. It explains what needs to be done.
• GLoW Business Rules 
  This document contains the various business rules used to understand the process. This is a mid-level document which exposes the logic of the process. It explains why things are done.
• GLoW Procedures
  This document contains the various procedures used to execute the process. This is a low level document which exposes the details of the process. It explains how things are done.

Additional Support Documentation.

The following documents are located in: [LINK TO SUPPORTING DOCUMENTS]

• New Editor Orientation (onboarding manual for new editorial staff)
• System Administrator Orientation (onboarding manual for new System Admins)
• GLoW Specifications Manual (details of GLoW system for IT staff)
• BPMN Spec 2.0.pdf (reference manual for BPMN specification)

Maintenance of GLoW documentation.

Maintaining the documentation that makes up the GLoW business process model is an ongoing activity, and is the responsibility of the entire GLoW Operational Team. Complete maintenance details are contained in a separate GLoW Document Maintenance Schedule.

Process diagrams are at a higher level than business rules, and should only be changed when the process changes. Changing the process diagrams can lead to many changes in the business rules. Changes to the process diagrams should be considered carefully by the entire GLoW Team since they reflect significant changes in the organization. Changes to the process diagrams should always be done in accordance with the BPMN 2.0 standard.

Business rules are at a lower level than the process diagrams. You can change a business rule without changing the process diagrams. Business rules are easier to change and maintain than the process diagrams, and can be done by the individual(s) who have the knowledge that needs to be recorded in the rules. Once a change is made to a business rule, the entire GLoW Team should be notified of the change. There are currently no widely accepted standards for writing business rules, however, they generally fall into the category of technical documents, and should always be user friendly for the people who will use them. 

Procedures are at the lowest level. You can change a procedure without changing the process diagrams or the business rules. Procedures are easy to change and maintain, and can be done by the individual(s) who have the knowledge that needs to be recorded in the procedures. Once a change is made to a procedure, the entire GLoW Team should be notified of the change. Procedures should always be user friendly for the people who will use them. Procedures change often and they require frequent maintenance.

Whenever you revise one or more of these core documents you should also append the document’s version history table, usually on the second page, or the version number located at the bottom of the sheet in the case of a diagram.