The Oracle Utilities Network Management System minimally combines data from Geographic Information Systems (GIS) and Customer Information Systems (CIS) to form the operational electrical network model. Beyond GIS and CIS, NMS production deployments often include at least some data from one or more of the following:

Other more utility specific enterprise systems are also often integrated to Oracle NMS to help maintain the real-time operational NMS Electrical Network Data model (NMS model).

A typical Network Management System implementation has very little truly sensitive personal (utility customer data) involved in the construction or maintenance of the NMS model. The required personal information that is periodically extracted from the appropriate Customer Information System is generally used to identify or categorize utility customers. The required information typically includes customer name, address, phone and utility account number. Optional fields like "life support equipment," critical customer classification information and power usage data can also be used to help categorize customers for routine analysis. The majority of NMS Electrical Network Data model information is publicly available and as a whole is generally not considered highly sensitive.

Because the persistent data behind the Oracle Network Management System is not generally considered highly sensitive and because NMS systems typically reside behind multiple firewalls, NMS customers do not typically encrypt "data at rest" (on disk) or "on-the-wire/in-flight" (between core NMS components like the RDBMS and WebLogic). Specifically the vast majority of relevant Network Management System data is stored in an Oracle RDBMS. The NMS data that resides in the RDBMS is typically not encrypted on disk nor in-transit between the RDBMS and WebLogic by default - but can be.