Dears,

Please schedule a session today to go through the audit steps that should be followed on Zain KSA.

Below points to be covered:

1- Sites Matching.
2- Decommissioning nodes (2 APIs are working properly)
3- XML import on daily basis.
4- All Serial numbers are available in XML and imported in NEP.
5- …etc

Thanks
Bassem

++ daljeet
Dears

Mostafa On leave today , so we need to schedule it tomorrow

Regards
Abir

Please join

Below points to be covered:

1- Sites Matching.
2- Decommissioning nodes (2 APIs are working properly)
3- XML import on daily basis.
4- All Serial numbers are available in XML and imported in NEP.
5- …etc

________________________________________________________________________________
Microsoft Teams Need help?
Join the meeting now
Meeting ID: 365 674 077 316 9
Passcode: og7Xe9An
________________________________________
For organizers: Meeting options
________________________________________________________________________________
Abir

From: Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Sent: Thursday, June 12, 2025 2:56 PM
To: Mostafa Kalawoun <Mostafa.kalawoun@mobinets.com>; Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>
Cc: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>
Subject: RE: zain KSA Sanity checks

Dear All,

Below points has been explained as requested except API which we will conclude on Monday.

1- Sites Matching. Done
2- Decommissioning nodes (2 APIs are working properly) Pending
3- XML import on daily basis. Done
4- All Serial numbers are available in XML and imported in NEP. Done
5- …etc

Thank you
Indrasan

Dear Indrasan,

Please find the doubts below:
1. If the nodes have actual site values in additional info, should it not be reflected in the Physical Inventory report? During the session, we checked some nodes that had actual site values in Add info, but these were not available under the Actual Site attribute in the Physical Inventory.
2. We need to know whether the API triggers after 21 days, deletes only the nodes, or also includes associated physical data like cabinets, boards, and shelves.
3. For NA nodes in Site Components, why are they still available after 21 days?

Regards,

NETWORKS TRANSFORMED

Mostafa Kalawoun | Telecom Support Engineer
Mob: +96170530179
Maarad Street, La Cite Building, 1st Floor
Tripoli, Lebanon
mostafa.kalawoun@mobinets.com | www.mobinets.com

Dear Mostafa,

Kindly find inline my answers in green..

Thanks

Dear Indrasan,

Please find the doubts below:
1. If the nodes have actual site values in additional info, should it not be reflected in the Physical Inventory report? During the session, we checked some nodes that had actual site values in Add info, but these were not available under the Actual Site attribute in the Physical Inventory.
[BS] it is a bug that is already highlighted. Please raise a jira to NEP DEV if not yet done. Indrasan to confirm if the jira is already raised.

2. We need to know whether the API triggers after 21 days, deletes only the nodes, or also includes associated physical data like cabinets, boards, and shelves.
[BS] Please confirm with Diana. I believe it should delete all data associated with this node.
3. For NA nodes in Site Components, why are they still available after 21 days?
[BS] please confirm with product if deleted node should appear in sites component report.

Thanks

Dear All,

No JIRA is raised for point 1 so @Mostafa Kalawoun you need to create the JIRA for same.

Thank you
Indrasan