ASPIRE Upgrade Preparation Guidance

ASPIRE Upgrade Preparation Guidance


This article is intended to provide guidance for ASPIRE v5 customers to test a new release of the system prior to deployment for production use. The processes outlined are not representative of all potential configurations and usage of the system and do not constitute a warranty against issues occurring following the upgrade of a production instance to a later version of the platform. Customers planning to adopt a later version of the system should use this information as a baseline to develop a strategy that includes their business processes, licensed modules, integrations and other processes specific to their use of ASPIRE v5.

Test Environment

All processes to be validated prior to a production upgrade should be tested in a non-production instance of ASPIRE v5. If a test environment is needed please reach out to LTi Account Management.

System Inventory

In preparing for a production upgrade testing effort it is recommended that customers review their current usage of the ASPIRE platform to accurately gather an inventory of users, business processes and other critical information to establish a testing methodology. Examples of information to collect are:

  1. Users and roles – Active system users with respective permissions and business functions
  2. Reports – Reports used for daily, weekly, monthly and annual reconciliation efforts
  3. Business Cases – Sample transactions representative of common business
  4. Integrations – System or non-standard processes that retrieve or provide data to a third party
  5. Business Process Map – Visual representation of transactional ecosystem and business processes

Project Planning

It is recommended that a formal project plan with assigned resources and deliverables be developed prior to the commencement of testing efforts. An owner of the project plan to maintain it throughout the testing efforts with documented progress, representatives of functional business teams, representatives of technical teams and other critical business process owners should be considered stakeholders of the upgrade effort.

Planning Template

A sample template for documenting a project methodology is attached to this article and can be used as a baseline for constructing an approach that incorporates specific business processes into the validation of a later release of ASPIRE v5 prior to a production upgrade.

Working With LTi

Customers engaging in an upgrade testing effort should submit requests, inquiries or potential issues to LTi via standard Application and Technical Support processes. If assistance in planning and executing a production upgrade effort is needed, our Account Management team can provide further information as to the services available and their associated costs.

    • Related Articles

    • How to build a new User in ASPIRE v5

      See Attachment for detailed information on each step BASICS:   1.  Build a new Account 2.  Fill out the Login screens for that user, which will assign them to an existing Security Profile 3.  If the user needs to be able to process  Payments, ...
    • ASPIRE APR Calculation User Guide

      The functionality available in ASPIRE regarding the calculation of an APR and generating disclosure notification documents is available in the attached user guide. Attachment Contents Overview Configuration Options Application of the US APR in ASPIRE ...
    • Great Plains Configuration for ASPIRE

      See attached document for complete details. The attached document covers the required configuration between Great Plains and ASPIRE v5.
    • ASPIRE Navigation Video

      See linked video for complete details. The attached 21 minute video goes over navigating ASPIRE and understanding the menus and layouts available. Click here for the video.
    • ASPIRE v5 System Requirements

      ASPIRE v5 System Requirements For hardware capacity planning, LTi uses an historical model of database backup size to plan for future growth. This projection is usually configured for 1-, 2-, and 3-year growth, but can be configured depending on ...