Data Explorer
The Data Explorer lets compliance and licence teams analyse the Nomasx-1 data on their own, without a new screen: rows, measures, filters and a period picked from a list of fields, shown as a table, a pivot, a chart or a KPI, then saved, shared, gathered into a dashboard and exported to Excel or PDF. It reads the data collected from every connected application, under the same rights as the screens.
How the explorer works — fields, shelves, views, drill, calculated fields — is described in the Liberty Next documentation. This page lists what Nomasx-1 ships.
At a glance
Where to find it
Data Explorer, right under Overview in the Nomasx-1 menu, opens the explorer with the three Nomasx-1 models in its picker. The picker switches from one model to another at any time; the analyses and dashboards follow the model.
Security
The users of each application, their status and last login, their role assignments, their profile (company, business unit, country, category codes) and their directory entry (department, title, manager), with the application and the roles around them.
Analyses: Users (with the technical and generic accounts), Users by status, Users by application, Users by company, Users by country, Users by department, Technical and generic accounts, Last logins by month — the older the month, the more dormant the accounts —, Accounts created by month, Users with the most roles, Users per role.
Dashboard Security overview: users by status, application, company and department; the last logins; the roles with the most users.
Segregation of duties
Every conflict found by the SoD matrix: the user, the two activities, the two roles that grant them, the process and the risk — and the summary of each refresh, for the trend.
Analyses: Users in conflict, Users in conflict by process, Users in conflict by risk level, Conflicts by risk, Privileged conflicts, Users with the most conflicts, Role pairs in conflict, Activity pairs in conflict, Users in conflict by company, Conflicts per refresh, Conflicts per refresh and process — one column per process.
Dashboard SoD overview: users in conflict by process, risk level and company; the role pairs; the trend across refreshes.
Licence compliance
The transactions of each user per table and day, the chain object → system code → licence component, the usage against the subscribed quantities, the financial exposure, and the employees per extraction date.
Analyses: Financial exposure, Financial exposure by component (price, support and total), Usage vs subscribed by component, Compliance gap by component — negative means more users than subscribed —, Transactions by month, Transacting users by component and by company — pick the period to apply a 90-day rule —, Most used tables, Employees per extraction.
Dashboard Licence overview: the financial exposure, the usage against the subscription per component, the transaction trend and the transacting users.
The transactions and the object → system code → licence component chain come from the JD Edwards EnterpriseOne usage collection. For another source, the Licence compliance model holds what that source's collection provides.
Shipped analyses
The analyses and dashboards above are shared: every user who may open the model sees them. They are updated with new versions of Nomasx-1, until someone saves changes to one — the local version is then kept. To adapt one without touching it, open it and use Save as.
Who sees what
- A model is offered to the holders of a role that grants it (Data Explorer in the role's Beyond the menus rules) — see Roles & permissions.
- The row-level scope of the user's roles applies inside every analysis: a user limited to one application or company sees only its rows, totals included.
Related
- Overview — Audit synthesis — the synthesis page.
- Saved analyses and dashboards — saving, sharing, exporting.