ACTION WEEK ROUNDUP

DEREK FLEXER

FEBRUARY 25, 2019

Page 2 of 33

Table of Contents Introduction ............................................................................................................................................................................ 3

Open Digital Architecture (ODA) ............................................................................................................................................ 4

AI & Data Analytics/Data Management ................................................................................................................................ 10

Open APIs .............................................................................................................................................................................. 14

Customer Centricity .............................................................................................................................................................. 19

Frameworx ............................................................................................................................................................................ 21

Internet of Everything and Digital Ecosystems ..................................................................................................................... 24

Business Assurance ............................................................................................................................................................... 28

Catalysts ................................................................................................................................................................................ 30

Page 3 of 33

Introduction

The sun shone brightly as we assembled in Cascais near Lisbon, Portugal, for TM Forum Action Week from Monday 11th to Friday 15th of February 2019. There were 176 attendees from 74 companies travelling from 30 different countries spanning the world. 40% of the attendees were representing 21 unique CSP companies. Here a group of smart, hard-working and passionate members from every corner of the globe gathered to collectively address the biggest issues communications service providers (CSPs) are facing – including developing global solutions to 5G management challenges. Attendees from CSPs like AT&T, China Mobile, Orange, Telefónica, Telstra, Verizon and Vodafone sat down with representatives from vendors such as Amdocs, Ericsson, Huawei, Netcracker and Nokia to work out how best to handle everything from revenue assurance to platform business models and 5G network slicing. The week was a mix of inspirational keynotes, workshops and case studies, focusing on the “how” of making the leap to be a truly digital operator and unlocking value beyond connectivity. Throughout this collaborative working event, attendees explored the big issues facing the industry and had a chance to influence industry-wide change, focusing on the decisions to be made and how to achieve the objectives needed to shape the future of the industry. The presentations from Monday’s keynote sessions are posted on the Agenda-at-a-glance page here: https://actionweek.tmforum.org/agenda/ To get a flavor of the event, here are links to four Inform articles relating to Action Week:

• 5G and AI take center stage at Action Week

• CSPs must embrace platforms and APIs to survive, says DTs Campbell McClean

• How can CSPs unlock 70% of growth potential when it requires radical transformation?

• TM Forum members develop code to test ODA concepts

Page 4 of 33

Open Digital Architecture (ODA) ODA sets a new vision for operational and business support systems (OSS/BSS), and a de facto standard for the design of open digital platforms. ODA embraces fresh ideas and the latest thinking, with the ambition to deliver a model-driven and data-driven architecture that relies on the use of metadata, microservices and a clear set of normalized APIs. ODA offers an industry-agreed blueprint, language and set of key design principles to follow. It will provide pragmatic pathways for the journey from maintaining monolithic, legacy software solutions, towards managing nimble, cloud-based capabilities that can be orchestrated using AI. It is a reference architecture that maps TM Forum’s Open APIs against technical and business platform functions. To read the latest white paper on ODA, see: https://www.tmforum.org/resources/whitepapers/open-digital-architecture/

If you are not already a project member, you may join the ODA project (in the ‘Core Project Area’)

here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=603731cf-09c5-4229-8730-

c900c157c07b&CommunityKey=0430eebd-2dac-41b6-bd1b-fba7ebcfe7d7

Members wishing to get involved in the ODA project may access the working area on the project

Wiki, Confluence, here:

https://projects.tmforum.org/wiki/display/ODA/Open+Digital+Architecture+Project+Home

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/display/ODA/Lisbon+TAW+2019+Meeting+Notes

And working calls here:

https://projects.tmforum.org/wiki/display/ODA/Meeting+Notes

Summary of ODA Sessions at Action Week: MEETING TITLE: Development of TM Forum’s Open Digital Architecture (ODA); The Core Commerce Management Pioneer project and the construction of a reference implementation – the Business Operating System (BOS) (JOINT: API) OBJECTIVE: Within TM Forum, at the request of members, we have initiated a program to build a reference implementation of the core commerce management functions that make up the Open Digital Architecture (ODA). Its aim is to address the level of agility we need in a 5G world. A reference implementation would drive ODA standards in the ‘build then standardize’ approach adopted by hyperscale web companies, as well as providing a common reference for interoperability testing. We are running a Core Commerce Management Pioneer Project to further develop the architecture for ODA so that reference implementations of the architecture can be built and demonstrated. This involved identifying the sub-components of the Core Commerce layer and the associated APIs, which will enable a “plug and play” approach to the interoperability testing of such functions as product catalogue, product ordering, customer asset creation or billing. Our plan is to then use the Catalyst program to develop several proof of concepts (PoC). One PoC called the Business Operating System (BOS) is looking at generating code to implement the solution (either contributed or open source). We are investigating an approach to a reference implementation where only the relevant APIs are exposed, and the internal code of the component remains the IPR of the contributor. For the various PoC to work there will probably have to be a mix of both contributed code,

stubs of components to maintain the e2e referential integrity of the data model and components exposed via APIs. When there is an open reference implementation of the Core Commerce part of the ODA architecture, COTS or SaaS vendors could demonstrate inter-operability as part of their core product offering. The long RFP procurement cycles

Page 5 of 33

would be reduced since both CSPs and vendors would have a reference model describing the functional scope, data mastership and Open-API services available for each component in the reference architecture. Systems Integrators would be able to focus on value-added innovation, instead of their effort being consumed in making oddly-shaped pieces of a puzzle fit together. At this session in Action week, we will have an update on the overall Core Commerce Management Pioneer project as well as updates on Catalysts that are underway to construct the reference implementations.

OUTCOME: This was a very well attended session were the BOS Pioneer Project was introduced to the audience. For several participants in the audience this was their first exposure to BOS, so it was important to quickly bring them up to speed to allow them to participate effectively in the rest of the week. Several of the members who have participated in the project actively over the last four months offered their observations and mentioned areas they thought were of key importance.

MEETING TITLE: Newcomers Introduction to the ODA Project OBJECTIVE: To welcome newcomers to the ODA project and provide an overview of the project workstreams, topics and deliverables via the document roadmap.

OUTCOME: This session was designed to introduce ODA to members not familiar with the work. The slides were developed to both introduce the key ODA topics and provide links to all the current ODA documents, work in progress and contributions. This was also an opportunity for the Team Leads of the ODA workstreams to explain the goals of their working sessions during the week to allow members to plan the most effective use of their time.

MEETING TITLE: Business Operating System (BOS) Reference Implementation Project OBJECTIVE: To present an overview of the BOS architecture and review the components and APIs required for the implementation.

OUTCOME: This session was a technical dive into the details of the BOS Pioneer Project proposed Catalyst. The initial architecture, process flows and use cases were presented and discussed. A lively discussion on certain technical assumptions the Catalyst team was making occurred regarding the cardinality of the relationship between Product Order and CFS. The overall concept of a Reference Implementation at the Core Commerce block was also discussed as it might entail the group having to agree at the implementation level, certain details that are classically left optional.

MEETING TITLE: ODA Engagement Management OBJECTIVE: Better define and illustrate, at a functional level, the coverage of Engagement Management.

OUTCOME: Orange shared some initial thinking regarding the interaction between the Engagement Management Functional block and the other ODA blocks. The use case was driven primarily by the same scenarios driving the BOS Catalyst. Several key concepts and principles about the Engagement Management Block were reviewed i.e. there will be no process flow or business functionality in the Engagement Management block. As this work progresses in Release 19.0 additional usage scenarios will be built out to illustrate the interaction of the Engagement Management Block and the other ODA blocks.

MEETING TITLE: 5G Business Models & Technologies (JOINT: IoE (EBA)) OBJECTIVE: Align work in the Ecosystems Business Architecture team with ODA Service & Resource Management.

OUTCOME: Content-packed session with questions raised regarding the scope of 5G impacts on revenue assurance; monetizing 5G is about how to utilize 5G in supporting cost reduction and selling new products and services; do we treat 5G the same as 3G and 4G in deployment, selling of 5G, selling of speed or do we sell a whole new experience? 2018 & 2019 Catalysts demonstrated the new experience that could be sold; in the Tour de France drone experience and to emergency response and remote surgery use cases; with the uncertainty of demand, there is a concept for a multi-layered business model that would support a concept of value-added

Page 6 of 33

connectivity on demand. Need to compile the 5G use cases in an easy way for analysis of business models and impact assessments.

MEETING TITLE: ODA Production Best practice guide (with NaaS Connectivity Service and 5G examples) OBJECTIVE: Enhance GB999 based on Catalyst (incl. KL) to be an ODA Production Best practice using connectivity services and 5G as exemplars.

OUTCOME: Yuval Stein of TEOCO provided an overview of the progress on GB999 User Guide for Network Slicing which was based on the analysis of four 5G Catalysts and two NaaS Catalysts in 2018. The large number of contributions were overviewed, and it was explained in which session each contribution would be reviewed. Several modelling related items were deferred to discussion on Thursday Q1 and Q2. GB999 has resulted in the analysis of 5G Catalyst use cases the production of a candidate ODA Production Implementation Framework which is more general than 5G, and a detailed proposal for a simple (intelligent) Connectivity Services model (discussed Thursday Q1). ODA-125 put the case for dividing the Current GB999 into multiple parts, some addressing the general ODA Production Implementation Model and some addressing 5G Specifics.

Several errata have been identified in ODA-125 which will be addressed as Jira requests by the team. Two additional changes identified are to pull out specifically the E2E service management at the top of ODA production and the need to introduce lifecycle management function i.e., something like a service or software factory.

