Business Process Automation

Business process automation projects can vary in scope, nature and type of solutions used. But one thing is certain - the more accurate information is available in the form of requirements the better outcome can be expected. We offer our clients a great opportunity to miss as little as possible by using the best of breed approach to gathering requirements. The issue with requirements is that no-one has the entire idea of what the future state will look like and that getting to the bottom of takes a collaborative effort.

That’s where it becomes tricky. Getting various points of view combined together into coherent and useful output is not an easy task, one that takes a lot of time and skill. What we offer you is a collaborative approach that lets everyone provide the input and get the best set of requirements in the end. The key is the use of future process design that lets us link all the pieces together.

Using our services you will get both the big picture and the necessary level of details in each of the individual processes, both at operational and requirements levels.

Individual diagrams and requriements

Individual step requirements:

Process Step: Fill  E-room Creation Request Form

Actor: Project Manager, role

Actor: BPM application, Web Publisher application

Description: The requesting business user refines the request to include 

Data set:

• name of the room
• user id, first name, last name
• access - home/.work
• go live date
• can the user be trained prior to go live date?
• purpose of the room
• business issue addressed
• manager 

Use Case: 

Requirements:

a. Users fill a form with required room creation information

b. Form is validated for completeness

c. If all the data is there the next step is triggered by BPM

d. If some data is missing the users are given a friendly message to complete the fields

e. There should be a way to report against the data in this form.

f. The data should be saved if not complete. The taks remains in acquired state until it can be completed.

e. User chooses the eroom template on the form and completes the task.

f. Users types in the eroom group name. The field is limited to the eroom standard.

g. BPM will automatically populate the room based on the selected template.

h. If the form is not complete the form should be returned to the requestor, all the data is saved.

Gap Analysis: 

Custom: Yes

Config: Yes

OOTB: No

Gap Comments: 

Custom Development needed. The form will need to be designed and developed in the BPM Forms Builder. Fields in the form will be processed based on rules defined in Forms Builder.  The form has an underlying data structure that will allow saving the data even if the task is not complete.  On average, how much time is required to build a form?

Estimate - 2-3 days before testing depending on the form

———————————————————————————————————————————————————————-