Está en la página 1de 11

Pega’s University Academic Program

Online bidding for resources / Project


Management Office
(Project)
University Academic Program

Copyright 2018
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: UAP_Project1_CampusRecruitment


Date: February 10, 2018

© 2018 Pegasystems Page 2


University Academic Program

Table of Contents

Pega’s University Academic Program ......................................................................................................... 4


Scenario Overview......................................................................................................................................... 5
Actors .............................................................................................................................................................. 5
Process overview ........................................................................................................................................... 5
Detailed Process Requirements .................................................................................................................. 6
Vendor Registration................................................................................................................................ 6
Consumer Registration .......................................................................................................................... 6
Approval .................................................................................................................................................... 6
Project Creation ....................................................................................................................................... 6
Post Project Creation ............................................................................................................................. 7
Assumptions .................................................................................................................................................. 7
Ad Hoc Requirements ................................................................................................................................... 7
UX Requirements .......................................................................................................................................... 8
Vendor Registration................................................................................................................................ 8
Consumer Registration .......................................................................................................................... 8
Project Creation ....................................................................................................................................... 9
Portal Requirements ..................................................................................................................................... 9
Vendors ...................................................................................................................................................... 9
Consumers ................................................................................................................................................ 9
Project Manager ...................................................................................................................................... 9
Project Officer .......................................................................................................................................... 9
Administrator ........................................................................................................................................ 10
Reporting Requirements ........................................................................................................................... 10
Mail .......................................................................................................................................................... 10
Security Requirements .............................................................................................................................. 10
Appendix...................................................................................................................................................... 10
Sample Users /Operators ................................................................................................................... 10
Sample Skills .......................................................................................................................................... 11
Sample WorkGroups ............................................................................................................................ 11

© 2018 Pegasystems Page 3


University Academic Program

Pega’s University Academic Program

Pega has developed university level-curriculum for students seeking degrees in Business
Information Technology, Management Information Systems, Computer Information Systems,
Computer Science and other related degree programs.
The primary classes focus on DPA/BPM (Digital Process Automation/Business Process
Management), Pega’s core technology. Additional classes focus on AI (Artificial Technology) and
RDA (Robotic Desktop Automation). After finishing the program, students can achieve Pega
certification and look for sought-after internships and employment with Pega clients and
partners around the world.

UAP COURSES CERTIFICATIONS


Business Course CPBA – Certified Pega Business Architect
Technical Course I CSA – Certified System Architect
Technical Course II CSSA – Certified Senior System Architect
AI/Decisioning CPDC – Certified Pega Decisioning Consultant
Robotic Desktop CRSA – Certified Robotics System Architect
Automation

The curriculum, software and support are available at no cost to the university. Our Train-the-
Professor program is a combination of online and in-person/remote training and is also offered
at no cost. For more information, please visit www.pega.com/uap or contact us at
uap@pega.com.

© 2018 Pegasystems Page 4


University Academic Program

Scenario Overview

CST is a Project Management Office which can be internal or external to a company — that sets,
maintains and ensures standards for project management across that organization. PMO
ensures best practices, project status and direction — all in one spot.
PMOs manage and allocate resources accurately across projects. It also manages
priorities based on timelines, budgets, resource loads and what-if analysis information and
accordingly provides the right resources at the right time. They also define roles and
responsibilities.

At a high level and with the initial Phase I release, this application will:

 Allow Vendors to register themselves.


 Allow Consumers to register themselves.
 Allow Admin to review the information and approve or reject.
 Allow Consumers to create the Project for which they need resources.
 Allow Vendors to view those details when published by Consumers.
 Allow Vendors to send the proposal to the consumers.
 Allow Consumers to accept or reject the proposal.
 Allow vendors to generate the Invoice.

Actors
 Admin
 Vendor Project Officer (VPO)
 Vendor Project Manager (VPM)
 Consumer Project Officer (CPO)
 Consumer Project Manager (CPM)
 Resource

Process overview
Project Management office will include the following process

 Vendor Registration: Vendor registers with all the necessary information like Company
Name, VPO Name, VPM Name and their Contact Details. Operator ID’s will be created for
both VPO and VPM and sent to their company email ID’s.
 Consumer Registration: Consumer registers with all necessary information like
Company Name, CPO Name, CPM Name and their Contact Details. Operator ID’s will be
created for both CPO and CPM and sent to their company email ID’s.

© 2018 Pegasystems Page 5


University Academic Program

 Approval: Admin reviews the vendors and consumers information and approve or reject
it based on their company rating. In case of rejection a proper reason can be provided.
 Project Creation: Consumer Project officer will create the Project with details such as
Project Name, Domain, Role, Experience, Skills Required, Number of resources needed,
and Duration and then publish the project.
 Post-Project Creation: Vendor Project officer will be able to view the published projects
by different consumers and if there are resources available then he will prepare a
proposal and send it to the VPM for approval.

Detailed Process Requirements

Vendor Registration
 Vendor clicks on “Register” link to provide Company Name, Registration Type, VPO Name,
VPM Name, and their Contact Information.
 Vendor provides the previously executed projects details and maintains resources
information such as number of resources available in each domain, experience, skills, and
previous projects.
 Vendor reviews the completed information they provided and can edit if required.
 Vendor submits the information, which will be forwarded to admin for approval process.

Consumer Registration
 Consumer clicks on “Register” link to provide Company Name, Registration Type, CPO