MEETING TITLE: Zero Touch Partnering (ZTP) OBJECTIVE: Zero Touch Partnering is about establishing a suite of APIs and methods for working which will support partner integration across a diverse range of service types and suit the needs of all service providers. Zero Touch in essence means Zero IT development and if our industry of Communications and Digital Service Providers can adopt this approach then there are a number of possibilities which may be realized:

1. A service provider may on-board and integrate with a myriad of different service suppliers with very low effort. 2. Marketplaces will form, facilitated by zero code interworking 3. New innovation will find it simpler to get to market

This session will discuss the following: 1. Requirements for ZTP 2. What has been proven through the Catalyst program to date 3. Scope of ZTP and implementation phases 4. Relationship to TM Forum initiatives

OUTCOME: Greg Tilton of DGIT shared detailed technical findings of a Catalyst effort his team has been engaged in during several Catalyst cycles. Specific recommendations for changes and enhancement to several APIs were explained and plans for entry of JIRA change requests shared. There was a very detailed exchange of ideas around the proposed changes and several items were taken away for further study and clarification. Greg also shared plans for the next phase of the Catalyst and additional participants were solicited.

MEETING TITLE: Continued Evolution of the ODA Component (JOINT: Frameworx) OBJECTIVE: Recap of the work in IG1171 & consider suggested additional data types: Configuration data, Referenced data, Transaction data, Variable Data & Metadata.

Page 7 of 33

OUTCOME: The session was an important exposure of the ODA Component for ODA and BOS. It emphasized the interaction of the group's output. It seems that the ODA component work is to be viewed as a pattern and guidelines for the real implementation of ODA. Immediate collaboration can be greatly beneficial.

MEETING TITLE: Mapping of ODA to Frameworks (JOINT: Frameworx) OBJECTIVE: Clearly describe and share business coverage of each functional block of ODA architecture, at business process and business information levels. These mappings are a pre-requisite to functional frameworks and Open API’s mappings.

OUTCOME: Sylvie Demarest of Orange shared a prepared contribution with the group that explained the ODA Functional Architecture team's approach to mapping and the guidelines they had established to do the mapping in an objective a repeatable way. Sylvie also shared with the group where gaps and inconsistencies had been discovered in the existing Frameworx and plans to create change requests to the appropriate framework to effect the necessary changes. Additional contributions were solicited especially around Engagement and Intelligence Management.

This session was an important coordination session. The Frameworx group was updated on current suggestions for new Frameworx artifacts based on the ODA to Frameworx mapping. Also, the Frameworx team presented two items that explore the relationship between the structure of Frameworx and the Functional Architecture of the ODA. The session was another reminder that both artifacts are part of the future Open Digital Framework. Additional contributions were solicited especially around Engagement and Intelligence Management.

MEETING TITLE: Ecosystem Business Concepts Mappings (JOINT: IoE (EBA)) OBJECTIVE: Mapping of ecosystem business concepts to the ODA Functional Architecture.

OUTCOME: Great contributions and discussions during this joint meeting that resulted in actions to further align the work done on the ODA and EBA Concepts & Principles (GB998 & GB1000) and enhance the concepts by including the introduction of new ecosystem roles, incorporate branding and automotive use cases and referencing existing work to the different models described in TR211. An overview of past work related to managing service lifecycle across domains was presented.

MEETING TITLE: ODA & Open APIs (JOINT: API) OBJECTIVE: Explore the implications of ODA developments on the Open APIs and the implications of recent Open API developments on the ODA program.

OUTCOME: This discussion centered specifically on the usage scenario of the BOS Pioneer Project Catalyst effort and the new requirements for APIs between the Core Commerce Block and Engagement Management. A proposal for a new "Process API" was shared with the team. A very lively discussion ensued, and several clarifications and alternative approaches were discussed. Several action items were established to help clarify the intent of the API and when it would be appropriate to use. However, the consensus was that the proposed work should proceed.

MEETING TITLE: NaaS Connectivity Service Models (UML & NaaS API Data Models) (JOINT: Frameworx (SID)) OBJECTIVE: Update of GB999 Connectivity Services Data Model and improve alignment with SID Logical Resource, NaaS APIs ONF MEF Models and simplification with respect to 3GPP Network Slice/Communication Service. May need additional documents to create an ODA NaaS Connectivity Services ‘Product’ within GB999.

OUTCOME: The meeting reviewed all the incoming 10 contributions. Time precluded detailed review as there was only 9 minutes per contribution. The areas covered were:

• The 5G NaaS Connectivity Service requirements established in the 5G Catalysts and GB999 User Guide for Network Slicing.

Page 8 of 33

• Additional requirements arising as we change scope from 5G Catalyst to ODA Production particularly input from EU 5G-VINNI ODP-148 and Microsoft Edge Computing ODA-137 and NTT Connectivity requirements for 5G ODA-130 .

• Review of current SID models and capabilities around Service, Resource function, Function and Features. • Modelling issues ODA-126 - ODA Production modelling challenges/issues - 5G focus were reviewed.

Conclusions were that there are best practices needed to describe how to model NaaS connectivity services in the SID and possible adjustments to the Service and Logical Resource models to support 5G CFS models based on features.

Agreed to further review contributions on Joint ODA/SID calls but may need to move the current meeting time Tuesday 11:00 GMT forward to accommodate participation by Japan and Australia. The priority issue being around Service, Resource and Functions.

Participants will review the six issues in ODA-126 with a view to creating a definitive team response. MEETING TITLE: Model Driven Automation Blueprint (lifecycle and operations management) OBJECTIVE: Document how ODA implements Model Driven Automation – may be a multi-part ODA ‘Product”. Extend the work of TOSCA-based model-driven automation and IG1141 considering both commercial and technical onboarding (addressed initially in R18.5) and the integration with the runtime implementation in a hybrid physical and virtualized environment.

OUTCOME: Contribution ODA-119 - Mapping SID to TOSCA for onboarding resources on using TOSCA' models the metadata of resources such as a Router was reviewed and the patterns for mapping from SID based resources to TOSCA templates were discussed in depth. Several extensions to TOSCA and SID were identified e.g. Component. The approach in ODA-119 has the potential to create common metadata for onboarding and operating any resource/ software that can be represented in the SID in a common way using TOSCA. The example used is a router. Noted by NTT that TOSCA could also be used for modelling connectivity services. Agreed to validate and cross review, on a retimed weekly call: the NTT TOSCA proposal for legacy and new network communication services with the ODA-119 proposal for modelling Physical related devices.

MEETING TITLE: ODA Security and Privacy OBJECTIVE: Create best practice guidelines for ODA Security and Privacy re-using prior work in the API program and TR263D (covering requirements, architecture, mapping to API solutions and policy with examples).

OUTCOME: Reviewed contributions on current telecom challenges, current TM Forum Security and Privacy assets and identified gaps and threats. Recognizing the importance of this topic, the team considered where in the IG1167 ODA Vision lifecycle we should focus. The conclusion was to focus on the Information Systems Architecture (ISA) carrying out a Security Privacy Audit of the ODA Functional Architecture and the security process used to go from the ODA Functional Architecture to the ODA Implementation viewpoint. For other ODA vision architecture viewpoints, we probably could reference other industry activities. It was noted that API security, whilst necessary, was not the focus for this initial work. Proposal is that we scope up these activities for a 2-day face-to-face workshop.

MEETING TITLE: ODA Use Case Development (JOINT: AI/DA, CEM) OBJECTIVE: To extend the series of User Stories and Use Cases for the ODA and align with AI/DA and CEM Use Cases.

OUTCOME: Sylvie Demarest of Orange opened the session by presenting a set of three user stories relating to the Open Digital Architecture (ODA) - Inbound Marketing; Event-Based Marketing; Offer & Product Catalog Marketing. Each user story was illustrated by aspects of the ODA Functional Architecture and led to discussions

Page 9 of 33

on a wide range of topics including Affinity Analysis, CFS/RFS, Internet Security, Self-Care Portals and Composite Offerings.

MEETING TITLE: AI Data Model for Telco & Data Governance: Joint Session with AI/IoE/ODA/API Collaboration (JOINT: AI/DA, CEM, IoE, API) OBJECTIVE: Opportunity for Digital Ecosystems/IOE, ODA, API, AI&DA, Data Management and CEM to collaborate on key topics.

OUTCOME: Members were able to come together from the ODA, AI & DA, API and IOE project teams to recap the work done throughout the week. The teams focused on recapping key areas where cross collaboration is needed as we move forward with the 19.0 release. Please see contributions listed in the "Input Materials" in the meeting minutes. The hot topic was the TM Forum Data Model and identify gaps (if any) that need to be discussed across the project areas to help enhance the model. Tayeb Ben Meriem of Orange presented several contributions on AI as applicable to ODA Intelligence Management. There was also a use case illustrating how AI might be used for engagement management. There was some general discussion about the potential cross team impacts but no specific actions were assigned. There was a general discussion about the fact the TM Forum currently has only one data model, the TM Forum Data Model, and the default starting point for any TM Forum project should be attempting to reuse it and extend, change and modify as necessary. There was an exchange of information regarding the results of the week.

Page 10 of 33

AI & Data Analytics/Data Management TM Forum is leading the communications industry in data analytics and realizing the business value of AI through a range of best practices, thought-leading collaboration activities, and research, in addition to services such as training and coaching to get you started. The project teams are currently working on:

• Service Management Standards for AI

• AI Data Model and Training Repository for Telco

• AI Maturity Model

• AI Use Cases & User Stories (Guide Book)

