action week roundup

FEBRUARY 1-5, 2021

ACTION WEEK ROUNDUP

CECILIA ORTEGA LAGOS

Website Phone Address www.tmforum.org +1 973-944-5100 181 New Road, Suite 304, Parsippany NJ 07054 USA

of 35

Table of Contents Session Timing .........................................................................................................................................2

TM Forum Virtual Action Week ...............................................................................................................3

AI & Data Analytics (AI) ............................................................................................................................4

Autonomous Networks (AN)....................................................................................................................8

Business Assurance (BA) ....................................................................................................................... 10

Customer Experience Management (CEM) .......................................................................................... 13

Digital Ecosystem Management (DEM) ................................................................................................ 16

Digital Maturity Model (DMM) ............................................................................................................. 19

Digital Organizational Transformation (DOT) ....................................................................................... 20

Diversity & Inclusion Program (DIP) ..................................................................................................... 21

Frameworx (FX) ..................................................................................................................................... 22

Open APIs (API) ..................................................................................................................................... 24

Open Digital Architecture (ODA) .......................................................................................................... 28

Session Timing Central European Time (CET)

Q0: 07:00 - 08.30

Q1: 09:00 - 10.30

Q2: 11:00 - 12.30

Q3: 14:00 - 15.30

Q4: 16:00 - 17.30

Q5: 18:00 - 19.30

Commented [CL1]: Not sure why this is relevant?

http://www.tmforum.org/


of 35

TM Forum Virtual Action Week

Virtual Action Week provided a platform for our members worldwide to meet, work and progress their projects virtually.

All of the programs and initiatives underway at TM Forum are designed to help our member companies improve operational agility while reducing costs and risk, engaging customers, expanding market share, and driving revenue growth through new services.

Virtual Action Week 2021 was comprised of a series of workshops and intro sessions across our six themes. The action-packed week was an opportunity for new and existing collaboration members to attend several intro sessions throughout the week and in-depth working sessions.

Included in this packet, you will find a list of sessions during Virtual Action Week along with the title, description, list of objectives and outcomes, and links to each session's recordings.

For all who joined us at Virtual Action Week, thank you for collaborating! For those who didn’t have the opportunity to join, we invite you to look into topic areas you might be interested in and join our weekly collaboration sessions. There are many exciting and innovative objectives and outcomes coming out of TM Forum’s collaboration area led by our members. Join the excitement!

If you have any questions, please feel free to contact me at [email protected], or you can submit a question at TM Forum’s JustAsk.

Sincerely,

Cecilia Ortega Lagos Head of Collaboration Experience


mailto:[email protected]

https://projects.tmforum.org/jira/servicedesk/customer/portal/3


of 35

AI & Data Analytics (AI) TM Forum’s AI & Data Analytics program is helping the industry deploy and manage AI at scale by reducing risks within and between different organizations. It provides a blueprint on how to deploy AI operations by redesigning and reengineering operational processes to support AI, as well as a framework and toolset for governing AI operations at scale. It empowers service providers to get more intelligence from their data, allowing better decision making.

AI is only as good as the data you have available to expose to algorithms, which is why data is often called the “new oil”. The work undertaken by TM Forum as part of its data governance initiative aims to create an ethical and secure framework so that service providers can easily share and use large sets of data with their partners. AI offers huge business and operational opportunities, which, coupled with those offered by 5G, could be worth over $400 billion. However, if service providers cannot embrace AI and modernize their operations, telecom business is at risk of breaking down as operations in the 5G era become too complex for humans to manage. AI alone is not enough to solve that problem, and CSPs need greater agility in their networks and operations. The AI, Data and Analytics program provides a cornerstone to the Open Digital Architecture (ODA) – a blueprint for modular, cloud-based, open digital platforms that can be orchestrated using AI, which aims to accelerate concept-to-cash from 18 months to 18 days.

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

‘Application Project Area’) here

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

on the project Wiki, Confluence, here

See the meeting notes from Virtual Action Week, February 2021 and working calls here

Summary of AI sessions at Virtual Action Week:

MEETING TITLE: Driving towards common, intelligent, AI-driven and autonomous operations, networks and services (Parts 1 and 2) Mon Q3 & Q4 JOINT: AI & Data Analytics, Autonomous Networks (AN), Beyond Connectivity - Ecosystem Component Suites OBJECTIVE:

• 1.General status update - Teams sharing what they have done so far • 2. AI, AN and IOE teams creating a taxonomy of AI and maturity levels across AI and AN –

What does it mean? What would it look like? What do we need? OUTCOME: Include the cohesion between the workstreams that were presented at Virtual Action Week and continue to align and seek synergies.

SESSION RECORDING:

Part 1 - 2021-02-01 Mon Q3 & Q4: Driving towards common intelligent, AI driven and autonomous operations, networks and services-Part 1

Part 2 - 2021-02-01 Mon Q3 & Q4: Driving towards common intelligent, AI driven and autonomous operations, networks and services-Part 2


https://www.tmforum.org/oda/

https://engage.tmforum.org/projects/volunteer-opportunity-details?VolunteerOpportunityKey=cf30e980-0698-483f-86e3-bd1be83755de

https://projects.tmforum.org/wiki/x/34dHBQ

https://projects.tmforum.org/wiki/x/A6IwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EdizXsx8vsxFnBG3P7vOKS0BoouFyoD-E4m6fwMBkwWGvw?e=vIgFpj

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EdizXsx8vsxFnBG3P7vOKS0BoouFyoD-E4m6fwMBkwWGvw?e=vIgFpj

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/Ef5ZXIpM2Z1LrRCZXbOBm7wB09BH5h6u5Ak0ITrz3t8zqQ?e=jaF4Lb

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/Ef5ZXIpM2Z1LrRCZXbOBm7wB09BH5h6u5Ak0ITrz3t8zqQ?e=jaF4Lb


of 35

MEETING TITLE: A practical framework for AI-driven operations in the telecom industry (Parts 1 & 2) Tue Q1 & Q2 JOINT: AI Operations (AIOps), AN OBJECTIVE:

1. Realigning processes and ensuring coherence, integration of processes and an end-to-end view.

2. Review the AI Checklists and see if any extensions are required, and input catalyst feedback. OUTCOME: Part one of this very popular double session began with Luca Varvello (Huawei) introducing the AIOps Initiative. Min He (Futurewei) and Dong Sun (Futurewei) then discussed the synergies between AIOps and Autonomous Networks (AN) Initiatives and, before the break, Luca presented details of the AIOps Sprint Plan for 2021. Following the break, Luca shared the recently published deliverables for the AIOps Service Management suite of documents, reviewed synergies between the AIOps and AI Governance Initiatives, discussed logos and 'branding' of terms such as AIGov, AIDev and AIOps, before reviewing the AIOps Catalysts submitted for the Catalyst Digital Showcase and Digital Transformation World during 2021. Members were encouraged to join the weekly AIOps and AN collaboration meetings where this work will continue. SESSION RECORDING: 2021-02-02 Tue Q1 & Q2: AI Operations: A practical framework for AI-driven operations in the telecom industry (Parts 1 and 2)

MEETING TITLE: Bringing the AI reference architecture and AI model data sheets to life with TM Forum Open APIs

Tue Q3 JOINT: AI, API OBJECTIVE:

1. Working session developing the suite of APIs to bring the reference architecture to life (alarm correlation & traffic flow optimization).

2. Address how to automate the capture into data to the AI Model Data Sheets. 3. How to enable the Data Sheets to become live documents to capture its life history – what

API interfaces are needed. OUTCOME: This session, hosted by the API collaboration team, provided an overview of work being carried out by the AI collaboration team on the AI reference architecture and data sheets. The objective was to present the work with next steps and actions to be determined during the subsequent Virtual Action Week session on Friday. Questions around trust and knowing when AI models are "good enough" came up; no answers were determined. SESSION RECORDING: 2021-02-02 Tue Q3: Bringing the AI reference architecture and AI Model Data Sheets to life with TM Forum Open APIs


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ETQQ5jdxie9MiBvYJ32tKpsBNF1FjlotABuMUD3UlsyPcg?e=sewIgl

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ETQQ5jdxie9MiBvYJ32tKpsBNF1FjlotABuMUD3UlsyPcg?e=sewIgl

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EfaVqrgyt2BOldq_CID5dlgBo36YgNheJT7_uC3qAWGg6A?e=rugROb



of 35

MEETING TITLE: Enabling AI adoption through effective governance (Parts 1 and 2) Tue Q4 & Q5 JOINT: AI & Data Analytics - AIOps, AI Governance, Data Governance, Closed Loop Anomaly Detection OBJECTIVE:

1. Developing the AI Canvas and understanding how to align this with AI Checklists and AIOps 2. AI Governance APIs: Need to understand how to bring together the AI Model Data Sheet

(which should capture the supported Model Contract of a model) and the Contract Management API.

3. AI Model Data Sheet: Thinking about how to automate the process of populating the data sheet, and how to produce customized reports from the data sheet.

4. Also define what a ‘good’ data sheet should look like – what do we expect to be provided as a minimum, etc.?

OUTCOME: The AI Governance project team hosted two sessions on Day 2 on ‘Enabling AI adoption through effective governance’. With a great turnout of 36 members, the first session launched with a summary of earlier discussions with the AIOps team regarding cross-team collaboration, any synergies with the work that both teams are doing, and how best to leverage the team momentum and deliverables. The team concluded that the next step will be to create a brief for a new visual identity that harnesses this joint work and deliverables. This was followed by an informative presentation on “IG1238 AI Canvas”, a brand-new tool that provides a use case template to explore and validate the feasibility of starting a new AI project and continuing to assess the work’s continuing viability through the project’s lifecycle. Attendees were invited to join the AI Governance project and work with the team to further develop the AI Canvas in readiness for publishing in 2021.

