Terraphim role node creation #20
Description
In the beginning, the user has a templated Business function node(s), for example:
type:: [[Business function]]
source:: [[@Digital Systems Engineering Process Model Version 1]]
documentation:: As stated in ISO/IEC/IEEE 15288, [6.2.5.1] The purpose of the Quality Management process is to assure that products, services and implementations of the quality management process meet organizational and project quality objectives and achieve customer satisfaction. See detailed description in the INCOSE Handbook v.4, page 156.
inputs:: [[Organization strategic plan]], [[Quality assurance plan]], [[Quality assurance report]], [[Quality assurance evaluation report]], [[Customer satisfaction inputs]]
outputs:: [[Quality management plan]], [[Quality management guidelines]], [[QM corrective actions]], [[Quality management report]], [[Quality management evaluation report]], [[Quality management record]]
activities:: [[Plan quality management]], [[Assess quality management]], [[Perform quality management corrective action and preventive action]]
At the end of the flow, the user has the enriched Business function node and the Terraphim role. The Terraphim role has key Terraphim terms and synonyms to them:
https://system-operator.s3.eu-west-2.amazonaws.com/term_to_id.json. The user needs terms and synonyms to perform role-based search further.
Overall, 30 business function nodes exist in the graph. This use case can cover any of them or any composition of individual business function nodes but no more than five nodes. The graph also contains hundreds of nodes with bibliographical sources, like this:
tags:: [[Chief Executive Officer]], [[Implementation Strategy]], [[Product Data]], [[Product Development]], [[Total Quality Management]]
date:: 2016
publisher:: Springer
title:: @Product lifecycle management
book-title:: Product Lifecycle Management (Volume 2)
pages:: 1–35
item-type:: [[bookSection]]
original-title:: Product lifecycle management
authors:: [[John Stark]]
library-catalog:: Google Scholar
links:: [Local library](zotero://select/library/items/XL8M2VLA), [Web library](https://www.zotero.org/users/6520516/items/XL8M2VLA)
All bibliographical nodes start with @. It also can contain the field abstract like this:
- [[Abstract]]
- Causal decision theory adopts principles of rational choice that attend to an act’s consequences. It maintains that an account of rational choice must use causality to identify the considerations that make a choice rational., Given a set of options constituting a decision problem, decision theory recommends an option that maximizes utility, that is, an option whose utility equals or exceeds the utility of every other option. It evaluates an option’s utility by calculating the option's expected utility. It uses probabilities and utilities of an option’s possible outcomes to define its expected utility. The probabilities depend on the option. Causal decision theory takes the dependence to be causal rather than merely evidential., This essay explains causal decision theory, reviews its history, describes current research in causal decision theory, and surveys its philosophical foundations. The literature on causal decision theory is vast, and this essay covers only a portion.
The graph also has 99 nodes with type:: [[Business process]]. Node names of these pages are also used in the search.
The user performs this task in several steps:
1. The user selects the business function (search topic) and creates a prompt to find the relevant bibliographical sources.
Terraphim autocompletes the prompt with activities and outputs and proposes to add the inputs from the business function. Each activity, output, or input is a block in a search prompt and can be deleted with one click. The user can also add any term to the prompt. Search results should include the nodes with any of the terms, but the term here can consist of several words, like [[Plan quality management]]; Terraphim should propose terms autocompletion from inputs, outputs or activities, or business process names. Visual guidance is Bing search:
Suggestions go in the drop-down. The search prompt should start with "Topic:"; it should not be a blank search prompt field. It also should indicate that the user now creates a Terraphim role (the search lens). For Terraphim role modification, it will be another use case.
2. The user views the search results, selects relevant sources for further topic search terms extension with synonyms from bibliographical sources, and creates a blank Terraphim role page.
Terraphim shows a complete search query above and produces the list of bibliography nodes that match this query (the user performs this as no role search). Search is performed over all the content of the bibliography node. It must be an exact match with one or more search terms. The more search terms coincide, the higher the relevance. There should be a button to export search results into CSV or JSON format. Search results should be presented in the table - title, year (date), authors, and highlighted keywords that were found.
For example, for the example above, Terraphim should produce this list:
- https://terraphim.github.io/INCOSE-Systems-Engineering-Handbook/#/page/%40product%20lifecycle%20management
- https://terraphim.github.io/INCOSE-Systems-Engineering-Handbook/#/page/%40conceptualizing%20and%20exploring%20the%20organizational%20effects%20of%20iso%209000%20insights%20from%20the%20%C3%B8resund%20bridge%20project
- https://terraphim.github.io/INCOSE-Systems-Engineering-Handbook/#/page/%40megaproject%20management%20lessons%20on%20risk%20and%20project%20management%20from%20the%20big%20dig
- https://terraphim.github.io/INCOSE-Systems-Engineering-Handbook/#/page/%40reengineering%20the%20corporation%20manifesto%20for%20business%20revolution
The user can "Terraphim it" each source selection. Terraphim proposes to create a new Terraphim role or modify the existing. It proposes to name it (by default, the name is safe as a business function), checks for duplicates and creates a relevant Logseq page. The user adds the Terraphim role template on this page and opens it in the sidebar.
When the user opens the bibliographical source, the proper Logseq page (see 1)-4) above) should open together with the business function page (topical page). In the Logseq PDF annotation plugin, the user can attach and annotate the PDF with the Logseq highlights plugin. As the user annotates the PDF, he adds synonyms and related concepts to the page in the Logseq:
synonyms:: operate the system, operation of system, system maintains key functions, system operationally effective, maintenance actions, breakdown in services, monitor the services, monitor system performance, sustain service, identify analyze operational problems, analyze operational problems, service life extension program, SLEP, manage the migration between systems
relatedconcepts:: [[Disposal]], [[Transition]], [[Maintenance]], [[Validation]], [[Knowledge Management]], [[Change management]], [[Concept of operations (ConOps)]], [[Measurement]]
Once the user opens ht bibliography node, Terraphim adds the line with the topic name in the frontmatter:
relatedconcepts:: [[Operation]]
terraphimrole:: [[System operator]]
Also, the user adds synonyms for activities, input, or outputs:
Prepare for operation
type:: [[Business process]]
terraphimrole:: [[System operator]]
source:: [[@Digital Systems Engineering Process Model Version 1]]
documentation:: See detailed description in the INCOSE Handbook v.4, page 96.
synonyms:: sustain a pool of operators,
Also, the user adds an attribute for terraphimrole:: [[System operator]].
Currently, this feature is for the bibliography, which is only in the graph. Later, we will add external sources (articles from web pages) processing.
All node names and synonyms fields with attribute terraphimrole:: should be processed in the search for this role as described in the 1.
3. Add the relevant SFIA skills and synonyms.
Goes the same way as with bibliography sources, but for the SFIA skills catalog.
sfiaskills:: [[IT infrastructure]], [[Database administration]], [[Application support]], [[Security operations]], [[Certification scheme operation]], [[Storage management]], [[Network support]], [[Service catalogue management]], [[Technology service management]], [[Asset management]], [[Demand management]], [[Measurement SFIA]], [[Sustainability]], [[Continuity management]], [[Information security]], [[Acceptance testing]], [[Organisational capability development]], [[Systems installation and removal]], [[Facilities management]], [[Service level management]], [[Availability management]], [[Capacity management]], [[Incident management]], [[Problem management]], [[Change control]], [[Service acceptance]]
Terraphim looks for the topic name ("quality management") in the skills description, provides the list, opens the Logseq page, adds synonyms, but also generates the Logseq pages for the selected skills:
IT infrastructure
type:: [[skill]]
terraphimrole:: [[System operator]]
source:: [[@The global skills and competency framework for a digital world]]
documentation:: Deploying, configuring and operating IT Infrastructure.
sfiacode:: [[ITOP]]
sfiaskill:: [[IT infrastructure]]
sfiacategory:: [[Delivery and operation]]
sfiasubcategory:: [[Technology management]]
sfiaguidancenotes:: IT infrastructure components include, but are not limited to, physical devices, virtual resources, infrastructure-related software, middleware, network services and data storage. Infrastructure components may be on-premises, outsourced, or provisioned as cloud services. Activities may include — but are not limited to: preparing for new or changed services to meet defined needs of organisational users or providers; maintaining and enhancing the IT infrastructure and infrastructure components, including task automation via tools and coding; managing and applying software updates; building and managing systems and components in virtualised and cloud computing environments; monitoring the performance of systems and services related to their contribution to organisation performance, security and sustainability.
sfialevel1description:: Contributes, under supervision, to routine infrastructure operation. Gains understanding of infrastructure components and services by following the activities of experienced colleagues.
sfialevel2description:: Carries out routine operational procedures, including the execution of specified automation tools/scripts. Amends existing automation tasks under supervision to gain a basic understanding of the scripting language/automation tools. Contributes to maintenance and installation. Monitors and reports on infrastructure performance to enable service delivery. Resolves issues or refers to others for assistance.
sfialevel3description:: Provisions/installs, configures and maintains infrastructure services and components. Monitors, measures and reports on infrastructure load, performance and security events. Identifies operational issues and contributes to their resolution. Carries out agreed operational procedures, including backup/restore, using supplied infrastructure tools and scripts. Carries out agreed system software maintenance tasks. Automates routine system administration tasks to specifications using standard tools and basic scripting.
sfialevel4description:: Provides technical expertise to enable the correct application of operational procedures. Contributes to the planning and implementation of infrastructure maintenance and updates. Implements agreed infrastructure changes and maintenance routines. Uses infrastructure management tools to determine load and performance statistics. Configures tools and/or creates scripts to automate the provisioning, testing and deployment of new and changed infrastructure. Maintains operational procedures and checks that they are executed following agreed standards. Investigates and enables the resolution of operational issues. Provides reports and proposals for improvement, to specialists, users and managers.
sfialevel5description:: Provides technical leadership to optimise the performance of IT infrastructure. Investigates and manages the adoption of tools, techniques and processes (including automation) for the management of systems and services. Oversees the planning, installation, maintenance and acceptance of new and updated infrastructure components and infrastructure-based services. Aligns to service expectations, security requirements and other quality standards. Ensures that operational procedures and documentation are fit for purpose and kept up to date. Ensures that operational issues are identified, recorded, monitored and resolved. Provides appropriate status and other reports to specialists, users and managers.