• Data Management

If you are not already a project member, you may join the AI & Data Analytics project (in the

‘Application Project Area’) here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=cf30e980-0698-483f-86e3-

bd1be83755de&CommunityKey=3c508ba8-5775-4b3b-8ee4-48ed16af69e2

Members wishing to get involved in the AI & Data Analytics project may access the working area

on the project Wiki, Confluence, here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=88573919

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=110135124

and working calls here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=108757804

Summary of AI & Data Analytics / Data Management Sessions at Action Week: MEETING TITLE: Program Kick-Off Welcome Session (JOINT: AI & Data Analytics, CEM, Data Management) OBJECTIVE: Review of the key AI drivers, from network automation to customer centricity and service management. Overview of TM Forum’s AI Program, R18.5 deliverables & a look to R19.0.

OUTCOME: Action Week in Lisbon 2019 kicked off by Aaron Boasman-Patel, TM Forum, giving a recap of the work done in R18.5 and the introduction of the Data Management workstream. Members were reminded of the importance of driving AI adoption through the creation of standards and improving customer centricity. Throughout the week members worked through all of the AI & DA workstreams to enhance the work done in 18.5 and discuss the need for Data Management.

MEETING TITLE: AI Data Model for Telco & Data Governance (JOINT: CEM, AI & Data Analytics, Data Management, ODA, DE (IOE)) OBJECTIVE: Understanding why there is a need for a specific AI Data Model for Telco; TM Forum’s Data Model – a brief update (Genesis of the API Model, what is available, production of the interactive model, extensions). Proposed next steps for R19 and beyond; Develop a use case from one operational domain, establishment of a Catalyst for mapping data ingestion, creation of data catalog, best practice guide for functional models, data governance – how do we set up a governance model & scope?

OUTCOME: George Glass of TM Forum introduced the TM Forum Data Model and discussed its appropriateness for usage as the input schema for the input schema to the Intelligence Management block.

Page 11 of 33

Ken Dilbeck of TM Forum then presented the AI Project proposed Catalyst for DTW 2019 to validate this approach. Ken shared the challenge the group was having on getting access to production quality test data from the CSPs. The group brainstormed several approaches for data access. The AI team took away a proposal to move the model to the data vs. moving the data to the model. TM Forum members were also introduced to the Data Management workstream the AI & DA project launched during Lisbon Action Week. Data governance is a set of processes that ensures that important data assets are formally managed throughout the enterprise. During Action Week members explored this new workstream and discussed how data is impacting how businesses are managing the governance of data.

MEETING TITLE: Management Standards for AI OBJECTIVE: Discuss reference architecture and interface definitions to be updated accordingly; begin building reference implementations with the purpose of investigating the practicality of the standards being developed and identify any gaps. In addition, look at how does the AI Management Standards for AI reference architecture map into the ODA Functional Architecture (IG1167), develop a data model for AI Management and specify the corresponding API functions; specify as little as is necessary and draw instead from existing standards where possible; Work with AI Data Model work stream to ensure alignment with their output on a data model for AI Management; Discuss the best practice for AI management and data handling with AI Maturity Model and AI Training Data Repository workstream; Continue working with CEM Use Case team to develop use cases created in this stream to reflect the CX point of view.

OUTCOME: During the session members were given a recap of the work done in R18.5 with the completion of IG1184 Service Management Standards for AI R18.5. IG1184 was the first step towards understanding the need for governance around AI. Having the opportunity to collaborate face-to-face, the members broke out into teams to define operational policy for specific scenarios:

• Virtual agent / chat bot • Forecasting and scheduling

• Predictive modelling (churn, next-best-action…) • Anomaly detection (monitoring, fraud…)

• Network planning and optimization • Network failure prediction

• Network diagnostics • Cybersecurity The collaboration that took place gave the team better insight into how to capture business/operational policy spanning both narrative style policy through to policy that can be measured and acted upon.

MEETING TITLE: AI Data Model/AI Data Training Repository (JOINT: CEM & Data Management) OBJECTIVE: AI Data Model/AI Data Training Repository; flush out intelligence function for data model; Continue discussion around Data Lake work surrounding AI; Discuss working with Linux Foundation to understand Acumos and its capabilities; Catalyst for TM Forum Data Model; Discuss getting real data; Jointly validate schema can be achieved - with ODA/SID.

OUTCOME: Members continued to discuss next steps for AI Data Model/Training Repository. On Tuesday, members questioned if the data repository should be combined with the AI Data Model discussion right now or if it would make sense to wait. Members also learned more about ABDR and how it was created from AI/ML Use Cases. Members are looking to adopt the TM Forum Data Model but would like to know how ABDR could assist the team with the AI needs moving forward. Next steps will focus on taking a look at uses cases used in the overall AI & DA Program, ODA, and ABDR. Comparing those uses cases to the entities in the ABDR spreadsheet and API Data Model will help fill in the gaps needed in the TM Forum Model. All members are encouraged to continue this discussion by joining the AI Data Model calls on Tuesday 1pm (GMT).

MEETING TITLE: AI Maturity Model (JOINT: DMM) OBJECTIVE: Understanding the complexities of deploying AI – where do we start?

Page 12 of 33

• How do you assess your own maturity? Where are you now and where do you want to go? • Getting the implementation right from the customer, technology, strategy to data and operations • Outlining the proposed TM Forum AI Maturity Model • More work across the dimensions needed • Discuss testing model • Feedback of the model • AI Maturity Model make sure we are in line with work being done in ODA

OUTCOME: Emmanuel A. Otchere of Huawei presented the current status of the AIMM and reviewed the content of the model as a result of the R18.5 work. The work plan for R19.0 was reviewed and the plans for scrubbing and clarifying the criteria and evaluation wording discussed. The group reviewed the plan to begin alpha testing with the excel spreadsheet. Axiata has volunteered to provide feedback. During the meeting DT volunteered to explore their ability to exercise the model using the spreadsheet. The intention is to have the AIMM alpha tested and available in the web-based tool for demonstration at Digital Transformation World 2019.

MEETING TITLE: AI User Story/Use Cases (JOINT: CEM, AI & Data Analytics, eTOM) OBJECTIVE:

• User Stories to Test Case Guidebook discussion. Highlight the need to gravitate AI User stories based on eTOM and therefore build an AI version of TOM – AITOM

• Continue discussion around Catalyst • Continue work done with AI workstreams around the role Artificial Intelligence has in enhancing the Customer

Experience. How can CSP allow customers to express their concerns by helping to reduce response times and personalizing the customer experience? How can network and processes be improved by utilizing AI functionality within the CEM space?

OUTCOME: Members were given an overview of the work done in R18.5 with the publication of GB1002 Artificial Intelligence User Stories & Use Cases 18.5.0. During the R18.5 collaboration the team noted the need to be aligned with the eTOM team. Action Week Lisbon allowed for a face-to-face collaboration session that helped both teams ensure the work being done is aligned. Many of the action items discussed will be the focal point for R19.0. Both teams will continue to have joint meetings to produce objectives for R19.0.

MEETING TITLE: AI Data Model for Telco & Data Governance: Joint Session with AI/IoE/ODA/API Collaboration (JOINT: AI/DA, CEM, IoE, API) OBJECTIVE: Opportunity for Digital Ecosystems/IOE, ODA, API, AI&DA, Data Management and CEM to collaborate on key topics.

OUTCOME: Members were able to come together from the ODA, AI & DA, API and IOE project teams to recap the work done throughout the week. The teams focused on recapping key areas where cross collaboration is needed as we move forward with the 19.0 release. Please see contributions listed in the "Input Materials" in the meeting minutes. The hot topic was the TM Forum Data Model and identify gaps (if any) that need to be discussed across the project areas to help enhance the model. Tayeb Ben Meriem of Orange presented several contributions on AI as applicable to ODA Intelligence Management. There was also a use case illustrating how AI might be used for engagement management. There was some general discussion about the potential cross team impacts but no specific actions were assigned. There was a general discussion about the fact the TM Forum current has only one data model, the TM Forum Data Model, and the default starting point for any TM Forum project should be attempting to reuse it and extend, change and modify as necessary.

Page 13 of 33

There was an exchange of information regarding the results of the week.

Page 14 of 33

Open APIs

TM Forum’s suite of normalized industry agreed Open APIs automate all the essential operational management capabilities to drive an ecosystem enabled model & data-driven flexible microservice oriented architecture. TM Forum’s API Ecosystem is a family of APIs making it easier to create, build and operate complex innovative services. This set of standard interfaces enables rapid, repeatable, and flexible integration among operations and management systems. TM Forum REST based APIs are designed for use on anything from IoT device management to complex B2B value fabrics and they apply to all the topics our members are focused on: NaaS, IoT, Digital Health, Smart Grid, Big Data, NFV, Next Generation OSS/BSS and more.

If you are not already a project member, you may join the API project (in the ‘Core Project Area’) here:

https://engage.tmforum.org/projects/volunteer-opportunity-details?VolunteerOpportunityKey=603731cf-

09c5-4229-8730-c900c157c07b&CommunityKey=0430eebd-2dac-41b6-bd1b-fba7ebcfe7d7

Members wishing to get involved in the API project may access the working area on the project Wiki,

Confluence, here: https://projects.tmforum.org/wiki/display/AP/API+Project+Home

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/display/AP/2019+Lisbon

and working calls here:

https://projects.tmforum.org/wiki/display/AP/Meeting+notes

