...
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case)The use case is fundamental for supporting efficiently business agreements between the operator and the vendor.
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
SUPPORTING FILES:
View file | ||||
---|---|---|---|---|
|
Use Case Contacts & Team
DEVELOPMENT IMPACTS
There is no expected Software Impact to any of the ONAP platform components for this Use Case, aside from possibly modeling and architecture work.
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |||
AAF | |||
APPC | |||
CLAMP | |||
CC-SDK | |||
DCAE | |||
DMaaP | |||
External API | |||
MODELING | Epic #1: Introduction of basic Licensing Modeling | Modeling for Licensing Management (Kevin Scaggs ) | |
Multi-VIM / Cloud | |||
OOF | Shankaranarayanan Puzhavakath Narayanan | ||
POLICY | |||
PORTAL | |||
SDN-C | |||
SDC | |||
SO | |||
VID | |||
VNFRQTS | |||
VNF-SDK | |||
CDS |
...