consult21 systems & process working group 19th october 2005 welcome
DESCRIPTION
1. Introduction Expanded the scope of the Systems Workgroup to include processes Now need to go to the next level of detail to provide the standards for process and systems interface development for 21CN and beyond. Propose not to define a single process that will work across all relevant products in the individual product groups - (which would only exacerbate the current silo problem) Propose to break down the process flow into individual elements then each element can be agreed within a working group of experts across all the relevant products. We have created a "straw man" of the process flow and a suggestion as to how to carve it up into “bite” size chunks. We have with the other workgroup co-chairs started to understand what the various workgroups do and how they will work togetherTRANSCRIPT
Consult21 Systems & Process
Working Group
19th October 2005
Welcome
Agenda1. Introduction, Scope & Actions from previous
meeting (Graham Crane/Nancy Saunders/Tim Short)
2. Process Experts Co-Chairs (identify experts across relevant product sets to work on the elements of the process flow)
3. ToRs for sub-groups Co-Chairs (flesh out straw men that will have been created in advance)
4. IT Interface Experts Co-Chairs (identify experts to work on agreeing the standards for the IT interface (s)
5. Roadmap Feedback All
6. Review BT (Tim Short)
14.00-14.30
14.30-14.45
14.45-15.40
15.40-16.10
16.10-16.30
16.30-16.45
1. Introduction•Expanded the scope of the Systems Workgroup to include
processes •Now need to go to the next level of detail to provide the standards
for process and systems interface development for 21CN and beyond.
•Propose not to define a single process that will work across all relevant products in the individual product groups - (which would only exacerbate the current silo problem)
•Propose to break down the process flow into individual elements then each element can be agreed within a working group of experts across all the relevant products.
•We have created a "straw man" of the process flow and a suggestion as to how to carve it up into “bite” size chunks.
•We have with the other workgroup co-chairs started to understand what the various workgroups do and how they will work together
Implementation & Migration
To make tomorrow happen
• Trials• Operational Planning• Implementation
Consult21 Working Group Structure
Co-Chair Co-ordination
Steering Board
To be a co-ordination and
escalation point
Red = Physical Working Group
LegacyTo clear the way
for tomorrow
• Products - VIEC• Billing• etc
Communications
To keep end users informed
NGN Product Groups
BroadbandLine AccessInterconnect & PortfolioPoint to PointFutures
Commercial GroupContract Group
Architecture & FrameworkSystems & Processes
NetworkNetwork Hooks
Workgroup Roles & Inter-working
PrinciplesStandardsGovernanceFrameworksCapabilities Systems & Processes Group
Networks GroupDevelop:1
UK S
tand
ards
2 Align/Develop
Requirements/ Clarification
Product Group
Commercial Group
Implementation & Migration Group {
4
New productsChanges, etc
6
Confirm,Standards, Process, etc conform& review & improve standards
7BT Product Development
Submit SOR5
Build into BT architecture, roadmaps, components, governance, etc
3
See notes
8 Submit SoR to resolveAny issues
Systems & Process Work Group• Aim
• To create principles, standards, frameworks etc that govern the development and implementation of networks and systems
• Input • Draft principles / comments / agreement• Product requirements requests for clarification• New/change products compliance
• Output / Timelines / Milestones• Principles – April 05• Standards/frameworks agreed – tba• Alignment with UK standards - tba• Clarification of requests - ongoing• Conformance & standards etc - ongoing• Review & improvement of principles, etc – ongoing
• Measures / CSF• Agreed principles, frameworks, standards, etc• Conforming products
Dependencies
Product TeamsIndustry/Customers/Steering Group
Product/System/network Teams
Draft
2. Process Experts Co-Chairs (identify experts across relevant product sets to work on the elements of the process flow)
Mark Gray
Generic Process Flow
Delivery timeline
Sell Service
Supply Service
Use Service
Obtain Payment
Trouble toRepair
From an opportunity
To a confirmed order
From a confirmed order
To anestablished service
From the start of a transaction
To the end of a transaction
From Payment due
To Payment confirmed
From identifying or predicting a problem
To the Problem resolved
• What they want
• Where they want it
• Order validation
• Physical and logical fulfilment
• Order changes and cancellations
• Operating the service
• What has been charged for
• What charging rates have been used
• Pro-active detection
• User reported problems
• Diagnostics• Jeopardy
management
TBA TBA TBA TBA
• Interface Standards• Interface Points
• Interface Specifications• Interface KPI’s, SLA’s, etc
•Technical & Business Support (Design/Impl)
Systems Actions – Derrick Evans
Technology Standards
•ISO 15000-1: ebXML Collaborative Partner Profile Agreement •http://www.ebxml.org/specs/ebcpp-2.0.pdf•ISO 15000-2: ebXML Messaging Service Specification •http://www.ebxml.org/specs/ebMS2.pdf•Also possibly • OASIS ebXML ebBP Business process Specification Schema•http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-bp
•OASIS Unviversal Business Language UBL•http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl
Scope