Summary of API Sessions at Action Week: MEETING TITLE: Development of TM Forum’s Open Digital Architecture (ODA); The Core Commerce Management Pioneer project and the construction of a reference implementation – the Business Operating System (BOS) (JOINT: ODA) OBJECTIVE: Within TM Forum, at the request of members, we have initiated a program to build a reference implementation of the core commerce management functions that make up the Open Digital Architecture (ODA). Its aim is to address the level of agility we need in a 5G world. A reference implementation would drive ODA standards in the ‘build then standardize’ approach adopted by hyperscale web companies, as well as providing a common reference for interoperability testing. We are running a Core Commerce Management Pioneer Project to further develop the architecture for ODA so that reference implementations of the architecture can be built and demonstrated. This involved identifying the sub-components of the Core Commerce layer and the associated APIs, which will enable a “plug and play” approach to the interoperability testing of such functions as product catalogue, product ordering, customer asset creation or billing. Our plan is to then use the Catalyst program to develop several proof of concepts (PoC). One PoC called the Business Operating System (BOS) is looking at generating code to implement the solution (either contributed or open source). We are investigating an approach to a reference implementation where only the relevant APIs are exposed, and the internal code of the component remains the IPR of the contributor. For the various PoC to work there will probably have to be a mix of both contributed code,

stubs of components to maintain the e2e referential integrity of the data model and components exposed via APIs. When there is an open reference implementation of the Core Commerce part of the ODA architecture, COTS or SaaS vendors could demonstrate inter-operability as part of their core product offering. The long RFP procurement cycles would be reduced since both CSPs and vendors would have a reference model describing the functional scope, data mastership and Open-API services available for each component in the reference architecture. Systems Integrators would be able to focus on value-added innovation, instead of their effort being consumed in making oddly-shaped pieces of a puzzle fit together. At this

Page 15 of 33

session in Action week, we will have an update on the overall Core Commerce Management Pioneer project as well as

updates on Catalysts that are underway to construct the reference implementations.

OUTCOME: This was a very well attended session were the BOS Pioneer Project was introduced to the audience. For several participants in the audience this was their first exposure to BOS, so it was important to quickly bring them up to speed to allow them to participate effectively in the rest of the week.

Several of the members who have participated in the project actively over the last four months offered their observations and mentioned areas they thought were of key importance.

MEETING TITLE: Excursions in the API Landscape OBJECTIVE: Presenting the realities of using Open APIs and the challenges of getting the best from them.

OUTCOME: Andreas Polz of BearingPoint presented a series of “real-life” challenges associated with implementing TM Forum Open APIs alongside legacy systems and described his experience of addressing them. He shared one of his key conclusions, to always engineer API implementations and exposed services to be usable both internally externally. This saves designing the API implementation twice and forces you to think through both internal & external issues at the outset, which tends to lead to a much more robust solution.

Andreas went on to give examples of how his teams have worked on integrations with legacy systems and he did a live demonstration of creating a REST API "wrapper" around a publicly available data source, in this case using the Microsoft Azure API Management Service.

MEETING TITLE: TM Forum Open API / ONAP / MEF / ETSI Technical Session OBJECTIVE: Updates on MEF and ONAP & ESTI technical work – next steps and alignment, NaaS APIs phase II – focus on promoting into other standards and incorporation of TMF641, TMF638.

OUTCOME: The current status of using TM Forum Open APIs to support the NaaS, MEF & ONAP developments was explored. In particular, it was discussed how it would improve things if Members who are common to both TM Forum and MEF &/or ONAP could each speak with one voice when dealing with the two organizations, as currently some member companies are expressing different views to TM Forum compared to the view they are expressing at MEF or ONAP, which does not help with timely alignment.

It was agreed it would be helpful if those working with MEF & ONAP on API issues could also attend a regular (tentatively fortnightly) call to bring the issues & status back to the TM Forum API project, the core API design could be reviewed with a view to accommodate as many of the ONAP & MEF requirements as makes sense.

MEETING TITLE: API Welcome, The Week’s Agenda and API Swagger “Schemification” OBJECTIVE: Welcome to new-comers to the API program. API "state of the Nation" – especially API Swagger "schemification". High level summary of planned work in R19.0. Summarize API agenda for the week. Swagger Schemas "schemification" - What has been done in R18.5? The strengths of this approach. The tooling in place to support it. Plans for "schemification" for the remaining APIs.

OUTCOME: Stephen Harrop of Vodafone presented an introduction, overview and current state of affairs in the API program, as well as some practical examples of how some of the newer techniques introduced in the past 2 cycles, like polymorphism, are used in practical examples. In the slides posted in the meeting minutes, look for an embedded second set of slides with some of those examples.

MEETING TITLE: API Architecture Update OBJECTIVE: API architecture topics – where we are, where we are going – Design Guideline “roadmap”.

Page 16 of 33

OUTCOME: Pierre Gauthier of TM Forum presented the roadmap for the API Design Guidelines (towards Version 4). A discussion followed on some of the topics referenced. On the topic of moving towards Swagger3, there was consensus that we are now nearer to move to this, but no clarity on whether this will actually be started in this cycle. A consensus was formed that a definition of priorities and a target scope that can realistically be achieved in 19.0 still needs to be locked down in the next call of the architecture.

MEETING TITLE: API Tooling & Auto generation OBJECTIVE: Continue work to develop the plans for the next phase of Open API automation to continue to drive up the quality, consistency and referential integrity between interoperating APIs. Explore Open API JSON to SID tooling options.

OUTCOME: Mariano Belaunde of Orange gave an overview of the tools and processes that have been created during Release 18.5 (validating schemas, generating swagger, diagrams, and documentation). There was a discussion of next steps to "industrialize" these for a smoother Continuous Integration/Delivery workflow, together with improving our GitHub organization for concurrent development in Release 19.0.

MEETING TITLE: Financial Transaction – Richer support OBJECTIVE: Extending payment and financial capabilities – extending across the full business use cases (refunds, backing out, etc.).

OUTCOME: Yaniv Gigi of Amdocs (with Jonathan Goldberg on the conference call) presented their proposed updates to the area of unbilled charges on a customer bill. This highlighted a contentious design issue about how to handle unbilled charges, and whether to use CustomerBill as the API to retrieve this. This debate was not concluded in this session and is ripe for further work.

MEETING TITLE: New API Developments OBJECTIVE: Explore candidate new Open API developments for the R19.0 cycle.

OUTCOME: This was a productive session where four new API proposals were presented and discussed. The data models were reviewed for each and guidance was given to help them progress to the next stage of development. There was strong support for all the discussed APIs to be developed and added to the catalog. There will be a follow-on meeting on Thursday Q2 to complete this review.

MEETING TITLE: R19.0 API Roadmap & Beyond OBJECTIVE: Work to derive a common view to enable the team to publish a clear roadmap of intention for the next set of Open APIs that the members wish to collectively develop, prioritize by demand and available skilled member resource – and next rounds(s) of schemification – address by a “code-jam”? Also solicit general feedback – what APIs would members like to see and provide feedback on roadmap plans?

OUTCOME: This session was used to prioritize specific APIs for development in the R19.0 timeframe, allocating ownership and gaining commitment. The Open-API Catalog was updated to reflect this, which will be uploaded. Having focused on service-layer APIs in R18.5, R19.0 APIs will focus on the Product area.

MEETING TITLE: Common Open API Payloads OBJECTIVE: After we complete the Schemification exercise for R18.5 we could look at how TM Forum Open APIs can carry MEF payloads (links to previous work done in ZOOM projects). There are currently teams working on YANG models at the resource level and we could show how this could be encapsulated with our APIs at the service and product levels. Planned Output: How to produce a guide book on extensibility for payloads.

OUTCOME: Ludovic Robert of Orange gave a detailed presentation of the gap-analysis with TM Forum and MEF APIs, with technical recommendations on how the TM Forum Open API design guidelines can accommodate these using the polymorphic pattern. This raised many good discussion points with some agreement on the way

Page 17 of 33

forward, such as extension-by-restriction to constrain attributes for the MEF. It was highlighted that OAS/Swagger v3.0 will give us the capabilities to better address these.

MEETING TITLE: ODA & Open APIs (JOINT: ODA) OBJECTIVE: Explore the implications of ODA developments on the Open APIs and the implications of recent Open API developments on the ODA program.

OUTCOME: Ludovic Robert of Orange and his team presented an overview of concepts to align with ODA requirements for process and task-centric APIs that deal with long-lived workflow which may involve human-interaction. Much debate ensued over traditional BPM approaches in a microservices architecture. The "process" API is an attempt to break-down the component parts of a workflow into reusable "blocks" of functionality that may be composed by BPM.

MEETING TITLE: API Conformance & Vendor Assessment Report (VAR) OBJECTIVE: The recent launch of API Conformance - Current status, recent announcements and ongoing plans with Q&A. Develop plans for the structure of the Vendor Adoption Assessment Report (VAAR) that will enable members to clearly determine which vendors are utilizing Open APIs within their solutions and which vendors have certified their use of the Open APIs within their solutions.

OUTCOME: Jonathan Coleman and George Glass of TM Forum took the team through the VAAR survey and a sample set of reports. There was general agreement that the report would be very useful. There was a discussion about ensuring that smaller vendors whose product portfolio only covered a small percentage of the Open APIs would still be able to appear in the top right-hand quadrant of the report. Jon took an action to modify some of the reports and see if it was possible. A request was made to develop a CSP version of the report, which we will look at after we finalize the vendor version and get it launched. We will do a final trial of the vendor report taking into account the changes and improvements noted above, so we have a VAAR ready for Digital Transformation World in Nice in May 2019.

