Duration of workflow projects

[Robert Bates]

Stefan,
 
I'm afraid that my answer will be the usual consultant's answer when asked to
estimate ..... "It depends....".
 
The main thing that it will depend on is how close to the SAP standard templates
you will be. A two level approval workflow for invoices is provided as a
standard template, using the PD Organisation structure to determine superior and
superior's superior. If you use this, then the bulk of the time spent will be
setting up the organisation structure (unless you already have HR implemented)
which is a task I recommend you pass to responsible users, as ongoing
maintenance will be required. A Purchase Requisition release workflow is also
provided as standard - this uses tables in the MM part of the IMG to determine
the release levels, criteria and organisational units assigned - I recommend you
work with an MM consultant on this.
 
I have implemented the standard workflows for both scenarios in a couple of
weeks - however I can almost guarantee that when your key users test the process
they will come up with process changes they want which will require modification
of the workflow. These modifications could require ABAP skills if significant
deviations from the standard templates. Because a workflow is optimising a
business process, I find that the workflow design tends to be an iterative
process, where the users keep coming up with new changes as they practice using
the workflow - and this tends to lead to longer timescales for the project. If
workflow is new to the company, and you are rolling out to 2000 employees, then
user training becomes a big issue: although using workflow is simple, I have
found that it requires a new way of thinking from end users, and they need
plenty of "hand holding" before they use the system comfortably. I would
recommend a phased rollout.
 
If you can get the business to agree to follow SAP standard templates (or minor
variations of them), with a phased rollout,  then I would feel confident about a
2 month deadline. if you promise them that the workflow will incorporate all
their requirements then you may find the project lasts longer.
 
Good luck,
Rob.
 
To:       SAP-WUG at MITVMA.MIT.EDU
cc:        (bcc: Rob Bates/ITnet)
From:     Stefan Altendorfer <stefan.altendorfer at novaintegra.com>
Date:     03/21/2001 08:45:24 AM
Subject:  Duration of workflow projects
 
 
 
Hi all,
 
We are going to lead a project which has to implement a SAP Workflow based
purchase requisition and invoice approval scenario. We will have a max. 5
level approval scenario for purchase requisistions and a 2 level approval
scenario for invoices and all employees (2000) will be users in SAP and in
the workflow. We already have done the first Business Blueprint (showing
alternatives and solutions) and we now have to tell the customer if their
new goal to implement the whole workflow within 2 months is possible or not
(I doubt it).
 
For this project we were given only one Workflow engineer (which
unfortunately has no ABAP Knowledge) and if we have big luck there will be
an additional one with more experience and ABAP knowledge, otherwise I will
have to do the ABAP part. We will implement this solution on a 4.6B System
and we'll use MS Outlook instead of the SAP Inbox.
 
>From your experience, can someone tell me how long an implementation of a
standard workflow scenario approximately will take? I have heard times
around 13 Months which in my humble oppinion is very long, but I am not a
SAP workflow specialist at all (normaly working with CORBA, COM, XML and
SAP).
 
Thanks,
 
Stefan Altendorfer
 
 
 
 
 
***********************************************************************************
http://www.itnet.co.uk
http://www.itnet.co.uk/eb  -  Click here to see ITNET's ebusiness capabilities
 
Any opinions expressed in this email are those of the individual and
not necessarily those of ITNET plc and/or its subsidiaries. This email
and any files transmitted with it, including replies and forwarded
copies (which may contain alterations) subsequently transmitted from
ITNET plc and/or its subsidiaries, are confidential and solely for the
use of the intended recipient. If you are not the intended recipient
or the person responsible for delivering to the intended recipient, be
advised that  you have received this email in error and that any use
is strictly prohibited.
 
If you have received this email in error please notify ITNET Customer Service
Centre by telephone on +44 (0)121 683 4043 or via email to
csccom at itnet.co.uk, including a copy of this message.
Please then delete this email and destroy any copies of it.
***********************************************************************************