|
|
www.johnstark.com |
|
|
|
Workflow structure definition The Workflow structure definition module is used to define the structure, flow and content of engineering activities. It is used to define the various tasks that make up each engineering activity, the relationships between activities, and the order and attributes of each task. These definitions will later be used by the Workflow control module to control the flow of work through engineering activities and tasks. A wide range of engineering activities has to be defined. Engineering activities vary in size and complexity from lengthy and complex activities such as multi-year multi-disciplinary projects to short and simple activities such as document release. For program management, the activities to be defined could entail all the engineering processes that make up the entire life cycle for a particular product. In other cases the workflow structure definition module may be used to define an activity that is effectively an individual task. The Workflow structure definition module is used to define the structure and flow of all these activities. The Workflow structure definition has to include all the information required to make workflow control possible. For example, for a particular process the module could be used to specify which users will be involved in design activities, which systems they should use, the information they will need, the information they should produce, the procedures and standards they should follow, and the approval process. The approval process work definition will include the specification of the roles, responsibilities, and authorities of the individuals involved, the rules and requirements for sign-off, and the process to be followed if sign-off is refused. The workflow structure should be as detailed as possible. It will be the source of work statements, defining the activities to be carried out, and the resources to be used. However, full detail may not always be possible, particularly as in early stages of an activity there may only be limited information available about processes and related resources. As a result, the Workflow structure definition module has to be able to work with varying degrees of information. Sometimes it will only be possible to outline the structure at the level of project phases, sometimes at the level of individual tasks. The structure of the workflow may be defined in different ways. Sometimes the workflow will already be well known in which case it can immediately be laid out in detail. In other cases, it may be possible to define the workflow for a particular activity by copying and modifying the workflow of an existing activity. Sometimes the workflow can be reconstructed by taking a finished product and working backwards to identify the activities used to produce it. In other cases the only solution may be to start with a blank sheet, and work forward to identify the individual activities that will occur. Once an activity has been started, it may be necessary to change the workflow, so the Workflow structure definition module has to be flexible enough to handle workflow changes. The Workflow structure definition module is made up of several sub-modules such as:
In the engineering change definition sub-module, the engineering change process has to be modeled. The various steps, reviewers, approvers and sign-off procedures have to be defined. The definition should include hierarchies so that if an activity does not occur, it will automatically be passed to the next highest authority. Since parts of the process are similar or repetitive, some workflow structure elements will be repeated throughout the overall workflow. The creation of change requests and orders is a typical example. In this case, automatic process sequences can be set up to handle tasks such as the provision of copies to individuals named on a distribution list. In addition to defining workflows, the Workflow structure definition module also has to provide functionality to formally manage and maintain workflow structures. As organizations evolve, and people change jobs, workflows will change. Formal definition and management of the workflow will provide opportunities to identify and remove unnecessary activities and to identify activities that can be run in parallel. Workflow structure definition can be seen as an enabler of Concurrent Engineering. |