diff --git a/site/docs/concepts/asset.md b/site/docs/concepts/asset.md
index fdcface5c03..10f3b384cba 100644
--- a/site/docs/concepts/asset.md
+++ b/site/docs/concepts/asset.md
@@ -52,6 +52,6 @@ Egeria's [Asset Maker API](/services/omvs/asset-maker/overview) provide the spec
Egeria's [Open Metadata Repository Services (OMRS)](/services/omrs) provides the ability to store and extract information about assets in a distributed collection of servers called an [open metadata repository cohort](/concepts/cohort-member). The cohort provides both peer-to-peer exchange of metadata via an event bus topic and federated queries between different members of the cohort. Egeria provides a [metadata access store](/concepts/metadata-access-store), a [metadata access point](/concepts/metadata-access-point) and a [repository proxy](/concepts/repository-proxy) server that are all able to join a cohort. The repository proxy supports the integration of third party servers (typically [asset managers](/software-capability/#asset-manager)) into the cohort. The mapping between the third party server's APIs and the open metadata APIs in this case is implemented in a [repository connector](/concepts/repository-connector).
-It is also possible to manage the exchange of asset metadata with other types of third party technologies using the [Integration Connectors](/concepts/integraiton-connector) running in an [integration daemon](/concepts/integration-daemon). Using this pattern is simpler to integrate but involves maintaining a copy of the third party technology's metadata in a [metadata access store](/concepts/metadata-access-store) that can then join one or more open metadata repository cohorts to share this metadata more broadly. The mapping between the third party technology's APIs and the open metadata APIs in this case is implemented in an [integration connector](/connectors/integration-connector).
+It is also possible to manage the exchange of asset metadata with other types of third party technologies using the [Integration Connectors](/concepts/integration-connector) running in an [integration daemon](/concepts/integration-daemon). Using this pattern is simpler to integrate but involves maintaining a copy of the third party technology's metadata in a [metadata access store](/concepts/metadata-access-store) that can then join one or more open metadata repository cohorts to share this metadata more broadly. The mapping between the third party technology's APIs and the open metadata APIs in this case is implemented in an [integration connector](/connectors/integration-connector).
--8<-- "snippets/abbr.md"
diff --git a/site/docs/concepts/audit-log-record-structure.svg b/site/docs/concepts/audit-log-record-structure.svg
index 922bc45ab7d..0d1b5a1d4d8 100644
--- a/site/docs/concepts/audit-log-record-structure.svg
+++ b/site/docs/concepts/audit-log-record-structure.svg
@@ -1,4 +1,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/site/docs/concepts/governance-definition.md b/site/docs/concepts/governance-definition.md
index de297e9dfa3..ef61d7fa835 100644
--- a/site/docs/concepts/governance-definition.md
+++ b/site/docs/concepts/governance-definition.md
@@ -4,11 +4,40 @@
# Governance Definition
+Governance definitions are used to record precise requirements, decisions, intents around governance to help people understand what is being asked of them, why, and how their activity will be measured.
+
+They are hard to define and are often revised as a [governance domain](/concepts/governance-domain) matures. However, they keep the investment and metrics targeted, making it easier to measure, justify and improve.
+
+There are three levels of governance definitions: drivers, policies and controls.
## Governance Driver
+A [governance driver](/types/4/0405-Governance-Drivers) describes a motivation to act. It may be a regulation, threat, or an aspect of the business strategy (called a business imperative) that requires a change in the organization.
+
## Governance Policy
+[Governance policies](/types/4/0415-Governance-Responses) describe what is required of the organization. Typically they describe the desired future state (or at least a desirable intermediate state :). There are three main types of policies:
+
+* Principles define the overall values and guidelines for the organization. These help people decide how to act in a situation where there are no rules laid down.
+* Obligations define specific actions or processing that must be accommodated.
+* Approaches define new initiatives, best practices and ways of working that will be adopted.
+
+They are said to be the "responses to the challenges proposed by the governance drivers" and so they are linked to their relevant governance drivers using the [GovernanceResponse](/types/4/0415-Governance-Responses) relationship.
+
## Governance Control
+Governance is enabled through People, Process and Technology. The governance controls describe actions and activities that support achieving the governance policies that support the drivers. Traditionally governance controls are divided into technical controls (implemented IT function) and organizational controls (training, responsibility, buddy-checking etc). In Egeria we do not formally distinguish between technical and organization controls in the type system since the dividing line between the things that humans do and those that are automated is changing all the time.
+
+[Governance controls](/types/4/0425-Governance-Controls) are linked to their relevant governance policies using the [GovernanceMechanism](/types/4/0425-Governance-Controls) relationship. They include [Governance Actions](/concepts/governance-action) and [Governance Zones](/concepts/governance-zone).
+
+???+ info "Further information"
+
+ Definind governance definitions appear in the following Coco Pharmaceuticals scenarios:
+
+ * [Creating a data governance program](/practices/coco-pharmaceuticals/scenarios/creating-data-governance-program/overview)
+ * [Creating a sustainability initiative](/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview)
+
+ You can browse the governance definitions using [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Governance Definitions** tile. They are organized by type and can be filtered by **domainIdentifier**. Setting up a new governance definition is through the [Governance Officer API](/services/omvs/governance-officer/overview).
+
+
--8<-- "snippets/abbr.md"
diff --git a/site/docs/concepts/information-supply-chain.md b/site/docs/concepts/information-supply-chain.md
index 61bd5d6d871..e97519b0ba4 100644
--- a/site/docs/concepts/information-supply-chain.md
+++ b/site/docs/concepts/information-supply-chain.md
@@ -1,28 +1,67 @@
----
-hide:
-- toc
----
-
# Information supply chain
-Lineage is typically captured from the running technology at a very fine-level of detail. This detail enables automated governance processes to validate that the data pipelines are running as they should be. However, this level of detail is too much for most business users and regulators to comprehend. Therefore, it is necessary to model the flow of data at a level of detail that is meaningful to these users and correlate the fine-grained detail to this business view.
+[Lineage](/concepts/lineage) is typically captured at a very fine-level of detail. This detail enables automated governance processes to validate that the data pipelines are running as they should be. However, this level of detail is often too much for most business users and regulators to comprehend. It is necessary to model the flow of data at a level of detail that is meaningful to these users and correlate the fine-grained detail to this business view.
+
+An *InformationSupplyChain* serves as a high-level depiction of data and control movement. It generally outlines how a particular kind of data travels through a digital environment. For instance, one information supply chain might track risk data for a regulatory compliance report, while another illustrates the assembly of data required for carbon accounting.
+
+So the information supply chain is an architectural construct that can provide the focus for data governance or compliance activities that must demonstrate data being delivered where it is needed in a timely and efficient manner.
+
+However, the information supply chain is more than a mere diagram. It is associated with the real lineage producing components that are executing the data flow. It provides a target for roll-ups of activity, errors and volumetrics extracted from the underlying lineage data. The traceability back to the actual components and lineage logs supports validation, investigation and auditability of the information supply chain metrics.
+
+## Information Supply Chain Segments
+
+An information supply chain may be broken down into multiple, nested *segments*. Each segment may represent, for example, the portion of the information supply chain that is owned by a particular team, or the data flows that occur at different phases of the work. This allows drill-down and more focused analysis by the owners of each segment.
+
+## Information Supply Chain Examples
+
+The skill in using information supply chains is to get the right level of abstraction to make its description and analysis meaningful to its intended audience. As such they tend to be designed as part of an initiative or project, where the audience is understood.
+
+In the [Coco Pharmaceuticals](/practices/coco-pharmaceuticals) scenarios we see multiple examples of information supply chains:
+
+* In the [Investigating suspicious activity](/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/overview) scenario, Coco Pharmaceuticals use an information supply chain to model the flow of supplier information and orders through their systems to identify where bogus supplier information could be inserted without detection.
+* In the [Sustainability initiative](/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview) scenario, Coco Pharmaceuticals model an information supply chain during the development of their new sustainability data pipeline.
+* In [Receiving patient data from a hospital](/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/overview), we seem various Coco Pharmaceuticals persona using the information supply chains supporting their clinical trials to understand the process of a clinical trial and any issues that need action.
+* In the initial set up of the data governance program, we see Coco Pharmaceuticals [identifying the key information supply chains](/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview) that the program will need to support.
+
+## Working with Information Supply Chains
+
+Information supply chains can be viewed in [Egeria Explorer](/user-interfaces/egeria-explorer/overview) by clicking on the **Information Supply Chains** card. The [Quickstart](/egeria-workspaces/quick-start/overview) environment includes multiple examples of information supply chains, both from Coco Pharmaceuticals and those that are part of the base Egeria implementation.
+
+The [Lineage Explorer](/user-interfaces/lineage-explorer/overview) supports linking from a technical component in a lineage graph to its associated information supply chains in *Egeria Explorer*.
+
+The [Solution Architect API](/services/omvs/solution-architect/overview) is where you can define, query and maintain your information supply chains. This includes the standard OMVS REST API, python interface and Java client libraries for connectors. They are also fully supported by [Dr.Egeria](/user-interfaces/dr-egeria/overview) in the *Solution Architect* family.
+
+## Modelling Information Supply Chains
+
+An information supply chain is represented by an [*InformationSupplyChain*](/types/7/0720-Information-Supply-Chains) entity. This is a type of [collection](/types/0/0021-Collections). So, its nested segments, and any parent information supply chain are organised into a hierarchy using the [*CollectionMembership*](/types/0/0021-Collections) relationship. The handoff of control/data flow between information supply chains is captured using the [*InformationSupplyChainLink*](/types/7/0720-Information-Supply-Chains) relationship. This relationship can also be used to link the business elements (typically [business capability](/concepts/business-capability) or [actor](/concepts/actor)) that initiates or consumes the data/control flow.
+
+### Information Supply Chain Design
+
+The high-level components illustrating the flow of data/control are captured by [Solution Components](/concepts/solution-component). Providing a design is optional, but recommented since it creates a pictorial view of the flow for people that find the detail overwhelming and/or do not have access to the technical assets that are involved.
+
+A solution component may represent an implementation that has multiple information supply chains flowing through it. The linkage between the *InformationSupplyChain* and a relevant solution component uses a [CollectionMembership](/types/0/0021-Collections) relationship. The flows between these solution component in the information supply chain's design are [SolutionLinkingWire](/types/7/0735-Solution-Ports-and-Wires) relationships that have the qualified name of the information supply chain stored in their *iscQualifiedNames* attribute.
-An *InformationSupplyChain* is the highest level of abstraction for lineage. It typically identifies the flow of a particular type of data across a digital landscape. For example, there may be an information supply chain capturing risk data for a regulatory compliance report, and another one showing how the data necessary for carbon accounting is assembled.
+An information supply chain segment is also represented by an *InformationSupplyChain* entity. It is also linked to its parent using the *CollectionMembership* relationship.
-It is an architectural construct that can provide the focus for data governance activities that ensure data is delivered where it is needed in a timely and efficient manner.
+### Lineage Implementation
-The information supply chain is typically broken down into segments represented by *InformationSupplyChainSegment* entities that each define a particular exchange of data. For example, it may be the flow of data through a specific business unit or country. The segments are linked to their information supply chain via the *InformationSupplyChainComposition* relationship. Their relationship to one another, and its logical sources and destinations are captured using *InformationSupplyChainLink* relationships.
+The unique identifiers/names of the information supply chain segments, or information supply chain itself, are encoded in the *iscQualifiedName* attribute of the lineage relationships captured in the lower levels of lineage detail.
-The unique identifiers/names of the information supply chain segments, or information supply chain itself, are encoded in the lineage relationships captured in the lower levels of lineage detail:
+The lineage relationships that support information supply chains include:
-* The architectural view of the flow of data that the information supply chain represents is described using [solution components](/concepts/solution-somponent) that are linked via [ports and wires](/types/7/0735-Solution-Ports-and-Wires). The [*SolutionLinkingWire*](/types/7/0735-Solution-Ports-and-Wires) contains the unique identifiers (GUIDs) of the information supply chain segments that it implements. Typically, each identified segment is for a different information supply chain that happen to share a part of the data flow.
+* The [data passing](/types/7/0750-Data-Passing) relationships: DataFlow, ControlFlow and ProcessCall.
+* The [lineage mapping](/types/7/0770-Lineage-Mapping) relationships: LineageMapping and DataMapping.
+* The [ultimate edges](/types/7/0755-Ultimate-Source-Destination) relationships: UltimateSource and UltimateDesination.
+* The [DataSetContent](/types/2/0210-Data-Stores) relationship.
+* The [DerivedSchemaTypeQueryTarget](/types/5/0512-Derived-Schema-Elements) relationship.
+* The [ImplementedBy](/types/7/0737-Solution-Implementation) relationship.
-* The fine-grained view captured from the implementation and operation of the deployed technology is described using the [data passing](/types/7/0750-Data-Passing) and [lineage mapping](/types/7/0770-Lineage-Mapping) relationships.
-If additional processing is required to move the data between solution components *along the wire*, for example via an ETL process, this is shown by an *ImplementedBy* relationship between the information supply chain segment and the [Process](/types/0/0010-Base-Model) that represents the implementation. Alternatively, the component that provides the data movement can be show explicitly as a solution component in the [solution blueprint](/types/7/0740-Solution-Blueprints).
+???+ info "Further information"
+ * [Lineage Management](/features/lineage-management/overview)
--8<-- "snippets/abbr.md"
diff --git a/site/docs/concepts/integration-daemon.md b/site/docs/concepts/integration-daemon.md
index 5ed7dcf455f..01c22219fc9 100644
--- a/site/docs/concepts/integration-daemon.md
+++ b/site/docs/concepts/integration-daemon.md
@@ -24,7 +24,7 @@ The specific interface that the integration connector needs to implement is defi
The integration connectors that run inside the integration daemon are managed dynamically as open metadata using [integration groups](/concepts/integration-group). Integration connectors are able to modify the integration groups dynamically, and also initiate [governance actions](/concepts/governance-action), create [to dos](/concepts/to-do) and raise [incident reports](/concepts/incident-report).
-Each time the integration connector is called (refreshed) by the integration daemon, it produces an [integration report](/concpets/integraiton-report) listing the metadata elements it has created, updated or deleted. The integration report is stored in the open metadata repository. It is possible to disable this function in the integration connector's configuration.
+Each time the integration connector is called (refreshed) by the integration daemon, it produces an [integration report](/concpets/integration-report) listing the metadata elements it has created, updated or deleted. The integration report is stored in the open metadata repository. It is possible to disable this function in the integration connector's configuration.
!!! info "Further information"
diff --git a/site/docs/concepts/lineage.md b/site/docs/concepts/lineage.md
index 00b587e8852..7b179b94f3a 100644
--- a/site/docs/concepts/lineage.md
+++ b/site/docs/concepts/lineage.md
@@ -11,7 +11,8 @@ Lineage shows how data and control flows from its origins to its various destina
* whether the operational processes that implement the data flows are executing correctly (known as *governance by expectation*).
-[Lineage Management](/features/lineage-management/overview) describes how lineage is collected, managed and used in Egeria.
+[Lineage Management](/features/lineage-management/overview) describes how lineage is collected, managed and used in Egeria. [Information Supply Chains](/concepts/information-supply-chain) are used to create business-friendly views of lineage.
+
???+ info "Further information"
@@ -22,7 +23,7 @@ Lineage shows how data and control flows from its origins to its various destina
* [Model 0750](/types/7/0750-Data-Passing) for the DataFlow, ProcessCall and ControlFlow relationships.
* [Model 0755](/types/7/0755-Ultimate-Source-Destination) for the UltimateSource and UltimateDestination relationships.
* [Model 0760](/types/7/0760-Business-Lineage) for the BusinessLineage classification.
- * [Model 0770](/types/7/0770-Lineage-Mapping) for the LineageMapping and DataMapping relaitonships.
+ * [Model 0770](/types/7/0770-Lineage-Mapping) for the LineageMapping and DataMapping relationships.
Also see how to set up an [information supply chain](/concepts/information-supply-chain).
diff --git a/site/docs/egeria-workspaces/quick-start/overview.md b/site/docs/egeria-workspaces/quick-start/overview.md
index 903dac9c96c..4a0ece3a464 100644
--- a/site/docs/egeria-workspaces/quick-start/overview.md
+++ b/site/docs/egeria-workspaces/quick-start/overview.md
@@ -7,6 +7,8 @@ The **quickstart** environment is a pre-configured environment based around the
learning and experimentation. It is a good starting point for those who are new to Egeria and want to
get a feel for the platform without having to configure everything from scratch.
+The instructions below will guide you through the process of setting up the environment on you own computer. There is also a public version of the environment that you can use to explore Egeria, called the [Egeria Quickstart Demo Sandbox](/egeria-workspaces/demo-environment/overview).
+
## Up and running with Quickstart
---8<-- "snippets/tasks/task-getting-workspaces.md"
@@ -36,17 +38,28 @@ get a feel for the platform without having to configure everything from scratch.
The script will download all the software needed by Egeria and start it up. Once it has completed, you are ready to go ...
-??? tip "5. Start exploring the open metadata ecosystem with **Egeria Explorer**"
-
-
-
-## Begin with the Explorer
+??? tip "5. Select a persona"
+ Selecting a persona logs you into the quickstart environment with the credentials for that persona. This effects the view of the metadata, and access priviliges you have when exploring the system. No-one can see everything. So pick a persona closest to your interest. For example, if you are interested in metadata about systems, pick **Gary Geeke**, if you like to explore their data governance program, pick **Jules Keeper** and so on.
+ The persona supported by the Quickstart environment are:
+ * [Erin Overview](/practices/coco-pharmaceuticals/personas/erin-overview) - Erin is an information architect involved in the data governance program and the data aspects of their [business transformation](/practices/coco-pharmaceuticals).
+ * [Gary Geeke](/practices/coco-pharmaceuticals/personas/gary-geeke) - Gary is their infrastructure lead. He is building the inventory of their systems and a governance program on top.
+ * [Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) - Jules is the CDO, responsible for the data governance program.
+ * [Peter Profile](/practices/coco-pharmaceuticals/personas/peter-profile) - Peter is a Data Engineer working on digital products and the supply chains used for clinical trials.
+ * [Callie Quartile](/practices/coco-pharmaceuticals/personas/callie-quartile) - Callie is a data scientist working on clinical trials.
+ * [Ivor Padlock](/practices/coco-pharmaceuticals/personas/ivor-padlock) - Ivor is the head of security and is setting up their security governance.
+ * [Faith Broker](/practices/coco-pharmaceuticals/personas/faith-broker) - Faith is the head of HR and CPO and so is interested in the protection of personal data.
+ * [Polly Tasker](/practices/coco-pharmaceuticals/personas/polly-tasker) - Polly is a senior IT Project Manager and is responsible for the IT governance program.
+ * [Tom Tally](/practices/coco-pharmaceuticals/personas/tom-tally) - Tom leads the sustainability program.
+ * [Lemmie Stage](/practices/coco-pharmaceuticals/personas/lemmie-stage) - Lemmie is a DevOps specialist looking to automae the capture of the IT landscape.
+ * [Stew Faster](/practices/coco-pharmaceuticals/personas/stew-faster) - Stew is head of manufacturing. He is leading the digitization of the manufacturing plants.
+
+??? tip "6. Start exploring the open metadata ecosystem"
---8<-- "snippets/work-in-progress.md"
+ You are ready to go. There are no set paths to follow, however, each of the [scenarios](/practices/coco-pharmaceuticals/scenarios) includes suggestions on how to explore Egeria in the context of that scenario.
## Inside the Quickstart environment
diff --git a/site/docs/features/lineage-management/overview.md b/site/docs/features/lineage-management/overview.md
index b89ffb8d47b..66a1dfaf221 100644
--- a/site/docs/features/lineage-management/overview.md
+++ b/site/docs/features/lineage-management/overview.md
@@ -262,7 +262,7 @@ The numbers on the diagram refer to the notes below.
2. A third party technology is using the proxy backend to publish Open Lineage event to a Kafka topic.
-3. The [Open Lineage Event Receiver](/connectors/integration/open-lineage-event-receiver-integration-connector) integration connector is receiving Open Lineage events from the Kafka topic. It passes them to the integraiton daemon's context manager via its own context.
+3. The [Open Lineage Event Receiver](/connectors/integration/open-lineage-event-receiver-integration-connector) integration connector is receiving Open Lineage events from the Kafka topic. It passes them to the integration daemon's context manager via its own context.
4. The [Governance Action Open Lineage](/connectors/integration/governance-action-open-lineage-integration-connector) integration connector has registered a listener to receive events about the [engine actions](/concepts/engine-action) that are being processed in the open metadata ecosystem.
diff --git a/site/docs/guides/planning/governance-program/sustainability-samples.drawio b/site/docs/guides/planning/governance-program/sustainability-samples.drawio
index b2e128c3e68..0f701f0557e 100644
--- a/site/docs/guides/planning/governance-program/sustainability-samples.drawio
+++ b/site/docs/guides/planning/governance-program/sustainability-samples.drawio
@@ -1,4 +1,4 @@
-
+
@@ -208,35 +208,35 @@
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
@@ -244,120 +244,120 @@
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
+
@@ -366,7 +366,7 @@
-
+
@@ -379,92 +379,92 @@
-
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
@@ -472,7 +472,7 @@
-
+
@@ -480,45 +480,45 @@
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
@@ -526,82 +526,321 @@
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -1242,112 +1481,118 @@
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
+
+
+
+
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
@@ -1355,138 +1600,167 @@
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
-
-
+
+
+
+
-
-
+
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
+
+
-
-
+
+
-
-
+
+
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
+
+
-
-
+
+
+
+
+
@@ -1774,301 +2048,301 @@
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
diff --git a/site/docs/practices/coco-pharmaceuticals/personas/index.md b/site/docs/practices/coco-pharmaceuticals/personas/index.md
index c126a1fbab7..ebb5b90c0ab 100644
--- a/site/docs/practices/coco-pharmaceuticals/personas/index.md
+++ b/site/docs/practices/coco-pharmaceuticals/personas/index.md
@@ -5,14 +5,29 @@
The personas from [Coco Pharmaceuticals](/practices/coco-pharmaceuticals) are fictitious, although they are blended from the experiences of real people working with data today. They are used to illustrate the types of people that work with data in an organization and how they use Egeria to support their work.
+## Sustainability team
+
+These personas are responsible for leading [sustainability improvements](/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview) within the company's operations.
+
+* [Tom Tally](/practices/coco-pharmaceuticals/personas/tom-tally) - Accounts Manager
+* [Erin Overview](/practices/coco-pharmaceuticals/personas/erin-overview) - Information Architect
+* [Stew Faster](/practices/coco-pharmaceuticals/personas/stew-faster) - Manufacturing General Manager
+* [Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) - Chief Data Officer
+* [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint) - Chief Finance Officer
+
+
+
## Security team
-These personas are responsible for defining the security strategy for Coco Pharmaceuticals and ensuring compliance.
+These personas are responsible for defining the [security strategy](/practices/coco-pharmaceuticals/scenarios/) for Coco Pharmaceuticals and ensuring compliance.
* [Ivor Padlock](/practices/coco-pharmaceuticals/personas/ivor-padlock) - Security Officer
* [Gary Geeke](/practices/coco-pharmaceuticals/personas/gary-geeke) - IT Infrastructure Lead
* [Lemmie Stage](/practices/coco-pharmaceuticals/personas/lemmie-stage) - DevOps Specialist
-* [Polly Tasker](/practices/coco-pharmaceuticals/personas/polly-tasker) - IT Project Leader
+* [Simon Burr](/practices/coco-pharmaceuticals/personas/simon-burr) - Cyber Security Specialist
+* [Sidney Seeker](/practices/coco-pharmaceuticals/personas/sidney-seeker) - Fraud Investigator
+
+
## AI pilot team
@@ -24,7 +39,9 @@ It is very experimental at this time but has a lot of interest at board level.
* [Bob Nitter](/practices/coco-pharmaceuticals/personas/bob-nitter) - Integration Architect/Developer
* [Harry Hopeful](/practices/coco-pharmaceuticals/personas/harry-hopeful) - Sales
* [Tessa Tube](/practices/coco-pharmaceuticals/personas/tessa-tube) - Lead Researcher
+* [Polly Tasker](/practices/coco-pharmaceuticals/personas/polly-tasker) - IT Project Leader
+
## Fraud investigation team
@@ -36,13 +53,7 @@ These personas are investigating a [potential incidence of fraud](/practices/coc
* [Harry Hopeful](/practices/coco-pharmaceuticals/personas/harry-hopeful) - Sales
* [Sidney Seeker](/practices/coco-pharmaceuticals/personas/sidney-seeker) - Fraud Investigator
-## Sustainability team
-
-These personas are responsible for leading sustainability improvements within the company's operations.
-
-* [Tom Tally](/practices/coco-pharmaceuticals/personas/tom-tally) - Accounts Manager
-* [Stew Faster](/practices/coco-pharmaceuticals/personas/stew-faster) - Manufacturing General Manager
-* [Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) - Chief Data Officer
+
## Corporate governance
@@ -54,21 +65,6 @@ These personas are the executives whose full-time job is the governance and prot
* [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint) - Chief Finance Officer
-## IT operations team
-
-These personas are responsible for the planning and operation of the IT systems used by the company. They are not all of the people involved, but they each have a potential impact on the way the company's data is managed.
-
-* [Erin Overview](/practices/coco-pharmaceuticals/personas/erin-overview) - Information Architect
-* [Peter Profile](/practices/coco-pharmaceuticals/personas/peter-profile) - Information Analyst
-* [Gary Geeke](/practices/coco-pharmaceuticals/personas/gary-geeke) - IT Infrastructure Lead
-
-## Digital product managers
-
-Peter is responsible for the digital products that are managed by Egeria.
-
-* [Peter Profile](/practices/coco-pharmaceuticals/personas/peter-profile) - Information Analyst
-
-
## IT project team
This is the IT Project Team enhancing the IT Systems to create a supplier/customer hub, to provide end-to-end monitoring of the manufacturing process, and to provide support for a data lake for the clinical research teams.
@@ -87,7 +83,10 @@ Bob Nitter supports the multitude of application systems that the company runs.
Coco Pharmaceuticals has its own manufacturing plants. Stew Faster is the general manager of the plants and is involved in the digitization program for manufacturing and distribution of the products.
* [Stew Faster](/practices/coco-pharmaceuticals/personas/stew-faster) - Manufacturing General Manager
+* [Florence Paynter](/practices/coco-pharmaceuticals/personas/florence-paynter) - Cancer Patient
+* [George Pie](/practices/coco-pharmaceuticals/personas/george-pie) - Cancer Patient
+
## Clinical trials team
@@ -98,18 +97,8 @@ This is the first use of the company's data lake.
* [Callie Quartile](/practices/coco-pharmaceuticals/personas/callie-quartile) - Data Scientist
* [Tessa Tube](/practices/coco-pharmaceuticals/personas/tessa-tube) - Lead Researcher
* [Tanya Tidie](/practices/coco-pharmaceuticals/personas/tanya-tidie) - Clinical Records Clerk
-* [Angela Cummings](/practices/coco-pharmaceuticals/personas/angela-cummings) - Nurse
-* [Grant Able](/practices/coco-pharmaceuticals/personas/grant-able) - Consultant
-* [Julie Stitched](/practices/coco-pharmaceuticals/personas/julie-stitched) - Surgeon
-* [Robbie Records](/practices/coco-pharmaceuticals/personas/robbie-records) - Patient Data Manager
-
-
-## Cancer Patients
-
-These personas represent external data subjects for Coco Pharmaceuticals.
+* [Peter Profile](/practices/coco-pharmaceuticals/personas/peter-profile) - Information Analyst
-* [Florence Paynter](/practices/coco-pharmaceuticals/personas/florence-paynter) - Cancer Patient
-* [George Pie](/practices/coco-pharmaceuticals/personas/george-pie) - Cancer Patient
## External consultants
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/ai-pilot-team.png b/site/docs/practices/coco-pharmaceuticals/scenarios/ai-pilot-team.png
new file mode 100644
index 00000000000..dcfecabe024
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/ai-pilot-team.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/assuring-it-systems-security/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/assuring-it-systems-security/overview.md
index 14ecf6c2e1d..c54271451db 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/assuring-it-systems-security/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/assuring-it-systems-security/overview.md
@@ -3,6 +3,8 @@
# Assuring IT System Security
+This scenario illustrates how Egeria can be used to support the assurance of IT system security.
+

diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-si-lemmie-gary-it-security-strategy-meeting.png b/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-sidney-lemmie-gary-it-security-strategy-meeting.png
similarity index 100%
rename from site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-si-lemmie-gary-it-security-strategy-meeting.png
rename to site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-sidney-lemmie-gary-it-security-strategy-meeting.png
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-welcoming-si-to-coco.png b/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-welcoming-si-to-coco.png
new file mode 100644
index 00000000000..5649ba4f1cb
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/ivor-welcoming-si-to-coco.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/overview.md
index cf86bd6249c..576d9a66d28 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/building-a-data-security-strategy/overview.md
@@ -3,6 +3,22 @@
# Building a Data Security Strategy
-
+[Ivor Padlock](/coco-pharmaceuticals/personas/ivor-padlock) invites [Sidney Seeker](/coco-pharmaceuticals/personas/sidney-seeker), [Gary Geeke](/coco-pharmaceuticals/personas/gary-geeke) and [Lemmie Stage](/coco-pharmaceuticals/personas/lemmie-stage) to a meeting to discuss the data security strategy. Lemmie and Gary describe their processes to secure the IT systems. They use certificates, a firewall and SSL on the internal network, along with strong passwords on administrative user accounts.
+
+Sidney asks if the security of the systems has ever been tested, but an expert - or using advanced tools? The answer was "no".
+
+Sidney explained that cyber attackers are using sophisticated tools that include AI to penetrate organizations and steal information. They have a lot of computing resources to pound an organization's systems, looking for vulnerabilities. They may also use social engineering (such as phishing) to get information from employees.
+Since cyber threats are not static and evolve rapidly it is necessary to perform regular audits and assessments to stay one step ahead of the threats by identifying and mitigating potential vulnerabilities before they can be exploited.
+
+
+
+Ivor realizes that this is a serious situation. Coco Pharmaceuticals' future depends on taking care of its intellectual property and reputation. Both are at risk from cyber attacks. It needs to take steps to protect their data and ensure that it is safe and secure. He asks Sidney to help him build a briefing for the board to raise awareness of the situation and request further investment in IT security.
+
+
+## Supporting the Data Security Strategy
+
+A key finding of their analysis was that Ivor needed specialist help to monitor, test and improve the security of the IT systems. As a result, Coco Pharmaceuticals hire [Simon Burr](/coco-pharmaceuticals/personas/simon-burr) (known as Si to his friends) to lead their Cyber Security practice.
+
+
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/business-transformation.drawio b/site/docs/practices/coco-pharmaceuticals/scenarios/business-transformation.drawio
index ab9519a9b94..9400fc26843 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/business-transformation.drawio
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/business-transformation.drawio
@@ -1,4 +1,4 @@
-
+
@@ -58,118 +58,118 @@
-
+
-
-
+
+
-
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
+
-
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
+
-
+
-
-
+
+
-
-
+
+
-
+
-
+
-
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
-
-
+
+
@@ -310,4 +310,96 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/cataloguing-infrastructure/gary-jules-discussing-what-to-catalog.png b/site/docs/practices/coco-pharmaceuticals/scenarios/cataloguing-infrastructure/gary-jules-discussing-what-to-catalog.png
new file mode 100644
index 00000000000..17f5b643b65
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/cataloguing-infrastructure/gary-jules-discussing-what-to-catalog.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview.md
index 7c22f40b357..ce0f0794f80 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview.md
@@ -22,7 +22,7 @@ In addition to training, to make permanent changes to the culture, leaders need
When the [governance leaders](/practices/coco-pharmaceuticals/scenarios/building-the-governance-team/overview) began to discuss staff training, they quickly agreed that it should be an interactive experience, with everyone given the opportunity to consider the issues, identify key asset, threats and positive actions as well as build a personal plan of action.
-As such, each training course they identified included a basic set of training informaiton followed by a set of questions that they were to work through, some as a team and others individually. The aim was to make it personal and real to all who participated. It also spread the start-up costs of creating the inventory of the companies assets and their role in the business.
+As such, each training course they identified included a basic set of training information followed by a set of questions that they were to work through, some as a team and others individually. The aim was to make it personal and real to all who participated. It also spread the start-up costs of creating the inventory of the companies assets and their role in the business.
For example, each team discussed cyber-security they were taught about data breaches, phishing attacks, and ransomware. Then they were aske to identify shared passwords, systems that might be vulnerable, and other ways they could safe-guard their personal privacy and Coco Pharmaceuticals, operations and intellectual property.
@@ -41,6 +41,6 @@ In particular, the teams were asked to separate out the valuable data assets fro
The results from the training sessions were collated into Egeria, mostly through [Dr Egeria](/user-interfaces/dr-egeria/overview) markwoen document processing with oversight from the governance leaders.
-
+
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview.md
index 50de66b6fd3..f3315a0ce24 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview.md
@@ -1,8 +1,19 @@
-# Defining key information supply chains
+# Identifying the key information supply chains
+[Information Supply Chains](/concepts/information-supply-chain) represent the flow of key information from its sources to its destinations. The detail from lineage data captured from the relevant IT operations is associated with the information supply chain so it can be used for analysis and metrics collection, monitoring and business decision-making. An optional high level design of the flow associated with the information supply chain provides a business-friendly view of the data/control flow.
+
+## Background
+
+[Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) is keen that Coco Pharmaceuticals' [data strategy](/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview) is focused on the key data processing changes that that will drive Coco Pharmaceuticals' transformation to personalized medicine. [Erin Overview's](/practices/coco-pharmaceuticals/personas/erin-overview) work identifying the [key subject areas](/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview) highlighted the lack of data exchange between the research, sales, manufacturing and finance. This will need to change if they are to reduce their cycle times and batch sizes down to single patient requests.
+
+At this point, they have a [high-level conceptual architecture](/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview) for the systems integration and an initial list of [existing authoritative sources](/practices/coco-pharmaceuticals/scenarios/identifying-authoritative-sources/overview). The challenge now is to define the critical data flows that will be enabled through this new architecture and how they should be designed, rolled out and monitored to ensure they are working as expected.
+
+*More to come ...*
+
+--8<-- "snippets/work-in-progress.md"
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/data-driven-systems-architecture.png b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/data-driven-systems-architecture.png
deleted file mode 100644
index 1573fbb0e3f..00000000000
Binary files a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/data-driven-systems-architecture.png and /dev/null differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.png b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.png
new file mode 100644
index 00000000000..5d22a2f5f31
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.svg
new file mode 100644
index 00000000000..8490fd202be
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/data-driven-systems-architecture.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview.md
similarity index 100%
rename from site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/overview.md
rename to site/docs/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview.md
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview.md
index fc254375f49..ba67f0daf85 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/defining-the-data-strategy/overview.md
@@ -93,7 +93,7 @@ He begins to work on the next level of detail with [Erin Overview](/practices/co
* [Planning for creating common definitions materials](/practices/coco-pharmaceuticals/scenarios/planning-for-common-data-definitions/overview)
* [Identifying authoritative sources](/practices/coco-pharmaceuticals/scenarios/identifying-authoritative-sources/overview)
-* [Defining the new data-driven systems architecture overview](/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/overview)
+* [Defining the new data-driven systems architecture overview](/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview)
* [Defining the key information supply chains](/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview)
* [Defining what is meant by continuous analytics](/practices/coco-pharmaceuticals/scenarios/defining-continuous-analytics/overview)
* [Defining how employees can be data-enabled](/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview)
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/fraud-investigation-team.png b/site/docs/practices/coco-pharmaceuticals/scenarios/fraud-investigation-team.png
new file mode 100644
index 00000000000..ab1334c796f
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/fraud-investigation-team.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/index.md b/site/docs/practices/coco-pharmaceuticals/scenarios/index.md
index 920a466be7a..94addb34c45 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/index.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/index.md
@@ -9,7 +9,7 @@ The scenarios follow the [Coco Pharmaceutical personas](/practices/coco-pharmace
- [Planning for common data definitions](/practices/coco-pharmaceuticals/scenarios/planning-for-common-data-definitions/overview)
- [Identifying authoritative sources](/practices/coco-pharmaceuticals/scenarios/identifying-authoritative-sources/overview)
- - [Defining the new data-driven systems architecture overview](/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/overview)
+ - [Defining the new data-driven systems architecture overview](/practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview)
- [Defining the key information supply chains](/practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview)
- [Defining what is meant by continuous analytics](/practices/coco-pharmaceuticals/scenarios/defining-continuous-analytics/overview)
- [Defining how employees can be data-enabled](/practices/coco-pharmaceuticals/scenarios/defining-data-enabled-employees/overview)
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/reggie-sally-jules-tom-discussing-financial-systems.png b/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/reggie-sally-jules-tom-discussing-financial-systems.png
new file mode 100644
index 00000000000..cb57ddbf97a
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/reggie-sally-jules-tom-discussing-financial-systems.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-and-sally-discussing-the-possilbe-fraud.png b/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-and-sally-discussing-the-possible-fraud.png
similarity index 100%
rename from site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-and-sally-discussing-the-possilbe-fraud.png
rename to site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-and-sally-discussing-the-possible-fraud.png
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-realizing-how-much-work-she-has-taken-on.png b/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-realizing-how-much-work-she-has-taken-on.png
new file mode 100644
index 00000000000..ae0ac84177f
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/tom-realizing-how-much-work-she-has-taken-on.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/manufacturing-team.png b/site/docs/practices/coco-pharmaceuticals/scenarios/manufacturing-team.png
new file mode 100644
index 00000000000..03d9720552e
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/manufacturing-team.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/overview.md
index 3c54eb5ea58..3e64f0a7032 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/overview.md
@@ -6,9 +6,6 @@

-## Shaping a new clinical trial
-
-
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/patient-data-sharing-hub/angela-grant-julie-discussing-treatment.png b/site/docs/practices/coco-pharmaceuticals/scenarios/patient-data-sharing-hub/angela-grant-julie-discussing-treatment.png
new file mode 100644
index 00000000000..36352a2eb4b
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/patient-data-sharing-hub/angela-grant-julie-discussing-treatment.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/capturing-martyns-law.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/capturing-martyns-law.svg
index a0f178aca83..273239ceb12 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/capturing-martyns-law.svg
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/capturing-martyns-law.svg
@@ -1,4 +1,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/martyns-law.drawio b/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/martyns-law.drawio
index f0e206999e9..75768a1b925 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/martyns-law.drawio
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/martyns-law.drawio
@@ -1,4 +1,4 @@
-
+
@@ -820,7 +820,7 @@
-
+
@@ -833,9 +833,6 @@
-
-
-
@@ -845,15 +842,15 @@
-
+
-
+
-
+
@@ -928,6 +925,9 @@
+
+
+
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/overview.md
index a54077effbc..673a5887437 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/overview.md
@@ -5,4 +5,9 @@

+
+## Shaping a new clinical trial
+
+
+
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/tessa-callie-tanya-discussing-new-clinical-trial.png b/site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/tessa-callie-tanya-discussing-new-clinical-trial.png
similarity index 100%
rename from site/docs/practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/tessa-callie-tanya-discussing-new-clinical-trial.png
rename to site/docs/practices/coco-pharmaceuticals/scenarios/receiving-patient-data-from-a-hospital/tessa-callie-tanya-discussing-new-clinical-trial.png
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/security-team.png b/site/docs/practices/coco-pharmaceuticals/scenarios/security-team.png
new file mode 100644
index 00000000000..381e8083558
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/security-team.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-Enterprise.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-Enterprise.png
new file mode 100644
index 00000000000..d7ec6ca272c
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-Enterprise.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Operation.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Operation.png
new file mode 100644
index 00000000000..81dda47f7c5
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Operation.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Scope.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Scope.png
new file mode 100644
index 00000000000..4a1e091e7d2
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Scope.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Site.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Site.png
new file mode 100644
index 00000000000..9d855f73824
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/Sustainability-Dashboard-by-Site.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-peter-designing-pipelines.jpg b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-peter-designing-pipelines.jpg
new file mode 100644
index 00000000000..945e8e1a470
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-peter-designing-pipelines.jpg differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-polly-peter-callie-top-discussing-collection-of-sustainability-data.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-polly-peter-callie-top-discussing-collection-of-sustainability-data.png
new file mode 100644
index 00000000000..86593787ce0
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/bob-polly-peter-callie-top-discussing-collection-of-sustainability-data.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/callie-tom-discussing-ghg-calculations.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/callie-tom-discussing-ghg-calculations.png
new file mode 100644
index 00000000000..3bf654904c8
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/callie-tom-discussing-ghg-calculations.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/communities.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/communities.png
new file mode 100644
index 00000000000..3e8311f92ea
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/communities.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/delivery-at-hampton-hospital.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/delivery-at-hampton-hospital.png
new file mode 100644
index 00000000000..a9d8209c253
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/delivery-at-hampton-hospital.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/domain-identifier-valid-values.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/domain-identifier-valid-values.png
new file mode 100644
index 00000000000..f362a630953
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/domain-identifier-valid-values.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/erin-gary-stew-tom-mapping-locations.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/erin-gary-stew-tom-mapping-locations.png
new file mode 100644
index 00000000000..ab94fa78627
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/erin-gary-stew-tom-mapping-locations.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/faith-tom-jules-erin-discussing-new-refrigeration-unit-type.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/faith-tom-jules-erin-discussing-new-refrigeration-unit-type.png
new file mode 100644
index 00000000000..6da0b32e10f
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/faith-tom-jules-erin-discussing-new-refrigeration-unit-type.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-approach.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-approach.svg
new file mode 100644
index 00000000000..0643c760e26
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-approach.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-drivers.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-drivers.svg
new file mode 100644
index 00000000000..35d018e46b1
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/governance-drivers.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/lemmie-defining-refrigeration-unit.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/lemmie-defining-refrigeration-unit.png
new file mode 100644
index 00000000000..c225e428939
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/lemmie-defining-refrigeration-unit.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview.md b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview.md
index a750fcf9661..746e10ab0f0 100644
--- a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview.md
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/overview.md
@@ -3,47 +3,334 @@
# New Sustainability Initiative
-Climate change is upon us. Public and private institutions recognize the role that each have in reaching sustainability goals to slow climate change as well as mitigate and adapt to the various risks that climate change is driving.
+Climate change is upon us. Many public and private institutions recognize they have a role to play in reaching global sustainability goals to slow climate change, as well as mitigating and adapting to the various risks that climate change is driving. There are also emerging [regulatory reporting requirements for sustainability](https://finance.ec.europa.eu/financial-markets/company-reporting-and-auditing/company-reporting/corporate-sustainability-reporting_en) to add a "stick" to the mix.
-The Board of Directors for Coco pharmaceuticals has come to recognize the need for a formal sustainability program. This is a major cross-cutting initiative with many complexities that will affect many parts of the business, provide opportunities for innovation, differentiation and cost-savings over time - as well as meet commitments to shareholders, partners and regulators.
+Making a systemic change in the way an organization does business is a major cross-cutting initiative with many complexities. It is likely to affect all parts of the business and require upfront investment. On the other hand, if done well, it will provide opportunities for innovation, differentiation and cost-savings over time - as well as meet commitments to shareholders, partners and regulators.
-These initiatives require careful consideration, planning and collaboration - often over many years. It is important to choose a good starting point that is tangible, understandable and incrementally achievable. The board is aware of emerging regulatory reporting requirements for sustainability and decides that it would be beneficial to be proactive and start with this as a focus area.
+**Choosing a good starting point that is tangible, understandable and incrementally achievable is important.**
-The foundation for much of sustainability reporting is accounting for the carbon emissions (and their equivalence) by following protocols such as the GHG Protocols. This can help all stakeholders establish:
+The foundation for sustainability reporting is accounting for carbon emissions (and their equivalence) by following protocols such as the [Greenhouse Gas (GHG) Protocol](https://ghgprotocol.org/). This can help all stakeholders establish:
-* Coco's direct and indirect carbon emissions baseline
-* goals and targets to reduce these emissions
-* campaigns and projects to achieve these goals
+* The organization's direct and indirect carbon emissions baseline
+* Goals and targets to reduce these emissions
+* Campaigns and projects to achieve these goals
* Progress monitoring and reporting
* Auditable results to publish to stakeholders - governmental, financial and market.
-With this mission in mind, the Coco board decides to establish a sustainability program.
+With this mission in mind, the Coco Pharmaceuticals' board decides to establish a sustainability program.
## Leadership
-The board considered how to organize and execute the program. Through these discussions they quickly realized that this program was not only important in itself, but would also provide an opportunity for some promising, more junior staff to learn how to collaborate and lead across the business.
+The board considered how to organize and execute the program. Through these discussions they realize that this program was not only important in itself, but would provide an opportunity for some promising, more junior staff to learn how to collaborate and lead across the business.
-There were many promising candidates put forward, but at the end of the discussions, all agreed that this would be an excellent experience for Tom Tally. As Tom already had dealings with both sales and suppliers that would help her to understand and interact with external parties to gather and share key information. There were of course concerns that she was too inexperienced - and so it was quickly agreed that Tom should be paired with experienced leaders throughout the company. As a result, the following team was announced:
+There were a few candidates put forward, but at the end of the discussions, all agreed that this would be an excellent experience for [Tom Tally](/practices/coco-pharmaceuticals/personas/tom-tally). As Tom already had dealings with both [sales and suppliers](/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/overview) this would expand her experience across the whole company.
+
+There were concerns, of course, that she was inexperienced - and so it was agreed that Tom should be paired with two experienced leaders to support her. As a result, the following team was announced:
- [Tom Tally](/practices/coco-pharmaceuticals/personas/tom-tally) - team leader, Accounts Manager
- [Stew Faster](/practices/coco-pharmaceuticals/personas/stew-faster) - technical lead, Manufacturing Manager
- [Erin Overview](/practices/coco-pharmaceuticals/personas/erin-overview) - information lead, Information Architect
-To provide overall guidance and oversight it was agreed that a partnership between [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint) and [Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) would provide executive sponsorship.
+To provide overall guidance and oversight, it was agreed that a partnership between [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint) and [Jules Keeper](/practices/coco-pharmaceuticals/personas/jules-keeper) would provide executive sponsorship.
+
+> The sustainability team from left to right: Erin, Tom, Reggie, Stew and Jules
## First steps
-Reggie Mint and Jules Keeper call a meeting with the newly formed team of Tom, Stew and Erin. They explain the situation as related to them from the board meeting and lay out the business imperatives that they must all achieve. Reggie and Jules ask the team to put together an initial proposal for how to proceed - and to come back in a week to discuss. Tom, Stew and Erin nervously agree and depart to discuss over a working lunch.
+Reggie Mint and Jules Keeper call a meeting with the newly formed team of Tom, Stew and Erin. They explain the situation as related to them from the board meeting and lay out what the board wants them to achieve.
+

-## Establishing the new domain
+Reggie and Jules ask the team to put together an initial proposal for how to proceed - and to come back in a week to discuss. Tom, Stew and Erin nervously agree and depart to discuss over a working lunch.
+
+## Scoping the Sustainability Program
+
+Over lunch, they discuss next steps. Tom offered to review the [Greenhouse Gas Protocol](https://ghgprotocol.org/) requirements to understand what types of data collection and reporting are required.
+
+Stew suggests they have conference calls with a range of managers across the business to get their view on where the sustainability program should focus.
-After some lively discussion, they agree that sustainability is another governance domain in their governance program. This will allow them to make use of many of the definitions and organizational structures already in place.
+Erin offered to review how the data governance and security teams managed their cross-organizational responsibilities.
+
+
+
+When they next meet, Erin shows them the list of governance domains operating in Coco Pharmaceuticals - including the new value added for their sustainability work.
???+ info "Governance Domain definition"
- The definition of this new domain can be seen in [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Valid Values** tile, look for the **Governance Domain** valid value set. Setting up a new domain is through the [Valid Metadata API](/services/omvs/valid-metadata/overview)
+ The definition of the governance domains can be seen in [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Valid Values** tile, look for the **domainIdentifier** valid value set. Setting up a new domain is through the [Valid Metadata API](/services/omvs/valid-metadata/overview).
+
+ 
+
+She also showed them the governance definitions that Jules and Reggie had created as a result of the board meeting.
+
+There was a *business imperative* to protect Coco Pharmaceuticals from global instability, and linked to that was a *governance principle* to operate Coco Pharmaceuticals in an increasingly sustainable way.
+
+
+
+Erin said they need to define how they want to structure the sustainability program. She also showed Tom the types of approaches both the [Data Governance](/practices/coco-pharmaceuticals/scenarios/defining-the-data-governance-program/overview) and [Security](/practices/coco-pharmaceuticals/scenarios/defining-the-data-security-strategy/overview) teams have created.
+
+???+ info "Governance Definitions"
+ Governance drivers and principles are types of governance definitions. Governance definitions are used to record precise requirements, decisions, intents around governance to help people understand what is being asked of them, why, and how their activity will be measured.
+
+ You can browse the governance definitions using [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Governance Definitions** tile. They are organized by type and can be filtered by **domainIdentifier**. Setting up a new governance definition is through the [Governance Officer API](/services/omvs/governance-officer/overview).
+
+Tom offered to come up with an initial plan, and they would meet the next day to discuss it.
+
+
+## Scoping the Sustainability Governance Program
+
+Tom realised that the sustainability topic was huge, but if she was going to have an impact, she must keep it very focused. She also needed to recruit people from across the organization since it needed a cultural change to keep the initiative vital over the longer term. She liked the idea of a cross-company community to bring people together. She also thought the sustainability reporting regulations would provide a concrete framework for gathering relevant data.
+
+
+
+The next day, Erin and Stew help Tom structure the approach and create the governance definitions to show to Reggie and Jules.
+
+There are three main parts to it:
+
+* Build a sustainability community to education and inspire people across the company on their role in the company's sustainability imperative.
+* Using existing data collected by the business, create a sustainability dashboard that can be used to show their current position. Over time, it would allow them to track the progress of the initiative.
+* Run an initiative to reduce the use of CFCs in refrigeration units.
+
+
+
+Reggie and Jules agreed with the approach, and the team moved on to the implementation plan.
+
+???+ info "Reviewing the Governance Definitions"
+
+ You can browse the governance definitions using [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Governance Definitions** tile. Select the **Domain 9 - Sustainability** option from the domain drop-down to filter the definitions just for sustainability.Then select **Protecting Coco Pharmaceuticals from global instability**. You can **Load Context Diagram** to see the governance approaches defined by the team and bleow the diagram are links to navidate to the governance principle of **Operate Coco Pharmaceuticals in an increasingly sustainable way** and then onto the governance appropaches. Alternatively you can select them directly by opening up the left-hand tree view.
+
+ 
+
+## Establishing the broader sustainability team
+
+Tom takes [Faith Broker](/practices/coco-pharmaceuticals/personas/faith-broker) from Human Resources through the idea of the sustainability community.
+
+For the membership, they agree that the community should be open to all employees, including contractors and interns who are interested. However, there would be a core membership based on specific roles. The people appointed to these roles are required to participate in the community.
+
+
+
+The roles they agree are:
+
+* Sustainability Leader - this is Tom as the leader of the initiative and community.
+* Site and Facility Owner - for site/facility specific discussions.
+* Sustainability Champion - one per business area in Coco Pharmaceuticals to drive initiatives specific to their the business area.
+* Sustainability Technology Lead - this is the person responsible for the Sustainability reporting information supply chain.
+
+When Tom takes Erin and Stew through the community structure, Erin shows them how a community and their roles are defined.
+
+
+
+???+ info "Reviewing the Communities"
+ You can browse the communities using [egeria-explorer](/user-interfaces/egeria-explorer/overview) under the **Communities** tile.
+
+ 
+
+## Mapping out the company
+
+
+
+
+
+
+
+
+
+
+
+
+## Building the Sustainability Glossary
+
+
+
+## Designing the Sustainability Supply Chain
+
+To build the supply chain we need to first understand the requirements. A good way to start is to work backwards from the results we are trying to produce. In this case, we are producing a sustainability dashboard that documents Scope 1 and Scope 2 emissions across a number of dimensions - so lets start there.
+A quick look at the Dashboard
+
+While we won't always be able to start with a concrete target such as this dashboard, in the case of sustainability reporting all we have to do is to look at the kinds of material different companies produce to get an idea of what Coco Pharmaceuticals will need to construct. With that in mind, we've put together the following prototype sustainability dashboard. This dashboard is for internal stakeholders within Coco Pharmaceuticals - it contains much more information than would typically be published to broader communities.
+
+
+
+
+### What type of data is needed?
+
+
+
+
+
+### Where will the data come from?
+
+
+
+### Where will the data be stored?
+
+### How will the data be processed?
+
+
+
+### How will the data be visualized?
+
+=== "Sustainability Dashboard - Enterprise Level"
+
+ The main page of the dashboard looks like this:
+
+ 
+
+=== "Sustainability Dashboard - by Scope"
+
+ To gain a better understanding of how emissions are being produced and from where we need to be able to drill-in to the data to investigate further. The first step is to break the emissions down by scope:
+
+ 
+
+ This tells us that Scope 2 emissions from electric utilities are the primary contributors. We can also see that this starts to show how the different work locations (sites) contribute to the scope 1 and scope 2 totals.
+
+=== "Sustainability Dashboard - by Site"
+
+ We also want to understand how each of the work locations contributes to the overall enterprise emissions. These graphs shows the emissions for each site - note that the number of sites has increased over the years as the business continues to expand and change.
+
+ 
+
+=== "Sustainability Dashboard - by Operation"
+
+ To understand why some sites produce more emissions than others, it is important to consider what kinds of business operations are taking place. From the graphs we can see that some sites have a combination of offices workers, research and a computer room while manufacturing and distribution happens elsewhere. Manufacturing produces much more scope 1 emissions than research does.
+
+ 
+
+ It is important for us to gain a detailed understanding of how emissions are produced in order for realistic reduction targets to be set and improvement programs designed.
+
+#### Inferred requirements
+
+By understanding the dashboard we can better understand some key requirements for the supply chain that we need to design and implement:
+
+* Collect data and calculate scope 1 and scope 2 emissions
+* Collect information per site and operation
+* Store the information over time to create yearly comparisons
+* Aggregate data across time, site, scope, operations
+* Accommodate change - new sites, changing operations, changing business structure, business expansion
+
+Designing a supply chain
+
+The inferred requirements are the beginning of the supply chain design process. As we continue to work backwards, the issues that we have to address include:
+
+* How often does the dashboard need to be updated?
+* How often do emissions calculations need to be run?
+* How are we going to execute these calculations?
+* Where is the data for these calculations coming from?
+* How do we need to prepare this data for calculations to be performed?
+* Who owns the source data that we need?
+
+Working through these questions leads us to break the supply chain down into three logical stages:
+
+* Collect data from source systems
+* Refine and process this data to calculate emissions
+* Store the results and aggregations for analysis and reporting
+
+These stages are discussed further in Creating the Data Pipeline
+
+### Putting it all together
+
+Peter Profile and Bob Nitter work together on delivering the sustainability information supply chain. Bob focuses on building the data pipelines that fill `coco_sus` and Peter focuses on building the dashboard.
+
+
+
+When the pipelines are running, they can be viewed in the [Lineage Explorer](/user-interfaces/lineage-explorer/overview). Enter `coco`
+[Egeria Explorer](/user-interfaces/egeria-explorer/overview) through the
+
+And this is the resulting dashboard:
+
+=== "Sustainability Dashboard - Enterprise Level"
+
+ 
+
+=== "Sustainability Dashboard - by Scope"
+
+ 
+
+=== "Sustainability Dashboard - by Site"
+
+ 
+
+=== "Sustainability Dashboard - by Operation"
+
+ 
+
+----
+> Version 1 of the sustainability dashboard running in Apache Superset
+
+## Launching the Sustainability Community
+
+With the dashboard in place, Tom is ready to launch the sustainability community. On their first call, they discuss the sustainability challenge, the roles in the community, and hence why then have been invited. There was also discussion of how the community should work, and Tom shared the details of the sustainability dashboard.
+
+
+
+She also had the pleasure of announcing their first initiative - the CFC-Free Initiative.
+
+## The CFC-Free Initiative
+
+In the first phase of the sustainability initiative, Tom is keen to run an initiative that makes a difference to sustainability. [Zach Now](/practices/coco-pharmaceuticals/personas/zach-now), founder and leader of the New York Lab suggested they run a campaign to reduce the use of chlorofluorocarbons (CFCs) in refrigeration units throughout the company. These are principally in the labs and manufacturing units.
+
+
+> Tom and Zach discussing the CFC-Free Initiative
+
+The initiative will involve identifying and replacing CFC-containing units with more environmentally friendly alternatives.
+
+### Capturing details of the CFCs in refrigeration units
+
+Tom discovers that although the refrigeration units were catalogued in the various asset management systems across the company, details of the coolant installed was not captured. Her plan is to use Egeria as the company asset register for equipment that is relevant to sustainability so that she can use governance controls such as [certification types](/types/4/0482-Certifications) and [exception types](/types/4/0455-Exception-Management) to keep track of progress.
+
+#### Is this the right solution?
+
+Tom looks at the existing [open metadata types](/types) and cannot find a good place to store details of their refrigeration units. She proposes to add a new RefrigerationUnit type to Egeria. It would inherit from [Infrastructure](/types/0/001-Base-Model) and include a new attribute called *coolantType*.
+
+
+
+This type would be used to store details of the refrigeration units. She takes her idea to Erin, who calls a meeting to discuss it. There are two items on the agenda:
+
+* Is Egeria the right place to store this information? We could just use a database?
+* If we do use Egeria, is this new type all that we need?
+
+
+> Tom requesting permission to add the new open metadata type to Egeria
+
+The decision to use Egeria for this data was easy. Egeria supports the ongoing integration of the company's asset management systems, and providing a common language for describing assets across the company. It then was well placed to support the governance of this equipment.
+
+The proposed new type generated more discussion. Erin had picked up on Tom's broader plan to bring details of other equipment relevant to sustainability. She suggested that they should define a new type called Equipment, and then have RefrigerationUnit inherit from Equipment.
+This means that they can have common management of all Equipment, beyond just refrigeration units.
+
+The others agreed and [Lemmie Stage](/practices/coco-pharmaceuticals/personas/lemmie-stage) was asked to add the new type to Egeria.
+
+#### Adding a new open metadata type for refrigeration units
+
+There are three steps to adding a new open metadata type:
+
+* Create a new type definition in an [Open Metadata Archive](/concepts/open-metadata-archive).
+* Add the new archive to the start-up list of archive files to load at [Metadata Access Store](/concepts/metadata-access-store) start-up.
+* Restart the metadata access store to load the new archive.
+
+
+
+### Awarding the First CFC-Free certificate
+
+Once the RefrigerationUnit was installed in Egeria, Tom was able to load the refrigeration unit data that she had collected from the different sites. She showed the results to her boos, [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint) to request budget to replace the CFC-containing units with CFC-free alternatives. He agrees because it matches their strategy and the budget is approved.
+
+Then the race is on to acquire the CFC-free alternatives. Which location will be the first to be CFC-Free? Not surprisingly, the New York lab is the first, because [Zach Now](/practices/coco-pharmaceuticals/personas/zach-now), forewarned of the initiative, had gone ahead and ordered new units before Tom had the data into Egeria! The other locations followed over the next few months allowing Tom to declare the company CFC-Free.
+
+
+
+## In conclusion
+
+Tom has presented the first findings of her sustainability program to the board. The board could see she had made a solid start. There was more to do, but she had created foundations that they can build on, both technically and culturally, and demonstrated improvements though a simple first initiative.
+
+
+
+The board then asked her, "So what is next?"
+
+Tom responds:
+
+* We need to automate the capture of equipment data into Egeria. [Reggie Mint](/practices/coco-pharmaceuticals/personas/reggie-mint), the head of Finance, was interested in how this could help his capital management since he had no global view of their equipment. Stew see this as a way to get more budget to replace obsolete equipment that is costing too much to maintain, and is slowing down his manufacturing automation initiative. The board agreeds to fund a feasibility study to understand what this would cost. Jules suspected they should invest in a global asset management system integrated with Egeria, rather than build their own in Egeria. He volunteers [Erin Overview](/practices/coco-pharmaceuticals/personas/erin-overview) to lead the feasibility study.
+* We should start looking at our scope 3 requirements, which means working with their suppliers to understand their emissions and how they can reduce them. This also ties up with other efforts to tighten their supplier selection after their [fraud incident](/practices/coco-pharmaceuticals/scenarios/investigating-suspicious-activity/overview).
+The story continues ...
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/peter-building-sustainability-pipeline.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/peter-building-sustainability-pipeline.png
new file mode 100644
index 00000000000..9aaf6527de4
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/peter-building-sustainability-pipeline.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type-proposed.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type-proposed.svg
new file mode 100644
index 00000000000..d9e56e4c0f8
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type-proposed.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type.svg b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type.svg
new file mode 100644
index 00000000000..3af43f229ea
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/refrigeration-unit-type.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-discussing-broader-sus-team-structure.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-discussing-broader-sus-team-structure.png
new file mode 100644
index 00000000000..3033429b51d
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-discussing-broader-sus-team-structure.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-having-lunch.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-having-lunch.png
new file mode 100644
index 00000000000..769bd68c58e
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-erin-tom-having-lunch.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-working-on-facilities-plan.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-working-on-facilities-plan.png
new file mode 100644
index 00000000000..b81305cd807
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/stew-working-on-facilities-plan.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-definitions-screenshot.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-definitions-screenshot.png
new file mode 100644
index 00000000000..85567f8ffee
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-definitions-screenshot.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-samples.drawio b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-samples.drawio
new file mode 100644
index 00000000000..00c5f8bf10c
--- /dev/null
+++ b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/sustainability-samples.drawio
@@ -0,0 +1,2633 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tessa-accessing-hazardous-materials.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tessa-accessing-hazardous-materials.png
new file mode 100644
index 00000000000..d05d157a3e3
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tessa-accessing-hazardous-materials.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-awarding-zach-cfc-free-certificate.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-awarding-zach-cfc-free-certificate.png
new file mode 100644
index 00000000000..ee4b052c47f
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-awarding-zach-cfc-free-certificate.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-erin-building-sustainability-glossary.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-erin-building-sustainability-glossary.png
new file mode 100644
index 00000000000..dec5f83cf29
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-erin-building-sustainability-glossary.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-faith-discussing-sustainability-community.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-faith-discussing-sustainability-community.png
new file mode 100644
index 00000000000..505f2ac8bc9
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-faith-discussing-sustainability-community.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-gary-on-zoom-with-bucharest-factory.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-gary-on-zoom-with-bucharest-factory.png
new file mode 100644
index 00000000000..dd23e73a8ac
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-gary-on-zoom-with-bucharest-factory.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-talking-to-coco-leaders.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-talking-to-coco-leaders.png
new file mode 100644
index 00000000000..739426efb19
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-talking-to-coco-leaders.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-thinking-about-sustainability.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-thinking-about-sustainability.png
new file mode 100644
index 00000000000..9a69246bd59
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-in-car-thinking-about-sustainability.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-leading-sustainabilty-community-zoom-call.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-leading-sustainabilty-community-zoom-call.png
new file mode 100644
index 00000000000..3eda7db5b5d
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-leading-sustainabilty-community-zoom-call.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-mapping-fuel-types.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-mapping-fuel-types.png
new file mode 100644
index 00000000000..8ed9bc0709f
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-mapping-fuel-types.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-presenting-ghg-emissions-analysis.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-presenting-ghg-emissions-analysis.png
new file mode 100644
index 00000000000..2876a6db5f2
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-presenting-ghg-emissions-analysis.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-zach-discussing-refrigerants.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-zach-discussing-refrigerants.png
new file mode 100644
index 00000000000..ab88efd0708
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/tom-zach-discussing-refrigerants.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/two-toms-mapping-fuel-types.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/two-toms-mapping-fuel-types.png
new file mode 100644
index 00000000000..7b68144da0d
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/two-toms-mapping-fuel-types.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/zach-working-on-plane.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/zach-working-on-plane.png
new file mode 100644
index 00000000000..4ea7205f87e
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-initiative/zach-working-on-plane.png differ
diff --git a/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-team.png b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-team.png
new file mode 100644
index 00000000000..e2c496e4e3e
Binary files /dev/null and b/site/docs/practices/coco-pharmaceuticals/scenarios/sustainability-team.png differ
diff --git a/site/docs/services/omvs/index.md b/site/docs/services/omvs/index.md
index 08502036964..1f96d288cf7 100644
--- a/site/docs/services/omvs/index.md
+++ b/site/docs/services/omvs/index.md
@@ -16,9 +16,9 @@ This first collection of view services provide generic function, using in many s
| [Actor Manager](/services/omvs/actor-manager/overview) | **Create and maintain actor information.** | The Actor Manager API is a REST API to set up actor profiles, contact details, contribution records, actor roles and user identities. |
| [Asset Maker](/services/omvs/asset-maker/overview) | **Create and maintain asset information.** | The Asset Maker API is a REST API to set up all types of assets and software capabilities. |
| [Automated Curation](/services/omvs/automated-curation/overview) | **Discovery, initiate and monitor metadata cataloging and governance actions such as automated surveying.** | The Automated Curation API is a REST API that allows asset owners and consumers to set up, execute and monitor automated harvesting and governance services. |
-| [Classification Explorer](/services/omvs/classification-explorer/overview) | **Manage relationships and classifications used to enrich details of elements.** | The Classification Manager API enables the caller to maintain key classifications and relationships on elements. It is designed to support curaiton and stewardship. |
+| [Classification Explorer](/services/omvs/classification-explorer/overview) | **Manage relationships and classifications used to enrich details of elements.** | The Classification Manager API enables the caller to maintain key classifications and relationships on elements. It is designed to support curation and stewardship. |
| [Collection Manager](/services/omvs/collection-manager/overview) | **Manage collections of assets and other elements.** | The Collection Manager API provides the REST APIs to create collections of asset and other elements such as glossary terms or policies. The collections can be nested (like folders in a file system) and they can be classified to describe the type of collection. For example, one type of classification for a collection is a *DigitalProduct* that allows the collections of assets and other related material to describe data and or services for a specific consumer or purpose. |
-| [Connection Maker](/services/omvs/connection-maker/overview) | **Create and maintain connection information for assets.** | The Connection Maker API is a REST API to set up connectios, connector types and endpoints. |
+| [Connection Maker](/services/omvs/connection-maker/overview) | **Create and maintain connection information for assets.** | The Connection Maker API is a REST API to set up connections, connector types and endpoints. |
| [External Links](/services/omvs/external-links/overview) | **Maintain information about external sources and identifiers.** | The External Links API manages details of external identifiers that capture the identifier for elements that are replicated in multiple systems/tools, as well as details of external sources such as external data sets, related media and models. |
| [Feedback Manager](/services/omvs/feedback-manager/overview) | **Maintain feedback such as comments, tags, reviews, likes and note logs.** | The Feedback Manager API manages feedback from users. A registered user is able to add comments, informal tags, notes, reviews and likes to elements such as assets or glossary terms. |
| [Governance Officer](/services/omvs/governance-officer/overview) | **Maintain governance definitions used to define any governance domain.** | The Governance Officer API is a REST API supporting the creation and editing of a new governance domain. |
diff --git a/site/docs/services/omvs/notification-manager/overview.md b/site/docs/services/omvs/notification-manager/overview.md
index 523d0a3d3b2..b26e9309e56 100644
--- a/site/docs/services/omvs/notification-manager/overview.md
+++ b/site/docs/services/omvs/notification-manager/overview.md
@@ -26,7 +26,7 @@ In addition:
* [Egeria-baudot-create-subscription.http](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/view-services/notification-manager/Egeria-baudot-create-subscription.http) shows how to create a subscription for an Open Metadata Digital Product.
* [Egeria-baudot-subscription-processes.http](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/view-services/notification-manager/Egeria-baudot-subscription-processes.http) shows the subscription processes for an Open Metadata Digital Product.
-* [Egeria-notification-types-and-actions.http](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/view-services/notification-manager/Egeria-notification-types-and-actions.http) shows how to retrieve informaiton about the notification types used in Egeria.
+* [Egeria-notification-types-and-actions.http](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/view-services/notification-manager/Egeria-notification-types-and-actions.http) shows how to retrieve information about the notification types used in Egeria.
## Usage Examples
diff --git a/site/docs/types/4/0401-Governance-Definitions.md b/site/docs/types/4/0401-Governance-Definitions.md
index f3e2e0b4aa4..0d765ab9c2f 100644
--- a/site/docs/types/4/0401-Governance-Definitions.md
+++ b/site/docs/types/4/0401-Governance-Definitions.md
@@ -3,8 +3,10 @@
# 0401 Governance Definitions
-The world of governance is divided into different governance domains that focus on a specific set of assets or activities.
-Egeria aims to unify the metadata and governance activity across these governance domains.
+The world of governance is divided into different [governance domains](/concepts/governance-domain) that focus on a specific set of assets or activities.
+
+Egeria aims to unify the metadata and governance activity across these governance domains. The description of how a governance domain is operating is described in a [governance definition](/concepts/governance-definition).
+The governance definitions are linked to the elements they govern through the *GovernedBy* relationship.

@@ -14,7 +16,7 @@ Egeria aims to unify the metadata and governance activity across these governanc
*GovernanceDefinition* describes an aspect of a governance program. They are authored in the metadata repository. They inherit from [AuthoredReferenceable](/types/0/0010-Base-Model), which means they have a unique identifier and link to external references for more information.
-The *GovernanceDomainIdentifier* defines which governance domain this governance definition belongs to (0 for all). The following are examples of governance domains:
+The *domainIdentifier* defines which governance domain this governance definition belongs to (0 for all). The following are examples of governance domains:
* DATA - the governance of data and its use.
* PRIVACY - the support for data privacy.
@@ -50,7 +52,7 @@ The *GovernedBy* relationship links the governance definitions to the elements t
* *description* - the description of how the governance is defined.
!!! info "Related types"
- * The role of leader of a governance domain is represented as a [*GovernanceOfficer*](/types/4/0445-Governance-Roles) entity.
+ * The role of leader of a governance domain is represented as a [*GovernanceRole*](/types/4/0445-Governance-Roles) entity with the *actorRoleType* of *GovernanceOfficer*.
* The scope of a governance definition is represented through the [ScopedBy](/types/1/0120-Assignment-Scopes).
!!! info "Implementing Services"
diff --git a/site/docs/types/4/0415-Governance-Responses.md b/site/docs/types/4/0415-Governance-Responses.md
index 05af5054731..949265995b0 100644
--- a/site/docs/types/4/0415-Governance-Responses.md
+++ b/site/docs/types/4/0415-Governance-Responses.md
@@ -17,7 +17,7 @@ There are three main types of policy:
* Principles define the overall values and guidelines for the organization.
* Obligations define specific actions or processing that must be accommodated.
-* Approaches define best practices for how a resource should be implemented and managed.
+* Approaches define new initiatives, best practices and ways of working that will be adopted.
## GovernancePrinciple
@@ -29,7 +29,7 @@ The *GovernanceObligation* entity defines a policy that describes a requirement,
## GovernanceApproach
-The *GovernanceApproach* entity defines a policy that describes a method that should be used for a particular activity.
+The *GovernanceApproach* entity defines a policy that describes a method that should be used for a particular activity, or a new activity/initiative that will be adopted.
## GovernanceResponse
diff --git a/site/docs/types/4/0457-Connector-Activity-Reports.md b/site/docs/types/4/0457-Connector-Activity-Reports.md
index 4d74f1a7926..35d3e41f96f 100644
--- a/site/docs/types/4/0457-Connector-Activity-Reports.md
+++ b/site/docs/types/4/0457-Connector-Activity-Reports.md
@@ -12,7 +12,7 @@ The *ConnectorActivityReport* entity describes the updates made by an [integrati
The attributes are as follows:
* *serverName* - name of the [integration daemon](/concepts/integration-daemon) where the integration connector is running/ran or the [engine host](/concepts/engine-host) where the governance service ran.
-* *connectorId* : unique identifier of the connector. This is either the unique identifier (guid) of the [RegisteredIntegrationConnector](/types/4/0464-Dynamic-Integraiton-Groups) relationship that links the integration connector into a running integration group OR the unique identifier of the [SupportedGovernanceService](/types/4/0461-Governance-Engines) relationship that identified the governance service to run.
+* *connectorId* : unique identifier of the connector. This is either the unique identifier (guid) of the [RegisteredIntegrationConnector](/types/4/0464-Dynamic-Integration-Groups) relationship that links the integration connector into a running integration group OR the unique identifier of the [SupportedGovernanceService](/types/4/0461-Governance-Engines) relationship that identified the governance service to run.
* *connectorName* : name of the connector. This is either set in the integration daemon's configuration document or it is the unique identifier (guid) of the *RegisteredIntegrationConnector* relationship that links the integration connector into a running integration group.
* *createCounts* : A map of element type names to the number of instances of that type that were created and anchored to the anchor subject.
* *updateCounts* : A map of element type names to the number of instances of that type that were updated while anchored to the anchor subject.
diff --git a/site/docs/types/5/0512-Derived-Schema-Elements.md b/site/docs/types/5/0512-Derived-Schema-Elements.md
index e8a59f1cb1c..97573b8c530 100644
--- a/site/docs/types/5/0512-Derived-Schema-Elements.md
+++ b/site/docs/types/5/0512-Derived-Schema-Elements.md
@@ -10,17 +10,16 @@ hide:
Derived schema elements access other data, possibly in the same or a different asset to generate/derive the values for the attribute. Examples of this are [database views](/types/5/0534-Relational-Schemas) and [derived database columns]((/types/5/0534-Relational-Schemas)).
-The *CalculatedValue* classification contains the *formula* attribute which is set to the query that retrieves the data, *formulaType* describes the notation language used to describe the formula. There are optional links to *DerivedSchemaTypeQueryTarget* to identify which schema elements are accessed by the formula. The formula may contain placeholders that refer to the *queryId* in *DerivedSchemaTypeQueryTarget*. Alternatively, the query can be expressed complement using the *query* and *queryType* attributes.

+## CalculatedValue classification
+
+The *CalculatedValue* classification contains the *formula* attribute which is set to the query that retrieves the data, *formulaType* describes the notation language used to describe the formula. There are optional links to *DerivedSchemaTypeQueryTarget* to identify which schema elements are accessed by the formula. The formula may contain placeholders that refer to the *queryId* in *DerivedSchemaTypeQueryTarget*. Alternatively, the query can be expressed complement using the *query* and *queryType* attributes.
+
+## DerivedSchemaTypeQueryTarget relationship
-??? deprecated "Deprecated types"
- The following types were replaced by *DerivedSchemaTypeQueryTarget*.
+The *DerivedSchemaTypeQueryTarget* relationship identifies the schema elements that are queried to generate all or part of the value for the attribute at end 1.
- - *DerivedSchemaAttribute*
- - *SchemaLinkElement*
- - *LinkedType*
- - *SchemaLinkToType*
--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/types/7/0720-Information-Supply-Chains.md b/site/docs/types/7/0720-Information-Supply-Chains.md
index dcc50d5845e..fa75d0df2a7 100644
--- a/site/docs/types/7/0720-Information-Supply-Chains.md
+++ b/site/docs/types/7/0720-Information-Supply-Chains.md
@@ -4,21 +4,8 @@
# 0720 Information Supply Chains
-Lineage is typically captured from the running technology at a very fine-level of detail. This detail enables automated governance processes to validate that the data pipelines are running as they should be. However, this level of detail is too much for most business users and regulators to comprehend. Therefore, it is necessary to model the flow of data at a level of detail that is meaningful to these users and correlate the fine-grained detail to this business view.
-An *InformationSupplyChain* is the highest level of abstraction for lineage. It typically identifies the flow of a particular type of data across a digital landscape. For example, there may be an information supply chain capturing risk data for a regulatory compliance report, and another one showing how the data necessary for carbon accounting is assembled.
-
-It is an architectural construct that can provide the focus for data governance activities that ensure data is delivered where it is needed in a timely and efficient manner.
-
-The information supply chain is typically broken down into segments also represented by *InformationSupplyChain* entities that each define a particular exchange of data. For example, it may be the flow of data through a specific business unit or country. The segments are linked to their parent information supply chain via the *InformationSupplyChainComposition* relationship. Their relationship to one another, and its logical sources and destinations are captured using *InformationSupplyChainLink* relationships.
-
-The unique names of the information supply chains, are encoded in the lineage relationships captured in the lower levels of lineage detail:
-
-* The architectural view of the data flow that the information supply chain represents is described using [solution components](/types/7/0730-Solution-Components) that are linked via [ports and wires](/types/7/0735-Solution-Ports-and-Wires). The [*SolutionLinkingWire*](/types/7/0735-Solution-Ports-and-Wires) contains the unique names (qualifiedName) of the information supply chains that it implements. The is is required because multiple information supply chains may share a part of the data flow.
-
-* The fine-grained view captured from the implementation and operation of the deployed technology is described using the [data passing](/types/7/0750-Data-Passing) and [lineage mapping](/types/7/0770-Lineage-Mapping) relationships.
-
-If additional processing is required to move the data between solution components *along the wire*, for example via an ETL process, this is shown by an *ImplementedBy* relationship between the information supply chain and the [Process](/types/0/0010-Base-Model) that represents the implementation. Alternatively, the component that provides the data movement can be show explicitly as a solution component in the [solution blueprint](/types/7/0740-Solution-Blueprints).
+An [InformationSupplyChain](/concepts/information-supply-chain) is a high level view of lineage.

diff --git a/site/docs/types/7/0735-Solution-Ports-and-Wires.md b/site/docs/types/7/0735-Solution-Ports-and-Wires.md
index a1464c8d6d2..0693f0d7c71 100644
--- a/site/docs/types/7/0735-Solution-Ports-and-Wires.md
+++ b/site/docs/types/7/0735-Solution-Ports-and-Wires.md
@@ -18,7 +18,7 @@ The *SolutionComponentPort* relationship links a solution component to one of it
## SolutionLinkingWire relationship
-The *SolutionLinkingWire* shows the linkage between solution components via their ports to other elements in the architecture. The *iscQualifiedNames* property allows linkage to the [information supply chains](/types/7/0720-Information-Supply-Chains) that identify critical data flows for the organization. The *label* and *description* attributes help to explain how/why the lineage flow progresses.
+The *SolutionLinkingWire* shows the linkage between solution components via their ports to other elements in the architecture. The *iscQualifiedNames* attribute allows linkage to the [information supply chains](/types/7/0720-Information-Supply-Chains) that identify critical data flows for the organization. The *label* and *description* attributes help to explain how/why the lineage flow progresses.
## SolutionPortDelegation relationship
diff --git a/site/docs/user-interfaces/index.md b/site/docs/user-interfaces/index.md
index 0c1f47279ec..463eee64df9 100644
--- a/site/docs/user-interfaces/index.md
+++ b/site/docs/user-interfaces/index.md
@@ -7,23 +7,29 @@ Most metadata is created and used through the tools and platforms (third party t
Egeria adds the following specialized user interfaces that view metadata across the open metadata ecosystem, irrespective of which technology originated it, or where it is stored. They also allow your to create the descriptive metadata that provides the business context to your metadata.
-| User Interface Name | Description |
-|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Egeria Explorer](/user-interfaces/egeria-explorer/overview) | A web-based browser for searching, viewing and navigating through your open metadata. |
-| [Dr.Egeria](/user-interfaces/dr-egeria/overview) | A markdown processor that can be used to create, update and delete open metadata and to create reports. |
-| [Hey Egeria](/user-interfaces/hey-egeria/overview) | Command line services and visualizations for technical and data professionals working with the open metadata ecosystem or managing Egeria's infrastructure. |
-| [My Egeria](/user-interfaces/my-egeria/overview) | Interactive user interface for nagivating collections of open metadata and performing multi-step tasks. |
-| [Mermaid Diagrams](/user-interfaces/mermaid/overvew) | Markdown based diagrams showing collections of linked metadata elements that can be rendered in a JavaScript display such as Jupyter Notebooks and drawio diagrams. |
+| User Interface Name | Description |
+|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [Egeria Explorer](/user-interfaces/egeria-explorer/overview) | A web-based browser for searching, viewing and navigating through your open metadata. |
+| [Lineage Explorer](/user-interfaces/lineage-explorer/overview) | A web-based browser for exploring lineage graphs at different levels of detail. |
+| [The Catalog](/user-interfaces/the-catalog/overview) | A web-based browser for searching, viewing and navigating through your inventories of infratrusture assets, data assets, APIs and processes. |
+| [Dr.Egeria](/user-interfaces/dr-egeria/overview) | A markdown processor that can be used to create, update and delete open metadata and to create reports. |
+| [Hey Egeria](/user-interfaces/hey-egeria/overview) | Command line services and visualizations for technical and data professionals working with the open metadata ecosystem or managing Egeria's infrastructure. |
+| [My Egeria](/user-interfaces/my-egeria/overview) | Interactive user interface for nagivating collections of open metadata and performing multi-step tasks. |
+| [Mermaid Diagrams](/user-interfaces/mermaid/overvew) | Markdown based diagrams showing collections of linked metadata elements that can be rendered in a JavaScript display such as Jupyter Notebooks and drawio diagrams. |
These user interfaces are under constant development, and it is worthwhile to keep engaged with the community members that are developing them.
Egeria also integrates with other popular user technologies to provide a comprehensive metadata management experience. These are described in the following sections.
-## Subject Matter Experts (SMEs)
+## User Perspectives
+
+--8<-- "snippets/work-in-progress.md"
+
+### Subject Matter Experts (SMEs)
If you are a subject matter expert asked to create some definitions (such as glossary terms, data standards, ...) or to capture the results of some research you are doing, Egeria provides a number of tools to help you do this. These tools are built on open standard formats such as Markdown and HTML. They work with files, so you can edit them using your favourite editor, share your work with colleagues for review and feedback and backup your files to a tool such as GitHub for safe-keeping and audit. When the content is ready, it can be loaded into open metadata, linked to other information, queried using different report styles and published to a website.
-### Dr.Egeria
+#### Dr.Egeria
Dr.Egeria validates and processes markdown documents that include Dr.Egeria commands to maintain and query the open metadata in Egeria. The queries generate reports in a variety of formats including Markdown and HTML.
@@ -32,13 +38,13 @@ Dr.Egeria validates and processes markdown documents that include Dr.Egeria comm
[More information on Dr.Egeria](/user-interfaces/dr-egeria/overview)
-### Egeria's Webserver
+#### Egeria's Webserver
-[Egeria Workspaces](/egeria-workspaces) includes a webserver in both the [quickstart](/egeria-workspaces/quick-start/overview) and [freshstart](/egeria-workspaces/fresh-start/overview) environments. This webserver can publish HTML reports generated by **Dr.Egeria** as a website to share informaiton with other people.
+[Egeria Workspaces](/egeria-workspaces) includes a webserver in both the [quickstart](/egeria-workspaces/quick-start/overview) and [freshstart](/egeria-workspaces/fresh-start/overview) environments. This webserver can publish HTML reports generated by **Dr.Egeria** as a website to share information with other people.

-### Apache SuperSet dashboards
+#### Apache SuperSet dashboards
[Apache SuperSet](https://superset.apache.org/) is an open source dashboard and reporting tool. It reads data from relational databases.
@@ -48,19 +54,19 @@ With the technology managed by Egeria Workspaces, you to create dashboards and r

-## Data Engineers and Data Scientists
+### Data Engineers and Data Scientists
-## DevOps and Operations Engineers
+### DevOps and Operations Engineers
-## Software Developers
+### Software Developers
-### Connector Developers
+#### Connector Developers
-### Python Developers
+#### Python Developers
-### Egeria Contributors
+#### Egeria Contributors
diff --git a/site/docs/user-interfaces/lineage-explorer/overview.md b/site/docs/user-interfaces/lineage-explorer/overview.md
new file mode 100644
index 00000000000..e7dbc7ebd13
--- /dev/null
+++ b/site/docs/user-interfaces/lineage-explorer/overview.md
@@ -0,0 +1,16 @@
+---
+hide:
+- toc
+---
+
+
+
+
+# Lineage Explorer
+
+**Lineage Explorer** is a user interface for exploring lineage at different levels of detail.
+
+--8<-- "snippets/work-in-progress.md"
+
+
+--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/docs/user-interfaces/the-catalog/overview.md b/site/docs/user-interfaces/the-catalog/overview.md
new file mode 100644
index 00000000000..7a33b804baf
--- /dev/null
+++ b/site/docs/user-interfaces/the-catalog/overview.md
@@ -0,0 +1,16 @@
+---
+hide:
+- toc
+---
+
+
+
+
+# The Catalog
+
+**The Catalog** is a user interface for exploring technical assets such as infrastructure, data assets, APIs and software processes.
+
+--8<-- "snippets/work-in-progress.md"
+
+
+--8<-- "snippets/abbr.md"
\ No newline at end of file
diff --git a/site/mkdocs.yml b/site/mkdocs.yml
index f02f59b12fb..16f5d20f28b 100644
--- a/site/mkdocs.yml
+++ b/site/mkdocs.yml
@@ -67,6 +67,8 @@ nav:
- User Interfaces:
- User Interface overview: user-interfaces/index.md
- Egeria Explorer: user-interfaces/egeria-explorer/overview.md
+ - Lineage Explorer: user-interfaces/lineage-explorer/overview.md
+ - The Catalog: user-interfaces/the-catalog/overview.md
- Dr.Egeria: user-interfaces/dr-egeria/overview.md
- Hey Egeria: user-interfaces/hey-egeria/overview.md
- My Egeria: user-interfaces/my-egeria/overview.md
@@ -810,7 +812,7 @@ nav:
- Governance Team: practices/coco-pharmaceuticals/scenarios/building-the-governance-team/overview.md
- Information Supply Chains: practices/coco-pharmaceuticals/scenarios/defining-information-supply-chains/overview.md
- Multi-Faceted Governance: practices/coco-pharmaceuticals/scenarios/defining-multi-faceted-governance/overview.md
- - New Systems Architecture: practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture-overview/overview.md
+ - New Systems Architecture: practices/coco-pharmaceuticals/scenarios/defining-new-systems-architecture/overview.md
- New Digital Service: practices/coco-pharmaceuticals/scenarios/new-clinical-trials-digital-service/overview.md
- Patient Data Sharing Hub: practices/coco-pharmaceuticals/scenarios/patient-data-sharing-hub/overview.md
- Preparing for Martyn's Law: practices/coco-pharmaceuticals/scenarios/preparing-for-martyns-law/overview.md
diff --git a/site/snippets/release-notes/5-0.md b/site/snippets/release-notes/5-0.md
index 8cf55007eae..861bce61562 100644
--- a/site/snippets/release-notes/5-0.md
+++ b/site/snippets/release-notes/5-0.md
@@ -115,7 +115,7 @@ Release 5.0 is a major functional release focused on usability, both from the po
There is a new [survey action service](/concepts/survey-action-service) that provides a report on the content of an Apache Atlas server. It is called the [Apache Atlas Survey Service](/connectors/apache-atlas/apache-atlas-survey-action-service). This survey action services complements the [Apache Atlas Integration Connector](/connectors/apache-atlas/apache-atlas-catalog-integration-connector) that exchanges metadata between the open metadata ecosystem and an Apache Atlas server.
??? functional "Extended support for file system monitoring"
- The context for all the [Open Metadata Integration Services (OMIS)](/services/omis) has been updated to support a file system listener. This means that [integration connectors](/concepts/integraiton-connector) can easily monitor changing files and directories. This can be useful for situations where new information is being exchanged with open metadata using files such as CSV files and spreadsheets.
+ The context for all the [Open Metadata Integration Services (OMIS)](/services/omis) has been updated to support a file system listener. This means that [integration connectors](/concepts/integration-connector) can easily monitor changing files and directories. This can be useful for situations where new information is being exchanged with open metadata using files such as CSV files and spreadsheets.
??? functional "New View Service: Action Author OMVS"
[Action Author OMVS](/services/omvs/action-author/overview) is a new view service for managing the definitions of governance action types and and governance action processes.