MEETING TITLE: Suite of IoT/IoE APIs (JOINT: IoT) OBJECTIVE: Applied Assets: Define a suite of IoT/IoE APIs which we can jointly develop; Validation of IOT Component Suites/Data Model & reference architecture; Joint meetings with IOT Management & API teams; Goal to sign off on IoT management suite.

OUTCOME: Informative session led by Pierre Gauthier of TM Forum, describing the current state of the IoT and Smart City reference architecture and harmonization of data modes work as a result of liaison with FIWARE as well as review of the assets now in team review associated with the IoT API component suites. Active discussion and questions regarding alignment of this work with other standards and movement towards full harmonization of the models. More work to be done to lay out next phases of harmonization of the data models prior to announcing the roll out plans. The session covered an introduction and history staring with the Smart City Business Framework. It described a component suite (a grouping of existing APIs that share common roles/security policies to operate). It was agreed to document a "DSM API Component Suite" starting from the NaaS component suite.

MEETING TITLE: API Feedback & JIRA status review

OBJECTIVE: General feedback on existing APIs and an analysis and review of the API JIRA database with an aim of closing as many as possible and planning for the closure in upcoming work. Prior analysis of those to propose for closure, cross-cutting concerns or duplicates and clusters will be presented to help this process. Outputs will include updates to the JIRA database and high-level analysis of where the pressure for change exists across our API catalog – feeding into the API roadmap.

Page 18 of 33

OUTCOME: Steve Harrop of Vodafone gave an overview of the JIRA database: used for managing change within the API program, and then pointed to a number of pre-defined queries that offered up some "low-hanging fruit". The rest of the session was then a working-party to look through these issues with a view to closing them out. 7 JIRA issues were then closed.

MEETING TITLE: AI Data Model for Telco & Data Governance: Joint Session with AI/IoE/ODA/API Collaboration (JOINT: AI/DA, CEM, IoE, API) OBJECTIVE: Opportunity for Digital Ecosystems/IOE, ODA, API, AI&DA, Data Management and CEM to collaborate on key topics.

OUTCOME: Members were able to come together from the ODA, AI & DA, API and IOE project teams to recap the work done throughout the week. The teams focused on recapping key areas where cross collaboration is needed as we move forward with the 19.0 release. Please see contributions listed in the "Input Materials" in the meeting minutes. The hot topic was the TM Forum Data Model and identify gaps (if any) that need to be discussed across the project areas to help enhance the model. Tayeb Ben Meriem of Orange presented several contributions on AI as applicable to ODA Intelligence Management. There was also a use case illustrating how AI might be used for engagement management. There was some general discussion about the potential cross team impacts but no specific actions were assigned. There was a general discussion about the fact the TM Forum current has only one data model, the TM Forum Data Model, and the default starting point for any TM Forum project should be attempting to reuse it and extend, change and modify as necessary. There was an exchange of information regarding the results of the week.

Page 19 of 33

Customer Centricity

CX is about the entire customer journey focusing on the complete ideology and methodology of the business

• A basis to discover a true omnichannel methodology integrating all relevant channels to drive CX

• Leverage deep learning and AI through disruptive analytics to gauge customer sentiment

• Developing and delivering security and trust throughout the customer journey

The Customer Centricity & Analytics Project helps service providers and global enterprises to continuously evolve their businesses by moving beyond traditional customer experience to true one-to-one customer engagement in order to maximize market share, customer loyalty and opportunities for growth.

If you are not already a project member, you may join the Customer Experience Management project (in the

‘Application Project Area’) here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=cf30e980-0698-483f-86e3-bd1be83755de&CommunityKey=3c508ba8-5775-

4b3b-8ee4-48ed16af69e2 Members wishing to get involved in the CUSTOMER CENTRICITY project may access the working area on the

project Wiki, Confluence, here:

https://projects.tmforum.org/wiki/display/CEM/Customer+Experience+Management+Project+Home

See the meeting notes from Action Week Lisbon here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=110135166

And working calls here:

https://projects.tmforum.org/wiki/display/CEM/R19.0+Meeting+Notes

Summary of Customer Centricity Sessions at Action Week: MEETING TITLE: Omnichannel Guide: Customer 2025

OBJECTIVE: CX Design has become a key aspect in digital engagement experience and change in contemporary audience segments. Design projects have emerged which aim to integrate the strengths of design thinking. Focus for this workstream is end-to-end CX design practice that delivers business value. Continue building and updating the existing Omnichannel Guideline through IG1183 release in R18.5:

• Know Customer on personal level

• DSP Agile Engagement Methodology

• DSP Management of customer with third parties

OUTCOME: Members were introduced to the new work done in R18.5 with the publication of IG1183 Omni Channel CEM Guideline; What Customers Will Expect By 2025 R18.5.0. The CEM team is working to update the work done around omnichannel focused the challenges CSPs are facing today and in the future. Face-to-face discussions focused around what the 2025 customer is expecting. The team worked on a use case to set the stage of the 2025 customer. In R19.0, the team will continue to evolve a new guide with what the 2025 customer is expecting. We encourage all members to join the discussion every Monday at 1pm (GMT).

MEETING TITLE: 360 Degree view of the Customer

OBJECTIVE: Telcos have an opportunity to rebuild their market positions and create innovative offerings for customers by re-inventing their 360 Degree View of the Customer. Few companies are close to capturing their full potential in this area. Three key initiatives in this space to consider:

Page 20 of 33

• Telcos are expanding their revenue streams • M&A means CSP are unifying CX processes & need to identify customers • Digital Transformation - How can CSPs promote 360 degree view of the customer?

OUTCOME: Members were introduced to the work done during R18.5 with the publication of IG1182 The CSPs Guide to AI-Driven 360 Degree Customer Profiles R18.5.0. Customer expectations are increasing, and a key focus must be creating highly successful customer engagements. Through the work done in 18.5 and into 19.0 the focus will be in a renewed focus on customer-centricity powered by an integrated, intelligent and actionable 360-degree customer profile. The groundwork has been laid out; however, members attending the session noted the need for CSPs to be present in the conversation. We encourage CSPs to join the conversation to evolve the CX 360 Degree view of the Customer.

Page 21 of 33

Frameworx Frameworx provides the fundamental building blocks for digital transformation based on a proven history of enabling business transformation through numerous major technology changes. - A Blueprint for Best Practice Business Operations - A comprehensive suite of standards and best practices to accelerate and de-risk transformation projects and enable any service provider’s business to run with maximum agility and efficiency:

• Business Process Framework (eTOM): Multi-layered model of the key business processes for efficient, agile operations

• Information Framework (SID): Standard definitions for all the information that flows through the enterprise and between service providers and their business partners

• Frameworx Metrics: Definitions for over 2900 measures and KPIs to help run your business

• Application Framework (TAM): A systems map showing how business capabilities are implemented in software applications

If you are not already a project member, you may join the Frameworx project (in the ‘Core Project Area’)

here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=603731cf-09c5-4229-8730-c900c157c07b&CommunityKey=0430eebd-

2dac-41b6-bd1b-fba7ebcfe7d7

Members wishing to get involved in the FRAMEWORX project may access the working area on the project

Wiki, Confluence, here: https://projects.tmforum.org/wiki/display/FP/Frameworx+Project+Home

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/display/FP/19.0-TAW+Lisbon

And working calls here:

https://projects.tmforum.org/wiki/display/FP/Meeting+notes

Summary of Frameworx Sessions at Action Week MEETING TITLE: Development of TM Forum’s Open Digital Architecture (ODA); The Core Commerce Management Pioneer project and the construction of a reference implementation – the Business Operating System (BOS) (JOINT: ODA) OBJECTIVE: Within TM Forum, at the request of members, we have initiated a program to build a reference implementation of the core commerce management functions that make up the Open Digital Architecture (ODA). Its aim is to address the level of agility we need in a 5G world. A reference implementation would drive ODA standards in the ‘build then standardize’ approach adopted by hyperscale web companies, as well as providing a common reference for interoperability testing. We are running a Core Commerce Management Pioneer Project to further develop the architecture for ODA so that reference implementations of the architecture can be built and demonstrated. This involved identifying the sub-components of the Core Commerce layer and the associated APIs, which will enable a “plug and play” approach to the interoperability testing of such functions as product catalogue, product ordering, customer asset creation or billing. Our plan is to then use the Catalyst program to develop several proof of concepts (PoC). One PoC called the Business Operating System (BOS) is looking at generating code to implement the solution (either contributed or open source). We are investigating an approach to a reference implementation where only the relevant APIs are exposed, and the internal code of the component remains the IPR of the contributor. For the various PoC to work there will probably have to be a mix of both contributed code,

stubs of components to maintain the e2e referential integrity of the data model and components exposed via APIs. When there is an open reference implementation of the Core Commerce part of the ODA architecture, COTS or SaaS vendors could demonstrate inter-operability as part of their core product offering. The long RFP procurement cycles

Page 22 of 33

would be reduced since both CSPs and vendors would have a reference model describing the functional scope, data mastership and Open-API services available for each component in the reference architecture. Systems Integrators would be able to focus on value-added innovation, instead of their effort being consumed in making oddly-shaped pieces of a puzzle fit together. At this session in Action week, we will have an update on the overall Core Commerce Management Pioneer project as well as updates on Catalysts that are underway to construct the reference implementations.

