An a19 best practice is to take the UAT system off-line when UAT is undergoing maintenance or configuration in preparation for End User Acceptance testing. This is to prevent any unauthorized access by end users that might want to start testing the system before it’s ready, which is never a good idea. After all, you don’t call the building inspector until you’re up to code, right? Leaving UAT available during configuration can be disastrous. Don’t make this rookie ISM mistake, you will thank me later!
Ivanti Asset Manager | Asset Scanner Requirements
Presently only available to android devices, more specifically Android OS Based Bar Scanning Devices, there are two models that have been tested by Ivanti.
IAM Asset Scanner Getting Started
- Purchase Asset Scanner device above.
- Download Ivanti Asset Manager Android App from Google Play Store
- Contact us to streamline your asset scanning and overall asset management operating procedures
Note: Enhancement requests have been made to include scanning ability for android smart devices (smartphone, tablet) with APP. There is a workaround for using android smart devices, contact us to find out more.
Ivanti Asset Manager | Asset Scanner UI
Ivanti Asset Manager | Asset Scanner Role Functionality
The Out-of-the-box (OOTB) functionality allows for scanning bar codes and looking up Asset Tags, creating and adding assets, with Asset Type, Sub Type, Asset Name, Serial Number, Location, Assigned Model, and Manufacturer. The “Scan Log” is then attached to the new/updated Configuration Item (CI, now Asset)
Ivanti Asset Scanner | Best Practice
a19 Consulting has taken the asset scanner to the next level customized the Asset Scanner UI with an asset scanning wizard that after scanning an asset tag walks you through creating a new asset or updating an asset, plus the ability to scan packing slips for procurement, with pictures of the packing slips, and 1 or more Assets (CI’s) attached to the packing slips, which roll up into the Purchase Order and Invoices for reconciliation.
When you are gathering Ivanti Service Manager (ISM) and Ivanti Asset Manager (IAM) requirements to build your Solution Design Documentation and Scope of Work (SOW) there is one very important best practice. Set Implementation Priorities!
Setting Priorities for your Ivanti Service Manager Project
Scoping is an art of finding the right balance between effort, benefits, and long term gains. Quick Wins should be your 1st Priority (P1) followed by long term gains which are Priority 2 (P2) and have the highest benefits.
For example, on a recent Asset Management implementation the core project team determined that the quickest wins and highest benefits would be asset scanning and a foundation for procurement and assets (hardware and software) that we could built upon on future phases.
That lead us to this high level scope:
- P1 – Ivanti Asset Manager | Asset Bar Code Scanning
- P2 – Ivanti Software Asset Management (SAM)
- P3 – Ivanti Hardware Asset Management Enhancements
What this meant was that we would build asset scanning capabilities not only for assets but also packing slips, replace the existing purchase order tracking excel sheets, and vendor inventory tracking sheets from Softchoice and various software vendors, with an Ivanti Service Manager product catalog for hardware and software, utilized the purchase order workspace for sales orders, enabled contracts and entitlements for software inventory, and built a softchoice integration to automatically update invoice and shipping information and functionality to reconcile against packing slips and purchase orders.
These were just our P1’s and P2’s! With further integration to discovery tools, enhancements to assets, and workflow automation for P3. Of course keep in mind that upon project completion some of the other requirements from the parking lot will become P1’s and P2’s and the cycle begings.
Along the way we identified more quick wins that improved overall product usability and project tracking:
- Ivanti Service Manager | Administrator Level 2 Role – for limited admin access with dedicated top level tabs to manage assigned validation lists and some configurations without full administration console access
- a19 Consulting Tracker – a custom built project tracking tool by a19 Consulting with backlog, artifacts, parking lot, status updates, project dashboard, heat release project and package tracking, to-do list, and many more features
- a19 Consulting Change Control with Announcements, Alerts, Notifications, and approval process for User Acceptance Testing (UAT)
- a19 Consulting UAT Test Scripts Workspace for ISM Administrators and Consultants to develop test scripts, run test scripts, log defect, pass/fail tests, request enhancements and identify show stoppers, must-haves, and nice-to-haves
One of the most crucial steps in System Development Life Cycle (SDLC) is User Acceptance Testing (UAT), a type of system and business objective validation, performed by the end users, and business objective sign off by the project owner; not to be confused with System Testing which is performed by the Ivanti Developer and/or ISM Administrator
Many Ivanti Service Manager implementations fall short when it comes to proper UAT Testing, be it due to a lack of resources, time, or budget, but more often than not due to a shortcoming of proper UAT Action Plan and UAT Test Cases and Scripts.
Today we will focus on a sample high level UAT Action plan:
- Refresh UAT with PROD (ISM Administrator)
- Push Asset Scanner Packages to UAT (ISM Consultant)
- Create UAT Test Cases/Scripts (ISM Administrator/Knowledge Manager; with assistance from ISM Consultant)
- Create Documentation for ISM Users (ISM Administrator/Knowledge Manager with assistance from ISM Consultant)
- Test Data Preparation (ISM Administrator)
- Test Run (ISM Administrator)
- UAT Run (ISM Administrator+ Storage Managers)
- Remediation (ISM Consultant)*
- UAT Run (ISM Administrator+ Storage Managers)*
- Including Validation of Documentation and Knowledge Article Creation (ISM Administrator/Knowledge Manager)
- Confirm Business Objectives – Sign Off (Project Owner)
- Schedule Push to PROD (ISM Consultant)
- Communication Plan (Core Team)
- ISM Change Control Announcement
- ISM Change Control Email with Documentation
- Determine schedule
- Before – for example 3 days before
- At PROD Push
- After – optional – follow up
- Determine schedule
- PROD Push (ISM Consultant)
- Validate PROD Push (Core Team)
- PROD Emergency Support – 1 to 2 hours after push – (ISM Consultant)