Table of Contents

Project Name	Enter the name of the project
Target Release Name	KohnLondon
Project Lifecycle State	Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company	AT&T, Nokia, Wipro, Huawei, ChinaTelecomDT, ESTCapgemini

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R11 is on followingR12

Address DCAE transformation carry-over items
- Common Template Enhancement for dcaegen2-services-common (For support for dynamic configuration update via ConfigMap)
- DR Feed configuration cleanup
- Bug fixes for MOD/Helm-gen (log.path setting override)
DCAE backlog reduction
Support TSC approved ONAP Usecases and Features (details below)
Address SECCOM identified vulnerability*
Alignment with TSC/SECCOM Global requirements & TSCTSC/SECCOM Best Practice
OpenSSF Best Practice progression (target Gold badging)
SBOM Report integration with CI and validation*
*
Continue AAF certificate dependency removal (by making it a configurable property)
Microservice enhancements in support for ONAP usecases/features
- SliceAnalysis Ms (under E2E Slicing/IBN/CCVPN), SON-Handler (5G SON)
Enable automated static-check code review/scan with CI/verify job
Improving code coverage across all DCAE components
DCAE backlog reduction

Kohn Usecases with DCAE impact

for SVC mesh compaibility)*
Code coverage improvements*

(* - Stretchgoals)

London Usecases with DCAE impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-12151378 - E2E Network Slicing use case enhancements for Kohn London release	YES	AI/ML MS for IBN based closed Loop in E2E Network Slicing • Mainstreaming the ml-prediction-ms(New mS introduction) • Support for multiple slices (sNSSAIs) in training and prediction modules • Use CPS instead of Config DB • Remove RAN Simulator dependency Commitment from Kevin Tang sendil kumar Jaya kumar Ahila P /WIPRO	DCAEGEN2-3067
REQ-1212 5G SON use case enhancements for Kohn release	YES	CL message for ANR created by SON-Handler MS to be modified to align with A1-based flow/support Commitment from WIPRO	DCAEGEN2-3148
REQ-1268 - CCVPN Kohn Enhancements for Intent-based Cloud Leased Line and Transport Slicing	YES	DCAE SDK alignment for SliceAnalysis MS & enhanching AAI interface for supporting IBN CL Commitment from HUAWEI/ChinaTelecom	DCAEGEN2-3195

Kohn Features with DCAE Impact

...

REQ-1214 Maintenance and Enhancement of Intent-driven Closed-loop Autonomous Networks in R11

...

Slice Analysis enhancement

Enhancement with AAI Interface/processing for CL notification

Commitment from HUAWEI/ChinaTelecom

...

DCAEGEN2-3194

...

REQ-1207 DMaaP Enhancements for K release

...

Impact on DCAE components for migrating from exiting MR clients to use kafka native towards the strimzi cluster.

Dependent on resource availability

Commitment from EST

...

London Features with DCAE Impact

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1351 - External secure communication only via Ingress	NO	No resource/support available from DCAE project; changes likely in OOM charts.
REQ-1349 - Removal of AAF	Stretch-goal	OOM-3068 (DCAE Svc template updates) - Jack Lucas DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf cert dependency removal) - Kedar Ambekar DCAEGEN2-3335 - VESOpenAPI -	DCAEGEN2-3037 (EPIC) - Story DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf) DCAEGEN2-3335 - VESOpenAPI
REQ-1376 - DMaaP Enhancements for L release	NO	DMAAP BC removal support BC used mainly for BulkPM flow for Feed provisioning - need assessment on switching DFC/PM-Mapper to use non-secure endpoints.

London Spec with DCAE Impact

...

Best Practices/GLOBAL Requirements

REQ#DCAE Commit StatusDCAE Impact AssesmentDCAE JIRA #

REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL

Global-REQ

YES

CII badging score improvement

Commitment from AT&T

DCAEGEN2-3209

REQ-1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES

Global-REQ

YES

Kohn DCAE (SECCOM)

Commitment: AT&T, Wipro, HUAWEI, ChinaTelecom, Nokia

DCAEGEN2-3196

REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8)

