The steps below represent a “typical” implementation for InventoryManager and MobileMap for new customers. Typical is in quotes here because every customer has different needs and constraints. Needs include regional considerations (species, products, markets), business considerations (in-house GIS capabilities, cruising by field staff vs. contractors, products), technical considerations (Esri licensing and architecture), etc.
This implementation is for deployments that do not involve customization or enhancements but do include standard configuration of documented functionality. When customization or enhancements are included, a unique list of steps and timeline(s) will be developed to ensure that these align with key milestones of the implementation, especially the testing and training events.
High Level Tasks
Design - Use a standardized process and templates to document requirements including cruise specs, merch specs, and reporting requirements to ensure these are understood and accepted by all participants
Configure - Use requirements created in prior step to implement all aspects of system including data model, MobileMap settings, InventoryManager settings, etc.
Test/Train - This is an iterative process that may include multiple phases (internal, key staff, all staff, contractors). Typically there is a training event for each testing phase to ensure testers are successful in testing.
Deploy & Support - Carefully coordinated deployment to ensure that all users have properly configured devices, have access to training materials, base maps, and are ready to begin production use of the system. For most scenarios, deployment will also include a transition of the Feature Service to the client’s AGOL or Portal instance prior to production use (sometimes this will happen during the Test/Train task above) For the support portion we ensure that all users have access to the appropriate support resources, and we schedule regular check-in meetings to ensure successful adoption.
Detailed Task List
Determine target GIS hosting environment
AGOL or Portal
If AGOL, determine if using ‘bundled’ solution (WSG’s organization) or customer’s organization
Determine compilation, reporting and integration needs
Compilation - is compilation support needed and if so is it via TCruise or integrated compilation within InventoryManager
Reporting - will InventoryManager provide reports (e.g., stand/stocking reports) form integrated compilation and/or 3rd party systems like TCruise
Integration - is there a need to integrate with TCruise, Trimble LRM, FVS, FPS or other forest information system?
Develop plan for evaluating acquiring and configuring devices
Register MM and IM in Portal and apply Client_ID and Settings to IM and MM settings (note that MM will need a settings file or document to enter these, can’t be imported from feature service when using Portal)
If relevant, register base maps and/or routing service with Portal
WSG updates IM settings using Portal registration and URL(s)
Test all functionality with new Feature Service(s)
Expand tests to include greater number of users, end-to-end workflows, etc.
Test all aspects of MM and IM with Portal authentication and services
Deploy and Support
Coordinate timing and process to deployment to ensure that all users have properly configured devices, have access to training materials, base maps, and are ready to begin production use of the system.
Ensure that all users have access to the appropriate support resources
Schedule schedule regular check-in meetings to ensure successful adoption.