The second session discussed a taxonomy for ‘AI levels of automation’ which looks at the risks and safety of human and machine control, good architectural solutions, due diligence to stakeholders and regulators and also highlighted the key 'dimensions' to consider in determining who is responsible for the core tasks, updating the tasks, monitoring/responding to the environment, monitoring performance and resolving conflicts between systems. The session ended with a presentation on 'AI Checklists Mapping with the AI/AN Maturity Model’ that addresses how to link the AI Maturity Model guidelines with the AI Checklist recommendations. This discussion focused on the dimensions and sub-dimensions in the AI Maturity Model that are relevant for the AI Checklists.

The AI Governance team received some great feedback and concluded next steps on a number of the deliverables discussed in this session.

SESSION RECORDING: 2021-02-02 Tue Q4 & Q5: Enabling AI adoption through effective governance (Parts 1 and 2)


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EQVAweF_ZitCrQ7UQ3guYdQBTaJmQFLTH8mIlU95W_02bQ?e=b8DjaH



of 35

MEETING TITLE: Designing the data governance framework: A vision (Parts 1, 2 and 3) Thu Q1, Q2, Q3 JOINT: AI Governance, AIOps, Data Governance, Closed Loop Anomaly Detection, ODA OBJECTIVE: The aim of the TM Forum Data Governance project is to allow service providers, public and private organizations, and governments to have an ethical and secure framework to conform to. This enables easy sharing and use of large data sets across different sources and origins. The framework will comprise of some core technical components such as APIs and governance models as well as including technologies which rely on heavy data processing and use such as AI, blockchain and advanced data analytics. OUTCOME: The Data Governance project team hosted a series of three sessions on Day 4 of Virtual Action Week entitled ‘Designing the Data Governance Framework, a vision’. With 36 members in attendance over the course of the day, the team produced a set of potential new ideas for the Data Governance framework.

Session one included an introduction to data governance, as well as a high-level view of the data governance whitepaper (IG1225) that the Data Governance team has just finalized and is due for publication this week.

Interactivity was key throughout the day and session two was a full-on online interactive brainstorm to capture team input on the types of data to focus on and the limitations that are stopping progress. A poll was then conducted to identify the top priorities that should be addressed as the key drivers of future data governance.

Session three then built on the earlier session’s work and developed a set of ideas for projects and catalyst for the Data Governance Roadmap and also identified the key stakeholders/actors that should be involved. As a next step, the Data Governance project team will now further refine these ideas to produce their next set of deliverables for 2021.

The data governance sessions were a great success and have produced ideas and insights for the immediate Data Governance Roadmap.

SESSION RECORDING: 2021-02-02 Tue Q4 & Q5: Enabling AI adoption through effective governance (Parts 1 and 2)





of 35

Autonomous Networks (AN)

The Autonomous Networks Project aims to define fully automated zero wait, zero touch, zero trouble innovative network/ICT services for vertical industries’ users and consumers, supporting self-configuration, self-healing, self-optimizing and self-evolving telecom network infrastructures for telecom internal users: planning, service/marketing, operations and management. Autonomous Networks incorporate a simplified network architecture, autonomous domains and automated intelligent business/network operations for the closed-loop control of digital business, offering the best possible user experience, full lifecycle operations automation/autonomy and maximum resource utilization.

If you are not already a project member, you may join the Autonomous Networks project (in the

‘Core Project Area’) here

Members wishing to get involved in the Autonomous Networks project may access the working

area on the project Wiki in Confluence, here

See the meeting notes from Virtual Action Week, February 2021 here

MEETING TITLE: Establishing the 2021 roadmap for autonomous networks (Part 1 of 2) Tue Q0 OBJECTIVE: A working session to discuss the priorities for the Autonomous Network project, and to agree the roadmap for 2021 (and possibly beyond).

• Revisit and agree the autonomous networks vision • Define and agree our goals, activities and deliverables • Where possible, identify alignment with the Catalyst projects • Produce a prioritized plan for the year

OUTCOME: Ian Turkington (TM Forum) introduced this first of two sessions before passing over to Dong Sun (Futurewei) who presented an introduction to the Autonomous Networks vision, describing the 'Zero-X' Experience (zero-wait, zero-touch, zero-trouble), supporting Self-X (self-serving, self-fulfilling, self-assuring) network/ICT infrastructures and services. These are based on the TM Forum AN Framework of 3 layers + 4 closed loops with autonomous levels. Dong then summarized the work completed, the deliverables, and the Catalyst projects related to this topic. Kevin McDonnell (Huawei) reviewed the AN Roadmap, including a proposal to break the IG1230 Technical Architecture document into a suite of separate documents focusing on architecture principles, AN levels, and intent. Dave Milham (TM Forum) presented details of our Autonomous Networks Multi-SDO activities, summarizing the outcome of the initial workshop held on September 28th, 2020, and sharing plans for a further call on February 22nd, 2021. SESSION RECORDING: 2021-02-02 Tue Q0: AN: Establishing the 2021 roadmap for autonomous networks (Part 1 of 2)


https://engage.tmforum.org/projects/volunteer-opportunity-details?VolunteerOpportunityKey=603731cf-09c5-4229-8730-c900c157c07b

https://projects.tmforum.org/wiki/display/ANP/Current

https://projects.tmforum.org/wiki/display/ANP/ANP%3A+Meeting+Notes+-+VAW%2C+February+2021

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EUtASD8x-e5Pq7NeSCq78D8BETfnzrNLXy-jVmskv2d_4Q?e=IXAh64

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EUtASD8x-e5Pq7NeSCq78D8BETfnzrNLXy-jVmskv2d_4Q?e=IXAh64


of 35

MEETING TITLE: Establishing the 2021 roadmap for autonomous networks (Part 2 of 2) Wed Q4 OBJECTIVE: A working session to discuss the priorities for the Autonomous Network project, and to agree the roadmap for 2021 (and possibly beyond).

• Revisit and agree the autonomous networks vision • Define and agree our goals, activities and deliverables • Where possible identify alignment with the catalysts • Produce a prioritized plan for the year

OUTCOME: This meeting was a follow-up session during which the team looked at roadmap for AN. Themes covered were:

• General • Intent • AN ops (including use of AI) • Maturity levels • Domains • Closed loop

It was agreed that the objective of this collaboration group is to define best practices, standards and how-to guides to help factory build the Autonomous Networks.

Whereas the focus in 2020 was IG1230 (high level), this year the collaboration team is focusing on improving brevity, simplification to be more normative and focused. The goal is now to communicate the actual architecture.

SESSION RECORDING: 2021-02-03 Wed Q4: AN: Establishing the 2021 roadmap for autonomous networks (Part 2 of 2)


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EdjYHafR69hBkPx4pGdE4MwBOKzvEiDB9MMyndgqPqJIrQ?e=VZgSQe

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EdjYHafR69hBkPx4pGdE4MwBOKzvEiDB9MMyndgqPqJIrQ?e=VZgSQe


of 35

Business Assurance (BA) A new vision of the methods used to monitor and drive overall business performance and revenue, which:

• 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 the 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

Members wishing to get involved in the Business Assurance project may access the working area

on the project Wiki, Confluence, here


Summary of business assurance/revenue management Sessions at Virtual Action Week:

MEETING TITLE: 5G Business Assurance Risk Assessment Mon Q3 OBJECTIVE: Review the 5G Business Assurance Risk Matrix, to assess its completeness in a technical context. Evaluate the identified risks against the technical billing ability to offset these risks thereby creating business assurance in a 5G ecosystem context. OUTCOME:

• Team received feedback on the BA 5G Risk Matrix. • Next steps:

− Abinash Vishwakarma (Netcracker) to input additional information. − The team will study the 3GPP structure. − The team will add new models relating to 3rd party companies. − The team will also consider quality of experience for the network and end users as it

relates to billing and charging, and will do so in collaboration with the Customer Experience Management team

SESSION RECORDING: 2021-0202 Mon Q3 5G Business Assurance Risk Assessment

MEETING TITLE: Introduction to the Business Assurance (BA) project Mon Q4 OBJECTIVE: Presentation of the Business Assurance project within TM Forum. Open discussion about the challenges faced by business assurance professionals. Attract revenue assurance and business assurance practitioners to our collaborative work. OUTCOME: This session introduced business assurance to members not familiar with the ongoing work. The slides presented key business assurance topics including important standards and frameworks developed by the RA/BA team and displayed a selection of business assurance catalyst



https://projects.tmforum.org/wiki/x/soCWAw

https://projects.tmforum.org/wiki/x/5_0wCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EYpdlDXnYgZPsYbtDoxqpdIBHd4JM_ObINC959ak7zDBVw?e=lhIoGf


of 35

projects. The presentation also provided a list of references with links to the current BA suite of assets, as well as work in progress.

The team leads explained the day, time and goals of their weekly meetings, to allow potential new members the information necessary to consider joining this team. SESSION RECORDING: 2021-02-01 Mon Q4: Introduction to the Business Assurance Project

MEETING TITLE: Roadmapping the transition towards business assurance Tue Q3 OBJECTIVE: The aim is to present several best practices for successful transition towards BA and the major challenges on that way. The topics will arise around which preconditions need to be fulfilled, how to raise awareness amongst key stakeholders and how to obtain management support. The session should provide future BA professionals and managers a set of toolboxes and guidelines for transitioning towards BA. OUTCOME: The session covered recommendations for transitioning towards business assurance and outlined the challenges in making the transition successful. The session leaders shared their own experiences in the transition towards BA in their companies. An open discussion with the help of poll questions geared towards discovering what the triggers could be used to introduce business assurance. SESSION RECORDING: 2021-02-02 Tue Q3 Roadmapping the transition towards business assurance

