|
|
Architecture for group
support tools
 |
Identify and characterize tools already used. |
|
Select the domains that can take benefit of each family of tools:
process management, document management and collaboration. |
|
Define technical and functional goals for potential tools
|
|
Propose a target scenario and an evolution framework to
reach that target. |
Business Process Management
|
Identify processes that are worth targets for automation I |
|
Select most promising processes |
|
Analyze,
re-engineer and specify selected processes |
|
Select a process technology according to characteristics of selected
processes |
|
Design and launch a project plan taking into account the needed
transitions steps and existing applications transitions. |
|
Measure results |
Group work
computer support, from the most structured one (Business process
management) to the most spontaneous one (real-time collaboration) |
Document and knowledge
management
|
Identify documents sources |
|
Identify documents to be digitized, and documents to be managed
|
|
Detect documents usages across business processes, with use scenarios
|
|
Define documents lifecycles |
|
Specify the life cycle management support system for each class of
document |
|
Select the technology, or set of technologies to handle documents and
knowledge according to their lifecycle specificities |
|
Define the project plan, including the plans to transfer all the
existing paper or electronic documents |
|
Measure results |
Collaboration and groupware
|
Identify the typology of group work
situations in the company |
|
Identify requirements for each class of situation |
|
Select groups to be part of the project, and according to that selection
conduct a return on investments analysis |
|
Specify technical requirements, and select one or several group
technologies |
|
Define a deployment plan, including any change management actions
|
|
Measure results |
|
|
