SLA

Author: agile-lab

README.md

@@ -40,7 +40,11 @@ The fixed structure must be technology-agnostic. The first fields of teh fixed s
 * `Email: [Option[String]]` point of contact between consumers and maintainers of the Data Product. It could be the owner or a distribution list, but must be reliable and responsive.
 * `OwnerGroup [String]`: LDAP user/group that is owning the data product.
 * `DevGroup [String]`: LDAP user/group that is in charge to develop and maintain the data product.
-* `InformationSLA: [Option[String]]` describes what SLA the Data Product team is providing to answer additional information requests about the Data Product itself.
+* `SupportSLA: [Option[String]]` describes what SLA the Data Product team is providing when some support is needed.
+  * `SupportHours: [Option[String]]` define when the suport is available. Ex During working days from 9 to 18
+  * `ResponseTime: [Option[String]]` define the amount of time needed to take care of an incoming feature
+  * `ResolutionTime: [Option[String]]` define the amount of time needed to fix the date
+  * `InformationTime: [Option[String]]` define the amount of time needed to answer clarification questions.
 * `Status: [Option[String]]` this is an enum representing the status of this version of the Data Product. Allowed values are: `[Draft|Published|Retired]`. This is a metadata that communicates the overall status of the Data Product but is not reflected to the actual deployment status.
 * `Maturity: [Option[String]]` this is an enum to let the consumer understand if it is a tactical solution or not. It is really useful during migration from Data Warehouse or Data Lake. Allowed values are: `[Tactical|Strategic]`.
 * `Billing: [Option[Yaml]]` this is a free form key-value area where is possible to put information useful for resource tagging and billing.
@@ -94,18 +98,18 @@ Constraints:
     * `IntervalOfChange: [Option[String]]` how often changes in the data are reflected.
     * `Timeliness: [Option[String]]` the skew between the time that a business fact occurs and when it becomes visibile in the data.
     * `UpTime: [Option[String]]` the percentage of port availability.
-  * `TermsAndConditions: [Option[String]]` If the data is usable only in specific environments.
   * `Endpoint: [Option[URL]]` this is the API endpoint that self-describe the output port and provide insightful information at runtime about the physical location of the data, the protocol must be used, etc.