MEETING TITLE Discovering new tools for business assurance Tue Q4 OBJECTIVE: Explore the dimension on new tools we should use in business assurance and how these can create and present new capabilities. OUTCOME: The Business Assurance team broke into two groups to begin identifying pain points that could be addressed by the identification of new tools and capabilities. Work will continue during the weekly project meetings. It is agreed that tool flexibility is necessary to align business assurance processes. SESSION RECORDING: 2021-02-02 Tue Q4: Discovering new tools and capabilities for Business Assurance

MEETING TITLE: Building the Business Assurance Maturity Model Wed Q3 OBJECTIVE: Update the approaches to assess the maturity from revenue assurance to unveil the state of business assurance dimensions – where they start and what the roadmap could be.

Updating the Revenue Assurance Maturity Model to meet the need of a questionnaire suitable for evaluating the progress and to support the evolution from revenue assurance by developing towards business assurance.

OUTCOME: Susi Winter (A1 Telekom) gave a detailed presentation on building the business assurance maturity model with a proposal on how the team could start the effort. This generated


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZqr3x49j3VEqn7u7Hm9bOABvtM8pIItYZQNeQEXxvehSQ?e=eNc2Zr

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ETzH5J7Vi01ArvmtfuCiYZkBpptx2swtsZVBTpixrqBmNQ?e=NZtxEE

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVA_sJtI26ZKksJwwICv8hMBfNy7WYIwHbEeQ9zbLC7OOA?e=bRJDNb

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVA_sJtI26ZKksJwwICv8hMBfNy7WYIwHbEeQ9zbLC7OOA?e=bRJDNb


of 35

good discussion points ending with agreement that this was probably a two-year process, but the goal would be a draft in about one year. SESSION RECORDING: 2021-02-02 Wed Q3: Building the Business Assurance Maturity Model

MEETING TITLE: Creating a Business Assurance Survey Wed Q4 OBJECTIVE: Assess the maturity of business assurance within the telco. This is a platform for building the Business Assurance Maturity Model. OUTCOME: The team had an active session resulting in considerations to be considered/integrated into the new survey, so that we can gauge the level of awareness and adoption of business assurance principles and functions within organizations. We also established key timing, with the survey to be rolled out early May 2021, and the publication of results targeted for early November 2021. The team agreed to continue discussions in the weekly project team meetings. SESSION RECORDING: 2021-02-02 Wed Q4: Creating a Business Assurance Survey

MEETING TITLE: IoT and business assurance Thu Q4 OBJECTIVE: Developing capabilities to mitigate against future risks OUTCOME:

• The team was taken through the importance of IoT and its challenges and opportunities for CSPs, DSPs and verticals.

• We addressed and discussed the elements of business assurance within a digital ecosystem, supported by use cases in remote patient monitoring and cold chain logistics as examples.

• Next steps will be to continue this discussion within Business Assurance project calls and decide on a way forward for addressing this important issue.

SESSION RECORDING: 2021-02-02 Thu Q4: IoT and Business Assurance


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EQXYXYkqBfJHiL-w3nzGvJIBpEfifHwuSBZIR4EswAB4kA?e=CcO9OC

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/Edi7Um2uUItCsBbdXGTaI64BPj_5qeQHkgVch3pT2lEzAA?e=n5Spix

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ET5TxNXcEHdCkdJOLRuNN7QBeeQcPNXsK6Lv36jP-Up9qA?e=mKjPrt


of 35

Customer Experience Management (CEM)

TM Forum’s Customer Experience Management (CEM) project group is where TM Forum members

collaboratively develop the best practices, tools and blueprints that enable service providers to

define their customer management strategy, improve brand loyalty, grow revenue, increase

retention rates and reduce costs across their full range of services. We have tools to map and

measure the experience both from the provider’s as well as the customer’s point of view. In an

increasingly digitized and connected world, customer experience is complex and needs to be viewed

from multiple perspectives across the value fabric.

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

project (in the ‘Application Project Area’) here

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

Wiki in Confluence here


Summary of Customer Experience Management sessions at Virtual Action Week:

MEETING TITLE: CEM Workshop: Driving towards intent-based customer engagement Wed Q4 OBJECTIVE: Review of Intent Oriented customer Engagement and review of IG1234 IoCE Whitepaper draft OUTCOME: This session showcased a new workstream within the CEM project that is developing a methodology for CSPs to engage with customers through real-time decisions instead of following present day methodology where customer requests and queries go through a fixed process flow involving systems, people and departments, thus taking considerable time and effort. With a solid attendance of 30+ members, attendees were briefed on the CEM project mandate and objectives, and we provided a brief overview of the intent-oriented customer engagement (IoCE) definition and principle. The team was then led through the CSPs’ need for transformation their customer engagement, the IoCE customer journey and the key functional blocks on how to implement IoCE. Further IoCE insights were shared including the key ingredients needed for successful IoCE, the current state of the project plan for IG1234 - IoCE whitepaper, including the initial deliverables from the team on this work. The team also outlined the TM Forum vision for the future deployment of IoCE and answered a number of questions from the audience on synergy with other TM Forum projects that feature ‘intent’ including APIs and Autonomous Networks. Five polls were also run throughout the session to capture audience feedback on key aspects of IoCE including customer engagement maturity, CSP readiness for efficient customer engagement for 5G services, average response times by CSPs to customers, the audience’s perception on the importance of IoCE in the future, and the propensity of the audience to learn more about IoCE and become involved in the CEM project.

In summary, the CEM project team received great feedback on the IoCE work and gained new interest from members to become involved in developing IoCE further. SESSION RECORDING: 2021-02-03 Wed Q4: CEM Workshop: Driving towards intent-based customer engagement



https://projects.tmforum.org/wiki/x/DoDjAQ

https://projects.tmforum.org/wiki/x/hKIwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ETMRlzlq6OhIvofr1qd3L7kBTXKMFFolVexWPB8EsRA6Uw?e=g8InZ2

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ETMRlzlq6OhIvofr1qd3L7kBTXKMFFolVexWPB8EsRA6Uw?e=g8InZ2


of 35

MEETING TITLE: Creating the future of customer experience in a 5G world Thu Q0 JOINT: CEM, Beyond Connectivity-Business Assurance, Cloud Native IT & Agility-Frameworx OBJECTIVE Scoping out the future program with all interested teams

OUTCOME: The Customer Experience Management (CEM) project team hosted a cross-team session

at Virtual Action Week with the Business Assurance and Frameworx teams to discuss and compare

traditional CEM with future CEM in a 5G context and to identify parameters and requirements to

satisfy future customer needs and desires.

With 41 members in attendance, the session kicked off with a poll that explored the importance of

CEM within organizations, CEM KPIs and measurement, and how eTOM can reflect customer

experience in the context of 5G. The CEM team then talked through a high-level view of current and

future aspects of CEM including the need for more successful engagements, gamification in

customer journeys, intent orientation journeys and intent oriented customer engagement. A further

overview was shared on the difference between traditional and future customer experience and

how these future approaches improve business and IT processes. The presentation then highlighted

the consequences of these new approaches to CEM where digital transformation demands a variety

of customer journey data processing. These consequences include CSPs evolving from a

communications company to an experience company, CEM in eTOM, data processes and KPIs, the

need for a CEM data framework as well as the need for cohesion between business assurance,

customer experience assurance, CEM and eTOM. The discussion then centered around the

outcomes and ‘call to action’ for the teams who identified the need for 1) An overview of

collaboration work and Catalyst projects on the customer journey over the last two years, 2) An

overview of all the documentation that the teams have produced e.g., guidebooks, whitepapers and

3) More work needed on data curation.

In summary, this session resulted in the teams mapping out some key deliverables to support future customer experience and customer journey management. SESSION RECORDING: 2021-02-04 Thu Q0: Creating the future of customer experience in a 5G world

MEETING TITLE: Gamification – one more way to improve telecom customer experience Thu Q3 JOINT: CEM, Beyond Connectivity - 5G Monetization, Cloud Native IT & Agility - Frameworx-eTOM OBJECTIVE: Provide an overview of the work that has been done around the customer journey gamification in the CEM community and collect wider audience feedback for the role of gamification in enhancing telecoms. OUTCOME: With 21 members in attendance, the session launched with a poll question to gauge the levels of awareness of gamification in telecoms. The CEM team then presented an overview of gamification, why it is important to customer experience and how it is applicable to the telco business. Attendees also received an update on the Catalyst project ‘Ready Telco One’ that featured gamified customer journeys enabled by a dynamic partner ecosystem and marketplace. The latest asset produced by the CEM Team IG1205 Gamification and Continuous Communication with Customers Whitepaper v1.0.0 was also highlighted. The CEM team then outlined the deliverables that they plan to work on during 2021 which includes updating IG1205 - Developing a Technical


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZqPa3C_pBZCqEqV2HTipWQBdhHbqb3YunhyNT-i4uMVHA?e=YqNKvh

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZqPa3C_pBZCqEqV2HTipWQBdhHbqb3YunhyNT-i4uMVHA?e=YqNKvh


of 35

Specification for Gamified Customer Journey in a DSP ecosystem, and also updating GB1006 - Customer Experience Management Guidebook. Attendees were then invited to take part in two further poll questions that asked if attendees know if any CSPs already have a gamification solution and, if so, is it a ‘game changer’ for customer journey management/customer experience management.

In summary, this session was well received and elevated the topic of gamification in customer experience with members. Members were also invited to join the CEM project team and work with them to help develop the new gamification assets identified for 2021.

