Get documents about "INTRODUCTION TO OUR PPT TEMPLATE
Shared by: moneu
-
Stats
- views:
- 34
- posted:
- 11/16/2008
- language:
- English
- pages:
- 40
Document Sample
.
Standard Contract Forum
1 February 2007
13.30
Customer Suite, BT Centre, London
www.btwholesale.com
Standard Contract Forum
Thursday 1 Feb 2007
AGENDA
1 Introduction and Notes of Previous Meeting
2 Consult 21
3 AIT Update
4 Review of New and Amended Schedules
5 Any Other Business
www.btwholesale.com
Consult21 January 07 Update
Tim Short
www.btwholesale.com
Steering Board Agenda
End User Communications Update – including Broadband Joe Kelly
Impacts & Communication (from Comms Working Group
discussion 12th Jan)
Monthly Progress Report / Plan Update Ian Stirrat
Condoc Summaries / Current Consultations (with response Nigel Scott
information) & Working Group Updates
Consultation futures: How we consult; Nigel Scott
Closing to Industry;
Website security
Steering Board Refresh Discussion All
AOB All
Systems & Processes Working Group – new co-Chair proposed –
Marian Goody (global Crossing) & Working Group to go on a quarterly
basis. For Steering Board agreement & endorsement – briefing
C21-SP-005
End User Communications
Options:
Blanket mail drop to every home
CPs provide their broadband customer date for Carlson to
distribute on a named basis (Pooling Data)
CPs distribute the information packs to their own
broadband customers
CPs email their Broadband customers with the
information
Part of ISP’s/CP’s E-Letters or Billing Information letters
Don’t mail Broadband Customers but do more local
advertisements
A mixture of the above
Consult21
Review, Refresh & Re-launch
of
Scope, Structure & Operation
January 2007
Environment
• General consensus that Consult21 offers a useful
engagement platform
• Long term desire for BAU
• Working Groups perhaps designed for “yesterday”.
• Evolution to condoc driven activity not issues
• The relationship with other areas
• BT-CP, NGNuk, NICC, BAU forums.
Scope of Consult21 (1)
• Currently defined by 21CN: products and end users
migrating to it, and the initial “obligatory” products to be
launched on it.
• Several Working Groups are close to achieving their
objectives.
• Systems interfaces defined
• 20CN product trajectories clear
• Initial products
• Still outstanding areas to address in depth
• VIC, MSIL, Broadband, NGN Interconnect etc
• Implementation in it’s infancy
Next Steps: Gather Views
• To maintain and improve existing:
• What works well, what could be improved, and how?
• Are processes appropriate and sufficiently robust?
• To seek industry views on whether Consult21 should
continue, and if so what:
• Scope, objectives
• Structure: Steering Board, Working Groups etc
Achieved through Consultation, or Steering Board Management?
Working Group Status
January 2007
Architecture & Framework RAG
Network Structure A
Systems & Processes G
Products
Interconnect & Portfolio
G
Broadband
A
Line Access
G
Point to Point
A
Implementation & Migration
Communications A
G
Network Structure
Key Milestones RAG Status Amber
December/January Achievements Key Issues (For Discussion)
This working group is managing the consultation on the technical The work being carried out by the WG is falling
aspects of the service VLAN for next generation PSTN voice onto the shoulders of a handful of individuals,
interconnect. and we are still seeking to identify additional
This includes important considerations such as resilience, granularity, people who can share the remaining activities,
efficiency, and latency. The condoc was issued in December and is and thus spread the responsibility across the
expected to be concluded in February 2007. wider Communications Provider community.
Work is also proceeding on the network inventory. This is network Briefing C21-NS-007 refers.
topological and location data related to obligatory products that CPs Consideration is being given to assigning the
need to know for investment planning purposes. A condoc on the utility
of the data schema is being prepared and is expected to be issued in technical consultation of the SVLAN over the
January 2007 MSIL to the this WG (at present it is with the
P2P WG). This is because the specification of
the SVLAN needs to reflect the needs of the
different services that will be transported.
Moreover, the SVLAN extends beyond the
January / February Work plan MSIL itself and has a network context, not just a
point-to-point context
Progressing the consultation on SVLAN for NGN voice
interconnect with bilaterals prior to the deadline for
comments. The intention will be to expose some initial
conclusions at the NS WG on 30 Jan.
Status: Customer Information
Time (A) Cost (G) Quality (G)
Sat. (G) (A)
Systems & Processes
Key Milestones
December/January Achievements RAG Status Green
Issued v3 of the Systems Roadmap updating Industry on known
systems changes. There are now some minor 21CN systems and data Key Issues (For Discussion)
field changes identified. TSR undertakings and BT Wholesale interface
changes are also included to bring all CP impacting systems changes Request the 21CN Programme Board to
into one place. re-visit their decision to delay implementing
Systems & Processes Working Group held 8th December – low the 20CN/21CN systems identifier for
attendance, however did cover: General BT Systems update, Dialogue
Services, Security requirements and address matching. Follow-up call Voice.
held 10th January with greater CP attendance where we agreed to
move Working group frequency to quarterly beginning March 16th. Co-Chair of working Group (Geoff Izzard,
Building on the C21 S&P work, the NICC B2B WG has: adopted C21 NTL:Telewest) leaving that company –
developed requirements; published 5 management documents Marian Goody of Global Crossing to
including ToRs, work plan, stakeholder analysis and best practice
guide; and has issued first 2 UK standards covering B2B architectural confirm if she can replace him.
principles, and CP-to-CP B2B gateway development
January/February Work plan
Supporting I&M WG on operational systems issues as Pathfinder
progresses.
NICC B2B will agree priorities for the next phase of its work plan at a
meeting on the 26th January. An expert sub-group has identified 9
areas to focus on starting with establishing use case scenarios,
process and data standards. CPs are encouraged to support this key
activity to improve the automation of CP-to-CP inter-working
Status: Customer Information
Time (G) Cost (G) Quality (G)
Sat. (G) (A)
Interconnect & Portfolio
Key Milestones
December / January Achievements RAG Status Green
• Opened Consultation on PSTN Emulation Experts Group
Recommendations
• Opened Consultation on Service VLAN definition for NGN Call
Key Issues (For discussion)
Conveyance • All issues described in milestones.
• Provided new Option 4 in Process for Agreeing Minutes for Right-
Sizing on Migration
• Introduced Consultation on VIC minutes Table Review Process
• Introduced Consultation on Materiality Of VIC Overflow
• Introduced new Option for calculating Blended rates surcharge
January/ February Work plan
• Close PSTN Emulation Experts Group Recommendations Consultation
• Open Consultation on Proposals from Blended Rates Billing Experts
Group
• Close Consultation on Service VLAN definition for NGN Call
Conveyance
• Open discussion on operational planning for NGN Migration
• Open Consultation on VIC Minutes Table Review Process
• Open Consultation on Materiality Of VIC Overflow
• Agree option for calculating Blended rates surcharge
Status: Customer Information
Time (G) Cost (G) Quality (G)
Sat. (G) (G)
Broadband (inc LLU)
Key Milestones RAG Status Amber
December/January Achievements Key Issues (For Discussion)
Working Group held on 20 December 2006. 36 people attended Commercials are required for the QoS aspects of WBC.
representing 14 CPs plus BT Wholesale. The main agenda items These will be discussed at the January meeting.
were:
Many customers require out of hours Datastream
MSIL Pricing, launch of Wholesale Converged Access grooming especially for business customers and ask
Consultation, IPstream Transfer Engineering Condoc closure andthat this is considered.
updates on Datastream and wBC Condocs.
IPstream consultation now closed.
Customers require more detail on Managed Broadband
Connect before they can make strategic decisions
January/February Work plan Customers are concerned about the migration plan
including costs from Datastream to WBC
Next Working Group is on 23rd of January 2007.
Industry remain concerned about IPstream migration to
Agenda to include (for wBC) : 21CN (e.g. number of CBUK changes and impacts on
Deep Dive on Aggregation Points
their own systems and call centres)
Provision times and overview of the process for the provision of WBC Consultation will have to be extended into
SVLANs and AP bandwidth February 2007 to take commercial considerations into
account
QoS Pricing
Exchange to AP mapping for the trial
A Refresh on Migrations and Customer Experience
Status: Customer Information
Time (R) Cost (G) Quality (A)
Sat. (A) (A)
Line Access
Key Milestones RAG Status: Green
December/January Achievements Key Issues
The Line Access Working Group met on 18th January with 17
people representing 8 CPs plus Ofcom , BT Wholesale and Further work required in NICC, Consult21 Network
Openreach. The key topic was the continuing work on Voice Line Structures WG and in BTW to support the network
Access. aspects of the VLA product. Industry are concerned
that agreeing technical requirements and standards
are now on the critical path.
January/February Work plan
Further work is still required to establish market
The next meeting is to be held on 26th February 2007. The plan is demand for the VLA product.
to reissue the VLA Condoc by end January 2007, closing
consultation in March 2007. Future consultation will then to move The ISDN version of the product (most in demand) will
to Openreach. Feasibility April - May 2007. NICC Standards for not be available until at least a year after the launch
VLA become available approx July 2007. Aiming for launch of VLA in 2008 due to lack of standards.
in March 2008.
A technical sub-committee will meet in January 2007 to discuss
Standards and to liaise with Network Structures and NICC to help
to ensure that VLA standards are agreed at NICC in mid 2007.
Customer Information
Status: Time (G) Cost (G) Quality (G)
Sat. (G) (G)
Point to Point
Key Milestones RAG Status Amber
December/January Achievements
Key Issues
Working Group meeting held on 21st December , attended by
11 people, representing 4 CPs plus BTW and Openreach. Plan of record for sub 2M products needs to be further
amended to clarify some points.
Key issues covered were: ONES Condoc, Sub 2M Analogue
circuits, MSIL, Linkage and timing of Consultations Openreach WES/ONES Consultation document issued and
will finally close in January 2007.
January/February Work Plan Noting that Sub 2M products in 21CN have progressed to
RIA, Industry still have concerns that these
Next P2P WG meetings on 25th January 2007 and 21st developments are being given insufficient priority and
February 2007. resource. Work ongoing in January and February
BTW will issue a closure document in January 2007on Utility 2007.
Customers consultation. Utility customers Consultation closure report awaited and
ONES Condoc will close for final Industry input on 5 January in delay.
with an Openreach closure on 12 January 2007. CPs are concerned about the process allowing them to
Condoc on SVLANs within MSIL to be issued and discussions order and obtain space at Metro Nodes.
commenced in January 2007.
Customer
Status: Time (R) Cost (G) Quality (G) Satisfaction (G)
Information (G)
Migration Communications
Key Milestones
December/January Achievements RAG Status Green
At the 12th January Working Group a full discussion took place on:
Communicating Broadband. The recommendation from the Working Group was: Key Issues
i) the pooling of data which Carlson will use to distribute the material
Continued need for ISP
ii) the opt out option of ISPs distributing the material themselves. engagement/involvement in
This will be trialled and reviewed. this working group
Reseller Communications – agreed that a re-seller event (either virtual or face to face) is
required. Timing will be crucial – likely to be 2nd half of year. Joe will document
the proposal for the Steering Board meeting.
Product Withdrawals – agreed that a “Teaching the Teachers” event on product
withdrawal is required. Either virtual or face to face. Joe will present the proposal
at the Steering Board meeting.
December switched-on Dashboard circulated.
January/February Work plan
Continue work started on above key issues and the general switched-on communication
for the local communities and special needs requirements.
Next Working Group is planned for 2nd Feb.
Status: Customer Information
Time (G) Cost (G) Quality (G)
Sat. (G) (G)
Implementation & Migration (&CT)
Key Milestones
RAG Status Amber
December/January Achievements
Published: Key Issues (For Discussion)
Testing & Pathfinder update briefings 1. Framework required for planning for
Had the initial pathfinder 1a review meeting with industry Tranche 2/3 of DLE to NGS migration
The CTWG activities have been fully integrated into the Working [from I&P WG]
group plan
2. Resolution of the PEW window issue
January /February Work plan (phase1b +)
Confirm the plan for completing 1a migration – note ph1A RAG is 3. Timeline for ISDN migration required
currently red
Formally update Operational Readiness Reviews process for Ph1b 4. Further clarity/discussion of impacts
onwards required on BB migration
Complete 1a migration review implementation [ongoing through
experts groups]
Complete the migration process test exercise for voice quality gate 2
to quality gate 6
Test & trials workshop for BB (to finalise plan)
Commence pathfinder reviews for DLE to NGS migration
Status: Customer Information
Time (A) Cost (A) Quality (G) Satisfaction (A) (A)
Standard Contract Forum 2007
Update on revision of
AIT Annex E of SIA
Erica Cumming
Commercial Lawyer, Core Network Services,
Legal & Business Services
1 February 2007
Page 1
www.btwholesale.com
Standard Contract Forum 2007
Current Annex E outdated
• Definition of “AIT” too narrow
• Does not necessarily reflect what is happening in
practice
• Disputes are lengthened by involvement of too many
parties
• Unnecessarily complicated
Page 2
www.btwholesale.com
Standard Contract Forum 2007
Joint Effort
BT has been working with an industry group (incl. mobile operators,
originating and terminating network operators and aggregators) to redraft
the current Annex E
Aim was to make the process simpler and clearer
Greater clarity of the roles and responsibilities of the parties
Timeframes make the overall process more expedient
Use of standard forms
Parties required to put more effort into explaining why a retention
is made or reasons rejecting that retention
www.btwholesale.com
Page 3
Standard Contract Forum 2007
“AIT” has been broadened and geographic calls have been excluded
“AIT” 2 limbs: 1st Calls for benefit of a party connected to a
telecommunication service as a result of activity
by that party or on their behalf
AND
2nd Calling pattern of calls disproportionate to pattern
would expect from:
- good faith usage; or
- acceptable and reasonable commercial practice
Not “good faith” Situations which are NOT good faith usage or an
(paragraph 2.2) acceptable and reasonable commercial practice:
- customer is misled
- breach ICSTIS code (unless “minor” – as
defined in ICSTIS Sanctions Guide)
- activity intended to prevent billing system
capturing necessary information
Page 4
Standard Contract Forum 2007
Process Timeline:
1st “AIT calendar day” = 1st day of the calendar month after the date of
the call traffic
14th ONO sends A1 Retention Notice to TNO (16th if via TO) explaining
why they have a “reasonable suspicion” of AIT
26th ONO or TO provides AIT Call Data to TNO explaining why the
data shows a “reasonable suspicion” of AIT. If no data provided
A1 is withdrawn
34th If TNO disagrees issues a Rejection Notice
49th ONO or TO issues Dispute Notice, or may withdraw dispute with a
Withdrawal Notice
54th If unresolved then becomes an “AIT Dispute”. Parties free to
chose how to resolve the dispute (ie., ADR, court)
10mths After 10 months, an AIT Dispute deemed to be Resolved in favour
of ONO if parties to dispute have not:
- agreed to commencing a form of binding dispute resolution
- commenced court proceedings; or
- have agreement in writing of resolution (achieved via non-
Page 5 binding dispute resolution process)
Standard Contract Forum 2007
Initiating A1 Retention Notice:
Under the new Annex E provisions, in transit situations the A1 Retention
Notice can be issued by:
- ONO: ONO to the TNO via BT (ie., initial A1 retention
Notice via BT but then ONO and TNO to serve notices
directly on each other and merely copy to BT);
OR
- TO: In exceptional cases * BT (if BT has AIT Data which
the ONO doesn’t have – BT will deal directly with the TNO
and copy in the ONO)
*exceptional cases = only BT aware of AIT due to
nature of AIT
This will speed up the resolution process. It will also enable BT to respond
quickly to certain types of AIT which for technical reasons the ONO may
not pick up
Page 6
Standard Contract Forum 2007
Information to be provided as part of the A1 Retention Notice:
- Reasons for holding a “reasonable suspicion” of AIT (with
reference to the definition of AIT)
- Estimated value of sums to be retained
- Estimated total duration and/or number of relevant calls
- Start and end dates when relevant calls were made
- Full dialled telephone number(s) (unless exceptional
circumstances*)
*Exceptional circumstances may include informal/formal regulatory alerts
or investigations or calling patterns which suggest a party is attempting to
disguise AIT activity across a block of numbers
In exceptional circumstances may provide incomplete dialled numbers
provided uses best endeavours to supply full numbers as soon as possible,
but no later than 26th AIT calendar day
Page 7
Standard Contract Forum 2007
AIT Call Data:
- Partial CLI of calling party
- Full dialled destination number(s) (unless exceptional
circumstances)
- Start times, durations, dates
- Detailed written explanation of why the AIT Call Data above
supports a reasonable suspicion of AIT
In exceptional circumstances may provide data later, but still no later than
26th AIT calendar day
Page 8
Standard Contract Forum 2007
AIT Indicators:
- May be minor additions to list of AIT Indicators in current Annex E
- This will form part of wider industry consultation and will be
seeking views of industry bodies such as TUFF
- New methods of AIT are constantly evolving so may need a
mechanism to update the list…..
Page 9
Standard Contract Forum 2007
AIT Disputes:
- Arbitration problematic given nature of AIT disputes (ie., may involve
three parties across two SIA contracts, mediation or court proceedings
may be more suitable depending on the circumstances and in practice
AIT disputes have been dealt with relatively quickly once the relevant
parties start communicating)
- New Annex E will not proscribe any particular form of dispute resolution
– that will be totally up to the relevant parties.
- “AIT Dispute” = “a dispute relating to AIT or suspected AIT between a
Party serving an A1 Retention Notice and a TNO and which remains
unresolved:
(a) 5 Working Days after a Party has validly served a Dispute Notice;
or
(b) on the 54th AIT calendar day in the absence of a Dispute Notice
having been served…”
- Important Note: the new “AIT Disputes” in Annex E do not take away or
change the nature of any “SIA contractual disputes”
Page 10
Standard Contract Forum 2007
AIT Disputes:
- Standard of proof to permanently retain the sums is a “strong and
convincing suspicion” of AIT (whereas the initial retention requires
the slightly less onerous “reasonable suspicion”)
- 4 different AIT Disputes scenarios:
Non-Transit: 1. ONO & TNO
Transit: 2. ONO & TNO (all parties agree to let TO stay out of dispute)
3. TO & TNO
4. ONO & BT & TNO (may begin as TO & TNO dispute)
- Depending on the parties to the dispute (who may Parties under 2
different SIAs) the Annex sets out what will be accepted as dispute
resolution and indicates what consent is required, by whom and
whether or not a formal assignment of rights is necessary for
particular courses of action.
- Deemed resolution if parties take no action to resolve it after 10
months
Page 11
Standard Contract Forum 2007
Implementation Plan:
• Draft sent to the working group (1 Feb)
• Working group final comment (1 March)
• Aim to consult with industry at large (April / May)
• Will need to have a definite industry-wide commencement date
once all parties signed-up
• Release for signature (June / July)
New Annex E will benefit all parties by clarifying process,
speeding up disputes and lessening fraud or at least
identifying and halting it expediently
Page 12
Standard Contract Forum 2007
A1 Retention O ONO has “reasonable
suspicion” of AIT and
1. ONO Initiated Notice
serves A1 on TNO by
14th AIT Day
Non-Transit Retention
14 service TNO
AIT Call Data ONO provides TNO
with “AIT Call Data” by service TNO
26th AIT Day
26
If ONO doesn’t provide
Withdrawal Notice AIT Call Data ONO
serves Withdrawal (or is
deemed to) = NO AIT
TNO serves Rejection
Rejection Notice service
ONO Notice to ONO by 34 th
34 AIT Day
If TNO doesn’t issue
41 Rejection then must give
credit note to ONO (or
deemed to) by 41st AIT
Day
Dispute Notice ONO serves Dispute
Notice to TNO by 49th service TNO
49 AIT Day
Or ONO serves
Withdrawal [or is
deemed to] to TNO by
49th AIT Day = ONO
pays + interest
AIT Dispute ONO TNO
AIT Dispute
Page 13 60 AIT Dispute with TNO AIT Dispute with ONO
Standard Contract Forum 2007
A1 Retention O ONO has “reasonable
2. ONO Initiated Notice suspicion” of AIT and
issues A1 to TO by 14 th
Transit Retention AIT Day
issue TO re-issues A1 to TNO
14 by 16th AIT Day re-issue
TNO
16
service
AIT Call Data ONO provides TNO copy TO
with “AIT Call Data” TNO
(and copy to TO) by
26th AIT Day
26
service
If ONO doesn’t provide
Withdrawal Notice AIT Call Data ONO
serves Withdrawal (or is
deemed to) = NO AIT
TO copy TNO serves Rejection
Rejection Notice
ONO Notice to ONO (and
34 copies TO) by 34th AIT
Day
service
41 If TNO doesn’t issue
Rejection then must give
TO then gives credit credit note to TO (or
48 note to ONO by 48 th deemed to) by 41 st AIT
AIT Day Day
Dispute Notice ONO serves Dispute copy TO
Notice to TNO (and TNO
49 copies to TO) by 49 th
AIT Day
service
Or ONO serves
Withdrawal [or is
deemed to] to TNO
(and copy to TO) by
49th AIT Day = ONO
pays + interest
AIT Dispute ONO TO TNO
Page 14 60 AIT Dispute with TNO AIT Dispute with ONO
AIT Dispute
Standard Contract Forum 2007
A1 Retention O TO has “reasonable
3. TO Initiated Notice
TO sends copy of A1 to
ONO
copy suspicion” of AIT and
issues A1 to TNO by
Transit Retention 14th AIT Day
service TNO
14
AIT Call Data TO provides TNO with
TO sends copy of A1 to copy “AIT Call Data” (and TNO
ONO copy to TO) by 26 th AIT
Day
26
If TO doesn’t provide
Withdrawal Notice AIT Call Data TO
serves Withdrawal (or is
deemed to) = NO AIT
Rejection Notice TNO serves Rejection
ONO copy TO service Notice to ONO (and
34 copies TO) by 34 th AIT
Day
41 If TNO doesn’t issue
Rejection then must give
TO passes to ONO credit note to TO (or
48
deemed to) by 41 st AIT
Day
Dispute Notice TO serves Dispute
ONO copy Notice to TNO (and service TNO
49 copies to ONO) by 49 th
AIT Day
Or TO serves
Withdrawal [or is
deemed to] to TNO
(and copy to ONO) by
49th AIT Day = TO pays
+ interest
AIT Dispute TO AIT TNO
Page 15 60
ONO copy
AIT Dispute with TNO
Dispute
AIT Dispute with TO
Standard Contract Forum 2007
Any Questions?
Standard Contract Forum
1 February 2007
Keith Mitchinson
1 February 07
www.btwholesale.com
Standard Contract Forum
1 February 2007
DLE CLOSURE/21CN – SIA IMPACT: PROCESS
• Preliminary Contract Notice (6 October 2006)
• Interconnect Notification 06048 and
• SCF brief
• General Contract Notice (31 October 2006)
• Interconnect Notification 06050,
• SCF brief and
• SIA paragraph 28 notices
• Updated SIA Reference Offer (31 October 2006)
www.btwholesale.com
Standard Contract Forum
1 February 2007
INDUSTRY GENERIC CONTRACT CHANGES:
• Annex A - new para 3.4
• Annex D - revised “BT DLE” definition; new "BT
Virtual DLE", "EBC Matrix" and "VIC"
• Schedule 01 - new para 12.17 (VIC impact)
• Schedule 130 - new para 9.15 (VIC impact)
• Schedules 101/105/106/141 - largely DLE closure
impact
www.btwholesale.com
Standard Contract Forum
1 February 2007
SIA CONTRACT DOCUMENTATION
REVISED DOCUMENTS:
• 102 BT Transit Calls via the BT System
• 120 National Operator Assistance Service
• 122 International Operator Assistance Service
• 125 Emergency Service (including Post Code
Allocation for Fixed Emergency Calls)
• 143 Carrier Pre-Selection
www.btwholesale.com
Standard Contract Forum
1 February 2007
SIA CONTRACT DOCUMENTATION (Cont)
NEW SCHEDULE :
• 403 Operator Corporate Customer Service Calls
www.btwholesale.com
Related docs
