diff --git a/.cspell-project-words.txt b/.cspell-project-words.txt
index ef4b9f3d4615e93796db4788cca495a0afdf03e2..41bce7fe303625aa8c09bac4db0b37871be5b18f 100644
--- a/.cspell-project-words.txt
+++ b/.cspell-project-words.txt
@@ -5,3 +5,6 @@ fontawesome
 mexic
 texa
 knowledgeblock
+cust
+spidering
+lemmatization
diff --git a/.gitignore b/.gitignore
index 77230ba6b854f1e3500553941ec5cd5e5c57ed73..cb49ca7bbfad7ce893feb23481f903fecfa3cee5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,3 @@
 composer.lock
 web/*
-vendor/*
\ No newline at end of file
+vendor/*
diff --git a/docs/capture/01 integration.md b/docs/capture/01 integration.md
new file mode 100644
index 0000000000000000000000000000000000000000..95862046ef88587fcc235414f8c5923742c0f4f7
--- /dev/null
+++ b/docs/capture/01 integration.md	
@@ -0,0 +1,41 @@
+
+##Mandatory##
+
+Seamless, logical transition for a user searching on web portal.  Ability to initiate a search and present results before or after the incident creation. The content of search strings and documents reviewed are preserved and automatically populated in the incident or article.
+
+##Practice/Technique##
+
+* Process Integration
+* Seamless Technology Integration
+* Integration with Web Portals and Online Processes
+
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 6.5: KCS Process Integration Indicators](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/020/060)
+
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Process Integration
+  - Seamless Technology Integration
+  - Integration with Web Portals and Online Processes
+---
\ No newline at end of file
diff --git a/docs/capture/02 context.md b/docs/capture/02 context.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a5b51ac352e154a0b1375f4d6ef5b0c4c3817ad
--- /dev/null
+++ b/docs/capture/02 context.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+As the issue is being solved information can be captured in the requestor's context and does not have to be re-typed to create an new article.
+
+##Practice/Technique##
+
+* Capture
+* Capture the Requestor's Context
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 1.2 Capture the Requestor's Context](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/010/020)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Capture
+  - Capture the Requestor's Context
+---
\ No newline at end of file
diff --git a/docs/capture/03 relevant.md b/docs/capture/03 relevant.md
new file mode 100644
index 0000000000000000000000000000000000000000..8deded8ecceb314f59dd0c4e8e8a5614340bdcba
--- /dev/null
+++ b/docs/capture/03 relevant.md	
@@ -0,0 +1,37 @@
+##Mandatory##
+
+Preserved information can be edited or re-purposed into a KCS article. Searches shall be capable of being refined iteratively through rewording the search string, without requiring changes to the text of the incident record.  Ideally, other methods of search refinement shall be provided as well (such as drill down by taxonomy, ontology, or tags.)
+
+
+##Practice/Technique##
+
+* Capture
+* Capture Relevant Content
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 1.2 Capture the Requestor's Context](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/010/020)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Capture
+  - Capture Relevant Content
+---
\ No newline at end of file
diff --git a/docs/content health/01.md b/docs/content health/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..aafe4477a1053d919181a69122668f6d77cb08b8
--- /dev/null
+++ b/docs/content health/01.md	
@@ -0,0 +1,42 @@
+##Mandatory##
+
+For each KCS article, the system shall record:
+
+Date Created, and ID of creator
+Modification date/times, and ID
+Article confidence change date/time and ID
+Article audience change date/time and ID
+Article governance change date/time and ID
+
+
+##Practice/Technique##
+
+* Content Health
+* The KCS Article State
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 5.1: KCS Article Structure](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/020)
+
+##Demo Requirements for Verified Only##
+Scenario 3
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - The KCS Article State
+---
\ No newline at end of file
diff --git a/docs/content health/02.md b/docs/content health/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..deaeb5a107fae20c8fee93dd9d7b07b70a6cc1d3
--- /dev/null
+++ b/docs/content health/02.md	
@@ -0,0 +1,39 @@
+##Mandatory##
+
+For each KCS article, the system shall record for an identified audience(internal vs external), date, role
+
+Number of times linked to an incident
+Explicit this helped button
+Page views
+
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+Scenario 3
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+---
\ No newline at end of file
diff --git a/docs/content health/03.md b/docs/content health/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..b005c2adedc055c353cab7c55cc7c8031095cb0b
--- /dev/null
+++ b/docs/content health/03.md	
@@ -0,0 +1,41 @@
+##Mandatory##
+
+The system shall support content being in a minimum of four article confidence levels:
+Work In Progress
+Not Validated
+Validated
+Archive
+
+
+
+##Practice/Technique##
+
+* Content Health
+* The KCS Article State
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 5.1: KCS Article Structure](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/020)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - The KCS Article State
+---
\ No newline at end of file
diff --git a/docs/content health/04.md b/docs/content health/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..7543f1117ba1661277af7edee067b8714874132b
--- /dev/null
+++ b/docs/content health/04.md	
@@ -0,0 +1,39 @@
+##Mandatory##
+
+Articles in each confidence level WIP, Not Validated, Validated, Archive, shall be searchable and visible to an appropriately entitled knowledge workers based on license level, audience, and governance.
+
+##Practice/Technique##
+
+* Content Health
+* The KCS Article State
+* Article Visibility: Who Gets to See What
+
+
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 5.1: KCS Article Structure](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/020)
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - The KCS Article State
+  - Article Visibility: Who Gets to See What
+---
\ No newline at end of file
diff --git a/docs/content health/05.md b/docs/content health/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..acefabef4e9dd28d41421be9f438eb4e9008bcf5
--- /dev/null
+++ b/docs/content health/05.md	
@@ -0,0 +1,37 @@
+##Not Mandatory##
+
+Specific staff, for example KCS Publishers or KDE's, shall have the ability to see articles that are Not Validated, and that have been linked to N incidents, where N may be a site-configurable or individually settable parameter.  This mechanism may be implemented, for example, through a search or a special queue.
+
+##Practice/Technique##
+
+* Content Health
+* Assessing the Value of Articles
+* Article value based on reuse
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.10: Content Health Indicators
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Content Health
+  - Assessing the Value of Articles
+  - Article value based on reuse
+---
\ No newline at end of file
diff --git a/docs/content health/06.md b/docs/content health/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..efd302bf1bc053493c83bd1af916cc45d0f69dd1
--- /dev/null
+++ b/docs/content health/06.md	
@@ -0,0 +1,41 @@
+##Mandatory##
+
+Processing customer feedback on KCS articles. Ability to trigger workflow in order to process the feedback.  Respond, track and report on it.  Flag completed. Provide feedback of the value of giving feedback.  Same concept as Flag-it on article.  Should be done at any point where feedback is provided. (Ideally - to report on turn around time.
+1.  Feedback can be on a separate object
+2. Feedback can be tracked by state
+3. What is the feedback, how long it there
+4. What is the state, created date, date of change.
+
+##Practice/Technique##
+
+* Content Health
+* Self-Service Measures
+* Integrating Feedback
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.12: Self-Service Measures
+
+
+##Demo Requirements for Verified Only##
+Scenario 2
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Self-Service Measures
+  - Integrating Feedback
+---
\ No newline at end of file
diff --git a/docs/content health/07.md b/docs/content health/07.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc69725f9cc3c0f13b6f8dfa8e68be343d364a25
--- /dev/null
+++ b/docs/content health/07.md	
@@ -0,0 +1,35 @@
+##Not Mandatory##
+
+Mechanism to configure rules to automatically publish KCS articles.
+
+##Practice/Technique##
+
+* Content Health
+* Self-service Success
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Self-service Success
+---
\ No newline at end of file
diff --git a/docs/content health/08.md b/docs/content health/08.md
new file mode 100644
index 0000000000000000000000000000000000000000..be4028437169c7980e3505979298b29929fa0bad
--- /dev/null
+++ b/docs/content health/08.md	
@@ -0,0 +1,30 @@
+##Not Mandatory##
+
+Enable a configuration that allows an external audience or end users in the community to reuse, create, and modify KCS articles
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/content health/09.md b/docs/content health/09.md
new file mode 100644
index 0000000000000000000000000000000000000000..42fa3dbc5d2dd86c50131e697b1ee687a3540c87
--- /dev/null
+++ b/docs/content health/09.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Describe your strategy and licensing model to author content both internally and externally.  (example: Single user named license internal to the company can create content in the knowledge base, vs unlimited number of users can create knowledge in the knowledge base vs. external customers can create draft knowledge in the knowledge base)
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/content health/10.md b/docs/content health/10.md
new file mode 100644
index 0000000000000000000000000000000000000000..7262fd2ecf6d8f2787b480bcbfc336c09d7ed518
--- /dev/null
+++ b/docs/content health/10.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Describe the self-service access point (integrated into product, mobile app, portal or web page)
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/content health/11.md b/docs/content health/11.md
new file mode 100644
index 0000000000000000000000000000000000000000..38d79bbc45e57aa7fd7cc1e4275b4fe197263be2
--- /dev/null
+++ b/docs/content health/11.md	
@@ -0,0 +1,31 @@
+##Not Mandatory##
+
+Navigation in self-service mechanism aligns to the requestor's intent
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  -
+---
\ No newline at end of file
diff --git a/docs/content health/12.md b/docs/content health/12.md
new file mode 100644
index 0000000000000000000000000000000000000000..5dd41543dec5a5269eaf2c6e9a669151f0566220
--- /dev/null
+++ b/docs/content health/12.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Navigation in self-service transitions to assisted support (click to submit an incident or click to chat)
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/content health/13.md b/docs/content health/13.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a3205924cfa305789f8cfb20bad12b28af1eccb
--- /dev/null
+++ b/docs/content health/13.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Navigation in self-service provides for both browsing and searching (product specific, indexed table of context, FAQ's, basic search, advanced search)
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/improve/01.md b/docs/improve/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c0e5a47fe53509c29ecd46a5db59c7a098e0baf
--- /dev/null
+++ b/docs/improve/01.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+The system shall support a KCS Candidate finding and flagging content that needs to be reworked.  The flag will be visible to at least other internal users.  The flagger will have the ability to append feedback to indicate the reason for rework.
+
+##Practice/Technique##
+
+* Improve
+* Flag it or Fix it
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 4.2: Flag It or Fix It](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/040/030)
+
+##Demo Requirements for Verified Only##
+Scenario 2
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Flag it or Fix it
+---
\ No newline at end of file
diff --git a/docs/improve/02.md b/docs/improve/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae64c797a108ea3523bbb47e78bd38e6bcf14b82
--- /dev/null
+++ b/docs/improve/02.md
@@ -0,0 +1,38 @@
+##Mandatory##
+
+System shall support KCS Contributor finding and fixing KCS article immediately.
+
+##Practice/Technique##
+
+* Improve
+* Flag it or Fix it
+* License to Modify
+
+##Reference: KCS v6 Practices Guide##
+
+[KCS Roles and the Licensing Model](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/030/020)
+
+
+##Demo Requirements for Verified Only##
+Scenario 2
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Flag it or Fix it
+  - License to Modify
+---
\ No newline at end of file
diff --git a/docs/improve/03.md b/docs/improve/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..37f6d876680554c4d57c5b55f8f2d7551635e7f2
--- /dev/null
+++ b/docs/improve/03.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+All users, including external self-service users, shall have the ability to provide feedback on KCS article, such as ratings, verbatim comments or both.
+
+##Practice/Technique##
+
+* Improve
+* Flag it or Fix it
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 4.2: Flag It or Fix It](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/040/030)
+
+##Demo Requirements for Verified Only##
+Scenario 2
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Flag it or Fix it
+---
\ No newline at end of file
diff --git a/docs/improve/04.md b/docs/improve/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb77e2f0000c46e4e0fa7c0d90ea397e8116336c
--- /dev/null
+++ b/docs/improve/04.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+During the course of knowledge capture, after the user has entered content into an article, the system shall provide a function to help identify duplicate content by issuing a search based on the content currently entered in the new article. This function shall be available to the user during the course of article capture and immediately prior to submitting the article for saving into the knowledge base.
+
+##Practice/Technique##
+
+* Improve
+* Duplicate Articles
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 4.2: Dealing with Duplicates - The Merge](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/040/030#Dealing_with_Duplicates:_The_Merge)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Duplicate Articles
+---
\ No newline at end of file
diff --git a/docs/improve/05.md b/docs/improve/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..98b0f46c888dfe2e2a3e84a2a87e43427d110e32
--- /dev/null
+++ b/docs/improve/05.md
@@ -0,0 +1,35 @@
+##Not Mandatory##
+
+System shall support a function to merge duplicates. Newer articles content and links to incidents merges into the older article and the newer article gets archived or deleted.
+
+##Practice/Technique##
+
+* Improve
+* Dealing with Duplicates - The Merge
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 4.2: Dealing with Duplicates - The Merge](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/040/030#Dealing_with_Duplicates:_The_Merge)
+
+##Demo Requirements for Verified Only##
+Scenario 6
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Dealing with Duplicates - The Merge
+---
\ No newline at end of file
diff --git a/docs/improve/06.md b/docs/improve/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1cbbfe81eef2677baac6efd1eed773e9d473e10
--- /dev/null
+++ b/docs/improve/06.md
@@ -0,0 +1,36 @@
+##Mandatory##
+
+System shall support the ability to view and edit multiple articles simultaneously in order to merge duplicate articles by editing and changing state.
+
+##Practice/Technique##
+
+* Improve
+* Dealing with Duplicates - The Merge
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 4.2: Dealing with Duplicates - The Merge](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/040/030#Dealing_with_Duplicates:_The_Merge)
+
+
+##Demo Requirements for Verified Only##
+Scenario 6
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Improve
+  - Dealing with Duplicates - The Merge
+---
\ No newline at end of file
diff --git a/docs/index.md b/docs/index.md
index 8edf6774aaa78851ad9b0c853ea2820a6f1cb200..fd93378c1970a4d68ad3caf745cc2518323d97ed 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1 +1,38 @@
 Open Knowledge, a powerful and versatile Drupal distribution designed to unlock the potential of collaborative learning and knowledge sharing. Built on the robust Drupal framework, Open Knowledge is a Knowledge-Centered Service (KCS®) knowledge-base
+
+✅
+❌
+❎
+
+##Definitions##
+
+###OBConfig, for “out of the box” and/or configurable.###
+
+Out of the box functionality should fulfill the functional requirement described with no additional customization.  Requirements marked for configuration should require some setting of parameters, use of administrative tools, or other non-programmatic methods for adjusting or specifying the behavior of the system in such a way that it meets the requirement.  For each OBConfig item, the vendor should specify:
+
+The native product capability that is being used and configured
+What mechanisms are being used for the configuration (e.g., configuration files, administrative web pages, graphical user interfaces, etc.)
+The general strategy for the configuration (e.g., “create the following user classes by assigning permissions as shown…”)
+
+
+
+
+###Cust, for “Customization.”###
+
+Requirements marked for customization may require configuration but also require programming that leverages documented application programming interfaces (APIs), web services interfaces, and the like.  Typically, integration with external systems such as an authentication, directory, or incident tracking interface is accomplished with customization.  For each Cust item, the vendor should specify:
+
+The native product capability that is being used configured and customized
+What mechanisms are being used for the customization (e.g., specific APIs, extension loaders, web services calls, etc.) and the configuration (e.g., configuration files, administrative web pages, graphical user interfaces , etc.
+The general strategy for the customization and configuration
+Dependencies (e.g., third-party applications, libraries, developer tools,etc)
+Specific documents or manuals in which the mechanisms for customization and configuration are described, and the relevant page numbers or sections
+Documentation, reference implementations, or code samples specific to the specific customization, as available
+
+
+###SF, for Separate Feature.###
+
+This may be added to any of the above descriptions to indicate that additional software or services must be licensed, installed, or provisioned, and that additional fees may apply.  For each SF, please identify what a customer needs to do to gain access to this feature, including specific product or service names.
+
+
+
+Note that the Consortium anticipates that sophisticated software is designed to be configured, extended, and integrated in a typical customer installation, and “Cust” responses are expected.  The key factor for KCS Verification is to make sure that customers, third-party integrators, and the vendor’s own professional services team are able to meet these requirements in a documented, repeatable, and efficient manner.    
\ No newline at end of file
diff --git a/docs/performance assessment/01.md b/docs/performance assessment/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..5766d2646723be19a03817dddec672c3b76cdfde
--- /dev/null
+++ b/docs/performance assessment/01.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide reports showing documents created, modified, and flagged by anyone who has contributed to any version of the article over time for a particular time period. These reports will be capable of segmentation by individual, team (group of users and knowledge domain (category, tag, or node),
+
+##Practice/Technique##
+
+* Performance Assessment
+* Assessing the Creation of Value
+* Measures for Individuals and Teams
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.3: Assessing the Creation of Value
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Assessing the Creation of Value
+  - Measures for Individuals and Teams
+---
\ No newline at end of file
diff --git a/docs/performance assessment/02.md b/docs/performance assessment/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..80ae7afb13960b1865af0a80d602e72f36bd0eec
--- /dev/null
+++ b/docs/performance assessment/02.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+The system shall provide reports showing citation rates for an individual or team (group of users) and knowledge domain (category, tag, or node).
+
+##Practice/Technique##
+
+* Performance Assessment
+* Assessing the Creation of Value
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.3: Assessing the Creation of Value
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Assessing the Creation of Value
+---
\ No newline at end of file
diff --git a/docs/performance assessment/03.md b/docs/performance assessment/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..83c707c72d5245e551e957cbe0f139a0096719ae
--- /dev/null
+++ b/docs/performance assessment/03.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide reports showing a link rate indicator for a particular time period. These reports will be capable of segmentation by individual, team (group of users) and knowledge domain (category, tag, or role).
+
+##Practice/Technique##
+
+* Performance Assessment
+* Assessing the Creation of Value
+* Link Rate as an Indicator
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.3: Assessing the Creation of Value
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Assessing the Creation of Value
+  - Link Rate as an Indicator
+---
\ No newline at end of file
diff --git a/docs/performance assessment/04.md b/docs/performance assessment/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..07ba9fe2349ae61a24bc3c9f6229989820e599d3
--- /dev/null
+++ b/docs/performance assessment/04.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide reports showing the number of documents in each article state and date/times indicating how long they have been in each state.These reports will be capable of segmentation by knowledge domain (category, tag, or role.)
+
+##Practice/Technique##
+
+* Performance Assessment
+* Assessing the Creation of Value
+* KCS Article Life Cycle Trend
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.3: Assessing the Creation of Value
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Assessing the Creation of Value
+  - KCS Article Life Cycle Trend
+---
\ No newline at end of file
diff --git a/docs/performance assessment/05.md b/docs/performance assessment/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..9cd66c1b3dc79825fa80cc441a7b0513b9e24cf5
--- /dev/null
+++ b/docs/performance assessment/05.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide reports/enables showing the Content Standard Checklist with associated KCS article reference.  These reports will be capable of segmentation by individual, team (designated by coach).  Visibility should be limited to Coach, Author, and Author's Manager.
+
+##Practice/Technique##
+
+* Content Health
+* Managing KCS Article Quality
+* The Article Quality Index
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.10: Content Health Indicators
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Managing KCS Article Quality
+  - The Article Quality Index
+---
\ No newline at end of file
diff --git a/docs/performance assessment/06.md b/docs/performance assessment/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..340ddc8332a0e538bb2b8f545e55fa6872b80256
--- /dev/null
+++ b/docs/performance assessment/06.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+The system shall provide/enables reports showing the PAR (link accuracy and capture loss only) with associated KCS article reference.  These reports will be capable of segmentation by individual, team (designated by coach)
+
+##Practice/Technique##
+
+* Process Integration
+* KCS Process Integration Indicators
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.5: KCS Process Integration Indicators
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - KCS Process Integration Indicators
+---
\ No newline at end of file
diff --git a/docs/performance assessment/07.md b/docs/performance assessment/07.md
new file mode 100644
index 0000000000000000000000000000000000000000..0be54dad2d60984b7198ba64dab2d368a3d6b330
--- /dev/null
+++ b/docs/performance assessment/07.md	
@@ -0,0 +1,37 @@
+##Mandatory##
+
+The system shall provide reports showing how often KCS articles (mandatory) and other content types (non-mandatory) are linked to and from incidents. These reports will be capable of segmentation by date, knowledge domain (category, tag, or role.)
+
+1. Incidents and Content Attached
+2. KCS Articles and Incidents attached
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+
+##Reference: KCS v6 Practices Guide##
+Technique 3.3: Linking
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+---
\ No newline at end of file
diff --git a/docs/performance assessment/08.md b/docs/performance assessment/08.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2037de1ae86ef1ae32f176ad559ee871c310502
--- /dev/null
+++ b/docs/performance assessment/08.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+The system shall provide reports showing history of the KCS article and the individuals that have contributed over a particular period of time. These reports will be capable of segmentation by individual, team (group of users), date, and knowledge domain (category, tag, or role).
+
+##Practice/Technique##
+
+* Closing Thoughts on the Solve Loop
+* Collective Ownership in the Solve Loop
+
+##Reference: KCS v6 Practices Guide##
+Closing Thoughts on the Solve Loop
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Closing Thoughts on the Solve Loop
+  - Collective Ownership in the Solve Loop
+---
\ No newline at end of file
diff --git a/docs/performance assessment/09.md b/docs/performance assessment/09.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f3d12c7780e25b9d153fb9e0c1521d4f5b6aee5
--- /dev/null
+++ b/docs/performance assessment/09.md	
@@ -0,0 +1,36 @@
+##Not Mandatory##
+
+The system shall provide reports showing how often a KCS article was used as a reference over a particular period of time. These reports will be capable of segmentation by individual, team (group of users), knowledge domain (category, tag, or role), and date.
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Referencing or Linking to Other Information Sources
+
+##Reference: KCS v6 Practices Guide##
+Technique 3.3: Linking
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Referencing or Linking to Other Information Sources
+---
\ No newline at end of file
diff --git a/docs/performance assessment/10.md b/docs/performance assessment/10.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f70d1b863963bdbcd651b20bad80ba79985f857
--- /dev/null
+++ b/docs/performance assessment/10.md	
@@ -0,0 +1,40 @@
+##Mandatory##
+
+The system shall provide a report showing a graph of distribution of reuse counts for KCS articles over a particular period of time.These reports will be capable of segmentation by knowledge domain (category, tag, or role.), date, owner, creator
+
+##Practice/Technique##
+
+* Content Health
+* Knowledge Domain Analysis
+* Creating Evolve Loop Articles
+* Methods for Prioritizing Root Cause Analysis
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 5.9: Knowledge Domain Analysis](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/060)
+[Technique 5.4: Creating Evolve Loop Articles](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/042)
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Knowledge Domain Analysis
+  - Creating Evolve Loop Articles
+  - Methods for Prioritizing Root Cause Analysis
+---
\ No newline at end of file
diff --git a/docs/performance assessment/11.md b/docs/performance assessment/11.md
new file mode 100644
index 0000000000000000000000000000000000000000..cc7f2370ae019f3706ca2de9ce230e8139347461
--- /dev/null
+++ b/docs/performance assessment/11.md	
@@ -0,0 +1,46 @@
+##Mandatory##
+
+The system shall provide reports showing a Radar chart for an individual over a particular period of time that contains these mandatory elements:
+Content Standard Checklist
+Citations or Link Rate
+Contribution Index (old participation)
+Link Accuracy
+and optionally show:
+# of incidents
+Articles creation
+Articles modification
+Articles published
+These shall be normalized to a team average that is configurable.
+
+##Practice/Technique##
+
+* Performance Assessment
+* Assessing the Creation of Value
+* Radar Charts - Creating a Value Footprint
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.3: Assessing the Creation of Value
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Assessing the Creation of Value
+  - Radar Charts - Creating a Value Footprint
+---
\ No newline at end of file
diff --git a/docs/performance assessment/12.md b/docs/performance assessment/12.md
new file mode 100644
index 0000000000000000000000000000000000000000..46541934c82a4c6af6f9874743621c085ef3c6cd
--- /dev/null
+++ b/docs/performance assessment/12.md	
@@ -0,0 +1,43 @@
+##Mandatory##
+
+The system shall provide reports showing the following self-service metrics over a particular period of time.
+Search strings
+Articles viewed
+Feedback on articles
+Deflection/avoidance
+and optionally show:
+Abandoned search strings
+Empty search
+Search escalation
+These reports will be capable of segmentation by knowledge domain (category, tag, or role.), date/time, owner, creator
+
+##Practice/Technique##
+
+* Content Health
+* Self-Service Measures
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.12: Self-Service Measures
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Self-Service Measures
+---
\ No newline at end of file
diff --git a/docs/performance assessment/13.md b/docs/performance assessment/13.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c5f1dc3730f469fd98edc14d5d200969968b5d2
--- /dev/null
+++ b/docs/performance assessment/13.md	
@@ -0,0 +1,41 @@
+##Mandatory##
+
+The system shall provide reports showing the following article feedback.
+1. Feedback comments associated with article
+2. State of feedback
+3. Date feedback was created
+4. Turn around time processing turn around time, date of change of state
+
+
+##Practice/Technique##
+
+* Content Health
+* Self-Service Measures
+* Integrating Feedback
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.12: Self-Service Measures
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Self-Service Measures
+  - Integrating Feedback
+---
\ No newline at end of file
diff --git a/docs/performance assessment/14.md b/docs/performance assessment/14.md
new file mode 100644
index 0000000000000000000000000000000000000000..9411773a9a1007198bd4c5cccf3eaf13faab9547
--- /dev/null
+++ b/docs/performance assessment/14.md	
@@ -0,0 +1,38 @@
+##Mandatory##
+
+The system shall provide visibility management options that uses the user role, from user profiles, along with article quality, article confidence, article governance or other article attributes to determine visibility.  This visibility must at minimum be article level and ideally in-line or at the field or statement level.
+
+##Practice/Technique##
+
+* Content Health
+* KCS Article State
+* Performance Assessment
+* KCS Roles and the Licensing Model
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.12: Self-Service Measures
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - KCS Article State
+  - Performance Assessment
+  - KCS Roles and the Licensing Model
+---
\ No newline at end of file
diff --git a/docs/performance assessment/15.md b/docs/performance assessment/15.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9478bcf4471c33bc6eca3a7b64c6929c4a86e5b
--- /dev/null
+++ b/docs/performance assessment/15.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+KCS articles in each level of audience shall be searchable and visible to an appropriate KCS license level. For example, a KCS Contributor might have access to view all articles, a KCS Candidate might have access to view Non-Verified and Verified articles, and customer end-users might have access to only Verified/External articles.
+
+##Practice/Technique##
+
+* Performance Assessment
+* KCS Roles and the Licensing Model
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.1: KCS Roles and the Licensing Model
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - KCS Roles and the Licensing Model
+---
\ No newline at end of file
diff --git a/docs/performance assessment/16.md b/docs/performance assessment/16.md
new file mode 100644
index 0000000000000000000000000000000000000000..a698f66927c096d92bde9afe7f224871de1bad0e
--- /dev/null
+++ b/docs/performance assessment/16.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+KCS articles in each level of governance shall be editable to an appropriate KCS license level. For example, a KCS Contributor might have access to edit a Non-Validated Compliance Based article but only a small user group would be designated to edit Validated articles.
+
+##Practice/Technique##
+
+* Performance Assessment
+* KCS Roles and the Licensing Model
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.1: KCS Roles and the Licensing Model
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - KCS Roles and the Licensing Model
+---
\ No newline at end of file
diff --git a/docs/performance assessment/17.md b/docs/performance assessment/17.md
new file mode 100644
index 0000000000000000000000000000000000000000..78189586bbe58112eaa301be86107bd20576a021
--- /dev/null
+++ b/docs/performance assessment/17.md	
@@ -0,0 +1,34 @@
+##Mandatory/Not Mandatory##
+
+The Coach's focus should first be on evolving an individual's KCS skills, then, over time, shift to developing team capabilities. Although organizations recognize the need for training, they often overlook the need for coaching.
+
+##Practice/Technique##
+
+* Performance Assessment
+* Coaching
+
+##Reference: KCS v6 Practices Guide##
+Technique 7.2: Coaching for Success
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Performance Assessment
+  - Coaching
+---
\ No newline at end of file
diff --git a/docs/performance assessment/18.md b/docs/performance assessment/18.md
new file mode 100644
index 0000000000000000000000000000000000000000..5db61bf110184ee52d35d7435e7c11299780bea8
--- /dev/null
+++ b/docs/performance assessment/18.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Mechanism for integration of reporting tools. In documentation column list all possible export formats.
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/19.md b/docs/performance assessment/19.md
new file mode 100644
index 0000000000000000000000000000000000000000..4648513a07c575f2c51818b413c0b2ef6b5deccc
--- /dev/null
+++ b/docs/performance assessment/19.md	
@@ -0,0 +1,29 @@
+##Not Mandatory##
+
+Mechanism for storing article activity data.  Describe in documentation column.
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/20.md b/docs/performance assessment/20.md
new file mode 100644
index 0000000000000000000000000000000000000000..0bc9adb9668ad0465354f73561cdb6f29fac8759
--- /dev/null
+++ b/docs/performance assessment/20.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Data structure for articles/incidents, API and tools available.  Describe in documentation column.
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/21.md b/docs/performance assessment/21.md
new file mode 100644
index 0000000000000000000000000000000000000000..590b723789de8a38cdb7cbc1cfe79d30c8187d28
--- /dev/null
+++ b/docs/performance assessment/21.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Mechanism for performing Calculations. Describe in documentation column.
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/22.md b/docs/performance assessment/22.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b72be34eeda5c0d08a52d9aedc1b85a0ea69808
--- /dev/null
+++ b/docs/performance assessment/22.md	
@@ -0,0 +1,30 @@
+##Mandatory##
+
+Third party tools required for reporting (use documentation column)
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/23.md b/docs/performance assessment/23.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d59315e0b095387fdd21c9922e2fedeadc9c235
--- /dev/null
+++ b/docs/performance assessment/23.md	
@@ -0,0 +1,29 @@
+##Mandatory##
+
+Mechanism for grouping article activities, individual and group, distinguish between all contributors (define in documentation column how individual contribution is extracted, initial author, last modified, assigned owner, all historical contributors across versions.
+
+##Practice/Technique##
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/performance assessment/24.md b/docs/performance assessment/24.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c772cd0c885597810cb712652f4e1ee491cd215
--- /dev/null
+++ b/docs/performance assessment/24.md	
@@ -0,0 +1,39 @@
+##Mandatory##
+
+Report on the self-service experience and internal search effectiveness analysis on search success and effectiveness. (Could used Normalized Discounted Cumulative Gain.  Could use escalation
+reports, content gap analysis, null search reports, whether users
+selected search results, and where in the results list (Search Engine Result Page) the clicks
+ Happened)
+
+##Practice/Technique##
+
+* Content Health
+* Creating Evolve Loop Articles
+* Plugging Content Gaps Identified from the Web
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.4: Creating Evolve Loop Articles
+
+##Demo Requirements for Verified Only##
+Scenario 11
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Creating Evolve Loop Articles
+  - Plugging Content Gaps Identified from the Web
+---
\ No newline at end of file
diff --git a/docs/performance assessment/25.md b/docs/performance assessment/25.md
new file mode 100644
index 0000000000000000000000000000000000000000..301f6eb6ef83ae1a1cd2e0332ca8c7ade2253bfd
--- /dev/null
+++ b/docs/performance assessment/25.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+Report on passive failed search. Abandoned, ability to filter and trigger and the ability to report on.
+
+##Practice/Technique##
+
+* Content Health
+* Creating Evolve Loop Articles
+* Plugging Content Gaps Identified from the Web
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.4: Creating Evolve Loop Articles
+
+##Demo Requirements for Verified Only##
+Scenario 11
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Creating Evolve Loop Articles
+  - Plugging Content Gaps Identified from the Web
+---
\ No newline at end of file
diff --git a/docs/performance assessment/26.md b/docs/performance assessment/26.md
new file mode 100644
index 0000000000000000000000000000000000000000..08692fd17f1a8689b85b55847b6224e0da21f994
--- /dev/null
+++ b/docs/performance assessment/26.md	
@@ -0,0 +1,34 @@
+##Not Mandatory##
+
+Enable analytics in the evolve loop: for example (but not limited to) ability to identify common symptoms with different causes, common causes with different symptoms, patterns based on environment statements
+
+##Practice/Technique##
+
+* Content Health
+* Knowledge Domain Analysis
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.9: Knowledge Domain Analysis
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Knowledge Domain Analysis
+---
\ No newline at end of file
diff --git a/docs/process integration/01.md b/docs/process integration/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..abdb8e48a528d5c0b08ec2f930391451ea43fede
--- /dev/null
+++ b/docs/process integration/01.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+User interface and integrated workflow
+
+##Practice/Technique##
+
+* Process Integration
+* Seamless Technology Integration
+* Integration of Workflow and Technology with CRM, IM, and Other Tools
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.2: Seamless Technology Integration
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Seamless Technology Integration
+  - Integration of Workflow and Technology with CRM, IM, and Other Tools
+---
\ No newline at end of file
diff --git a/docs/process integration/02.md b/docs/process integration/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..167e2f602c6ccfe799db5e82cccf7dc684b06156
--- /dev/null
+++ b/docs/process integration/02.md	
@@ -0,0 +1,38 @@
+##Mandatory##
+
+Meta Data Management – Ability to use metadata to change the ranking, filtering, and relevance of search results.  Metadata can include:
+(1) A predefined list of attributes (e.g., ontologies or taxonomies)
+(2) a flexible undefined field (e.g., textual title or description)
+(3) Crowd sourced lists (e.g., tags)
+(4) System-generated metadata (e.g., reuse counts)
+
+##Practice/Technique##
+
+* Process Integration
+* Search Technology for KCS
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology for KCS
+---
\ No newline at end of file
diff --git a/docs/process integration/03.md b/docs/process integration/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..36d71b2cb69aea2722ab945ddeb03c11e96c5651
--- /dev/null
+++ b/docs/process integration/03.md	
@@ -0,0 +1,34 @@
+##Not Mandatory##
+
+Describe the capabilities for personalization to audiences, known individuals, or contexts
+
+##Practice/Technique##
+
+* Process Integration
+* Search Technology for KCS
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology for KCS
+---
\ No newline at end of file
diff --git a/docs/process integration/04.md b/docs/process integration/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c5fb5f39c10ee5e963b6e444dd89efe08d3c882
--- /dev/null
+++ b/docs/process integration/04.md	
@@ -0,0 +1,34 @@
+##Not Mandatory##
+
+Aggregated Search – Access to content repositories with relevant content outside the knowledge base, using approaches such as spidering / crawling of external content repositories, or federating of external search systems
+
+##Practice/Technique##
+
+* Process Integration
+*  Technology for KCS
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology for KCS
+---
\ No newline at end of file
diff --git a/docs/process integration/05.md b/docs/process integration/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..287a26bdbf31a18b8e401f2f35d68566d0c3b7ae
--- /dev/null
+++ b/docs/process integration/05.md	
@@ -0,0 +1,34 @@
+##Mandatory##
+
+Describe the search capabilities and how they return relevant results, appropriately ranked, to analyst and customer.  Examples include: stemming, lemmatization, tagging, concept matching, user intent, machine learning, consensus tagging, autocomplete/typeahead, autosuggest, spelling correction, "did you mean," relevance ranking, search cases, multi-contextual sensitivity
+
+##Practice/Technique##
+
+* Process Integration
+* Search Technology for KCS
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology for KCS
+---
\ No newline at end of file
diff --git a/docs/process integration/06.md b/docs/process integration/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..5cab81c00b30da8031559861cad71e4a9fea4423
--- /dev/null
+++ b/docs/process integration/06.md	
@@ -0,0 +1,37 @@
+##Mandatory##
+
+The system shall provide the ability to perform search tuning. Describe the mechanism for search tuning (machine learning, user interface, or no interface.   In addition to listing the technical features describe the process and the strategy you recommend for ongoing tuning.
+For example, by maintaining dictionaries / acronym / synonym lists, taxonomies and ontologies, keywords, "best bets" / "Directed Documents".  Describe the strategy for random sampling of content or queries.
+
+##Practice/Technique##
+
+* Process Integration
+* Search Technology of KCS
+* Planning for the Ongoing Effort of Search Tuning
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology of KCS
+  - Planning for the Ongoing Effort of Search Tuning
+---
\ No newline at end of file
diff --git a/docs/process integration/07.md b/docs/process integration/07.md
new file mode 100644
index 0000000000000000000000000000000000000000..761bbc99185e492f490b8d1c25f48e47e23edc69
--- /dev/null
+++ b/docs/process integration/07.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide the ability for real time indexing (searchable and findable) for intended audience , less than 5 min. for internal knowledge workers, less than 90 minutes for authenticated external customers.  System shall provide indexing for external web content content (indexed by Google, Bing etc.)
+
+##Practice/Technique##
+
+* Process Integration
+* Search Technology of KCS
+* Planning for the Ongoing Effort of Search Tuning
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.3: Search Technology for KCS
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Search Technology of KCS
+  - Planning for the Ongoing Effort of Search Tuning
+---
\ No newline at end of file
diff --git a/docs/process integration/08.md b/docs/process integration/08.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba883ac6439d72fa3ac2a87bd73e97b54f2988b0
--- /dev/null
+++ b/docs/process integration/08.md	
@@ -0,0 +1,34 @@
+##Not Mandatory##
+
+Describe your process for publishing content to the web and SEO.
+1. xml site map
+2. htaccess for redirects
+3. canonical urls (nicely formatted)
+4. meta attributes
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+---
\ No newline at end of file
diff --git a/docs/process integration/09.md b/docs/process integration/09.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ea85c79ddc2a3dd828ce8bc0a428a9d67f4fb07
--- /dev/null
+++ b/docs/process integration/09.md	
@@ -0,0 +1,34 @@
+##Not Mandatory##
+
+Administrators can adjust KCS Article structured such that the search engine can apply different weights by field, include/exclude fields in the search
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.1: KCS Article Structure
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/process integration/10.md b/docs/process integration/10.md
new file mode 100644
index 0000000000000000000000000000000000000000..180125c35055f69f337bdbf13f56b7e729a0a541
--- /dev/null
+++ b/docs/process integration/10.md	
@@ -0,0 +1,36 @@
+##Not Mandatory##
+
+The system shall extend this navigation or browsing experience to external (non knowledge base) content indexed by the system
+
+##Practice/Technique##
+
+* Content Health
+* Self-Service Success
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 5.11: Self-Service Success
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Self-Service Success
+
+---
\ No newline at end of file
diff --git a/docs/process integration/11.md b/docs/process integration/11.md
new file mode 100644
index 0000000000000000000000000000000000000000..14b9f27e90fa54d8c3bad021dc9d926741703b4b
--- /dev/null
+++ b/docs/process integration/11.md	
@@ -0,0 +1,36 @@
+##Mandatory##
+
+The system shall provide an integrated search and navigation experience, where a user can start with a search and further refine (navigate) based on metadata tags, or can initiate a search that is restricted to a particular part of a browse tree.
+
+##Practice/Technique##
+
+* Process Integration
+* Seamless Technology Integration
+
+
+##Reference: KCS v6 Practices Guide##
+Technique 6.2: Seamless Technology Integration
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Process Integration
+  - Seamless Technology Integration
+
+---
\ No newline at end of file
diff --git a/docs/reuse/01.md b/docs/reuse/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ea52c6fe3f7caba9ce39232dd25c9771ed90240
--- /dev/null
+++ b/docs/reuse/01.md
@@ -0,0 +1,41 @@
+##Not Mandatory##
+
+Content from other sources (user community, discussion forums, etc.) be added to the knowledge base or within the tools, what content types are supported.
+3 Approaches:
+1. Single source content authored in KB tool.  (mandatory)
+2.  Same index applied to external sources (ie. .pdf, .docs, external via API) master source resides outside of KB (non-mandatory)
+3. Federated search (non-mandatory)
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Linking an Incident to Non-KCS Content
+
+##Reference: KCS v6 Practices Guide##
+
+[Linking to Non-KCS Content](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030#Linking_to_non-KCS_content)
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Linking an Incident to Non-KCS Content
+---
\ No newline at end of file
diff --git a/docs/reuse/02.md b/docs/reuse/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..b53470016e4279ef90d69d5938a2020b912d25f1
--- /dev/null
+++ b/docs/reuse/02.md
@@ -0,0 +1,26 @@
+##Mandatory##
+
+The system shall support the provisioning of internal (inside the firewall) and external (outside the firewall, or in a DMZ) access to a single logical knowledge base.  Changes to the master knowledge base will be reflected appropriately in each end-user’s experience.
+
+##Practice/Technique##
+
+
+##Reference: KCS v6 Practices Guide##
+
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
diff --git a/docs/reuse/03.md b/docs/reuse/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..13338767680cf9c064e90b51449319384f49ce15
--- /dev/null
+++ b/docs/reuse/03.md
@@ -0,0 +1,37 @@
+##Not Mandatory##
+
+The system shall provide a mechanism to distinguish a reference link from a resolution/fix link. (This can be done through meta-data and shall have capability to be reported on.)
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Referencing and Linking to Other Information Sources
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Referencing and Linking to Other Information Sources
+---
\ No newline at end of file
diff --git a/docs/reuse/04.md b/docs/reuse/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..7013b8d9fca86343d65f690276728de9fb487dc6
--- /dev/null
+++ b/docs/reuse/04.md
@@ -0,0 +1,37 @@
+##Mandatory##
+
+The linking mechanism shall be structured such that each article may be linked to multiple incidents, and each incident may link to multiple articles. These links shall be implemented in such a way to be available to other processes - e.g. reporting, search, ranking algorithms, search results display.  (In other words, as an example, a link embedded in an unstructured text field as part of an incident note would generally not satisfy this requirement.)
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Many-to-Many Relationship Between Incidents and Articles
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+Scenario 3
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Many-to-Many Relationship Between Incidents and Articles
+---
\ No newline at end of file
diff --git a/docs/reuse/05.md b/docs/reuse/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..0debdeae72c4dd4d7f8c7909a1821410307edcc8
--- /dev/null
+++ b/docs/reuse/05.md
@@ -0,0 +1,37 @@
+##Mandatory##
+
+Links shall be capable of being deleted by the analyst.
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Linking to an existing KCS Article
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+Scenario 3
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Linking to an existing KCS Article
+---
\ No newline at end of file
diff --git a/docs/reuse/06.md b/docs/reuse/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a9fd7899b967e81b8b817be320115db154a3f86
--- /dev/null
+++ b/docs/reuse/06.md
@@ -0,0 +1,37 @@
+##Not Mandatory##
+
+Linking incident to other types of content that solve the issue. These links shall be implemented in such a way to be available to other processes - e.g. reporting, search, ranking algorithms, search results display. Enables more than KCS articles counted in reuse counts, link rates and known vs new.
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Referencing and Linking to Other Information Sources
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+Scenario 9
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Referencing and Linking to Other Information Sources
+---
\ No newline at end of file
diff --git a/docs/reuse/07.md b/docs/reuse/07.md
new file mode 100644
index 0000000000000000000000000000000000000000..0744c3e5dc35351595de5b05d282cbe715ecfa8e
--- /dev/null
+++ b/docs/reuse/07.md
@@ -0,0 +1,37 @@
+##Mandatory##
+
+The linking mechanism shall allow the analyst viewing the incident to see both the current version of any linked KCS article and the version of the article at the time it was delivered to the customer in the incident workflow.
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Managing Article Versions
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+Scenario 10
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Managing Article Versions
+---
\ No newline at end of file
diff --git a/docs/solve/structure/referencing.md b/docs/solve/structure/referencing.md
deleted file mode 100644
index 943ca51ea2c9db3c93214798df8f4979cd5b25c0..0000000000000000000000000000000000000000
--- a/docs/solve/structure/referencing.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-Referencing and Linking to Other Information Sources
-
-##Mandatory##
-KCS articles can have embedded hyperlinks to other sources of content, such as KCS articles, or content addressable by a URL.
-
-##Out Of the Box##
-Open Knowledge uses the CKEditor WYSIWYG. It supports anchor tags and renders them correctly when viewing the article.
-
-Additionally, other KCS articles are linked in the article, are displayed on the right sidebar. Other articles, that link to our article, are also displayed in the right sidebar
-
-Also, all urls, http or https, including other articles, are listed below the article under the label 'References'
-
-###Linked articles###
-Links to other articles
-
-###Linked URLs###
-
-
-
-##Configuration##
-The fields of the article to scan for articles/urls is configurable. The content type(s) to accept is configurable. The linked content, and/or linked urls can be removed or added to each content type.
-
-The two view block in the sidebar can be configured, like any other view block.
-
-##Customization##
-
-No new hooks or events are provided by Open Knowledge, related to the linked content, and linked urls.  There are core hooks, and the field(s) can have a custom formatter, like another other field. Field widgets are not used, the links are automatically extracted from the article.
-
-
-
-##References##
-[3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030%22,%22Technique)
diff --git a/docs/structure/01.md b/docs/structure/01.md
new file mode 100644
index 0000000000000000000000000000000000000000..3dd764e5cef34fa821e25c2b78f872eb6373d2a1
--- /dev/null
+++ b/docs/structure/01.md
@@ -0,0 +1,41 @@
+##Mandatory##
+
+A  KCS article template that includes the following fields:
+* Issue
+* Environment
+* Resolution
+* Cause
+* Comments and Notes (Feedback from users)
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.1: Use a Simple Template](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/010)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/structure/02.md b/docs/structure/02.md
new file mode 100644
index 0000000000000000000000000000000000000000..36167f7878575cf5106e1d299d188d8f5a175c34
--- /dev/null
+++ b/docs/structure/02.md
@@ -0,0 +1,36 @@
+##Mandatory##
+
+Issue can be captured in the workflow in a template that helps to structure the content.
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.1: Use a Simple Template](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/010)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/structure/03.md b/docs/structure/03.md
new file mode 100644
index 0000000000000000000000000000000000000000..e63c7fcca3f5cad0d9a55f84c5afd0d5e1e47838
--- /dev/null
+++ b/docs/structure/03.md
@@ -0,0 +1,37 @@
+##Not Mandatory##
+
+Template structure of the Article is not alterable by the user when creating or editing an article
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.1: Use a Simple Template](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/010)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/structure/04.md b/docs/structure/04.md
new file mode 100644
index 0000000000000000000000000000000000000000..174c082fa4582d884c72ffbe6b82b5c4c2dd36f3
--- /dev/null
+++ b/docs/structure/04.md
@@ -0,0 +1,36 @@
+##Mandatory##
+
+Administrators may specify or adjust which fields are being present in any given template and multiple templates may be maintained.
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.1: Use a Simple Template](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/010)
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/structure/05.md b/docs/structure/05.md
new file mode 100644
index 0000000000000000000000000000000000000000..abc711e1ffad99d7a6db112076cb15ce1a75dba6
--- /dev/null
+++ b/docs/structure/05.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+At KCS Article capture, user may select which template they use, although a default may be maintained.
+
+##Practice/Technique##
+
+* Structure
+* Utilize Simple Templates
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.1: Use a Simple Template](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/010)
+
+##Demo Requirements for Verified Only##
+Scenario 7
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Structure
+  - Utilize Simple Templates
+---
\ No newline at end of file
diff --git a/docs/structure/06.md b/docs/structure/06.md
new file mode 100644
index 0000000000000000000000000000000000000000..91c89a3c3255245370d67e84cce9406c9c4f505a
--- /dev/null
+++ b/docs/structure/06.md
@@ -0,0 +1,35 @@
+##Not Mandatory##
+
+Visibility of content can be managed at the field level of the article based on the role and/or entitlement of the person looking at the article
+
+##Practice/Technique##
+
+* Structure
+* Details on the Resolution Field
+
+##Reference: KCS v6 Practices Guide##
+
+Technique 5.1: KCS Article Structure
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Structure
+  - Details on the Resolution Field
+---
\ No newline at end of file
diff --git a/docs/structure/07.md b/docs/structure/07.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d8782aa3b1382bb95eab5a1b9deb38a44122cf6
--- /dev/null
+++ b/docs/structure/07.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+Captured KCS Article content from initial entry will support at least basic formatting, including preservation of breaks.  No arbitrary limit on the length of template sections will be imposed.
+
+##Practice/Technique##
+
+* Structure
+* Complete Thoughts, Not Complete Sentences
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.2: Complete Thoughts, Not Complete Sentences](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/020)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Structure
+  - Complete Thoughts, Not Complete Sentences
+---
\ No newline at end of file
diff --git a/docs/structure/08.md b/docs/structure/08.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce5944aae03094a9aa57d71b1571ab3c80f4178a
--- /dev/null
+++ b/docs/structure/08.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+KCS Articles can be entered and edited as bullet lists and numbered lists.
+
+##Practice/Technique##
+
+* Structure
+* Complete Thoughts, Not Complete Sentences
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 2.2: Complete Thoughts, Not Complete Sentences](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/020/020)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Structure
+  - Complete Thoughts, Not Complete Sentences
+---
\ No newline at end of file
diff --git a/docs/structure/09.md b/docs/structure/09.md
new file mode 100644
index 0000000000000000000000000000000000000000..39af7820b6e1064e45128fe6652e1e269702ae98
--- /dev/null
+++ b/docs/structure/09.md
@@ -0,0 +1,37 @@
+##Mandatory##
+
+KCS articles can have embedded hyperlinks to other sources of content, such as KCS articles, or content addressable by a URL.
+
+##Practice/Technique##
+
+* Reuse
+* Linking
+* Referencing and Linking to Other Information Sources
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 3.3: Linking](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/030/030/030)
+
+##Demo Requirements for Verified Only##
+Scenario 1
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Reuse
+  - Linking
+  - Referencing and Linking to Other Information Sources
+---
\ No newline at end of file
diff --git a/docs/structure/10.md b/docs/structure/10.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c2fcf67e7b1e0088e50d999935564fb4fcfa587
--- /dev/null
+++ b/docs/structure/10.md
@@ -0,0 +1,35 @@
+##Mandatory##
+
+Describe your strategy for supporting locale-specific or multilingual content, including support for translation workflow or machine translation. List supported languages and restrictions associated with specific languages, if any.  Example: Include double-byte languages and right-to-left languages. Is a master-slave relationship between translated documents supported? Must there be a single master language, or can content in any language be the"master" for a given article.
+
+##Practice/Technique##
+
+* Content Health
+* Global Support Considerations
+
+##Reference: KCS v6 Practices Guide##
+
+[Technique 5.8: Global Support Considerations](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/030/040/010/055)
+
+##Demo Requirements for Verified Only##
+
+
+##OB/Config/Cust/NS/SF##
+
+
+##Native Product Capability##
+
+##Mechanism for Config##
+
+##Config Strategy##
+
+##Dependencies & Version Numbers##
+
+
+##Documentation##
+
+---
+tags:
+  - Content Health
+  - Global Support Considerations
+---
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index b2252e89dfca27e13659d4371ba7e9253bfa724a..872d9e11d1a4871427c71db7f281fd8f40783b79 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -11,15 +11,98 @@ theme:
 
 nav:
   - Home: index.md
-  - Solve:
-      - Structure:
-          - Referencing: solve/structure/referencing.md
+  - Capture:
+      - Integration: capture/01 integration.md
+      - Context: capture/02 context.md
+      - Relevant: capture/03 relevant.md
+  - Structure:
+      - '01': structure/01.md
+      - '02': structure/02.md
+      - '03': structure/03.md
+      - '04': structure/04.md
+      - '05': structure/05.md
+      - '06': structure/06.md
+      - '07': structure/07.md
+      - '08': structure/08.md
+      - '09': structure/09.md
+      - '10': structure/10.md
+  - Reuse:
+      - '01': reuse/01.md
+      - '02': reuse/02.md
+      - '03': reuse/03.md
+      - '04': reuse/04.md
+      - '05': reuse/05.md
+      - '06': reuse/06.md
+      - '07': reuse/07.md
+  - Improve:
+      - '01': improve/01.md
+      - '02': improve/02.md
+      - '03': improve/03.md
+      - '04': improve/04.md
+      - '05': improve/05.md
+      - '06': improve/06.md
+  - Content Health:
+      - '01': content health/01.md
+      - '02': content health/02.md
+      - '03': content health/03.md
+      - '04': content health/04.md
+      - '05': content health/05.md
+      - '06': content health/06.md
+      - '07': content health/07.md
+      - '08': content health/08.md
+      - '09': content health/09.md
+      - '10': content health/10.md
+      - '11': content health/11.md
+      - '12': content health/12.md
+      - '13': content health/13.md
+      - '14': content health/14.md
+  - Process Integration:
+      - '01': process integration/01.md
+      - '02': process integration/02.md
+      - '03': process integration/03.md
+      - '04': process integration/04.md
+      - '05': process integration/05.md
+      - '06': process integration/06.md
+      - '07': process integration/07.md
+      - '08': process integration/08.md
+      - '09': process integration/09.md
+      - '10': process integration/10.md
+      - '11': process integration/11.md
+  - Performance Assessment:
+      - '01': performance assessment/01.md
+      - '02': performance assessment/02.md
+      - '03': performance assessment/03.md
+      - '04': performance assessment/04.md
+      - '05': performance assessment/05.md
+      - '06': performance assessment/06.md
+      - '07': performance assessment/07.md
+      - '08': performance assessment/08.md
+      - '09': performance assessment/09.md
+      - '10': performance assessment/10.md
+      - '11': performance assessment/11.md
+      - '12': performance assessment/12.md
+      - '13': performance assessment/13.md
+      - '14': performance assessment/14.md
+      - '15': performance assessment/15.md
+      - '16': performance assessment/16.md
+      - '17': performance assessment/17.md
+      - '18': performance assessment/18.md
+      - '19': performance assessment/19.md
+      - '20': performance assessment/20.md
+      - '21': performance assessment/21.md
+      - '22': performance assessment/22.md
+      - '23': performance assessment/23.md
+      - '24': performance assessment/24.md
+      - '25': performance assessment/25.md
+      - '26': performance assessment/26.md
+
   - Tags: tags.md
 
 plugins:
   - search
   - tags:
       tags_file: tags.md
+      enabled: true
 
 repo_url: https://git.drupalcode.org/project/open_knowledge
 copyright: Copyright &copy; 2020 - 2025 Steven Ayers<br/>KCS® is a service mark of the Consortium for Service InnovationTM. Open Knowledge is not certified by the Consortium for Service Innovation.