SESSION RECORDING: 2021-02-04 Thu Q3: Gamification - one more way to improve telecom customer experience


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EUHWUXNXTvFFkwH16KY7-rgB6Dkc1-AWFmzwJe9xe3x4LA?e=Dji1CG

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EUHWUXNXTvFFkwH16KY7-rgB6Dkc1-AWFmzwJe9xe3x4LA?e=Dji1CG


of 35

Digital Ecosystem Management (DEM)

The Digital Ecosystem Program champions the telco industry and builds the cross-industry relationships to enable co-innovation opportunities with the ultimate ambition to reduce friction and barriers of growing new business.

It does this by bringing together industry verticals, forging relationships with industry organizations, companies, academia and governmental bodies to deepen the understanding of any challenges and needs, ensuring that the relationship opportunity and technical infrastructure allow for ease of partnering and delivery of cross industry services.

TM Forum’s Digital Ecosystem Management project focus has been on business architecture practices, driven by identifying business capabilities and ecosystem business capabilities to drive the applied IoT assets needed to offer complex digital services in a vibrant digital economy:

• Through open collaboration among members, TM Forum provides how-to guidance to both

business and technical users who need to rapidly design, implement, operate and monetize

digital services with partners in intricate and extensive open digital ecosystems.

• With the rapid development of the ecosystem economy, organizations need to gain a

holistic view of roles, relationships, business models, value flow, etc., and share a common

vision of the end service being delivered. To move from small scale proof of concept to mass

market industrialization of the Internet of Everything (IoE), the right systems and processes

need to be assured; and to make sure organizations have the right technical resources in

place, they need to first understand the business requirements and capabilities to be

delivered.

If you are not already a project member, you may join the DEM project (in the ‘Application Project

Area’) here:

Members wishing to get involved in the DEM project may access the project page, here:

See the meeting notes from Virtual Action Week, February 2021 here:

MEETING TITLE: 5G Network Slice Monetization Mon Q2 OBJECTIVE: This meeting presents the work of this collaboration group and asks participants for input and guidance. OUTCOME: Consensus reached on the direction and scope of work for IG1179A: Network Slice Monetization V1.0.

The team received feedback on key points around the categorization of slice-based offerings, utilizing third party models and addressing the quality of experience for the network and customer. The 5G Monetization project team will discuss the feedback received during their weekly project call on 15 Feb 2021 and incorporate new insights into the work of IG1179A: Network Slice Monetization v1.0 which is due to be published in sprint 2.

SESSION RECORDING: 2021-02-01 Mon Q2: 5G Network Slice Monetization



https://projects.tmforum.org/wiki/x/s4HjAQ

https://projects.tmforum.org/wiki/x/t-MwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/mmusillo_tmforum_org/Ea-qiqZApn1ElS3PbuuTXLIBurScT_9p_NK8D8ig_5bDeA?e=aEdxv5


of 35

MEETING TITLE: Digital ecosystem playbooks: Connectivity as-a-service (Parts 1 and 2 of 3) Tue Q3 & Q4 OBJECTIVE: This new business focused workstream will develop practical guidance in the form of playbooks for connectivity-as-a-service (CaaS). This is a workshop style session using design thinking methodologies.

CSPs need to dramatically improve the ease with which they offer connectivity services to their enterprise customers. This playbook will provide the blueprint for how to realize this ambition.

OUTCOME: • Gained a broader and deeper understanding of CaaS from multiple persona perspectives. • Agreed an outline structure for the playbooks. • Reviewed and agreed a series of CaaS use cases. • Captured the first iteration of a CaaS definition. • Onboarded new members to the project. • Agreed a timeline and way forward for sprint 2.

SESSION RECORDING: 2021-02-02 Tue Q3 & Q4: Digital Ecosystem Playbooks: Connectivity-as-a-Service (Parts 1 & 2 of 3)

MEETING TITLE: Digital Ecosystem Playbooks: Zero-Touch Partnering (ZTP) Wed Q1 OBJECTIVE:

• This new business focused workstream will develop practical guidance in the form of playbooks to help enable zero-touch partnering.

• Empower firms with the ability to manage partnerships safely, onboard partners easily, and manage them through their lifecycle right through to the ability to manage revenue share and settlement in a complex ecosystem will be a core competency required in the future.

• This session will continue the development of the blueprint to realize this ambition. OUTCOME:

• Reviewed a comprehensive definition and capture of the scope and boundary of zero touch partnering. While there was some discussion around the inclusion of additional aspects such as end-to-end lifecycle management, the presentation brought great clarity to the way forward regarding zero touch partnering. This will be used to frame the playbook and members are welcome to comment to help refine the language.

• Reviewed the definition of the Zero Touch Partnering Maturity Model and the need to include business and technical rules and cover multiple, varied perspectives. A tailored version of this work based on feedback will be included in the playbook for zero touch partnering.

• New team members were onboarded, and work will continue through the Thursday ‘Ecosystem Playbooks’ sessions

SESSION RECORDING: 2021-02-03 Wed Q1: Digital Ecosystem Playbooks: Zero-Touch-Partnering (ZTP)


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EZi1xa-Z7NlClK3NLgN9x8QB6vkWNb7czQsoeQrUB4oyqQ?e=eu62TS

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EZi1xa-Z7NlClK3NLgN9x8QB6vkWNb7czQsoeQrUB4oyqQ?e=eu62TS

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ES5rDijBdTxDo_jLIYEdfPUBD6e8PnmtCQfSv1YssNN0xg?e=yNjuzx

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ES5rDijBdTxDo_jLIYEdfPUBD6e8PnmtCQfSv1YssNN0xg?e=yNjuzx


of 35

MEETING TITLE: Digital ecosystem playbooks: Connectivity as-a-service (Part 3 of 3) Thu Q2 JOINT: ODA OBJECTIVE: This is a cross-functional meeting Connectivity-as-a-Service Playbook and ODA Ecosystems Enablement to ensure alignment and harmonization of activities. OUTCOME:

• The Digital Ecosystem Component Suites team and the ODA Ecosystem Enablement team had a cross-functional session where details of work items, current and future focus and scope of work were shared as it relates to connectivity-as-a-service (CaaS).

• The teams discussed definitions and various perspectives of CaaS, including the customer and telco points of view.

• The teams concluded that regular catchups between each other would be useful, and that there is a lot of work to be done in first defining CaaS and its scope.

SESSION RECORDING: 2021-02-04 Thu Q2: Digital Ecosystem Playbooks: Connectivity-as-a-Service (Part 3 of 3)


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EQvCfp5rT05Dj1DzHQPJnpYBPkKHRqAz3wmXI2yBxXSZaQ?e=rnXdFx

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EQvCfp5rT05Dj1DzHQPJnpYBPkKHRqAz3wmXI2yBxXSZaQ?e=rnXdFx


of 35

Digital Maturity Model (DMM) The digital revolution brings significant opportunities and threats, impacting every industry. Communication Service Providers (CSPs) can embrace significant growth opportunities by looking beyond connectivity. At the same time, commoditization and digitalization of connectivity services have created an urgency to dramatically simplify and transform the efficiency of existing business. To help TM Forum members navigate this complex digital transformation journey, leading CSPs and global consultancies have worked together in a collaboration project to develop the definitive telecommunications industry standard Digital Maturity Model (DMM) and a set of key strategic KPIs.

If you are not already a project member, you may join the Digital Maturity Model project (in the

Application Project Area) here:

Members wishing to get involved in the DMM project may access the project Wiki in Confluence

here:

See the meeting notes from Virtual Action Week 2021 here:

MEETING TITLE: Linking architectural transformation (ODA) to digital maturity and the need for new skills and capabilities (Part 1) Wed Q1 JOINT: Digital Organizational Transformation (DOT), Open Digital Architecture (ODA) OBJECTIVE: Creating a skills and cultural framework and linking the two teams together, including ODA to enable mapping for architectural migrations of the ODA with DMM. OUTCOME: The Digital Maturity Model & Metrics project team hosted a cross-team session with the Open Digital Architecture project team at Virtual Action Week. The primary aim was to identify synergies between both teams to enable mapping for architectural migrations of the ODA with the DMM. With 32 members across both teams participating in this session, the DMM team provided attendees with a comprehensive presentation that started with an overview of the DOT project team’s work that looks at the people aspect of digital transformation. Attendees were then shown the ODA lifecycle model that shows the journey for digital transformation. The latest DMM structure was also shared, and the teams reviewed the telco industry’s challenges, and looked at how the DMM can help CSPs address those challenges in becoming a digital service provider.

The teams were then presented with some real-life examples of ODA in action from Vodafone and operating design skills transformation from Detecon. Vodafone shared its experience in deploying ODA, highlighting the need for change, discussing how it approached transitioning to ODA and laying out its current focus areas for its transformation team. Detecon shared their Operating Model design and their newly developed IHUB that helps organizations with skills transformation.

In summary, the DMM and ODA cross-team session was a great success and resulted in five key areas to explore for future development. SESSION RECORDING 2021-02-03 Wed Q1: DMM: Linking architectural transformation (ODA) to digital maturity and the need for new skills and capabilities (Part 1)



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

https://projects.tmforum.org/wiki/x/eKIwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/Ef9qoHSctp9IovgOx9k1fogBD5qZ_-9nB0vDjfDoXIcNjQ?e=reif6p

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/Ef9qoHSctp9IovgOx9k1fogBD5qZ_-9nB0vDjfDoXIcNjQ?e=reif6p


of 35

