All control automation should be done on VNFs stood up in the operator’s cloud as well as on the CPE

Priorities:

Functional Platform Requirements	Priority	Basic/stretch goal Default basic goal	Related components
PNFs configuration	1		SDNC,
Traffic scheduling	3	stretch	PCE, DCAE, SDNC, A&AI
Overlay selection	1		Portal, SDC, SO
VNF onboarding	1
Service Design	1
Service Composition	1
Network Provisioning	1
Deployment automation	1
Termination automation	1
Policy driven/optimal VNF placement	3
Performance monitoring and analysis	2
Resource dedication	3
Control Loops	2
Capacity based scaling	3
Triggered Healthcheck	2
Health monitoring and analysis	2
Data collection	2
Data Analysis	2
Policy based healing	3
Policy based scaling	2
Configuration audit	3
Multi Cloud Support	2
Framework for integration with OSS/BSS	3
Framework for integration with vendor provided VNFM(if needed)	1
Framework for integration with external controller	1

Project Impact:

Modeling
The enterprise gateway will typically implement a proprietary VIM. Modeling will need to be added to describe how VNFs are to be instantiated, removed, healed (restart, rebuild), how statistics are gathered, how events are received
SDC SDC
Add logic to use the new modeling when designing the service, and then distribute the resulting artifacts
SO
Add logic to understand the new artifacts; orchestrate/manage changes according to it
SDNC
Add logic to issue the proper commands to the CPE to support instantiation, chaining, configuration, healing, etc.
DCAE
Support statistics collection on the CPE and receipt of events as per the new model
APPC/VF-C and DCAE
Support more complex control loops
SO or SDNC
Monitor the CPE to verify the all VNFs and chaining have been executed, and update A&AI. Is more granular information needed? (e.g. on which vServer each VNF is stood up)
A&AI
Support the new data model
Policy
Support new policy related to the connectivity to the CPE

...