diff --git a/aws/documentation/naming-tagging-standard/tags/ops.md b/aws/documentation/naming-tagging-standard/tags/ops.md
index 30c0be73..33c46f31 100644
--- a/aws/documentation/naming-tagging-standard/tags/ops.md
+++ b/aws/documentation/naming-tagging-standard/tags/ops.md
@@ -10,7 +10,7 @@ The following tags are to be applied to resources which support tagging.
 
 | Tag key               | Status   |
 |-----------------------|----------|
-| ops_support | Required for EC2 |
+| [ops_contact](#ops_contact) | Required for EC2 |
 
 # Applicability
 
@@ -45,7 +45,9 @@ be tagged accordingly.
 
 # Tags
 
-## ops_support
+## ops_contact
+
+This supercedes `ops_support`.
 
 This is `REQUIRED` for these resources:
 
@@ -59,11 +61,26 @@ ALB, etc.).
 
 ### Format
 
-The tag name is all lowercase, and *must* be set to `ops_support`.
+The tag name is all lowercase, and *must* be set to `ops_contact`.
 
 ### Values
 
-These values will come from the _{business-label}_ from the [base label format](../README.md#base-label-format). The value
+This is a multi-part value, consisting of sub key/value pairs separated by spaces.  Currently, two are defined
+
+* ops
+* apps
+
+Not we explicitly exclude an `email` sub-key due to complexity in maintaining the value across many resources.  Instead, we defer
+to an Atrium entry for tracking such information, consistent with how this is done with on-prem VMware.
+
+This takes the format as:
+
+```
+ops/{operational_business-label} apps/{application_business-label}
+
+```
+
+These values will come from the _{business-label}_ from the [base label format](../README.md#base-label-format). The `ops` key's value
 will mostly be set to `csvd`, but cases exist where other groups are possible.  Examples include:
 
 * dice
@@ -84,22 +101,8 @@ The following tags in the original proposal will not be moving forward:
 such as [here](https://github.e.it.census.gov/terraform/cloud-information/blob/master/aws/info/ACCOUNTS.md)
 * ops_division | ops_organization
   * This is replaced with `ops_support`
-
-## ops_contact
-
-Supercedes `ops_support`
-
-### Format
-
-```
-ops/{operational_division} app/{application_division}
-```
-
-OR
-
-```
-{"ops":"{operational_division}","app":"{application_division}"}
-```
+* ops_support
+  * This is replaced with consolidated values of `ops` and `apps` into ops_contact
 
 # CHANGELOG