Digital Organizational Transformation (DOT) The telecoms industry is in a catch-22: New digital architectures, processes and work practices such as Agile software development, DevOps, cloud and microservices can help communications service providers (CSPs) address the pressure they’re under to cut costs and find new sources of revenue, but organizational silos and cultural issues like hierarchies, red tape and aversion to risk are standing in the way. There is widespread acknowledgement among CSPs that culture is the biggest barrier to transformation, but this does not mean it is an easy problem to address. In the latest TM Forum Digital Transformation Tracker on culture, 75% of CSP respondents believe culture and organizational issues are a very serious or moderately serious challenge to digital transformation. The biggest challenges they identified is that they are too hierarchical with 50% of respondents acknowledging this. Until CSPs flatten their organizations and devolve decision-making, they will be unable to take risks and innovate. Indeed, less than 15% of CSP respondents believe that their companies are agile or innovative. For CSPs’ digital transformation to be a success and not to fall into the 70% failure bucket, they urgently need to undergo not only technological and operational transformation but also address and align cultural, talent and organizational transformation. Digital Organizational Transformation project TM Forum is leading the communications industry in digital organization and talent transformation by creating a range of best practices, thought-leading collaboration activities, and research, in addition to services such as training and coaching to get you started.

If you are not already a project member, you may join the Digital Organizational Transformation

project (in the ‘Applications Project Area’) here

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

Wiki in Confluence, here


Summary of Digital Organizational Transformation Sessions at Virtual Action Week -

MEETING TITLE: Identifying the human and organizational factors impacting our transformation activities Wed Q0 JOINT: DMM, FX, AI OBJECTIVE: Mapping skills with current and future needs and how to effectively manage talent pooling (Part 1) OUTCOME: Identified a skills repository as a possible work item for 2021

SESSION RECORDING: 2021-02-03 Wed Q0: Identifying the human and organizational factors impacting our transformation activities



https://projects.tmforum.org/wiki/x/hELVBg

https://projects.tmforum.org/wiki/x/8vIwCQ

https://projects.tmforum.org/wiki/display/OTCT/2021-02-03+Wed+Q0%3A+Identifying+the+human+and+organizational+factors+impacting+our+transformation+activities

https://projects.tmforum.org/wiki/display/OTCT/2021-02-03+Wed+Q0%3A+Identifying+the+human+and+organizational+factors+impacting+our+transformation+activities


of 35

Diversity & Inclusion Program (DIP) The TM Forum Diversity and Inclusion Council has been developing a single industry wide metric to capture organizational performance in inclusion and diversity. The workshop aims to share the work and plans so far to gather inputs and insights to support the development of the score through to pilot stage.

Members wishing to get involved in the DIP project may contact Vicky Sleight

([email protected])


MEETING TITLE: Designing the Diversity Promotor Score Model (DPS) Wed Q3 OBJECTIVE: To further define a simple metric that can be applied across the industry to catalyze change. It will allow operators to measure and track the results of their diversity, equality and inclusion initiatives against industry peers. OUTCOME: The Diversity & Inclusion council presented the Diversity & Inclusion Score (IDS) in an open session. A mini-workshop was hosted through the Mural digital workspace, where all session participants gave their feedback on the proposed IDS question. An open discussion was held on the feedback from the mini workshop, with the following outcomes:

• The D&I council would review the feedback and make amendments to the proposed question.

• IDS to be launched at the end of February 2021 as a pilot.

SESSION RECORDING: 2021-02-03 Wed Q3: Designing the Diversity Promotor Score Model (DPS)


https://projects.tmforum.org/wiki/x/S-kwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ES4D6ReYnXlEvfC5QqJuOsEBWjEpv5Qq7U6u_IyuSriXzg?e=GpdUWH


of 35

Frameworx (FX) Frameworx provides the fundamental building blocks for digital transformation based on a proven history of enabling business transformation through numerous major technology changes. 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. Frameworx resources include:

• 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.

• Best Practices: Practical guides to support implementation.

• 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

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

project Wiki in Confluence, here


Summary of Frameworx sessions at Virtual Action Week -

MEETING TITLE: Reviewing eTOM Contributions Tue Q1 OBJECTIVE: Review pending eTOM contributions, prioritize work

OUTCOME: In this session, changes were suggested for eTOM, actual suggestions were discussed,

and dates were set for the full changes to be submitted. We now have a clear view of the next release. The meeting enabled attendees to understand the needed improvements. SESSION RECORDING: 2021-02-02 Tue Q1: Reviewing eTOM Contributions

MEETING TITLE: Review SID Contributions Tue Q2 & Q3 OBJECTIVE: Review pending SID contributions, prioritize work

OUTCOME: This was a very productive meeting in which we have ensured we have a clear

understating of our planned changes in the upcoming release.

We have looked at each of the change requests and ensured we have agreement on any necessary

action.

We agreed on planned changes and discussed options, reaching a consensus where needed. SESSION RECORDING: 2021-02-02 Tue Q2 & Q3: Reviewing SID Contributions



https://projects.tmforum.org/wiki/x/nos6Ag

https://projects.tmforum.org/wiki/x/4KEwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/Ef9GbLUQ_f9DnUG-tIv0aD8BTmwDocoqVL-nl8b0LVrKVA?e=hchrIR

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ETdJGBh1D7ZHsXiNjXQ4V2cB5_cQvIMUZtWajD8-I7TXpA?e=2RsEMj


of 35

MEETING TITLE: Understanding and governing the catalogs and libraries which underpin ODA Thu Q4 JOINT: AI, API, DEM, ODA OBJECTIVE: ODA is underpinned by a set of interrelated catalogs and libraries. This session will bring together the projects who produce, maintain and consume the data in these catalogs; to improve understanding of the high-level model, and agree governance principles.

• Agree a high-level model of the catalogs and their relationships.

• Agree the catalog ownership and responsibilities.

• Define the key catalog ownership principles (i.e., ownership of mappings)

• Establish initial catalog governance process for changes to the catalogs and relationships.

OUTCOME: An important meeting that discussed the version for a well governed, all-encompassing collaboration in the area of mapping and coordination. This will include ODA, APIs, Frameworx and the Business Capabilities. Additionally, Andrew Greff (Telus) shared his new streamlined version of the metamodel. We have agreed further work in this area and plan to create a team to drive this work. SESSION RECORDING: 2021-02-04 Thu Q4: FX: Understanding and governing the catalogs and libraries which underpin ODA


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EbjU1bWnlvZPiQ1_42XixfsBMypFLMpnNYtdnX8h4TFY0Q?e=MrAahL

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EbjU1bWnlvZPiQ1_42XixfsBMypFLMpnNYtdnX8h4TFY0Q?e=MrAahL


of 35

Open APIs (API)

The TM Forum API Ecosystem is a family of APIs that make 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.

In the age of the digital economy, services are typically delivered through a sophisticated partnering of multiple providers who are all using different systems and interfaces. 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: 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

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

Wiki, Confluence, here:

See the meeting notes and working calls from Virtual Action Week here

Summary of API Sessions at Action Week:

MEETING TITLE: Alignment of digital identity and party role specification with the Information Framework team (SID) Mon Q4 JOINT: ODA, FX, AI OBJECTIVE: Presentation and review of new APIs for authentication and its relationship to the Party model. OUTCOME: Ludovic Robert (Orange) presented details of a proposal by Deutsche Telekom and Orange members for a new Digital Identity Management API. This requirement was identified during the preparation of the IG1228 ODA/API Call Flow Use Cases.

Cécile Ludwichowski (Orange) shared the current context of Identity in SID 20.5 and explained that a new Digital Identity aggregate business entity (ABE) is proposed, located in the Common Domain, replacing the current Users & Roles ABE. A second change request will specify the addition of a Permission ABE. An improvement to ContactMedium is also proposed.

Gregoire Laurent (Orange) shared a proposal to introduce a PartyRole specification entity and link UserRole to PartyRoleSpecification to ease permission management depending on the party role.

SESSION RECORDING: 2021-02-01 Mon Q4: API: Alignment of digital identify and party role specification with the Information Framework team (SID)



https://projects.tmforum.org/wiki/x/BQXvAQ

https://projects.tmforum.org/wiki/x/F48wCQ

https://www.tmforum.org/resources/reference/ig1228-oda-api-call-flow-use-cases-v2-1-0/

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EfbaiXL5zwdCrrZLDT46XsgB5oHO2_pfrZfkVICPatftMA?e=1mDCao

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EfbaiXL5zwdCrrZLDT46XsgB5oHO2_pfrZfkVICPatftMA?e=1mDCao


of 35

MEETING TITLE: Review of proposals for new APIs Mon Q5 OBJECTIVE: To review and discuss new APIs identified and proposed by members within the API project. OUTCOME: Pierre Gauthier (TM Forum) opened this project meeting with a summary of plans for new APIs and API Suites, new features and patterns including Domain Context Schemas, and a transition to the OpenAPI Specification (OAS 3.0) for Version 5.x. Ludovic Robert (Orange) presented detailed proposals for a Process Flow Orchestration API (TMF719) to complement the TMF701 Process Flow API. SESSION RECORDING: 2021-02-01 Mon Q5: API: Review of proposals for new APIs

MEETING TITLE: Bringing the AI reference architecture and AI model data sheets to life with TM Forum Open APIs Tue Q3 JOINT: API, AN, AI OBJECTIVE:

