Dear @Salim Ali Abubakar,

Generic Connector introduced to reduce the number of small connectors with different Dump format.

As mentioned in below sample case ,If the node discovered via BMC, it should come in NEP via IT xml import.
There is no need to import via Generic template. Because as per the current logic , if you import via Generic, it will show error as the preference given to Active Inventory over Generic (IT Inventory comes under one of the Active Inventory).

Now If the time taking to provide the Serial to the asset is long, still it will be available in NEP IT Inventory for the financialization.

Try to have a sample case where an Asset is not able to import in NEP having the TAG ID with below mentioned conditions :

1) Asset must not be present in Passive DB.
2) Asset must not be coming via BMC discovery or any active Inventory.
3) Asset must not be present in any of the Warehouse , where it can track with TAG ID.

NETWORKS TRANSFORMED

Daljeet Singh Virdi| Senior Telecom Engineer
Mob: +91 9717304711
1102-1103, Tower C, Unitech Cyber Park, Gurgaon
daljeet.virdi@mobinets.com | www.mobinets.com

From: Salim Ali Abubakar <Salim.A@cybermak.net>
Sent: 25 November 2024 05:41 PM
To: Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Medhat El Shenawy <Medhat.M@cybermak.net>
Cc: ALM Support <ALM.Support@cybermak.net>; support <support@mobinets.com>; L2_Team_Leb <L2_Team_Leb@mobinets.com>; Mohamad Ezzedine <Mohamad.Ezzedine@mobinets.com>
Subject: RE: ZKW | GENERIC TEMPLATE | NEW SEQUENCE ENHANCEMENT

Dear Daljeet,

As per a sample business case,
Consider an IT node that is discovered by BMC with a tag number manually imported through Generic template into the NEP with a Tag number which is given to the asset before being Serialized.
Note that sometimes the serialization may take a lot of time thus assets are provided with temporary Tag Numbers.
Once the assets are serialized and imported into the NEP, Necessary changes to the assets should take place which will be the registering of the SN into the assets.

Should you have any questions or require additional details, please feel free to reach out to me.

Kind regards,

Salim Abubakar,
ALM Support Team.
CyberMAK Information Systems.

to be resumed in Q1 2025 upon management decision

WL for changing the sequence between generic and passive: 5 days
+WL to add shifting base on tag nb from generic to passive: 3 days
+testing: 2 days

Dear @Hassan Abdine,

Currently, the shifting is being performed based on the Serial Number, wherein Generic elements are given higher priority over Passive elements.

Please note that there is no rule implemented based on Item Barcode.

Kindly find the attached email containing the relevant documents outlining the rules based on Serial Number.

For reference, Passive elements here refer to assets present in the Passive Database (DB).

NETWORKS TRANSFORMED

Daljeet Singh Virdi| Senior Telecom Engineer
Mob: +91 9717304711
1102-1103, Tower C, Unitech Cyber Park, Gurgaon
daljeet.virdi@mobinets.com | www.mobinets.com

From: Hassan Abdine <Hassan.Abdine@nuiva.com>
Sent: 02 July 2025 11:33 AM
To: Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>
Cc: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Aurobinda Panda <Aurobinda.Panda@mobinets.com>; Mostafa Kalawoun <Mostafa.kalawoun@mobinets.com>
Subject: Re: Zain KW | Generic Enhancement for Passive DB elements

Hi Daljeet,

Could you please highlight the difference between the current rules/priority and the new ones?

Thank you,
Hassan
________________________________________
From: Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>
Sent: Monday, June 30, 2025 12:00 PM
To: Hassan Abdine <Hassan.Abdine@nuiva.com>; Hassan Abdine <Hassan.Abdine@nuiva.com>
Cc: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Aurobinda Panda <Aurobinda.Panda@mobinets.com>; Mostafa Kalawoun <Mostafa.kalawoun@mobinets.com>
Subject: Zain KW | Generic Enhancement for Passive DB elements

Dear @Hassan Abdine,

Pl find the below new request shared by customer for Generic enhancement in terms of Passive DB assets.

Kindly go through it and provide your valuable feedback for the same.

I would like to clarify the logic for the Generic Connector – Shifting Passive Assets by Barcode, especially in light of some observed contradictions.
Please review the below refined and elaborated logic, and confirm if it aligns with your expectations — or advise if there are any comments or changes needed:
________________________________________
Passive Asset Handling via Generic Template
When a passive asset dump is loaded through the Generic Template, the system will behave as follows:
• If the asset already exists in the mobile app passive inventory (based on ItemBarcode):
o Priority will be given to the Generic Template Passive Asset details.
o This means the asset’s attributes (Site ID, Category, Part No, Model, etc.) will be updated/overwritten using the Generic Template.
• If the asset is later removed from the Generic Template:
o The system assumes it is no longer being managed externally.
o It will revert to using the mobile app inventory as the data source (if the asset still exists there).
• If the asset reappears in a future Generic Template dump:
o The system will again prioritize the Generic Template and update the asset attributes accordingly.
• Important Note on Updates:
o Passive asset attributes will only be updated when the asset is present in the Generic Template.
o If it is removed from the template, the system will no longer apply updates from it and will rely solely on the mobile app inventory.
________________________________________
This clarification is to address the earlier confusion regarding how the system can prioritize the Generic Template and yet update passive asset attributes consistently — the key is updates only occur when the asset exists in the Generic template

Dear Salim, Medhat

We had a discussion with our product team and it is understood from the scenarios described by Daljeet from Al Duraidi that we need to update our rules so that AL duraidi corrects partially some data available in existing Passive DB through generic template for some period of time however initially the generic template was designed to import data one time, also there is a possibility to revert back on old data provided in Passive DB again which is creating too much complexity. Since those changes are provided initially manually by Alduraidi /Zain KW, we need to check the possibility to apply those data change on Passive DB directly manually and not NEP and we continue our usual daily sync for updated data without any rules updates since our main source of information for daily update of passive element is the Passive DB

This is the context of our discussion so let us know your feedback accordingly

Regards
Abir

as discussed, as CyberMark are the master of passive data, they shall be responsible of updating passive attributes, and NEP will sync ...

We are checking with Cybermak to provide suitable to discuss the way forward on this tickt.

As checked with Cybermak they will check internally to way forward on this ticket.

Closure confirmed by Customer