Chubb Case Study
Automated Workflow Process
A roles-based CMS was essential for Chubb due to the scale of the organisation. 'Roles-based' essentially means that different users have different privileges. Not only did each department need to have responsibility for their area of the site but Chubb Ireland (in effect a different entity) needed to control their site which would run off the same system, but have different content.
Scenario
A large organisation has 3000 documents that have to be added to its Intranet by the time of its launch in three weeks time. The deadline is looming, and the web team decide to hire temporary staff to enter the data into the system. Before they let the temps loose, they setup a workflow structure:
The temps will add the documents to the system. A department administrator will receive notification when a document is added. They will then proof it, make any amendments and submit it back into the system. An Authoriser will then be notified. They will review the document and if it is satisfactory, approve it. The document will now be 'live' and viewable via the Intranet.
Workflow structures can be setup to work with an organisation as a whole, or individual business units.
Document Index
- Company Profile
- The Issues
- Automated Workflow Process
- A Web Application - The Contact Wizard
- Virtual Walkthrough
- Conclusion
