LMO This type provides the details of the platform the application is hosted on. It details the processor / core and model details to cater for licenses where the applications are tier or processor based. It is repeated for each platform. Operating system the applications operate on The version number of the operating environment. Total number of central processing units installed or available to the system in total The number of central processing units of the total available that are active Total number of processor cores available The percentage of the processing capability of the platform allocated to the instance Central processing unit feature code or type. For example “x86”, “i5”, “Cloud resource” or what have you. The manufacturer of the central processing unit e.g.. Intel, IBM, Motorola, AMD or what have you This holds details that relate to counts of things. For example the number of employees, the number of product lines, or the number of reports produced. The identity allocated to this count type which is defined per application The count value (integer) This component relates to an hourly consolidation of system usage. The consolidation will take place on a scheduled basis the frequency of which can be adjusted to reflect the granularity of the data required. It provides a picture of all application users that have been active in the previous time slice. The snapshot time period will be adjustable however it be must multiples of, or an even sub division of 60 minutes to allow for synchronisation of regional data collections on the hour. The data consists of details relating to the date and time the snapshot was captured, users and details of the modules / programs touched. The date and time the consolidate count relates to. This is the calculated period of time between snapshots in seconds. So if the snapshot was timed to occur ever hour the value would be 60. Total number of unique users included in this consolidation The a code identifying the application in use This contains session details and each program touched during that session. It is repeated for each session recorded. This is the unique identifier for the session. This could be the token, the job number workstation IP combination or something similar. This identifies the session type, Interactive, Batch, Queued etc. This type provides the details relating to "named user" including access permissions set within the application for the application details this type is part of. It is repeated for each user recorded. Is this user identity active for this application. User type relates to the user class/roll E.G. Admin, Accounts, Stores Languages that can be used by this User identity. Indicates the language for the associated object. This can be any valid language code. Program code details (repeated for every program) This type provides the details within the user application permissions type to detail the program access permissions the user has been granted in the application. It is repeated for program permission is granted for or denied for This type provides the details within the name user type to detail the module access permissions the user has been granted in the application. It is repeated for module permission is granted for or denied for. This type provides the details within the user application permissions type to detail the module group access permissions the user has been granted in the application. It is repeated for module permission is granted for or denied for. This standard application name BPCS, LX, LN, M3 etc. (Standard list to be added). Installed Location indicates in which location the product is installed This is the user identity that is specific to the application and is required for authentication and permissions within the application itself. Does the user have access to this (true or false?) User access type relates to the level of access to the application and differentiates between "Full users", "Light user" , or “Enquiry only.”