• Developing the suite of APIs to bring the reference architecture to life (alarm correlation & traffic flow optimization

• Addressing how to automate the capture of data into the AI Model Data Sheets. • How to enable the Data Sheets to become a live document to capture its life history,

specifically – what API interfaces are needed?

OUTCOME: This session provided an overview of work being carried out by the AI collaboration team on the AI reference architecture and data sheets and the API collaboration team. The objective was to present the work with next steps and actions to be determined during the subsequent Virtual Action Week session on Friday.

Questions around trust and knowing when AI models are "good enough" came up; no answers were determined.

SESSION RECORDING: 2021-02-02 Tue Q3: API: Bringing the AI reference architecture and AI model

data sheets to life with TM Forum Open APIs

MEETING TITLE: Agreeing the API delivery process with the delivery team Tue Q4 JOINT: API, PMO OBJECTIVE: Use of Confluence, JIRA, GitHub and other tools for the governance, planning and delivery of API assets. OUTCOME: Alexis de Peufeilhoux (DT) introduced the session by identifying the problem statement and sharing ideas to resolve this, including treating the API User Guide and Conformance Profile documents as software. To evaluate this, a pilot was set up to edit and publish the TMF630 Design Guidelines from code. Editing takes place in the Git repository in source format (AsciiDoc, PlantUML, JSON…). Jira items match to branches in the Git repository. GitHub orchestrates the review and approval processes and generates the PDF documents outside of the repository. Output can also be generated as HTML.


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZ71WT2RsT1GqcN4Od0bNdwB2SvukJ7lL_dVn4vBnSIsow?e=3N5ifm




of 35

Knut Johannessen (Telenor) demonstrated how a similar process could be applied to the API User Guides and Conformance Profiles. John Gillam (TM Forum) discussed ideas to make the many TM Forum assets more easily accessible and consumable, which is consistent with the proposals from the API team. SESSION RECORDING: 2021-02-02 Tue Q4: API: Agreeing the API delivery process with the delivery team

MEETING TITLE: Open API workshop to create first version of the v5.0 schema Wed Q5 OBJECTIVE: Schema domain mapping validated, and schema pattern guideline validated OUTCOME: Ludovic Robert (Orange) presented an overview of work to date on the new schema patterns and domain context specialization (DCS) including the API Resource Representation Definition - Mandatory Representation (MR), Data Transfer Representation (DTR), Lifecycle Representation (LR), Editable Representation (ER). and Schema Definitions - Core Schemas, Generic Context (GC) Schemas, Specialized Schemas (TMF & SDO). Henrique Rodrigues (TM Forum) updated the schema directory to separate Core, GC, and TM Forum directories for the new GC schema design pattern. Joel Burgess (Oracle) - Shared the latest status of the tooling for OAS 3.0 Generation. Starting with the Schema, applying the Rules, and generating the OAS document. SESSION RECORDING: 2021-02-03 Wed Q5: API: Open API workshop to create first version of the v5.0 schema MEETING TITLE: Understanding the digital ecosystem requirements on the Open API team

Thu Q3 JOINT: API, DEM, ODA OBJECTIVE: Review requirements for a Zero-Touch Partnership & Connectivity Service API Suite OUTCOME: Pierre Gauthier (TM Forum) opened this session with an overview of GB1017 IoT Platform Reference Architecture v1.0.0 the FIWARE TMF Business API Ecosystem and the Zero Touch Partnering Architecture. The plan is to update the TMF650 Onboarding Management API as part of an API Component Suite. It was agreed that TR217 Partnership Revenue Models V0.5.2 and TR211 Online B2B2X Partnering Step by Step Guide R18.0.1 may be updated and/or used as reference documents. Members were invited to contribute to the requirements definition and to participate in the development of the APIs. SESSION RECORDING: 2021-02-04 Thu Q3: API: Understanding the digital ecosystem requirements on the Open API team


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ETdIbRLpyYVAgmXi1NYp8jIBrJstZT_ChNOC7vVhOILBlA?e=LniIwP

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ETdIbRLpyYVAgmXi1NYp8jIBrJstZT_ChNOC7vVhOILBlA?e=LniIwP

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EaF50Eh02f5OhbOgBqwdTicB60Tb_nLc0c260aLdGxZ4zA?e=0HYhn8

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EaF50Eh02f5OhbOgBqwdTicB60Tb_nLc0c260aLdGxZ4zA?e=0HYhn8

https://projects.tmforum.org/wiki/display/PUB/GB1017+IoT+Platform+Reference+Architecture+v1.0.0

https://projects.tmforum.org/wiki/display/PUB/GB1017+IoT+Platform+Reference+Architecture+v1.0.0

https://fiwaretmfbizecosystem.docs.apiary.io/#reference/asset-type-management-api

https://projects.tmforum.org/wiki/download/attachments/154204732/210204%20Understanding%20the%20digital%20ecosystem%20requirements.pptx?version=1&modificationDate=1614070393000&api=v2

https://projects.tmforum.org/wiki/download/attachments/154204732/210204%20Understanding%20the%20digital%20ecosystem%20requirements.pptx?version=1&modificationDate=1614070393000&api=v2

https://www.tmforum.org/resources/specification/tmf650-onboarding-management-api-rest-specification-r16-0-1/

https://www.tmforum.org/resources/technical-report-exploratory-report/tr217-partnership-revenue-models-v0-5-2/

https://www.tmforum.org/resources/technical-report/tr211-online-b2b2x-partnering-step-by-step-guide-r18-0-0/

https://www.tmforum.org/resources/technical-report/tr211-online-b2b2x-partnering-step-by-step-guide-r18-0-0/

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EecIAM8ljbVClcMIfwr_cqkBInmJ25NOeibWo4HJFuL7hQ?e=l1YI0z



of 35

MEETING TITLE: Reviewing the proposed API suite for edge computing Thu Q5 OBJECTIVE: Review requirements for an Edge Computing as a Service (ECaaS) management API Suite OUTCOME: Pierre Gauthier (TM Forum) opened the discussion by sharing the ECaaS document contributed by Xosé Ramon Sousa Vazquez (Optare Solutions) as JIRA submission AP-2369. This is based on the 2020 Catalyst project 'The Edge in Automation'. Johanne Mayer (MayerConsult) presented details of the project and the proposal to create an API Component Suite for ECaaS. This led to a healthy debate regarding the pros and cons of this solution. It was agreed that the proposed implementation made sense and might be achieved without any new APIs. SESSION RECORDING: 2021-02-04 Thu Q3: API: Understanding the digital ecosystem requirements on the Open API team

MEETING TITLE: Defining the API closed loop suite Fri Q3 JOINT: API, AI (Closed Loop) OBJECTIVE:

• Input: Looking at anomaly detection from AI requirement • Output: The API profile suite

OUTCOME: In this cross-project meeting the teams shared some of the requirements they are currently working on for closed loop. The next step is to define a suite of APIs for closed loop using the API profile document TMF909 as a template to capture requirements and figure out the domain entities that need to be addressed/exposed, with the goal to manufacture APIs for those domain entities. All agreed that we want the whole team participating in the process or at least be part of the governance process of this closed loop set of APIs. There will be a joint meeting scheduled in the next two-week timeframe. SESSION RECORDING: 2021-02-05 Fri Q3: API: Defining the API closed loop suite


https://projects.tmforum.org/jira/browse/AP-2369



https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EXifHL00PZdHo4r4W5zuIgIBhLCT_v0vVtiou6JC3SREfQ?e=dBWBFX


of 35

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. Read the latest white paper on ODA here:

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

here

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

Wiki, Confluence, here

See the meeting notes from Virtual Action Week, February 2021 and working calls here

Summary of ODA Sessions at Action Week:

JOINT: AI, AN, API, BA, BAR, CEM, DEM, DMM, DOT, FX, IoT, ODA Mon Q0 & Q1 MEETING TITLE: Enabling a blueprint for intelligent operations fit for the 5G era (Part 1 and 2) OBJECTIVE: Introduction to the collaboration projects OUTCOME: George Glass (TM Forum) and Theme Leads, Ian Turkington, Aaron Boasman-Patel, Joann O'Brien and Vicky Sleight got Virtual Action Week off to a flying start with these very well attended sessions, providing a comprehensive overview of current and planned activities within these projects. The sessions concluded with a panel discussion / Q&A hosted by Aaron. SESSION RECORDING: 2021-02-01 Mon Q0 & Q1: ALL: Enabling a blueprint for intelligent operations fit for the 5G era

MEETING TITLE: Bringing collaboration projects together to support the Open Digital Architecture (ODA) (Part 1 of 2) Mon Q2 & FRI Q2 JOINT: AI, AN, API, BA, BAR, DMM, FX OBJECTIVE: ODA spans several interdependent TM Forum collaboration projects, (Frameworx, Open APIs, AI & Data Analytics, Business Architecture and of course the ODA project itself). It is essential that these projects work together to produce a consistent reference architecture. This session will bring the team together to ensure better collaboration, and more specifically:

• Ensure we have common understanding of the scope of ODA, and the deliverables which are

required to document this reference architecture.


https://www.tmforum.org/resources/whitepapers/open-digital-architecture/


https://projects.tmforum.org/wiki/x/s6JHBQ

https://projects.tmforum.org/wiki/x/aJAwCQ

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EWf5nESjSbVBv0asqC8U794B4E1KSa6cX65DWM0bcmwTGw?e=xeIMBy

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EWf5nESjSbVBv0asqC8U794B4E1KSa6cX65DWM0bcmwTGw?e=xeIMBy


of 35

• Understand the repositories which underpin ODA (including but not limited to Frameworx).

• Ensure the projects together fully support ODA, and to propose any changes required.

OUTCOME: In this first of two sessions, Ian Turkington (TM Forum) brought together workstream leaders and representatives from the ODA, AI, API, Autonomous Networks, Business Architecture, and Frameworks projects to review and discuss how the teams can work together to improve the complete ODA Reference Architecture. Specifically, incorporating total ODA Governance, extending the scope of Frameworx to include all our repositories, and ensuring that responsibility for the content of the repositories lies with the relevant owning project. Proposed changes include establishing an ODA Functional Architecture project which incorporates the current ODA Functional Architecture and ODA Production workstreams; establishing a Components, Implementation & Deployment project incorporating the current ODA Technical Architecture and ODA Reference Implementation workstreams - working closely with the ODA-CA and API projects; a new Total ODA Project Governance project incorporating the current ODA Transformation Guides and ODA Security & Privacy workstreams; merging the current ODA Ecosystem Enablement workstream into the Digital Ecosystem Management project.

This popular and highly interactive session generated numerous questions and responses which were captured in the Zoom chat log attached to the meeting notes.

SESSION RECORDING: 2021-02-01 Mon Q2: ODA - Bringing collaboration projects together to support the Open Digital Architecture

MEETING TITLE: Connecting Open APIs to realize ODA with API call-flows (IG1288) Mon Q3 JOINT: ODA Functional Architecture (ODA-FA), API, ODA Reference Implementation (ODA-RI), ODA Technical Architecture (ODA-TA) OBJECTIVE: To achieve alignment between ODA-FA, ODA-RI and API and prioritize backlog of ODA-FA/API call-flows for year 2021 OUTCOME: All the session objectives were achieved and, in some respects, exceeded.

• Reviewed - The work reported in ODA Presentation on connecting API to realize ODA API call Flows by Sylvie Demarest (Orange), Alexis de Peufeilhoux (DT), Ludovic Robert (Orange) and Konstantin Petrosov (DT)

• So that - TM Forum Membership is informed about progress, impacts and requirements on both ODA and Open APIs; and to encourage further member participation in addressing the use case backlog work.

• As a result - Members expressed considerable enthusiasm about the progress and quality of the work and several members signed up to help progress additional use cases with a strong interest in B2B use cases

SESSION RECORDING: 2021-02-01 Mon Q3: Connecting Open APIs to realize ODA with API call-flows (IG1228)


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ESs_YyY3vu5Ep3hyQrHrBJUBlfNrJiP4ZGN48vvujwDZPA?e=JVHjoL

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/ESs_YyY3vu5Ep3hyQrHrBJUBlfNrJiP4ZGN48vvujwDZPA?e=JVHjoL

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EWhS2kbFuhFOoR2U_RQHaVMBaffjcM5QjesU7_TEPULGxA?e=biYCeR

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EWhS2kbFuhFOoR2U_RQHaVMBaffjcM5QjesU7_TEPULGxA?e=biYCeR


of 35

MEETING TITLE: Charging, rating and balance management Tue Q4 JOINT: FX, ODA-RI, ODA-TA, ODA-FA OBJECTIVE: To discuss and agree where charging, rating and balance management should be located within the Open Digital Architecture. OUTCOME: Brice Petitfrère (Orange) led this discussion regarding the Charging, Rating and Balance Management network activities, their relationship, and their positioning within the Open Digital Architecture (ODA). This has been the subject of debate within the ODA workstreams and the Catalyst projects for some time, and the teams took the opportunity of a joint session at Virtual Action Week to clarify the terminology, identify the different options, share their different views, and agree on a way forward. The conclusion was that we need to consider additional use cases, including real-time rating, identify best practices and review the impact of relevant APIs. SESSION RECORDING: 2021-02-02 Tue Q4: ODA: Charging, rating and balance management

MEETING TITLE: Realigning and understanding the component architecture requirements (ODA-RI) with the Open API Team Tue Q5 JOINT: ODA-FA with API, ODA-RI, ODA-TA OBJECTIVE:

• Processing ODA Reference Implementation team requirements from the API team • Planning future work and component architecture • Reviewing TM Forum processes regarding the API requirement input and output roadmap

OUTCOME: A lively discussion between the ODA Functional Architecture, Reference Implementation, Technical Architecture, Open API, and Frameworx teams discussing many aspects of ODA components, including the optimum granularity, process flow mapping, and their relationship with ODA functional blocks, Frameworx functions, and Open APIs. The teams acknowledged the need to work more closely together and agreed to hold a short workshop after Virtual Action Week to share their different perspectives and develop a structured methodology to develop concrete examples. We have all the ingredients for success. We have a rough idea of the processes from the mapping work that Sylvie Demarest (Orange), Alexis de Peufeilhoux (DT), and Konstantin Petrosov (DT) have done. We have a good idea of what an API looks like and the rules and principles involve, and we have a good idea of what a component looks like including the definition and rules. Taking those three things, along with the ODA Component Accelerator project, we can come up with an example of a component. Ultimately the market will determine what a component should be – the operators will say 'I want a product catalog' and the vendors will say

'We'll build you a product catalog’, which is where we want to get to. SESSION RECORDING: 2021-02-02 Tue Q5: ODA-RI: Realigning and understanding the component architecture requirements (ODA-RI) with the Open API team


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EcrlFEYsQWdIgXrP6YFwsvAB6kTHXz8zO7PS8Lcb5A_IDg?e=HudGZl

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVquSbAaYNJDnapGAU2cqD8BJ8PFFG87lalgxLPAZWy5BQ?e=bfNRD6

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVquSbAaYNJDnapGAU2cqD8BJ8PFFG87lalgxLPAZWy5BQ?e=bfNRD6


of 35

MEETING TITLE: Developing a multi-layer Topology discovery service API Wed Q0 JOINT: ODA-Production with API OBJECTIVE:

• An overview of a conceptual model for a Topology Discovery Service, outlining a set of

scenarios and defining use cases from which formal general static and dynamic

requirements are derived.

• Outlining the requirements for this service, with filtered views of topology across multiple

Frameworx domains to overcome the challenges of separated and siloed systems.

• Incorporating stringent security and privacy requirements based on operational

requirements and experiences.

• ODA production: Topology Discovery TMF920A

OUTCOME: Reviewed using slides in JIRA contribution ODA-674, the business requirements in TR-283 and the progress and rationale on the Topology Discovery Service (TDS) Component Suite TMF920A and API TMF686 with the goal of familiarizing the API team with the scope of business requirements, content and progress of the work achieved. We agreed the next steps which are work items in the API program to govern delivery of these items being developed in the ODA team.

We reviewed: The operational use case background captured in TR283 Business Requirements Topology Discovery Service (TDS) and progress on TMF920A TDS API Component Suite

So that: We got feedback from the API team on how to jointly proceed technically and organizationally with the API team to get the work completed and published.

As a result: The API team provided feedback on technical considerations about the use of entity specification patterns in API data models, and discovery reporting patterns in TMF677 which might be leveraged for the API development. There was also a proposal on which work items to create in the API team, to link API development and governance teams to the working team in ODA.

SESSION RECORDING: 2021-02-03 Wed Q0: ODA: Developing a multi-layer Topology Discovery Service API

MEETING TITLE: Using all parts of Open Digital Architecture to produce business solutions (Enterprise Architecture) (Part 1 of 2) Wed Q2 JOINT: ODA, AI, DEM OBJECTIVE: ODA provides a complete reference architecture, covering all aspects of the landscape from the business drivers to the deployed software and infrastructure. The sheer scope of ODA often makes it difficult to understand how to use the different parts of ODA together to produce solutions to business problems. At this session, the Solution Design Guides team will work on a template to describe how to use ODA end-to-end.

1) Agree the scope of this activity.