OUTCOME: This was a very well attended session were the BOS Pioneer Project was introduced to the audience. For several participants in the audience this was their first exposure to BOS, so it was important to quickly bring them up to speed to allow them to participate effectively in the rest of the week. Several of the members who have participated in the project actively over the last four months offered their observations and mentioned areas they thought were of key importance.

MEETING TITLE: Application Framework and the Functional Model OBJECTIVE: Explain our plans of transforming the TAM into a Functional Model.

OUTCOME: The Frameworx team presented findings and questions regarding the planned development of a Functional Model and contemplated the optimal structure of such a model and it benefits. Consideration was also given to the proper granularity and best approach of grouping of functions. The matter is of great importance since it is significant in several other activities such as the APIs and ODA.

MEETING TITLE: Frameworx Metamodel OBJECTIVE: Expose our work on GB986, discuss plans, request assistance.

OUTCOME: A vibrant meeting in which the long-term scope of a Metamodel for Frameworx was presented. It included detailing original work when the metamodel was conceived. In addition, major changes that were performed in the last year were discussed. Future plans were also featured and discussed. This meeting also included a discussion and presentation of an endeavor of NTT to map between the Frameworx sub sections and the Open APIs.

MEETING TITLE: ODA Component Development

OBJECTIVE: Explain the work on ODA Component and further align it with the ODA work.

OUTCOME: The session was an important exposure of the ODA Component for ODA and BOS. It emphasized the interaction of the groups output. It seems that the ODA component work is to be viewed as a pattern and guidelines for real implementation of ODA. Immediate collaboration can be greatly beneficial.

MEETING TITLE: ODA/Frameworx Mapping Session (JOINT: ODA) OBJECTIVE: Discuss findings of ODA Frameworx Mapping.

OUTCOME: Sylvie Demarest of Orange shared a prepared contribution with the group that explained the ODA Functional Architecture team's approach to mapping and the guidelines they had established to do the mapping in an objective a repeatable way. Sylvie also shared with the group where gaps and inconsistencies had been discovered in the existing Frameworx and plans to create change requests to the appropriate framework to effect the necessary changes. Additional contributions were solicited especially around Engagement and Intelligence Management.

This session was an important coordination session. The Frameworx group was updated on current suggestions for new Frameworx artifacts based on the ODA to Frameworx mapping. Also, the Frameworx team presented two items that explore the relationship between the structure of Frameworx and the Functional Architecture of the ODA. The

Page 23 of 33

session was another reminder that both artifacts are part of the future Open Digital Framework. Additional contributions were solicited especially around Engagement and Intelligence Management.

MEETING TITLE: Development of IG1130x Impacts of SDN/NFV on the Application Framework OBJECTIVE: Explore continuing development the Application Framework, discuss Knowledge Management and how this area in TAM will progress.

OUTCOME: This was a working session; various online definitions were consulted. Material debate on the definition of Knowledge Management and its common use took place. This is a 19.0 candidate for change. This work is an ongoing effort and with many iterations already in place. The work is another stage of this significant work.

MEETING TITLE: NaaS Connectivity Service Models (UML & NaaS API Data Models) OBJECTIVE: Update of GB999 Connectivity Services Model and improve alignment with SID Logical Resource, NaaS APIs ONF MEF Models and simplification with respect to 3GPP Network Slice/Communication Service.

OUTCOME: The meeting reviewed all the incoming 10 contributions. Time precluded detailed review as there was only 9 minutes per contribution. The areas covered were:

• The 5G NaaS Connectivity Service requirements established in the 5G Catalysts and GB999 User Guide for Network Slicing.

• Additional requirements arising as we change scope from 5G Catalysts to ODA production particularly input from EU VINNI ODP-148 and Microsoft Edge Computing ODA-137 and NTT Connectivity requirements for 5G ODA-130

• Review of current SID models and capabilities around Service, Resource function, Function and Features

• Modelling issues ODA-126 - ODA Production modelling challenges/issues - 5G focus were reviewed

Conclusions were that there is a best practice needed to describe how to model NaaS connectivity services in the SID and possible adjustment to the Service and Logical resource models to support 5G CFS models based on features.

Agreed to further review contributions on Joint ODA/SID calls but may need to move the meeting time of Tuesday 11:00 GMT forward to accommodate participation by Japan and Australia. The priority issue being around Service, Resource and Functions. Participants will review the six issue in ODA-126 with a view to creating a definitive team response.

Page 24 of 33

Internet of Everything and Digital Ecosystems Digital Ecosystem program focuses on 4 key areas:

• The Business Architecture & Capability model work generates the critical elements of Business Architecture, both from the CSP and DSP perspectives, including: Vison & Mission, Concepts & Principles, Capability Model, Value Fabric Map. These assets can be used to plot the digital transformation strategy and enables a more cohesive co-operation between business and technical partners which is a critical success factor of digital transformation. For Action Week, the focus was on identifying the core Telco and Ecosystem Business capabilities needed in a digital ecosystem and building a collaborative team lead by successful ecosystem companies and operators.

• Ecosystem Applied Assets: We collaborate with relevant organizations to build reference architectures, API component suites and data models for different ecosystems. The first full collaborative activity on this is Smart Cities. As service providers seek new revenue streams and to enter complex digital ecosystem scenarios, interoperability and swift, simple, secure data and process flows are essential. This work will produce assets facilitating the application of enablers such as IoT API component suite and Smart City Data Models.

• Ecosystem Co-Innovation: Exploration of cross-ecosystem co-innovation with different industry verticals, exploring how TM Forum member capabilities can be applied to make a valuable impact in an ecosystem context. This activity will work alongside a collaborative project which will aim to create the relevant applied assets for these verticals, with a clear ambition of enabling interoperability and seamless movement of data across ecosystems.

• Business Assurance: Our ambition is to evaluate and gain greater insight into how traditional areas of business need to adapt to cope with the changing needs of organizations, driven by the digital ecosystem revolution, 5G and emerging technologies as well as AI and Blockchain.

If you are not already a project member, you may join the IoE & Digital Ecosystems project (in the

‘Application Project Area’) here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=cf30e980-0698-483f-86e3-

bd1be83755de&CommunityKey=3c508ba8-5775-4b3b-8ee4-48ed16af69e2

Members wishing to get involved in the IoE & Digital Ecosystems project may access the project

Wiki, Confluence, here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=31687091

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/display/ODEP/2019-02-

11+Lisbon+2019+Team+Action+Week+Meeting+Minutes

Summary of the IoE & Digital Ecosystem Sessions focusing on Ecosystem & Telco Business Architecture Action Week: MEETING TITLE: Ecosystem Business Architecture OBJECTIVE: Align vision, mission and further develop the key themes based on value streams as they will focus the Ecosystem Business Architecture into a business capability library.

OUTCOME: The session kicked off with a general overview of the Digital Ecosystem program provided by Joann O'Brien of TM Forum. Emmanuel Otchere from Huawei provided an overview of TR282A. Review of the R18.5 work activities of the Ecosystem Business Architecture, its key concepts & principles. A review of the process steps in creating a business architecture; highlighting the TOGAF EA approach and the discussion of

Page 25 of 33

key entities required. Further work to continue to focus on additional ecosystem themes and their analysis identifying a catalog of actors/roles, their interactions and relationships using matrices. Session 2 covered the definitions of a generic set of ecosystem roles categorized by business /technical ecosystem roles to be aligned and incorporated into TMF071. More work to be done to identify and incorporate new roles as defined in GDPR to ensure their coverage. The team agreed to remove the framing of the roles in the context of IoT.

MEETING TITLE: Review of the CSP/Telco Business Architecture OBJECTIVE: Outline the plan and gain agreement for the crowd sourcing of Telco Business Capabilities and agree next steps for coming months.

OUTCOME: The team walked through the concepts of a business architecture reference model as a frame of reference for making business decisions. This model focuses on starting with customer and depicting the why and what (rationale) for how a business creates, delivers and captures value. Further discussions in Session 2 included a work through example. There followed discussions and concluded with resounding consensus on the essential need for a Telco capability map which will be supported by Verizon, BT, Vodafone, Orange and DT. The abstracted business capability map is needed by the industry to enable Telcos to pivot and grow their business by reselling capabilities in different ecosystem contexts. It is also essential to create the separation of concern between the business and technology areas of business and empowers the business people to rapidly design, develop and deliver new products and services based on existing capabilities. Other valuable reasons included the ability to risk assess new ventures based on maturity of a dependent capability, as well as improve estimation based on where capabilities are less mature. This analysis will also help guide and prioritize partnering arrangements based on where desired capabilities can be partnered for successful delivery. The team will move forward aiming to build a set of business capabilities with operators and experienced business architects in a F2F workshop in March / April timeframe.

MEETING TITLE: Telco Business Capabilities Wrap-up OBJECTIVE: Review, summary discussions to date and set plans for R19.0 deliverables.

OUTCOME: Agreement on the need and support to build a Telco Capability Map working with operators and business architects from vendors. This is now supported by Vodafone, Orange, BT, DT and led by Verizon. The face to face workshop to build this asset will be held in March/April time frame. Please contact us if you wish to attend.

MEETING TITLE: 5G Business Models & Technologies (JOINT: ODA) OBJECTIVE: Discover, learning session on 5G models to be used to further evaluate the Business Assurance team work items.

• Introduction to 5G Monetization & Revenue Assurance: • Convergence of Revenue Management and Charging and Billing • Outline of 5G models & technologies • Multi-Layer Modular Business Models for 5G. Work in progress by 5G-VINNI (5G Verticals Innovation

Infrastructure).

