|
PHASE I: DESIGN, DEVELOPMENT,
AND CONFERENCE ROOM PILOT
Consisting of up to five major events, the Design, Development, and Conference
Room Pilot phase establishes complete competence transfer between ScanData and
our customers, resulting in a ready-to-install system that fits all of our
customer's industry- and business-specific goals. Within the first primary phase, a
detailed gap analysis is constructed and reviewed; the base-line system is
configured with our customer's business parameters; and the initial product
training and testing begins.
Project Kick Off|
Detail Design
Process|
Parameterization and Training|
System
Development|
Conference Room Pilot
EVENT ONE: PROJECT KICK OFF
A Kick Off meeting is held via telephone conference or at ScanData's facility in
order to review the project scope and re-visit ScanData's product and processes
outlined during the sales process.
This event includes:
 |
Standard Operations Overview — Review of both ScanData's and our
customer's operational processes in order to familiarize all project
team members with the structure of existing processes. |
|
|
|
Project Scope Review
— Review all major milestones and
responsibilities for both ScanData and our customers so that all
parties have an understanding of the scope of the project. |
|
|
|
Project
Dependencies Review and Acceptance —
Review a list of the
project dependencies to be monitored and the projected deadlines so
that the proposed date of live use will be met. |
|
[Top]
EVENT TWO: DETAIL DESIGN PROCESS
During the Detail Design Process, ScanData's project team expands upon our
customer's functional processes outlined during the sales process, producing detail design documents for communications and hardware requirements as well as a
detail gap review for the operational processes.
This event includes:
|
|
Communications Detail Design
— Provides detailed design
documents, for all communications-related system parameters,
modifications, and customizations in relationship to all data
dependency and communications protocol required to drive the system. |
|
|
|
Hardware Detail Requirements —
Provides a detailed overview of
the hardware topology and third party software necessary to run the
ScanData solution according to the specifications outlined within the
Operational Functional Design. |
|
|
|
Operational Detail Design
— Provides our customer's Project Team
a clear understanding of the applications to be installed at our
customer's site and how they will work within that environment. |
|
|
|
Detailed Product Review
— Reviews the parameterized applications
to be used by our customers in order to begin training of specific
operational features contained within ScanData's base-line product. |
|
|
|
Detailed Gap Analysis
—
Provides a final review of the gap
analysis prior to any modification or customization necessary for
our customer's specific operational requirements. |
|
[Top]
EVENT THREE: PARAMETERIZATION
AND TRAINING
Once the detail designs have been fully defined, the base-line system is
tailored to fit our customer's industry-specific requirements. ScanData works
hand-in-hand with our customer's process supervisors to parameterize the
standard product, review the parameterized applications, and provide
administrative training of the parameterization processes.
This event includes:
|
|
Application
— Provides a high-level overview of all ScanData
applications to be used within our customer's operational
environment in order to facilitate future training processes. |
|
|
|
Parameterization
— Involves the configuration of the ScanData
product focusing on industry-specific rules for the utilization of
ScanData applications within our customer's operational
requirements. Parameterization is accomplished along with our
customer's supervisors in order to facilitate parameterization
training and a general application review. |
|
|
|
Parameterization Training
—
Provides training for the
parameterization of base-line applications to our customer's supervisor(s). Parameterization training provides supervisors with
the ability to manipulate configurations of the product as the need
arises. |
|
[Top]
EVENT FOUR: SYSTEM DEVELOPMENT
System Development involves the modification or customization of the ScanData
product in order to fit our customer's specific requirements that are not
included within the base-line system. Development also includes the construction
of the Communications host interface in order to provide competent data transfer
between ScanData and our customers' host system . Depending upon the complexity or amount
of development to be performed, a secondary development event may occur after
the conference room pilot as preliminary installation and training is occurring.
Our customers will be given a full review of the developed product prior to
final installation.
This event includes:
|
|
Modification (If Necessary)
— Change a feature, view, or process
within the ScanData product line in order to accommodate our
customer's specific operational and informational requirements. |
|
|
|
Customization (If Necessary)
— Add to or create applications or
reports within the ScanData product line to accommodate our
customer's specific operational and informational needs. |
|
|
|
Communications Host Interface
— Realizes data set parameterization
in relationship to all data dependency and the communications
protocol required to drive our customer's system and establishes a
connection between ScanData and the host system. Also involves the
parameterization and modification of data exchange, API mapping, and
communications user interface. |
|
[Top]
EVENT FIVE: CONFERENCE ROOM PILOT
During the Conference Room Pilot, a real-world view of the tailored product and
its functions are reviewed prior to implementation, and our customer's trainer(s) are instructed.
This event includes:
|
|
System and Application Detail Review
—
Reviews all functionality
and parameterization of the tailored system with our customer's
Project Team within ScanData's operational environment. |
|
|
|
Conference Room Pilot System Acceptance
— Our customer accepts the
tailored system acknowledging that it operates as it should. |
|
|
|
Training —
Up to three of our customer trainer(s) are trained in
order to fully utilize the applications within our customer's
operational environment. |
|
[Top]
| 
