Transcript Document

What if integration came standard?
OSLC to be standardized at OASIS
Analyst Community Call: 10 AM EDT, 30 May 2013
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
1
© 2013 OSLC Steering Committee
Leading today’s call
Mik Kersten
CEO
Tasktop
OSLC Steering Committee
Scott McGrath
COO
OASIS
Ludmila Ohlsson
Product Manager, Software Development
Ericsson
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
© 2013 OSLC Steering Committee
Agenda
1. The News
2. Related Background
1. OSLC
2. OASIS
3. What this Means
4. Questions and Discussion
3
© 2013 OSLC Steering Committee
Mik Kersten
CEO
Tasktop
OSLC Steering Committee
The News
1.
© 2013 OSLC Steering Committee
OSLC Member Section Created at OASIS
5
Mission
• To standardize OSLC
Support
• Co-founded by 22
organizations
Blessing
• Unanimous OASIS
Board approval
© 2013 OSLC Steering Committee
History
Community governance of OSLC
OASIS
 Internationally recognized
independent SDO
 Formal support from 22
organizations (at launch)
 Participation governed by
established OASIS model
Steering committee
IBM de facto
governance
(with
community
support)
June
2012
6
 Multi-organization steering
committee established
 New governance model
introduced
May 2013
2012
© 2013 OSLC Steering Committee
Why OSLC and Standardizing at OASIS Matters
Software runs the world
But it is heterogeneous and disjoint
And it needs to be integrated
Traditional approaches to software integration require custom software
Custom software is expensive to maintain and a limit on future choice
Custom integrations drive software TCO higher and limit choice
Open standards are key enablers for broad and large-scale integration
OSLC standards simplify lifecycle integration leading to cost savings and increased flexibility
OSLC is helping the world run more efficiently
Standardizing OSLC at OASIS will increase adoption and acceptance of OSLC
The world will benefit from standardized integration through OSLC
7
© 2013 OSLC Steering Committee
The OSLC Member Section Co-Founders
Accenture
Bank of
America
Boeing
Creative
Intellect
EADS
Eclipse
Foundation
Ericsson
Fujitsu
IBM
JPMorgan
Chase
Kovair
Software
KTH Royal
Institute of
Technology
Mentor
Graphics
National
Instruments
Persistent
Red Hat
Siemens
Sodius
Software AG
Tasktop
Universidad
Politécnica
de Madrid
8
WSO2
© 2013 OSLC Steering Committee
Mik Kersten
CEO
Tasktop
OSLC Steering Committee
Background on OSLC
2.1.
© 2013 OSLC Steering Committee
The Basics: What is OSLC, and why should I care?
OSLC is an open community building practical specifications for integrating software
Tool
Maker
• create software using reusable and open assets that will
interoperate with other tools both inside and outside your influence
providing time and cost savings
Tool
Manager
• reduce the complexity and risk of increasingly complex software
infrastructures, and improve the value of software across a broader
set of internal and external stakeholders
Tool User
• choose the best tools for your job and have them interact
seamlessly to achieve traceability and visibility with the rest of your
organization
Systems
Integrator
• focus energy and resources on higher-value customizations,
deliver more business value to your clients, and increase client
satisfaction
OSLC is beneficial to many stakeholders
Contributing Organizations: http://oslc.co/organizations
10
© 2013 OSLC Steering Committee
The Executive Summary: OSLC’s Simple Solution
Users can work seamlessly across their tools
(complex and fragile synchronization schemes not required)
Architecture of the Web
Standard Interfaces
Automation
Linked Data
“Just Enough” integration
Increased reuse
Increased traceability
Monitoring
Decreased maintenance costs
Better visibility
OSLC is an open and scalable approach to lifecycle integration.
It simplifies key integration scenarios across heterogeneous tools
11
© 2013 OSLC Steering Committee
OSLC: Standardizing the sharing of lifecycle data
Scenario-driven &
Solution-oriented
Leading choice for strategic
integration technology
Generally applicable: specs available for many
domains covering ALM, DevOps, ISM, and PLM
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
OSLC Member Section
Linked Data Platform Working Group
Based on and
Shaping the
Future of Internet
Architecture
OSLC:
12
Open and Independent
Governance and Leadership
The Resource for OSLC Implementers
Inspired by the web
Free to use and share
Changing the industry
Proven
Open
Innovative
© 2013 OSLC Steering Committee
Aspirations for OSLC
Foundational technology for all
integration
The household name for integrations
Natural choice for standardizing looselycoupled integrations in new domains
13
© 2013 OSLC Steering Committee
Scott McGrath
COO
OASIS
Background on OASIS
2.2.
© 2013 OSLC Steering Committee
OASIS Background
• Nonprofit consortium, founded 1993
to advance document standards
• Global community
5,000+ participants
600+ orgs & individuals in 100+ countries
• Open, democratic, transparent
• Home of nine Member Sections and
70+ Technical Committees
• Create standards for Cloud, M2M, IoT, security, privacy,
content technologies, energy, eGov, legal, emergency
management + other areas identified by members.
+ OSLC
16
OASIS OSLC Co-Founders
17
What criteria did OSLC use in choosing
OASIS?
Must Have
Open accredited process— transparent and available to all
Large community of experts that welcomes participants
Level playing field– organizations large and small have same
influence
Balance of rules and freedom– permanence and respect of
outcomes
18
What happens when OSLC transitions to
OASIS?
OASIS OSLC
Member Section
OSLC retains its elected governance and brand
OSLC continues to set its own technical agenda
Members form OSLC Technical Committees under OASIS process
OASIS commits to providing OSLC specs freely and permanently
Participation in OSLC expands to existing OASIS member base
OSLC takes advantage of proven OASIS IPR Policy
Ratified OSLC standards may be advanced to ISO, ITU, IEC, ANSI…
19
Ludmila Ohlsson
Product Manager, Software Development
Ericsson
What this Means
3.
© 2013 OSLC Steering Committee
Ericsson
Integration Framework
Ludmila Ohlsson
ERICSSON at a glance
40%
Of the world's
mobile calls are on
Ericsson networks
30 000
950M
2.5B
Number of
patents
110 255
227.8B
Number of
employees
180
Ericsson Internal | 2013-05-20 | Page 22
Subscribers in
networks that we
manage
Countries we
operate in
Subscribers on
Ericsson supported
networks
SEK, Net
sales 2012
135 years OF INNOVATIONS
› 1878
Telegraph to telephone
› 1923
Manual switching to automatic switching
› 1968
Electro mechanics to computer control
› 1981
Fixed communications to mobile communication
› 1991
Analog (1G) to digital (2G) mobile technology
› 1998
Integration of voice and data in mobile networks
Early automatic switch
› 2001
Launch of WCDMA/3G networks in Western Europe
› 2006
Launch of HSPA mobile broadband globally
› 2009
First commercial LTE network launched
› 2011
Sales of mobile broadband took off
Multi-standard radio base station RBS 6000
Ericsson Internal | 2013-05-20 | Page 23
OPEN standards KEY
FOR THE INDUSTRY
›
›
›
›
›
Innovation is an important element of our corporate culture
Early involvement in creating new standards
Largest contributor to open standards
Often first to market with new solutions
5th largest software supplier in the world
Ericsson Internal | 2013-05-20 | Page 24
Why Integrations?
› Support the end 2 end flow
– Multiple tools involved - integrations to make information flow
efficient (more than 4000 tools in our IT Catalog!)
– Should be as seamless and transparent as possible
– Ideally focus on flow, tasks, information – not tools
› Visualization, traceability, dashboards
– Cross PDUs, multi-standard features
Ericsson Internal | 2013-05-20 | Page 25
Tools Framework
System & Product
Team & Program
Architecture
Backlog
Use Cases
Anatomy
Dashboard
Defects
Resources
Modeling
Wiki
Release
Integration & Verification
Design &
Implementation
Pass or Fail
IDE
Code generation
Builds
Reviews
CAD
Ericsson Internal | 2013-05-20 | Page 26
Integration
Principles
Reporting
Service
OSLC
Use Cases
Test Automation
Simulation
SQA
Test Service
Data Model
Ongoing activities
› Implementation of OSLC interfaces
› PoC of existing interfaces
› Discussions with vendors on OSLC implementation
› Visualization
› Collaboration with similar companies on OSLC
› Collaboration with Universities and EU projects
› Collection of findings
› more
Ericsson Internal | 2013-05-20 | Page 28
Summary
› We need OSLC for cheaper, quicker and better
integrations and visualisations
› OASIS OSLC standards will drive new implementations
from our many suppliers
› OASIS standardization process will help us drive new
scenarios into future OSLC standards
Ericsson Internal | 2013-05-20 | Page 29
Questions and Discussion
4.
© 2013 OSLC Steering Committee
BACKUP
© 2013 OSLC Steering Committee
The OSLC Steering Committee
Rainer Ersch
Senior Research Scientist
Siemens
Andreas Keis
Manager, Software Engineering
EADS Innovation Works UK
Bola Rotibi
Research Director
Creative Intellect
OSLC StC
Staff Members:
David Ingram
Managing Director
Accenture
Mik Kersten
CEO
Tasktop
John Wiegand
Distinguished Engineer and Chief Architect
IBM Rational
(Steering Committee Chairman)
Sean Kennedy
OSLC StC
Operations Coordinator
Steve Speicher
OSLC StC
Technical Coordinator
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
33
© 2013 OSLC Steering Committee
Roadmap for OSLC at OASIS
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
December
2012
• OSLC Steering
Committee
approves plan to
standardize
OSLC domain
specs at OASIS
May 2013
June 2013
3Q 2013
• OASIS Board
unanimously
approves
creation of the
OSLC Member
Section cofounded by 22
organizations
• First OSLC
Member Section
Steering
Committee
meeting
• Election
announced to fill
remaining
Steering
Committee seat
• OSLC Core 3.0
spec to be
contributed to
OASIS to launch
the OSLC Core
Technical
Committee
4Q 2013 –
2014
• OSLC 3.0
domain specs
are contributed
to OASIS as
they reach
finalization
To be refined with input from the OSLC Member Section participants.
OSLC Member Section
34
© 2013 OSLC Steering Committee
The Vision for OSLC
OASIS OSLC Member Section
Steering
Committee
open-services.net
Technical
Committees
Approved
Standard
Approved
Implementer’s
Expo
User Groups
Forums
Standard
Approved
Standard
Approved
Standard
News
Subcommittees
~~~
~~..~~
Resources
and Tutorials
Use what you need,
share what you can.
Eclipse Lyo
W3C LDP WG
Libraries
Test Suites
Samples
and
Examples
OSLC4Net
Reference Implementations
35
© 2013 OSLC Steering Committee
OSLC inside OASIS
OASIS
OSLC Member Section
5+ OASIS Members are the founders
Other OASIS Members can join when
they choose
Steering
Committee1
advises
<relationship>
Technical
Architecture TC2
guides
1.
2.
3.
4.
36
oversees
oversees
Domain TC
Domain TC
Domain TC3
Subcommittee
Subcommittee
Subcommittee4
The current OSLC Steering Committee becomes the OASIS OSLC Member Section Steering Committee
The Core workgroup becomes the Technical Architecture TC (Technical Committee).
Domain TCs are created by composing several OSLC domain workgroups.
Subcommittees may be created by the Steering Committee for a number of purposes. E.g. scenario development and
prioritization or exploration of new domains ahead of creating a new TC.
© 2013 OSLC Steering Committee