View
5
Download
0
Category
Preview:
Citation preview
Connecting Enterprises. Transforming Experiences.
NEWGEN SOFTWARE
COPYRIGHT 2016, NEWGEN SOFTWARE INC.
COPYRIGHT 2019, NEWGEN SOFTWARE
iBPS Process Modelling Capabilities
Pro
cess
Mo
del
ing Industry Standard Process
Modeling Notation
Single communication vehicle between Business & IT
Process Model always reflects what is running in production
One version of the truth with automated version control
Process Model is automatically validated
Pro
cess
D
ocu
men
tati
on Note down your
requirements related to the Process within the Process Map.
Complete browser-based access
Artifacts/Documents stored within the process model itself
Combined Process Model & Documentation
Key features – iBPS Process Modelling
Process Views
Milestones & Swim lanes
Project TreeProcess
Tree
Process Export / Import
Requirement Capturing
Ad-Hoc Task Initiation
Form Builder
Process Activities
Data Model Association
Process Validation
Process Versioning
SAP Integration Adapters
Process Artifacts
Audit Logs
iBPS Process Modelling Sequence
Divide the Process Design Canvas into milestones and swimlanes.
Use Start, End and Reject activity types to initiate and end process.
Use Workdesk to show user activities. Connect activities.
Add business requirements for each activity under requirements section of each Activity.
Use Data based Exclusive – If/Else for defining conditional routes.
Use Distribute Collect for parallel routing.
Validate the designed and completed process through registration.
Abstract View – A high level view to visualize Process Milestones
View Process Milestones and related
activities to visualize the process
overview
A BPMN compliant tool enabling users to DISCOVER & MODEL processes
Process Artifacts Process Properties
Drag and Drop
Components
Process and Project
Classification
BPMN View
Detailed Process
Route
Web Based Process Modeler
Adding milestones to the Process
Resizing milestone window width
Renaming of milestone
Resizing the milestone view
Add MileStones as vertical stages or phases in the process.
Adding Swim Lane
Add user or group of users who are supposed to work on that group of activities as Swim Lane. Either swimlane or each activity can be converted to a queue. A queue is like a shared list of items on which users can work.
Out of the Box Support for Role Based Queue
Out of the box support for
defining role based queues
User can define different
types of queues (FIFO/WIP)
based on business
requirements
Support for fixed
assignment on the basis of
filters & dynamic allocation
of workitems based on user
availability.
9
Defining Escalations and SLA
Define Escalation Matrix
Support for SLA definition for each activity
Out of the Box Process KPI reports
10
Automatic Prioritization of Workitems based on Rules
User can create multiple rules
for auto prioritization of
workitems
11
Data Definition
Associating transactional data
variables with the Process.
Creating Complex Variables to be
associated with the process.Ease of Reusability of (Address)
Complex Variable type
Generating Custom Templates
14
Gen
erat
e R
esp
on
se
Tem
pla
tes Allows user to register a
pre-designed custom template and associate it with the process
Can be generated at runtime using triggers or on Action buttons
PDF & DOC format supported G
ener
ate
Tem
pla
tes
usi
ng
C
CM
Su
ite
Inte
gra
tio
n Enables user to integrate with CCM suite and use the templates defined in CCM suite in the business processes
At run time process data is passed on to CCM suite to generate customized templates based on different rules
Process Modelling Guidelines❑ Requirements for each iBPS activity can be under the following heads:
❑ WHAT: Describe steps to be performed in the activity. E.g., Enter financial info, Small/Diverse certification, Contact info
❑ WHO: Process Role. E.g., Buyer. In ‘real life’, you will need to specify the system role for the systems in which the activity will be performed, after (after Role Mapping is completed)
❑ WHERE: The system in which the activity will be performed. E.g., EVEREST-ECC, or ‘C’ Drive of your laptop, or back of a napkin, or none (if performed within iBPS)
❑ WHY: Why is this activity needed? This will help determine optimize/eliminate/combine opportunities❑ WHEN: Timing of activity. Specify if timing is dependent on anything other than completion of prior activity. E.g.,
First working Day of the month❑ BUSINESS RULES: Specify conditions or rules affecting the above, or other parameters. E.g., IF HCL contract, use
SOW. If CG contract use Work Authorization Form.❑ SLA: Expected duration to complete the activity (in working days)❑ ESCALATION: Frequency of reminders and to whom sent. E.g., reminders to activity performer, with cc to their
Manager, start on last day of SLA and continue daily until completed.
❑ All process steps must be modeled. If some activities are to be grouped into one workflow step, specify those tasks in the ‘WHAT’ and specify the activities/boxes to be grouped in the ‘BUSINESS RULES’. E.g., If Process Metrics tracking does not need to be very granular.
❑ In your model, include activities having a downstream impact on other activities or reports. E.g., Capture Arrival Time of trailer at DC. This is an activity. The data will be used for reporting a metric comparing Arrival Time vs Goods Receipt Time. Without the activity to capture trailer arrival time, the reporting metric will not be possible.
Concept - Activity Properties View
Activities are defined within a Process flow. An activity is used when the work in the
Process cannot be broken down to a finer level of detail.
Access requirements tab of the Activity to
define detailed business requirements
Capturing Business requirements for Activities
Capturing business requirements in requirements tab at each activity level
Documentation Generation from Process Modeler
• Report generated including user activities only and business requirements using modifiable template
• iForm – define descriptions @section level, field level, generate form details in Report
• Document Attachments can be added in an activity which will be downloaded in Reports folder zip file as an annexure and will be referenced in main report
Process Report Annexure containing Form Details
Generate Process Documentation
iBPS enables the user to easily capture requirements while process designing. User can
generate the process specification document in HTML, PDF or DOC format.
File Upload & Download
SOAP & REST Web Services Integration
Data extraction & Initiation through Scanners
Java Messaging Service Bus
Email / Fax Server Integration
Data Base Linking
Out Of The Box Integration With Multiple Channels
24
Activity Types – Integration & Search
• Export Workstep is used to export the workitem data from process into the CSV file.
Export Workstep:
• The Query workstep is a dangling workstep in a business process, which has no incoming or outgoing links. It serves the primary purpose of defining a view for the workitems when they are opened for the purpose of status tracking, from the Query WorkDesk.
Query:
• Business Rule work step is used to add rules defined in the BRMS engine.
Business Rule:
• The DMS Adapter workstep allows the user to archive the workitem documents in the underlying Document management System.
DMS Adapter:
• OMS Adapter workstep allows the user to integrate the process with Newgen’s CCM Suite for generating dynamic rule based templates at run time.
OMS Adapter
Initiation Channels
SCAN CSV FILE UPLOAD EXCEL UPLOAD FTP/NETWORK PATH
INITIATION WEB SERVICE (DEFAULT
+ CUSTOM)
Recommended