~~NOTOC~~ ====== Overview of Reports ====== DMS includes a [[dms:The_Reports_Portal|Reports Portal]]. This is made available to Admin users in the same way the other web based interfaces are with the ability to control which reports Admin users can run. This section provides information on the many different reports. The reports are split into 4 different categories: * [[reports#Asset Tracking|Asset Tracking]] * [[reports#Project Reports|Project]] * [[reports#Schedule Group Reports|Schedule Group]] * [[reports#Survey Reports|Survey]] ====== Asset Tracking ====== There are 4 asset tracking reports: * [[dms:reports#AT1 Routes Detail|AT1 Routes Detail]]: lists all assets routes from a a selected location within a structure * [[dms:reports#AT2 Stock Summary|AT2 Stock Summary]]: shows stock of assets (totals) from a selected location within the structure * [[dms:reports#AT3 Location Detail|AT3 Location Detail]]: lists details of all assets from a selected location within the structure * [[dms:reports#AT4 New Stock|AT4 New Stock]]: lists stock totals of new assets by model from a selected location within the structure ===== AT1 Routes Detail ===== Run for a part of the OU structure the report shows all asset tracking routes for the selected portion of the structure. Each row details a given route between two asset locations showing the owner of the asset locations, the route direction and the source (asset_location) and destination (path) paths of the route. Where ownership isn’t set for a source or destination route path this is shown as **NOT SET** Where an asset location has no outbound route this is shown with a path of ** NO OUTBOUND PATH ** and a destination path owner of “N/A”. This indicates a terminating asset location, i.e. there is no path for assets to travel once in the asset location. Routes which cross into or out of the requested structure are included in the report. ===== AT2 Stock Summary ===== Used to report on the stock levels for a given part of the OU structure. When run, the report will report on the owner, asset location and stock levels for the asset locations within the selected portion of the structure. Both new and legacy computers are included in the stock levels. Stock can be: Stock: currently held in the asset location In pending: currently marked as inbound to the asset location but not yet confirmed Out pending: current marked as outbound to a different asset location but has yet to be confirmed. In Pending or Out Pending values indicate one or more asset transfers have been created which haven’t yet been confirmed (or rejected). ===== AT3 Location Detail ===== Used to report on the stock for asset locations, from a given point in the structure. Asset type can either be New, Legacy or Legacy(Rebuilt). New assets once deployed to desk assets retain asset type of New. Legacy assets which have been successfully rebuilt are set to a status of “Legacy (Rebuilt)” to distinguish them from legacy assets which haven’t been rebuilt. Status can be Stock, In Pending or Out Pending. For pending transfers (in or out) Route shows which inbound or outbound route the asset is on. Assets which are in Pending are not considered stock until the asset transfer request is accepted. ===== AT4 New Stock ===== Used to report on the new stock levels by asset location and model for a given portion of the structure. Only New assets are counted. Legacy assets are not included, nor are Legacy (rebuilt) assets. Only asset locations holding stock are listed. Zero stock levels are not reported ====== Project Reports ====== There are 6 project report. Project reports typically allow you to select a given point in the project structure and report across all the data within that section of the structure. * [[dms:reports#PR1 Project Schedule|PR1 Project Schedule]]: lists the start (T-0) and end dates of all all Schedule Groups within the project structure * [[dms:reports#PR2 Application List|PR2 Applications List]]: lists all component Applications and their properties by Schedule Group availability * [[dms:reports#PR3 Deployments|PR3 Deployments]]: lists total number of successful desktop and laptop deployments by date from a selected location within the structure * [[dms:reports#PR4 Deployment Failure|PR3 Deployment Failure]]: lists all failed deployments by date, including fail code and deployment user, from a selected location within the structure * [[dms:reports#PR5c Project OU Report|PR5c Project OU Report]]: Deployment details plus custom field * [[dms:reports#PR5 Project OU Deployment|PR5c Project OU Deployment]]: Status of deployments * [[dms:reports#PR6 Deployment Applications|PR6 Deployment Applications]]: Show application package IDs for each deployment for a selected deployment date ===== PR1 Project Schedule ===== No parameters required. Shows every schedule group defined for the DMS instance. T0 date is date set in the DMS console to indicate the first deployment date. End date is the latest deployment day listed for the schedule group. i.e. the last available deployment day for the schedule group. This date will be shown even if the available slots for the day is set as 0. If the deployment window hasn’t been set then this field is blank. ===== PR2 Application List ===== No parameters required. List every application available for each schedule group, including if its mandatory, set by default or designed specifically for laptop deployments. 1 indicates true, 0 indicates false. ===== PR3 Deployments ===== Parameter: Select portion of structure which report is to include. Reports the number of successful deployments by date grouped by desktop and laptop The only available status is Deployment Successful Only dates which have either successful laptop or desktop deployments are reported. Scheduled deployments are not reported. ===== PR4 Deployment Failure ===== Parameter: Select portion of structure on which report is to be run. Details each individual failed deployment for the selected portion of the structure. Only values for Deployment state are either 6F Deploy failed or 7R Rescheduled. Failure reason code can be defined in the system. Scheduled date is date on which deployment was due to occur, not date of failure. ===== PR5 Project OU Deployment ===== Parameters: Select portion of structure on which report is to be run, Start date to include, End Date to include and use completed date. Details each individual deployment for the selected portion of the structure including user legacy plus new asset, schedule status and notes. Report is limited to dates entered unless one or both dates are blank in which case all dates are reported. By default schedule date is used for Start/End dates. If use completed dates is checked then the deployment completed date is used instead of schedule date. It provides a detailed snapshot of each deployment and its current status. Report will include deployments in all states, included completed, failed and rescheduled. Where a deployed asset model is different type to the expected model type then new model is shown as “model deployed !! EXP model expected”. Status will show the state of the deployment, from Edit through to User Accepted or Deploy Failed. If deployment is overdue (schedule date < actual date) the “Overdue” is appended to this column. Not all columns will necessarily be complete as this report will show deployments whatever the state, i.e, no date, no new model, no new asset details. Note column will show first 200 characters of last entered note associated with the deployment. If more than 200 characters have been entered this will be indicated by three ellipses at the end of the text, e.g. “more text...”. Any commas (,) within column Note is replaced with a semi-colon (;) and line breaks are removed. Given the number of columns and data shown it is expected that once generated the report will be exported in CSV format. ===== PR6 Deployment Applications ===== Parameter: Select schedule date of deployment. The PR6 report has been designed to show all the application packages per deployment for a given date. It enables a report to be generated to show exactly which accounts will be involved in a deployment on a specific scheduled deployment date. The report will show the Account ID, Legacy asset (Asset tag), new asset (asset tag) and package_id. If a deployment has no linked application packages then a single report row will still be generated showing the other available columns. If the deployment is a rebuild then the legacy asset is also duplicated into the new asset field. If the same account ID has more than one deployment for a given day then you need to use the legacy and new asset fields to determine the deployment it relates to. Only deployments with states 5 -Deploy Ready, 6 -Deploy Success, 7 - User Accepted and 7F - User Acceptance Rejected will be included. Deployments with other states are excluded. ====== Schedule Group Reports ====== There are 8 Schedule Group reports. Schedule Group reports are run against a selected individual Schedule Group. * [[dms:reports#SG1 Deployment|SG1 Deployment]]: lists all deployments for the selected Schedule Group * [[dms:reports#SG2 RAG Status|SG2 RAG Status]]: lists the T-Schedule tasks and their respect RAG Status for the selected Schedule Group * [[dms:reports#SG3 Users|SG3 Users]]: lists the core user details for all users for the selected Schedule Group * [[dms:reports#SG4 User Applications|SG4 User Applications]]: lists deployment applications by user (username and email address) along with package ID, deployment ID and deployment date * [[dms:reports#SG5 Schedule Group Deployment Dates|SG5 Deployment Dates]]: lists deployment dates and availability for the Selected Schedule Group * [[dms:reports#SG6 Schedule Group Deployment Report|SG6 Deployment Report]]: lists deployment applications by user (username and email address) along with package ID, deployment ID and deployment date * [[dms:reports#SG7 Deployment Peripheral List|SG7 Deployment Peripherals]]: details the number of each peripheral model required for the selected Schedule Group * [[dms:reports#SG8 Hardware Summary List|SG8 Hardware Summary]]: details the number of each hardware model required for the selected Schedule Group ===== SG1 Deployment ===== Parameter: Select schedule group to analyse. Detail each deployment for a given schedule group. Scheduled date is date on which deployment will or has occurred. Deployment is included irrespective of the deployment status (e.g. may even be rescheduled). A user can have more than one deployment, which would appear on multiple lines. Deployment ID is not shown in this report so may look like duplicates if other details (e.g. date/model) are the same. ===== SG2 RAG Status ===== Parameter: Select schedule group to analyse. For all tasks within a schedule group, show the task, its t-date, completed date and RAG status. RAG status is Red, Amber or Green. A status of ‘.’ shows that the task is in the future and has not triggered the amber alert status yet. A completed task always appears as green irrespective of its state prior to completion. T-date indicates planned number of days/weeks prior to t-0. T-date is either days or weeks dependent on system wide setting. ===== SG3 Users ===== Parameter: Select schedule group to analyse. For the selected schedule group list all users alongside their primary contact and location information. List the number of deployments allocated to that user. A user can have 0, 1 or many deployments. A deployment is included in the count even if the deployment has already been completed, it has failed or marked as rescheduled. Vip values; 1=vip , 0= normal user. ===== SG4 User Applications ===== Parameter: Select schedule group to analyse. For the selected schedule group list all applications and package ids required for each deployment. As a user may have more than one deployment this can be seen by looking at the deployment-id. Each deployment can have many packages associated to it. An application is listed one per line. Deployment date is shown when a deployment date is set. Report will include completed, failed and rescheduled deployments as well as upcoming deployments. ===== SG5 Schedule Group Deployment Dates ===== Run for a specific Schedule group the report details the deployment window dates showing one row per day and the number of available and scheduled deployments. An additional row at bottom of the report shows the total number of deployments which haven’t been assigned to a deployment date. This row has a blank schedule_date. Deployments available shows the number of available slots for the given day. This can be negative if the deployment date is over scheduled. Deployments scheduled includes Rescheduled, Failed, Scheduled and completed deployments. ===== SG6 Schedule Group Deployment Report ===== Run for a specific Schedule group the report details each deployment and its current state. Where a build has been completed its state is shown, including new asset details where appropriate. Where a user has more than one deployment, all deployments are listed on individual rows. Completed timestamp is time the system was updated with its current status. If a deployment is a rebuild of a legacy asset then the rebuild column is marked as “Rebuild”. ===== SG7 Deployment Peripheral List ===== Run for a specific Schedule group, the report details each peripheral by deployment. Summary of new hardware and peripherals required for a schedule group. Deployments with no new model type selected are not shown. Deployment date shows the scheduled deployment date. ===== SG8 Hardware Summary List ====== Run for a specific Schedule group the report details the number of each peripheral and new model required. Report will include deployments in all states, included completed, failed and rescheduled. If this report is run once a schedule group has started then further analysis will be required to ascertain correct number of new peripherals and computers required. A rebuild deployment will count a new piece of hardware if the new asset model has been (incorrectly) set in the deployment. ====== Survey Reports ====== There are 2 Survey reports and these allow you to view any data collected via the User Survey in the User Portal. ===== SV1 User Survey Detail ===== Run without parameters the report provides details of recorded answers for each deployment. Comments are also recorded. Survey results provide question answer value pairs giving both question name and recorded answer. The separator between value pairs is set as a semicolon ‘;’. Possible answers are: ^ Value ^ Meaning ^ | 0 |Not Applicable | | 1 |Very Dissatisfied | | 2 |Dissatisfied | | 3 |Satisfied | | 4 |Very Satisfied | The web portal should ensure that all questions have an answer. Where questions have been added or removed, this can be derived from either having more or less answers. All answers in a survey are mandatory. Completed date shows the date the survey was completed by the user. ===== SV2 User Satisfaction Survey Summary ===== Run without parameters the report provides a count of the number of recorded answers for each survey question. As multiple surveys can be used (for different schedule groups), the survey is identified by name. Number of surveys completed can be calculated by adding up the answers for a single survey question.