Global-REQDCAEGEN2-3037

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
DCAE Helm Transformation - Post migration activities	YES	Complete the post-migration updates. Commitment from AT&T	DCAEGEN2-3119
NA	YES	VES 7.2.1 support for DCAE Microservices (outside of collectors) - TCAgen2 Commitment from Wipro	DCAEGEN2-2975
NA	Stretch-goal	AAF certificate dependency to be removed by making it a configurable property for MS DFC, RESTConf Stretch goals: Nokia for DCAEGEN2-3039 (DFC), Huawei for DCAEGEN2-3095 (RESTConf)	REQ-1379 - Improve DCAE PRH to handle Early PNF Registrations	YES	Enable persistence for PRH reprocessesing DCAE SDK dmaap-client enhancement to support native kafka interface Commitment from Sangeeta Bellara / DT	DCAEGEN2-3312
DCAE MOD retirement	YES	Retire MOD from ONAP/DCAE OOM charts updates Documentation Commitment from Vijay Kumar / AT&T	DCAEGEN2-3278
PM-Mapper Improvement/Bug-fixes	YES	Fix issues of duplicate events handling & DR retry Commitment from Viresh Navalli / Vamshi Namilikonda Capgemini	DCAEGEN2-3315 DCAEGEN2-3313
NA	YES	Sonarcoverage improvements for DCAE components SliceAnalysis mS, SNMPTrap, TCA-gen2, SON-Handler,DL-Handler, KPi-MS, VES-HV, VESCollector, MOD/onboardingAPI, SDK, Mapper, RESTConf, MOD/genprocessor, MOD/distributorapi Commitment from AT&T, Wipro, HUAWEI, ChinaTelecom, Nokia (* stretch-goal) Heartbeat MS, VESCollector Commitment from Vijay Kumar Tony Hansen AT&T	Sub-Jira under EPIC EPIC DCAEGEN2-30893256
NA	YES	Automated review tool integration with CI/verify Commitment from AT&T	DCAEGEN2-3186
NA	YES	Enhancements to KPI Computation MS Support KPI to be defined spanning multiple resources Handle unavailability of required counter for calculation Commitment from Wipro	DCAEGEN2-3193 (sub-task to DCAEGEN2-2801)
REQ-358	Stretch-Goal	No root (superuser) access to database from application container TCAgen2 Commitment from Wipro	DCAEGEN2-2907
NA	YES	DMAAP SDK standardization for DCAE Microservices SliceAnalysis mS KPI-mS SON-Handler mS RESTConf* Commitment from Huawei, Wipro	DCAEGEN2-3030

Kohn POC (DCAE impact)

...

Pending Assessment	DMAAP SDK standardization for DCAE Microservices (following components are using cambria client) KPI-mS (deferred from Kohn; need to be confirmed by Ahila P / Niranjana Y ) SON-Handler mS (deferred from Kohn; need to be confirmed by Ahila P / Niranjana Y ) RESTConf (No resouce/support available from DCAE project)	DCAEGEN2-3030

London POC (DCAE impact)

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1072 - Standardized logging fields Image AddedREQ-1345 - Standardized logging fields - Python London release	NO	No resources for POC	NA

Best Practices/GLOBAL Requirements

New mS (ml-prediction-mS) will be complaint to the requirement. All other DCAE mS area already complaint STDOUT logging

