Digital Services Toolkit

Contribute, Collaborate, Communicate

© 2016 TM Forum Live! 2016 | 1
What does the Digital Services Toolkit provide?

 The ability to trace a path from a business scenario to a

specific collection of related TM Forum assets
 Integrity and continuity in tooling and semantics
 Smooth handoff across user journeys through deeper levels of detail
 E.g. line of business manager  architect  developer

 The ability to reason across multiple business scenarios and

asset collections
 Eventually, the ability to recommend asset collections based
on similarity to other scenarios
© 2016 TM Forum Live! 2016 | 2
What will the Digital Services Toolkit do?

 Broaden our base of inputs (Wikipedia vs encyclopedia)

 Reduce barriers to collaboration and consumption
 Link assets to real-world business scenarios
 Provide a consistent semantics and vocabulary across all assets
 Make everything accessible via both GUI and API
 Reduce the need for specialized tooling for consumption
 Connect a very large producer/consumer base with governance
 Make Forum assets more easily accessible by purpose

© 2016 TM Forum Live! 2016 | 3

What is the Digital Services Toolkit (DST)?

 A collection of Confluence spaces

 Eventually containing or linking all TM Forum assets
 Individually represented as Confluence pages
 Linked and tagged to indicate known relationships
 Linkable and taggable to allow creation of customized views
 Accessible for browsing and contributing
 Through Confluence GUIs and APIs
 Through apps that use the APIs

© 2016 TM Forum Live! 2016 | 4

A comprehensive collection of assets

 Over 6000 interlinked Confluence pages including

 1900+ information entities
 1700+ metrics
 1600+ business processes
 600+ application functions
 400+ applications
 100+ B2B touchpoints
 Links to business scenarios, platform capabilities,
supporting services, use cases, …

© 2016 TM Forum Live! 2016 | 5

New capabilities for Forum members

 Comment on assets at the “atomic” level

 Search assets by many criteria
 Visualize assets and relationships in multiple ways
 Navigate according to multiple criteria
 By existing hierarchies
 By categories
 By relationship to a business scenario or use case
 Download only what is of interest
 Create new associations between assets
© 2016 TM Forum Live! 2016 | 6
Who might use the DST?
DST User Journey

 Example personas:
 Solution architect
 Frameworx contributor
 Developer
 Line of business manager
 Subject matter expert
 Big data analyst
 User experience specialist

© 2016 TM Forum Live! 2016 | 7

What might people intend to do with the DST?
DST User Journey

 User intentions:
 Browse collections of scenarios, solutions and assets
 Collaborate with other Frameworx users / contributors
 Contribute scenarios / solutions / new Frameworx assets
 Apply Frameworx concepts / models / specifications into a solution
 Discover concepts and categories that may be useful
 Find Frameworx assets that are relevant to user’s situation
 Learn how to use Frameworx assets

© 2016 TM Forum Live! 2016 | 8

What actions might people take in the DST?
DST User Journey

 User actions:
 Comment on pages representing scenarios / solutions / assets
 Create new pages, links, and collections
 Download materials
 Follow links
 Read existing pages
 Search and find pages and attachments
 Update existing pages and collections

© 2016 TM Forum Live! 2016 | 9

What Confluence components might be used?
DST User Journey

 User touchpoints:
 Attachments to pages containing related information
 Comments on pages for revision and approval
 Diagrams added or generated using Confluence plug-ins
 Links between pages and to external resources
 Pages representing individual assets
 Content-based or label-based Searches across pages
 Labels representing categories and searchable terms

© 2016 TM Forum Live! 2016 | 10

 A user journey canvas for the DST
DST User Journey User actions
Comment Create Download Follow Read Search Update
Touchpoints
Attachments

Comments

Diagrams

Links

Pages

Searches

Tags

© 2016 TM Forum Live! 2016 | 11

Problem statement: solution architect
 As an architect for a system / solution integrator selling enterprise IoE
 I need to gain time to market / revenue advantage and cost savings
 so that I can compete successfully with other system / solution integrators.
 To do this I need to
 Enable fast definition of standard solution sets e.g Managed LAN
 Create tight and agile linkages cross-organization and cross-partner between business, development and
deployment
 Facilitate deployment scaling of the solution set
 Define once and replicate nationally / globally
 Remove skill set bottlenecks in my organization
 Improve customer experience / reduce support costs through standardized solution set

 I will know that I am successful when I use these capabilities to rapidly develop competitive
solutions.

© 2016 TM Forum Live! 2016 | 12

 Solution Architect: discover, learn, design
DST User Journey User actions
Comment Create Download Follow Read Search Update
Touchpoints
Attachments 4
Download API Locate
Download diagrams related APIs
Comments specs, data and
and white papers
process models and models
Read
solution set
Diagrams 4 pages
Find relevant
Links 3 solution sets

Pages 2
Searches 1
Tags

© 2016 TM Forum Live! 2016 | 13

Problem statement: Frameworx contributor
 As a subject matter expert with valuable experience / material to contribute
to Frameworx
 I need to collaborate effectively with other SMEs to develop assets of value
to both my own company and the larger community
 so that I can make contributions that advance Frameworx while enhancing
my own career and my company’s reputation
 To do this I need to
 Find work in progress in my area of expertise
 Contribute my / my company’s ideas and experience
 Collaborate with other experts to develop assets
 I will know that I am successful when I can use these capabilities to
efficiently co-develop assets that are recognized as valuable by members.

© 2016 TM Forum Live! 2016 | 14

 Frameworx contributor: find, contribute, collaborate
DST User Journey User actions
Comment Create Download Follow Read Search Update
Touchpoints
Attachments 3 5
Comments 2 4
Contribute
Contribute Contribute
Finalize
Diagrams 3 new material
material new material
release 5
Join or
Links Comment on
moderate
others’ work
discussion
Pages 3 5
Searches 1
Find relevant
Tags work in
progress

© 2016 TM Forum Live! 2016 | 15

Backup Materials

© 2016 TM Forum Live! 2016 | 16

 DST structure

• Problem Statements and Business Model Canvases

define stakeholder (Actor) Viewpoints within a
Business Scenario
• Use Case Collections aggregate Use Cases to
achieve a specific business goal
• Use Cases can be linked to Use Case Sequence
Diagrams and/or to Process Flows
• Process Flows aggregate Process Elements
• Both Sequence Diagrams and Process Flows can
be linked to Touchpoints
• Touchpoints can be linked to APIs
• Additional components can also be linked:
• Information Framework ABEs / Entities
• Metrics
• Any other Forum asset that makes sense for a
particular Business Scenario
© 2016 TM Forum Live! 2016 | 17
DST construction

• Each context element of each

business scenario, and each
Frameworx component, is
individually represented as a
Confluence page
• Tagged context pages within
a scenario-specific hierarchy
are linked to non-scenario-
specific component pages in
the “creator view”
• Confluence plugins use the
links, tags and metadata to
visualize the collection of
assets related to a scenario
and link the consumer to the
page content

© 2016 TM Forum Live! 2016 | 18