|
One of our "lighthouse" customers for the
WAMware I-PROCESS product has been gracious in allowing us to share a
generic-ized version of their implementation. What is most striking is
that the project team -- the IT manager and an IT engineer from the customer
plus one WAMware implementation engineer -- had the I-PROCESS solution
defined, installed, configured and up-and-running in 5 days!!

|
Testimonial Comments from I-PROCESS "Lighthouse" Customer |
 |
Without
any programming, we defined our bid package process, installed and
configured I-PROCESS, and had the solution up-and-running in 5
days! |
 |
The
elegant simplicity of I-PROCESS has been key to the rapid and
eager user acceptance of our process automation project. |
|
|
Rodney Pack, IT Specialist, Vermax
Inc. |
|
In many
industries, it is critical that manufacturers control their design
processes to assure the visibility and traceability of all information and
decisions. This is important both for the efficiency of the product
development process itself, as well as the ability for the manufacturer to
satisfy industry regulatory requirements.
WAMware has developed a web-based
engineering process control system, I-PROCESS, that allows customers to
directly address these needs by defining in what order engineering,
manufacturing and related activities are conducted within the product
development process... and then capturing all decision points, approvals
and related data. |
A Case Study
Project for I-PROCESS
This subweb
provides an example framework on how "as-is" and "to-be" processes can be
captured together with pertinent actions, approvals and related documents.
This example represents an actual customer situation in which I-PROCESS is used to manage, control and trace the processes related to "bid
packages", i.e.
requirements definition, proposals to customers, order entry and
installation.
 |
First, the
customer documents the as-is paper-based
process with a complete description of the task flow and related
documents (2 days). |
 |
Then the
customer follows on to define the
detailed to-be process including information on actions, approvals
and specific task assignments (1 day). |
 |
From the
to-be definition, the Process Administrator or WAMware can readily
configure I-PROCESS (2 days, with no programming). |
|
|