Commitment from Wipro

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL Global-REQ	YES	DCAE passed silver badging; Gold badging improvements dependent on LF wide policy/infra updates. (No new impact for DCAE)	NA
REQ-439/REQ-1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ	Stretch-goal	London DCAE DCAE Wiki - DCAE R12 London Vulnerability - SECCOM Report Commitment: Kedar Ambekar / DT Team (TCAGEN2/RESTConf/PM-Mapper, DataFileCollector, VESMapper, SDK, VES-OpenAPI manager) SliceAnalysis - Shuting Qing SON-handler - Shuting Qing Following are OPEN (pending resource/commitment) PRH - Sangeeta Bellara	DCAEGEN2-3318
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) Global-REQ	YES	Existing DCAE python components are already compliant; New mS (ml-prediction-mS) will also meet this requirement when delivered. Covered under REQ-1378 (Commitment from Kevin Tang Ahila P /WIPRO )	NA
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ	YES	Complaint with DCAEMOD deprecation. Java17 upgrade pilot targetted for PM-Mapper in London (supported by Kedar Ambekar/DT Team)	NA
REQ-432/REQ-760 - IPv4/IPv6 dual stack support in ONAP	YES	Enhance ONAP common-service template - add IPv4/IPv6 support (No new impact for DCAE)	OOM-2749
REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - London RELEASE Global-REQ	YES	New mS (ml-prediction-mS) will be complaint to the requirement. All other DCAE mS area already complaint STDOUT logging Covered under REQ-1378 (Commitment from Kevin Tang Ahila P /WIPRO )	Tracked under DCAEGEN2-3067
REQ-1073 - Using basic image from Integration	YES	(No new impact for DCAE in Kohn London release)	DCAEGEN2-3196
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ	No	dcaemod-designtool dcaemod-nifi-registry Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency	DCAEGEN2-3019 (J)
REQ-432 - IPv4/IPv6 dual stack support in ONAP	YES	Enhance ONAP common-service template - add IPv4/IPv6 support (No new impact for DCAE in Kohn release)	OOM-2749
REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - KOHN RELEASE Global-REQ	YES	Tracked under DCAEGEN2-3067
REQ-1073 - Using basic image from Integration	YES	(No new impact for DCAE in Kohn release)	NA
REQ-1072 - Standardized logging fields	YES (for new Ms only)	No change planned for existing DCAE microservice. New mS (ml-prediction-mS) will be developed to be complaint to this Best-practice requirement. Commitment from Wipro	Tracked under DCAEGEN2-3067	NA
REQ-1072 - Standardized logging fields REQ-1341 - Standardized logging fields - Java London release	NO	Will need updates to several DCAE java component - no resource (only vescollector updates committed by AT&T)	DCAEGEN2-3257
REQ-1342 - Retirement of unmaintained repos	YES	DCAE MOD will be retired in London release Commitment from Vijay Kumar / AT&T	DCAEGEN2-3278

Best Practices

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-396 - Clearly split ONAP code and use case code	YES	No new impact; already compliant	NA
REQ-399 - ONAP Projects dealing with GUI must provide GUI test suites	NO	DL Admin is only DCAE component with UI No resource/commitment	NA
REQ-1073 - Using basic image from Integration	YES	No new impact; already compliant	NA
REQ-1346 - Software BOMs	YES	No new impact; already compliant	NA

Note: The above commitment should be consistent with Kohn London Impact View per Component at M2.

New Services/Components

...

ML MS (REQ-1215)
- Repository : https://git.onap.org/dcaegen2/services/tree/components/ml-prediction-ms(introduced as new subproject under existing repo)

Retirement/Deprecation

Acumos Adapter

DCAE MOD under assessment for EOL with London release

DCAE MOD was introduced in Frankfurt release to address following requirements:

...

Platform Maturity (i.e., S3P items) Kohn London Release Platform Maturity

Green color → Target level ( details see Platform Maturity below)

Performance: Level 1
Stability: Level 2
Resiliency: Level 2
Security: Level 1+
Scalability: Level 1
Manageability: Level 1+
Usability: Level 1+

...

Helm Deployment (dcaegen2-services)

- VESCollector
- TCA-gen2
- PRH
- HV_VES

DCAE-MOD deployment is optional and will include following component (controlled via helm chart configuration under OOM)

- Genprocessor
- MOD/NiFI UI
- Distributorapi
- Runtimeapi
- Onboardingapi

...

- PRH
- HV_VES

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = dcaegen2 and issuetype in (epic) and fixversion='Kohn Release' DCAEGEN2 AND fixVersion = "London Release" AND type = Epic AND status not in (Closed) AND labels not in (relman)
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=dcaegen2 and issuetype in (story) and fixversion = 'Kohn Release' AND fixVersion = "London Release" AND status not in (Closed) AND labels not in (relman)
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

- Policy/CLAMP: Continue integration for Control Loop design for Helm-based deployment of DCAE Services*Assess DCAEMOD platform continued support/retirement
- Prometheus Integration
- TICK/ELK Integration

