CHANGE REQUEST FORM
Reference Number (number allocated by BT): / e.g. CRv1.2/Ethernet/TDM/R1400/001(Roadmap version/product/deliverable/release/change no)
Product Group(i.e. Group, Cross-Product, Other): / e.g. Ethernet
Raised by:A N Other (company name)
Date (dd/mm/yyyy):
1. Description
Proposed Change:Description: / Description of proposed change (further details can be attached)
Justification: / Reason/need for proposed change
Type of Change: Please mark the appropriate category(ies) with an ‘x’
Strategic / [ ] / Product / [ ] / Commercial / [ ] / Delivery / [ ]Legal & Regulatory / [ ] / Service / [ ] / Customer Satisfaction / [ ] / Other / [ ]
If Other, please specify:
Required by: / Desired implementation date (and reason)
Dependencies: / Identify any known dependencies
Change requestswill be discussed at the appropriate Industry fora (e.g. Product & Commercial)
Date referred to Industry Forum(name of Industry forum & dd/mm/yyyy):
2. Industry Review (of Proposed Change)Recommended Action (based ondiscussions in Industry forum):
Referred for impact analysis by (name of Industry forum & date):
Communication Provider
& Openreach Client / Name of Lead / Contact Details
CP1 Company Name
CP2 Company Name
CP3 Company Name
CP4 Company Name
etc
Openreach Lead
Openreach Product Lead
etc
Rejected: / Reason / Deferred: / Date to which Request is deferred and reason
Priority of change request[1]: / Critical[ ] / High[ ] / Low [ ]
Assumed that full impact analysis will be required unless otherwise specified
Commercial Impact /
- Market
- Volumes
- Pricing/revenue
- Efficiency
- Other
- Key drivers, sector impact
- Volume projection, adoption & growth
- Price (if applicable) and timing
- Cost efficiencies
- E.g. Environmental impact
Cost Impact: /
- Development
- Operation
- Capex/investment
- Opex/recurring costs
Resource Impact: /
- Development
- Operation
- Impact on development and existing workstack
- Impact on operational resource
Delivery Schedule: /
- Roadmap
- Impact on current Roadmap (including indication of impact if candidate change necessitates promotion, demotion or substitution)
- Impact on Release schedule, development stack and prioritisation
Customer Experience: /
- Process
- Operations
- Customer Sat
- Impact on current processes
- Impact on operational manageability
- Impact on customer satisfaction
Other (e.g. legal): /
- Title
- To be specified as appropriate
Risk associated with not implementing the change: /
- As appropriate
Feasibility completion date[dd/mm/yyyy]
3. Impact Analysis Results
Summary of impact analysis (content of which was outlined in the previous section) to be attached:Impact of NOT Implementing the Change: / Summary impact of non-implementation
Alternatives to the Proposed Change: / Outline potential alternative solutions to proposed change
Impact Analysis reviewed by (Industry Forum & date):
Recommended Action:
1)Submit Change Request to OTA2 / [ ]
2)Change Request rejected / [ ] / Reason for rejection
3)Referred for further analysis / [ ] / Specify what areas require further analysis
4)Deferred / [ ] / Deferred date and reason
5)Referred to OTA2 for arbitration / [ ] / Reason
6)Other (e.g. alternative solution) / [ ] / Please specify
Name
/Company
/Signature
/Date
(dd/mm/yyyy)Note – electronic authorisation is an acceptable alternative to physical sign off via an agreed set of minutes
4. OTA2 Review
Recommended Action:1)Approved for implementation / [ ]
2)Other / [ ] / Please specify e.g. the change request may be referred for clarification/further analysis. In exceptional circumstances, the request could be referred to Ofcom for arbitration.
OTA Member/Product Representative
/Company
/Signature
/Date
(dd/mm/yyyy)The signatures above indicate agreement and authority to implement this Change Request
Note – electronic authorisation is an acceptable alternative to physical sign off (especially where the OTA is conducted by audio) i.e. the decision to implement would be captured in an agreed set of minutes
Page 1 of 5
[1]Critical = change to be implemented at first opportunity (in interim release); High = change to be included in first available major release; Low = to be scheduled at later date (as agreed)