Feasibility Check: Darwish Requirements for Cutover Process Modification (LS-783)

[LS-784] Feasibility Check: Darwish Requirements for Cutover Process Modification Requirements Writing Created: 14/Nov/25  Updated: 14/Nov/25  Due: 14/Nov/25

Status: Open Bug
Project: L3 Support
Component/s: FN
Affects Version/s: None
Fix Version/s: None

Type: Technical task Priority: Normal
Reporter: Shamim Ahmed Assignee: Khaled Khalil
Resolution: Unresolved Votes: 0
Labels: MS_OT
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

Dear @Abir Messaikeh

This memo outlines three key requirements from Darwish concerning the Cutover process. We require an assessment of their technical feasibility:

1. DP (Distribution Point) Selection Logic:
o Current State: During cutover, NEP determines the DP based on the existing (OLD) DP, using the provided OLD EXC, New EXC, OLD Cabinet, and New Cabinet inputs.
o Required Change: NEP must ignore the OLD DP. If the OLD DP is available within the New Exchange (New EXC), it should be used. If not, NEP must select any available DP from the New Exchange (New EXC).

2. Cutover History Management:
o Requirement: All existing data must be cleared from the Cutover History upon completion of the process.

3. Error Handling and Messaging:
o Current State: NEP currently displays a "Cutover successful" prompt simultaneously with a system error (as shown below/in the attachment).
o Required Change: When the cutover process is not fully/partially successful, NEP must correctly display a "Cutover failure" message instead of a success prompt.

Action Required: Please review these three points and advise on the feasibility required for implementation.


Generated at Fri Apr 17 10:34:00 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.