...

Deliverable Name	Deliverable Description
Component spec	All ms added into DCAE should provide meta data representation of the component itself; will be used to generate design flow under MOD and enable blueprint generation
configbinding	SourceCode/Docker image
policy side-car	SourceCode/Docker image
dcae-healthcheck	SourceCode/Docker image
dcae-mod	SourceCode/jar/Docker image/Documentation
VES Collector	SourceCode/Docker image/helm charts
HV_VES Collector	SourceCode/jar/Docker image/helm charts
PRH	SourceCode/jar/Docker image/helm charts
TCA-GEN2	SourceCode/jar/Docker image/helm charts
DFC	SourceCode/Docker image/helm charts
RESTConf	SourceCode/Docker image/helm charts
PM-MAPPER	SourceCode/Docker image/helm charts
VES-MAPPER	SourceCode/Docker image/helm charts
DL Components (DES, DL-ADMIN, DL-FEEDER)	SourceCode/Docker image/helm charts
SLICE ANALYSIS	SourceCode/Docker image/helm charts
KPI-MS	SourceCode/Docker image/helm charts
HEARTBEAT MS	SourceCode/Docker image/helm charts
SON-HANDLER MS	SourceCode/Docker image/helm charts
PMSH	SourceCode/Docker image/helm charts
ML/Prediction Ms	SourceCode/Docker image/helm charts

...

Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.

Image RemovedImage Added

DCAE Interfaces

Image RemovedImage Added

Platform Maturity

Kohn London Release Platform Maturity

...

Area	Actual Level	Targeted Level for current Release	Comments
Performance	1	1	Level 0: no performance testing done Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component) Level 2: performance improvement plan created Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
Stability	2	2	Level 0: none beyond release requirements Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load) Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load) Level 3: track record over 6 months of reduced defect rate
Resiliency	2	2	0 – none 1 – manual failure and recovery (< 30 minutes) 2 – automated detection and recovery (single site) 3 – automated detection and recovery (geo redundancy)
Security	1	1+	Level 0: None Level 1: CII Passing badge Including no critical and high known vulnerabilities > 60 days old Level 2: CII Silver badge, plus: All internal/external system communications shall be able to be encrypted. All internal/external service calls shall have common role-based access control and authorization using CADI framework. Level 3: CII Gold badge
Scalability	1	1	Level 0: no ability to scale Level 1: supports single site horizontal scale out and scale in, independent of other components Level 2: supports geographic scaling, independent of other components Level 3: support scaling (interoperability) across multiple ONAP instances
Manageability	1	1+ (Except logging, all other requirements are met)	Level 1: All ONAP components will use a single logging system. Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint Level 2: A component can be independently upgraded without impacting operation interacting components Component configuration to be externalized in a common fashion across ONAP projects All application logging to adhere to ONAP Application Logging Specification v1.2 Implement guidelines for a minimal container footprint Level 3 Transaction tracing across components
Usability	1	1+	Level 1: User guide created Deployment documentation API documentation Adherence to coding guidelines Level 2: API Documentation All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines All existing APIs must be documented in Swagger 2.0 Level 3 Consistent UI across ONAP projects Usability testing conducted API Documentation All new API’s, all external APIs, and all existing API’s that are modified must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines Level 4 API Documentation All API’s for a given project must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines

...

List the API this project is expecting from other projects. Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)
VES Collector	API for VNFs to send VES data	Currently Available		No change for this release
Healthcheck	API for querying DCAE component healthcheck	Currently Available	R4	No change for this release	DCAE Onboarding API	API for publishing DCAE spec into MOD	Currently Available	R6R4	No change for this release
Data Extraction Service (DES)	API for data retrieval and simple computation from DL-Handler maintained storages (For R8, this will be used by DCAE components such Slice-Analyis MS) and UUI	Currently Available	R8	No change for this release
PMSH	API support for Subscription/Filters/Measurement group management	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/pmsh_swagger.json
SliceAnalysis Ms	API support for data aggregation based on NSI/NSSI; this will be consumed by OOF	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/swagger_slice_analysis.json https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/11774039616493831/slice-analysis-swagger.yaml?version=1&modificationDate=1640159785000&api=v2

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected. List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

