University Academic Program

Pega’s University Academic Program

Emergency Help Services

(Use Case)
University Academic Program

Copyright 2020
Pegasystems Inc., Cambridge, MA
All rights reserved.

This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and
product are protected by copyright and distributed under licenses restricting their use, copying, distribution, or transmittal in any form without prior
written authorization of Pegasystems Inc.

This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of
Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any
commitment to offer or deliver the products or services provided. This document may include references to Pegasystems product features that
have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult
your Pegasystems service Consultant.

PegaRULES, Process Commander, SmartBPM® and the Pegasystems logo are trademarks or registered trademarks of Pegasystems Inc. All other
product names, logos and symbols may be registered trademarks of their respective owners. Although Pegasystems Inc. strives for accuracy in its
publications, any publication may contain inaccuracies or typographical errors. This document or Help System could contain technical inaccuracies
or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in
the information described herein at any time.

This document is the property of:

Pegasystems Inc.
1 Rogers Street
Cambridge, MA 02142
Phone: (617) 374-9600
Fax: (617) 374-9620
www.pega.com

Document Name: Emergency Help Services

Date: 10-06-2020
University Academic Program

Table of Contents

Contents
1 <Emergency Help Services - No. of Hours> ............................................................................................................... 8
University Academic Program

1 <Name of the use case - No. of Hours>

Use Case UC-EHS-1 Version 1.0
ID
Use case Emergency Help Services
Name
Platform Pega 8.3 Time for completion 8 Hours
Details
Created Pavan Kumar A Last Updated By Pavan Kumar A
By
Date 10-06-2020 Last Revision Date 10-06-2020
Created
Concepts 1) Case Management: Designing case life cycle
covered 2) Data Modelling: Adding fields to a case type
3) Validation: validating case data
4) Information Exchange: Creating data types
5) Information Exchange: Managing data pages and views
6) Case Management: Sending correspondence
7) Business Reports
8) Dynamic UI

Descripti XYZ company wants to build an application that can take request for an Emergency Help and create a
on notification case for the concerned team.
Any individual, who register with this application will have some Emergency buttons on their initial
screen, just by clicking on that buttons, a case gets created and will be routed to the concerned team for
immediate action.
Currently XYZ is dealing with two types of emergencies – Medical and Fire, in future it may extend its
services for other kind of emergencies like floods, hurricanes, etc., Design application for easy future
extensions.
“Emergency Help” is one Line of Business, Application structure should support easy adoption of other
LOBs of XYZ company.

Actors User, Audit Team, Service Providers, Admin, Directors, relationship manager
University Academic Program

Mock up
screens
University Academic Program
University Academic Program
University Academic Program
University Academic Program

Wallet creation
University Academic Program
University Academic Program
University Academic Program

Service Provider Registration:

University Academic Program

Directors Approval

Director1:
University Academic Program

Directors 2:
University Academic Program

ServiceRequest:
University Academic Program
University Academic Program

Routed to service Provider

University Academic Program
University Academic Program

Reports:
1. Total Bonus paid on given date

1. List of Service Providers

2. List of Registered Individuals

University Academic Program

3. Emergency Service executed, group by Service Providers

4. Total Fee collected on given date

Minimum amount to be maintained in wallet based on below fields.

Type Of Minimum
Age Location Service Amount
if <= 30 USA Medical 500$
else if USA Fire 700$
>40 &&
else if <=50 USA Medical 1000$
else if USA Fire 1200$
>50 && <=
else if 80 USA Medical 900$
else if USA Fire 1100$
else if <= 30 AUS Medical 400AUD
else if AUS Fire 500AUD
>40 &&
else if <=50 AUS Medical 300AUD
else if AUS Fire 600AUD
>50 && <=
else if 80 AUS Medical 250AUD
else AUS Fire 350AUD

Trigger Case is instantiated when a user requests for an emergency help

Precondi User is the operator in the Emergency Help services application
tions
Post Service Provider should get acknowledgement once they are signed up in to the application
condition
s
University Academic Program