2) Produce a high-level first draft of the how-to-use ODA guide.

3) Agree what is required to complete this work including what will be delivered, who needs to

be involved, etc.


https://projects.tmforum.org/jira/browse/ODA-674

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ERBi9oBQdKVEuUgelhKx6YQBHXVmHgOhcDCusqo7mbJ42Q?e=eBRo6q

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/ERBi9oBQdKVEuUgelhKx6YQBHXVmHgOhcDCusqo7mbJ42Q?e=eBRo6q


of 35

OUTCOME: The session was opened by Ian Turkington (TM Forum) who set out the need for an enterprise architecture informed approach to realizing solutions using all ODA assets. The notion is some form of template or infographic capturing best practice for ODA based solutions. The presentation covered material from Business Architecture and CurateFx tooling, as well as the current work happening on ODA Solution Design Guides. There was a highly interactive exchange of ideas between presenters and participants and two breakout sessions were identified for the follow-on session on Thursday Q1 at 09:00 CET. We reviewed - The known best practice for enterprise architecture-based business architecture, CurateFx and ODA solution design examples on modelling products, B2B and B2B wholesale using Metro Ethernet Forum (MEF). So that -We can identify what the best practice template/infographic might look like using two examples. As a result - We have two proposed use cases for B2B end-to-end solutions and integration of components, processes and APIs.

SESSION RECORDING: 2021-02-03 Wed Q2: ODA: Using all parts of Open Digital Architecture (ODA) to produce business solutions (Enterprise Architecture) (Part 1 of 2)

MEETING TITLE: ODA Component Accelerator Show & Tell WED Q3 JOINT: AI, AN, API, BA, BAR, CEM, DEM, DMM, DOT, FX, IoT, ODA OBJECTIVE: Building on the Business Operating System (BOS) Catalyst project, the ODA Component Accelerator project, which started in December 2020, has a mission to develop a practical test platform for ODA components, and to deploy ODA reference implementations which TM Forum members can use in the Forum’s Open Digital Lab.

This show and tell session presented and demonstrated the outcomes of the project’s first sprint, which establishes the Open Digital Lab environment and delivers an initial proof-of-concept for automated ODA compliance validation of ‘black box’ and ‘glass box’ commercial products. The work also provides useful insights into ODA Technical Architecture by mapping real products supplied by ODA Component Accelerator (CA) project members against the v1 ODA component definitions. OUTCOME: George Glass (TM Forum) opened this popular session with an overview of the ODA-CA project including the mission, objectives, founders, and press coverage. The project aims to provide multi-stage compliance testing for ODA components following a three-sprint plan. George described the initial objectives, project phases, and component characteristics. Gaetano Biancardi (Accenture) and Andy Tiller (TM Forum) then shared details of the work done to create an ODA component inventory, dictionary, and heatmap, relating components to the ODA function blocks, as described in