OUTCOME: Content packed session with questions raised regarding scope of 5G impacts on revenue assurance; monetizing 5G is about how to utilize 5G in supporting cost reduction and selling new products and services; do we treat 5G the same as 3G and 4G in deployment, selling of 5G, selling of speed or do we sell a whole new experience? 2018 & 2019 Catalysts demonstrated the new experience that could be sold; in the Tour de France drone experience and to emergency response and remote surgery use cases; with uncertainty of demand, there is concept for multi-layered business model that would support a concept of value-added connectivity on demand. Need to compile the 5G use cases in an easy way for analysis of business models and impact assessments.

Page 26 of 33

MEETING TITLE: Ecosystem Business Concepts Mapping (JOINT: ODA) OBJECTIVE: Mapping of ecosystem business concepts to the ODA Functional Architecture.

OUTCOME: Great contributions and discussions during this joint meeting led by Johan Vandenberghe of Bell Labs Consulting that resulted in actions to further align the work done on the ODA and EBA Concepts & Principles (GB998 & GB1000) and enhance the concepts by including the introduction of new ecosystem roles, incorporate branding and automotive use cases and referencing existing work to the different models described in TR211. An overview of past work related to managing service lifecycle across domains was presented.

MEETING TITLE: Open Digital Labs - cross industry co-innovation environment available OBJECTIVE: Provide overview of the Open Digital Lab: roadmap & strategy. Explore the technical components and experience ease of use through demonstration.

OUTCOME: Informative meeting with Joann O’Brien of TM Forum presenting the overview and goals for the Open Digital Lab. Henrique Rodrigues of TM Forum provided a hands-on demonstration. Goal was to provide additional information to interested Catalysts and provide hands on support during Action Week for joining the Open Digital Lab. All are urged to reach out to this team to request access to the lab and get started!

MEETING TITLE: Suite of IoT/IoE APIs (JOINT: API) OBJECTIVE: Applied Assets: Define a suite of IoT/IoE APIs which we can jointly develop; Validation of IOT Component Suites/Data Model & reference architecture; Joint meetings with IOT Management & API teams; Goal to sign off on IoT management suite.

OUTCOME: Informative session led by Pierre Gauthier of TM M Forum, describing the current status of the IOT and Smart City reference architecture and harmonization of data modes as a joint collaboration with FIWARE, as well as review of the IoT API component suite. Active discussion and questions regarding alignment of this work with other standards and movement toward full harmonization of the models. More work to be done to lay out next phases of harmonization of the data models prior to announcing the roll out plans. The session covered an introduction and history staring with the Smart City Business Framework. It described a component suite (a grouping of existing APIs that share common roles/security policies to operate). It was agreed to document a "DSM API Component Suite" starting from the NaaS component suite.

MEETING TITLE: AI Data Model for Telco & Data Governance: Joint Session with AI/IoE/ODA/API Collaboration (JOINT: AI/DA, CEM, IoE, API) OBJECTIVE: Opportunity for Digital Ecosystems/IOE, ODA, API, AI&DA, Data Management and CEM to collaborate on key topics.

OUTCOME: Members were able to come together from the ODA, AI & DA, API and IOE project teams to recap the work done throughout the week. The teams focused on recapping key areas where cross collaboration is needed as we move forward with the 19.0 release. Please see contributions listed in the "Input Materials" in the meeting minutes. The hot topic was the TM Forum Data Model and identify gaps (if any) that need to be discussed across the project areas to help enhance the model. Tayeb Ben Meriem of Orange presented several contributions on AI as applicable to ODA Intelligence Management. There was also a use case illustrating how AI might be used for engagement management. There was some general discussion about the potential cross team impacts but no specific actions were assigned.

There was discussion on how to engage with the TM Forum Data Model. For example, the AI team are likely to make changes to the TM Forum Data Model and to execute on this, a Jira request should be made and allocated to the Data Model. As part of the governance system there will be an evaluation of the change request and this will either be accepted or rejected. Based on an acceptance at this stage, the respective changes can be made. It

Page 27 of 33

was noted that the same process will be used for the harmonization of the data model with other industry verticals. For example, if a change is required to the TM Forum data model to ensure alignment with the FIWARE data model this will be captured as a change request and evaluated as part of the existing governance system. The same will hold true for other further harmonization activities in the future. The team agreed that this would be mechanism for how to manage the consistency of the Data Model and George Glass of TM Forum was noted as having the ownership to capture this process and share with the wider community.

Page 28 of 33

Business Assurance Our ambition is to evaluate and gain greater insight into how traditional areas of business need to adapt to cope with the changing needs of organizations, driven by the digital ecosystem revolution, 5G and emerging technologies such as AI and Blockchain. Along with considering how the insights from this team can be driven through to the Frameworx models as this is primarily how operators and the industry adopts the insights of the collaborative working teams. Traditional Business Assurance:

• Optimizes existing methods and disciplines to minimize revenue losses across the business

• Identifies proactive/active measures to create cross domain control mechanisms to monitor and boost health of

the organization.

• Applies technology enabled best practice principles such as “assurance by design”.

• Reconciles siloed departments increasing agility and the ability to compete in the connected digital economy.

If you are not already a project member, you may join the Business Assurance project (in the

‘Application Project Area’) here: https://engage.tmforum.org/projects/volunteer-opportunity-

details?VolunteerOpportunityKey=cf30e980-0698-483f-86e3-

bd1be83755de&CommunityKey=3c508ba8-5775-4b3b-8ee4-48ed16af69e2

Members wishing to get involved in the BUSINESS ASSURANCE project may access the working

area on the project Wiki, Confluence, here:

https://projects.tmforum.org/wiki/display/RM/Business+Assurance+Project+Home

See the meeting notes from Action Week, Lisbon here:

https://projects.tmforum.org/wiki/display/RM/TAW+Lisbon+2019+Meeting+Notes

Summary of Business Assurance/Revenue Management Sessions at Action Week: MEETING TITLE: Business Assurance Team Plenary OBJECTIVE: Review, align and prioritize next set of business assurance deliverables R19.0.

OUTCOME: Business Assurance scope in the context of this working group is to be further defined as part of the dimension framework item. Good progress was made in this session towards identifying missing items in the toolkit and discussions around areas that can/should be included in the group's initiatives. Team will continue to explore goals and KPIs and refining the scope and dimensions of our business assurance work. Active participation is critical, and support has resulted in setting goals and objectives with named leaders for key aspects to map business assurance concepts to eTOM, defining business assurance profiles and roles and assessing capabilities gaps in the business assurance toolkit.

MEETING TITLE: Business Assurance OBJECTIVE: Explore the business assurance use cases where blockchain can/should be implemented for optimization of existing or new functions required in a digital business scenario.

OUTCOME: The key points highlighted the need to carefully consider application of blockchain/DLT and not just get caught up in the hype. There is a need for openness in blockchain collaboration across industries and ecosystems. Blockchain/DLT can be applied to current issues and gaps but will above all enable future opportunities. It's all about sharing, transparency and truth. Interoperability is emerging as a potential issue but is already being addressed. We need to be able to move on from POC to MVP and MVE (minimal viable engagement).

Page 29 of 33

MEETING TITLE: Business Assurance – Balanced Scorecard GB941A OBJECTIVE: Review and approve for incorporation into the balanced scorecard; methodology updates recommended based on CSP usage.

OUTCOME: Key questions raised during this session include the relevance of this CX journey mapping and evaluation to BA. This to many in the room is a different domain and responsibility of specific teams within their organizations, not part of RA/BA. Can and should aspects be integrated into BA functions? Also, does it make sense to integrate the credit note aspect into the next version of the TM Forum balance scorecard? If so, we need an agreed-upon definition that the team can consider moving forward. It might make sense to review the balanced scorecard again in a future cycle.

MEETING TITLE: Business/Revenue Assurance – Coverage Model GB941E OBJECTIVE: Review of recommendations for general model updates and discussion on how to update the TM Forum Coverage Risk Catalog:

• by applying best practice examples from CSPs and developing a method of how to continuously incorporate new risks

• with new risks referring to the Digital Transformation and its implicit migrations • that support system migrations leading to maintenance as well as new technical developments

OUTCOME: The key takeaway from this session is in line with what was also highlighted in the Dimension Framework session: the need to focus now on transformation assurance. There are many challenges with this due to the complexity of transformation (and migration) projects and the heavy impact on time and human resources for the BA/RA/risk teams. We do not currently have solutions to these challenges, but it is an important area for the team to address.

MEETING TITLE: Business Assurance/Revenue Assurance Questionnaire OBJECTIVE: Review the basis of revenue assurance questions asked in the 2017 survey and expand on it based on latest digital business assurance economy trends; for survey issuance in 2019.

OUTCOME: The team had an active workshop-style session resulting in several new questions and considerations to be considered/integrated into the new survey, which will still focus primarily on RA, but also gauge the level of awareness and adoption of BA principles and functions within organizations. We also established key timing with the survey to be rolled out early May with publication of results targeted for early September 2019. The team are committed to both broadening the scope and streamlining/simplifying the survey itself. We are targeting 170 respondents this year.

MEETING TITLE: Fraud Management Survey Review of Preliminary Findings OBJECTIVE: Review of preliminary findings and assessment of trends for incorporation into the R19.0 TR246 Survey results deliverable.

OUTCOME: The survey shows encouraging results, but new challenges with the advent of 5G, IoT, exposure through open APIs, etc. are just around the corner and we don't have solutions to these. We will need to update the existing guidebooks (in particular GB947 and GB969) as we develop solutions.

Page 30 of 33

