Goals of process and services team:
- Move rules and decision making steps up-front in the process or embed in the UI supported with analytics
- Assess up-stream and down-stream process and decision points from the "Application Acceptance"
- Simplify the process flow and move decision flow to UI
Following the above criteria review requirements for services, rules and UI
- Services might include: Power usage data, projected generation capacity, excess generation
- Rules: Assist with equipment pre-purchase decisions and what-if, think about downstream contract setup
- UI: For example embedded analytics to assist with "what-if"
Based on inputs from other subgroups we can produce a service inventory, agree UI and Rules specs. Through collaborative modeling from Gravity Wave sequencing of services, rules and UI can be exported/imported from Gravity to BPM.
Current simplification of the model is shown below as modeled in 7.2:
New features in 7.2:
- Service composition to combine multiple service calls into one
- Auto generating VC forms based on process context
- Asynchronous messaging
- Human interaction via NetWeaver BPM by enriching PI ccBPM capability for system integration
- Flow rules for complex rule sets
- Reporting and analytics and email notifications