This Web-based application is a workflow that manages business processes/tasks. Tasks and their subtasks will be set up in their own area, then certain roles can pick and assign the tasks to participants who are assigned roles. Roles will define security. The workflow will have a graphical metaphor that shows steps, decisions, rules etc. The workflow will give the ability to re-assign tasks in the workflow to others either permanently or for a given time period that when reached will revert back to the original. The set-up functions will include: Define Organization Types Define Organization Define Tasks/Subtasks (Activities or Deliverables) Define Checklist Types Define Checklist Assign Checklist Define Deliverable Assign Deliverable to task Assign due dates to task, subtask, checklist Comments area for each task Select comments type (radio button?) Define Organization hierarchy (HR, Sales, Finance etc.) Define Role type Assign Roles (employee, contractor, external) Define Security Profiles based on role Define Alert/Event types Define Alert/Event messages Define Approval types and approvals Define Calendar Attach Documents - MS Office, Images etc. Components of the design will include e-mail notifications to the task owner based on task completion by a subordinate. The e-mail will contain the URL for the login, whereby the application will present an "inbox" containing the completed task(s) waiting for approval appearing on the checklist. A checklist may also have a hierarchy rolling up to another checklist. As these tasks complete, if they are part of a larger task, an indicator showing percent complete will be updated. Example - if a task has 5 subtasks, and 4 are complete (approved in the workflow) then the indicator will show 80% complete for the task. The manager hierarchy will allow any manager to have visibility to all downstream participants, tasks, etc. The hierarchy for the workflow will allow the top manager to assign tasks/checklists to subordinates. The subordinate roles can then delegate the checklist or tasks, or set up new tasks and assign to their subordinates and so on. Each task approval, disapproval, attachment will be logged/archived so that when the major task is complete, all history is stored under the task name. The events will be in a report.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased. 4) Code must be well-documented. 5) Technical writing resource will work with developer to produce tech doc. for the system.
Developed for IE browser. Web-based front-end, RDBMS back-end. Technology used can be front end tools such as Front Page, JSP, ASP. Database can be SQL/Server or Oracle. Other technologies will be considered if widely used. Platform can be Apache/Linux or NT. Transaction volume will be low, but System must scale to perform well with 30-50 concurrent users on a one/two CPU Intel class server.
## Deadline information
Please review overall requirements. If Oct. 30, 2002 is too aggressive, a compromise would be a working Pilot or Demo that will have a large percentage of the functionality, with the remaining functionality to be completed shortly thereafter.