Catalysts Accelerating R&D and multiplying R&D investment through TM Forum’s collaboration environment and methods

• Collaborative member teams verifying, piloting and test drive the above collaborative R&D result

• Accelerate market development and innovation funnel towards production by leverage industry best practices

• Close working relationships enable more creative solutions than the perspective of a single company

• In the world of IoT, ecosystems and virtualization, partners are vital, and Catalysts enable this mindset

• Marketing benefit of showcasing at the industry’s biggest event and to thousands of industry contacts

If you are interested in joining a catalyst project, you may see a summary of planned projects and

their requirements for additional members here:

https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=108757895

Summary of the proposed Catalyst Projects that were represented at Action Week in Lisbon:

URN Project Name Who to contact Short Description

C19.0.01 5G Dynamic Service management

Yuval Stein Agile real time Dynamic Communication Services and Network Slices Life Cycle Management assisted by AI for 5G and other network capabilities delivered as assured NaaS into multiple industry verticals supporting multiple assured 5G service classes e.g. uRLL mMTC and eMBB. The catalyst will be focusing on an extreme weather use cases and their practical impacts on the 5G network at both the business level and the slice management and orchestration level.

C19.0.03 The Marketplace Greg Tilton Zero touch partnering will allow Telcos to transform into platform businesses, platforms where innovative new services from partners may be represented or bundled seamlessly. Partners will on-boarded and operationally integrated, have their services discovered and then be included in offers through the platform all without an IT project.

C19.0.04 Digital Twins Vincent Seet 2025 Digital Operator Powered By Digital Twins

C19.0.05 Skynet Michel Valette End-to-end service orchestration and monetization on a 5G network slice in hybrid network for large enterprises with multiple global locations

C19.0.07 End to End AI Catalyst

Maria Adamczyk Deliver real tangible, high impact value for members by providing standards and best practices for AI in telecoms

C19.0.08 Via Optimus: 5G Planning & Optimization (focus on assured roaming)

Vinay Devadatta The catalyst project will focus on Planning and Optimization of 5G network resources in support of network slice instances. The Catalyst will also focus on the management of slices in a roaming scenario which may cross CSP boundaries. Block chain technology will be explored in facilitating inter CSP Network Slice Fulfillment and Assurance.

C19.0.09 Open AI Business Assurance Marketplace - Phase II

Gadi Solotorevski

This catalyst demonstrates how digital service providers can apply AI, Machine Learning and API-based revenue-assurance and fraud-management implementations to effectively protect the digital business, as well as ensuring trustful, simple and flawless customer and partner experiences.

Page 31 of 33

URN Project Name Who to contact Short Description

C19.0.12 Connected Citizens: The Smart City Accelerator

Christian Maitre Connected Citizens will propose the canvas to build smart city ecosystems with standardized tools, methods, processes and technical components under the paradigm of the City as a Platform: communities of city actors that will organize their digital journey on top of one scalable, interoperable, intelligent, monetizable, secured platform in the cloud

C19.0.14 Business Operating System (BOS): an implementation of ODA Core Commerce Management

Karim JAMMAL Operationalization of ODA Core Commerce Management by implementing and showcasing both « Welcome » and beginning of « Order Capture » processes in a simple use case through a seamless user experience to pave the way for more enriched business cases.

C19.0.15 E2E Federated ODA Knowledge Planes for Autonomic (Closed-Loop) Security Management & Control across Multiple Network Infrastructure and Administrative ODA Domains, with Autonomic & Programmable Traffic Monitoring as enabler

Tayeb BEN MERIEM

E2E Federated ODA Knowledge Planes for Autonomic (Closed-Loop) Security Management & Control (powered by AI, Distributed Ledger Technologies, Blockchain, NFV, SDN, Big Data) across Multiple Network Infrastructure and Administrative ODA Domains, with Autonomic & Programmable Traffic Monitoring as enabler.

C19.0.16 The Digital Business Marketplace

Gary Bruce Slides 17 to 25 capture the initial set of user stories. It is expected that further user stories will develop, and more champions commit to the project.

C19.0.19 Smart City Ecosystem Enablement & Business Models 1&2

Velumani Ramasamy

To build a smart platform and business models which can enable STC to monetize the data in an effective & efficient way. & To provide best in class Smart City Service at the attractive price to the end customer through various business models and ‘Smart City Platform’ as a service for Business Customers in B2B2X scenarios.

C19.0.20 Proactive Service Assurance via Closed Loop Predictive AI/ML

Rich Pappalardo Zero-Touch, Automated/Orchestrated Service Assurance on Hybrid Networks with Knowledge-Based Self-Learning Resolution

C19.0.21 Machine Learning Engine for Product and Sales Management through Digital Channel

Dahyr José Vergara Suárez

Driving revenue growth by exploiting data available in the systems of the CSP using machine algorithms techniques and big data stream processing in order to offer personalized and relevant customer products through an existing digital or cognitive channel.

Page 32 of 33

URN Project Name Who to contact Short Description

C19.0.27 Maximizing Engagement with Predictive Customer Journeys, Phase III

Arnold Buddenberg

Demonstrate how communications service providers can deliver flawless omnichannel engagement experiences, using the “shop experience of 2025” that mobilizes customers and convert a higher percentage of sales opportunities by maximizing the personalized customer engagement through leveraging omnichannel customer journey information with rich referential customer metadata and actively collecting shop experience user generated intent.

C19.0.28 Maximize CSPs Digital Sales/Revenue through AI based Online Customer Journey Analytics

Krishna Mohan SK

Maximize CSPs Online Sales/Revenue through AI based Online Customer Journey Analytics

C19.0.29 Blockchain-based Telecom Infrastructure Marketplace

Tayeb Ben Meriem

Blockchain-based Telecom Infrastructure Marketplace as a platform to evaluate the profitability of new business models that do not require CAPEX while ensuring trust and confidence, transparency, traceability among the ecosystem’s partners including regulator and the transactions they perform for transferring assets (physical and digital); Network Slice could be another asset to be considered as well.

C19.0.30 Blockchains for Media, SW Creative Asset Royalties, IPR Trust & Tracebility

Jorge Tellez We will build a trusted platform for digital asset management (IPR management) based on private blockchain technology as an implementation of TM Forum “Trust & Traceability in Digital Ecosystems” (IG 1175 Release 18.0)

C19.0.32 Cognitive Contact Center Phase 2

Luis Fernando Rubio Martínez

An accessible, responsive, smart assistant primed with data about callers’ needs and likely reason for calling as well as a potentially infinite memory of successful - call resolution strategies

C19.0.37 Fuel Customer Journey with Predictive Intelligence

Abhi Sur Create an integrated and personalized connected driver journey that incorporates proactive diagnostics, mobility services, vehicle telematics and predictive intelligence to ensure seamless vehicle usage experience

C19.0.38 TM Forum Data Model schema reuse for AI Data Model Proof of Concept

This catalyst will be a proof of concept to determine if the data schema developed by the TM Forum Open API program will be adequate to become the basis of a Common AI information model/schema for the Telecom industry for input into AI systems. Note – use of the schema does not mandate the use of REST APIs themselves. Other transport mechanisms may be more appropriate. This phase is input only, output from the AI system is for future study.

C19.0.40 Assurance of Dynamic Digital Service Offers

Drew Jordan As digital services become more dynamic with the introduction of 5G, Virtualization and SDN, monitoring and testing of the network services becomes increasingly important and allowing Product Managers within a CSP to coordinate the definition of Products and Services that they sell with capabilities within the network is essential.

Page 33 of 33

URN Project Name Who to contact Short Description

C19.0.43 AI Management Standards

Rob Claxton Build components of the AI Management Standards reference architecture to investigate and demonstrate governance of AI from model development through to operational deployment and in-life management.

C19.0.44 BOS with Complex Multiparty ecosystems

Brian Burton To apply the BOS reference implementation of the Core Commerce platform to an ecosystem scenario.

Projects sponsored by TM Forum and IBCs joint activity to promote Media-Telco Catalysts:

URN Project Name Who to contact Short Description

M19.0.04 Turbocharge Associated Press’ Image UX and AI applications with PERSEUS Pro

Guendalina Cobianchi

Deploying technique into the AP mobile app to make a better cx experience to access content. A new way to compression & to classify images & video, which needs to be rapidly quicker, quicker in archiving / tagging but also in accessing /transmission. "Showcase how PERSEUS Pro data compression transforms both the user experience (UX) and semantic indexing capability of the world’s largest image archive."

M19.0.14 AI enabled Media Desk Operations Automation

Manish Upadhyay

Next generation Media Desk automated solutions enabled by integrated workflows for Media & Entertainment will unlock efficiency in day to day operations, content processing and QA transformation, assisting in doing more with less.

M19.0.15 Media Content Piracy Solution using Blockchain

Manish Upadhyay

Content is the lifeblood of Media business which revenues are hugely affected by piracy – bring a solution using Blockchain technology to reduce revenue loss, recognize, protect the legitimate rights of content owners, producers, and distributors.

M19.0.16 Mobile news gathering using AI powered compression

Grant Totten Al Jazeera is currently working to empower our Newsroom and Journalists through improved intelligence for the Mobile Reporter and faster time-to-air for both Lives and Pre-Recorded content through leveraging AI, techniques for improved bandwidth utilization and advanced compression.

M19.0.17 Ai indexing for regulatory practice

Grant Totten Al Jazeera is currently exploring ways to intelligently automate the identification of violations of its own internal Editorial, Creative and Technical standards as well as those that external regulatory bodies, such as Ofcom, are mandatory to comply to.