Name	Description	Version
NIFI	Apache NIFI	1.9.x
Consul	version based on OOM

In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.

Testing and Integration Plans
- - Unit Test addition will be enforced part of new code submission; all components are required to maintain 55% codecoverage at the minumum.
    https://sonarcloud.io/organizations/onap/projects?search=dcaegen2
  - Functional test plan
    DCAE R12 London Testplan
  - CSIT tests will continue to be supported for existing components and new components
    DCAE has number of CSIT - https://jenkins.onap.org/view/CSIT/; these will be continued to be validated during course of development for this release.
  - Pairwise testing will be done in the WindRiver Dev lab; below wiki page captures the test planned
    DCAE R12 London Pairwise Test
  - DCAE also has number of Smoke test (Example - https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/01-18-2021_08-01/) enabled for several components/flows; these test are validated part of gating for new container releases
    Bulk-PM
    HV-VES
    VES
    PRH flow
    MOD

Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release. List identified release gaps (if any), and its impact.

...

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

...

Request exception for SECCOM.

Assess migration to use new MOD2 standalone components for onboarding (based on community resource/support)

MOD retirement under assessment

...

materialized (contingency).

Risk identified	Mitigation Plan	Contingency Plan
Documented under London Risks

Resources

Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae

...

The milestones are defined at the Release Planning: KohnLondon and all the supporting project agreed to comply with these dates.

...

Date to be completed by	Sprint	Deliverable
Key dates for KOHN London release - Release Planning: KohnLondon
M2	DCAE Kohn London Sprint 1 (Planning)	Finalize DCAE scope and committment API definition formalized and shared with impacted teams
M2-M3	DCAE Kohn London Sprint 2 (Development)	50% or more of Functional delivery completed Atleast 60% of release/compliance (coverage & security) Integration test plan completed CSIT/automated test delivery SDK version to be baselined and released Documentation repo updates (API updates & new MS/component) - Kohn London Documentation
M3	DCAE Kohn London Sprint 3 (Code Freeze)	All code intended for release MUST be submitted into gerrit Minimum 80% code coverage 100% of release/compliance (Global Requirement & Best-Practice) Validate deployment/integration with ONAP/DCAE deploy Update OOM chart/documentation to reflect correct version Documentation update for deployment/configuration/architecture/logging
M4	DCAE Kohn London Sprint 4 (Container Release/artifact)	Finalize containers/jars for release and submit patch to OOM for revisions
RC	Integration/Sign-Off	Fix Integration blockers and high priorty issue Demo for new components introduced Pair-wise testing Branching

Documentation, Training
- - Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  - Highlight the team contributions to the overall Release Documentation and training asset
  - High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  - Documentation includes items such as:
    Installation instructions
    Configuration instructions
    Developer guide
    End User guide
    Admin guide

Kohn London Documentation

Other Information

...

Versions Compared

Old Version 2

New Version Current

Key

Scope

What is this release trying to address?

Release Focus

Kohn Usecases with DCAE impact

London Usecases with DCAE impact

Kohn Features with DCAE Impact

London Features with DCAE Impact

London Spec with DCAE Impact

Best Practices/GLOBAL Requirements

Kohn POC (DCAE impact)

London POC (DCAE impact)

Best Practices/GLOBAL Requirements

Best Practices

New Services/Components

Retirement/Deprecation

Functionalities

DCAE Interfaces

Platform Maturity

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Resources

Documentation, Training

Other Information

Page Comparison

Versions Compared

Old Version 2

New Version Current

Key

Scope

What is this release trying to address?

Release Focus

Kohn Usecases with DCAE impact

London Usecases with DCAE impact

Kohn Features with DCAE Impact

London Features with DCAE Impact

London Spec with DCAE Impact

Best Practices/GLOBAL Requirements

Kohn POC (DCAE impact)

London POC (DCAE impact)

Best Practices/GLOBAL Requirements

Best Practices

New Services/Components

Retirement/Deprecation

Functionalities

DCAE Interfaces

Platform Maturity

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Resources

Documentation, Training

Other Information