Normal 1. XYZ Company’s Emergency Help requirement is having two main processes inn their application.
Flow a. Registration
b. Emergency Help – (Medical & Fire)
c. Administration
2. XYZ is having two types of registrations, individuals can register to utilize the emergency services
and Service Provider can register with XYZ to provide paid services to the users of the application
on request.
a. Individual registration
b. Service Provider Registration
3. Individual should provide the required details, then the request will be sent for review, once
approved by admin, Individuals will get credentials via email to login and access to utilize the
services.
4. Registration is of two types trail and membership.
5. Trail is for 30 days, it is free and can utilize only one of the available selected service. Individual
are validated on email and phone, so that the same user cannot utilize trail more than once.
6. Member registration, it is in three different categories- 3 months, 6 months, 12 months, 2 years,
5 years, Life time, these durations can be changed by XYZ management team.
7. Once individual registration is submitted it will go for review and after validation, and user will
be acknowledged via email with credentials.
8. In the email rules and regulations document will be attached. These documents are maintained
by XYZ team
9. Once registered, the user should create a wallet to keep the money, as these are emergency
services, a fund should be available to utilize the service.
10. Minimum fund to be maintained is decided by XYZ Company based on the age of the individual,
Location of the residence and types of services opted.
11. If the fund amount decreases than the certain limit, an email must be sent to the individual.
12. Service providers have to get registered with XYZ to provide emergency services to the user.
13. Service providers will charge for the services they provide.
14. Service provider should give organisation name, director name, date of establishment area of
expertise, office address, contact details, and types of services and charges.
15. The request submitted by service provider will be routed to the XYZ directors, currently three
directors are available in which two of them must approve, and otherwise request will be
considered as rejected.
16. Once approved service provider will be notified via email with credentials to login and rules and
regulations document will be attached in email.
17. When the user logins in emergency buttons will appear on the first screen.
18. Based on the selection of the button a case instance of that type will be created and routed to
the service provider.
19. The service provider should accept the request with in a min. Otherwise next available service
provider will be selected and notified.
20. Once the emergency request raised the request has to be accepted by the service provider by
accept button which will happen in execute request stage.
21. After execute request it will move forward to the fee collection stage, where the invoice will be
generated based on the data provided by the service provider.
22. The invoice which is generated by for the service provider must route to XYZ team and it has to
be approved then the fee will be paid to the service provider.
23. If the individual is above 80yrs then facilitation charges are zero.
24. In fee collection stage bonus has to be provided to the service provider, bonus bill has to be
approved by any one of the XYZ director, bonus amount must be paid by XYZ.
25. Feedback needs to be collected about the service provider where an individual has to fill it.
Alternate <Scenario other than the normal flow that results in a user completing the goal>
Flows
Exceptio 1. Out of three directors available if any one director rejects the service provider request then
ns rejection email has to be sent.
University Academic Program

2. If the service provider didn’t accept the request then the request should be sent to next
available service provider.
3. At the time of registration, the customer must provide answers to few security questions, such
that if a customer forgets password, there will be a security question need to be answered as
given during registration time, which is show in the mock up screens, then the customer should
be type in new password and login into the application.

Includes 1. Create data types for Service Provider, Customer, Emergency Services
Frequenc N/A
y of Use
Special 1. If the service provider misses the request then XYZ will penalize 100$
Require 2. If the service provider attending more than 10 services a week, a bonus of 100$ will be
ments announced.
3. Final generated bill have service provider fee + facilitation charge (by xyz) must be deducted
from the individual’s wallet.
4.

Future 1. A notice will be sent to the service provider if they don’t provide the quality service.
Require 2. A notice can be sent to the individuals if they involve in any anti-social activities
ments
Assumpti N/A
ons
Notes Create the following operators ids for testing the application.
and bruce@xyz(admin), jimgorden@xyz(director), luciusfox@xyz(director), alfred@xyz(director),
Issues marindatate@xyz(relationship manager), selinakayle@xyz(audit member)
Acceptan 1. Make all fields as mandatory fields
ce 2. If the admin rejects the service provider request, the reason should be captured in the
Criteria email and set to the service provider.
(scenario
s for Unit
Testing)