|
Implementation Services- Support your Project
Start to Finish
NDI offers a number of services
to help the customer meet their implementation milestones and budget.
Every new customer implementation will use a different amount of
service hours from each of the categorizes below, depending on the
complexity of the project, size and strength of internal resources,
and expected completion date.
Scheduling resources among multiple implementations is required
to match customer schedules to NDI implementation services delivery,
development of on-time enhancements, organizing release upgrades
to match customer needs and generally supporting acceptance and
beta test efforts.
Gap analysis is carefully conducted to make sure required features
are satisfied by existing functionality, report, and data flow and
that end to end processing meets customer expectations.
This is a detailed technical analysis to evaluate the best of many
possible ways to organize host data for the handheld routes. Customers
often start with a specific data design and alter portions of it
based on early processing results.
This is an early consultative phase to initiate server hardware
and system software ordering and evaluate how IT will provide system
software support and remote access
privileges to allow NDI to perform its routine software upgrade
and maintenance functions remotely.
RouteRider LE provides a standard semaphore mechanism to facilitate
the flow of data between RRLE and the back office system on a minute
to minute basis or a variety of other schedules.
Here the initial tables and input/out processing scripts are built
based on the customer’s expected data design. Parameters are
set based on the customer’s business rules, and the initial
version of software is provided in a small scale test environment.
Often customers will ask the vendor or a third party to set-up,
configure and delivery working handhelds and bonded Bluetooth printers
and spares for the implementation.
Typically a small core team of users is trained on site in the use
of the handheld computers, printers, and WebBI data queries to enable
acceptance testing. Later, when parallel beta testing starts, the
core team trains others with NDI support and consulting provided.
After data design results in the first flow in back office information,
the customer begins a very deliberate series of acceptances tests
to prove the data accuracy, the parameter settings, and that RRLE
functions as expected. Until data is proven this is a process that
requires NDI consultation to demonstrate processing is correct and
functions as expected. Once the customer reaches heavy cycle testing
the majority of data issues are resolved, configurations set, and
learning curve rapidly accelerating.. Once all functionality is
proven and accepted, the system is ready for a wider new audience.
The purpose of parallel Beta testing is to assure that in actual
use the new system produces the correct results and there are no
barriers to broader implementation.
Although enhancements are generally deferred until the system is
in production and users are accustomed to operation, many customers
will have one or two things they need to function slightly different.
The definition of any initial enhancements must be done very early
in the process in order that delivery coincides with final acceptance
testing.
|
