The development process is a highly standardized business process.
The process should be followed by all groups.
Approval needs to be recorded.
Customers should be able to track progress.
Some WF actors are notoriously slow, so their responses needs to be tracked.
Working Message QC Approval Solution Support Technical Review QA Business Analyst UA Approval User Acceptance Release to Production MTP Success Project Finished 30 Days Maintenance and Solution Support Approved Project Business Analyst Message “Map” Message Developer Specs OK Report Specs not OK Message Developer Develop Message Check Specs Business Analysis QC Check Internal QC Team QC not OK Message Developer QA not OK UA not OK slow
ABC business units act as customers, because projects are normally “sold” for a fixed price.
“ Solution Support” and several external providers participate in the development projects. External providers can connect to ]po[ via VPN.
The “internal company” represents the ABC EDI CC.
The ABC EDI CC consists of three departments for each of the tree geographical areas. These groups are modeled as]po[ Cost Centers:
Co: The entire EDI CC “internal company”
CoAm: Americas EDI CC group
CoAp: Asia Pacific EDI CC
CoEu: Europe EDI CC
Final customers are represented as a text fields
ABC EDI CC Solution Support External Providers ABC BU “Consumer” Co CoAm Dept. CoAp Dept. CoEu Dept. Customers Provider “ Internal Company” EMEA AMER ASPA ABC BU “Enterprise“ EMEA AMER Final Cust. A Final Customers Final Cust. B Final Cust. C Final Cust. E ... Final Cust. F ... $$$ Deliverables
Assignee: Who else is assigned to the current transition?
Owner: Owner of the underlying business object
Object Name: Name of the underlying business object
Relationship: What is the relationship between the current user and the workflow? “Assignment Group” means that the current user is assigned (task), “My Object” means that the underlying biz object has been created by the current user (tracking). Only WF admins can see tasks with relationship “none”.