the recently published document IG1242 ODA Component Inventory and Heatmap v1.0.0. An interesting and informative discussion covered many aspects of the project, including the relationship between the ODA-CA project and the ODA Collaboration projects. Andy explained that the ODA collaboration projects would define/own the specification of ODA components, while the ODA-CA project, like a Catalyst, would use the standards to provide proofs of concept validations and submit team-approved contributions back to the collaboration projects. SESSION RECORDING: 2021-02-03 Wed Q3: ODA-CA: ODA Component Accelerator Show & Tell


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EeG3YzTiiXhHuUzzYrwOMNoBwCOolEBUkLI3M-3T190r-w?e=sR6X1o

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EeG3YzTiiXhHuUzzYrwOMNoBwCOolEBUkLI3M-3T190r-w?e=sR6X1o

https://www.tmforum.org/resources/how-to-guide/ig1242-oda-component-inventory-and-heatmap-v1-0-0/

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/Ef4DZW6WChpPj9IQuiijxZUBBntmrkX5ffGv-ttxxHYssQ?e=AJpU2Y


of 35

MEETING TITLE: Establishing the vision for security and privacy across the Open Digital Architecture (ODA) WED Q4 JOINT: AI, DEM, API OBJECTIVE: Security is a key element of the Open Digital Architecture (ODA) and we need to ensure security is not seen as a separate standalone activity, but an integral part of the architecture. • Revisit the security vision documents (IG1186 - ODA Governance and Security Vision and

IG1187 - ODA Enterprise Risk Assessment) to establish an agreed vision and to identify any changes which may be required.

• Decide what is required to deliver this vision – what deliverables are required, and which project will be responsible for these deliverables (this should not all fall to the security workstream)

OUTCOME: We reviewed - The proposal from Alexander Rockel (Oracle) to establish an organizational structure to design in security and privacy into an ODA solutions approach is based on the ODA Security and privacy team being a 'Guild ' for best practice that support practitioners working on specific aspect of ODA. An early objective is to create a secure solution for the ODA Component Canvas work. So that - We can scale ODA security efforts in practical working teams As a result - The proposal was accepted as a pragmatic way to improve ODA security and privacy by design. SESSION RECORDING: 2021-02-03 Wed Q4: ODA: Establishing the vision for security and privacy across the Open Digital Architecture (ODA)

TITLE: Cross collaboration agreement on NaaS WED Q5 JOINT: AN, DEM, API OBJECTIVE: None provided OUTCOME: Johanne Mayer (MayerConsult) provided information about what network-as-a-service (NaaS) is and what has been done so far, including a discussion on all the assets currently available and how other work within TM Forum can benefit from NaaS.

SESSION RECORDING: 2021-02-03 Wed Q5: ODA: Cross collaboration agreement on NaaS

MEETING TITLE: Using all parts of Open Digital Architecture to produce business solutions Thu Q1 JOINT: ODA, AI, DEM OBJECTIVE: ODA provides a complete reference architecture, covering all aspects of the landscape from the business drivers to the deployed software and infrastructure. The sheer scope of ODA often makes it difficult to understand how to use the different parts of ODA together to produce solutions to business problems. At this session, the Solution Design Guides team will work on a template to describe how to use ODA end-to-end.


https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVTiu4KhzKxNkKGsimDSMYMBcOX5fdbAdF1_AAMGkPY6-Q?e=bGFEvB

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EVTiu4KhzKxNkKGsimDSMYMBcOX5fdbAdF1_AAMGkPY6-Q?e=bGFEvB

https://tmf365-my.sharepoint.com/:v:/g/personal/soregan_tmforum_org/EQVikPTl1blEgr8UPIgTcy0B5LnoICoQRtvdT_mb7z3JiQ?e=Tf5oSM


of 35

1) Agree the scope of this activity.

2) Produce a high-level first draft of the how-to-use ODA guide.

3) Agree what is required to complete this work. What will be delivered, who needs to be

involved, etc.

OUTCOME: A small task force was set up under Ian Turkington (TM Forum) to produce a straw man proposal for consideration by the ODA team. The team includes Milind Bhagwat (BT), Tony Shepherd (BT), Emmanuel A. Otchere (Huawei) and Andrew Thomson (BearingPoint). Reviewer: Lennart Isaksson (Ericsson). SESSION RECORDING: 2021-02-04 Thu Q1: ODA: Using all parts of Open Digital Architecture (ODA) to produce business solutions (Enterprise Architecture) (Part 2 of 2)

MEETING TITLE: Overview of the TM Forum Agile Process FRI Q1 JOINT: AI, AN, API, BA, BAR, CEM, DEM, DMM, DOT, FX, IoT, ODA OBJECTIVE: An overview of agile tooling and how it is used for collaboration (i.e., Confluence, Jira, Git, etc.) OUTCOME: In this well-attended open session, John Gillam (TM Forum) provided an overview of TM Forum collaboration processes, tooling, and project structure, including themes, projects, and charters. The 8-week 'sprint' timeline was explained, and benefits in tracking and efficiency shared. Attendees then joined one of two breakout rooms to focus on Principles/Processes, led by Sue Davis (TM Forum) and Tooling, led by John Gillam, using Mural boards to capture input. The next steps will be to review all inputs, create a proposal and provide feedback to TM Forum members, before appointing working project teams to implement key improvements. SESSION RECORDING: 2021-02-05 Fri Q1: ALL: Overview of the TM Forum agile process

MEETING TITLE: Bringing collaboration projects together to support the open digital architecture (Part 2 of 2) FRI Q2 JOINT: AI, AN, API, BA, BAR, CEM, DEM, DMM, DOT, FX, IoT, ODA OBJECTIVE: ODA spans several inter-dependent TM Forum collaboration projects, (Frameworx, Open APIs, AI & Data Analytics, Business Architecture and of course the ODA project itself.) It is essential that these projects work together to produce a consistent reference architecture. This session will bring the teams together to ensure better collaboration, and in particular:

• Ensure we have a common understanding of the scope of ODA, and the deliverables which are required to document this reference architecture.

• Understand the repositories which underpin ODA (including but not limited to Frameworx). • Ensure the projects together fully support ODA, and propose any changes required.

OUTCOME: In the second of two sessions, Ian Turkington (TM Forum) began with a recap of the topics presented during the first session on Monday Q2. He then shared proposed changes to the projects and workstreams based on his thoughts and on feedback received during Virtual Action Week. Proposed changes include the creation of new projects, new workstreams, scope changes, and re-assignment of


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EaCUDLW8h1lPiT4ef82FT44BXzP-6QpWclKPdYhBGGffRQ?e=MlVxyE

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EaCUDLW8h1lPiT4ef82FT44BXzP-6QpWclKPdYhBGGffRQ?e=MlVxyE

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EQys85iwOBhDjqKZCEtpGkoB38wjedQl7J3L3BRQryTKPA?e=5P1i1p


of 35

work. While reviewing the ODF/ODA diagrams, Andy Tiller (TM Forum) shared proposals to place these diagrams under a formal governance process. Ian also presented initial terms of reference for a total ODA project governance, with regular review meetings required. A summary of outstanding questions included ownership and visibility of the TM Forum Data Model and alignment of AI and Autonomous Networks projects. The proposed changes will be presented to the Collaboration Sub-Committee (CSC) on February 9, for implementation ahead of Sprint 3 (beginning April 5th).

SESSION RECORDING: 2021-02-05 Fri Q2: ODA: Bringing collaboration projects together to support the Open Digital Architecture (Part 2 of 2)

MEETING TITLE: Developer-level walkthrough of packaging software as ODA-component FRI Q3 JOINT: ODA-CA, AI, AN, API, BA, BAR, CEM, DEM, DMM, DOT, FX, IoT, ODA OBJECTIVE:

• Building on the BOS Catalyst, the Open Digital Architecture (ODA) Component Accelerator project (started last December) has a mission to develop a practical test platform for ODA components and deploy ODA reference implementations which TM Forum members can use in our Open Digital Lab

• Detailed walkthrough building and testing an ODA component from scratch using Open API reference implementation code as starting point.

• A tutorial/Q&A session to answer any questions about the software approach to packaging software into the ODA reference implementation

OUTCOME: This popular session, led by Lester Thomas (Vodafone) provided a deeper dive into the process and tooling used to create ODA components in the test environment, following the ODA-CA show & tell session on Wednesday Q3. Lester based his demonstration on the TMF646 Appointment API, using its reference implementation code as his source. This relatively simple API provides a good way of testing the component implementation. Lester showed how the YAML definition could be packaged as a docker file for testing in the Kubernetes environment, deployed in the canvas, and displayed using a Helm chart. A highly interactive discussion ensued, raising and responding to numerous questions from the participants, and covering topics such as the publication/subscription of components, security using Keycloak, and the potential to use TOSCA and Kafka. An interesting and enjoyable session to close Virtual Action Week. SESSION RECORDING: 2021-02-05 Fri Q3: ODA-CA: Developer-level walkthrough of packaging software as ODA-Component


https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EYiVrv2OlKdMvJ1agzh_wwwB3B5_OUtwbUXJrYsElTcPQw?e=iyvZY8

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EYiVrv2OlKdMvJ1agzh_wwwB3B5_OUtwbUXJrYsElTcPQw?e=iyvZY8

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZId1E-O98dDhEWWMJ9aCTYBRVNtuJuWE-4avUmm3Y8JdQ?e=KHb9P4

https://tmf365-my.sharepoint.com/:v:/g/personal/psorce_tmforum_org/EZId1E-O98dDhEWWMJ9aCTYBRVNtuJuWE-4avUmm3Y8JdQ?e=KHb9P4

action week roundup

Documents