Name, CPM Name and their Contact Information.
 Consumer reviews the completed information they provided and can edit if required.
 Consumer submits the information, which will be forwarded to admin for approval
process.

Approval
 Admin either approves or rejects the registration based on the information provided and
company rating.
 If admin approves then the vendors or consumers can continue with further process.
 If admin rejects then there is no alternative for that vendor or consumer to register again.

Project Creation
 CPO login into the application with the username and password received and creates a
project with number of resources, experience, skills required and publish the project.
 CPO reviews the proposals sent by multiple vendors and get them reviewed by CPM and
CPO will further negotiate with the vendors.
 CPO can reject the proposal if the resources requirements are not as per the required
criteria.

© 2018 Pegasystems Page 6


University Academic Program

 After the negotiation process, CPM will pick the best proposal and send it to the CPM to
accept the proposal.
 Invoice Generation received will be reviewed by both CPO and CPM and then on boarding
facilities for the new resources will be done.

Post Project Creation


 VPO login into the application with the username and password received.
 VPO will be able to see the published projects by different consumers.
 VPO prepares a proposal for the published projects and sends it to the VPM for the
Approval.
 VPM can approve/reject the proposal. If VPM approves the proposal, it will be sent to the
Consumer through email. If VPM rejects, CPM will prepare a fresh Proposal and send it
once again to the VPM for approval.
 Once the consumer accepts the proposal, invoice generation will be done by VPO and get
it reviewed by VPM and sent to the consumer.
 Resources under vendor will fill up the timesheets for the project they have been
assigned.
 Billing generation is based on the timesheets logged by the resources on hourly basis.

Assumptions
 There is no need of interview for the resources proposed by the vendor.
 Further processing will be carried out based on the skills asked by the consumer, if
vendor proposes resources with those skills otherwise proposal will be rejected.

Ad Hoc Requirements

 This is just a phase I application and there is no need to implement all real world
recruitment application features.
 Use DWA wherever possible for emails. Wherever DWA is not applicable, emails can be
viewed ad attachments to the case.
 Designated portals should be there for each member. Refer to portal requirements for
more details.
 Routing has to be dynamic and follow best practices.
 Case management has to be followed along with proper naming conventions.
 OOTB Reusability is expected. You can follow PDN help to learn already available features
in Pega 7.
 Necessary privileges and roles have to be defined and used for security purposes.

© 2018 Pegasystems Page 7


University Academic Program

 Unauthenticated portal can be given for vendors and consumers for signup/register.
 SLA are expected to be used for escalation and notifications purpose.
 Proper usage of New, Perform, Review, Confirm harness is expected.
 Validations should be handled at UI and server level.
 Error handling should be done with proper messages.
 HTML and inline styles are best to avoid.
 Styling should be accurate and skin rules should be used as per best practices.
 Workgroups and workbaskets are expected to be used whenever necessary.
 Data model should be simple enough to carry out all the required tasks.
 Proper rule information like usage and description is expected.
 Guardrails are expected to be minimal or at least justified for exceptional conditions.
 UI clutter should be minimal with only required information.

UX Requirements
Below are minimum UX requirements that this application needs for flexible and dynamic
process execution.
Note: These are minimum requirements and any additional useful requirements are welcome

Vendor Registration
 Company Name
 Number of Projects Executed
 Number of resources available in each domain

For both VPO and VPM


 Name
 Mobile
 Business Email
 Address

Resources Info
 Resource name
 Domain
 Experience
 Skills
 Previous projects

Consumer Registration
 Company Name

© 2018 Pegasystems Page 8


University Academic Program

For both CPO and CPM


 Name
 Mobile
 Business Email
 Address

Project Creation
 Project Name
 Domain
 Number of Resources Required
 Project Duration

Resources Data
 Experience Required
 Skills Required

Portal Requirements
All Portals should have CST branding and unnecessary details in Perform/Confirm/Review
harness should not be displayed.

Vendors
Home Portal
 Vendors should have access to unauthenticated portal to login or sign up.

Consumers
Home Portal
 Consumers should have access to unauthenticated portal to login or sign up.

Project Manager
Manager Portal
 To review the information and accept or reject the proposals
 To accept the Proposal

Project Officer
Worker Portal
 To create or view projects info
 To prepare or review proposal
 To reject the proposal if requirements are not met

© 2018 Pegasystems Page 9


University Academic Program

Administrator
Developer Portal
 To provide access to each user and create operators/WG/WB etc.

Reporting Requirements
Following are required reports for VPO & VPM

 Projects published by different consumers.


 Available resources

Following are required reports for CPM

 Resources allocated to their project

Mail
 Proposal approval/rejection by VPM, to be sent to consumer through email.

Security Requirements
 Proposal can be accepted only by the Consumer project manager. No other member
should be able to perform the action.
 Vendor Project Manager should have access to all the resources information.

Appendix
Below is some sample data you can use it

Sample Users /Operators


Vendor VPO: VPOName@CST.com
Vendor VPM: VPMName@CST.com
Consumer CPO: CPOName@CST.com
Consumer CPM: CPMName@CST.com
Resource: ResourceName@CST.com
Administrator: Administrator@CST.com

© 2018 Pegasystems Page 10


University Academic Program

Sample Skills

C, C++, JAVA, Oracle

Sample WorkGroups

 VendorWG@CST
 ConsumerWG@CST

© 2018 Pegasystems Page 11