-  * `biTempBusinessTs: [Option[String]]` name of the field representing the business timestamp, as per the "bi-temporality" definition; it should match with a field in the related `Schema`
-  * `biTempWriteTs: [Option[String]]` name of the field representing the technical (write) timestamp, as per the "bi-temporality" definition; it should match with a field in the related `Schema`
-* `DataSharingAgreement: [Yaml]` This part is covering usage, privacy, purpose, limitations and is independent by the data contract.
-  * `Purpose: [Option[String]]` what is the goal of this data set.
-  * `Billing: [Option[String]]` how a consumer will be charged back when it consumes this output port.
-  * `Security: [Option[String]]` additional information related to security aspects, like restrictions, masking, sensibile information and privacy.
-  * `IntendedUsage: [Option[String]]` any other information needed by the consumer in order to effectively consume the data, it could be related to technical stuff (e.g. extract no more than one year of data for good performances ) or to business domains (e.g. this data is only useful in the marketing domains).
-  * `Limitations: [Option[String]]` If any limitation is present it must be made super clear to the consumers.
-  * `LifeCycle: [Option[String]]` Describe how the data will be historicized and how and when it will be deleted.
-  * `Confidentiality: [Option[String]]` Describe what a consumer should do to keep the information confidential, how to process and store it. Permission to share or report it.
+  * `DataSharingAgreement: [Yaml]` This part is covering usage, privacy, purpose, limitations and is independent by the data contract.
+    * `TermsAndConditions: [Option[String]]` If the data is usable only in specific environments.
+    * `Purpose: [Option[String]]` what is the goal of this data set.
+    * `Billing: [Option[String]]` how a consumer will be charged back when it consumes this output port.
+    * `Security: [Option[String]]` additional information related to security aspects, like restrictions, masking, sensibile information and privacy.
+    * `IntendedUsage: [Option[String]]` any other information needed by the consumer in order to effectively consume the data, it could be related to technical stuff (e.g. extract no more than one year of data for good performances ) or to business domains (e.g. this data is only useful in the marketing domains).
+    * `Limitations: [Option[String]]` If any limitation is present it must be made super clear to the consumers.
+    * `LifeCycle: [Option[String]]` Describe how the data will be historicized and how and when it will be deleted.
+    * `Confidentiality: [Option[String]]` Describe what a consumer should do to keep the information confidential, how to process and store it. Permission to share or report it.
+* `biTempBusinessTs: [Option[String]]` name of the field representing the business timestamp, as per the "bi-temporality" definition; it should match with a field in the related `Schema`
+* `biTempWriteTs: [Option[String]]` name of the field representing the technical (write) timestamp, as per the "bi-temporality" definition; it should match with a field in the related `Schema`
 * `Tags: [Array[Yaml]]` Tag labels at OutputPort level, here we can have security classification for example (please refer to [OpenMetadata documentation](https://docs.open-metadata.org/v1.0.0/main-concepts/metadata-standard/schemas/type/taglabel)).
 * `SampleData: [Option[Yaml]]` provides a sample data of your Output Port (please refer to [OpenMetadata specification](https://docs.open-metadata.org/v1.0.0/main-concepts/metadata-standard/schemas/entity/data/table#properties)).
 * `SemanticLinking: [Option[Yaml]]` here we can express semantic relationships between this output port and other outputports (also coming from other domains and data products). For example, we could say that column "customerId" of our SQL Output Port references the column "id" of the SQL Output Port of the "Customer" Data Product.

data-product-specification.cue

@@ -58,14 +58,13 @@ import "strings"
     upTime?:           string | null
     ...
   }
-  termsAndConditions?: string | null
   endpoint?:           #URL | null
-  biTempBusinessTs?:   string | null
-  biTempWriteTs?:      string | null
+  dataSharingAgreement: #DataSharingAgreement
   ...
 }
 
 #DataSharingAgreement: {
+  termsAndConditions?: string | null
   purpose?:         string | null
   billing?:         string | null
   security?:        string | null
@@ -93,9 +92,11 @@ import "strings"
   retentionTime?:       string | null
   processDescription?:  string | null
   dataContract:         #DataContract
-  dataSharingAgreement: #DataSharingAgreement
+  biTempBusinessTs?:   string | null
+  biTempWriteTs?:      string | null
   tags: [... #OM_Tag]
   sampleData?:      #OM_TableData | null
+  sampleQuery?:      string | null
   semanticLinking?: {...} | null
   specific: {...}
   ...
@@ -190,7 +191,12 @@ dataProductOwnerDisplayName: string
 devGroup:                    string
 ownerGroup:                  string
 email?:                      string | null
-informationSLA?:             string | null
+supportSLA: {
+  supportHours:             string | null
+  responseTime:             string | null
+  resolutionTime:           string | null
+  informationTime:          string | null
+}
 status?:                     string & =~"(?i)^(draft|published|retired)$" | null
 maturity?:                   string & =~"(?i)^(tactical|strategic)$" | null
 billing?:                    {...} | null

example.yaml

@@ -13,7 +13,11 @@ ownerGroup: dataproduct1_corp.com
 devGroup: dataproduct1_dev_corp.com
 ownerGroup: dataproduct1_corp.com
 devGroup: dataproduct1_dev_corp.com
-informationSLA: 2WD
+supportSLA:
+  supportHours: 8x5
+  responseTime: 1H
+  resolutionTime: undefined
+  informationTime: 2WD
 status: DRAFT
 maturity: Strategic
 billing: {}
@@ -64,16 +68,17 @@ components:
         intervalOfChange: 1 hours
         timeliness: 1 minutes 
         upTime: 99.9%
-      termsAndConditions: only usable in development environment
+      
       endpoint: https://myurl/development/my_domain/my_data_product/1.0.0/my_raw_s3_port
-    dataSharingAgreements:
-      purpose: this output port want to provide a rich set of profitability KPIs related to the customer
-      billing: 5$ for each full scan
-      security: In order to consume this output port an additional security check with compliance must be done
-      intendedUsage: the dataset is huge so it is recommended to extract maximum 1 year of data and to use these KPIs in the marketing or sales domain, but not for customer care
-      limitations: is not possible to use this data without a compliance check
-      lifeCycle: the maximum retention is 10 years, and eviction is happening on the first of january
-      confidentiality: if you want to store this data somewhere else, PII columns must be masked    
+      dataSharingAgreements:
+        termsAndConditions: only usable in development environment
+        purpose: this output port want to provide a rich set of profitability KPIs related to the customer
+        billing: 5$ for each full scan
+        security: In order to consume this output port an additional security check with compliance must be done
+        intendedUsage: the dataset is huge so it is recommended to extract maximum 1 year of data and to use these KPIs in the marketing or sales domain, but not for customer care
+        limitations: is not possible to use this data without a compliance check
+        lifeCycle: the maximum retention is 10 years, and eviction is happening on the first of january
+        confidentiality: if you want to store this data somewhere else, PII columns must be masked    
     tags:
       - tagFQN: experimental
         source: Tag
@@ -84,6 +89,7 @@ components:
         labelType: Manual
         state: Confirmed
     sampleData: {}
+    sampleQuery: select * from dp.table 
     semanticLinking: {}
     specific:
       directory: history