hackathon_id
int64 1.57k
23.4k
| project_link
stringlengths 30
96
| full_desc
stringlengths 1
547k
⌀ | title
stringlengths 1
60
⌀ | brief_desc
stringlengths 1
200
⌀ | team_members
stringlengths 2
870
| prize
stringlengths 2
792
| tags
stringlengths 2
4.47k
| __index_level_0__
int64 0
695
|
|---|---|---|---|---|---|---|---|---|
9,935 | https://devpost.com/software/uci | Inspiration
We realised that creators around the world were among the most affected by the crisis and are struggling to pay their rent, because creativity is often considered as "non-essential" and we wanted to push forward a new alternative for the funding of creativity.
What it does
Artists and creators worldwide can submit a grant application for their projects, which are then reviewed by a community of cultural organisations, called "the custodians" in order to allocate funds under the watch of the backers, the patrons. Patrons, artists and custodians form a resilient ecosystem that is independent from advertising market or retail, making creativity sustainable economically even during a crisis.
How we built it
We leveraged existing open source libraries, Flutter for mobile apps, and Telos Decide, an open source library for EOSIO governance.
Challenges we ran into
Interfacing smart contracts with Flutter because the libraries available online were obsolete and we had to fix bugs and adapt. Governance and smart contract product design. Caching and lazy-loading of profiles on the app.
Accomplishments that we're proud of
We managed to make this happen despite being from different parts of the world and all very busy with our work.
What we learned
How to use EOSIO and develop with the existing tools. How to sign transactions locally and using a wallet..
What's next for UCI
We are already starting to connect with some brands, magazines and getting ready for funding, and we are looking for an advisor to help with the legal aspects, setting up a foundation and making deals with retailers to integrate our stablecoin payment gateway and connect them with our creative communities.
Built With
blockchain
c++
dart
flutter
Try it out
github.com | Universal Creative Income | A DAC built on EOSIO to offer a new resilient infrastructure for the digitalisation and funding of creativity worldwide, through a decentralised governance. | ['Yurii Havrylko', 'Craig Branscom', 'Eugene Velizhenkov', 'Madeleine Parker'] | [] | ['blockchain', 'c++', 'dart', 'flutter'] | 8 |
9,935 | https://devpost.com/software/mroo | Main instructor dashboard
Students list
Enrolling a new student
Curriculum termination
A work contract is assigned to the best student
Visit our
website
mroo
[Em-roo]
is a decentralized micro-university creation platform that allows teachers to build a university according to the direct needs of businesses. mroo connects businesses, teachers and students to bring digital micro-universities to life.
In a world where a crisis causes millions of jobs to be lost, and economies to go down at light-speed, it is time to start building better solutions. At mroo we target education, the foundation of our societies. Our aim is to provide university-level education for everyone. We believe that learning should give you more opportunities and reduce student debts. Universities should prepare sudents for the jobs of the future. We believe that it should not be complicated - get skills, get opportunities and learn with mroo.
Our goal is to prevent certain structural, cultural, civilizational and secular sectors from collapsing, or being on the verge of extinction, due to a lack of imagination to build. We want to help those sectors by building new ways of learning, recruiting, and working using the best technology can offer.
Main Objectives :
Secure and guarantee education actors.
Bring transparence to all parties.
Make education more accessible.
Connect education with the real world & business needs.
Provide a solution suitable for remote work.
Micro-University
In traditional education, students gather in a place to be locked in several independent, unconnected units called classrooms. These classrooms, or compartments for knowledge transmission, are under a central authority body called the university. The university is a centralized institution that manages everything at the same time. It handles administrative tasks and tuition fees payments, chooses who is entitled to receive education, selects and pays teachers, often processes applications for scholarships and is an important decision maker on the curriculum and all this without consulting the real needs of businesses or our society. In this way we blindly train and educate a generation, without really knowing which professions are actually needed by today's and tomorrow's society.
The concept of micro-university is very simple, it is based on a decentralized system where universities directly represent self-managed classes using the blockchain. Micro-universities keep the traditional educational structure with a speciality, a curriculum and a real school program.
Philosophy, Art, History, Economy, Theology, Script writing, Political sciences... but also digital curricula, Sound design, Computing, Engineering, Architecture, Drawing... can all be taught at a micro-university. Micro-universities are without central authority and respond directly to the needs of businesses. These businesses are called sponsors, they have a protective and guarantor role.
A micro-university must necessarily connect 3 actors:
Company ⟷ Instructor ⟷ Student
3 interconnected actors.
Actors :
Company
Instructor
Student
Problem:
Company
: Long and competitive job market, forced to do vague and imprecise targeting.
Instructor
: Dominance of central educational authority.
Student
: Expensive fees, lack of support, no guarantee of employment or internship, debts.
Need :
Company
: Precise targeting of candidates in line with the company's identity and the position to be filled.
Instructor
: Teaching autonomy, flexibility, stable and guaranteed income.
Student
: Savings, support, hiring guarantee, security, apprenticeship training, easy credit agreement.
Answer given:
Company
: Targeting from education, candidates that respond to precise needs.
Instructor
: Different teaching format (3, 6, 9 months or custom), easy access to become a teacher.
Student
: Cheaper education, support, job opportunities, work placement in companies, recognized diploma.
Things to know
Company, Sponsors, Guarantor
Business involvement is crucial in the role of a micro-university and especially on mroo. The company sponsors the micro-university from its inception. The main feature of the sponsorship is the job guarantee offer, which is a secure and reserved job vacancy quota for the students of the micro-university which guarantees them high chances of being recruited as soon as they graduate. The company helps to create, together with the instructors, the education program and strategy for the students, the future employees of the company. This job guarantee offer will be in a contractual form defined by a smart contract on the EOS blockchain. In this way, companies secure and guarantee a micro-university.
Creation of a micro-university.
Requests for creation of a micro-university can only be made with a main instructor. To finalize the request, the micro-university must be sponsored by at least one company. An instructor alone is not enough to create a micro-university and a company alone is not enough either. The speciality and subject of teaching of the micro-university must be correlated with the speciality of the instructor and that of the guaranteed job offer issued by the company.
Sponsor Search
mroo will set up a section dedicated for instructors to find a sponsor company. In this way, micro-universities in the process of applying for sponsorship will be able to search for a sponsor directly on the mroo platform. It may very well be that both the Enterprise party and the Instructor party morally found the micro-university before starting the creation process on mroo, but in both cases, the parties must submit to a contractual agreement.
Curriculum
The courses are between 3 - 9 months. It includes a curriculum morally established by the sponsor and the instructors. They are based on remote learning. Nothing prevents universities from scheduling physical activities outside the mroo platform (library meeting, museum meeting, meeting in a dedicated co-working space, school outing...). Companies will have to carry out remote internships on a carefully programmed schedule, in order to prepare students for remote working and leave non-recruited students with experience in companies in addition to their training, which will have a real value in their diplomas and in the continuation of their career.
Blockchain
The micro-university is managed by one smart-contract and is linked to the smart-contract(s) of the job offer(s) from the business(es). We deploy those smart-contracts on a blockchain because of the properties associated with this technology. Once deployed, smart-contracts cannot be removed or altered, and there is no need for a central authority to certify this, it is an intrinsic feature of the blockchain technology. Additionally we want to keep a record of the skills acquired by students, and we also want to make sure that those certifications can never be hacked or modified after graduation.
Lastly, a blockchain allows us to make actions in a transparent way: the computation of the class ranking cannot be manipulated, and even more important the selection of the student(s) getting the work contract(s) cannot be hacked.
Smart Contract
EOSIO is the platform we use to deploy our smart-contracts. We have to kind of smart-contracts:
one per micro-university that holds all relevant information about the micro-university, namely the students, professors, and links to associated work contracts. It keeps track of students progression and after graduation computes the class ranking and select the student(s) getting the work contract(s).
one (or more) smart-contract representing a real work contract, with all details such as the salary, the duration of the trial-period, everything you would usually find in a classic work contract. The only difference is that the name of the future employee is left blank until graduation. After graduation, the name of the student getting this work contract will be added and the contract will be complete.
What it does
mroo lets you manage your micro-university, you can add fellow professors or specialists to create the right curriculum for your students and the business needs you address. You can enroll your students and certify their skills.
In addition to a diploma, you bring job offers to your students by partnering with businesses that need specific skills.
When the time of graduation comes, the micro-university’s creator is able to close the university and generate the final ranking of students, attributing the work contracts to the top students of the class. All of this automatically and in all transparency.
How we built it
mroo is built using the EOSIO platform for our smart-contracts deployments. To interact with those contracts we use a front-end built with Vue.js and quasar framework.
mroo vs classical universities
Our Choice
We really wanted to respond to the constraints communicated by block.one. And we chose education. We could have chosen to enter the health field because we saw the word "Covid 19" but the health field is a gladiatorial arena. It's an extremely competitive, expensive and legal field that brings together several financial powers and big industries looking for a miracle solution to repair and relaunch the standard economic machine. We have chosen realism. We choose the long term: Education, the pillar of our civilization that has been abandoned by digital technology and and which is for the moment in the hands of an extremely elitist central education. We must educate the world and raise our general knowledge.
Challenges we ran into
The project is the result of a very intense reflection over a period of 2 weeks. We constantly questioned ourselves to find a real solution that meets the demands of Block.one. Before arriving at mroo, in 2 weeks, we had 5 project proposals (including mroo) :
Job search platform for remote work, micro-services platform, smart-contract generation tool for freelance work, environment and health certification
. But every time we studied the market for all these proposals they did not correspond to our real expectations and the constraints required to "build", and it was very frustrating. mroo arrived very late, on May 20, 2020. The difficulty is to have searched and found an idea that really meets the constraints of Block.one. The use of Slack, Google Doc, Miro, Smartsheet and Zoom was very useful to exchange and gather our ideas, as we all worked remotely.
What's next for mroo
We are bringing mroo to the next level and will start making partnerships with companies. We will also continue to release updated versions of mroo.
Next steps :
UI/UX review
diploma issued on blockchain
more collaboration functionalities
listings of all micro-universities
partnerships
Visit our
website
Thank You
Built With
blockchain
c++
eos
eosio
eosjs
figma
quasar
smartcontract
vue.js
Try it out
github.com | mroo | The new face of higher education. | ['Kevin Bertin', 'David Giardi', 'Sarah Mauret'] | [] | ['blockchain', 'c++', 'eos', 'eosio', 'eosjs', 'figma', 'quasar', 'smartcontract', 'vue.js'] | 9 |
9,935 | https://devpost.com/software/distributed-markeplace | Title
Idea behind project
What is dMarketplace
dMarketplace smart contract
Mobile application
Summary
Inspiration
Direct trade between people have always been a driving factor in generating livelihood and supporting local economies. In extremely hard economic times, people rely less on centralized government as the later becomes less reliable and efficient in this role, and start relying more on local community.
Thus we want to establish a distributed Marketplace that will enable people trade with each other in a currency of their choice and build reputation within a marketplace.
What it does
We are basically build E-Bay on EOSIO Blockchain where all Marketplace operations are handled on a smart contract, which let people trade with each other using any cryptocurrency of fiat as payment methods.
The interface for the Marketplace will be on mobile application (both Android and iOS).
How I built it
Developed dMarketplace smart contract.
Deployed and tested on Telos testnet manually.
Documented list of client commands for smart contract for mobile team.
Developed NodeJS endpoint for new account creation on Testnet used in signup.
Deployed Amazon S3 upload endpoint using NodeJS Lambda functions - used for product image upload.
Team worked on native Swift iOS mobile client.
Challenges I ran into
The main challenge as in any e-commerce venture is fraud.
Rather than trying to solve it in centralized manner - we want distributed community to manage risks and fraud using reputation system, reviews, transactions history, disputes and bans for bad actors in a system.
Not enough time to complete project of this size - mainly native mobile application takes more time.
Accomplishments that I'm proud of
Fully implemented e-commerce foundational layer into EOSIO smart contract with seller review and dispute mechanisms.
What I learned
Communication is a key in a team to make project move forward.
Misunderstandings lead to time lost.
What's next for Distributed Marketplace
Continue development till viable MVP is released.
Traction with users and survival in Real World.
Security and fraud prevention.
Original project:
https://devpost.com/software/distributed-marketplace
Presentation slides:
https://docs.google.com/presentation/d/1kJf56jBDjR4Rl2uWRs_YZXYoGqRvtDot3r2JGGj_5Wc/edit?usp=sharing
Built With
c++
javascript
node.js
swift
Try it out
github.com
github.com | Distributed Markeplace | Mobile eBay on EOSIO platform with crypto payments. | ['Eugene Luzgin', 'Jacob Liu'] | [] | ['c++', 'javascript', 'node.js', 'swift'] | 10 |
9,935 | https://devpost.com/software/qure-d3ihje | Inspiration
We love building with EOSIO software, and saw this as a great opportunity to showcase our talent!
What's next for Qure
Qure was built from the ground up for the EOSIO Hackathon, while this is a project we may bring forth in the future, we at Onessus have a lot on our plate and a lot of other great EOSIO based applications that we would like to release first.
Built With
c++
css3
eosio
eosjs
html5
javascript
vuejs
waxjs | Qure | An economic virtual meet-up community, and decentralized donation network. | ['Dante Scott', 'J Scott'] | [] | ['c++', 'css3', 'eosio', 'eosjs', 'html5', 'javascript', 'vuejs', 'waxjs'] | 11 |
9,935 | https://devpost.com/software/smart-care-ap14m0 | Inspiration
As of May 31, 2020, 103,700 Americans have died from Covid-19. 62,000 doctors, nurses and health care providers have been infected and about 300 have died. Around the world, covid-19 has presented a number of challenges from absence of a vaccine to shortages of personal protective equipment (PPE). Healthcare providers are risking their lives to test and save others, but there is a safer method to test patients while protecting healthcare professionals.
What it does
Smart Care leverages EOSIO blockchain technology and smart contracts with facial recognition to automate the process of testing for Covid-19. To start, patients enter basic health screening questions and a computer screen with a webcam watches as they swab themselves. The patient must turn sideways to show a side profile. A good specimen is calculated after the swab has reached 50% of the diameter of the patient's head. To show that a good specimen has been collected the border around the screen changes from red to green. That information is then stored on the blockchain and sent to a doctor or other healthcare professional to notify them that a good specimen is collected at which time healthcare professionals can report the findings of the Covid-19 test.
How I built it
A lot of EOSIO smart contracts, tensorflow, opencv, blockchain.
Challenges I ran into
This is actually my first time using blockchain. I went from knowing close to nothing about blockchain to making my own blockchain with EOSIO. Understanding the concepts of blockchain proved to be the hardest part of the project. A
Accomplishments that I'm proud of
Coming up with and developing an application that could save thousands of lives.
Whats next for Smart Care
I would like for this to also be an app so that patients can pick up swabs from a safe location and swab themselves from their home or car without ever having to enter a medical facility, risking infecting themselves or others.
Built With
blockchain
eosio
opencv
tensorflow
Try it out
github.com | Smart Care | Safest way to test for Covid-19 and Influenza by using blockchain technology and AI to automate the testing process. | [] | [] | ['blockchain', 'eosio', 'opencv', 'tensorflow'] | 12 |
9,935 | https://devpost.com/software/terra-sapiens | Humans from visitors to citizens
non-transferable badges (tokens)
Inspiration: Mind (eosio), Body (humans) and Soul/Spirit
What it does: New blockchain built from ground up from human contributions towards creating a better system that works with Earth, humanity and all species for a better world that are hearts know is possible.
How I built it: The smart contract is a non-transferable token, however the idea is much bigger to help solve local and global challenges.
Challenges I ran into: Presenting a transformative system described in only 3 minutes!!!!
What's next for Terra Sapiens: Awareness, initial human contributions and launch chain.
Built With
citizen
eosio
humans
kyc
seeds
Try it out
github.com
tipit.io
www.joinseeds.com
dho.hypha.earth | Terra Sapiens | Human-first eosio blockchain with SEEDS to deal with local and global issues. | ['Mark Stair'] | [] | ['citizen', 'eosio', 'humans', 'kyc', 'seeds'] | 13 |
9,935 | https://devpost.com/software/mychainomics-pcot2e | Inspiration
One of our co-founders participated in clinical trials in her career, where she saw firsthand the gaps in how enrollment, consent and compensation worked.
In the global context of an emergency situation worldwide with COVID-19, we need thousands of participants quickly who need to feel safe to contribute and their information, know it is kept private and secure, while still being verifiable.
This is an old problem inspiring us in a current crisis: Henrietta Lacks in the 1950s provided one of the most important cell lines in medical research, while never getting paid for her contribution.
Creating a participant focused model - re-balancing power into the hands of participants. Addressing the need to think from a patient/participant perspective.
Looking for a business problem would truly benefit from blockchain.
Need to facilitate more clinical trials, and ensure money flows to small/medium researchers as well as large organizations. Connect dots to needed participants and incentivize them correctly.
What it does
A secure mobile matching system for individuals and researchers to anonymously share data, and reward participants who help find cures including for COVID-19.
Participants can join, get authorized, share data by authorizing data providers.
Participants are strongly identified.
Researchers can incentivize participants.
Researchers (and other data consumers) can register events upon providing relevant data into the system.
Researchers can confirm participation in trials/events by Participants and then the system enables compensation.
When users are paid, the system enables a transaction fee to be captured by the company.
All actions are cryptographically provabable (signed)
Transparent audit trail of transactions using blockchain.
Blockchain provides public proofs such as “this person participated in this study” which is cryptographically signed by participants. Anyone could check the proof and see "this company signed this with their private key"
Machine learning (ML) and artificial intelligence approach is integrated with blockchain technology. Through classification we match participants to trials. The ability for more advanced AI features such as prediction can be added in the future.
How we built it
EOSIO smart contract written in c++.
EOSIO development tools for smart contracts.
Product design interaction mockup created in Adobe XD available for interactive viewing online:
https://xd.adobe.com/view/279e3278-dbae-478b-6f38-2d23618ad6c3-51af/
. Link with a product walkthrough viewable here:
https://www.youtube.com/watch?v=6LGfWHLh6Ww
.
Video editing in Final Cut Pro X.
Unique contract design so each user does not need to have a chain account and we have our own account system in our app design.
The contract uses a flexible sub-account system and internal accounting to reduce reliance on chain accounts. Each account in our system is responsible to connect with onchain so our contract can work with existing authorization implementations.
Each of our primary participant types (user, data producer, data consumer) is stored in a dedicated table. Actions allows sub accounts to authorize all major types of participation in the system.
First class of actors “user” can be registered by system or can register themselves, can specificity who invited them (referral system), can reward referral and share earned percentages on rewards.
The system has a Metadata field for unstructured data to allow expansion over time. The user has structured data in the form of ‘data types’. The system might have hundreds of different data types that users can whitelist for sharing.
The user can also browse events. If they have the right kind of data in the system the event will allow them to apply, when the user applies organizers of the event can review and accept or deny.
Challenges we ran into
When thinking about data structures, it’s not always easy to predict the most efficient way to store data up-front. After some initial problems due to an over-opinionated data structure, we reworked things to keep our relationships between data more flexible. Additionally, using secondary tables to store additional information (instead of trying to fit all data in a row of a single table) proved to be an effective way to organize data.
Accomplishments that we're proud of
Crowdfunding the rewarding of participants in clinical trials.
Connecting gamification actions to specific badges (such as donating giving a social good badge) opens up a whole dimension of interactivity that expands the value.
The sub account system we implemented is not something we have seen implemented in any other contract before. We believe the level of flexibility this affords our contracts is very high and will ease further development of the platform by enabling many different kinds of innovative authorization solutions.
Solving key pain points in the rigid current system for finding participants for clinical trials, which could prove helpful now in finding a cure and key therapies for COVID-19, and in the future for new challenges.
What we learned
Having user reward tokens tied to on-chain entries enables a whole new dimension of gamification that can reach beyond the app itself and into wider markets.
The details of a transaction based business model on a blockchain.
EOSIO blockchain has the correct characteristics for our use case, over other blockchains. Ability to scale effectively and has needed speed which is required for addressing COVID 19 scale use cases.
What's next for MyChainOmics
Formalize the incorporation of the business.
Connect the front end and back-end to finish MVP
Test COVID-19 trials on the platform
Built With
adobe
c++
cryptokylin-testnet
eos
eosio.cdt
node.js
visual-studio
Try it out
github.com | myChainOmics | Secure matching system for individuals and researchers to anonymously share data, allowing researchers to crowdsource fund studies, and reward participants who help find cures starting with COVID-19. | ['John Heeter', 'Vikrant Akavaram', 'Dorian Buitrago', 'Jay Millard', 'Susan Ip-Jewell', 'John Hanacek'] | [] | ['adobe', 'c++', 'cryptokylin-testnet', 'eos', 'eosio.cdt', 'node.js', 'visual-studio'] | 14 |
9,935 | https://devpost.com/software/auream-io | Maximise protection against counterfeits
Auream logo
Inspiration
We were inspired by the recently appeared fake or low quality medical equipment and the negative consequences they could have on the spread of the virus. We have seen the opportunity to utilise blockchain as one of the key drivers of bringing transparency to medical supply chains and the significance of securing thereof. Bringing transparency to medical equipment is not just an option but is an absolute necessity, since people’s lives are at stake.
What it does
We have built an easy-to-use app, which firstly generates unique QR code for the particular item on the manufacturer’s level, links that item to a batch, writes this hash into the Eos blockchain. Once the hospital/end customers receives the item, he/she can easily scan this QR code and verify the entire history of the item’s movement and each important milestone(including GPS stamps).
How I built it
Our teams has worked on various blockchain based solutions in the past and when we have noticed the EOSIO Virtual Hackathon, we have realised that it was the perfect opportunity to turn our idea into reality.
First we have planned the rough idea in lean canvas, questioned possible issues and challenged each others point of view.
This was followed by drafting up the entire services flow, exploring each individual step in terms of design and implementation.
Challenges I ran into
Since we are a decentralised team scheduling of regular meetings has sometimes been a challenge, but we have managed to overcome this. Building a project on multiple interrilated parallel tracks can be a complex but with the right communication tools and attitude it becomes manageable. The use of Slack and Miro have helped a lot to bring all ideas and processes together.
Accomplishments that I'm proud of
We are extremely proud of what we have built. It took us plenty of time and effort to reach this point, but we are very happy with how the product feels and functions.
What I learned
We have learned that harmonising the design and building stages is quite hard and that you need a cohesive vision, which also looks at compatibility 2-3 steps down the line. The Eos blockchain is well suited to build blockchain based solutions, with well documented tools and user friendly environment.
What's next for Auream
We await for the verdict of the jury and would like to develop the project further to the commercial stage. We are also looking for investors and strategic partners for the next steps.
Built With
kafka
node.js
nuxtjs
springboot
springcloud
tailwind
Try it out
auream.io | Auream | securing medical supply chains using QR codes and blockchain | ['Michal Grman', 'Lukáš Figura', 'Michal Geci', 'Patrik Csókás', 'Peter Pongracz'] | [] | ['kafka', 'node.js', 'nuxtjs', 'springboot', 'springcloud', 'tailwind'] | 15 |
9,935 | https://devpost.com/software/crypto_bartender | Inspiration
During COVID-19 times social distancing became a very important part of life. The negative economical impact of the coronavirus period is especially faced by small businesses. The owners and personnel working in cafes, restaurants, shops, hotels, and related industries suffer losses, lose their jobs.
Even after the quarantine, social distancing will remain a practice many people will continue following. Taking to account all the social changes, with the help of EOS blockchain and eosio software, we would like to present a solution - Cryptobartender.
What it does
Cryptobartender is a device, which helps to buy wine (whiskey, water, any type of liquid is possible) by paying with EOS or EOS-based tokens, eliminating the need for personal contact.
Brief History
In 2019 there was a crypto bar Knygarium in the center of Kyiv (Ukraine). Cryptobartender of the first version was installed there which served a homemade wine. Knygarium had its own currency KNYGA token (created on top of EOS blockchain) which was distributed as loyalty rewards and had a stable exchange rate to the national currency. One of the goals of Knygarium was the popularization of cryptocurrencies in general and EOS in particular, so all interested frequent clients had an EOS mobile wallet installed and used the tokens for receiving rewards and paying for drinks, food, etc.
Cryptobartender accepted EOS and KNYGA tokens (as not everyone had used EOS before, using tokens was the easier way). Payment was usually sent via scanning QR-code and `Cryptobartender poured a glass of wine. Moreover, Cryptobartender distributed the profits among bar owners, wine producer, and wine distributor (as EOS transactions worked fast, the distribution happened instantly).
Even though homemade wine served by Cryptobartender costed more than other wine, it was a very popular service of Knygarium visitors.
How we built it
Especially for the EOS Hackathon, Cryptobartender was newly written taking to account all eosio updates, and deployed on Jungle testnet.
The payments are accepted in EOS and EOS-based tokens. We think that business which might use Cryptobartender might want to create their own token so this model will work well, as it will be easy to set up additional token or a number of tokens, as well as prices, percentage of distribution.
As the digital economy grows, this project might help to improve the supply chain and transaction process among all the participants involved.
This chart illustrates how the EOS smartcontract is used to run Cryptobartender with the help of Amazon Web Services.
The heart of Cryptobartender is microprocessor ESP8266 developed by Espressif Systems. C programming language was used to program this microchip.
It’s worth noting that such microchips are very low-cost (less than $1) which might be a strong point for potential mass-production in future.
With the help of MQTT broker, Cryptobartender connects to the Pyhon module, which runs on AWS. Cryptobartender communicates with device manager, which via the Communicator exchanges data with EOS crypto module. The latter communicates via API Endpoint with EOS blockchain (eosio.token smartcontract).
Crytpobartender’s transactions details
The account of Cryptobartender is set up to be wealthysnake (
https://jungle.bloks.io/account/wealthysnake
)
The price of 1 portion of wine is designed to be 0.5639 EOS or 50 JUNGLE tokens.
The process of income distribution is set up in the following way:
40% goes to wine producer (in our case it is account wealthytiger)
40% goes to bar owner (in our case it is account cryptotexty1)
20% goes to wine distributor (in our case it is account destitutecat)
The number of participants and their share in income can be shaped according to the needs. For example, in future wine producer and distributor might be one person, or the bar owners/managers can have several accounts. Also in future we can foresee more advanced payment management options (i.e. it will be possible to automatically convert EOS or EOS-based into another currency, tax management can also be applied, etc.)
The easiest way to send payment is via QR-code with the help of one of the available EOS wallets.
When the payment of the amount 0.5639 EOS is sent to wealthysnake, we see that wealthytiger receives 0.2255 EOS (40% of total amount), cryptotexty1 receives 0.2255 EOS (40% of total amount), and destitutecat receives 0.1127 EOS (20% of total amount).
Cryptobartender sends back 0.0001 EOS to customers with a memo (“Thank you! Have a nice day! :)”). We think that the memo field might become a powerful marketing tool for cafe owners or those who will use Cryptobartender. Also, it will be possible to setup cashback in native tokens of venue.
In case when a bigger amount than 0.5639 EOS is sent, Cryptobartender sends the rest to the customer indicating “Too much money sent. The price is 0.5639 EOS” (Of course the memo text can be changed). And if Cryptobarnder receives payment when it’s turned off - the full amount is returned to the customer.
Challenges we ran into
It was a challenge to use Jungle testnet, as previously we were using EOS mainnet and mobile wallets
Accomplishments that we're proud of
The new version is written in a block way, separated into 3 blocks, which makes scaling easy achievable.
Deployment on AWS instance gives the possibility to control multiple physical devices with an unlimited number of accounts with different permissions and business agreements.
The new version contains github docker-compose settings, which allows to setup and deploy numerous servers in a fast way.
We will be proud if Cryptobartender will be put into mass production and will really help to implement social distancing and fighting COVID-19
What we learned
We learned all the updates of the EOS network and the ways to use eosio.token smart contract
What's next for CryptoBartender
In the new version, there is an idea to rewrite microcontroller part, to allow turning off when there are no customers nearby, and therefore achieve better energy efficiency. Also, it is planned to make it possible to control several devices with 1 microcontroller.
The prototype of Cryptobartender can be used in multiple places: HORECA (hotels, restaurants, cafe) first of all, but also in public places, airports, bus and train stations, and just across the city. Tokenomics can be easily shaped to the benefit or certain conditions (i.e. in some places Cryptobartender can provide water for free, or even antiseptics).
An interesting use-case might be when some individual or company wants to sponsor drinks event, in this case, it’s possible to send the amount to 1 account, and use it for payments.
Cryptobartender provides full transparency, as all the transactions are visible on the blockchain, therefore all the parties involved can track their income in the real-time mode.
Cryptobartender won’t put out the real bartenders from the job, as this job also includes social aspect like communication, it only will improve the process of drinks distribution.
The project is an example of IoT and blockchain combination and it can grow as the whole EOS ecosystem grows.
Built With
amazon-web-services
arduino
c
docker
eosio
esp32
libeospy
mqtt
oled-display
python
Try it out
github.com | CryptoBartender | Cryptobartender helps social distancing, sells drinks in a contactless way, accepts EOS and EOS tokens and instantly distributes income | ['Vyacheslav Korotach', 'Andrii Voloshyn'] | [] | ['amazon-web-services', 'arduino', 'c', 'docker', 'eosio', 'esp32', 'libeospy', 'mqtt', 'oled-display', 'python'] | 16 |
9,935 | https://devpost.com/software/eos-open-registry | landing page
survey that displays data stored in the EOS blockchain and how to retrieve data with curl
preparing the response
when submitted the user receives the link to the blockchain transaction at eos testnet
Inspiration
Source data is an important part of the research. Pandemic COVID19 showed us that we need trustful independent data. We believe and prove that blockchain can solve the problem to trust data.
What it does
Anyone can signup, create surveys, and give or gather responses. Our service shows all the responses given to the survey and how to retrieve that data using EOS Node API as json using cURL.
How we built it
We store surveys and responses in EOS blockchain smart contract tables.
There are 2 tables: form and response. Each survey (form) has its questions set. Smart contract verifies the answers are given to all the questions from the survey.
We have implemented a server-side rendering site (python / django / plain javascript). Background tasks are run by celery service.
To send data to the EOS smart contract, we wrote a separate microservice called eos-gate (nodejs, eosjs) that takes the request (to create, delete survey or submit response), signs, and sends it as a signed transaction to the EOS Node via Nodeos RPC API.
This way anyone can check surveys and responses submitted to the smart contract through the transactions and also the data as it is available in public as smart contract tables. Data is not encrypted.
Challenges we ran into
interaction with blockchain
data validation
resources management with EOS
microservices interaction
covering EOS smart contract with unit tests
Accomplishments that we are proud of
It works
People can use it in day-to-day work and research
We are proud of how the site works and looks (inspired by block.one site)
What We learned
Smart contracts with EOS
eosjs
microservices interaction via API
how to integrate blockchain into the website
how to interact with the blockchain using Python, JavaScript
What's next for EOS-open-registry
Gather more statistics
SDK for R, Python, Julia, etc.
History of my responses (transaction id history to check it out)
Show the last responses in real-time
Realtime data about responses
Support different types of input (checkboxes, radio buttons, dropdowns, etc.)
Split survey questions to the pages (survey wizard)
Built With
c++
celery
circleci
css
django
eos
eosjs
github
html
javascript
postgresql
python
redis
rest
Try it out
eosform.app
github.com
testnet.eos.io | eosform | Simple service for anyone (scientists etc) to create surveys and gather responses stored in blockchain and public to anyone via EOS blockchain | ['Olexandr Shalakhin', 'Artem Maluga'] | [] | ['c++', 'celery', 'circleci', 'css', 'django', 'eos', 'eosjs', 'github', 'html', 'javascript', 'postgresql', 'python', 'redis', 'rest'] | 17 |
9,935 | https://devpost.com/software/pina-2709y4 | Smartwallet
Newsfeed
Business Profile
Service Professional Profile
Promotions
Dashboards
Inspiration
Anthony Bourdain Destroys Yelp
Billion Dollar Bully
Restaurants & Small Business' Troubled Comeback
VICE: David Chang Speaks On The Restaurant Impact From COVID-19
What it does
Supports Small Businesses during the economic downturn and beyond.
Provides sanitary, touch-less hospitality services and payments between small businesses and their customers.
Is an Online Digital Directory of businesses and services that makes Yelp and Yellow Pages look like relics of a distant past.
Provides management tools for small business operators through a simple, intuitive App, aggregating all digital data the business creates and displays it onto easy to manage dashboards.
Allows members to redeem Piña Points for services and products at local businesses.
Allows small businesses to bid on TopSpot advertising on their local Newsfeed and PromoBoard with Piña Points.
Incentivizes and Rewards:
Quality feedback from customers
5-Star service from small businesses
This data will eventually be stored on the businesses permissioned EOSIO blockchain
How I built it
The deep knowledge of 20+ years in the hospitality industry from restaurants to hotels, from luxury to boutique, fine dining to quick service and corporations to mom and pop.
Providing 5-Star service by implementing quality feedback from customers is EVERYTHING to a businesses growth!
5-Star Hospitality and Quality Feedback is extremely valuable, and that value has never been captured until now.
EOS Long Island Meetup was formed to bring likeminded individuals together to create community driven Apps that drive integrity and inclusion, aligning the interests of all parties involved.
Our first meetup was held in September 2018 where Kevin Rose joined us to introduce EOS to our community.
Since then we've been active in the space absorbing and educating ourselves on all we can pertaining to development, regulation and overall progress of EOSIO software.
Timing is everything and NOW is the perfect time to launch our main project Piña, which will help rebuild small businesses in your local community during these difficult times of uncertainty.
Did you know?
Pineapples are International symbols of Hospitality and a symbolic way of saying “you are perfect” when presented to someone.
Gate posts and door frames often have pineapples to signal a Welcome.
Challenges I ran into
Finding local team members and investors that understand the basics of blockchain technology and more specifically EOSIO.
Sacrificing family time to work on my dream project.
Funding.
Accomplishments that I'm proud of
Creating the first EOSIO Hospitality & Service Industry dApp.
Networking and building a small team of professionals and advisors looking to make the world a better place.
What I learned
Blockchain ain't easy, but it sure is FUN!
What's next for Piña
Continue to build and implement blockchain technology into the back-end of the App.
Find team members passionate about the vision of Piña.
Onboard small business partners.
Advertise with social media influencers interested in the project.
Read The White Paper!
"Well-written, thoughtful, and not painful to read, unlike many white papers."
-- Larry Sanger, Ex-Founder Wikipedia
Built With
blockchain
hospitality
love | Piña | Modern digital directory of local businesses and services. | ['Christopher Abate', 'Rene Spanier', 'Taner Seytgaziyev'] | [] | ['blockchain', 'hospitality', 'love'] | 18 |
9,935 | https://devpost.com/software/stimulus-integrity | logo2
logo1
Integrity within Stimulus Aid
In the midst of this pandemic, Congress and the United States government have already disbursed $2 trillion, an act signed into law as the Coronavirus Aid, Relief and Economic Security (CARES) Act. The bill is aimed towards providing much needed, urgent relief to Americans and organizations negatively affected by the Covid-19 pandemic. Shortly after the bill was passed, it has become apparent how much of a logistical nightmare it has been to issue this aid, with numerous headlines bringing to light the systemic failings this bill has surfaced - not reaching many that it was intended for in the first place. Some of these headlines include the following:
The Coronavirus Stimulus Package Is a Mess
Trump says he won’t comply with key transparency measures in the coronavirus stimulus bill
FBI issues warning about COVID-19 stimulus-package scams
IRS' antiquated technology could delay delivery of $1,200 coronavirus stimulus checks, experts warn
Stimulus check problems: Recently dead people getting checks, some live ones aren’t
Across America, a broken unemployment system is locking people out
A timeline of IRS stimulus payment glitches
The handling and distribution of these stimulus checks are in dire need of enhanced integrity and auditability, something that is very difficult to do without Blockchain at this sort of scale, to ensure that the funds reach the intended recipient safely and securely. Furthermore, the high-performance capabilities of EOSIO specifically are best suited for this particular use case, as the volume of checks to be sent in such a short timeframe will require the increased speed and utility that EOSIO provides over other blockchain protocols.
We have built a web portal as a demonstration of how integrity can be imbued into the disbursement of these stimulus aid packages using Blockchain technology.
To summarize:
A private EOSIO blockchain can be spun up by the IRS (or the controlling authority in charge of disbursing the funds), to which potential recipients can go to the portal and register an account on the blockchain.
This registration may include a KYC/AML process to ensure that each individual/organization controls a single, unique account.
Once potential recipients are registered and verified, they may sign in to fill out a survey to determine how much aid they are eligible to receive.
The execution of this survey process is implemented within a smart contract. This way, requests for aid can be handled quickly, affordably, and efficiently, and an auditable log is recorded on the blockchain of each recipient’s submission and how much they are owed.
Since this is built with EOSIO, it is prepared for the large influx of people and organizations seeking aid and unemployment insurance, unlike many of our current systems that struggled after a large spike of stimulus requests and unemployment claims. It is also much easier and cheaper to audit for the IRS since auditability and transparency of the records are baked into the EOSIO blockchain itself. All in all, using EOSIO makes sense here as it would allow us to disburse funds adaptably at scale with lightning speed while remaining safer and far more secure than any other system available to us today.
Note: this demo was modeled after the New York State Department of Labor Benefits Claims process
We hope this demonstration can shed light on a better way to distribute aid quickly, affordably, and verifiably to those in need during times like these. Many are still waiting to receive long-promised aid as they struggle to pay the bills. Some are told they will receive payments automatically and others are left confused when the amount they receive is not the same as the amount they were promised; either way, they have no way of verifying when and how these payments will arrive. And speaking to a real human on the other side is almost impossible when all else fails, with the IRS telling recipients NOT to call.
It does not have to be this way.
Built With
blockchain
c++
css
eosio
html
javascript
react
react-router
redux
Try it out
github.com | stimulus-integrity | Using Blockchain to enhance integrity within stimulus relief | ['Taner Seytgaziyev', 'Christopher Abate', 'Rene Spanier'] | [] | ['blockchain', 'c++', 'css', 'eosio', 'html', 'javascript', 'react', 'react-router', 'redux'] | 19 |
9,935 | https://devpost.com/software/gift-card | Gift Card Dapp For Businesses
Merchant issues Gift Card points and transfers them to the user whenever user purchases Gift Card for later use. Later whenever user wants to buy something, then they can make the purchase using Gift Card points.
Inspiration
During the coronavirus pandemic and lockdown, most of the businesses across the world are affected. Most of their revenue streams are affected and they may be forced to shutdown if they do not find any other revenue source. Hence I decided to work on Gift Card Dapp for Businesses which allows users to support businesses.
Why Gift Cards?
During the coronavirus pandemic, gift cards are a lifeline for small businesses.
Allows people a way to support businesses.
Businesses can generate revenue when their existing revenue streams are reduced or interrupted.
People can redeem their gift card in full or in part, which can encourage return visits.
People can buy a gift card for someone else or use it themselves.
Businesses can start online orders powered by gift card payments.
Why blockchain?
Blockchain allows to track the issuance and the transfer of Gift Card points. It also ensures transparency and accountability. It also provides a seamless experience to the businesses and users.
Setup and Instructions
https://github.com/viraja1/gift_card#setup
Built With
c++
eos
gitpod
react
Try it out
github.com | Gift Card | Gift Card Dapp For Businesses | ['Viraj Anchan'] | [] | ['c++', 'eos', 'gitpod', 'react'] | 20 |
9,935 | https://devpost.com/software/certificates | Inspiration
Kyros Certificates are a culmination of projects which Cryptolions has worked on for years, including Simple Assets, and the Jungle Testnet. We want to reach beyond the blockchain community and provide solutions to everyday organizations. Many of the use cases we have in mind can be precisely applied to problems revealed by the Covid-19 epidemic and the quarantine. (See our video demo for examples.)
Ultimately, we want to change the word in three ways:
1. Better Credentials
We want drivers' licenses which are harder to counterfeit, diplomas which are easier to verify, and licenses which are faster to issue.
2. Provide Useful Tools
Small businesses should be able to easily issue coupons, educators and trainers of any sort should be able to easily provide official diplomas and certificates.
3. Democratize Authority
We want credential entrepreneurs to be able to officially issue their certificates / diplomas / stamps of approval / licenses / etc, and then compete in the marketplace of ideas and reputation to make their certificates matter.
What it does
The Kyros Certificate Hub allows anyone with an EOS account to
register
themselves as some sort of credential authority.
Anyone registered, can then issue any type of certificate (diplomas / licenses / stamps of approval / vouchers / coupons / etc).
Receivers of credentials can print, share, scan (via QR code), and manage them. While issuers can update the parts of the certificate they designated as "mutable".
3 Minute Demo:
https://www.youtube.com/watch?v=TwVbfJNvvGA
Full Demo:
https://www.youtube.com/watch?v=gcC0fBoGoNs
How we built it
Design Principles:
simple
compatible / easy to integrate
unlock user's imagination (by imposing no unnecessary structure)
The Kyros Certificate Hub prototype runs on the Jungle Testnet. It was built with Html and Javascript, and uses the Simple Assets standard for digital assets.
Certificates are non-transferable NFTs, also called NTTs (non-transferable tokens). One advantage of using Simple Assets, aside from access to a lot of packaged functionality, is that a lot of EOSIO infrastructure (bloks.io, wallets) already supports, or is preparing to support Simple Assets. So for example, users would be able to see their certificates in bloks.io.
Challenges we ran into
We are providing an abstract tool which can be used for a wide variety of use cases from very formal ones, like driver's licenses and university degrees, to casual ones, like coupons for a small business, or certificates issued by a local yoga instructor.
We either need need a careful design which communicates to these disparate audiences, or we need to make different portals to the smart contract for use by different types of users. Hopefully, some user test in the near future will provide clarity.
Also, we tried to get YubiKeys and WebAuthn working, but we didn't quite get there.
Accomplishments that we're proud of
We think it's a very cool tool. Simple and powerful.
What we learned
I think the most of the learning is still ahead of us. It'll start when we expose the product to initial users.
But so far, we
think
we've learned that a lot can be accomplished with a simple and flexible design.
What's next for Kyros Certificates HUB
Better Documentation
Seeking feedback from to initial users
Design review
Template functionality for easier issuance of large numbers of certificates
Possible .csv import functionality, also for easy issuance of large quantities
More detailed certificate management functionality (tracking and updating)
Community management
Built With
eosio
html
javascript
simpleassets
Try it out
certs.cryptolions.io | Kyros Certificates Hub | Democratize authority with easy, verifiable, blockchain-based certificates. | ['Roman Skaskiw', 'Bohdan Kossak'] | [] | ['eosio', 'html', 'javascript', 'simpleassets'] | 21 |
9,935 | https://devpost.com/software/utudy | Search classes
See class details
Select one or more days to reserve.
All classes organized in one calendar.
Start classes
One-on-one remote training, teaching, learning
Share screen, split screen during class.
Certificate of accomplishments recorded on blockchain
One of the most basic traits of a human being is their ability to pass along knowledge. The Utudy team has developed a platform where anyone can now participate in the passing of knowledge with a one-on-one live training session to anyone from anyone about any subject. All of this can be done remotely and is recorded on blockchain with Utudy.
Through the Utudy platform, we can unlock the different learning and teaching styles of individuals by giving the world other options aside from pricey institutions and long-term curriculums, thereby liberating students and instructors. Now thanks to the Utudy platform and blockchain we can evolve learning into live one-on-one remote training and record our accomplishments on a blockchain for future validations.
The impact of social distancing in certain industries was a concern that the Utudy team wanted to tackle. We were looking to help industries such as: tutoring, fitness training and coaching, music teachers, inspiring gurus, homemakers, cooks, sports coaching, tour guides, mechanics, gamer, art instructors, and anyone who shared their time paid or unpaid to those who are willing to learn.
Inspiration
Utudy was inspired by the need for continuous learning, skill sharing and community growth. Utudy aimed to build a community-style platform that would bring some of the services that were interrupted during Covid-19 social distancing and stay at home orders. Of course, we did not want to build something that would only be used during pandemics. We set out to build a forward-thinking approach to e-learning and e-teaching.
Many industries were greatly affected by the pandemic but our freelance teachers, tutors, instructors, trainers, coaches, and others that relied on one-on-one social interaction to deliver their services as their primary source of income were heavily affected. We believe this can be prevented in the future with the Utudy platform.
Another inspiration was being able to cater e-learning to different learning styles. Today, we are seeing an influx of individuals with so many different learning styles that it has become difficult to place everyone into the same “boxed” learning. Utudy, we believe that everyone should have the opportunity to engage with instructors in a small group setting or one-on-one, where they can tailor their learning.
Traditional institutionalized schooling is not for everyone. Videos online that are catered to large audiences also do not meet the needs of every student.
With the Utudy peer-to-peer educational community anyone who wants to be a teacher can conduct a one-on-one live class; anyone who wants to be a student can learn from people with experience from anywhere. This creates a better learning environment and a better grasp of knowledge for everyone.
What it does
Utudy is a platform where people can connect to share their skills, knowledge, and experience as a freelance instructor. Utudy is beyond the simple video learning. It is done live in a one-on-one setting or in a small group. Where learning can truly be catered to individuals.
Utudy allows for any user on their platform to register as an instructor and post a class of their choosing as a paid or donation-based service. Utudy allows the instructor to post a schedule of their classes and have their student reserve the time and pay for the class all in one location.
Each class is given their own video session where instructors can conduct their class over video chats, with special tools and features all catered to control and optimize the classroom environment, emphasizing the focus on what the instructor wants the student to focus on.
How we built it
First, the idea struck us like lightning!
Many of our friends are freelancers and because of Covid-19 they were all out of work.
We were looking for a way to help our community.
We started by talking to people who were working as freelancers as rideshare drivers, delivery drivers, or entertainment industry workers. There were some similarities in their descriptions of their services and we added those as the main feature of the platform. Here are the items:
Being able to see their clients
Remove distractions and allow them to focus
Ability to share information
Ability to take payment
Publish an open and closed schedule
And most importantly for all the people we talked to, they wanted to give people a good dedicated experience.
Second, we sought out to build something sustainable beyond Covid-19 social distancing and stay at home orders.
This is when we added the calendar feature, the ability to post a public profile page and the ability to share their services through multiple social media channels that freelancers (Gig workers) could use Utudy as a new source of income.
Third, we wanted to make it user friendly.
You will see Utudy has an easy to use system for setting up classes and booking a reservation with a Utudy Instructor.
Finally, blockchain elevates learning to the next level.
Using blockchain and smart contracts gave us the ability to store the number of hours spent in a class in a trusted place, where it can be publicly accessed and verified.
Challenges we ran into
We had to decide how many students would be in a live class at once. We came to the conclusion that video is just not enough for some people and the many-to-many approach of e-learning is not for everyone. We became convinced that our platform should cater to the individual student and avoid a large classroom where we have 1 teacher for 30+ people. We decided to go with the one-on-one or small class approach allowing no more than 7 students currently to a group class.
Another challenge we faced was finding the number of instructors needed to teach everyone anything one-on-one. We decided the best way to get more instructors was to give everyone the opportunity to be an instructor themselves and get compensated for their time.
Now that we wanted to appeal to a larger audience of Gig Workers our next challenge was to create an interface that was easy to use and understand for adding classes and conducting the service.
We also felt it would be important to be able to store and verify the hours either being taught as an instructor or being learned as a student. This leaves the future of Utudy open to so many different variations of learning and completing courses in the future.
Accomplishments that we are proud of
We are proud of building a platform that can help people in so many ways including:
• Ability to connect people even when they cannot be connected or feel disconnected
• Give teachers, coaches, instructors and tutors a way to earn more for their skills
• Developing a way for individuals to learn anything of their choosing in an environment that is conducive to them and at a pace the student and instructor can agree on together
• Giving students a way to learn the things that interest them in the manner in which they learn best
We are proud of the way our team brought their ideas and experiences together to build a platform that can help so many people today and beyond.
What we learned
We learned that there is a huge need for people to feel connected, even when they are forced to stay away. People connect in so many ways that are not always obvious. It was amazing to learn how simply not allowing people to meet had an incredible impact on a huge freelance industry, as well as individuals needing that connection.
What's next for Utudy
We want to share this platform with the public and start to promote the platform to those who want to be freelance instructors. We want to further advance the technology by providing a mobile application and expand on the instructor tools to be able to store class notes. We hope to extend the services to include closed communities used by education institutions for tutoring services, and health care for one-on-one in-person patient treatment.
Built With
amazon-web-services
angular.js
eos.js
eosio.cdt
ionic
moment.js
mongodb
node.js
Try it out
howtoutudy.s3-us-west-1.amazonaws.com
utudy.com
gitlab.com
gitlab.com | Utudy | We have built the next step of learning evolution. Connecting students and instructors one-on-one through remote live training. Certifiable hours stored on blockchain. Everything else is just a video. | ['John Bardis'] | [] | ['amazon-web-services', 'angular.js', 'eos.js', 'eosio.cdt', 'ionic', 'moment.js', 'mongodb', 'node.js'] | 22 |
9,935 | https://devpost.com/software/jin-network-q6uln9 | smart contract relational graph
Deposit EOS and Mint JIN.
Swap token.
Add liquidity into market.
DAO status.
Inspiration
The first block of bitcoin blockchain we can see a message:
"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
The 629,999 block of bitcoin blockchain, we can see a message:
"NYTimes 09/Apr/2020 With $2.3T Injection, Fed's Plan Far Exceeds 2008 Rescue"
The virus has caused bank to print money indiscriminately.
The mission of cryptocurrencies has never been so clearer like today.
People need an extra option to protect their assets if traditional banks are not trusted.
JIN Netwokr's mission is provide a new way to save people's money and life.
We are building a decentralized bank and a free market for crypto asset trading.
Let's create an open finance network and free to use for anyone in the world.
Whether EOS is suitable for DeFi or not, We hope we are not alone.
What it does
In this project, we are building 3 things.
First one is a Bank, this is a DAI like protocol, can deposit EOS to issue a currency named JIN.
The different between DAI and JIN，
The deposit asset is 100% safety. System never clear user's deposit, even prices fell like March 12～13.
Can enjoy the staking reward. And not need to pay loan interest.
User pay 0.3% mint fee to the system. Mint fee will be share to the DAO member equality. This is a seigniorage in blockchain currency system.
JIN-bank is building for Holders, user never lost their deposit.
The currency mint action take a crypto asset as an anchor and never drop it. It's the shadow of crypto asset. Stay independent of the USD.
Second is a Dex, this is a Uniswap like protocol, allow user to create token market, and trade token, empowers developers, liquidity providers and traders to participate in a financial marketplace that is open and accessible to all.
It enables anyone to create new markets, provide liquidity, and build financial applications that could not have existed before.
Third，we save the cumulative price in the JIN-swap contract. So that we can create a decentralized price Oracle contract.
The price Oracle contract serve time-weighted average prices (TWAPs) .
Click the link for more details:
https://bloks.io/account/jinoraclesv2?loadContract=true&tab=Tables&table=avgprices&account=jinoraclesv2&scope=1&limit=100
Those 3 smart contarct work together like this :
How I built it
Build by eosio smart contract.
And front-end build by vue framework.
Challenges I ran into
Designing and Implementing the solution.
Than test all use case, act as the security auditor to test all smart contract action.
Accomplishments that I'm proud of
Finally, we success launch this project on Mainnet, It's not just a demo, it's a betterDAI and Uniswap on EOS.
It's a good beginning of EOS DeFi ecosystem.
What I learned
I think more deeply about the global economy.
and learned to implement ideas with smart contracts.
What's next for JIN Network
JIN-bank is a protocol that describe a new way to issue currency.
We have implemented a EOS version in this hackathon.
And it can be implemented on other blockchain too.
Just like USDT can issue on many blockchain, JIN also can issue to other blockchain.
Our JIN-swap，can be the first fully decentralized AMM protocol on EOS. User can craete any market on JIN-swap, earn trade fees by providing liquidity.
The next step of JIN Network is make it become a real useful protocol. More user, more aseets locked, more blockchain support.
But before JIN Network can realy launch.
We have the following important things to improve:
Smart contract security audit
Finished whitepaper
Developer docs
Responsive, user friendly trading interface
Whether EOS is suitable for DeFi or not, We hope we are not alone.
Built With
c++
node.js
Try it out
jin-network.hodls.cn
jin-network.hodls.cn
github.com | JIN Network | We try to create a transparent, censorship-resistant financial infrastructure for EOS. Inlucde bank, exchange and price oracle. | ['Joe Gan', 'xhb xhb', 'Yang Yang'] | [] | ['c++', 'node.js'] | 23 |
9,935 | https://devpost.com/software/myfacemaskapp | Prototype model 1 "Dany" pink opaque
Prototype model 1 "Dany" white opaque
AiRFace.it (App)
A new customizable, economic and ecological mask tailored to you
Millions of disposable masks are thrown out every day, which in addition to having a significant environmental impact on nature also have a high monetary expenditure.
To meet all these needs, the
AiRFace.it App
team has developed a project that allows the customization of the mask or the creation of transparent masks that can adapt to the features and therefore customizable by scanning the face in 3D.
This is
AiRFace.it App
, a mobile application that can be downloaded free on IOS and Android devices.
The scanning process is quick and easy: it happens through the use of the mobile phone camera.
In addition, the material used in the production of the masks, biodegradable and hypoallergenic allows a repeated use, being able to sterilize the washing at high temperatures .
The mask is therefore ergonomic and environmentally friendly, because you just need to change the filters.
The 3D model can also be printed from the comfort of the house without leaving. The advantage is that, being custom-built, the signs released by normal masks after hours of use will be reduced.
Considering the difficult and delicate situation we are experiencing,
AiRFace.it App
would ensure protection and prevention with zero impact on the environment and would meet individual needs.
It would be an optimal solution, without going out to buy it if you already have a 3D printer or otherwise we print and deliver directly to your home! The App is free as well as the availability of the various basic 3D models.
Ergonomic
My face mask with its 3D scanning process, allows you to create ergonomic masks suitable for every feature of your face. This custom adaptation will allow you to reduce the marks released by normal masks after hours of use.
3d Printer
The realization of the 3D masks allows anyone to create them independently.
In fact, a 3D printer and a mobile phone are enough to quickly create personalized templates based on the desired quantity.
Ecological
The material of these masks is absolutely ecological, a very important feature if you consider high consumption
daily, especially in
some sectors.
In fact, these masks can
be reused several times later
washing at high temperatures which allows sterilization.
Trasparent
One of the main features of AiRFace.it is transparency.
The idea of making these masks with a transparent material was born mainly from the awareness of the importance of lip reading for deaf people.
Privacy
For us your privacy comes first, that's why AiRFace.it complies with all Gdpr (
https://gdpr.eu
) regulations and no personal data will be transmitted.
The problem solved by the project
With AiRFace.it App we want to find the solution to the problem of the availability of personal protection devices for everyone, in fact thanks to this app anyone can print his mask, following our guidelines for the use of safe and biodegradable materials, with their own 3D printer,only if you are certificated member of our network to ensure the quality and safety of the mask produced according to all applicable regulations, so that you have a mask for you and your family that can last for all this complicated period that we are living.
The solution you bring to the table
AiRFace.it is installable for free on all iOS and Android devices that have compatibility requirements and in a simple automated way and can create your own 3D mask and send it directly to the 3d printer certificated
The impact of the solution on the crisis
The idea behind this project is to create a safe, cost-effective product that respects nature for us and future generations
The needs to continue the project
This project needs funds in order to create the best mask with the best materials and for this a significant investment in research and development in addition to wanting to make and print masks to those who do not have the opportunity to have their own 3D printer
The value of your post-crisis solutions
We believe a lot in this project because it is a valuable help to anyone who does not have the opportunity to always have a disposable mask and this mask can be reused even after this crisis (hopefully it ends as soon as possible) in any sector that needs personal protection devices
The AiR net blockchain
We are creating a network of certified makers to be able to print masks for doctors and nurses for free to thank them for their valuable help.
We are working with other startups to create a network of certified makers using the Ethereum blockchain to create smart contracts in order to be able to transparently verify the entire network.
We are creating a decentralized system that is based on blockchain eos to ensure the total transparency of certification of the materials used to print the masks.
Currently our team also collaborates in the creation of protective equipment for doctors and nurses to thank them for their difficult work.
Built With
blockchain
c#
html5
java
javascript
kotlin
objective-c
python
swift
Try it out
airface.it
bitbucket.org | AiRFace.it App | A new customizable and ecological mask tailored for you | ['Massimiliano Pizzola', 'Daniela Tabascio'] | [] | ['blockchain', 'c#', 'html5', 'java', 'javascript', 'kotlin', 'objective-c', 'python', 'swift'] | 24 |
9,935 | https://devpost.com/software/mutualdao | Mutual Aid Trade
Mutual Aid Program
Mutual Aid Detail
Inspiration
The worsening of health risk, together with increasing medical cost, makes mutual aid a service in great demand by everybody in the world.
The operating and trust costs of traditional insurance are still relatively high, the capital management has a centralized risk, and it is unable to provide more subdivided mutual aid needs.
Combine the traditional mutual insurance model with blockchain technology, we think smart contract based mutual aid can make change in this space.
What it does
It is the global mutual aid smart contract on the blockchain. It combines the traditional mutual insurance model with blockchain smart contract + DAO which provide a low operation cost and guarantee of compensation for risks.
How I built it
We built the system on EOSIO and EOS smart contract. The frontend is built by VueJS.
Challenges I ran into
Blockchain-based mutual aid system is limited by the transaction cost of the public chain.
It also need to effectively reduce the operating cost and provide attractive incentives for members to acquire new users and to be involved in community governance.
Accomplishments that I'm proud of
The demo site:
http://mutualdao.org
The smart contract code is open source in the repo below
https://github.com/MediShares/mds-mutual-aid-dao-eos
EOSIO can solve the transaction cost of blockchain-based mutual aid system. It will effectively reduce the operating cost and the smart contract.
We also built the invitation system in the smart contract which will provide tokenized incentives for members to acquire new users and to be involved in community governance.
Any one can leverage the code to create a new mutual aid smart contract.
What I learned
Coding EOS Smart Contract.
Coding dApp frontend.
Design the DAO model for mutual aid governance.
What's next for MutualDAO
With the improvement of data on the chain, Oracle could be used in mutual aid review protocol as a data dimension in the future, providing more accurate analysis and improving system efficiency.
The system is also suitable for all non-profit organizations as the token donation model and will be an important direction of the smart contract + DAO model.
We believe that the blockchain will bring more inclusive insurance products to the world.
Built With
eos-smartcontract
html
javascript
Try it out
mutualdao.org | MediShares MutualDAO | Mutual Aid SmartContract on EOSIO. Mutual Insurance on the Blockchain | ['Eric Yu'] | [] | ['eos-smartcontract', 'html', 'javascript'] | 25 |
9,935 | https://devpost.com/software/trendie-q71gmk | Some have said that art is what makes us human. The emphasis in the recent past has been on economic growth and financial prosperity, yet, our planet is aching. Art is created from nothing and inspires future progress. We can create, share, and grow with art. With Trendie we intend to:
create an economy based on art
empower people to contribute by providing learning materials
help communities get toghether and exhibit art
This project could be huge. An economy for an artist is not just creating, provenance, and selling work. We intend to sell digital rights, create virtual galleries, have community based galleries, connect local artists, provide teaching resourses to buy and sell, curate trend boards, and so much more.
The application was built using React, IPFS, Bootstrap css, Google maps, and EOS Studio. The initial app was built using Svelte, but we ran into problems with certain npm modules so needed to switch to using React. IPFS needed some CORS settings in order to upload files too.
Another challenge was learning a new blockchain technology. EOS however is very developer friendly. Compared to other blockchains, to get a basic contract running did not take too long. As technology moves very fast some of the learning resources we used were not relevant, so some time was wasted there. C++ is a new language so that was a learning curve. The EOS platform itself is super flexible and performant. We also wanted to create our own token, and use that for the buying and selling of digital rights. Also to use as gamification regarding to teaching and learning. We worked on a branch integrating tokens but ran out of time. This is something we will integrate next.
My team has done an amazing job building and implementing what was necessary. I have learned that learning new technology can advance any project, the next step for Trendie is to Promote, Market and deliver on it's potential.
Built With
eos
google-maps
ipfs
react
ui
wrapstrap
Try it out
trendie.now.sh | Trendie | Local art on a global blockchain scale | ['Mark Robson', 'Colin Bowen', 'Lorraine Duignan'] | [] | ['eos', 'google-maps', 'ipfs', 'react', 'ui', 'wrapstrap'] | 26 |
9,937 | https://devpost.com/software/v-for-volunteer | Volunteering Vacancies (or Missions) Volunteers can sign up for
Volunteering Vacancies (or Missions) Volunteers can sign up for
View of Volunteering Opportunities comprised of 1 or more Vacancies
Reports Dashboard with qualitative and quantitative data
Spaces created by the Volunteering Opportunity and pined to the case
Volunteer Profile to view Personal Details, Current and Past missions and skill set matrix
Kudos Store to exchange Kudos points with some cool prizes
Content Overview
Inspiration
What it does
How I built it
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for V for Volunteer
Getting Started
Research
Reach out
Final food for thought...
Acknowledgements
Inspiration
I wanted to create a solution that solves a business problem in a creative and different way. I remembered a presentation I attended a couple of years ago in the Pega Customer Engagement Summit in London and specifically a reference that said customer satisfaction is linked to employee engagement.
This inspired me to start unravelling the direct and indirect elements that affect both customer satisfaction and employee engagement which led me to several articles and research papers around the subject of volunteering and its benefits on employee engagement, productivity and businesses that have volunteering embedded in their ethos and culture.
Research Paper from Accenture
That made me realise how much of a business problem missing out on volunteering opportunities is - or not having a structured way to for employees to volunteer and gain skills. Volunteering has been proven to be such an effective way to increase employee engagement, increase soft skills and even technical skills that it's practically an up skilling opportunity for you.
Besides the direct benefits volunteering can have to the individuals, businesses gain lots from encouraging employees to partake in volunteering opportunities. Not just the fact that by raising your employee engagement you’re going to increase your customer satisfaction but also gain brand awareness and most importantly build a stronger community where your business may be operating. Strong businesses are built in strong communities.
But sometimes it's hard to fully understand benefits that volunteering could give to you as an individual, your business and your local community.
Research Infographic from Deloitte
Research Infographic from Deloitte
Reading all these research papers, stories and infographics and especially the last two references from the Survey conducted by Deloitte. I realised, even though I would love to get involved in volunteering I barely do. So, I started thinking of ways to solve this problem from an individual, business and community perspective. That’s what inspired me to create “V for Volunteer”.
What it does
The solution sources volunteering opportunities connects them with your employees/potential volunteers and helps them grow their skills in a structured way and rewards them.
The main functionality of the platform and where it has an edge compared to other solutions is the ability to create and join in volunteering opportunities. Volunteering needs to be structured but not rigid. This solution allows anyone in your organisation to post a new volunteering opportunity for approval and to find colleagues within your organisation eager to take a new challenge and grow their skills.
Post a New Volunteering Opportunity
Anyone in your organisation can use the application to create a new volunteering opportunity. In the future, volunteering opportunities will also be able to be created by partnered charities, foundations and volunteering organisations by either sending an email to a shared mailbox and using Email IVA to create a new opportunity or you will be able to choose to embed the DX API or Mashup Web to your company’s website.
When a new opportunity is created, it gets routed for approval by one of your organisations appointed Volunteering Coordinators and once that’s approved the application automatically creates as many Volunteering Vacancies as needed and posts them on the Volunteering Board.
Auto Pega Space Creation
The only way of creating a Pega Space currently is by going to the Space tab. End users may not realise the benefits of using Spaces or may want to create a Space for a particular case… luckily the application takes care of that by suggesting to the end user if they would like to create a Pega Space automatically for the Volunteering Opportunity and add a reference of it to the case so that Volunteering Vacancies can have a direct link where Volunteers can collaborate, exchange information and so on.
Pega Pulse Communicate
The application posts messages automatically to Pulse when a Volunteering Challenge has been completed. Volunteers can also use the Pulse chat in the newly created Pega Space to communicate within their Volunteering group.
Search for Volunteering Vacancy
You can use the search functionality in the Volunteering Board to find a vacancy for you to volunteer for.
Using the Cosmos UI and DX API to show each Volunteering Vacancy as a card, users can get all the information they need to get them interested in getting involved! And in addition to that, a quick link to the associated Space (if it has been created as part of the Volunteering Opportunity)
Ensure organisational compliance
The application ensures organisational compliance by capturing if the Vacancy requires managerial approval and automatically making the decision if it needs to get approval by the volunteers manager prior to them commencing on their new mission.
Volunteer Reflection
Volunteers can use either the WebApp, mobile app or the chat bot to log their reflection. Keeping a journal/reflecting in what you have done and doing is an important part of the growth and skill set enhancement of the individual. The application provides a structured but flexible way to reflect on your experience, to plan and get the most out of your volunteering mission.
Volunteer Feedback
It’s very important for the organisation to be able to collate feedback from their employees who have volunteered so that they can see the real positive impact they’re having. The volunteers add feedback at the end of each Volunteering mission which gets reviewed by the Volunteer Coordinators and is posted onto the Volunteer Stories Board for everyone to get inspired. In the future, the Volunteers will be able to reassess their skill set as part of the completion of a Volunteering Mission.
Reporting
Reporting is very important so that you can gauge the impact and effect you’re having. The application comes with a Dashboard view of both qualitative and quantitative reports. In terms of qualitative feedback you can view the amount of volunteer days, current volunteer statuses and types of volunteering. In terms of qualitative feedback in the Dashboard, there are cards from each volunteer that get posted once the whole Volunteering Opportunity has been completed.
Your Volunteer Profile
You can use your Volunteer Profile to have a look at your current and past Volunteering Missions, Kudos Points and skills set matrix. In the future, Volunteers will be able to link their profile to the personal and professional goals and update their skill sets via their profile.
Kudos Prizes, Gamification and Machine Learning
The application has gamification built into it to attract volunteers in Volunteering Vacancies that may not be very popular. Using Predictions Studio case type completion prediction, the application makes a decision to increase the Kudos Reward points for that mission.
The Volunteer can earn kudos points which they can go and exchange in the Kudos Store. The Kudos Store prizes can be set by the organisation, if the organisation wants to give a special prize such as Pega World tickets, concert tickets and so on. But also other people can donate prizes to the Kudos store.
How I built it
I started by focusing on the centre of the process... the microjourney, the rules and the 'brain' of the operation.
Highlighting the most important transaction of the solution, the 'Volunteering Mission' I started by defining the personas alongside with the data elements, the business rules needed (Approvals processes and routing) and the intelligence part of the solution which would manage the supply and demand of the requests.
(above) Pega App Studio - View of Microjourney and Personas in 'V For Volunteer'
This approach meant that the solution can be omni channel without having to start building any custom logic or siloed view of the data within the application.
A key point that was highlighted in the microjourney looking at the business architecture was the fact that multiple people could be volunteering in multiple vacancies under one 'Volunteering Opportunity'. As this was my first time developing on 8.4 I decided to take a look at Pega Spaces and found these to be very fitting for a use case where you need to coordinate and collaborate with a team. As there wasn't a way to create a new space or post to an existing space from App Studio I created the logic to allow the end users to create their own Space and attach it to the case.
As part of this, I created a Smart Shape (Post post to an existing Social space) which I will be looking to componitise (alongside with a create Pega Space Smart Shape) and submit to the Pega Marketplace in the future.
While working on the key microjourney I soon realised that the relationship of a volunteering opportunity and a vacancy can be one to one or one to many. As I already had the basis of the microjourney mapped out, it was easy for me to abstract the Volunteering Mission into a Parent/Child case structure.
By doing so I created a 'Volunteering Opportunity' which has 'Volunteering Vacancy' as a Child Cases. I then started creating all the logic required in the Parent Case in order for users to be able to create New Opportunities that would get the correct organisational approval, will capture any additional managerial approval requirements and will automatically create Vacancies and post them to the Volunteering Board - alongside automatically creating a new Pega Space if the user selected to.
An initial idea was to create a 'brain' to manage the supply and demand of the requests. While researching the new features and techniques the Pega platform has I decided to used the out of the box model but create a custom 'adjustment' mechanism with the introduction of gamification.
Using the Pega Predictions Studio I create a prediction to find out the likelihood of a volunteering vacancy getting completed. As you can assign any type of proactive action based on the predictions I created a Local Data Storage Data Type that with the use of a Data Page is capable of initialising and maintaining Volunteer Kudos Points.
I identified the first stage of the Volunteering Vacancy being the point within the microjourney that would give insight if the case is to be completed. Maybe not in the initial stage, but if the Volunteers Manager had to reject the Volunteering mission or the Volunteer half way through their mission they gave up, the case would move to the initial stage where the prediction would be used to increase the Kudos points.
(above) Actionable ML Model used within the application
Challenges I ran into
One of the key challenges I ran into and a huge lesson learnt was not using savable data pages right from the start. It’s important to take time to understand the new features of the platform to ensure you’re building the solution in the right way.
Accomplishments that I'm proud of
I created a Smart Shape as a result of working with Pega Spaces and seeing the potential they could have and how Pega App Studio users could interact with Spaces.
Pega Spaces are fairly new (at least to me!), initially I didn't really know what to make of them but then I saw their potential. I felt like this is a great way to organise teams and work but thought it would be good to guide users to when they should create new spaces through a case rather than only be able to create new ones in the Pega Spaces tab. I incorporated Spaces in the Volunteering Opportunity as an optional preference to encourage collaboration. When the user selects that they would like a new Space created, the solution creates a new Space, pins the case to it and also inserts a reference to the Case and Child Case(s).
As this was a new idea I created the rules within the application but I have since started abstracting the rules into their own component and have exposed the functionality as a Smart Shape that all Pega Platform users will be able to import into their solution and use the smart shapes in Pega App Studio.
(above) New Smart Shape [Pin Case to Group] - to be 'componentised' in the future and utilised by the solution in the future
What I learned
This has been a great learning experience. I don't have a lot of experience in working with the Pega platform and especially Pega 8.4 but I learned lots of knew things such as:
How to create report definitions
How to create a chatbot in Pega
How to create Case Type predictions
How to create and user saveable data pages
The importance on working on the micro journeys prior to any major development and understanding the key issues you're trying to solve
(by taking a hands on approach and using Pega Academy)
What's next for V for Volunteer
1. Enhanced employee skill set functionality
The solution already comes with a skillsets feature which you can edit and add the skills of the volunteer. However, a future feature will include the ability for the Volunteer to make a 'self assessment' of their skills sets and be able to connect these to their professional development. In addition to that at the end of each Volunteering challenge, the Volunteer would be able to update their skills and add knew skills they felt they gained from the experience.
2. Get feedback from Volunteering buddies
Using email IVA the solution will be able to (as long as the Volunteer agrees) email the people the Volunteer interacted with during their mission, get some feedback to allow the Volunteer to review that feedback in order to reflect on what they've done and what they could have done better.
3. Smart notifications to match volunteers looking to improve in areas new opportunities are based in
This feature is the one of the most ambitious ones. The solution will be able to find what the Volunteers have entered in their self assessment and match Volunteers with challenges that would help them grow in those specific areas. This would also require a more upfront list of skill sets at the Volunteering Opportunity and decisioning features.
4. DX API exposed in your company's website to allow partner charities, foundations and volunteering organisations to create new opportunities
Leveraging the power of the DX API, the solution will be able to be embedded in your website to allow you to collaborate with local Foundations, Charities and other organisations that require Volunteers.
5. Log my current volunteering missions
Do you already Volunteer for a special cause? The vision is for the solution in the future to allow you to log your current Volunteering missions so that you can link that good work to your personal and professional development in a structured way and gain recognition.
Getting Started
Due to the GitHub files size limit being 100mb and the Product Rule being slightly larger (129MB) the Product Rule is hosted on a publicly available Google Drive folder which you can download it from.
The out of the box solution comes with four operators. To get a feel for the application and a general demo, you can use the SudoDemoVolunteerUser operator that has access to perform all actions. If you would like to see how each role within the application interacts then you can use the three set operators and switch between them to create, approve and volunteer for an opportunity.
Once you have imported the application, you will need to go and enable the out of the box operators and assign them a password which you will need to change at first log in.
Out of the box operators:
DemoVolunteer
(Can create volunteer opportunity and volunteer for existing vacancy)
DemoVolunteerManager
(Can create volunteer opportunity, volunteer for existing vacancy can approve volunteering for DemoVolunteer)
DemoVolunteerCoordinator
(Can create volunteer opportunity, volunteer for existing vacancy and approve new volunteering opportunities)
SudoDemoVolunteerUser
(Use this role if you want to take a quick look at the application. This role can create, approve and volunteer for any vacancy allowing you to go through the demo without having to jump from operator to operator.)
Roles
The solution has kept the roles simple. You can assign the out of the box cosmos 'VoluntApp:Users' role to a Volunteer/Manager (and just reference the Reporting Manager in the Operator Rule) or assign the 'VolunteerCoordinators' to a user that can do the same as a Volunteer/Manager but also approve new Volunteering Opportunities. The Admin role is set as standard 'VoluntApp:Authors'.
Research
A 2020 Vision for Employer-Supported Volunteering (Accenture)
https://www.accenture.com/t00010101T000000__w__/gb-en/_acnmedia/PDF-17/Accenture-ESV-Report-V13.pdf
TIME WELL SPENT - A NATIONAL SURVEY ON THE VOLUNTEER EXPERIENCE (NVCO)
https://www.ncvo.org.uk/images/documents/policy_and_research/volunteering/Volunteer-experience_Full-Report.pdf
TATA Engage (TATA)
https://tataengage.com/blog/
2017 Volunteerism Survey (Deloitte)
https://www2.deloitte.com/content/dam/Deloitte/us/Images/Misc/infographic/us-2017-volunteerism-infographic.pdf
Corporate Volunteering Survey: The Extent and Nature of Corporate Volunteering Programs in Australia
https://search.informit.com.au/documentSummary;dn=149230874020089;res=IELFSC
CIPD Employer Supported Volunteering Guide (CIPD)
https://www.cipd.co.uk/Images/employer-supported-volunteering-guide_tcm18-27612.pdf
Information on The Institute of Customer Service
https://www.instituteofcustomerservice.com/
7 business benefits of employee volunteering (SAGE)
https://www.sagepeople.com/about-us/news-hub/benefits-volunteer-days-employee-engagement/#
NCVO WHAT ARE THE BENEFITS OF VOLUNTEERING (NVCO)
https://data.ncvo.org.uk/impact/what-are-benefits-volunteering/
Reach out
I started this project just as a submission for the hackathon but learning so much about Volunteering and the benefits it can provide to individual, businesses and our communities I've developed a passion for this subject and tried to make a solution that is as close to production ready as I can make it. I hope organisations realise the true potential this solution has to offer them and if there is a take up of this application I would be looking at enhancing its features.
If you would like to collaborate on this in the future please feel free to reach out:
https://www.linkedin.com/in/angelomermiklis
Final food for thought...
Research Infographic from Deloitte
Acknowledgements
Music:
https://www.bensound.com/royalty-free-music
Slide design:
www.slidescarnival.com
[Creative Commons License Attribution 4.0 International]
The photo of
Volunteers in blue T-shirts
[Creative Commons — CC0 1.0 Universal]
All logos and images have been referenced in the place of use.
The logo for this project (V/Victory Hand) and Kudos Points coin icon have been created by Angelo Mermiklis as part of this project.
Built With
appstudio
cosmos-ui
dedication
passion
pega
pega-chatbot
pega-cloud
pega-predictions-studio
pega8.4
Try it out
drive.google.com | V for Volunteer | An omni-channel web platform built on Pega 8.4 that sources new volunteering opportunities, connects your employees with opportunities, helps them grow their skill sets and rewards them. | ['Angelo Mermiklis'] | ['Best in Show'] | ['appstudio', 'cosmos-ui', 'dedication', 'passion', 'pega', 'pega-chatbot', 'pega-cloud', 'pega-predictions-studio', 'pega8.4'] | 0 |
9,937 | https://devpost.com/software/pyra | Home
Dashboard
Collaborate
Voting
Vote Results
User Profile
All Ideas
Search
Inspiration
2020 brought tremendous change to the way we work. Almost overnight, our team transformed from a group of teammates working side by side in our office every day, to sending emails and setting up video conferences from a distance. While we continued to deliver successful implementations and provide top-notch support to our clients, we lost much of the connection and togetherness we once had in our office setting. Our new work-from-home way of life limited our collaboration and our limited collaboration began to stifle our innovation. The company culture we worked so hard to cultivate was in danger of becoming a thing of the past.
That is why we created Pyra. Pyra is an application we use to innovate, collaborate, and reach the highest levels of our organization to make change. Pyra is an “Idea Factory” where any employee can submit a new idea to the organization, and everyone has a say in where that idea goes. Ideas are open for collaboration and voting, which follows a set of business rules to funnel them up the pyramid of our organization, where real change can be implemented.
Our work environment may continue to change, but our ability to innovate shouldn’t. Pyra is here to make sure of that.
What it does
Innovation
The Pyra application is built around one central case type, an “Idea” case. An Idea
case allows any employee to propose something new to their organization. An idea can be something as simple as a new team building event or something more complex, like a proposal to utilize a new technology or implement a new hiring strategy.
The case creation process is simple, allowing users to focus on their ideas rather than a complicated interface. All they need to get started is an idea name and description, and they are ready to go. But, thanks to Pega’s easy to use drag-and-drop development, these fields can easily be tweaked, modified, or added based on an individual organization’s needs.
Collaboration
While the “Idea” case is the center of the Pyra application, collaboration is the focus. Once an idea is created, it becomes discoverable to everyone at the organization. The Idea can now be followed and collaborated on, using the power of Pega’s Pulse capabilities. Users are encouraged to give their feedback and opinions on every case, so the creator can expand and improve upon their original idea.
To promote ideas as they are submitted, an activity feed keeps users up to date in real
time on their teammates actions. Exploring ideas is made easy with views on trending topics, ideas requesting collaboration, and ideas ready to “move up the Pyramid”.
Once an idea has passed it’s collaboration phase, the owner is ready to open the idea up for voting. Voting occurs in three tiers, although this can be dictated by the organization’s structure. Successful ideas that are voted up the tiers are exposed to the highest leadership at the company. Getting your ideas to the people who have the power to effect change is what Pyra is all about.
Engagement
Pega’s DX API allows for the use of a powerful Pega backend with the vast options of a custom front end. Pyra takes full advantage of these technologies in our metrics dashboard. Pega reports are displayed using custom react components, and leave open the possibility for any reporting an organization might need or want.
Powerful, custom dashboards keep users engaged and informed, encouraging higher
participation and company involvement. Leadership can also stay better informed about what is happening throughout their teams, allowing them to keep tabs on the pulse of their organization.
Discovery
Finding whatever you need in Pyra is made simple with Pega’s ElasticSearch
capabilities. ElasticSearch’s powerful search mechanism enables users to explore their interests and find relevant ideas at lightning fast speed. Teammates are brought together by their common passions to collaborate on new ideas.
How we built it
Pyra is a fusion of technologies, powered by Pegasystems. The Pega Digital Experience API allows this application to leverage all the best parts of the low code Pega platform as well as all the best parts of the custom front end React framework. Pyra’s robust, aesthetically appealing interface is backed by the powerful business logic of Pega Platform.
Challenges we ran into & What we learned
Our team had no experience working with React or working on the front-end side of the DX API prior to this application. There was a learning curve associated with learning how to work with both of these technologies. We were also limited by time constraints. We have ideas for other case types that we would like to implement in the future but wanted to make sure what we had was production ready and had a nice user interface.
Accomplishments that we're proud of
Our goals at the beginning of the competition were to increase our knowledge and to build a beautiful, non-traditional Pega user interface utilizing Pega’s Digital Experience API. We accomplished both of these goals and we are extremely happy with our final product. We established a reusable framework with which we can build additional case types, as well as use this framework as a starting point for future applications that plan to utilize DX APIs.
What's next for Pyra
While Pyra was created for the 2020 Pega Community Hackathon, development won’t stop once the competition ends. Pega is a technology built for change, and so is Pyra. Organizations come in many shapes and sizes, and Pyra will adapt to that reality. Administrators will be able to dictate complex voting structures without development changes. To focus the conversation, organization leaders will be able to pose challenges to their community, and community members can post their ideas in response to the challenge. Pyra is a simple but powerful idea, and the sky's the limit.
Developed by
Built With
digital-experience-api
elasticsearch
pega
react
semantic-ui-react | Pyra | Pyra uses a modern React UI integrated with Pega’s DX API to give employees a way to get their ideas in front of the right people to effect change in their organization, even while working from home. | ['Alex Vargo', 'Anna Whittaker', 'Amanda Shekarchi', 'Daniel Engel', 'bparlett', 'Allyson Meltzer', 'Joe Offutt'] | ['Runner Up'] | ['digital-experience-api', 'elasticsearch', 'pega', 'react', 'semantic-ui-react'] | 1 |
9,937 | https://devpost.com/software/dapi-gen-document-generation-via-rest-api | Diagram
Admin Portal: Dashboard
Admin Portal: Manage accounts
User Portal: Dashboard
User Portal: Account Details
User Portal: Templates
User Portal: Templates data fields
Inspiration
With the fast-changing market, the need for a different type of documents to produce is frequent. The ability to keep pace with the market need is hindered if every time a new document template or update to an existing template requires the business user to reach out to the IT team.
Idea was to provide document generation feature to non PEGA applications/lower than v8.4 PEGA applications of an organization which is already has PEGA Platform license. Reason behind this thought process is, there are many challenges/limitations faced on the document generation functionalities, cost for an additional software for each technology and difficulties in maintaining a huge number of templates in an organization level for several technologies used by certain organization.
What it does
Document generation REST API accepts request as JSON and generate the document along with the merged data from Request JSON and return the merged document (.docx as of now, it can be extended to .pdf also) as Base 64 encoding via JSON response. Requesting application needs to pass the merge fields and the template ID which is already setup through the document generation portal(JSON request automatically generated from user portal for each template).
Each Application or Department or Line of business has an account on document generation portal to setup their templates (Each account will be provided with separate API Key). Business users can deign, map and maintain their templates through the user portal and share the JSON request details for each document to developer and developer needs to map the value from the requesting application and call the document generation REST API.
How I built it
Recent version of PEGA platform v8.4 released with a feature for document generation which can be used for PEGA applications. This document generation REST API built on PEGA v8.4 along with 2 portals to manage accounts and templates which can be used by any application by calling the document generation REST API.(Technology agnostic and easy to setup and maintain)
Admin Portal
This is for creating a new account and managing existing accounts. An account could be an application in an organization or a department or a line of business. Once the user is added to an account, the user is notified with the user credentials via email. The ability is also available to make updates to the existing accounts.
User Portal
Once the user login to the assigned account, the user could see the account details, such as API Key and REST API Endpoint URL. Users can add new templates to the account then the user should identify the data fields in the template and the data type, whether the type is a scalar or list. User can add fields to template instance on portal and map the same fields accordingly on the template document (.docx file) and upload it. Then test it locally as well as via REST API also through this portal. Once all the tests are successfully completed generated JSON can be shared to developers to integrate the REST API to respective application(s).
Highlights of this solution
• Easy to setup and quick turnaround time to go-live
• Business users can use this portal as organization/department level master repository for templates. Single
place to keep the up to date templates. This will reduce the mismatches between versions compared to
conventional approach, having multiple repositories for business users and systems.
• Business users can directly update the template in case of a change in format or styling or static text updates.
Can simply search and download the template then update and upload it. (if there is no change on merge fields
then zero developer effort).
• Technology agnostic and most of the platforms support REST API.
• In addition to that business users can see the usage of each template on dashboard (Count of each
template requests under their account)
Challenges I ran into
Since I'm new to PEGA v8.x (I'm hands on PEGA v7.2.2 and lower versions), I have learned the new features which are introduced above v7.2.2 and applied to this project such as Savable data pages, queue processors, In-built document generation features and new UI design Cosmos within short period of time. It was interesting learning and applying the new features to this project.
Accomplishments that I'm proud of
I'm proud of completing this Hackathon project on-time with great quality(PEGA Compliance score of
97/100
) along with my routine work schedule. I will be able to apply this knowledge and new features on my future projects.
What I learned
I have learned the new features of PEGA v8.x and docx4j library functionalities used inside PEGA document generation function used internally.
What's next for DAPI GEN - Document generation via REST API
Currently this document generation API supports return type as Base 64 encoding and
.docx
as outcome document type. Planning to enhance the return type as
Uploading the documents to Amazon S3 bucket.
Sending as email from REST API.
In addition to that enhancing the support of outcome document type as
.pdf
.
Built With
pega | Document generation via REST API (DAPI GEN v1.1) | Generate documents with merge data from any application using a REST API with JSON, built on PEGA platform v8.4 | ['Ajanthan Arulananthar'] | ['Innovation Award'] | ['pega'] | 2 |
9,937 | https://devpost.com/software/empathia-employee-assistance-and-crisis-management-app | Application Overview
Dashboard - Disaster Alerts, Response Rate, Trend
Emergency Response Plan List
Application Architecture
Inspiration
Crisis Response Management System
application is inspired by our personal experience. Cyclone
Amphan
had landfall on May 20, 2020, which devastated our city, Kolkata and many areas in West Bengal, India. People were struggling with basic utilities. The communication system got so badly damaged that people couldn't communicate with each other for confirming their safety. No voice call was working. People were able to perform limited communication over SMS text. Though SMS provided very limited capabilities but it offered critical help to confirm people's safety during a crisis situation. All this happened amidst of COVID situation when organizations were already struggling with distributed workforce management. Virtual Assistance would have provided more assistance to the general population when people were isolated by physical space. We realized SMS is the only channel that is available in all types of phones(simple to smart) and attracts immediate attention. Thus, it is the most preferred channel for crisis-related communication.
What it does
Crisis Response Management System
is a Pega Powered Emergency Assistance and Crisis Management application. It is assumed that employees including field executives are using Pega based application for performing business functions. Geolocation tracking is enabled within the application. The application securely stores the last-known locations of the employees.
The application provides option to the Emergency Response Team to monitor potential disaster alerts which may need attention. For any critical alert, SMS notification is sent to the Emergency Response Team(ERT) who can create
Emergency Response Request if need. In Emergency Response Request, team can add impacted area details which will be used later to find impacted employees by looking up last known location repository. Then Emergency Response team can send SMS alerts to the identified employees.
Employees need to respond to the SMS sender with their safety status. This response will be picked up by an Intelligent Virtual Assistant which engages with the sending person to understand his/her status in a better way and offer additional assistance as needed.
How we built it
We have enabled geolocation tracking for all the Pega application users. The last known geo-location is stored securely in a repository. We are then calling
OpenCage Geocoder API
to convert geo-location data into address information. Application internally matches these addresses with disaster-affected areas to find potential impacted employees.
Application is integrated with
Global Disaster Alert and Coordination System(GDACS.org)
to get near real-time disaster alert.
The application uses
Twilio SMS API
to send alert to the emergency response team if any high alert comes in.
We have built SMS Channel using
Twilio Webhook
for bi-directional conversation using SMS. When any user replies to the message sender then Pega IVA is triggered. IVA sends back appropriate replies over the same channel. IVA internally creates different cases based on the response received from employees.
Challenges we ran into
Again the most challenging part was to find an infrastructure for distributed development. Internet connectivity was badly affected by Cyclone Amphan and it was not restored properly till early June. We couldn't make progress as planned.
Secondly, we struggled to find existing SMS based channel as Tropo service was sunset. Eventually, we built our own SMS channel using Twilio.
Third, this is our first application on Cosmos theme. It took little time to learn tips and tricks to build application using Cosmos.
Accomplishments that we're proud of
We have built several component applications which work in harmony to offer the business benefits.
Twilio SMS Channel
- We couldn't find any dedicated SMS based IVA channel in Pega Marketplace. We have built this channel which can be utilized by any application as component and use it for omni-channel experience.
OpenCage Geocoder API
- We have utilized OpenCage Geocoder API for map integration. This a good alternative to the Google Map API. The integration is created as form of component application and any other application or team can very easily reuse it.
We are really excited about the demo video which we created. The entire video was created using MS PowerPoint. We didn't have access to sophisticated editing tools and screen recorders. However, these challenges couldn't limit our creativity.
What we learned
We have learned how Multichannel Case Processor (MCP) works in Pega and how to extend it for new channels.
We have practiced building micro applications as components for better re-usability.
We have mastered the art of working collaboratively,specially when people are separated by physical space.
We now know how to use commonly available tools in the most optimized way to achieve extraordinary outcomes.
Additionally, we learned many tips and tricks of MS PowerPoint, TTS, etc.
What's next for Crisis Response Management System
This is a prototype build but has infinite potential. The application can be integrated with different public alert systems using the Common Alerting Protocol(CAP) to access the disaster alerts and redistribute the workload to have minimal impact on business services.
The virtual assistant channel can be expanded via other popular channels like Facebook, Twitter, Email to offer more connectivity options.
The application can be exposed via API to be consumed by others as SaaS services.
The application, currently, has few service requests which need to be extended based on actual requirements.
New Updates
Release 1.2 - July 20, 2020
User Interface Uplift
REST API for external applications for reporting geolocation data
Implementation of Notification channel for outbound SMS
Built With
chatbot
gdacs
opencagegeocoder
pega8.4
sms
twilio | Crisis Response Management System | A Pega powered intelligent app which minimizes communication gap between organization & its people during crisis by AI & Virtual Assistant. It accelerates assistance & services to those in need. | ['Arnab Paul'] | ['Inspiration Award'] | ['chatbot', 'gdacs', 'opencagegeocoder', 'pega8.4', 'sms', 'twilio'] | 3 |
9,937 | https://devpost.com/software/feed-the-need-9a0wcx | Crutch Services
Login Credential
Terms and Policies
Volunteer Survey
Our Inspiration
"Anybody can help but the help at the right time brings the big difference.
Anybody can help everybody but helping the needy brings the big difference".
As rightly quoted above, helping the needy at right time brings the huge impact on the society. On this pandemic situation we come across lot of people in a risk of losing their life though staying inside the home .The reason behind this is,not COVID-19 but POVERTY. There also exist people who is passionate to serve the society by providing the people needs .So we,the TEAM CRUTCH has decided to serve the society through our tech minds by designing the app called CRUTCH which act as bridge between the donor & recipient .
This application is built on top of PEGA platform version 8.4
Challenges
The challenging task for us is making the live request ,choosing the most needful services,handling the services between donor & recipient .But as a team we were able to conquer the challenges in to fruitful product.
CRUTCH acts as a platform of sharing assets to needy people at right time from donors.
Learning Experience
We had a great learning experience .We had a chance of experiencing activities,customizing harness & portal.
.
Uniqueness of Our Application CRUTCH
Crutch provides the customer 6 services ,where the customer can chose any service through his/her interest.
Bringing the Need at your doorstep & right time.
Apart from donor & requester crutch has an additional feature of volunteer for people who is passionate in serving the society to assist donor & recipient in bringing their need at their doorstep a right time. Serve the society-tops the leader board. Crutch has an unique feature of maintaining leader board for volunteers
on the basis of one who serves the best leads as top performer in leader board.
About crutch
Crutch is a platform that extends help for the needy people at right time.The motive of crutch is to concatenate the demand & supply . The services available in this app includes Food Service,Education
Service ,Cloth Service ,Blood donate/Receive (share blood ) service ,Organ donate /receive (share organ) service,Money (Crutch pay )service .
How Crutch Works
Customer can register as donor/recipient initially .while logging in the next time he has the option to change his role type if he wills. After logging in he can chose any of six exclusive services .If the customer acts as recipient he can request his/her need. The intimation about the request will be sent to all registered donors if any of the donor accepts to donate, then crutch provides them an option to chose Volunteer assistance .if he chooses volunteer service the crutch volunteer will help in delivering the requirement from donor to recipient at right time. Thereby crutch feed the needy people at right time. Crutch has verification team to ensure that details submitted by recipient doesn't contain any false information.
Crutch Functionality
The crutch has 6 services apart from registration & Volunteer Survey & Feed the Need.The following is the detailed description of all case type.
1)Registration:
The customer can sign in in to crutch application via registration case type. He has to specify his role type(donor/recipient) & service type(6 services) based on which the work group & workbaskets are assigned for them.They can change role type in future as well.After providing the preliminary details such as personal info,Organisation info(if he/she representing any org) & address details.After the approval by the admin crutch the access credentials are created for the customer.The case will not move to approval unless he accept terms & conditions of crutch .
Innovation:
We have implemented completion status- Progress bar for the customer to track his registration completion status
2)Feed The Need:
The purpose of this case type is to help the needy people in choosing the service according to their need.
Six exclusive services are shown to customer on their next login where he/she can choose one and proceed with flow.
Innovation: Six attractive icons are configured where the user clicks the Icon the corresponding case type begins.
3)Crutch Pay:
The purpose of this case type is to donate/receive money .The recipient begins the case where he views all his details in editable format .They can edit it if necessary.The customer can raise money request for his own self or for his friend/relatives.In case of friend/relative .He has to provide their details.There are few predefined reasons present for requesting money such as requesting fund for orphanage/home, requesting fund for natural calamity,,requesting for illness/Accident .Customer can also provide his own reason of requesting by choosing others.He has to provide all the required info along with necessary documents.He will also specify his preferred timing for help.After his submission,there happens background verification process by crutch admin where all details are checked. The case proceeds forward only if details are true. Then on the successful completion of verification the intimation will be sent to all donors if any donors accepts he can confirm his own details and move for payment. Method of Payment can also be Negotiated by donor if he is comfortable with.After receiving the money the recipient fills the fullfilment and provide feedback.
Innovation:Modal dialog -Pop up for thanking the customer
4)Food Service:
The donor /Recipient can begin the case by providing the Food details.If recipient begins the case it moves to donor for viewing the recipient details and if he accepts the request then it moves to gather delivery information.There the recipient has an option of requesting any volunteer service then the case routes to volunteer workbasket if any of the volunteer picks the work, then he confirms the donor& recipient address details and finally he delivers to them.
If the donor begins the case he provides the details of donating food,the case routes to recipient workbasket .
The recipient has an option of selecting self or volunteer service .If he goes for volunteer service ,then it routes to volunteer workbasket.if any of the volunteer picks the work, then he confirms the donor& recipient address details and finally he delivers to them.
5)Cloth Service:
The donor /Recipient can begin the case by providing the Food details.If recipient begins the case it moves to donor for viewing the recipient details and if he accepts the request then it moves to gather delivery information.There the recipient has an option of requesting any volunteer service then the case routes to
volunteer workbasket if any of the volunteer picks the work, then he confirms the donor& recipient address details and finally he delivers to them.If the donor begins the case he provides the details of donating cloth.the case routes to recipient workbasket .The recipient has an option of selecting self or volunteer service .If he goes for volunteer service ,then it routes to volunteer workbasket.if any of the volunteer picks the work, then he confirms the donor& recipient address details and finally he delivers to them.
6)Education Service:
The recipient begins the case where he has the option to acts as referencer or self based on type of request he raise. If he is raising for him he can provide as self, if not he can act as referencer. He gives all his preliminary details & attach Necessary Documents.Then the case move forwards to background verification Process.
Unless the background verification successfully completes the case does not move forward .On Successful completion ,it routes to donor workbasket.If any of the donor accept to provide contact details are shared with both.Then fulfillment details are received from recipient after receiving the help.
7)Share Blood:
This case type can be accessed by donor/Recipient.If donor begins the case he can donate the blood by Providing all the necessary details .If in case of recipient begins the case ,he has two options either he can view the already donated blood details which matches his requirements or he can raise a new request.After his submission of request the case move forwards to donor where he can accept the request & confirm his details and also assist for volunteer service..thus,with help of volunteer support requirements are delivered from donor to recipient.
8)Share Organ:
This case type can be accessed by donor/Recipient.If donor begins the case he need to provide his details If he had his organ registration certificate he need to attach it then the admin will review. Then the admin will approve /reject his request. If he does not have his organ registration certificate he can request for medical assistance.Now the hospital details are mailed to the donor. He have to visit the hospital within 5 days.Then the will check him and provide the certificate. If the case is begins by the recipient he can request for the organ.Noe he need to provide the required information and the certificate.Then the case will be routed to Donor hospital. If the donor is available the details will be send through mail.Then he will contact the hospital for further procedure.
his hackathon is one of the memorable learning experience for our team .We had a great learning experience of new rules such as creating dynamic routing etc.
What's Next
As a team we ensure to give our cent percent effort to bring solutions to the problems & Challenges prevail in the society.
Built With
pega
Try it out
github.com | Feed the need | To help the people who are in need | ['Royal A', 'Vinoth Prabhakaran', 'Sandhya Kamalraj', 'VISHALI MANIVANNAN', 'Hemalatha Gandhi', 'Rehaana Parveen N', 'Rubini Madhasen', 'Vijayalakshmi Murugesan'] | ['Community Choice Award'] | ['pega'] | 4 |
9,937 | https://devpost.com/software/privacy-enabled-contact-tracing-for-covid-19-using-pega | Inspiration
The idea is an excerpt based on the github link from Nicky Case -
https://ncase.me/contact-tracing/
Which details Protecting Lives and Liberty – how tracing apps can foil both COVID-19 and Big Brother
As part of this hackathon, a prototype based on the above diagram was established, with integrating capabilities of Pega to establish connectivity in reading the logs from privacy enables logs, process them in pega and maintain a common repository for anyone to check if they had been exposed to anyone suffering from COVID-19
What it does
It does ensure privacy in tracking peers who had been in close proximity without revealing the details of the person
How we built it
Using Pega 8.3 - the integration of DP3T is a mock up HTML only, which in real world could also be doable from Pega.
Challenges we ran into
Timeline. we did an entire project i pega cloud and the instance finally didnt show up - resulting in providing mock up screens to explain the flow at last minute.
Accomplishments that we're proud of
Unleash the capabilities of Pega to provide a single repostory for all types of contact tracing in place - without disturbing the privacy of people
This idea could also be a primer for business shops to promote the contact tracing locally
What we learned
Pega's capability to scale and hold any kind of data for processing and manipulating
Decentralized Privacy-Preserving Proximity Tracing
What's next for Privacy Enabled Contact Tracing for COVID-19 using Pega
Immediately is to create the provisioining of DP3T logs
360 use of this application
Built With
dp3t
pega
Try it out
github.com | Privacy Enabled Contact Tracing for COVID-19 using Pega | Contact Tracing using Decentralized Privacy Preserving Proximity Tracing (DP3T) - a technology used to send and receive formatted gibberish messages for tracking | ['Sathya Thangaraj', 'Jaghadish Rajagopalan'] | [] | ['dp3t', 'pega'] | 5 |
9,937 | https://devpost.com/software/agriconnect | Purchase process
Inspiration
In Today's post COVID 19 world, farmers are struggling to sell their produce in absence of farmer's market. While some of the states in US have set up a digital farmer's market, bringing them back to normal still seems to a far fetched idea.
What it does
Provides analytical insights based on data from government on the right crop, right season and better weather predictions. Additionally, it allows farmers to list their products and consumers to buy directly from farmers.
How we built it
Usage of Government data from various website, predictive analytics to predict the future trend.
Pega's OOTB drag and drop control and map API to create a e-commerce C2C platform
Challenges we ran into
Getting data from source to perform predictive analytics
Understanding what exactly does a farmer need
Accomplishments that we're proud of
Fully working shopping cart
Predictive analytics on prices and produce to cultivate
Realtime logistic tracking
What we learned
A problem as big as farmer's market needs to have the best data available and simplest UI to help them to their business
What's next for AgriConnect
Connecting to more real time data sources, interfaces to connect regional government data provides, enhancement the logistics facility due to post COVID19 conditions.
Built With
google-maps
pega
Try it out
lksi6dzt.pegace.net | AgriConnect | A post COVID 19 world digital farmers market | ['Hari Losari', 'Sudip Gupta', 'Avinash Haridasu', 'Chethankumar Mahalingappa'] | [] | ['google-maps', 'pega'] | 6 |
9,937 | https://devpost.com/software/process-hazard-analysis | A visual representation of the specific industrial chemical process which the PHA was created for in the demo.
What a traditional Process Hazard Analysis looks like
Potential savings
The matrix math used in the decision tree, based off of current/traditional Process Hazard Analysis logic
Inspiration
I just graduated from the University of Cincinnati with a Bachelor's in Chemical Engineering and a Pre-Medicine Certificate in May 2020 (one month ago). I worked as an intern at BASF (the world's largest chemical company) for about a year and a half. In my time there, I sat in on a lot of Process Hazard Analysis meetings. Basically, a Process Hazard Analysis is a document which identifies all possible risks inherent to a generic industrial chemical process and outlines how the company will minimize these risks. The word "meeting" is rather loose for these gatherings... they were a full 40 hours long -- a full work week, sometimes longer. Not only that, but the best and brightest were in attendance. Because the safety of humans was involved, all of the most experienced chemical engineers were usually present. Food was often catered to deal with tedious and dull details relating to the process in terms of safety -- even down to counting the threads on screws to be used. Contributing to these meetings was an arduous odyssey, and especially costly -- but it had to be done to ensure the safety of the workers, consumers, and residents nearby the plant. It's not only BASF that does this -- it's a necessary endeavor for
every
process on any chemical plant, and any given chemical plant usually has around 10+ processes, with more being added and updated frequently -- which means multiple Process Hazard Analysis meetings a year.
What it does
One of the most challenging parts of creating a Process Hazard Analysis is thinking of all the possible sources of risk. Another taxing duty when completing a Process Hazard Analysis is then thinking of realistic recommendations to address the possible sources of risk to minimize danger. Both of these tasks are facilitated using my application created in Pega. The user is prompted with relevant possible sources of risk by asking them questions, such as “What if a compressor overspeeds?” if the user has indicated that their process will use a compressor. Then the user can answer appropriately for their specific process. The app also prompts the user with respective recommendations to make their process safer, depending on which questions they answer. Finally, based on the answers that the user enters, a calculation is performed which rates each specific hazard with an Action Priority Status. The Action Priority Status can either be "A", "B", or "C", with "A" indicating a very high-risk hazard and "C" indicating a relatively low-risk hazard. After the user sees their current Action Priority Status, they can use the prompted recommendations to think of safeguards to prevent that hazard from happening. After inputting a safeguard and how well that safeguard protects the process, the Action Priority Status is re-calculated, taking the safeguard protection factor into account. The goal is to minimize the number of "A" Action Priority Statuses by implementing robust safeguards. Finally, the user can review their answers, safeguards, etc. and print all of their data as a PDF, which is the final and complete Process Hazard Analysis. The app cuts down on personnel and labor hours necessary to perform a sufficient Process Hazard Analysis by prompting the user with potential risk questions and relevant respective recommendations. Now instead of 10+ engineers working 40 hours to make it, my app requires only about 2 engineers working 8 hours. This will save the company significant money even after only a single use.
How I built it
I first began by compiling an extensive list of potential hazards inherent for different apparatus used in industrial chemical processes. For instance, "What if a valve leaks?", "What if a valve experiences corrosion internally?", "What if a valve experiences corrosion externally?", etc. The list has 398 records in it. However, if the user can think of any hazards that aren't already listed, they can add them. They can also remove questions which aren't applicable to their process. I also compiled a list of materials (chemicals) frequently used in industrial chemical processes and included their respective HMIS ratings for Health, Flammability, and Physical Hazards. Lastly, I compiled a list of recommendations to remedy certain hazards. For example, if the user indicates that "What if a valve leaks?" is an applicable risk to their process, the respective recommendation suggested to the user to minimize this risk would be "Consider implementing dike walls to the surrounding area, installing LEL sensors, selecting high-quality thick insulation, and performing regular preventative maintenance". The user can choose to copy this recommendation as their safeguard, or they can formulate their own.
Next, I created an Activity to iterate every question for as many times as the user utilizes a particular apparatus. For example, if the user indicates that they have 3 compressors, then they will be prompted with each question about compressor risks 3 separate times. This is because different compressors may be handling/exposed to different chemicals, so the corresponding risks may be different for each individual compressors, even though they perform similar functions.
Then I created a decision tree to interpret user input and use the data in a formula to calculate the respective Action Priority Status rating. I also used a skin to assign a red highlighted background to an "A" rating, a yellow highlighted background to a "B" rating, and a green highlighted background to a "C" rating. Subsequent input also factors into the equation, which allows the user to implement more robust protections to lower the Action Priority Status rating.
Challenges I ran into
The biggest challenge I ran into was that the declare expression associated with my decision tree caused an error when I tried to create a PDF with said data. Pega said that the heap size was exceeded. Specifically: "java.lang.OutOfMemoryError: GC overhead limit exceeded". To remedy this, I made a "Review" page after the page which referenced the decision tree which contained almost all of the same data (except for the decision tree), and used that section in the "create PDF" feature.
Accomplishments that I'm proud of
I'm really proud of what I could accomplish considering I worked alone and just started using Pega in April of this year (2020), and balanced schoolwork on top of this submission. I asked questions to some people at my company, and they all told me how ambitious it was.
What I learned
I learned SO MUCH about Pega in these 6 weeks. How to use a declare expression, a decision tree, how to import and export records, how to configure different views, how to trick the java into letting me use base-ten logarithms, how to make and use a skin, how to use embedded sections, how to create a PDF from existing data, how to create a guided tour, how to make activities, how to create a custom function and a library... and much more than I can't even remember. I was a total newbie before starting this app... so it's my baby. It's my blood, sweat, and tears.
What's next for Process Hazard Analysis
I could definitely make it a lot more user-friendly. It's pretty clunky. It still does the job, it's just not very visually pleasing. In the future, I'd like to include the Action Priority Status in the created PDF, and to make the PDF oriented to a landscape instead of portrait mode. To do this, I might instead try using a Word Document, but there wasn't time for that this time around.
Built With
pega
Try it out
www.filefactory.com
www.filedropper.com
app.box.com | Process Hazard Analysis | Making Industrial Chemical Processes Inherently Safer, Easier, and Cheaper! | ['Carrie Vennefron'] | [] | ['pega'] | 7 |
9,937 | https://devpost.com/software/smart-self-quarantine-system | Inspiration
Associated with Pega technology over years and with passion towards IOT, we came up with the idea that would help current or future pandemic situations, by building a IOT framework in Pega that can capture the data being shared by the wearable IOT trackers and trigger Next Best Action based services like 1. Ordering some prescribed medicines to deliver to door step 2.Scheduling video conferencing appointment with doctor to have an interaction with patient 3.Alert Emergency Medical services to pick the patient and move him to emergency center based on the strategies built on vitals. We can customize how we want use the data being received in establishing different customer journeys in Pega.
What it does
This application receives the health vitals data of the patient provided through the wearable IOT device and the same will be captured in to Pega. There will be predictive strategies running on the data received and appropriate service cases will be created in Pega to help the Self Quarantine patients.
How we built it
We utilized a Heart rate sensor IOT device connected to PI-board which will capture the heart rate from any person wearing it and sending the data periodically to the Pega application through API exposed in Pega, which will capture the data and act accordingly to create the respective case and route business configured work flow accordingly.
Challenges we ran into
Integrating IOT device to Pega application for the data share and configuring the firmware to communicate with APIs.
Accomplishments that we're proud of
Idea to address the crisis current world is facing and a collective effort of engineers coming together from various technological backgrounds (IOT and Pega) in accomplishing the same.
What we learned
So many things in fact, learned the real world problem by studying the American Hospital Association facts and statistics of how hospital resources being over utilized and on technology side how we can integrate IOT devices for remote monitoring to effectively manage the situations remotely using the Pega technological advancements.
What's next for Smart Self-Quarantine System
Dream to make it toto a working model and to give it a better shape for real use.
Built With
amazon-web-services
api
iot
pega | Smart Self-Quarantine System | Pega's Decision Hub integrated with Smart Wearable device, triggering Next Best Action based services based on health vitals being collected. | ['Surya Damodara', 'Mahesh Valavala', 'Anjaneyulu Karnati'] | [] | ['amazon-web-services', 'api', 'iot', 'pega'] | 8 |
9,937 | https://devpost.com/software/safe-hands-patient-engagement-platform-to-reduce-no-shows | Our user experience of all our portals for mobile/desktop. A consistent experience is a better experience.
Current world problem of health care systems.
Safe Hands Patient Engagement Platform. Built on Pega 8.4 and powered by Pega AI.
Real world impacts based on our research.
Our idea to solve this problem.
This solution can be used across multiple industries to avoid over booking and serve patients better in Healthcare, Life sciences as well
Features of our platform which can engage patients better.
Actors involved in our solution.
Our patient registration micro-journey which onboard patients into the application.
Our appointment booking micro-journey which feeds our adaptive models using out of the box case predictors.
Predictor classification according to Kaggle dataset.
Predictors which we have considered.
Predictors which we haven't considered.
Technologies used in this solution.
Just got an email notification which reminds me to take prescriptions on time...Applying personalization to improve patient experience
Just got an email notification which reminds me to take prescriptions on time...Applying personalization to improve patient experience
No-Show probability for healthcare assistant. Default value is 50% before the models gets updated.
Team behind this big journey. Special thanks to everyone.
Our logo - Your health is important for us. Thanks for watching this solution.
Inspiration
In today's world, patients are far too occupied to have time to wait around for the services that they don’t need. There are significant number of patients who would no-show for their scheduled visits or do not respond to the automated telephone call to cancel their appointments. Based on a recent study, one out of every five patients who schedule an appointment don’t show up. Every time a person skips their appointment, the healthcare industry endures a financial loss and patients miss out on receiving the treatment they need. If we could predict the no-show appointments, it would create a slot for others who are in actual need. Life is precious and every life is important.
In just a matter of four months as the COVID-19 pandemic spread across the world, it has stretched healthcare infrastructure of even the most developed countries. The rapidly increasing demand on health facilities and health care workers threatens to leave some health systems overstretched and unable to operate effectively. Our whole idea is to improve the health care utilization during this pandemic situation.
What it does
To reduce the repercussions of patient no-shows, we have implemented a new patient engagement platform built on Pega Infinity. This solution helps to predict no-show appointments for clinical trials, primary care and even specialty medical appointments powered by Pega self-learning adaptive AI models. This platform also helps to reduce physical interactions complemented with digital contact less collaboration and personalize all patient communications based on individuals' health conditions, medications with auto reminders
Key features of our solution:
1)Predict No-Show Appointments: AI is becoming a critical component for every industry. We have leveraged Pega Self-learning adaptive models that can suggest No-Show propensity by taking decisions in real-time. We have defined set of predictors based on data sets and designed an interactive mobile app to feed the data to train our models.
2)Contactless Virtual Appointments: Virtual consultation through skype that take place between patients and doctors via communications technology — the video and audio connectivity that allows “virtual” meetings to occur in real time, from virtually any location.
3)Patient Centric Safe Hands Mobile App: Now a days, Mobile apps become a primary way through which people patients contact hospitals. We have leveraged Pega Low Code mobile app builder to develop this Pega Mobile app.
4)Automated Personalized Reminders: Designed a framework on top of Pega Notification Framework to send daily Prescription reminders and appointment notifications to accomplish critical health tasks. These reminders are typically sent to individual patients to independently perform health tasks.
5)Instant Collaboration Platform: This feature facilitates collaboration and conversation among patients, doctors, and health care assistants. We have leveraged the out of the box Pega Pulse and Spaces to create patient groups to enable patients to post health related questions.
6)Data Sharing: Data sharing is an option to send videos, files between hospital and their patient. Patient data may include information relating to their past and current health or illness, their treatment history, lifestyle choices and diet details. We have leveraged the Pega out of the box documents gadget to build a better alternative to emails as the data might contain PHI.
https://safehandsapp.github.io/SafeHands/
How I built it
We prepared our product backlog with three sprint user stories with two epics and few features. Later we formed a team and started our development using Pega low code app studio. During the course of our agile discussions, we have improved our solution capabilities.
We have used the below three major technologies to implement this solution.
Pega 8.4 Community Edition: Used most of the out of the box platform capabilities to build our micro journeys. Low code mobile development platform to build our patient centric app. Self-learning adaptive AI models to predict appointment cancellation or no-show probability using Pega Customer Decision Hub.
DistanceMatrix.AI (Free Trial): To compute the distance and travel time between
points on a map with reliable and accurate APIs. This is used as a predictor for our self-leaning AI model which predicts appointment no-show.
Font Awesome: Icons are an essential part of many user interfaces, visually expressing objects, actions, and ideas. We believe that great icons can also affect in user experience. To leverage hospital or patient specific icons we have leveraged free version of font awesome to meet our requirements.
Leverage AI models in appointments:
• Adaptive AI models starts to learn based on the case response of every appointment micro-journey.
• Used Pega OOTB AI predictors to create a case Predictions.
• If the appointment is successfully completed, it will increase the model propensity.
• For this solution, we are showing this score to the Healthcare staff in the "All Appointments" landing page as a column.
• If the Probability of appointment no-show is high, Healthcare staff can either cancel, allow overbooking, add no-show fee, change appointment type, reschedule based on the organization policies.
• Right-now, we are allowing Healthcare staff to cancel the appointment.
• The above scenario scenarios are different for different clinics. Ex: There are lot many institutes like MHCD which can't even charge for no-shows.
• This solution can be used not only in Healthcare but also in early Clinical Trials, Airlines, Banking and many other industries. Based on the Kaggle dataset we realized that once the models perform well, its ROI will be high.
• We can also pass Patient past appointment interaction history to add as one the predictors to our models. This will be part of our future roadmap.
Reasons for choosing Pega to solve this real time problem:
• Based on few studies, we came to that September month has more healthcare no-shows and the lowest will be in October.
• Men has lower no-show compared to women. And there are many factors like hospital distance, time, day, patient age, gender etc.
• Based on research, each dataset will be different as it changes with hospital services. Then, how do we solve this?? We made an attempt using a new approach of Pega industry-standard Adaptive decisioning which captures and analyzes data to deliver predictions in situations where historical information is not available and continuously increases the accuracy of its No-Shows by learning from each appointment response.... #NoShowPattern #ModelDrivenResults #NaiveBayesClassifier
Challenges I ran into
We faced challenges to get the datasets to define our predictors. We spoke to few doctors in this field and spent most of the time to define our core requirements. We came to know that the hospital distance from home and travel time are two major real-time predictors in No-Show appointments and it was a challenge to calculate the distance on the appointment day considering traffic and distance. We are not able to find any libraries to get these values but after exploring we found distance matrix which compute the distance and travel time between points on a map in less than 1 second and 5 times cheaper.
Accomplishments that I'm proud of
Once we started this solution, we came to know that there is lot research going on this area. Even there are no major products(except few) or patents which can solve this problem. We have leveraged most of the capabilities of Pega which includes CDH Pega Mobile, Multichannel bots, Collaboration Platforms, OOTB gadgets to build something which is useful for the current situation.
The entire solution was built in less than 3-4 weeks. Initial 2-3 weeks of time was spent to design our idea.
What I learned
We learned to solve real world problems using Pega AI. Our intention is to apply AI for ethical and a good use case. Thanks to Pega for giving this wonderful opportunity to explore multiple use cases with this Hackathon. This Hackathon journey won't stop here as we wanted to apply Pega AI into many real time use cases.
What's next for Safe Hands patient engagement platform to reduce no shows
We would like use this application by extending as "Appointment prediction as a service" with any of the existing appointment platforms or tools used by Health Care applications. This can be used across the industries. Once our models becomes matured this will definitely reduce appointment no-show loss and create a new way of handling appointments across industries. This not only applies for Healthcare but it also applies for all the businesses which deals with appointment or booking process.
Features planned for Safe Hands 2.0 :
Schedule group appointments through mobile app and desktop.
Pass group appointments as inputs to self learning adaptive models.
Voice based reminders using Amazon Alexa Skills.
Leverage appointment booking interaction history into adaptive models.
Telemedicine enabled consultation/clinical trials using biomarkers and other native mobile features.
Predict events through stream data passed through wearable devices.
AI enabled personalized nutrition diet based on the health conditions.
Exploring Amazon Comprehend Medical to detect unstructured information and link to medical ontologies such as ICD-10-CM or RxNorm so it can be used to migrate the existing applications to Safehands.
Enable video calling facilities like Amazon Chime which is a HIPAA compliance to enable virtual appointments.
Build a generic appointment as a service which can be used across other industries. Ex: Overbooking in airlines.
https://www.youtube.com/watch?v=ZFNstNKgEDI&feature=youtu.be
Customize this solution for veterinary hospitals as well.
View all the previous appointments with observations both from internal and external applications using interfaces.
Enable localization to support multiple languages.
Store the patient health care records in block-chain for emergency support.
Survey based feedback capture and post-service follow-up care.
Built With
distancematrixai
fontawesome
google-maps
multichannelwebbots
pega8.4
pegacdh
pegamobile
Try it out
github.com | Safe Hands patient engagement platform to reduce no shows | Our solution helps to predict no-show appointments for clinical trials, primary care and specialty medical appointments powered by Pega self learning adaptive AI models with contactless collaboration. | ['https://safehandsapp.github.io/SafeHands/', 'Nizam Muhammad', 'Aparna Prathi', 'Patchipulusu Madhuri', 'Srinivas Adabala', 'Mounika Yerramsetty', 'Anjaneya Chari Maroju', 'vikram reddy', 'Mounika Yerramsetty'] | [] | ['distancematrixai', 'fontawesome', 'google-maps', 'multichannelwebbots', 'pega8.4', 'pegacdh', 'pegamobile'] | 9 |
9,937 | https://devpost.com/software/isearch-search-anything-anytime-anywhere | Inspiration
Search feature has always been a tough and debatable topic in terms of results accuracy and performance. Every application team generally ends up having their own flavor of searching and a lot of rework is encountered due to absence of a standard pattern/framework. Due to increased work and data transactions during COVID, or otherwise also, providing a search framework will save lot of development time/cost to build one and benefit application users to speed up their work thereby adding lot of value
What it does
'iSearch - Search anything, anytime, anywhere' is a search portal which can be used to search any content. User has options to choose the source and search type (light weight, heavy weight). User must type in a fragment of search text and click on a search button to get results. For Pega applications which have a non-Pega front end, iSearch comes with a simple REST API to do the searches. Eg. In a change management tool, a user could remember only a release name or a release manager's name vaguely and not the complete ID and other details. They could key in whatever info they know and get list of all matching releases in the result set.
Key features of iSearch framework:
Leverages Pega’s elastic search features to efficiently search all tables with string fragment
Provides UI to search contents
Provides REST API to search contents
Can be easily deployed and embedded in any Pega application (encouraging modular architecture)
Cuts across all business (healthcare, finance, insurance, etc) where work and data transactions are involved
Provided with two flavors – Standalone search portal and search component embedded in OOTB user portal
How we built it
Created multiple data sources to demonstrate search
UI screen to take user input and show results
A configurable report definition rule and calling pxRetrieveSearchData activity to trigger elastic search engine in v8.4
Configure all search parameters before invoking search engine
Consolidate results to show on the screen
Created a simple REST API to fire the search engine as another flavor
Challenges we ran into
FTSIncrementalIndexer Queue Processor was shut of due to stream errors and indexing wasn’t happening. Had to raise a Pega SR and get it sorted out on community edition
Showcasing result data from multiple sources (Pega tables) on the same screen as every source structure was different
Accomplishments that we're proud of
Coming up with a reusable search engine which can fit in any Pega project of any business vertical
Providing a wild card search feature where in user can search anything/everything
What we learned
How search engine works
How best the search engine could be interfaced with minimal configurations
What's next for iSearch - Search Anything, Anytime, Anywhere!
Admin portal to perform configurations directly on the app
The search portal can be given to non-pega UI as a json component to embed, using v8.4 UI APIs
Built With
pega
Try it out
bnyfeofs.pegace.net | iSearch - Search Anything, Anytime, Anywhere! | 'iSearch - Search anything, anytime, anywhere' is a search portal which can be used to search any content. | ['Bhargavi lakshmi', 'Manoj Rattihalli', 'Kshiroda Nayak', 'Prashant Daniel', 'Prathyusha Julapalli', 'pavan kumar'] | [] | ['pega'] | 10 |
9,937 | https://devpost.com/software/covidscan-an-pega-based-radiology-tool-for-covid-19-pandemic | Fig. 1: Map of Covid19 cases around the world (as of 4/30/2020)
Fig 2: Current chest X-ray diagnosis vs. noval process with CovidScan.ai
Fig. 3: Chart of wait-time reduction of AI radiology tool (data from a simulation stud reported in Mauro et al., 2019).
Fig. 4: Process of CovidScan development
Inspiration
What will be working situation for medical staff in hospitals during and after the COVID-19 pandemic? How can the medical staff quickly and securely log in and perform PPE safety check while dealing with a huge influx of patients in critical conditions? How can we automate the process of COVID-19 diagnosis so precious time can be saved for both medical doctors and the patients? How can our solution for hospital later be scaled and implemented to be a essential tool for automating the daily operation at hospital even after the COVID-19 pandemics is over?
To answer these core questions, we did some background research to identify the main challenges in order to develop the best solutions around those:
COVID-19 Pandemic:
Fig. 1: Map of Covid19 cases around the world (as of 4/30/2020). Our team created the map based on data collected by the Johns Hopkins University Center for Systems Science and Engineering.
As we see from the map above and the pie chart below, COVID-19, previously known as the novel Coronavirus, has killed more than 63,860 people and infected over 1,067,061 people in the United States alone, topping all other countries around the world. This number is continuing to grow every day.
Fig. 2: Top 10 countries with most COVID-19 deaths.
The main problem occur in the healthcare system during the pandemics is the long wait time for COVID-19 chest X-ray result:**
Fig 3: Current chest X-ray diagnosis vs. novel process with CovidScan.ai
Patients can first be screened for flu-like symptoms using nasal swap to confirm their COVID-19 status. After 14 days of quarantine for confirmed cases, the hospital draws the patient’s blood and takes the patient’s chest X-ray. Chest X-ray is a golden standard for physicians and radiologists to check for the infection caused by the virus. An x-ray imaging will allow your doctor to see your lungs, heart and blood vessels to help determine if you have pneumonia. When interpreting the x-ray, the radiologist will look for white spots in the lungs (called infiltrates) that identify an infection. This exam, together with other vital signs such as temperature, or flu-like symptoms, will also help doctors determine whether a patient is infected with COVID-19 or other pneumonia-related diseases. The standard procedure of pneumonia diagnosis involves a radiologist reviewing chest x-ray images and send the result report to a patient’s primary care physician (PCP), who then will discuss the results with the patient.
_Fig 4: Chart of wait-time reduction of AI radiology tool (data from a simulation stud reported in Mauro et al., 2019). _
A survey by the University of Michigan shows that patients usually expect the result came back after 2-3 days a chest X-ray test for pneumonia. (Crist, 2017) However, the average wait time for the patients is 11 days (2 weeks). This long delay happens because radiologists usually need at least 20 minutes to review the X-ray while the number of images keeps stacking up after each operation day of the clinic. New research has found that an artificial intelligence (AI) radiology platform such as our CovidScan.ai can dramatically reduce the patient’s wait time significantly, cutting the average delay from 11 days to less than 3 days for abnormal radiographs with critical findings. (Mauro et al., 2019) With this wait-tine reduction, patients I critical cases will receive their results faster, and receive appropriate care sooner.
What it does
Using the power of pretrained machine learning models from open source, CovidScan.ai is created as a full-scaled AI tool for radiology clinics and hospitals. It can automate the process of detecting sign of COVID-19 and pneumonia on chest X-ray images to assist radiologists during the pandemics. This tool of cutting edge technology can be used to reduce the workload for clinicians, and speed up patients’ wait time for pneumonia lab results in this critical time of the COVID-19 pandemic.
In summary, a patient who need COVID-19 testing will go through the following process using our application:
A user answers a series of questions using an algorithm built to identify whether they need additional screening or not.
If they need additional screening/X-Ray then we proceed to use their postal code to geo-locate the nearest hospitals with testing available
Once the case reaches at that point, the user just waits and it advances to a physician’s worklist
The physician opens the case and looks through the information and uploads X-ray images to identify whether the patient tests positive for pneumonia
The process of sending out for an X-Ray and getting them back are excluded from this application. The X-Rays could also be part of the patient’s existing medical records which could easily be located by the hospital’s system
Benefit of COVIDSCAN APP:
Using this application, the medical staff take patients’ chest X-ray images using the specialized machine and then upload the taken images to the database of web-app for testing for sign of COVID-19 infection or bacterial pneumonia.
It is due to the fact that an AI system can review, highlight the pneumonia sign and classify each X-ray image all in less than 10 seconds (comparing the radiologist’s 20 minutes that we mentioned earlier), and it can do that same task effortlessly for 24 hours without taking a break. This time cut is especially critical in the time amid the pandemic of COVID-19. With this spreading rate, it will be overwhelming for radiologists to review a massive number of chest X-ray images of potential COVID-19 infected patients. With the assistance of CovidScan.ai, it can automatically highlight the suspected signs of pneumonia for the radiologists and speed up the process of chest X-ray review. Therefore, more COVID-19 positive-tested patients will get their result back faster and receive appropriate care sooner to prevent the spread of the virus.
How we built it
Pega intergration:
We create a functional solution that incorporates the chest X-ray image detection model into Pega workflow. Platform used is Pega 8.2 and the application is scalable to different diagnosis and future disease recognition as CovidScan expands. Workflow was designed using Pega’s out of the box App creation and case management without any customization. The integration to the REST API’ was done by using the pega connectors. Due to the limited time, we have simulated the input and output for the hackathon.
Chest X-ray Classification Model:
For the deep learning model, we developed a Pytorch model. This project’s goal is to draw class activation heatmaps on suspected signs of pneumonia and then classify chest x-ray images as “Pneumonia” or “Normal”. For this project, we are going to use a dataset available at Kaggle consisting of 5433 training data points, 624 validation data points and 16 test data points. C. For the model, we load the pre-trained Resnet-152 available from Torchvision for transfer learning. ResNet-152 provides the state-of-art feature extraction since it is trained on a big dataset of ImageNet. ResNet-152, as the name sounds, consists of 152 convolutional layers. Due to its very deep network, the layers are arranged in a series of Residual blocks. These Residual blocks skip connections to help prevent the vanishing gradients which are a common problem with networks with deep architecture like ours. Resnet also supports Global Average Pooling Layer which is essential for our attention layer later on. For the attention layer to draw the heatmap, we use the global average pooling layer proposed in Zhou et al. Global average pooling layer explicitly enables the convolutional neural network (CNN) to have remarkable localization ability. We achieve 97% accuracy on the training dataset and 80% on the testing dataset.
Technical Requirements:
The packages required for this project are as follows:
Pega 8.3
Pega workflow
Torch (torch.nn, torch.optim, torchvision, torchvision.transforms)
Django
Numpy
Matplotlib
Scipy
PIL
Tensorflow
jQuery
Challenges we ran into
This hackathon project was a very different experience for us which challenged us throughout this project in the Pega intergration and deep learning model training part. This is the first time we all were working with creating endpoints of the pre-trained deep learning model to intergrate to Pega workflow.
Accomplishments that we're proud of
We manage to finish the project in such a limited time of 2 weeks in our free time from school and work. We still keep striving to submit on time while learning and developing at the same time. We are really satisfied and proud of our final product for the hackathon.
What we learned
Through this project, we learn to deploy a complicated image-recognition deep learning models on Pega platform. We also learn the process of developing a mini data science project from finding dataset to training the deep learning model and finally deploy & integrate it into a web-app. This project can’t be done without the efforts and collaboration from a team with such diverse backgrounds in technical skills.
What's next for CovidScan:
In the next 2 months, our plan is:
We will raise fund to invest more into the R&D process.
We will partner with research lab to collect more dataset and find hospitals to test our solution. One of our memeber has published his newly collected dataset on this open-source github:
https://github.com/nihalnihalani/COVID19-Detection-using-X-ray-images-/
Regarding our R&D, we plan on improving the performance of the platform, preferably by reading more scientific literature on state-of-art deep learning models implemented for radiology.
We also plan to add the bound box around the suspected area of infection on top of the heatmap to make the output image more interpretable for the radiologists. We are working to implament the multilabeling model of COVID-CXR on our dataset to improve our application. This model is published by The Artificial Intelligence Research and Innovation Lab at the City of London's Information Technology Services division and has accuracy 0.92, precision 0.5, recall 0.875, auc 0.96.
In many pieces of literature, they mentioned developing the NLP model on radiology report with other structured variables such as age, race, gender, temperature... and integrating it with the computer vision model of chest X-ray to give the expert radiologist’s level of diagnosis. (Irvin et al., 2019; Mauro et al., 2019) We may try to implement that as we move further with the project in the future.
With the improved results, we will publish these findings and methodologies in a user-interface journal so that it can be reviewed by expert computer scientists and radiologists in the field.
Eventually, we will expand our classes to include more pneumonia-related diseases such as atelectasis, cardiomegaly, effusion, infiltration, etc. so that this platform can be widely used by the radiologists for general diagnosis even after the COVID-19 pandemics is over. Our end goal is to make this tool a scalable that can be used in all the radiology clinic across the globe, even in the rural area with limited access to the internet like those in Southeast Asia or Africa.
References:
Crist, C. (2017, November 30). Radiologists want patients to get test results faster. Retrieved from
https://www.reuters.com/article/us-radiology-results-timeliness/radiologists-want-patients-to-get-test-results-faster-idUSKBN1DH2R6
Irvin, Jeremy & Rajpurkar, Pranav & Ko, Michael & Yu, Yifan & Ciurea-Ilcus, Silviana & Chute, Chris & Marklund, Henrik & Haghgoo, Behzad & Ball, Robyn & Shpanskaya, Katie & Seekins, Jayne & Mong, David & Halabi, Safwan & Sandberg, Jesse & Jones, Ricky & Larson, David & Langlotz, Curtis & Patel, Bhavik & Lungren, Matthew & Ng, Andrew. (2019). CheXpert: A Large Chest Radiograph Dataset with Uncertainty Labels and Expert Comparison.
Kent, J. (2019, September 30). Artificial Intelligence System Analyzes Chest X-Rays in 10 Seconds. Retrieved from
https://healthitanalytics.com/news/artificial-intelligence-system-analyzes-chest-x-rays-in-10-seconds
Lambert, J. (2020, March 11). What WHO calling the coronavirus outbreak a pandemic means. Retrieved from
https://www.sciencenews.org/article/coronavirus-outbreak-who-pandemic
Mauro Annarumma, Samuel J. Withey, Robert J. Bakewell, Emanuele Pesce, Vicky Goh, Giovanni Montana. (2019). Automated Triaging of Adult Chest Radiographs with Deep Artificial Neural Networks. Radiology; 180921 DOI: 10.1148/radiol.2018180921
Wang, L., & Wong, A. (2020, March 30). COVID-Net: A Tailored Deep Convolutional Neural Network Design for Detection of COVID-19 Cases from Chest Radiography Images. Retrieved from
https://arxiv.org/abs/2003.09871
Built With
matplotlib
numpy
pega
pil
pytorch1.0.1
torchvision0.2.2
Try it out
github.com | COVIDSCAN-A Rules Cube Pega framework For COVID19 Detection | A Rules Cube Pega accelerator framework powered by CovidScan.ai. This application is developed to be a secured AI platform with the purpose to assist radiologists with accurate COVID19 dectection. | ['Zishan Ali Khan', 'Ashish Pundir', 'Vi Ly'] | [] | ['matplotlib', 'numpy', 'pega', 'pil', 'pytorch1.0.1', 'torchvision0.2.2'] | 11 |
9,937 | https://devpost.com/software/job-portal | Inspiration: People
What it does: Job Portal
How I built it: Pega, NLP, Descising
Challenges I ran into: Ideas which can help people
Accomplishments that I'm proud of: Idea
What I learned: Sharing
What's next for Job Portal:
Plan is build for IT first and can be extended later for non IT sector as well.
Built With
decisioning
natural-language-processing
pega | Job Portal | Create a portal for jobs, people losing jobs due to Corona and other reasons, Notify Candidates with what they can learn extra inline with their current skill set + what is trending in market. | ['Gouri Shankar Korivi'] | [] | ['decisioning', 'natural-language-processing', 'pega'] | 12 |
9,937 | https://devpost.com/software/foodbeez | Mobile app QR
Home screen
Creating an order
Give order details
Can order for friends also using Add my buddy button
Adding buddies
Buddies
Added buddies
Menu list
Adding order items
Payment mode
Cashier Work queue
New items to be acted upon by cashiers
Approval of order by cashier
Confirming preparation of order by cashier
Server Work queue
Server updates the delivery details
Server updates the delivery details
Delivered items list
Manager can schedule dine time by filling necessary details
User log in page
About me screen
Menu list page
About me screen
About me screen
More Menu and log off
Home screen in large screen devices
Menu navigation
Menu screen in large screen devices
Configuraiton of tables by manager in large screen devices
Scheduling dine time screen by manager in large screen devices
About me in large screen devices
Delivered screen in large screen devices
Offers announcements and dine time screen in large screen devices
Example of table to be updated by manager in large screen devices
Inspired
It is a well known fact that we are terribly suffering from COVID 19.
And we won’t be able to stay at home forever.
We would need to go to office.
But, what happens if the virus still prevails?
What are we going to do ensure social distancing in work spaces?
These are answered by our Foodbeez.
Learnt
Learning was an inherent process during this app development. Learnt about creating
an app from scratch.
Came to know about more functionalities and capabilities of Pega.
How was it built
Pega 8.4 edition was used to build the application.
Mobile channel is used to build mobile app which can be experienced through Pega Mobile Preview.
Challenges faced
Making the application compatible with various types of devices was quite difficult.
Everytime testing has be done for all types of devices.
To try
Use these:
foodbeezuser- Buddy7@9
foodbeezserver- Buddy7@9
foodbeezcashier- Buddy7@9
foodbeezmanager- Buddy7@9
Three links are given:
Complete app package exported from PEGA. Can be imported in PEGA and run.
Pega mobile preview link. QR code is also given in images for easy accees.
A presentation which details the use case and contains demo steps for using the app.
Built With
cosmos
pega
Try it out
drive.google.com
qsr395la.pegace.net
drive.google.com | Foodbeez | Your's best buddy | ['Anto Sharon Prakash'] | [] | ['cosmos', 'pega'] | 13 |
9,937 | https://devpost.com/software/i-for-you-every-help-matters | Home Page
Request Confirmation
I offer help - location search
Selecting location
Results page
Request details
Activity Page with message
Email Notification
Mobile App Notification
I For You Logo
Inspiration
"
I For You
" was inspired by the heartwarming community responses to the COVID-19 pandemic seen across the globe. In particular, thousands of mutual aid Facebook/ Whatsapp groups have popped up, filled with posts from those offering and requesting help from their local community.
However, these groups have a big problem. If you wish to offer help, it's unlikely that the person who needs it most will find your post.
"
I For You
" aims to remove the friction in connecting those who are willing to help with those who need it.
What it does
"
I For You
" is on a mission to help the vulnerable amongst us get support during the current pandemic.
Put simply, "
I For You
" connect those in your locality who are willing to help with those who need it.
Select "I need help" if you are looking for help.
Fill in the form and submit request.
You will be notified via email and push notification, when a volunteer wants to help you.
If you offer help -
Search for your location
Go through all the requests and select the request you can help.
Have a conversation with the help seeker and fulfill the request.
How I built it
Pega platform - mobile capability
Google Places REST APIs
Gmail Integration
Challenges I ran into
A key challenge was to define a minimal feature set that would deliver real value to the community. My goal was to minimise the time to people so that "
I For You
" was able to help people suffering due to the coronavirus lockdown measures as quickly as possible. To this end, I focused on connecting those who need help with those who offer it via email, allowing the subsequent conversation between parties to take place over existing and well-established communication channels.
An additional challenge was to ensure the UX was as intuitive, beautiful and simply designed as possible, so that "
I For You
" application was accessible to a wide range of user demographics. This allows the project to have a positive impact on as many people as possible.
Accomplishments that I'm proud of
I am able to build a production-ready application over the course of 2 weeks which is already having a significant positive impact on many people's lives during this crisis. I am proud to be able to use my skills and Pega platform to help the most vulnerable in our society during this time of need.
What I learned
This project was an excellent lesson in:
Identifying the critical problem that needs to addressed.
The importance of deeply understanding the problem you wish to solve.
Defining a minimal yet sufficient feature set to address this problem.
The importance of quality UX design.
Development of a production-ready mobile app.
Efficient usage of Pega for seamless conversations between two parties.
What's next for "
I For You
"
I will continue to enhance this application to add new features. Planned features include:
Provision for volunteers to publish their willingness to support people in need as per their availability.
Allowing people in need to contact volunteers available to support at that point of time.
Feedback, rating feature to gain more hearts(similar to bonus points).
Reporting feature - if someone abuses/ misuses "
I For You
" platform.
Post tag filters.
Map view.
AI-assisted reporting and spam filters.
Support for additional communication platforms, e.g. Facebook Messenger.
Vetting process when a user registers.
Built With
api
gmail
gmail-integration
google-places
mobile
mobile-app
pega
rest
Try it out
github.com | I For You.. Every Help Matters! | I For U is on a mission to help the vulnerable amongst us to get support during the current pandemic. I For U uses Pega to connect people in your area who are willing to help with those, who need it. | [] | [] | ['api', 'gmail', 'gmail-integration', 'google-places', 'mobile', 'mobile-app', 'pega', 'rest'] | 14 |
9,937 | https://devpost.com/software/appointment-management-framework | Inspiration
In the post Covid-19 world, customers and organisations would surely want to go contact-less. To make any appointment and then go through the process, we need to come in contact with a lot of people and interact with them both physically and over phone. The entire journey of setting up and going through any meeting/appointment requires a lot of human controlled steps and uncertainty. But, we as a team thought, why don't make the process seamless, intelligent, guided and contact-less at the same time only through one single app. Doesn't that sound wow ? Yes, our Appointment Management Framework caters to this issue and addresses the problem of multiple human contacts and delays in going through any process like Doctor's appointment, Airport Checkin and Boarding, Restaurant Table Booking, any Office Appointment, Medical Test Appointment, visiting your Auto-Mobile dealer etc.
What it does
We have built a Framework application that helps in a guided appointment execution process for any individual. This generic framework contains generic and reusable rules which can be extended easily to any industry for the guided appointment process. Also, any organisation can extend its existing end-user-facing Pega application to include this framework e.g. any Bank can include this feature in its existing app and provide a seamless experience to its customers each time they decide to visit the Bank branch. The salient features of this framework are -
Book a new appointment easily through Web/mobile channels . Show available time slots while booking.
get reminders on the day of the appointment,
automatic notification in case of possible delay to adjust the plan accordingly for both customer and service personnel,
once reaching the destination, customer can enter the premises by scanning the QR code that is generated in the mobile app ensuring contact-less entrance to the premise,
customer gets follow up notification/instructions for next steps through the mobile app
automatically gets assigned a pre-allocated seat ensuring social-distancing and no queue/waiting
flexibility for the service personnel to start the meeting and notify the waiting customer
adding value to the discussion by providing Pega enabled AI input based on customer data and previous interactions
gets guided in the entire process so that the experience is entirely friction less.
As a sample implementation layer, we have built "U+ Hospital OPD Management" app in which the user goes through a similar seamless experience as explained above for a doctor's appointment process. The app is also AI powered - it provides diagnostic test recommendations based on a customer's past records like whether he/she has been in contact with a covid patient, age, sex, past medicine usage and tests taken etc.. The application can be used by both patient and doctor. Patients can book/reschedule/cancel the appointment through mobile app using the 24x7 chat bot or manual registration in web channel and then go through the entire process guided by that app. The doctor through his/her web portal can see the list of upcoming patients for the day, authenticate the patient, write & upload the prescription and complete each case. The patient in turn gets the notification in his/her app, gets notified regarding medicine buying and undergoing further diagnostic test options if any and then a guided exit. This way our application is ensuring a smooth, contactless, hassle-free journey for both the patient as well as the doctor involved in the appointment process. Both web and mobile versions of the application have been built.
How we built it
The Appointment Management Framework has been built in Pega 8.3 version. First the framework layer has been built where we have given all the case types/stages of a generic appointment booking like registration, guided entry, guided execution and exit. Then the same has been inherited in the implementation layer where we have built it specifically for the "U+ Hospital OPD Management" showcasing the contact-less journey of a patient and doctor in the appointment and execution process. Pega Mobile client was used to build the mobile app for helping the patient throughout the journey. Pega Chatbot has been utilized to help the customer with any help 24x7 like like booking registration, checking doctor availability etc.
Challenges we ran into
Getting the Pega Mobile Client up and running in 2-3 days was a real challenge
Making the QR Code scan work was another tough thing we faced
Accomplishments that we're proud of
The Patient can do the entire appointment booking process through the Chat Bot itself through constant guidance.
In case there is a delay in the process due to previous patients in the appointment list and hence the patient should start 30 mins late for the OPD compared to the previous scheduled time, the same is informed to the customer real time through push notification in our application. This helps the patient adjust his/her start time and in the process saves time and avoids churn or frustration in waiting time.
Adding intelligence to the discussion process by using Pega AI adaptive model suggestions.
Value proposition of the application -
Helps to meet "new normal" expectations in post-covid era
Opex savings by reducing human intervention in the entire process
Customer satisfaction by ensuring hassle-free and automatic process
Preventing customer churn by minimizing delay, removing queue/waiting time and adding AI enabled intelligence
What we learned
Using the application of QR Code scanning and progressing with the case automatically.
Using AI in Pega to offer propositions based on customer's data or past behavior.
What's next for Appointment Management Framework
We can strengthen the AI strategy and make the models more robust by offering discounts on medicines to be bought or tests to be taken. Also we can use customer propensity towards the offers for balancing customer needs and business benefits. We can also add a marketing framework such as Pega marketing to improve the Offer proposition process.
Improvising the web chat bot to display search results based on Pega geo-location
The look and feel of the application can be strengthened to make it more appealing to end users. The responsive UI for the mobile client has scopes of betterment.
The "medication details" is currently hard coded, in future it will be shown automatically based on what the doctor prescribed.
Built With
pega
Try it out
github.com | Appointment Management Framework | This is a framework to automate and manage the entire appointment process for any organisation ensuring zero-contact, queue-less process as well as adding intelligence data to help the discussion. | ['Saroj Roy', 'Sayantan Chowdhury', 'Ankit Gupta', 'Bhaskar Chatterjee', 'Anabadya Neogi'] | [] | ['pega'] | 15 |
9,937 | https://devpost.com/software/rule-not-found | Capture Customer Details
Capture Customer Information
Voucher Report
Questionnaire
Inventory Location
Store Location
Sponsor Reconciliation Report
Bar Code Generation
Inspiration
Due to spread of covid-19 and economic shutdown, most vulnerable families are hardest hit in our communities
Some people are forced to make impossible choice between food, rent or medical attention
People are facing financial burden as well unable to find essential items like Milk, Water, Tissue Paper, Face Masks, Wipes, Gloves etc. (most items are out of stock)
Pega Hackathon gave us an opportunity to do something for the community using this implementation.
What it does
This application helps in connecting sponsors with people who are looking for financial assistance.
Manually Identify Sponsors and update data table
Go Fund Me and Facebook API
Provides real-time inventory details
Product lookup API
Supports local businesses
Google Map API to find nearby participating stores
Supports individuals in financial crisis
Issue electronic gift card based on individual requirements
How we built it
We want to showcase PEGA 8.3/8.4 features using PEGA cloud version to build this application.
Google Maps integration
Bar Code Generation
Outlook Integration
Decisioning
Dynamic Questionnaire
Savable Data page
Score Cards
REST API
Supports range of mobile devices
Reconciliation Reports
Challenges we ran into
Convincing Local Businesses to join and support this initiative
Real-time inventory from local businesses
Acquiring Funds
Accomplishments that we're proud of
Here are the list of features we accomplished:
Provide list of items and quantity from preferred stores
Create scorecard based on the questionnaire
Scorecard drives the decision logic to approve financial assistance
Generate bar code based on approvals
Generate and send email to the recipient based on approvals
Fund tracking via audit log – sponsor to needy people
Funds Reconciliation Report
Sponsor's Dashboard Report
What we learned
Design thinking
Brainstorming sessions for Hackathon Idea generation
Covid-19 impact on local businesses
Networking and Collaboration
Research on GoFundMe, Google and Facebook APIs
Research on real-time inventory of local businesses
What's next for #DialHelp
Track Finances
Real time essential items availability and quantity based on Zip Code
Dedicated Help line number
Integration with GoFundMe and Facebook
Seamless Integration with local businesses
Increase reach – NGOs, Old Age Homes
Tagline: Get Connected Anytime, Anywhere. Contact Us for Help.
Built With
cosmos
open-services
pega
Try it out
drive.google.com | Dial Help (Dial 4357) | Essential items for customers in the natural disaster area | ['Srini Bhupathiraju', 'Tulshi Ram Bhakar', 'Gaurav Gupta', 'Soumyajit Surai', 'Soumen Maji', 'Deepak Deshmukh', 'pritam mondal', 'Chandan Tamada', 'Manish Jindal'] | [] | ['cosmos', 'open-services', 'pega'] | 16 |
9,937 | https://devpost.com/software/release-verifier | Cover Page
Intro Slide
Landing Page 1
Input Data (.csv)
Upload Process
Comparison Report
Release Articatct - Export to Excel
Inspiration During the software development life cycle (SDLC) development teams need to migrate code between environments up to Production/LIVE on regular intervals and in agility methodology its goes like every month new changes in market. During the releases App Dev & support teams spend lot of time to validate the code deployed.
What it does Tool minimize the efforts needed and also reduce the human errors during environment validation post code migration across pipelines or in LIVE/Production. Load all rules by using PZInsKey for versioned and un-versioned rules like RS, RSV, DSS, DI, Data Tables, Application, Access Groups etc with have PZINSKEY and xml to view. Compare existence of rules and RSV in destination environment.
How we built it Using existing libraries in Pega
Challenges we ran into
Accomplishments that we're proud of Improve efficiency and turnaround time is reduced by 80-90%. Implemented across all Pega applications within Bank of America.
What we learned, this tool saved lot of time during the major releases and also works in PEGA 7.1.8 through 8.3.2.
What's next for Release Verifier Patent Pending
Built With
libraries
pega
uikit | Release Verifier | Automation of deployment validation | ['Pavan Paruchuri', 'Wendy Lyman', 'ANKUSH TEWARI'] | [] | ['libraries', 'pega', 'uikit'] | 17 |
9,937 | https://devpost.com/software/vaccination-management-system | Cover page: An overview of our solution
An overview of the journeys covered in our solution.
A high-level description of how the various modules work together.
An overview of the target operating model
A description of why we chose to use blockchain with an example from the ethereum console.
Problems solved part-1
Problems solved part-2
Application Architecture
Features from the four modules
An overview of the data model
README: TEST USER LOGIN
Inspiration
In the wake of the current Covid-19 pandemic, Harvard Business recently published an article titled, “Why Big Pharma is betting on Blockchain”. As hospitals and health centers around the world struggle with shortages of equipment and are faced with the overwhelming task of hopefully vaccinating a majority of the citizens in the coming years, they need a solution that can provide authenticity, transparency, and traceability. The Vaccination Management System is built to provide exactly that. We decided to combine blockchain with Pega’s intelligent automation capabilities and layer cake architecture, to build an end to end solution wherein the procurement, distribution, and administration of vaccines can be done more safely and efficiently.
What it does
The Vaccination Management System, is a scalable solution allowing for the supply administration, procurement, and ultimately administering of, vaccines to citizens.
Our solution focuses on four micro-journeys. Product catalogue management, procurement, distribution, and vaccination administration. These journeys work together to create reliable and transparent end-to-end vaccination management.
The product management journey focuses on the relationship between supplier and healthcare center. As healthcare centers experience demand, this journey supports the bidding process for a necessary vaccine. Herein, a healthcare worker can request information regarding a specific vaccine. The healthcare worker is intelligently supported by the system which pulls up related products when needed to ensure the safe transport of those vaccines. The suppliers can respond to the specific questions and submit them back to the healthcare centers who then arrange a contract with the supplier. This process leads to transparency in the relationship between supplier and healthcare center.
The procurement journey is responsible for then procuring the vaccines from the supplier and ensuring they are distributed to the correct warehouse. This journey provides insight into the current stock, demand, and past usage trends of the vaccine. This is where blockchain comes in. By integrating Pega with Ethereum Blockchain with Pega’s blockchain starter kit, we ensured that the usage data of the vaccine was stored and retrieved from a distributed ledger. By utilizing blockchain, we can ensure the suppliers and healthcare centers all work from a shared, permanent ledger which leads to product authenticity, a reduction in friction, and the ability to expose fraud in the supply chain process. Any suspicious activity around the data is flagged, and permanently recorded on the ledger.
The distribution journey gives the control to the central health authority to assess demand for a certain vaccine in a particular area based on epidemiological urgency. The central health authority is able to assess demographic data and determine how, when, and where vaccines should be administered. Again here, by leveraging blockchain, we enable more granular visibility into the current inventory of necessary vaccines.
Finally, the vaccination administration process enables health workers who then administer the vaccines. The system automatically distributes “citizen-appointments” to the chosen vaccinator team. Per citizen appointment, the citizen receives an email with their appointment, and confirms their appointment afterwards with the health worker.
How we built it
The process of building this solution was truly a team effort. By following the scrum framework, we were able to stay aligned through daily stand-ups, planning sessions, refinements, and reviews at the end of our weekly sprints.
We started by preparing a complete backlog and prioritizing the backlog stories. To create the customer journeys, we did a lot of research. Many online medical journals and articles published on WHO’s official website helped us to brainstorm an advanced yet realistic solution.
One of our aim was to build the solution in a completely componentized, modular architecture. We started off by creating separate small applications for different functional modules. We chose to use the Cosmos and Clarity UI design themes as applicable in different portals.
During our research for a viable solution, we were convinced of the importance of blockchain in this use case. So we leveraged Pega’s blockchain starter kit to integrate Pega with Ethereum. Currently we have used blockchain for two functionalities: tracking vaccine supply to assess demand and confirming vaccine delivery to ensure transparency. In future this can be extended to other modules as well.
Another important design choice was to use a separate data layer for system of records. Wherever we used Pega as a system of records, we did it in a subclass of .. -Data-SOR. And then another data layer which is referred in UI and business logic. So for a business function XXX, we have class ABC-VMS-Data-XXX and data type ABC-VMS-Data-SOR-XXX. All UIs and business use the former. And data pages abstract the later from the former. So, in future any SOR can be replaced by a different data source simply by modifying these data pages without having to modify application UI or business logic.
Lastly, we built a heatmap to have an overview into which geographical area has most people vaccinated and which area needs more attention. We used Google map in our Pega application to achieve this.
Challenges we ran into
There were certainly challenges we ran into throughout the last few weeks. Integrating with Ethereum was something nobody in our team had any experience with and it was certainly a challenge to finally get it to work. Additionally, our team varied widely in terms of experience. While we had 4 LSA’s on our team, they were all very busy with other projects and therefore a large responsibility fell to our two CSSA’s and two new CSA’s for whom this was their first project.
Additionally, one of the challenges we foresee of utilizing blockchain is the necessity of broader implementation across manufacturers and suppliers. The ability to use blockchain is quite simple once a barcode is provided, however the technology to support the supply chain must be configured to also update the distributed ledger throughout the process so that the data stays reliable.
Accomplishments that we're proud of
We are very proud of the solution we built in how we hope it can contribute to society. We tried to build our solution as flexible and scalable as possible, allowing for implementation for an individual health care center or a wider implementation through a governmental agency. We are proud that we could use our experience to build a solution that could benefit humanity and contribute to a better tomorrow.
We are also proud of how we worked together as a team to utilize everyone’s strengths in building the solution. It was a team effort and a great learning experience for all of us.
What we learned
What we learned is the enormous complexity surrounding the vaccine distribution processes. There are very strict regulations in some countries, whereas others have very few regulations. Creating a platform that supports across countries, cultures and regions is quite challenging.
What's next for Vaccination Management System
There is quite some complexity not accounted for in our journeys. However, we believe this is only a starting point. By providing this solution, or aspects of this solution, as a framework, we took the first step to make the vaccination management system more intelligent and efficient. In future we can plugin reusable components into the solution to replace few of the Pega SORs and instead integrate with a different data source.
We would also like to eventually implement a track and trace system, enabled through a barcode to better leverage the benefits of blockchain. Additionally, a contact center would give additional support for citizens who want to report a problem or schedule their own appointment.
Friendly regards,
Pritam, Samya, Gökhan, Johny, Jowie, Osas, Christiaan, and Emily (The Pegavengers)
For any questions: please contact
[email protected]
Built With
blockchain
clarity
cosmos
ethereum
google-maps
pega
pegainfinity
solidity
Try it out
ns3079683.ip-217-182-134.eu | Vaccination Management System | Our solution leverages Pega with Blockchain, to build an end to end solution wherein the procurement, distribution, and administration of vaccines can be done more safely and efficiently. | ['Samya Ganguly', 'Gökhan Kuzu', 'Pritam Chakraborty', 'Jowie Sewnarain', 'Emily Wiemken', 'Johny Sheik', 'Osayuwamen Osaigbovo'] | [] | ['blockchain', 'clarity', 'cosmos', 'ethereum', 'google-maps', 'pega', 'pegainfinity', 'solidity'] | 18 |
9,937 | https://devpost.com/software/remotecontrol | Inspiration
What it does
RemoteControl is an automated task portal for the autonomous remote worker in the age of COVID-19.
How I built it
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for RemoteControl
Try it out
bitbucket.org | RemoteControl | RemoteControl is an automated task portal for the autonomous remote worker in the age of COVID-19. | ['Warp Smith'] | [] | [] | 19 |
9,937 | https://devpost.com/software/traceit-v9nmcj | Login for TraceIT
Onboarding of Patients
Reporting Capabilities
Inspiration
The current COVID-19 pandemic has put all the people under risk and has severely strained the Public Health Departments of all the countries. Case Investigation and Contact Tracing are core disease control method deployed by all Public Health Department.
What it does
Trace people with COVID 19 symptoms
Identify Community spread and keep Public Healthcare Department notified
Integrate with Hospitals / Testing Labs
Dashboards & Reports for all users of the application
How I built it
Using Pega Platform 8.3.0 with UI-Kit 14.01 with minimum customization.
Challenges I ran into
Figuring out a common work flow in a situation like Pandemic was found difficult. To have an organized work flow in chaos and panic world is challenging. But as we started, Pega made it easier.
Accomplishments that I'm proud of
We started off late and hence coming up with the build of this application in such a short span of time was something, we as a team, were happy about. It will be really helpful for Hospitals and Public Health Care Departments.
What's next for TraceIT
We will enhance the application further and make it a flexible, multi-purpose application.
Built With
pega
Try it out
github.com
m3pfowyk.pegace.net | TraceIT | To combat the Pandemic, the Healthcare Department needs an Intelligent, sophisticated application that co-ordinates with various Internal & 3rd party systems and ensures easy reporting. | ['Venkat Raj Gopal Ramanathan', 'Yashwanth C', 'Surya Narayanan Suresh', 'venkat kaza', 'Anjaneya Reddy Gurram', 'Subbarao Muthineni', 'Sathvik Desu'] | [] | ['pega'] | 20 |
9,937 | https://devpost.com/software/smart-content-engine | Select Template
Generated PDF
Review PDF
Master Table Configuration
Meta Configuration/Document properties
Inspiration
Below were the challenges faced which inspired us to build this framework:-
• To address the challenges in generating correspondence for individual or group of customers
• To address the challenges in personalization and customization of templates in email’s, and pdf’s
• To address the challenges in maintaining uniformed styling in various correspondence like Email, Post, etc.,
• To address the challenges in implementing customer-specific styling in Emails, Pdfs, etc.
• To cut-short the wait time in customization of content for the targeted audience
What it does
This Solution builds dynamic content on the fly and allows user to create a better individual experience that suits the reader and also allows the user to personalize fields, offers, contents or images on webpages, pdf’s, emails and all types of a correspondence using Smart content engine
How we built it
This solution is build using the PEGA OOTB rule engine and mostly using the Data type’s configurations. This mostly uses Data Tables configurations, declarative rules like data pages for caching, decision tables for run-time template generations.
Challenges we ran into
Building the dynamic solution with reusable components shared across multiple templates and documents was challenging. Styling based on customer user experience alongside configuring the document Metadata/properties was challenging.
Accomplishments that we're proud of
• Achieving the reusable components shared across different documents/template
• Making the smart content engine business user friendly so that business can configure the templates at run time without development changes. (Low code)
• Making the styling specific to templates/documents configurable by business users.
• Making the Metadata/properties like print format etc. specific to templates/documents configurable by business users.
What we learned
Pega OOTB capabilities could be used to build the frameworks which could be configured by business users for run time changes. And also we can build solutions that are low code (minimal) and requires no release.
What's next for
The next steps are to make this framework application as a component application which could be made available in PEGA market place as a ready to go product for building the run time templates and documents.
Built With
data-types
decision-rules
declarative-rules
pega | Smart Content Engine | Smart Content Engine is an Adaptive content builder that allows the user to personalize fields, offers, contents or images on webpages, pdf’s, emails, and all types of correspondences. | ['Vivek Sharma', 'Ashish Verma'] | [] | ['data-types', 'decision-rules', 'declarative-rules', 'pega'] | 21 |
9,937 | https://devpost.com/software/pega-upi-payments | 0
1
2
3
4
5
6
7
Inspiration
Developers to build UPI Transactions Apps in near-real-time.
What it does
With Pega Framework it enables the reusability of rules, Add UPI Transaction system to business flows. We save lot of time in building the apps with reusable rules
How we built it
We used Pega REST Connectors, Activities, HTML scripts to set up the UPI payment process for Paytm
Challenges we ran into
Security Key generation in Pega by importing JAR files
Configuring Callback parameters from the Javascript API response
Accomplishments that we're proud of
Complete flow of Paytm Initiate Transaction API to complete the simple payment process
Reusable UI elements using controls
HTML Script for Paytm Payment
What we learned
REST Connectors, Activities, HTML Scripts, UPI Integration through API, Control, Pega Rule Resolution
What's next for Pega UPI Payments
Bring in all the API for Paytm UPI transactions
Need to extend for other 3rd party UPI payments Applications
Integrate the code with official PRPC Engine
Built With
pega
upi
Try it out
github.com | Pega UPI Payments | A new Payment flavor in Pega Situation Layer Cake which satisfies UPI Payments Interface in business process | ['Karthee Periasamy', 'Dhanasekar Chellamuthu', 'MATTA CHANDRASHEKAR', 'Saravanan Selvamohan'] | [] | ['pega', 'upi'] | 22 |
9,937 | https://devpost.com/software/careteam-nlz5jc | Login Screen
Sign Up
Add New Request
View Request
List of Requests open for donation
Inspiration from the people who face a lot of crisis in resources and we decided to help them with our tech by creating an application to help and ask for help at any time.
This application is helpful in balancing the resources by sharing them among the needy.
This application is entirely built on the top of Pega Platform of version 8.2
The challenges in this application are making requests live and updating the status of request to both requestor and donor.
The accomplishments made in this application are handling live requests and fully customized Reports and harnesses in portals.
We have learned the customization of harness and configurations of activities.
We as a team will enhance the application and put forward our efforts to bring out new innovations.
Built With
pega
version8.2
Try it out
github.com | Freebie | This is an application for people to exchange resources and support during calamity and donors to make donations | ['keerthana ka', 'Maheswari Muralikumar', 'Shanmuga Surya', 'Rupa Ravulakollu', 'GIRUBA N', 'Mathumitha B M', 'DHAANYA N', 'Sandhya Muthukrishnan'] | [] | ['pega', 'version8.2'] | 23 |
9,937 | https://devpost.com/software/save-life-donate-blood | Inspiration
What it does
This application provides a one stop platform for Blood donors, recipients, Hospitals and NGOs.
Blood donors will be able to search the Hospitals or the Organizations which are running the blood donation drive and are near to the donor's location.
Recipients who are looking for the blood in case of any emergency, they can login to this application and search for the nearby blood banks or the donors.
A workflow system has been built for the donors which will keep track of the process and easy to maintain by both requestors(Donors) and Approvers(Hospitals)
How I built it
This application was built purely on the Pega Platform 8.4 Community Edition server enabled for the Hackathon using Cosmos Theme. Application has been configured to be accessible via Pega Mobile Channel(Pega Mobile App Viewer) as well apart from Web Browser. To get the user's current location, MapQuest GeoCoding API is used.
Challenges I ran into
Integrating with Pega Mashup.
Using the Search API for the Hospitals which can be used to get the list of Hospitals near the user's current location. Tried MapQuest Search API but it worked only if the user's location is within US. So, configured local data table to store the Data with the Hospital list present near the user's current location for the prototype.
Faced issue while integrating the Google Search API.
I currently work on Pega 7.1.8 version and building the App using Pega 8.4 version was really challenging. Even when Theme Cosmos UI was used. To understand the rules and usage it was little challenging.
Accomplishments that I'm proud of
Being able to participate in my first Pega Hackathon and to build a prototype within 2 weeks of time which is accessible as a Mobile App and Web Based Application. Even after working on older version of Pega, I was still able to use Pega 8.4 and able to develop a prototype in small time frame.
What I learned
Integration with Pega Mobile Channel
Usage of Theme Cosmos UI
What's next for Blood Bank Management System
It also needs to be enhanced for blood requisition workflow Process. Currently it will be able to search the list of Hospitals present for the requested Blood Group
It can be enhanced to integrate with different Systems and use real time data in order to make this application more effective for all kind of stakeholders involved during the blood donation and requisition process and can be used in Health care sector.
Shared the link of drive location with
[email protected]
Built With
mapquest-geocoding
pega | Blood Bank Management System | Pega based workflow System for blood donation and requisition | ['sneha agrawal'] | [] | ['mapquest-geocoding', 'pega'] | 24 |
9,937 | https://devpost.com/software/smart-pdf-page-mover | Splitter UI
Inspiration
The business problem we are trying to solve here is with splitting case attachments. Let's take a scenario where a user has to split a huge document attached to a case. Users would usually download the attachment from the case, then upload it into some third party software, split the document and then attach the smaller documents back to case. This process involves lot of effort and is time consuming.
What it does
Our PDF Page mover component provides an intuitive user friendly UI to split documents within the case, thus reducing the manual effort of using some other tool for the same purpose.
How we built it
Our component is built on Pega and PDF Box.
Challenges we ran into
Integrating PDF Box with pega
Writing generic code to work with attachments stored in different locations like DB, Repository
Accomplishments that we're proud of
Providing intuitive UI for business users
Potential time and effort savings for users
What we learned
Building components in Pega
Working with PDF Box API
What's next for Smart PDF Page Mover
Enable drag and drop functionality to select the pages to be split
Extend it to work on attachments in Repository
Built With
pdfbox
pega | Smart PDF Page Mover | An intuitive UI component helpful in splitting pdf documents attached to case | ['Hari Losari', 'Avinash Haridasu', 'Chethankumar Mahalingappa', 'Sudip Gupta'] | [] | ['pdfbox', 'pega'] | 25 |
9,937 | https://devpost.com/software/cross-bot-automation-for-customer-service | Cross-Bot Scenario
Cross-Bot Scenario Sequence Diagram
Change of Address Case Life Cycle
Inspiration
Current customers face lots of pressure to support their existing customer base via the call center due to Covid-19 situation.The call center agents were forced to work from home because of the lockdown and there were only a few of them able to support their customers as many went into quarantine. Hence, a quick automation solution was needed to increase operational efficiency and reduce CSR handling time.
Cross-Bot Automation for Customer Service
Pega Hackathon 2020 | Ai4Process Ltd | Cross-Bot for Customer Service with Chatbot and Emailbot
Value Proposition/Product Description
A quick (4 week production Go-Live) Out-of-box Pega solution to meet the automation needs for customer service by reducing the CSR handling time during the peak of omni-channel demand by more advanced digital customers. This solution not only considers the customer micro-journey but also helps the employee's journey by making the employee more productive in their work by focusing on real customer problems. Automation reduces the time for both the customer & employee journey, and also keeps both happy by giving them a 360 degree view of the customer interactions . Cross channel bots are a step ahead of omni-channel and help answer customer queries fast and aids retaining them in the organizations. This solution also helps with STP (Straight Through Processing) by Text Analysis, Machine Learning, OCR, pre-filled PDF generation, case management, all built in Pega and reducing the licence cost for third party components.
Objective
The objective of this product is to tackle new issues in our evolving world in terms of humanitarianism, economic relief and disaster recovery by improving access to
automated
services when normal human based services are adversely affected.
Benefits For Business
Supports remote working model for CSRs
Reduces the CSR workload by NLP processing
Conversation history is saved with the case instance
Benefits For Customers
Helps to reduce the call center wait time
Customers can access and log requests at anytime and from anywhere
What it does
The Customer – Kristina, has just moved house.
She goes to the AI4 Services webpage to inform them of her new address.
In the chat window she starts a conversation and then selects the change of address option.
The AI4 Services Pega chatbot receives the change of address message.
The Pega Chatbot then starts the change of address service process, which asks Kristina to enter her account number and then her new address.
The Chatbot then tells Christine to expect an email on her registered email address with further instructions to complete the process.
The Pega automated service process then generates a PDF form pre-filled with Kristina’s details including the new address and emails this to Kristina.
The email asks her to sign and return the form including a document as proof of her new address.
Kristina can either fill in the form and sign it electronically (if she has the capability) or she can print, fill, sign and scan the form and then email this back to Ai4 Services with a proof of address document also attached.
AI4 Services Pega email Bot receives Kristina’s email and uses OCR to read the scanned PDF attachment.
Text analysis and machine learning identifies the email as a response to an existing service case so it attaches the email to the case and routes an assignment to an agent work queue.
The CSR and managers can view a report of pending and completed Change of Address cases to manage the work load.
When Kristina’s email has been received the service case status changes from Pending-Response to Pending-Review.
The CSR Either picks the new case from the worklist, or receives the case when selecting the Get Most Urgent button.
The CSR reviews the data pre-populated in the case and checks the attachments sent by Kristina are in order.
The CSR can view the history of the interactions with the customer in the case audit and case narrative.
If the case is not in order, the CSR can use the suggested replies to email Kristina back for any further clarification.
The CSR authorises the change of address in the system records.
The process then sends Christina a confirmation email and the case is resolved.
Kristina receives the confirmation email as proof the change has been completed successfully.
The CSR returns to the report to view the current workload ( which shows Kristina’s case has been resolved) and views the Chatbot conversation that Kristina had for background information.
Video Links
Youtube channel Ai4Process consist of two video (usecase and real demo video)
Usecase Video (Animation)
Real Demo Video (Working example)
How we built it
We created micro journeys and implemented email bot first and enhanced it to chat bot along with the NLP (Ruta & ML)
after this we implemented pdf generation with the pre-filled values followed by integrating with OCR component
Challenges we ran into
Configuring Abbyy to read formatted complicated forms and scanned documents.
Initially the output of the OCR is un-formatted and we managed to retrieve formatted text by updating the abbyyTextExtractor parameters
Accomplishments that We're proud of
We have a generic solution which can be deployed to any customer within 4 weeks
What we learned
We Learned Pega capability around emaibots, chatbots, NLP, Machine Learning, PDF generation, OCR, etc
We are now capable of advising customers on Pega automation capabilities and are less dependent on 3rd party components which reduces the cost at customer side.
What's next for Cross-Bot Automation for customer service
Pushing Pega UI sections to the customer via chatbot
Handing over the chat conversation to the live agent
Integration with Docusign
Integration with Unified Messaging component
Built With
abbyyfrengine
chatbot
emaibot
linux
pega8.4.1
pegacrm8.4.1
postgresql
tomcat
Try it out
github.com | Cross-Bot Automation for customer service | Cross-Bot automation reduces CSR handling time & meets the excessive demand of digital customers. This increases the employee productivity & also serves customer journeys across omni channels. | ['Oliver Mason', 'Tharine Nagulendran', 'Amit Agrawal'] | [] | ['abbyyfrengine', 'chatbot', 'emaibot', 'linux', 'pega8.4.1', 'pegacrm8.4.1', 'postgresql', 'tomcat'] | 26 |
9,937 | https://devpost.com/software/digital-onboarding | Inspiration
We are currently facing unique challenges in the workplace because of the current pandemic situation.
One such challenge is, How would we onboard new hires virtually?
What it does
In response to the COVID-19 pandemic, many companies around the world have transitioned to a remote workforce at the advice of the Centers for Disease Control and Prevention. That means companies moving forward with hiring plans will most likely onboard new employees virtually.
We at LTI have tried to resolve this issue using Pega platform by leveraging the Chat Bot, NLP and OCR capabilities to bring in seamless automated virtual onboarding process.
The solution you are about to see would help companies to send the standard procedures and collect documents from the new hires over email along with a link to a chatbot portal for clarifying any queries.
How I built it
Using Pega we send automated emails to the new hires with basic procedures and documents to be submitted for seamless virtual onboarding.
New hires can simply reply to the email with all the documents like Marksheets, Experience documents, Personal Verification documents among others. They can leverage the chat bot facility to raise any questions on the onboarding process and then respond to the email.
On receiving the email, A Pega case would automatically get created and the data from the documents would be read through OCR and the same would be update to the company’s internal portal.
Challenges I ran into
Email triaging in pega is tricky at times
Accomplishments that I'm proud of
Email bot, OCR learning and NLP models capable of analyzing any
What I learned
Cool Pega features related to NLP, OCRs and pega case managements.
What's next for Digital Onboarding
Efficient document management system.
To be put in use within organization to reduce manual interventions in employee onboarding.
Built With
chatbot
emailbot
natural-language-processing
pega8.4 | Virtual Employee Onboarding | Using OCR, NLP and Bots, we help organizations to onboard new hires virtually. All new hires' documents are read digitally, saving on boarding time and manual verification. | ['Srividya Chinni', 'satish Kumar', 'leigh mitchell', 'Razauddin Ahmed', 'Sovan Parija'] | [] | ['chatbot', 'emailbot', 'natural-language-processing', 'pega8.4'] | 27 |
9,937 | https://devpost.com/software/aaseya-migration-made-easy-amme | AMME Dashboard
Add Staging Class
Migration Configuration
Reports
Inspiration Migrating data from one application to another is always challenging - but when it comes to content management data migration the fact that you’re moving tens to hundreds of millions of records across applications makes this kind of migration especially complex. With complexity comes problems - which usually cause lengthy delays in the migration process.
What it does AMME tool aims to lower the complexity of data migration from old legacy systems (which may or may not be built in Pega) to Pega PRPC, which will help Business Analyst & Business Architects to simply perform configuration wizard with a 360-degree view of migration process.
How we built it We have developed completely this application by using only Pega.
Challenges we ran into Performing migration for hierarchical data model of multiple entities.
Accomplishments that we're proud of by AMME which is making data migration configurable and very easy.
What we learned How to implement Data Structure Algorithm using Pega Activity and Clipboard Pages
What's next for Aaseya Migration Made Easy - AMME it needs to be enhance to support all kind of data bases. Implementing other data base related operations like purge and archive wizard.
Built With
pega | Aaseya Migration Made Easy - AMME | Migrating data from one application to another is always challenging and complex, which usually cause lengthy delays in the migration process. But with AMME it is very simple and quick. | ['Pankaj Malviya', 'Tushar Anil Rane', 'Ravi Padwal', 'Sachet Sharma', 'Prakhar Agarwal'] | [] | ['pega'] | 28 |
9,937 | https://devpost.com/software/bpmn-process-repository-and-importer | Portal
In today's agile era, business architects and product owners spend significant time creating process models and managing process repository. However, when the implementation starts, they are nothing but an visual artifact with all functional characteristics not being used. Ability to synchronise process models with Pega (process modelling with execution) allows business and IT to be in sync ensuring faster digital transformations.
Shows all the process models/flows. Allows to import BPMN models as XML and generate executable flows.
Overwrite the OOTB PegaAccel-Task-Harvest utility to use correct XSL transformers and BPMN 2.0 as transformation schema.
Customised OOTB harvest module to debug and fix. Map BPMN shapes to Process flow steps.
Ability to transform complex BPMN model into a functional process model to be used in Case Modelling
How BPMN 2.0 can be transformed into a Pega process rules
Next steps: Map CMMN and DMN models to make Case Designing fully automated with process repository
Allow improved managing of process models as a repository similar to other modelling tools
Built With
java
pega
xalan
xslt
Try it out
lksi6dzt.pegace.net | BPMN Process Repository and Importer | Uniform Process Repository with model import for 360 centre out transformation | ['Hari Losari', 'Sudip Gupta'] | [] | ['java', 'pega', 'xalan', 'xslt'] | 29 |
9,937 | https://devpost.com/software/intelligent-document-splitter-and-manager | Auto splitter and splitter UI
Inspiration
The business problem we are trying to solve here is with managing consolidated documents. Let's take a scenario where a user has to deal with a huge consolidated document attached to a Pega case. Business frequently come across such scenarios and finding relevant information from a consolidated document is often time consuming.
Users might also have to rely on some third party software, to split the consolidated document, to pass on to other applications for further processing. This manual process is often time consuming and prone to errors.
What it does
Our component focuses on introducing great efficiency in this managing process. With this users only have to validate the documents and action on exceptions, thereby reducing lot of time, effort and cost.
Our component helps users by intelligently splitting a consolidated document, by using state of the art template matching algorithm, from Open C V., It recognises the type of each page, in a consolidated document, by using some predefined templates.
How I built it
Built on top of Pega, Python, Open C V, PDF Box and Ghost Script. Here our Pega component is responsible to invoke the python script, which does all the heavy lifting in the background. Python script makes use of Ghost Script, to convert any pdf document either scanned, or textual, into images and then hands it over to Open C V, which does the template matching. PDF Box component is useful in manually splitting the PDF document, in case of exceptions in automated processing.
Challenges I ran into
=> Acquiring knowledge of ML
=> Using OpenCV to perform template matching
=> Understaneding how image processing takes place
=> Using PDFBox to build an intituite UI
=> Calling python script from pega
Accomplishments that I'm proud of
=> Implemented image recognition
=> Implemented an intuitive UI to handle exception scenarios
What I learned
=> Learnt how OpenCV perform image recognition
=> Usage of ghostscript to convert any pdf document to a set of images
=> Usage of PDFBox to split PDF's
=> Calling third party libraries from Pega compoent
What's next for Intelligent document splitter and manager
Future scope of this component, is to introduce some feed forward mechanism, to automate the training of the image recognition algorithm.
Built With
opencv
pdfbox
pega
python
Try it out
eb16dee8e5b2.ngrok.io | Intelligent document splitter and manager | This component provides an intelligent way of managing a combined PDF document, which is a combination of multiple smaller documents. | ['Chethankumar Mahalingappa', 'Hari Losari', 'Sudip Gupta', 'Avinash Haridasu'] | [] | ['opencv', 'pdfbox', 'pega', 'python'] | 30 |
9,937 | https://devpost.com/software/epidemic-tracker | Inspiration
Creating a safer work environment for those on the front lines helping day to day functioning to continue while putting themselves at risk
What it does
Inform user when he/she is entering an epidemic zone and provide information on precautions to be taken. Eg - Shipment pickup and delivery company employees. Informs Manager of where their employees are at all points.
How we built it
Used Pega 8.3.1, Pega Mobile, JS, Google API and Android.
Challenges we ran into
Getting proper certificates to get Pega Mobile to run. We couldn't get the certificates to enable push notifications.
Accomplishments that we're proud of
Building a small and effective application for variety of industries which can be quickly extended to other markets and epidemics in future
What we learned
Pega Mobile limitations and workarounds.
What's next for Epidemic Tracker
Extend for other countries and have backup APIs to get epidemic information in case one API doesn't work.
Github Repository for our project artifacts
User IDs to login and check the code are mentioned in the document Pega Hackathon 2020.docx
https://github.com/anup84/Pega-Hackathon-2020
Built With
android
google
javascript
pega
pegamobile
Try it out
tcs01.pegalabs.io | Epidemic Tracker | Inform user when he/she is entering an epidemic zone and provide information on precautions to be taken. Eg - Shipment pickup and delivery company employees. | ['PinakK2 Mallick', 'Anup Naik'] | [] | ['android', 'google', 'javascript', 'pega', 'pegamobile'] | 31 |
9,937 | https://devpost.com/software/project-ma8jqw3tvs5k | Application Name
Application Introduction
Application Features
Application Ecosystem
Application QR Code
Home Screen- Initial
Survey Questionnaires - Phone
Survey Questionnaires - Web
Home Screen- After Filling Survey
Roster Generation Algorithm
Home Screen- After Roster Generation
My Weekly Roster Screen
Login Time & Details Capture Screen
Configurable Notification Messages
Logout Time & Details Capture Screen
My Rewards Screen
Rewards Scoring Algorithm
Configurable features
Schedule Star- Team members
Thank you
Inspiration
In Post COVID 19 Era:
Health & Safety Risks involved at work & educational institutions.
Maintaining Social Distancing norms.
Struggle of institutions to cope up with regulatory norms put in place by respective governments.
What it does
Provides assistance to institutions for managing their capacity & continuity with government regulations.
Bridges the gap between distributed people and people managers with model driven roster management system.
Helps institutions to Adapt to new circumstances & challenges while ensuring health & safety.
How we built it
Using Pega Platform by utilizing Case Management with Survey feature and Mobile application capabilities.
Challenges we ran into
Managing roster on daily basis while monitoring health and guiding employees: Utilized Pega’s Case Management Capabilities with Notifications.
Capturing Self Health Assessment: Utilized Survey feature of Pega’s Case Management Capabilities.
Accomplishments that we're proud of
We are proud that we could address the problem of effective people management while focusing on Institutional Continuity Plan and the social distancing norms with a real time Pega based solution within a short period.
What we learned
Pega’s model-driven, unified approach that delivers an enterprise-grade, agile application with a no-code & low-code authoring experience.
Enterprise applications developed in Pega are automatically ready to run across a variety of devices, on or offline, with zero additional work required.
What's next for .
Registration to the application by users through an e-form/Pega Bots
SSO login & Account Management
SOS features to provide assistance who are need.
Intelligent roster generation considering Shifts, Leaves, Rotation Methods (Daily/Shift based), Weekends, Public Holidays & Preferences.
Improved Rewards Allocation which incl. triggering appreciation mails along with meal coupons etc.
Auto-assignment of roster to other team members in cases when the user is not able to come to office following the roster plan.
Integration of the application with email and SMS channel for updating roster plan based on SMS/ Email responses.
Mobile Offline Features to support roster management offline.
Built With
mobile
pega
survey
Try it out
drive.google.com | Schedule Star | An Adaptive Scheduling Solution To Maintain Institutional Continuity While Ensuring Health & Safety. | ['Deependra Rajpoot', 'Arnab Naskar', 'Bikash Agarwala', 'Archana Kumari', 'Mahesh Reddy T', 'Rohan Rathi'] | [] | ['mobile', 'pega', 'survey'] | 32 |
9,937 | https://devpost.com/software/smart-appointment | Confirmation of Doctor Appointment to the user
Inspiration
Any startup requires a career pitch. Our company is ready to take up any challenge positively and provide solution by creating a safer environment for the users during this fight against the covid - 19 pandemic. Pega Community and its opportunities inspired us for this PegaHackathon2020. So we have developed an application called Smart Appointment.
What it does
This web application created by our team for pega Hackathon 2020 helps the society counter the covid - 19 pandemic by minimising the queue in any service sector industries like Banks, Hospitals and help people in maintaining social distancing through scheduling appointment for maximum 5 users at a time. Our solution will definitely pave a path for easy scheduling and also in following the social distancing disciplines.First of bank application in which the user will find the nearest bank by entering zip code and another of hospital which filter the nearest branch by city and state Information. This application is highly customizable with any industry and with any pega solutions.
How I built it
Any service sectors or industry customizable web application from Team Darven Robotics for pega hackathon 2020. The workflow will explain users finding nearest services depending upon zipcode or current user location and another flow works on filtering the details based on user inputs like City State. The application is configured for maintaining user slot time booking by allowing maximum 5 users at a time. This will help in minimizing the queues and maintain social distancing during these tough times. This can also be easily integrated with any third-party application and as a future idea we can configure support channels via chatbots.
Challenges I ran into
Learning pitches were interesting. Each sprint worked wonders when the application was nearing completion.
Accomplishments that I'm proud of
How the workflow and idea just brought us forward for PegaHackathon2020. Definitely a solution that is most needed in this hour.
What I learned
What's next for Smart Appointment
Integrating our application with any third party services. Building user interfaces through Pega features and OOTB activities and also using Pega APIs for other major customer services. Chatbots. AI based booking and prediction.
Built With
8.2
api
application
google
key
pega
version
Try it out
github.com | Smart Appointment | Pandemic? Don't panic. Get your service done with our smart booking application! | ['darven robotics', 'Saranya M'] | [] | ['8.2', 'api', 'application', 'google', 'key', 'pega', 'version'] | 33 |
9,937 | https://devpost.com/software/collaboration-app | Inspiration: Create application on Pega Platform
What it does: Collaboration App
How I built it: Using Pega Platform
Challenges I ran into: Using Pega Platform
Accomplishments that I'm proud of: Using Pega Platform
What I learned: Using Pega Platform
What's next for Collaboration App: Needs further improvement
Built With
pega | Collaboration App | App for collaboration | ['Sandeep Chakravartty'] | [] | ['pega'] | 34 |
9,937 | https://devpost.com/software/medikare-1-0 | Medikare Mobile App
Chatbot
Email notifications
Google Maps integration
Reporting
Inspiration
Recent COVID-19 pandemic has highlighted the blaring inefficiencies of non-integrated healthcare facilities. Due to the absence of sync in healthcare systems, the present healthcare infrastructure has been overwhelmed. An early warning system for the identification of epidemic is also lacking. The need of the hour is to have an end to end integrated health care platform with early detection of an epidemic.
What it does
Medikare 1.0 is an end to end multi-channel healthcare platform leveraging Pega 8 platform capabilities. It attempts to integrate existing systems used by patients, doctors, testing labs, and hospitals. It helps reduce in-person meets for the safety of health care professionals and users.
Following are some of its key features:
Mobile App: Ease of usability and accessibility
Chatbot: Integration across interactive platforms
Google Maps: Help to locate doctors, hospitals, test facilities
Email notifications: Consistent communication of all key events
Reporting: Ability to detect future pandemics
How we built it
Medikare 1.0 has been built on the Pega platform version 8.3.0 leveraging most out of the box features
The process flow includes:
Consultation: User/patient enters symptoms, answers questionnaire
Diagnosis: Doctor performs online consultation and prescribes the further course of action
Treatment: Based on the diagnosis, the doctor creates a treatment plan
Reporting: Identification of potential pandemic based on transmission trends
MyCo-Medikare-Work-Consultation is the parent class for Consultation. This class holds information regarding the initial diagnosis of User and data gathering. MyCo-Medikare-Work-Treatment is the child class of Consultation. It holds reusable components for ease of use in its child classes.
At run time, Dynamic Class Referencing is used to determine whether Covid flow or General treatment flows needs to be initiated. Covid flow is built around the prevalent process followed in the treatment of COVID-19 disease. General flow on the other hand deals with the process followed in treatment of all diseases except COVID-19.
Challenges we ran into
Implementing this end to end solution within a short period of time was certainly a challenge in itself.
Creating a mobile app was also not easy considering the team was building it for the first time.
We also faced challenges in implementing the chatbot due to certain limitations associated with the current Pega Cloud instance.
There were other technical challenges related to dynamic class referencing and building complex workflows.
Finally, compressing all of the information within a 5-minute video was a great challenge.
Accomplishments that we are proud of
Considering the current pandemic situation, the entire team was remotely situated. They used phone and video conferencing for swift communication.
The team was able to successfully design, build, test and deliver an end to end multi-channel platform
In spite of having work and personal commitments.
The team dedicated a lot of time and effort to make this solution scalable and flexible.
The team overcame all of these hurdles and showed a lot of determination and character to build, document, and present this application.
What we learned
We learned some cool features of Pega including creating a Pega Mobile App.
We were able to successfully create a Pega chatbot that can be used to initiate consultation from any social channel.
Google Maps integration was another important feature the team explored.
Conceiving, designing, and building an application within such a short period of time provided us some valuable experience.
What's next for Medikare 1.0
Integration with Insurance providers/ Financial institutions: Medikare could be integrated with such systems for online insurance/loan packages associated with illnesses.
Chatbot integration with Facebook/other channels: This integration make Medikare accessible across a variety of social platforms.
Adding other illness types/epidemics: This can be easily extended to build treatment flows for other major illnesses or potential epidemics
User Sign-up: Self-sign up feature could be added in the future.
Push-Notification through Mobile: This can provide important updates to users
Implement Decisioning: Pega Decisioning could be implemented to calculate the propensity of healthcare facilities use.
Integration with Alexa: Voice-based appointment booking using Alexa.
How to access Medikare 1.0
URL :
https://tcs01.pegalabs.io/prweb/PRServlet/
Role: Patient/User, Id: user1@medikare, Password: Rules1
Role: Doctor, Id: doctor1@medikare, Password: Rules1
Role: Test Lab, Id: testlab1@medikare, Password: Rules1
All passwords are case sensitive
Built With
adobe-rush
google-developer-console
narrator?s-voice
pega-platform-8.3.0
Try it out
tcs01.pegalabs.io
drive.google.com
drive.google.com
drive.google.com
drive.google.com
drive.google.com | Medikare 1.0 - An integrated healthcare platform | Medikare is a solution to minimize the need for patients to visit doctors/hospitals in person. Healthcare professionals can have timely medical intervention, with early warnings for potential epidemic | ['Haziq Pathan', 'Kuldeep Shekhawat', 'Aakash Talreja', 'vaibhav srivastava', 'Sai Kulkarni'] | [] | ['adobe-rush', 'google-developer-console', 'narrator?s-voice', 'pega-platform-8.3.0'] | 35 |
9,937 | https://devpost.com/software/disease-screening | Disease Screening case type
Mock Medical Website with embedded chatbot (closed)
Mock Medical Website with embedded chatbot (opened)
Chat screenshot (1)
Chat screenshot (2)
Chat screenshot (3)
Chat screenshot (4)
Chat screenshot (5)
Chat screenshot (6)
Chat screenshot (7)
Chat screenshot (8)
Confirmation email with a summary of the process
Pega API's used for complete the case
Pega API call (GET) header response
Pega API call (PUT) header request
Pega API call (PUT) body request
List of symptoms used in the adaptive model
Propositions (diseases) for the adaptive model
Strategy to get the proposition (disease) with the higher propensity
Strategy to update the outcome (Success or Fail) of the proposed disease
Adaptive model trained with 10,000 records
Inspiration
During the
Covid-19 Pandemic
, a medical institution needs to
quickly
evaluate if a patient has symptoms compatible with that particular disease or another one with any similar external signs (flu, cold, allergy, asthma, anxiety, etc.).
In addition, the hospital needs to do it
remotely
, without jeopardizing the health of its employees or the patient, by using channels such us the telephone, a mobile application or a web form.
What it does
A
quick and secure
way of doing the disease screening based on the symptoms, without the need of came face to face with the patient, is to use
Big Data
and a
Decisioning Adaptive Model
, and make the screening remotely through
NLP (Natural Language Processing)
in a
Chatbot
hosted in the hospital website.
This is the approach we have followed.
How I built it
We have created an application with a
Disease Screening
Case Type. In addition to the normal flow of the case, we have added a Chatbot in several stages to:
Retrieve the symptoms based on basic NLP and flows using questions and decision shapes, with different behavior depending on the answers and the symptoms.
Retrieve additional data used as predictors in our model (date of first symptoms, age, gender, if the patient has been recently in any are of risk or in contact with a Covid-19 positive).
Give the patient the
First Diagnosis
provided by the adaptive model.
Give the patient some medical appointment options (for general doctor, specialist or test) and schedule the chosen one in the medical institution.
Send a summary by email.
When the doctor has the
Final Diagnosis
, it is sent back to the case through a couple of
Pega API
calls:
GET call to retrieve the
ETag
header and the
Pacient
content.
PUT call to invoke the “SetFinalDiagnosis” local action placed in the final stage, passing the
If-Match
header (the ETag from the previous call) and the Pacient content (from the previous call) in the body plus the Final Diagnosis.
The "SetFinalDiagnosis" local action updates the status to Resolved-Completed and updates the adaptive model to improve future predictions.
Challenges I ran into
Despite it is a
simple
project, we have faced several challenges:
Nodes for decisioning
: By default, the nodes in our environment were not configured for decisioning. We needed at least one node running in
DDS (Decision Data Store)
and
ADM (Adaptive Decision Manager)
modes. To configure the nodes in such a way, we needed to run the JVM adding those modes (or Universal) to the NodeType parameter.
Capture Response from Previous Decision
: We have stored the Interaction ID when the strategy response with the proposition/disease with the higher propensity. In the final stage we retrieve it and set the outcome (Success or Fail) to let the model learn.
HTTPS for Pega API
: Our local environment was running in HTTP mode, but we needed HTTPS to call the Pega API, so we created a local certificate and configure Tomcat accordingly.
Email Account
: We created an Gmail account for the demo and we configured a new email account in Pega, but we were not able to use it to send the summary emails. So, finally we configure the Default account with our Gmail.
Accomplishments that I'm proud of
We are proud of having the main features of the solution completed and running in a few weeks, with a serious lack of time and team to do it.
We are proud of having solved all the challenges faced and described in the previous section, plus some other points:
Train the Adaptive Model
: Due that the information given by the model is a medical diagnosis, we cannot just create the adaptive model and use it without a training for it to learn, because the initial accurate would be very poor. That is why we have developed a support Java code for generating 10,000 records of random predictor values in a while (with some hardcoded logic to assign the proper disease).
Pega API
: We have used the Pega API OOTB to resolve the case, instead of creating a custom service.
Mock Medical Website
and
Chatbot Mashup
: For demo purposes, we have used a mock medical website to embed the fully functional Chatbot mashup code.
What I learned
We have learnt some basics regarding Chatbot and NLP, and a lot about Adaptive Models in the real world (not only in a decisioning course). Also, we have learnt how to use the Pega API.
Before this Hackathon, we did not know much about these topics beyond theory. We are sure that all the knowledge acquired will be very useful for our future projects and our clients will be impressed.
What's next for Disease Screening
We have a list of improvements for future versions of Disease Screening:
Chat Bot
: We need to improve the NLP through the Pega IVA (Intelligent Virtual Assistant), because in this first approach of the solution, the chat bot interaction is based on flows using questions and decision shapes, with different behavior depending on the answers and the symptoms.
Adaptive Model Training
: We have trained the model with 10,000 records of random predictor values (with some hardcoded logic to assign the proper disease) generated by a simple Java code. Obviously, the real model must be trained with real data, probably obtained from the database of the medical institution.
Error Handling
: We need to improve error handling throughout the entire application. Mainly when implementing the real connectors with the medical institution instead of the placeholders, but also in sending emails or retrieving the final diagnosis.
Custom Reports
: In addition to the OOTB reports provided by Pega, we have configured some custom reports in case the hospital wanted to use them. However, we are sure that we should create more to get interesting statistics that could help to improve the customer satisfaction or increase the ROI of the medical institution.
More Symptoms and Diseases
: We have created this solution based on a limited set of symptoms and diseases, but it could be easily improved by adding more symptoms (for example high or low blood pressure, back pain, etc.) and diseases (such as dengue).
Protection Data Law
: We need to accomplish with the Data Protection Law of each country, for example the GDPR (General Data Protection Regulation) in the EU (European Union).
And also a list of ideas we could not implement in this first version:
List of Risk Areas
: We could use a RPA solution to retrieve and store in our application the list of countries considered as areas of risk for each country. We could do this by accessing the official health websites of the different countries, maybe once per week.
Geolocation
: Once the consent was given by the patient, we would have retrieved the latitude and longitude of his/her position at that time. Using these two properties and configuring a connector to the Google API, we could have obtained the country from which this patient is interacting with the chat bot. Knowing the origin country, we would have retrieved and populate in the case the list of countries considered as areas of risk.
Covid-19 Positives in your Area
: In addition to the chat bot, we could embed a button on the website of the medical institution to show a map of Covid-19 positives that have been diagnosed by the hospital in a predefined radius of 1km, 2km etc. from your current position.
Built With
adaptive-model
chat
decisioning
natural-language-processing
pega
Try it out
github.com | Disease Screening | Create an easy Covid-19 diagnostic app with a chatbot for retrieving the symptoms and an adaptive model to return the first diagnosis. The app will connect with a medical institution for next actions. | ['José Luis Laviña', 'Carlos Gomez Tome'] | [] | ['adaptive-model', 'chat', 'decisioning', 'natural-language-processing', 'pega'] | 36 |
9,937 | https://devpost.com/software/covid-19-self-checker | Login Screen
Collect Personal Details in step 1
Collect symptoms Details in step 2
Collect symptoms Details in step 2
Show Results in Step 3 based on symptoms details (Low)
Show Results in Step 3 based on symptoms details (Medium)
Show Results in Step 3 based on symptoms details (High)
Inspiration
Inspired from the people who can't able to spend more money for COVID-19 testing
What it does
My Application used for the people who not able to spend more money for checkup.
In my App, people will know the risk level of COVID-19 virus either low or medium or high.
In first stage, collect personal details from people. In second stage Collect symptoms details. In last stage show the risk level of COVID-19 virus based on ten questions.
How we built it
We built using Pega cloud version 8.4
Challenges we ran into
Challenges faced while testing Activity rule
Accomplishments that we're proud of
Successfully show the Risk level of the patient based on ten questions
What we learned
I learned many things while developing this hackathon project such as customize login screen using html and css, Different layouts on Section,passing parameters for field values,Skin rules, paragraph rule, Add Image on section,Add Icon for Properties,etc...
What's next for COVID-19 Self Checker
I'll continue to extend my application with more features using pega platform
Built With
cloud
pega
version8.4 | COVID-19 Self Checker | By the people, for the people! | ['Royal A'] | [] | ['cloud', 'pega', 'version8.4'] | 37 |
9,937 | https://devpost.com/software/hello-dr | Hello Dr
Notification
Challenges
Benefits
Solution
Patient Dashboard
Appointment with Specialist
Patient Portal
Illness Registration
Reports
Appointment for Lab Test
SOS
Doctor Portal
Doctor Dashboard
Reports
Patient Summary
Alerts
Thank you
Notification
Inspiration
To develop technological solution to avoid spread of chronic diseases in future.
What it does
This Pega mobile application would bring in Doctors and Patients get connected realtime. This app would help in identifying chronic diseases at earlier stage.
How I built it
Built using Pega V8.4.
Challenges I ran into
identifying problem statement, technological interfaces, etc.
Accomplishments that I'm proud of
The final Product and core content of this App.
What I learned
NLP, Voide channel integration
What's next for Hello Dr
Enhance and build a predictive framework for health care industry.
Built With
natural-language-processing
pega | Hello Dr | 'Hello Dr' Pega mobile application would bring in Doctors and Patients get connected real-time. This app would help in identifying chronic diseases at earlier stage. | ['Ashokkumar Thangaiah', 'Deenadayallan S'] | [] | ['natural-language-processing', 'pega'] | 38 |
9,937 | https://devpost.com/software/telco-oneapp-playbook-service-management | Case Life Cycle - New User KYC
Case Flow - New User KYC
Case Life Cycle - Customer Service Request
Case Flow - Customer Service Request
Case Flow - Customer Service Request 2
Inspiration
Pega’s ability to help us build customer solutions quickly inspires us to talk to our clients by always building playbooks. This is one such playbook to explain Pega’s capability and usage to our Telco clients
What it does
This play book displays Pega’s capability to enable digital transformation for Customer onboarding and service management for Telco Retail clients
How I built it
We identified the key usecases that could demonstrate the agility , security and scalability features of Pega and build the sales playbook solution around it.
Challenges I ran into
Not many; Only challenge was , we built several features and we were unable to showcase all of it in a 5 minutes video, with a platform like Pega challenges are minimal
Accomplishments that I'm proud of
Ability to stitch a quick story of Pega for the COVID times , for Pega sales to use and playback to potential customers globally ; Key security and scalability features of Pega that are very important during these COVID “Work From anywhere” times.
Ability to have developed 31 usecases in just 15 days , with 2 Pega Consultants
What I learned
As a team , we have realised that if we keep the customer’s key problem in mind and develop solutions , rather than focusing on too much documentation , Pega suits very well for such agile environment to build quickly for the changing environment
What's next for Telco OneApp PlayBook - Service Management
We always expand our Playbook solutions to touch upon all core business processes of Telecom.
• Create Pega Mashup to enable customer service portal to be launched from a web page
• BPM analytics using Pyze platform for comprehensive ROI analysis of this BPM Implementaton
• Implementing all core Telco processes such as Order Management , Number Management , OSS/BSS etc
Built With
pega
Try it out
drive.google.com | Telco OneApp PlayBook - Service Management | OneApp for all: Telco Digital transformation - defeating COVID challenges: zero-contact, serve from any where - bringing convergence, control, cost effectiveness and quality to customer service. | ['BlueRose Technologies'] | [] | ['pega'] | 39 |
9,937 | https://devpost.com/software/customer-experience-shifting-towards-new-normal | Shifting towards New Normal
Technology plug-in to enable business towards New Normal
Inspiration –
Enabling technology to help people to be safe and productive in post Covid era
What it does -
Enable Physical Access keeping in mind of workplace safety, Empower a remote workforce to work digitally and safely develop client relationships, Allowing a customer to talk to a virtual service representative instead of just waiting
How we built it -
The solution is envisaged to empower banks to create highly differentiated virtual banking experiences with technology plug-ins. We built the application on top of Pega CS 8.4 framework for Financial Services and augmented omnichannel experience by implementing
Voice Bot with Google Assistance
- We created Google Home dialogue flow project to define the intent, text analytics & extraction logic. The dialogue flow once invoked via Google Assistance voice bot, interacts with Pega API services exposed to return desired outcome through question & answer.
Microsoft Teams to enable video conferencing channel
: We enabled the video channel through MS teams and integrated the solution with Web Chatbot & PegaChat, seamlessly respond to the complete digital needs of consumers. We have leveraged U+ Bank demo application for retail bank and enabled Web ChatBot through mashup. The ChatBot transfers interaction to a financial advisor of the bank through PegaChat using OOTB configuration. Video channel in launched as a service request from Customer 360 unlike Co-Browse and leverage Microsoft Teams Graph API 1.0 to create online meeting object and fetch the meeting URL for both customer & financial advisor to seamlessly have face to face meeting.
QR code based Physical Access
: We have created a new case type for enabling customer scheduling appointment through Self-Service portal of U+ bank through Web Mashup to limit the physical access to safe deposit boxes or for any other reason. It collects data from Customer on available time-slots on a given day and generates QR code which can be used for an entry to the bank
Challenges we ran into -
The solution embraces technology plug-ins for Google Assistance & Microsoft teams and there were challenges in identifying the right API for the need. However one typical technical challenge we faced while transferring the interaction from Web ChatBot to PegaChat. Although we used OOTB configuration to enable web chatbot to support Live chat, the seamless hand-off between chatbot and PegaChat did not work because it was not getting the desired URL for PegaChat. We realized after quite a lot of tracing that the OOTB code was expecting the customer URL but there was no place to provide the URL or configuration in the web chat configuration from the self-service portal. We had to explicitly fetch the URL from the PegaChat configuration and set it in the data transform.
Accomplishments that we're proud of
We have successfully added the most important channel (video with MS Teams) with Pega Customer Service in post Covid-19 context where any back office employee like Financial Advisor for Bank, Insurance Agent for Insurance company etc can able to conduct face-to face chat/meeting along with the customer 360 degree view to personalise the interaction
This additional channel (can also be extended for other Video calling software) can be leveraged for any domain solution to engage customer 1:1 with a true digital omnichannel experience
Cloud based platform and API based integration architecture helps in quick configuration with minimum effort and fast adoption in consumer community
What we learned -
One of our major learning was how to leverage Google Dialogue flow to configure intents, text extraction and how to invoke REST API to call services in Pega. We studied both options of Action SDK & Dialogue flow and learned that Dialogue flow was better option as being hosted in cloud and also easier to configure. Also we learned lot around text extraction how google treats extracted data as text vs numbers etc.
Another learning was on the access token policy for MS Teams where we had to go through different grant type options and find the best one suitable for the integration. For example, using grant_type as "access_code" would require security challenge to the user, "client_credentials" would have restricted access to few API calls like onlineMeeting etc.
What's next for Customer Experience –
Shifting towards new normal – “Digitize the physical and humanize the digital"
Built With
dialogue-flow-google
microsoft-graph
pega
uplus
Try it out
maantic01.pegalabs.io
maanticuplus.web.app
console.actions.google.com | Customer Experience – Shifting towards new normal | “Workplace Safety, Workforce Safety” - Transforming Customer Engagement to enable business to new normal leveraging the technology plug-in integrated with Pega Customer Service from Maantic Inc. | ['Sayan Ghosh', 'Anurita Bhunia', 'Kalinga Rout'] | [] | ['dialogue-flow-google', 'microsoft-graph', 'pega', 'uplus'] | 40 |
9,937 | https://devpost.com/software/media-planning-suite | Media Analyst Media Plan
Media Planner
Media Director Approval
Media Analyst Media Plan
Media Director Approval
Media Analyst Manager Approval
Media Analyst Media Plan
Media Director Approval
Media Analyst Manager Approval
Media Analyst Media Plan
Media Analyst Manager Approval
Media Director Approval
Login Screen
Media Planner
Media Analyst Manager
Inspiration
In our research we found that Advertising Agencies did not have collaborative tools for their functions. This industry lacks an end to end tool and level of automation used is less. So we formed an idea of putting together a tool for E - Media planning tool.
What it does
It collaborates all the actors in the e media planning process.With this time to work on a media plan, and its related campaigns takes less time
How I built it
Using Pega PRPC platform and its native ootb features like case designer for case management. Similarly native portals for actors to achieve their work. And we used correspondence for sending emails.
Challenges I ran into
Yes I ran into few challenges like, need to write some custom scripts and logic to render reports.
Accomplishments that I'm proud of
Our hackathon team worked closely, and delivered this application with in very less time, with out teams spirit we would not have achieved this.
What I learned
Communication with team members on the requirements and their working status through agile work bench.
What's next for Media Planning Suite
It should be able to create cases using email listener automatically, and capture email approval or reject reponse to continue the case.
Built With
pega
Try it out
drive.google.com | Media Planning Suite | Media planning is the process of deriving the best strategy to reach the largest target audience through an effective use of the marketing mix, using appropriate channels. | ['syed rahamthulla', 'Madan Burra', 'dinesh kumar Koppuravuri', 'Pavankumaryadav pallapothu', 'Kalyani G', 'bharathi MM', 'Rekha Bantu'] | [] | ['pega'] | 41 |
9,937 | https://devpost.com/software/market-crowd-control | After Market Timing set by Market Authority
Consumer ID Generation
Safe Time suggestion sample 2
Safe Time suggestion sample 1
Application Home Page
Inspiration
A state Tamil Nadu in India had the pandemic under control until the breakout happens in a market. After this breakout the pandemic is out of control. Seeing this a question arises why cant people follow the government's rules of not crowding the market? The answer is people doesn't know how many people already present in the market and all visiting the market at the same time.
What if we can make the people know the number of people already present in the market so that he/she may rethink the time to visit the market? That is were my application Market Crowd Control (MCC) comes into the picture.
What it does
In simple points MCC makes sure that when people wants to visit the market he/she knows whether it is the safe time i.e that market is already crowded or not. If crowded, MCC will suggest the upcoming next safe time to reach the market.
This logic is implemented by using two actors.
Market Authority
Market Consumers
Market Authority is the one who sets the market timing and maximum number of people that can be in the market at any given point of time and there by controlling the crowd and letting the people know the safe time to reach the market.
Market Consumers are the common people uses this app to check whether the time is right to visit the market or not.
The app also has one start feature of Report Covid-19 Diagnosed.
When ever a user uses this option the MCC app fetches the user's last fourteen days market visit records and from there who were the people visited the market at that same time and sends COVID-19 alert asking them to approach nearest COVID-19 Test center.
By doing this we can easily track the COVID-19 spread.
How I built it
I used Pega Case Management and Pega Mobility features and for now showcased it in Pega Mobile Preview Android application
Challenges I ran into
Utilized Cosmos to build this application. Since it is my first time had some challenges.
Faced major challenge around customized authentication and auto case trigger
Accomplishments that I'm proud of
Managed to provide a complete mobile application in four weeks time that meets the Goal of Controlling the Crowd and Tracking the COVID-19 spread.
What I learned
Learned a lot of new concepts in pega like Pega Mobility features,Operator provisioning, pyMobileSnapStart and etc
What's next for Market Crowd Control
As of now the app considers one market and its users.
Future goal is to utilize the Google Maps to use real time data and extend the application for all markets available near a user's locality.
Pull in additional actors such as Market Sellers, Government persons and Medical persons
Detailed explanation of functionality
Downloading the Android app:
Download and install the Pega Mobile Preview application from below link
https://play.google.com/store/apps/details?id=com.pega.mobile.preview
Launch Pega Mobile Preview application and copy and paste the link below on mobile channel to get access to portal.
https://fdh0e9ig.pegace.net/prweb/PRRestService/MobilePreview/v1/configuration/RULE-CHANNEL-MOBILE+30F4DE87-2023-41C8-8E3F-792F1C1655E3+%2320200529T123527.746+GMT
Note:
MCC user below two Actors to achieve the goal of maintaining the people number under control and alerting the user if he came in contact with a COVID-19 diagnosed person.
Market Authority provided by MCC Administrator
Username: MarketAuthority@MCC
Password: b1ueSKY!
Market Consumers can be a new or existing user signed up with MCC
Test or Existing users:
Username: Consumer1; Consumer2; Consumer3
Password: b1ueSKY!
Signing Up with Market Crowd Control (MCC):
Click on that a log in page with “Login with MCC” button appears.
Click on that button. Enter your name/Email Id in the user name and a dummy password in the password field and click on login.
You will see a welcome text and Sign up button.
Click on the sign up button.
Enter the details and click on sign up and then click on log out. Login screen appears.
Now you have successfully signed up with MCC and you will receive an email with username and password.
Using MCC:
Click on the “Login with MCC” button and enter your user name and the password which you have used in the sign up page.
In the home page you will see the welcome text and the below three buttons
• About
• Crowd Control
• Update my details
About:
User on click of the button “About” a window pops up with the details about Market Crowd Control
Crowd Control:
When user have logged in as Market Authority, on click of the button “Crowd Control” user will see two options to choose an actor/role you are going to perform.
User on choosing the option “Market Authority” a screen comes up asking the details such as “Effective Date”, “Market Start Time”, “Market End Time”, “Allowed Maximum people” and etc.
User on entering all required details and click on button “Set Timing” for the entered “Effective Date” the screen refreshes to display the below message
“Market Timings has been set successfully”
MCC adds a record and starts monitoring the number of people such that at any given time people count is less or equal to the “Allowed Maximum people” in the market
User on choosing the option “Market Consumer” a screen refreshes with below three options
a. Plan a new purchase
b. Cancel the plan
c. Report COVID-19 diagnosed
Plan a new purchase:
User on choosing the option “Plan a new purchase” the screen refreshes asking the “Date of Purchase” and with the below two options.
• Give me the SAFE TIME
• Give me the START TIME
When user have a time of start from home he can choose the option “Give me the SAFE Time” and MCC will give the SAFE TIME from that start time.
When user don’t have a time of start i.e he wants to go to market at any time he can choose the option “Give me the START Time” and MCC will give the START TIME so that he reaches the market in the safe time.
User on choosing the option “Give me the SAFE TIME” the screen refreshes and asks for more details.
User on entering all required details and clicking on button “Check” you will see a message saying the SAFE TIME and related details.
User on choosing the option “Give me the START TIME” the screen refreshes and asks for more details.
User on entering all required details and clicking on button “Check” you will see a message saying the START TIME and related details
Finally, after checking the time and user on click of button “Finalize” a Consumer ID is generated and displayed on the screen and the details will be sent to the user through email.
Cancel the plan:
Why Cancel the plan in MCC is mandatory when the user chooses to cancel the visit to market?
Answer: If user doesn’t cancel the plan he may get false alert from MCC when an another user reports using the “Report” option
User on choosing the option “Cancel the plan” the screen refreshes asking for the “Consumer ID” which got generated for the plan.
User on entering the “Consumer ID” and click on button “Cancel Plan” the system removes the record and displays the below message
“ has been cancelled successfully"
Report COVID-19 diagnosed:
User on choosing the option “Report COVID-19 diagnosed” the screen refreshes asking for the “Diagnosed Date”
User on entering the date and click on button “Report” the system will fetch the user’s last fourteen days visit to market and the people who were in the market during their visit and will send an email alert with the below message
“You were in the market with a COVID-19 diagnosed person in the last fourteen days.
Kindly approach the nearest COVID-19 Test Center and take the test.”
User on screen sees the below message
“Thanks for reporting this information and helping to fight the spread of COVID-19”
When user have logged in as “Market Consumer” and on click of the button “Crowd Control” the user will straight away see the below three option
a. Plan a new purchase
b. Cancel the plan
c. Report COVID-19 diagnosed
Update my details:
User on clicking the button “Update my details” the screen refreshes asking the details to update.
User on entering all the required details and clicking on the button “Update” the information gets updated in the system.
Testing Notes:
I have added Market Timing from 6/22/2020 to 6/26/2020
I have created test users Consumer1, Consumer2, Consumer3 and checked for safe time and generated Consumer ID for the time 9.30 AM on 6/23/2020 and in this time the maximum number has been reached so when user checks for this time it will show the next upcoming safe time
Built With
pega
pegamobilepreview
Try it out
fdh0e9ig.pegace.net | Market Crowd Control | My idea is to control the crowd in the market by maintaining the number of people and alerting the user of COVID-19 risk. | ['Vinoth Kumar'] | [] | ['pega', 'pegamobilepreview'] | 42 |
9,937 | https://devpost.com/software/work-from-home-assistant | A standalone app / pega widget that organizations can distribute among their workforce that will help employees, vendors and customers get access quickly to information regarding essential services in their locations that is authenticated, validated and updated frequently by the workforce community. This will foster a greater sense of community among the workforce and keep them motivated while reducing stress of scouting for the right information when the need arises.
Built With
cosmos
google-maps
pega
Try it out
github.com | Work From Home Assistant | A standalone app that organizations can distribute among their workforce that will help employees, vendors to get access quickly to information regarding essential services in their locations. | ['Durga Ravi', 'Muralidharan P', 'Gnaneswar Naidu Sarangam', 'Chandana Teegala'] | [] | ['cosmos', 'google-maps', 'pega'] | 43 |
9,937 | https://devpost.com/software/smart-loan-framework | Apply loan from pega chat bot
Customer first, which has inspired us to develop this solution. where we are trying to engage customer when they need us most.
Technical perspective so much learning like configuring pega chat bot and seeing hows NLP works.
Built With
pega
pegachatbot | Smart Loan framework | Smart loan framework can be leveraged by any bank to automate loan creation and processing from pega chatbot. | ['Ganesh Walunj'] | [] | ['pega', 'pegachatbot'] | 44 |
9,937 | https://devpost.com/software/real-time-consultation-and-transfer | Initiate Consultation
New Consultation Request
Inspiration
Business Context:
Business users works on open cases which are assigned to them or in work queues by finishing assignments. Sometimes, they would need help from other business users to be able to complete that assignment. So, they usually do below things:
Add a note in Pulse by referring the user from whom help is needed and later transfer the case to that user.
If the other business user is available in the office and he/she is nearby, then 1st business user will go to 2nd business user’s desk and gets the required inputs and based on that finishes the assignment.
Directly transfer the case to other business user by just adding case notes.
Problem Statements:
Below are some of the issues in the current consultation/transfer process:
The person to whom the case was transferred may not be available as he/she is on vacation. So, in this case the overall time to finish that assignment will be more.
Because of Covid-19, many business users are working from home. So, a business user cannot go to other person’s desk and take inputs. A business user may need to contact other business user by pulse/other external chat application/phone call to discuss about it and complete the assignment. If other business user is contacted via a different chat application, then there are chances that some sensitive information might be entered in chat application.
In customer service applications, some clients may not be using CTI for phone call interactions. In this case, if a CSR wants to transfer phone call interaction they would first transfer phone call to other CSR and later transfer the phone call interaction/service case created from it to other CSR’s worklist. The other CSR needs to note down the interaction id or service case id and then open that case from worklist. Only after this other CSR can complete customer’s request.
What it does
Solution Overview :
The solution provides a way for different business users to consult other business users in real-time.
The solution includes below features:
A business user can make himself available/unavailable for consultation.
A business user can consult other business user by selecting a user from the list of available users. A pop-up will be displayed to the selected business user to accept/decline. Once 2nd business user accepts incoming request then both users can interact in real-time using Pega’s pulse.
A randomly selected business user by the system can also be consulted.
If the other business user wants to work on case which is being consulted then he/she can accept the transfer request and work on that assignment.
How I built it
We created Pega's notification channel to publish notifications for different events between initiator( person who initiated consultation) and receiver ( person to whom consultation request is sent). Used javascript functions and Pega's javascript APIs to process received notifications.
Accomplishments that I'm proud of
At the time when we came up with this idea we were not sure if we can implement it. We are proud that the features which we thought of implementing as part this idea, have been implemented by using correct Pega features.
What I learned
We learned about Pega's notification channel and how it can be utilized for sending and listening to those notifications. This concept can be utilized in other notifications related functionalities.
What's next for Real-time Consultation and Transfer
Below enhancements can be made in future:
Publishing notifications ends as soon as receiver accepts consultation request. We can send further notifications when either receiver or initiator closes consultation and when receiver accepts transfer.
Play sound notification when a new consultation window is displayed.
Currently, we check if a user is available for consultation based on consultation availability option selected by user. We can also check if users session is active or not. In this way, if the user had not logged off or browser had crashed we can accurately get users available for consultation.
A queue processor to remove older consultation availability records from database table.
Built With
javascript
pega | Pega Real-time Consultation and Transfer | Pega Real-time consultation and transfer component for better collaboration between business users especially during Covid-19 as many users are working from home | ['Ashok9884 Pathak', 'Raunak Jaiswal', 'Syed Hussaini'] | [] | ['javascript', 'pega'] | 45 |
9,937 | https://devpost.com/software/cognitonic-travel-bubble-management-system | Travel Case
ePass Request form
ePass
Cosmos
Capture health symptoms
Google map view and selection of isolation & hospital centers
Health symptoms summary of various stage of Travel
Business Administration
Please use below link to find Cognitonic Travel Bubble Management solution overview .The shared folder also contains guide to test the system with user credentials , Usecase scenarios and demo video for your reference.
link
Inspiration
Covid-19 outbreak has impacted everyone across the globe. These impact are not only on health front but also has huge impact on global economy. World is still coming to the terms with novel corona virus and adapting to the new ways of interacting.
To keep economy on track travel is very important but at the same time addressing health concerns as well.
What it does
Cognitonic Travel Bubble Management powered by Pega is a unique solution to help countries to minimize the health and economy impact due to Covid-19 by allowing them to configure and manage controlled international and domestic travel bubbles.
Our solution-
Allow a country or states to impose specific health advisory and regulations for travelers from different countries or states by providing the ability to create specialized travel bubbles and provide guided pathways before embarking on their journey( into the country or within the country).
Allow border security & health departments to monitor & manage travelers based on their travel bubble and health symptoms ,during travel and Post travel, hence minimize Covid-19 spread due to overseas or interstate travelers.
For Example : If Australia adopts this solution then it can configure:
A Travel bubble between Australia and New Zealand – which might have minimal or no regulations with no quarantine period.
A Travel bubble between Australia and Singapore – which might have moderate regulations with moderate quarantine period.
A Travel bubble between Australia and United States – which might have full regulations with no quarantine period.
Accomplishments that I'm proud of
*
Business benefit *
:
Allow travels based on specific travel bubble with a country or a state.
Guided pathway for travelers, hence reduce the stress of travelers as well as state authorities.
Reduce the risk of covid-19 spread from outside by managing overseas travelers or interstate travelers.
Online Travelers service to reduce the call volume to various state authority .
Pega web mashup feature will enable this solution to be part of existing states website in order to keep holistic information at one place .
This solution will provide a unified platform to capture travelers health information at various stages of travel and hence will eliminate the data loss risk.
This solution will reduce/remove the need to ask personal information multiple time at various stages of travel . Hence speed up the screening process and provide better customer experience.
This will provide the holistic health symptoms audit for a traveler at various stage like before travel, during travel and post travel .
Business management modules will enable to create a new travel bubble in minutes and will allow to manage various business rules by themselves.
Our platform also provide the ability to easily configure and manage any future pandemic and travel management .
What's next for Cognitonic Travel Bubble Management System
ePass generation / validation, self assessment (screening), travel bubble management and travel advise are production ready with initial data configuration for specific country and states. Any country or state can do initial setup and deploy it to production within days. New travel bubbles can be configured in minutes.
Cognitonic Travel Bubble Management System is configured using Pega low code platform and utilizing data driven design.
Our solution utilises Pega survey capabilities for screening questionnaire which makes it completely configurable for initial set-up for any countries / states should they choose to use this component.
This is utilising the Pega cosmos design system, it is multi device and cross platform supported and can be deployed for all devices.
Solution is built to support for any future Pandemic use cases where such situation arises.
Future extension
:
Real time monitoring of suspect and/or confirmed cases through Mob app or wearable tracking devices.
Wizard based Pandemic management case is to setup advice, questionnaire, thresholds, Risk rating algorithm , Self-isolation and quarantine rules for any future pandemic.
API enablement for hospital and test centers .
Built With
cosmos
pegainfinity
Try it out
aozks3vl.pegace.net
cognitonic.sharepoint.com | Cognitonic Travel Bubble Management System | A unique solution to help countries to minimize the health and economy impact due to Covid-19 by allowing them to configure and manage controlled international and domestic travel bubbles. | ['Ramakrishna Reddy Nallamilli', 'Lakshmi Supriya Gummadi', 'Mukesh Kumar'] | [] | ['cosmos', 'pegainfinity'] | 46 |
9,937 | https://devpost.com/software/malpractice-detection-via-pega-facial-recognition | The Predictors
Basic Information
Candidate id
Application Image
Inspiration
Talent is the world’s most valuable resource. During this critical time where educational institutions are unable to evaluate there students in a fair way, Professionals are concerned about enhancing their careers as test centers struggle with safety measures and seat availability which thereby affects personal & organization's growth. Our team saw this as a real problem which if not addressed today will have a long-term impact in the growth and prosperity of individual professionals and organizations. Our team has come up with an application "The Supervisor" to address this problem using Pega.
What it does
The application will manage and monitor the entire assessment in real time, screens candidate, reports and disqualifies candidates carrying out malpractice thereby preventing possible candidate malpractice and ensuring exam is carried out in a fair way. This application will allow may students and professionals to take up examinations and assessments safely & easily from their homes so that they make their career progression even in this unprecedented situation .
How we built it
"The Supervisor" application is built leveraging Pega and Amazon Rekognition
Challenges we ran into
One of the challenges that we encountered were to decide the approach for image recognition, We tried using python
for this which didn't yield accurate results and then with a Microsoft service and finally decided to go ahead with "Amazon Rekognition". Getting to screen candidates at real time is one more challenge that we faced.
Accomplishments that we're proud of
Our team takes the pride of providing students, professionals and organisations a way to continue their career progression and employees development programs in this critical time.
What we learned:
Social learning:
--Through our initial research we found the various pain points of students, professionals and test centers and made efforts to solve their problem
Tech learning:
--Learnt about various facial recognition services exposed by various organizations like Amazon and Microsoft
What's next for The Supervisor
The way educational Institutions operate will dramatically change Post Covid-19 and there is a high likely chance most of them will go through a digital transformation journey. This Examination & Certification Monitoring Application can be adopted in large by educational institutions and test centers thereby enabling users to take assessments remotely and also ensuring assessments are conducted in a fair way. A seamless experience for the users for end users indeed! There is also a scope to extend this application for identity verification of candidates, marking attendance and as a way to provide access to various other secured applications. Using this application will drastically reduce the operating cost as now we don't need a physical space or an invigilator for assessments.
Built With
pega
Try it out
10.225.94.197
pega.box.com | The Supervisor-An end to end assessment monitoring app | An app to scrutinize candidate authenticity & monitor assessment in real time leveraging Pega's Case management & Amazon Facial Rekognition. Allowing students&professionals continue career progression | ['Animesh Patnaik', 'Ganesh Damisetty', 'Priyabrata Nath', 'Ganesh Jayaraman', 'Ankur Bansal', 'Subramanyam Kopparam', 'Ramya Shetty'] | [] | ['pega'] | 47 |
9,937 | https://devpost.com/software/pega-peer-review | Component description and instructions
Review Task List and Review Explorer
Best practices at fingertips
Review a Rule
Contextual Review Conversation
Fix the Rule selecting it by status in Review Explorer
Complete Review By Reviewing Changed Rules in Review Explorer
Inspiration
DevOps is being a topic for many organizations nowadays. Imagine you have set up a pipeline which works like a charm.
So, how do you ensure your it doesn't deliver a rubbish to you production at the speed of light?
Have you seen suboptimal design decisions working in the production, and question yourself - how did we end up with this solution?
Or maybe, as a product owner, you want to distribute the knowledge in the team to ensure a support continuity, especially in such unprecedented times.
How we approach it
Our solution to the issues mentioned is a Peer Review practice.
We have been supporting customers for extended periods of time, and we truly believe this practice can help achieve a lot:
Promote best practices & govern design
Distribute knowledge & Improve co-production
Socialize quality by dragging team members into regular quality discussions
… and especially with the remote mode of operation that we have now.
Challenges we ran into
We usually encourage teams to use Pega branch reviews,…
… but we have to admit there is a huge space for improvement.
So we gathered together, despite the distance between the Munich and Moscow, and applied the design thinking to prototype and build our MLP…
Minimalistic, but very Lovely Product :)
What it does
Peer Review Component provides the following features:
Streamlined
Review process
with stages
Review Tasklist
provides visibility of work
Intuitive
Review Explorer
allows to easily navigate branch content and track review progress
Contextual review conversation
in a Rule form
Best practices
at fingertips in a History tab of rules
Accomplishments that we're proud of
Solution has naturally extended existing Pega Platform functionality.
Review Explorer
in the Application Explorer is perfect, it's so easy to use and it looks like it was always there.
What we learned
Design thinking approach is a great way to justify, plan and scope the work and to define the MLP.
UX is crucial; properly selected small changes in the UX can become great improvements for the end-users.
What's next for Pega Peer Review
Peer Review component is now pending approval in the Pega Marketplace, so it should be available for the community soon.
We are very happy how this worked out and are excited to continue our journey.
We have a full backlog of features to be implemented
… and we are planning continue until Infinity!
Built With
design
designthinking
pega
thinking
Try it out
pprpublic.s3.eu-central-1.amazonaws.com | Pega Peer Review Component | Pega Peer Review Component moves team collaboration to the next level facilitating contextual peer review process. | ['Oleg Lapshin', 'Kirill Marinichev'] | [] | ['design', 'designthinking', 'pega', 'thinking'] | 48 |
9,937 | https://devpost.com/software/dynamic-process-creator | What it does
Pega framework to quickly adopt changes in process. As a response to current COVID situation companies may wanted to change/introduce new process with Zero code change. We think our framework will help them.
Built With
pega
Try it out
pega.southindia.cloudapp.azure.com | Dynamic Process Creator | Pega framework is helpful to build process and UI with no code change. We have to add rows in few table to enable the process and UI | ['Swami Nathan'] | [] | ['pega'] | 49 |
9,937 | https://devpost.com/software/dailyco-video-component | Inspiration - Zoom,Google meet can do. why Pega cant have this. that made us to inspire and pitch inside.
What it does - Interacting with user and understand their problem and provide solution
Use cases like :
Tele caller resolving their issue by seeing the product of customer,
Patient can interact and get information with doctor,
Education platform can be used to it,
Live interaction can helps to solve lot of problems.
How we built it - During this situation Like Covid if we have any live interaction channel we can resolve multiple problems ( this can be flexible for all domains)
Challenges we ran into - Understanding real time problems to get the solution. finally we found real time live interaction will be one stop solution to resolve it
Accomplishments that we are proud to part of this development and ideas to improve lot of customers problem can be resolved through this
What we learned new things, multiple angle thinking, how pega is flexible more than this we learned from personally and understood that participation is key, success doesn't matter challenging is more satisfactions
What's next for DailyCo Video Component
One stop solution for customer
Pega's next big milestone
Build for change
Built With
dailyco
pega
Try it out
drive.google.com | DailyCo Video Component | Live video Assistant | ['Pavithra M', 'SOLLETI SAIDIVYA', 'Pushkala Sadhu', 'Karthick Murugesan', 'Arun Sabari', 'Subha Anandhi'] | [] | ['dailyco', 'pega'] | 50 |
9,937 | https://devpost.com/software/test-xjtrhi | Customer Journey
Inspiration :
Given the global pandemic situation, the need is more than ever for IT systems to support the economic recovery initiatives taken up by Governments aimed at creating a positive impact on the communities across the globe. This sets up the stage for mature platforms like Pega to showcase the ability to build applications that demonstrate the needed business agility to keep pace with the evolving economic situations. Being a Platinum Partner of Pega, NIIT Incessant considers this as an ideal opportunity to leverage the power of the Pega Infinity Platform to help deliver a Business Solution that has the potential to create a lasting impact on economies across the world
What it does:
The Special Purpose Business Loans solution built on Pega Infinity provides a platform for Banks to keep up with the volatile business situation and helps adapt to changing government policies. This solution provides a scalable foundation to be able to build/deploy processes in highly agile business environments to ensure that the needed impact is delivered in a time-sensitive manner
How I built it:
I composed a team of 8 people at NIIT Incessant to work on this application as part of the Hackathon submission. We leveraged most of the OOTB features of the Pega Infinity platform (elaborated in the design document). We took special care in creating various components of the application in a pluggable/extensible manner to facilitate needed specializations when the solution gets deployed for a given customer. We ensured that the application is pre-built to such an extent that deploying to any new customer shouldn’t take more than a couple of weeks. This ensures that the solution delivers real value and delivers relevant business outcomes in demanding situations
Challenges I ran into:
Geographically distributed team with everyone working from home, we were able to overcome this by making use of collaboration tools like Microsoft Teams, Agile workbench to track work.
We faced a lot of functional challenges in understanding the SBA special loan assistance process as it was constantly evolving with new laws and amendments. To overcome that we have delegated quite a lot of functionality to aid in quick changes.
Analyzing and understanding the SBA eTran systems functioning, were able to overcome that by reaching out to the various members of our practice to get details.
OCR implementation and application.
We were unable to test mashup and OCR on the cloud as we didn’t have access to the platform in the Pega provided cloud.
Accomplishments that I'm proud of:
Given our domain knowledge in the BFS space, I’m proud of our ability to turnaround an end-to-end business solution that is 60-70% pre-built, in a matter of weeks. We are also proud about the fact that we could deliver a scalable application that helps address an ongoing problem that the world faces during these trying times
What I learned:
I learned more about the extreme agility of the Pega Infinity platform in its capability to deliver solutions that are scalable and extensible. I also learned the real value of a true low-code platform provides to its customers in terms of time-to-market and business value
What's next for testing:
The testing document has been shared with the
[email protected]
email address which has access to the private repo.
Built With
ai
docusign
esignature
mashup
mobile
pega
predictive-analytics | Pega Special Purpose Business Loan | The solution equips small Lenders to gain instant burst capacity & customer trust by expediting the Special Loan Origination process with high accuracy, while adhering to required federal regulations. | ['Imranullah Dawoodbasha', 'Ashish Asrani', 'Sajal Banerjee', 'Manikanteswara rao Chinthakula', 'Praveen Kammili', 'Naga Ramu Gottam', 'Lovaraju Pentaboina', 'Sasanka Reddivari'] | [] | ['ai', 'docusign', 'esignature', 'mashup', 'mobile', 'pega', 'predictive-analytics'] | 51 |
9,937 | https://devpost.com/software/ok2s-ok-to-social | Social screening
Parent case type - Match availability with schedule
Mobile screenshot of Social screening1
Mobile screenshot of Social screening 2
Inspiration
Name: OK2S – OK 2 Social
Today we are challenged with COVID-19 realities. All physical locations, organizations and workplaces are asking their employees and patrons to complete a COVID-19 screening form to (1) provide physical health information and (2) temperature reading every time they plan to enter or enter a location. The document facilitates the liability issues around social distancing and required individuals to take personal responsibility of the well-being of themselves and others.
What it does
First an organization will have a facility and space, and people who need to utilize or be active in that space. Using availability and people needs, the app should create a schedule. Then send the person scheduled to be in a public space an email with a form to provide health information. If healthy, the person confirms the social connect and the app updates the schedule. This is the idea, but what I have built is not doing all of this, need some more tech SMEs to get this done.
How I built it
On a dev server I have access to as a Pega employee. I build it in AppStudio and DevStudio but it has no integrations or any data, it is just a backbone. [I provided the link, sure the dev team has access, notify if I need to provide access]
Challenges I ran into
Data and integrations. Time.
Accomplishments that I'm proud of
Getting an shell together that represent the idea.
What I learned
I have a lot to learn!
What's next for OK2S - OK to Social
Some solutions are already being put into place to facilitate the reality, but the market is not saturated and the really big benefit of automating this is capturing the data to appropriately take action and notify when illness is detected in the workplace. An organization can quickly find the people who were in contact with someone reporting their illness.
Built With
casetypes
pega
ui
Try it out
10.60.215.138 | OK2S - OK to Social | Complete a COVID-19 screening form to (1) provide physical health information and (2) temperature reading every time they plan to enter or enter a location. | ['Elmarie Esser'] | [] | ['casetypes', 'pega', 'ui'] | 52 |
9,937 | https://devpost.com/software/team-connect | Logo
Architecture
Team Connect Screenshot
Inspiration
Team Connect is inspired by the daily challenges we face when connecting with fellow colleagues on a daily basis with the traditional communication tools available to us. In a post
COVID
world we are increasingly dependent on enterprise messaging platforms. However due to bandwidth issues on the server and connectivity to the server often we face call drops and outages. So the inspiration was to create an additional / alternative communication tool that would be embedded into PEGA that as developers and end users we can use to communicate with our colleagues that would be simply peer to peer and not dependent on the strained communication platform servers
What it does
Team Connect is a PEGA component that allows end users on PEGA portal to engage with each other using real time text chat and audio calls
How I built it
Team Connect was built purely on the PEGA 8 Community Edition server enabled for the Hackathon. I did some digging into webRTC standards and APIs and decided on Peer JS as a suitable candidate to extend the capability to PEGA. After that it was an extremely exciting exercise in combining front end technology like React with webRTC APIs in PeerJS and integrating them on to the PEGA 8 platform.
Challenges I ran into
The main challenge was to seamlessly integrate the React component with PEGA. While I learnt React using Functional components, I had to refactor all of that using React class components to integrate with PEGA. Perhaps there may be a way around this, but did not have the time to research that fully. Something I intend to explore post
the submission.
Accomplishments that I'm proud of
I entered the hackathon late and had little more than a week to implement the idea. Given that I am quite happy that the outcome is a minimum viable product that can be deployed and utilized by consumers of the component.
What I learned
I mainly learnt how to integrate React with existing PEGA UI and use the Pega Notifications Channel for broadcasting information across PEGA users.
What's next for Team Connect
There are many features that are in the pipeline for team connect -
Markdown support for text chat
Support for binary images like Emojis, Likes embedded within the text
Screen share and Video call capability
Group chats and conferences
Using Kafka streams to store and access chat history
Built With
peerjs
pega
react
Try it out
github.com | Team Connect | A simple and fast communication tool for users on Pega Infinity platforms, | ['Gourab Lahiri'] | [] | ['peerjs', 'pega', 'react'] | 53 |
9,937 | https://devpost.com/software/omni-channel-virtual-banking | Inspiration
In the current COVID-19 situation, most of the branch related operations have become extremely difficult and hard to cope with for our day-to-day usual requests. Most of the branches remain closed and people want to follow safety measures that in-turn increases the duration to fulfil a request if they have any.
This led to our idea of Omni-Channel "Virtual Banking".
What it does
Imagine if we were to have a Virtual Bank and it does all operations that are performed in a branch but in a much effective manner with less time, less hassle and above all from wherever we are. Some of the benefits are as follows
Any form of device can be used to bank virtually (i.e., Laptop, mobile, tablet, desktop etc)
Customer can find a nearest branch within a mile radius and will be able to see slot availability based on red(Extremely busy), Yellow (moderate busy) and Green (Available) and then choose to fill a form for the purpose of visit to join a queue.
Virtual queue placement with notification. Customer will join a virtual queue and will be notified if he is next, thus saving a lot of time
Video conference ,audio conference and web chat facilities to have real time interaction with the customer and branch colleague.
Skill based routing (ex: If translator is required, then a colleague with that particular skill will be assigned to the customer)
Automated background API calls or service calls to authorise the customer while in virtual queue, thus when the case is assigned to branch colleague they already know what is the purpose of customer visit and all KYC checks done.
Microservices based architecture to call APIs based on the options selected by customer thus reusable across applications.
How we built it
The prototype was built using the following tools
PEGA PRPC 8.4 community edition
Postgres DB
Tomcat Application server
Challenges we ran into
Lack of funding and PEGA OOTB capabilities for some of the features like integration with conference facility. We had limited time to work on the prototype.
Accomplishments that we're proud of
Building a minimal prototype to visualize our idea
What we learned
Pega 8.4 features gives leverage to take advantage of COSMOS UI which could present a good digital experience.
With focus to More AI and ML based application the future is going to be virtual.
What's next for Omni Channel Virtual Banking
AI and Machine Learning capabilities can be exploited to provided seamless service to customer.
With easy Integration of Video conferencing tool with Bank Colleague's calendar , the experience of customer could be highly personalised. This would also eliminate the risk being posed by laws, making banking operation to completely go virtual.
Built With
8.4
microservice
pega
Try it out
drive.google.com | Omni Channel Virtual Banking | "Virtual Banking" the future of Banking. | ['Bhuvaneshwaran Srinivasan', 'Vijay Laxmi Shukla', 'Pradeep Shukla', 'Manju Bashini Thanjavur Sathish', 'Anurag Yadav'] | [] | ['8.4', 'microservice', 'pega'] | 54 |
9,937 | https://devpost.com/software/customer-service-in-the-world-of-covid | Next-Gen Virtual Customer service built for - Live Interaction||Virtual Sales & Service||Build Trust||Stay Compliant
Inspiration
I purchased a laptop a few months back and was struggling to get it serviced since due to COVID, all the service centers were closed in Amsterdam. I dropped the email and connected with the manufacturer to explain my issues. It was addressed, but somehow I felt a disconnect since I could not visit the actual Service Center and explain my issues. I thought that why can't we have something called a branchless virtual service center that can help me connect with a CSR on the go. I am working with Pega for the last 10 years and when it is customer service, i always think about our solutions. Hence, it fits perfectly to solve the existing crisis situation.
What it does
Technically It seamlessly connects with any Pega Customer Service Platform. In terms of business, it bridges the huge gap between Business and Customer. Due to the current pandemic situation, many organizations are lacking direct connection with the customers and missing out on empathy and personalization. Bringing a live video interaction over a live chat makes the most important difference in the customer experience in the COVID world. We named it Real-Time Interaction which works seamlessly with existing Pega platforms. On the Business side, it provides flexibility for the business to continue BAU with their existing CSR teams working remotely and help customers solving their key concerns by connecting in Person.
Demo Project Journey -
In the project journey, a Customer is using Pega Chat to interact with Chat Bot initially and then the Chat Bot based on the inputs (NLP) routes the conversation to a Human Agent. The Human Agent then chats with the customer and understands the issue from customer . CSR (Human Agent) then enables the RTI (Real TIme Interation) feature to connect with the customer virtually , since the customer could not visit the branch and have some concerns regarding the product he is using. The seamless journey of Interaction between a Customer and a Healthcare CSR is captured in the video shared with this project.
Real-Time Interaction often looks to assist the CSR in one of these main areas:
Understand customer needs
-When the customer is looking for assistance
-When the customer is unable to visit a branch/office
-Empathize
-Build Trust and Interact Real-Time
Connect with individual Customer
-Provide Service as required
-Cross-sell / Upsell new Products
-Seamless & Branchless Onboarding
-Recommend suitable products based on customer needs
-Product packaging/bundling
Competitive pricing
-Looking beyond regular Customer Service
-Provide insights with low Operation Costs (Brach/set
up)
-Capture / Record Customer interaction history
How we built it
-Created a custom health care application "Med" built on CareManagement_Sample
-Added a CSHCSelfService application on top of custom-built app Med and OOTB CSSelfService
-Added Custom-CSSelfService ruleset to CSHCSelfService application.
-Configured chat server, Queue
-Made use of CSHC IVA bot
-Modified chat window section to include a Video call button to initiate a call to the cloud where the script is hosted
-Included page push to initiate a call to the cloud where the script is hosted
-Pushed the page push request to the customer to initiate the video call
-We have made use of WebRTC for real-time communication, the script can be accessed in Github, link provided in the link section. The Js is deployed in heroku.
Challenges we ran into
-Faced challenges in making the Webchat work
-Installing SSL in AWS cloud
Accomplishments that we're proud of
RTI worked seamlessly without any software or hardware dependencies. We can easily deploy it to any existing Pega Platform or can easily package it will future Pega platform strategic applications for Customer Service.
What we learned
Pega is built for change and Pega can be used to build solutions that can help create new avenues of doing business with more Customer-Centric journeys.
What's next
For Next-Gen Virtual Customer service in the world of Covid-19 - Integrating with multiple strategic Pega applications we can make Customer Service a much stronger proposition with the most advanced chat feature that Pega has offered to its client.
Testing
Code accessible only for
[email protected]
Built With
javascript
node.js
pega | Next-Gen Virtual Customer service in the world of Covid-19 | Live interaction over a live video chat makes the most important difference in the customer experience in current and post COVID world.Organizations are lacking direct connection with the customers. | ['Manoj Sundar Rajendran', 'Koustav Dhar', 'Balakrishna Chirumamilla'] | [] | ['javascript', 'node.js', 'pega'] | 55 |
9,937 | https://devpost.com/software/testing-1e4cbj | Sanitize Workplace flow
Employee CheckIn flow
Manager Schedule flow
Inspiration:
We had a passion always on product development. With this application it turned to reality.
We thought about few concepts that can be implemented:
Automating Paycheck Protection Program for small business.
Streamline the process for Pandemic Un-Employment Insurance claims.
Come up with an E-Learning process to conduct exams and classes online using Pega case management features.
Return to Work – This application will automate and streamline the process to handle the return to work process seamlessly for all their employees and making sure that the workplace is sanitized and hygienic for employees.
Out of these, we went on implementing Return to Work application which addresses all the three problem statements defined for this hackathon :
• Bridge the gap between distributed people and systems
• Accelerate assistance and service to those in need
• Adapt quickly to new challenges and circumstances
What it does
Provide a safe, employee-ready workplace with Pega Case management specific work flow
Simplify the process using workflows involved with returning to the workplace.
The return to Work app with its different case types and dashboard help manage essential needs and services for seamless return.
Return to work flow encompasses the following Processes:
Employee Check in
Manager Schedule
Real Estate flow
Employee Volunteer Work Flow
How I built it
This application is built using Pega Case Management, API’s, Chatbot, Mashup
Challenges I ran into:
Creating the process map for this application.
Thought to integrate with Thermometer API's to record temperature but we had some exceptions with third party service rest.
Accomplishments that I'm proud of
This is the first product built and this will serve all the organizations in the coming days.
What I learned
Product development and how to conceptualize the product
What's next for testing
All the application built has a detailed instruction on how to test the application.
Built With
chatbots
mashup
twilio
usps-web-tools-api
workday
Try it out
drive.google.com | Application For Scheduling and Planning to Return to Work | Return to Work application allows organizations to automate and streamline the process of scheduling return to work, employee E-Check In Process, Sanitizing work places and assist in employee requests | ['Vittal Sai Srimattirumala', 'Krishnakishore Ramachandruni', 'Aaron Bosley', 'Mohammad Ruknuddin'] | [] | ['chatbots', 'mashup', 'twilio', 'usps-web-tools-api', 'workday'] | 56 |
9,937 | https://devpost.com/software/pay-it-forward-x8nt2u | Employee Directory
Grocery Deals
Local Food Pantries
Inspiration
I was inspired to design the Pay It Forward application after reading countless articles of how people were recovering from the recent impact on the economy. I tried to look at different ways to provide a solution for employers, employees, and the day to day person. I also built into the application a component that I knew I would look forward to using as a test to make sure that the application was in fact helpful. The application name and even the random quote generator were included to inspire the user as they are using the application.
What it does
The Pay It Forward application can be used 3 different ways, as an employer, an employee, or as a family member. If you are using the application as a Family Member, this piece was designed to help users save money and cut costs on groceries. We utilize the Pega Robotics component and have integrated it with Pega to allow users to enter their grocery list and find deals in their area. The best part of this component, which happens to be the component that I use the most is that you can use it in any state, you are not limited by location. Upon the bot completing and finding deals which only takes about 1-2 mins, your results will be displayed in Pega and you can even email the list to friends or colleagues, or your kids who have never quite been into looking at the grocery deals in the mail. This component eliminates users having to wait to receive a circular in the mail of grocery items on sale or even googling items on sale in their area. They can find grocery deals in a matter of minutes and email these deals to themselves in a matter of minutes. The second component of Pay It Forward is the Employee component which allows employees who are interested in volunteering or finding local food pantries in the area to find all food pantries at the click of a button. Users enter their city and state (once again, you can utilize this application component in any state), after clicking submit another piece of our Pega Robotics application will find all food pantries and return that list directly back to the users in Pega. Users are also able to email this list at the click of a button to anyone they choose. The final component of the Pay It Forward application is the Employer component. We built this component to ensure that any user would find the Pay It Forward application useful, that includes CEOS, or other employers who may have had to recently let go some employees, but still wanted to help them. Upon selecting to use the application as an Employer, an employee directory is displayed of previous employees for a particular company. This directory include the employee's name, highlights of their career, their industry and location, all of which a recruiter or employer can filter on. Should an employer or viewer of the directory take particular interest in a candidate, they can contact them on LinkedIn directly using the "View on LinkedIn" link in the employee directory. We cam up with this component after researching how employers were helping employees in need, even if they couldn't provide severance.
How I built it
I built the application to be centered around Pega, so a user never has to leave the main Pega application and all data and information comes to them. I began with a Pega workflow and then built the out of the box components with Pega Robotics to retrieve the grocery deals and food pantries and also used Soap UI to test the random quote generator before using the REST connector component in Pega to generate and display the quote on the Pay It Forward application.
Challenges I ran into
Were primarily in the Pega UI. I haven't used all of the Pega UI components on a regular basis, but I had some issues initially building the RESt connector, I resolved this by changing the parameters and was finally able to set a GET method with the connector. I also had issues storing the grocery list items in pega to a clipboard value, but this was resolved after figuring out how to access the list properties. I had some issues pulling back the grocery deals items in a clean format and deciding how to best display that data to the user. I had a few challenges with the Employee Directory. I wanted to be able to allow visitors of the directory to click on a link that would take them to the users profile, but here I discovered how to utilize the "Open URL in Window" action to display the users custom LinkedIn page. I ran into some trouble finding the right action to display the employee's highlights and name in the modal dialog, but I ended up finding the right action. Most of these issues were resolved by researching on the Pega forums and looking at how users resolved these issues in the past.
Accomplishments that I'm proud of
I'm so proud of the Grocery Deals component because I am able to use it. I have used it in the past after building it and I used that as an indicator that it will be helpful for so many others. I love that it helps users save money and time and that it doesn't take long. I'm also proud of the Employee Directory because of how simple it is for employers to upload a list and for all of that data to be formatted in a nice table on Pega. I love that potential recruiters and employers can also directly reach out to an employee that they believe may be a good fit all at the click of their mouse. With Pega at the center I had never really explored all of the possibilities that leveraging these different components and activities would bring, but I think that this application can still be used 10 years from now, and I hope that others find it useful outside of pandemics or special circumstances.
What I learned
I learned how to use more of Pega's internal features, activities, actions, and UI elements.
What's next for Pay It Forward
I'd like to add a recipe recommendation piece to the Grocery Deals component that would recommend recipes based on a user's grocery list. I also would like to have Pega return to the user the best deals on their grocery list item, in the robotic automation the robot would do the math and only return a deal on a grocery item that would cost the user the least amount of money instead of returning all deals on a particular item. I think it would be nice to make the UI look a little friendlier as well, maybe incorporate more media components. I think it would also be nice to integrate a component for shoppers who don't necessarily begin with a shopping list, but design their list based on seasonal items or deals they see in circulars. Definitely would like to add a feature where upon viewing the application as a Family Member, users can see an array of deals on common grocery items, this piece would also be better if there were more images as well.
Built With
api
pega
robotics
Try it out
drive.google.com
drive.google.com | Pay It Forward | Pay It Forward allows anyone needing a starting point to navigate this new normal leverage helpful resources through Pega. | ['Nia Christian'] | [] | ['api', 'pega', 'robotics'] | 57 |
9,937 | https://devpost.com/software/rapid-response-team-4nui7f | Identifying Geo Location
Available Services
Selected Services
Appointment Scheduling
Engineer Portal
Access to Content
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the
ReadMe
* document in GitHub for accessing all contents.
What inspired us?
We drew our inspiration from the problems we faced due to the lockdown imposed by governments as a result of the current COVID crisis and the
power of technology leveraging Internet of Things (IoT)
to solve those problems. Imagine the situation for someone whose boiler has gone dead while living in an area with sub-zero temperatures and facing lockdown imposition. Quiet petrifying isn’t it, as it will be extremely challenging for the customer to raise a service request with the company for getting his boiler repaired since company’s call centers are having huge call wait times and limited availability of the technicians to visit the customer premises and fix the issue. Our original idea was to conceptualize a boiler with an IoT sensor that can emit signals in case of any malfunctioning. The emitted signals can be processed by
Pega’s Event Strategy Manager
to automatically create a service case and
send email/sms notification
to the customer. In the backend, the
business rules engine can automatically
prioritize
the service request based on the data points like customer’s pin code, prevailing weather conditions and lockdown restrictions at the customer’s location by having
Google API integration
with relevant data providers. As it was difficult to build the IoT based integration in such short span of time time, we have developed a Chat-Bot based solution for the customer to raise his service request. The remaining concept remains the same with the only difference that customer needs to raise the service request manually via the Chat Bot instead of automatic service request creation using IoT technology. The ultimate goal of our idea is to offer a
complete end to end frictionless interaction experience
to the customer.
What we learned?
No one was prepared for the magnitude and scale of the economic crisis facing the world today. As a result, not even the smartest, savviest and customer centric company had ever prepared their service offerings for this kind of a global pandemic. But the COVID crisis has pressed the reset button, with significant implications for all the companies. So as an IT service provide company and Pega’s platinum partner, it is our duty to educate customers about the benefits of Digital Transformation projects that provides improvements in productivity, customer engagement and prepare them to face the uncertain future
Challenges
1) It was challenging to collect worldwide data regarding Covid crisis as none of the sites is readily available to provide service of required relevant data and we could get that as csv file only ... also importing all those data with no restrictions of boundaries in the pega internal data base was quite difficult and made the task even more challenging and consumed huge amount of time
2 ) Time Constraints in developing the demo, as we have to meet the deadlines for our current customer engagements
3) To collect and align the pictures related to various services also consumed lot of time.
Built With
pega
Try it out
ew6l14ot.pegace.net
github.com | Rapid Response Team | This solution for any service industry ,It will empathizes with the customer who are already suffering due to crisis by automating their service requests thereby reducing their pain and wait times | ['Abhisek Jhunjhunwala', 'Rama krishnan Ganesh', 'Balaji Perumal', 'Megala N', 'haritha vivekanandan', 'Mohamed Shafi'] | [] | ['pega'] | 58 |
9,937 | https://devpost.com/software/proworkman | Concept
Access to Content
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the **ReadMe
* document in GitHub for accessing all contents.*
Inspiration
Recently there has been a lot of discussion around distributed work environment, borderless, secure workplaces right from safety of home. It seemed that it solved all problems till recently the cyclone Amphan hit eastern coast of India on 16th May. It was like a wake up call for me. There was no electricity, internet, phone network for straight 4 days and I was completely out of network amid COVID lockdown.
Somehow, I informed my leadership and they were cooperative enough - there were some work that I had to
delegate
some work to others which
couldn't be avoided
, I
cancelled
few
less important
meetings,
rescheduled
some tasks
for a later date
etc.
This made me think that impact of a disaster can be in many ways and with a reduced work capacity, there's a need for a proactive work load planning and management is required so that system doesn't choke and keeps on delivering on the most important fronts while compromising on few.
What it does
ProactiveWorkloadManager intends to flattens to the Workload curve...
It leverages Pega platform to switch on to a Business Continuity (
BC
) mode
Predicts
the
availability status
of associates based on their location information and the information of impacted locations
Provides ability of
connecting
with the associates on a continual basis and
listen
to their response to update workforce availability status at real time
Utilize a decision model which considers workforce availability status (reduced headcount) & workload trend to recommend revised Urgency model, SLA(s) & re-prioritized tasks
Enable workforce leaders to
review and implement
the modified
Urgency model
so that the workload
curve can be flattened
and the reduced workforce doesn't get overwhelmed with an effective increased workload.
Continue on the
BC
mode and notify to switch to BAU mode once the workforce members reports as Available and availability reaches a threshold to indicate restoration of normalcy
Being able to predict/ assess reduction in capacity and modulate workload based on systematic decision capability enables Business Continuity.
How we built it
The build process went pretty much like how a regular project.
It started with the idea finalization round approx 3 weeks back
We laid down the story line
Each act in the story was translated into a technical user story
It was a daily build-demo-feedback-build cycle
Challenges we ran into
Amid the lockdown and this New Normal situation, the most difficult challenge was to get everybody together and on the same page
Discussions which used to be closed within 1 hr of in-person meeting now requires multiple iterations over Webex & MS Teams meetings
With a short timeline, it was difficult to visualize how we want to show case our idea - everyone in the team had their individual thought process and it was quite difficult to decide on a specific line of thought when we started discussing on virtual meetings. We lost a lot of productive hours in visualizing the final presentation.
Each associate has their regular day-job, client deliverable, meetings etc. - it was challenging for everybody to put a consistent/ constant attention
Accomplishments that we're proud of
In spite of the remote teams, short timeline, difference of opinions, client deliverable(s) we're able touch the finish line - that's gives a lot of satisfaction
We did at least ~30 hours of virtual meetings
We never did a video presentation before, it opened up a new skill area we never thought of - acting skills, dialog deliveries
What we learned
Co-location is still one of most effective ways to achieve stuff
Sometimes even a 15-min stopover at a fellow colleagues' desk can save a lot time by not letting the developers deviate from the aligned direction - whereas now the nearest stopover is the next virtual meeting
To survive in the new normal we need to think of better ways of collaboration not just meeting virtually over a scheduled Outlook meeting
What's next for ProactiveWorkloadManager
Currently it's a manual input for indicating the impacted locations, as a next step we would like to derive that from an official Weather Service API
Include a more realistic (and potentially complicated) model taking in more real world parameters into consideration to evaluate the Urgency model
Built With
pega
Try it out
cts-pega-hackathon.eastus.cloudapp.azure.com
github.com | Proactive Workload Manager | Proactive Workload Management during Disaster - Powered by Pega | ['Sumeru Saha', 'Parshant Sharma', 'Naveen V', 'Gaurav Kumar', 'Manpreet Bagga'] | [] | ['pega'] | 59 |
9,937 | https://devpost.com/software/askmaya-the-virtual-financial-advisor | Bank Portal for Back End users
NextGenDigital Bank Portal
Interaction with MAYA
Access to Content
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the **ReadMe
* document in GitHub for accessing all contents.*
Inspiration
In case of natural calamity (COVID19, IRMA etc) when the regular customer help desk is not working in it’s full capacity, with increased service requests for card disputes, institutions may find difficulty to provide the necessary support to their customers. This actually results into a long queue on phone channel for the stressed out customers and loss of faith to the bank. This actually inspired us to think for a digital solution which can help both customer and bank to tackle such situations
What it does
“AskMAYA” the virtual financial advisor has been conceptualized to support bank's customers 24X7 to raise the card dispute from their laptop or smart devices. This virtual financial advisor asks bare minimum questions to the customer and uses the Pega Smart Dispute for Issuer framework to create the dispute making life simpler for the customers.
How I built it
We wanted a flexible and salable solution which can be built rapidly to help users.
To Build the solution we choose Pega's Intelligent Virtual Assistant provided with WebChatBot capability which has been integrated with Smart Dispute for Issuer Framework. The chatbot has a threshold value of $ 50 on dispute amount, below which cases will be resolved as small dollar write off.
Challenges I ran into
To predict the customer response and let the bot act accordingly
Integrate Chatbot with Smart Dispute Framework for Issuer
Accomplishments that I'm proud of
In just 3 weeks, we developed this Pega’s Build for Change® solution
It will help customers to raise the disputes directly from their smart devices
Banks will be able to optimize their helpdesk workforce
What I learned
How an interactive chatbot can be implemented with Pega 8.x
How this solution can be leveraged to different service requests for the customers
What's next for AskMaya the Virtual Financial Advisor
Extend the application to use voice channel given by third party like Alexa, Google voice etc
Chatbot should be capable of handling all the dispute reasons
Built With
pega-v8.2.2
smart-dispute-framework-for-issuer-7.41
webchatbot-8
Try it out
github.com | AskMAYA the Virtual Financial Advisor | “AskMAYA”, the virtual financial advisor supports their customer to raise the card dispute during natural calamity using Smart Dispute Framework for issuer | ['Sanjoy Mukherjee', 'Kaustav Dutta', 'sudipta sur', 'kaustav guha', 'Vikash Singhi'] | [] | ['pega-v8.2.2', 'smart-dispute-framework-for-issuer-7.41', 'webchatbot-8'] | 60 |
9,937 | https://devpost.com/software/ping-healthchecks | Inspiration
Everyday, there are people in need. Everyday, healthcare organizations design programs to help people in need. Too often, the people and the programs fail to connect. Organizations spam members with offers and reminders. Information gathering is often cumbersome. Results are often aggregated, failing to solve the immediate needs of individuals. The lack of trust created by these practices makes members less likely to reach out to healthcare organizations when they need them. And, organizational silos mean they sometimes don’t get what they need when they do. Global challenges like the COVID 19 pandemic make the need to solve this problem urgent.
We wanted to design a solution that would allow healthcare organizations to reach their members proactively, gain understanding of their context, and take action immediately. The solution had to be simple on its surface, low effort for the member, and scalable. And most importantly, it had to be meaningful. We wanted to design something with the potential to save a life.
What it does
The solution we designed was HealthChecks. Healthchecks sends a message (SMS, Facebook Messenger,etc.) to a member regarding a relevant topic and then asks the member to rate themselves using a 5 point scale. Based on the member’s response, Pega kicks off processes to solve immediate needs, provides information, and collects data to inform analytics and AI. Using Pega to manage the outreach and intervention until direct human engagement is required allows us to provide meaningful interaction at scale with minimal effort costs. Using simple messages in an interactive channel allows us to avoid PHI concerns and cut through the noise, reaching members where they are.
In our video, you will see us check on the mental health of members during the COVID crisis. A low response results in immediate action, connecting a member with a behavioral health specialist. A high response results in a simple message. A neutral response engages an adaptive model to decide between a follow-up message or direct intervention.
How we built it
Our solution was built on Pega platform 8.4 and Pega Marketing 8.4 following agile development methodology with collaboration between a product owner, LSA, and CSSA. In less than 4 weeks we went from concept to what you see in the demonstration.
First we installed Pega Marketing and built the design components such as the Context Dictionary setup, Customer class, and data model design. Then we defined the structure of the Business Issues and Proposition Groups, taking the time to imagine the full context of a healthcare payer implementation. Following that we developed the happy path components such as the data sets and flows, decision strategies, and data models, including creating data sets to drive our processes, such as on call lists, benefit data, and customer data. This was done in small iterative cycles with in-line testing and daily reviews. Finally, we incorporated the AI and behavior controls that provide proactive contextual actions according to the customer’s propensity, context and other factors.
In addition to building these core features, we also created a case manager portal to follow a full process to completion instead of stopping at message delivery and response. We also designed revision management features to allow business users to manage data. By doing this, we created a product that could be piloted in a real world environment and ensured that we didn’t miss any features that would be required for implementation.
Challenges we ran into
Since Pega 8.4 and Pega Marketing 8.4 are new releases, faced several issues
a. in running the Context Dictionary
b. setting up D-Nodes
c. running the Segmentation rules and Campaigns
d. other petite issues concerned with both inbound and outbound pega marketing
To alleviate some of these issues, we've requested and installed several hotfixes.
Accomplishments that we're proud of
A healthcare organization could decide to run our COVID BH healthcheck tomorrow with minimal configuration.
We can see the path to saving a life through reacting to an indication of mental health crisis.
We reimagined marketing as a driver of wellness.
What we learned
We learned how Pega Marketing capabilities can be applied in the healthcare space to drive wellness by automating outreach and connecting it to process, much of which may already exist. We also learned how to use AI-powered decisioning to improve our responses to member needs.
What's next for HealthChecks
We envision a full suite of healthchecks. We have designed but not yet built checks for food insecurity and medication understanding. On the horizon are healthchecks for new moms and cancer patients. We need to take our vision to reality with a healthcare organization, gathering enough real world data to truly apply the power of the AI and refine the offers. From there, we’d like to expand our healthcare vision for PegaMarketing, continuing to apply the power of its features to the management of health and wellness.
Built With
pega
pegamarketing
Try it out
drive.google.com | HealthChecks | Connecting people in need to programs that help. HealthChecks allows healthcare organizations to check on their members in real time, gain insights, and automate interventions that drive wellness. | ['Leona Rickerson', 'Goverdhan Reddy', 'Mike Gromer', 'Saraswathi Siddamredy'] | [] | ['pega', 'pegamarketing'] | 61 |
9,937 | https://devpost.com/software/team-machine-aw15lb | Inspiration
We believe Pega is not "just" for workflow applications, Pega can totally change the world with advance technologies like Data Science, Artificial Intelligence & Machine Learning
We believe future is AI and surely wants to contribute to future
What it does
Our Application fetches tweets based on hashtags from twitter and internally interacts with machine learning model wherein it'll identify the sentiment of the tweet.
How we built it
In the beginning of video they are 389 cases for “twitter case”. Here, cases are number of tweets in twitter
We created following rules for our project :
TwitterDataFlow : rule facilitate decision execution in real time
TwitterDS1(Data set) : Contains access details and search keywords( twitter hashtags)
TwitterAnalyzer : Contains Machine learning model which we created and lexicon which helps in processing of NLP.
Best F-score value means good precision
We have trained model based on the sentiment of the sentence
TwitterCase : Contains the case details, we can map multiple properties to a case
Challenges we ran into
Initially it was bit tough to create machine learning models, As we didn't knew basics of machine learning before doing this project but Pega helped us to learn real quick and it's fascinating to do NLP with Pega rather than other programming languages.
As we both have just 2 years experience and we don't know much about API's so initially it was difficult to understand about API connections between twitter and Pega application.
Accomplishments that we're proud of
Doing the new and different project which was rarely done using Pega makes us really proud and behind this project their was smart work & quality amount of time spent on learning new concepts.
Setting up a twitter API and connecting it with Pega was really good for learning and we spent most of our time training machine learning models for our tweets and their sentiment analysis, and we love to contribute AI and Data Science projects with pega in future.
What we learned
Setting twitter API with pega
Data flows
3.Text Analyzer
Machine Learning models
Simulations
Natural Language Processing
Adaptive & Predictive models
Data Sets
The good part of doing this project was we get to learn ton of new concepts
What's next for Team Machine
Initially, when we got idea about this project we didn't thought we can do this using Pega because at that time we only believed Data Science/ Machine Learning projects can only be done using programming. However when we started data science course in Pega it was really easy and it made our work simple & on top of that the only thing where we spent most of the time was training machine learning models. We strongly feel that the idea of doing AI,Data Science,Machine Learning projects with Pega is really fascinating
We are planning to do many more machine learning, Data Science and AI projects in Pega like :
Customer purchase pattern
Credit Risk
Share market analysis using monte carlo
Love to be part of Pega Family
Built With
ai
api
machine-learning
ml
natural-language-processing
pega
tweetfeel-twitter-sentiment
twitter | Team Machine | Future is here | ['Kopparti Sai Suraj', 'Ambrish Patil'] | [] | ['ai', 'api', 'machine-learning', 'ml', 'natural-language-processing', 'pega', 'tweetfeel-twitter-sentiment', 'twitter'] | 62 |
9,937 | https://devpost.com/software/remote-support-for-pega-field-service | Remote support engineer connecting with customer
CSR capturing remote support request
Remote session
Inspiration
Field Service is critical in making sure that manufacturing process runs smoothly. In the difficult times of pandemic, safety of customers and employees becomes a key issue. That is why we are proposing a solution to provide high quality service from remote, using Pega Field Service capabilities combined with AR technology. Key benefits are:
employee and customer saftey
travel expenses reduced to 0
no time for travel needed, so support can be immediate.
What it does
We extended Pega FS with:
new Remote Support virutal territory for managing engineers and dispatchers;
new Remote Work Order case type for executing remote support;
integration with AIDAR solution, that is allowing to establish remote connection from Pega app in a popup window.
How I built it
The solution is built on top of Pega Field Service version 8.3.1 - at the time when we started Field Service 8.4 was not yet available.
Accomplishments that I'm proud of
We managed to extend the application with no major changes to the existing logic - so it supports both onsite service as well as remote.
What's next for Remote Support for Pega Field Service
We are planning to extend the integration with AIDAR, connecting directly knowledge content with remote session, so that sharing information will be one click activity.
Built With
ar
pega
Try it out
40.114.151.172 | Remote Support for Pega Field Service | Extension to Pega Field Service application that is introducing remote support using augmented reality technology. | ['Jakub Prosinski'] | [] | ['ar', 'pega'] | 63 |
9,937 | https://devpost.com/software/workmate | Login screen
Create Case
User Worklist
Workmate Assistance Required
Bot processing results part1
Bot processing results part12
Next Action After bot Processing
Inspiration
In time of Pandemic or time of uncertainty everyone primary concern is safety and health Whether it is employee , Customer or Self. There are some work and roles which are overburden in this time. Like in current covid time health system and anything related to health has to work extra to ensure others safety. There are some roles which like backend support or claim processing which need to work in tandem with frontline agencies.
Remote Working is one of option where user can continue working even if office location are not available. But sometimes if it is not planned which add overhead on person and become counterproductive due to lack of access, limited time and external distractions. One of the major overhead in remote working is overload of messaging and limited resources which impacts individual productivity.
Lack of productivity not only affects operational throughput but also personal finance due to loss of per case incentive.
There is need for solution which will actually fit work as per user preferences rather than traditional constraint.
Through WorkMate which is Personal Bot on mobile we are trying to demonstrate that work can be made fit to individual preferences during tough times. It is not only useful in crisis situation but can also be used in daily life in scenarios where user wants to work on its own timings and preferences.
What it does
“Workmate” is personal mobile work assistant which can be triggered through mobile which trigger bot to complete predefined steps for the user and user only have to complete steps where judgement is required. The best thing about workmate is the whole process is completed on mobile by configurable Bot and user.
How we built it
We have created PEGA Mobile Channel and a Application that can be accessed using PEGA mobile preview App.The PEGA Application is a Cosmos application built on top of PEGA Robot Manager which can read PDF document and perform content extraction.
Once the Case is created,Users of the Application can login to the Mobile app and Process the case. During processing, based on some conditions ,the cases are assigned to a Robotic Queue. The PEGA Bot reads the Claim Document(PDF) and Claim Application to verify certain parameters.
Challenges we ran into
Authentication issues while user logs on to Mobile App
To set default robotic automation package when robot runtime starts
Extracting a field value from a pdf document using bot.
Accomplishments that we're proud of
Building an application using Bot on PEGA Mobile as it opens up a huge window of Opportunity for running processes on mobile.
What we learned
Configuring PEGA Mobile App for users.
Configure PEGA Bot for background processing
Extract contents from a PDF document using bot
What's next for WorkMate
We are planning to enhance WorkMate to Automate more processes on mobile and creating a service offering for mobile based automation.The Bot component can also be enhanced to extract from images using OCR.
Built With
mobile
pega
robotics
Try it out
lmko3dg6.pegace.net | WorkMate | Remote working redefined using personal Mobile Bot.Happy working without boundaries anytime anywhere using any device. | ['Tilak Bhattacharya', 'Tilak Bhattacharya'] | [] | ['mobile', 'pega', 'robotics'] | 64 |
9,937 | https://devpost.com/software/personalized-chatbot | Built With
pega | Personalized chatbot | Personalized chatbot | ['Nazrana Perween'] | [] | ['pega'] | 65 |
9,937 | https://devpost.com/software/notag | Application Launch UI
AlertSMS
Welcome Interface
ProximityTrackingInterface
ProximityTrackingAlertCOVIDInterface
Access to Content
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the **ReadMe
* document in GitHub for accessing all contents.*
Inspiration
Life has changed for the entire mankind ever since the outbreak of the COVID 19 pandemic. Everyone is facing unprecedented disruption in life due to pandemic. While individuals are not able to carry out daily activities, businesses are not able to function as usual due to safety concerns. Healthcare system and Government agencies are overwhelmed and working tirelessly to prevent next outage.
The new mantra of life is to maintain social distancing to remain out of the reach of this pandemic which is easier said than done.
*
#NoTAG is *
built upon**** concept of TAG game with objective is to remain untouched as much as possible*
*. In this case simple Mobile app alerts an individual of presence of any infected person in proximity and guides to take precaution to remain **UNTAGGED
. It not only helps individual to break chain but also
gamify the whole concept which can be used in incentivize use of the app to make it successful.
The following sections give a detailed insight to the application.
What it does
Objective for every individual is to remain alert to avoid or prevent from getting infected. #NoTAG does same .
Once switched on , it continuously monitors presence of infected person in proximity zone selected by user. If a infected person comes in proximity it immediately alert user to take necessary precaution
. It is makes social distancing easier and fun.
How we built it
We build the solution using Pega provided Environment for Hackathon. The navigation feature of the browser is used to capture the current location coordinates and these coordinates are sent to the server through a custom built API. The server records the current coordinates and also the historical coordinates. The current coordinates in the table are used to calculate the proximity of the one person to another person. The SMS alert in done through integration to twillio.
Challenges we ran into
Team Coordination: This solution is a real time solution and
dependent on geography. Coordinating the work and testing the
solution by having people in different geography was a challenge.
Twillio Integration: Twillio is a free SMS sending service. Team
faced challenges to get the API and make it work
Pega Mobile Viewer: The Team was not able to view this application in
mobile viewer but the Team launched this application in web browser
and made it work
Making Video for demo in real time, showing whole concept of ppl moving and getting alerts.
Accomplishments that we're proud of
Key to success of this application is getting GPS coordinates and using those to calculate distance on a mobile application in Pega Viewer. This project has very short deadline, but the Team could deliver a complete working solution in a short time having the potential to be extended and enriched with many other features.
What we learned
We learn to work as a team even we were in different locations. Technically how to use GPS coordinates and build mobile ready application.
What's next for #NoTag
We understand that success of these tool depends on usage by mass and using data insights to take proactive actions.
This app can be seamlessly integrated with business and Health system COVID tracker which can be further used to automate contact tracing using insight generated from app data. It can further be augmented into gamification tool which can be used to provide incentive and promote usage. It can be easily extended to
Assess symptoms with integrated questionnaire.
Track historical data points like location , time spent to predict probability of exposure and feed into an Automated contact tracing to prevent outage.
Track nearby areas or localities with high density of infected cases and alert users upfront.
Implement organization's (closed ecosystem) mandatory Health Check Tool thereby keeping the Management aware of the employee health status and taking proactive preventive action like initiating WFH workflow for suspected employees automatically.
Gamification tool to promote it usage by business's like rewarding and providing offers individuals with less contacts.
Built With
api
css
java
javascript
pega
Try it out
github.com
bhqxqkhq.pegace.net | #NoTag | “#NoTAG” is social distancing gamification mobile app with real time assistant to alert person(s) in case of any breach in distancing norms ensuring safety from infection. | ['Manikandan Ganapathy', 'Abhishek Saurabh', 'Indrajit Chakravorty', 'Nandagopal Iyyamperumal', 'Abhay M'] | [] | ['api', 'css', 'java', 'javascript', 'pega'] | 66 |
9,937 | https://devpost.com/software/unicomm | This is the Landing Page of the Application. Also shows "My Worklist"
This is where users need to create a "new" communication case
This is where the users will need to provide outbound communication details
This is where user will need to upload documents for printing, sequence them and upload for preview generation
This is where the user views the preview of the generated PDF and confirms for printing
This is the confirmation page, when the document has been sent for printing and confirmation has been received
Access to Content:
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the _
ReadMe
* document in GitHub for accessing all contents.*
Inspiration:
Like most of the enterprises, COVID-19 has had unprecedented impact on the business operations of large and SMB business alike, across the world. Cognizant has partnered with many of its clients to rise up and respond to the emergency, ensuring client’s business continuity by engaging its workforce execute their functions without disruption.
With almost whole of its workforce are forced to work from home, one key impacted area of large organizations is the ability to send out ad-hoc communication to their customers and partners, which are typically handled by their local offices and local dispatch functions. Cognizant has helped develop a Pega based
Universal Ad-Hoc Communication Management Tool
, facilitating WFH wherein the users are able to send in their communication requests and upload the necessary files to be finally serviced by a shared outbound printing function, while being at home.
The problem area is an universally applicable problem area where employees of large enterprises across the world are working from home and such a global solution that can integrate with output communication functions, can potentially support all such enterprises send out ad-hoc and regular mail communications
What it does:
UniComm, the Pega enabled the Universal Ad-hoc Communication Management Solution enables ad-hoc printing of documents.
This application allows users to create a case & provide necessary communication details, upload multiple word and pdf files, merge them and create one single PDF for final print; they can review the PDF and send the file for printing. This application can integreate with central outbound printing function of organizations through an API. It displays success / failure messages to users. Not only that it also supports multiple validations at various stages like case creation, file generation, printing, to ensure that the communications are properly sent out. There are some reporting features, as well.
How we built it:
This application is built using Pega platform 8.2.2
.
We have leveraged OOTB case management and UI components
Challenges we ran into:
Pega 7.4 onward word to pdf conversion activex libraries has been removed. This is required to support docx format to covert in pdf.
org.apache.poi.xwpf has been considered which has limitation to convert checkox, text box content. Also supporting library has been overridden with OOTB library which has created product issue in export to excel. This were rolled back and leveraged latest OOTB libraries.
iText library has been leveraged to consolidate pdf and add even blank pages to separate out print documents.
Accomplishments that we're proud of:
The MVP version of the tool with all the important scenario was prepared in just three days
. The app has been built with an user friendly UI and easy navigation, considering no training should be needed to use this App. Also, we have developed this app to be a generic app, applicable across industries and geographical borders. Thanks to Pega's rapid development platform, and out of box features that allowed us to deliver the solution with minimal customization.
What we learned:
“Small feature” can have cross industry usability. While technical implementation, the group may think that this is simple and may not have a business value. However, in a practical business scenario, while the business was working from home, this was found to be most effective, time saving and handy application for outgoing mail communications.
While working on fulfilling requirements, we learnt Pega limitations on docx to pdf conversion. We were able to connect with end user needs, actual work and pain of not being able to have simple functionality at covid19 WFH.
What's next for UniComm?
The solution can be extended at multi-channel as if anyone can share email with attachment to Pega’s emailbox and Pega listener feature can read, convert, send to print and acknowledgement PDF to sender.
Also this feature can embedded to Pega’s framework or product capability to enable all platform customer. As stated it’s small but has good business value.
Built With:
Pega
Built With
pega
Try it out
dev-pega-hc.eastus.cloudapp.azure.com
github.com | UniComm | Ensuring business continuity by enabling geographically distributed workforce to send in ad-hoc outbound communication requests while working remote | ['Prodyot Biswas', 'I Hari', 'Sarika Fernandes', 'Shanth Rebello', 'Bhushan Patil'] | [] | ['pega'] | 67 |
9,937 | https://devpost.com/software/e-comply | e-Comply Progress Dashboard
Customer Self Endorsement Email
Customer Self-help Endorsement Form
Customer eSigned Form
Access to Content
For accessing the demo URL or Vimeo Link for this submission, credentials are required. The credentials are hosted in the above mentioned GitHub repository and invitation has been sent to
[email protected]
to access it. Please refer to the **ReadMe
* document in GitHub for accessing all contents*
Inspiration
Owing to the
COVID-19 pandemic
, the world around us has changed. And it has changed permanently. What that means for us is that every single aspect of our livelihoods have suddenly changed. Who would have thought just a few months back that simple things like filling up a form, signing it, and mailing it will be considered
“high risk”
activities, which people will be scared to do! However, today's Insurance companies often have to
comply with regulations
that would require them to
collect signatures from policy holders
on different forms and perform some endorsements to their policies. One of our Insurance customers had called us with such a need to comply with a legislation, which would require them to ask their policy holders to fill in some forms, sign them and send them back. Non-compliance to this would result the company being non-compliant and forbidden to do business in that area. This was a significant challenge, as they couldn't ask their policy holders to sign and mail forms to them due to the Shelter-In-Place restrictions.
What it does
This
Pega Marketing powered solution
uses a multi-channel approach to solve this problem. At the very beginning, a
campaign
is defined which is targeted to a given
customer segment,
matching the criteria of customers impacted by the legislation. The segmentation criteria can be configured at any time in the downstream processing to better tune the process. This first campaign sends out
emails to identified customers
explaining the process and providing them a link to themselves fill up the endorsement forms and electronically sign the documents, which get automatically attached and stored under that customer's profile.
For customers who won't open these emails, after some days, a second follow-up campaign is triggered, which sends
text messages to these customers
, asking for the same thing. This is the second leg of the solution.
Finally, if after a certain period of time, there is no response from the customer, then for each of the customers a
outbound phone call interaction
is triggered and CSRs reach out to these customers via call and gets them to complete the formalities.
How we built it
We built this solution using Pega Marketing platform, in which, campaigns can be defined at run time, targeting a given segment of customers, and generate offers for the identified customers through a communication channel. For our case, the first campaign was called
RegulatoryCampaign
, which ran on a strategy containing the demographics of the campaign. This campaign was also targeted to a segment called
RegulatoryAudience
, which defined the impacted customers. This campaign was then left to run for every weekday for the next one month.
As a follow-up, an
SMS campaign
was created, which would run on the criteria of customers who, after 7 days, did not
click
the link in the email sent earlier to them. For these customers, the
SMS campaign
would then send text messages to these customers guiding them with the process
The phone channel was not built as part of this solution, but for the customers who didn't respond to either emails or texts, a case was created in the back office application to tackle these cases.
Challenges we ran into
From a technology perspective, we found it challenging to launch a Pega Mashup URL from a Pega Marketing Treatment email, as the current format does not allow the URL to be dynamically populated.
We also had to create a Twilio integration with Pega to send the SMS offers, as we didn't have AWS licenses for sending SMS the OOTB way.
Also, due to the COVID-19 pandemic, the team that worked on this were all working from their homes, which presented a unique challenge of collaborating over the internet, which has its challenges, and it was difficult to create the team synergy that is so easily created during in-place hackathons. We felt, sometimes the team taking a break
together
also helps people to de-stress and be more productive.
Accomplishments that we're proud of
We are proud to present an omni-channel solution addressing any regulatory compliance requirements, which can be simply plugged and played at any real life scenario. This application was built end-to-end in 5 days, and we did this finding time from our day jobs (which typically takes the entire day).
Also, half of our team was in the UK and the other half in the US, time management was also a major challenge that we overcame and never let it dampen our rigor and commitment to see this to completion.
What we learned
As a team, we learned a lot about the Pega Marketing platform, which can really provide powerful insights to the whole process. For instance, we figured out that the click rates and success rates, which are OOTB KPIs of the Pega Marketing product, can be used as an overall success indicator of the compliance project. This can be a game-changer for companies implementing regulatory projects. The Marketing manager dashboard reports would give a clear understanding of how well the customers are becoming compliant, without a single line of code written to report this information.
Also, we learnt that the native Docusign connector in PEGA can be used readily to connect with any e-Signature workflow. We defined a trial connection to Docusign to test out solution. We also leveraged the OOTB signature capture feature of PEGA for cases where the implementing company does not have Docusign license, so that this solution does not have a dependency on Docusign.
What's next for e-Comply?
Creating Outbound phone call interactions for the non-compliant customers
Implementing Federated Case Management to tie back manual reconciliation cases with the campaign triggered items, to provide even better and transparent reporting.
Built With
Pega Platform (v8.4)
Pega Marketing (v8.4)
Docusign (optional),
Twilio (optional),
CSS,
Javascript.
Built With
css
docusign
javascript
pega
twilio
Try it out
cts-pega-hackathon.eastus.cloudapp.azure.com
github.com | e-Comply | A Pega Marketing driven regulatory compliance enabler, which sets up an omni-channel touchless endorsement process for Insurance policy holders. It also provides real-time progress reporting. | ['Arijit Banerjee'] | [] | ['css', 'docusign', 'javascript', 'pega', 'twilio'] | 68 |
9,937 | https://devpost.com/software/my-covidential-diary | Case life cycle
First submission page
Example of the multiple choice questions
Submission for multiple choice questions
End stage
Personalised email sent
Personalised diary entry received by user via their email
My Inspiration
Hello, my name is Jessica Levett.
I have created an application called My Covidential Diary using the PEGA Platform V 8.4.
It's inspired by a woman I have studied and read about for much of my life,
Anne Frank
.
She lived through one of the worlds most traumatic experiences and still wrote and documented her diary.
I wanted to make writing a diary as simple as clicking a button.
So that anyone can document their current experiences.
All entry's are sent personalised to your email and are customised by your answers.
I hope people can find comfort in creating their diary just as others have done before :)
I have entered my application into this
Amazing Hackathon
, in the hope that I can help spread awareness of positive change and using the resources around me avaliable to do so. And to show what girls can do 💪
I wish everyone in the world the best and have a great day!
What it does
It generates a personalised diary entry based on your multiple choice answers to help document your day.
It includes questions inspired by Anne Frank's diary and the types of things she wrote about.
I have also used questions given to me from a few years ago from my councillor which helped me come to terms with how I was feeling at the time.
The language is also not too complicated and provides straight forward answers for those with additional needs.
My younger brother who has severe learning disabilities has trialled the application and submitted his diary entry.
I really tried to make my application suitable and helpful to as many people as possible because writing is an amazing vice for those going through tough times.
How I built it
I built it using PEGA 8.4 in the App and Dev studio.
Challenges I ran into
I wanted to create this application as best as possible in the time frame to ensure functionality.
I'm all about perseverance, pushing through obstacles and finding solutions.
So I'm really happy that I was able to achieve my submitted product.
Accomplishments that I'm proud of
I am proud that it works and that it has already helped some people who have tested it out.
For example I have a teenage sister and offered her to test my app after a stressful day of online exams.
She told me how relieved she felt opening up to herself with the questions and now she has something to show herself in the future about how she has dealt with the current situation.
That really made my day because that was the goal for this application.
What I learned
That I can help people by using my skills with the PEGA system.
What's next for My Covidential Diary
I'm sure once people have grasped the concept they will want to try it, so to make it deployable would be a dream come true. The goal is to help people using PEGA resources and I really do feel that my application does that.
Built With
pega | My Covidential Diary | Document your Covidential Diary with just the click of a button. | ['Jessica Levett'] | [] | ['pega'] | 69 |
9,937 | https://devpost.com/software/localy-real-jobs-connected | Anonymous Guest-User Landing Page
Anonymous Guest-Job Search by Map
Registered User- Job Analytics
Registered User- Local Worker Search
Twilio API Integration
Registered User- Direct private message
Registered User- Private Messaging with Pulse Notification
Registered User- Built In Space feature
Anonymous Guest-Job Search by keyword
Anonymous Guest-Local Hires Search
Anonymous Guest-Sign Up to Localy
Registered User Posting Job
Registered User- Case Context Private Messaging using Pulse Notification
Registered User- Hiring a Worker
Registered User- Job Tagging
Inspiration
Due to the COVID-19 outbreak, local workers have lost their jobs. Even after reopening, due to social distancing, it will make it difficult for them to search for jobs. People have demands for various domestic services, local works. Small/Local businesses also need manpower (local workers) as well as local orders (for domestic or local services) to get back into the trade.
Facebook marketplace, craigslist
provides some advert-posting, but it lacks end to end tracking of works done. It does not help much in feedback tracking, payment, and building job history.
So we need a platform which can connect these people.
What it does
Hire people locally and get your work done.
Localy creates a bridge between people/local businesses and the manual laborers/workers for getting any form of local works done. It can be services, quick jobs, or permanent jobs as well.
It is an aggregator that connects these people. A worker can get hired by a person or local business who wants some work or services to be done. Alternatively, a local shop owner can also pick such customer requests from Localy and serve the customer to get paid.
Localy promotes the local economy.
Provides job posting related to domestic services (Landscaping, Home Delivery, Baby Sitting, Plumbing etc). Converts your local need into a quick job contract.
Job history build-up for all local works/quick jobs done.
End-to-End job tracking, which is missing in other Job advertisement sites.
Job analytics based on area, type, etc.
How we built it
We conceptualized our thoughts and then verified from the other job portals to assess the gap. It was an important assessment to identify the effectiveness of our tool.
We prepared a prototyping requirement to define the scope of work. Created a design approach and shortlisted the features for inclusion. Used Pega 8.3 version.
Created
anonymous guest user
experience and dynamic operator creation through the signup process.
Case life cycles were created through Case designer for Registration and Job posting.
Integrated
USPS API
for address validation and correction, and then integrated
MapQuest API
for long-lat determination (since the job can be posted in reference to any location). Integrated maps across the user views.
Integrated
Twilio API
for SMS-based OTP authentication.
Brought social flavors to process flow through tags, built-in public spaces, follow, and pulse private messaging. The idea was to enforce communication between parties without exposing contact details.
Gradually built reporting analytics. Job analytics was a very important feature because it will help users to identify locally popular forms of jobs available. And it can encourage them to re-skill or try various sets of jobs.
UI Elevation was done after end-to-end unit testing. To make it intuitive tooltips,
guided tours
were developed. It would allow the user to self-learn the use.
Challenges we ran into
There were
4 challenges
.
Challenge 1
- To verify a valid phone number belonging to the same user who is registering. For Phone number verification, Twilio-API was integrated and used for sending OTP via SMS. Invoking the right request structure from Pega was a difficult job.
Challenge 2
- Testing Twilio integration was difficult since we used a trial account. For the trial account, SMS can be sent only to numbers that were added to the Twilio-Verified list prior to testing. To mitigate it, we used a flag based approach to turn on/off the OTP feature, by bringing two different flavors of the application. In a real business scenario, it can be easily overcome through a paid business account.
Challenge 3
- The jobs’ location and the device from which the jobs are posted may not be the same. We had to correct user given addresses through USPS validation, and then convert them into Longitude/Latitude through MapQuest API. It allowed us to help a worker find nearby jobs.
Challenge 4
- Giving our entire interface a simplistic view that can be understood by a Local worker with limited or no knowledge. Adding the features which are not available in other job.ad-sites.
Accomplishments that we're proud of
We were able to learn and leverage the power of
Pega social gadgets (Tag, Follow, Pulse, Spaces)
into our application user experience. Additionally, we created an
Anonymous user experience
that can allow a guest user to explore across the website and gather interest for sign up. We created a simplistic 4 step sign up process which creates an ID for instant access.
Twilio API
integration helped us adding the OTP feature into the application.
What we learned
Technology or digital transformation can overcome the situations created by any pandemic or economic crisis. Simple tools or applications have solid potential to convert crisis into opportunity by connecting people. Alongside this, we learned how various microservices that are readily available in the market, can be orchestrated under a single Pega application to build an intuitive business process.
What's next for Localy - Real Jobs. Connected.
Localy has been built as a Prototype application with end-to-end coverage of the primary business scenario mentioned. But we have plans to make it market-ready with some more features in our mind-
Presently Localy is a Web application. It needs to be ported as a
mobile application
, as a must. Most of the workers are on the field, and hence creating it as an app will enhance its market-appeal.
Automated User profile verification
through Image scanning of driving license and profile inside Pega. Presently it’s a manual verification by the HR Team. Integration with
Identity Check API
.
Payment
gateway integration.
Language support and Localization
is a key feature we want to implement to enhance its appeal for workers from any native language.
Use Localy data to create
microservices
and support other online businesses and analytical services.
Additional security for anonymous log-in through masked-url.
Once implemented, we have a plan for bringing this application into the market.
Built With
google
iconfinder
mapquest
pega
twilio
usps-web-tools-api
Try it out
github.com | Localy - Real Jobs. Connected. | Transforming people's needs into the local marketplace. | ['Ghanshyam Kumar', 'Jayanta Dutta'] | [] | ['google', 'iconfinder', 'mapquest', 'pega', 'twilio', 'usps-web-tools-api'] | 70 |
9,937 | https://devpost.com/software/international-mediassist | Landing Page - Member Portal
Emergency Request Submission - Member Portal
CSR Emergency Request Review
CSR Provider Search
Provider Review Screen
Member Feedback Screen
Access to Content
_For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the
_ReadMe
* document in GitHub for accessing all contents.*
Inspiration:
With business travel more common, it’s important for Companies to ensuring their members safety while travelling. We have seen that most of the members have experienced some sort of safety- related incident while travelling. These incidents span from health and safety issues to natural disasters and Pandemics.
It’s important for business travelers to know what resources are available should they encounter a difficult situation.
Technology and new innovations have made safety and security much easier to access for travelers. With this new application we are empowering our members to seek help or indicate they are "OK" during emergency situations.
With current Travel restrictions in place across the world because of Covid -19. we wanted to build an application that can allow travelers to request for help , while they are struck in their destination away from home.
What it does
International MediAssist
powered by Pega empowers business travelers to seek necessary medical help during emergencies, leveraging digital channels.
With member location shared with the request, it helps supporting organizations cut their response time by more than 80%, thereby providing help at fraction of existing time and Cost.
How we built it
This application is built using Pega platform 8.2.2
.
Challenges we ran into
While designing this application, one major challenge was to integrate with various hospitals and provider networks. As we had ensure the safety of the Member information we need to have a secure connection with their network for transmission of the Data.
Another challenge was to integrate with sites to identify any travel notifications issued, and show that to the member.
Accomplishments that we're proud of
The basic version of the tool with the end-to-end scenario was built in four days using out of Box features with minimal customizations
. Secondly we are able to provide mobile notifications to the member based on their travel destination indicating any health notifications issued by CDC or other Similar Organizations.
What we learned
Business travelers need to be aware of what resources are available at their disposal especially while travelling. They need to have a way to request for help , so that timely medical assistance can be provided to the member.
What's next for International MediAssist?
Our application can be easily
integrated with multiple hospital networks and Provider networks .We are also planning to provide the ability to search for Provider based on their specializations or languages they speak .
Built With
Pega
Built With
pega
Try it out
cts-pega-hackathon.eastus.cloudapp.azure.com
github.com | International MediAssist | Our application equips business travelers to seek necessary help during emergencies, leveraging digital channels; while supporting organizations cut their response time by more than 80%. | ['BALASUBRAMANIAM RAMASAMY', 'Vinay Ega', 'Vishwabhilash Anantapally', 'Bhushan Patil'] | [] | ['pega'] | 71 |
9,937 | https://devpost.com/software/ifindhospital | Application Landing Page - Admin Portal
Hospital Resource Detailed View
User Portal View
User portal to capture Hospital resources
Access to Content
_For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the
_ReadMe
* document in GitHub for accessing all contents.*
Inspiration:
Covid19 exposed that lack of a centralized hospital facility tracker that shows the real-time availability of beds, ICUs or ventilators across major cities in US. With Authorities not having sufficient information on the Availability of resources across hospitals, coordinators were really struggling to route patients from one hospital to another and we saw a long wait times .
It was really important for the coordinators and health officials to have the updated information at their disposal, as any delay in providing care was costing precious lives. There was a need for a Centralized monitoring system, which can provide insight on important hospital resources to optimally manage facility demand-supply continuum. So the thought of building something that can help officials look at live inventory across hospitals inspired us to build this application.
What it does
IHospital
powered by Pega can help save lives by providing both patients and healthcare admins real-time insight into facilities availability; thereby guiding users reach out to the right facility at right time ; and optimally manage facility demand-supply continuum.
This application allows users to see a detailed view of
Primary Facilities
,
Beds (ICU and Non ICU Beds)
, and
Ventilators
along with Hospital Location.
This information can really be critical in deciding, to which hospital a patient can be routed to in times of emergencies.
How we built it
This application is built using Pega platform 8.2.2
.
Challenges we ran into
While building this application one important consideration that we had in our mind was to keep the
UI design as simple
for this application to be used by health officials without much training. Secondly we were not sure on how the data is stored across hospitals, in order to integrate our application with different hospitals. We also had challenges in implementing an RPA solution to scrape data from Hospital networks because of the data security requirements around handling sensitive information.
Accomplishments that we're proud of
The basic version of the tool with the end-to-end scenario was built in four days
. Thanks to Pega's rapid development platform, and out of box features which allowed us to speed up coding with minimal customization.
What we learned
Managing any emergencies/ Pandemic is a challenge without a centralized monitoring system. Health officials really need to be aware of facilities available at their disposal, to manage the supply and demand and reduce the average waiting time at hospitals for care.
What's next for IHospital?
Our application can be
easily integrated
with multiple hospital networks over as secured API connections to ensure data privacy. Similarly an RPA solution can also be implemented in order to fetch the updated facilities information from all participating hospitals. We are alos planning to provide a customized view for Providers and Hospitals to look for facilities across a given geographic location, for them to manage their resources more efficiently.
The plan is to make this tool available for Healthcare Clients, Government Authorities to help manage resources in these critical situations.
Built With
Pega
Built With
pega
Try it out
dev-pega-hc.eastus.cloudapp.azure.com
github.com | iFindHospital | A Pega powered app that can help save lives by providing both patients and healthcare admins real-time insight into available facilities allowing users reach out to the right facility at right time. | ['Vishwabhilash Anantapally', 'Padma Bharati Naga Sowmya Gadey', 'ANOOP SADASIVAN', 'Bhushan Patil'] | [] | ['pega'] | 72 |
9,937 | https://devpost.com/software/epidemia-fgympc | Landing Page Screen
New Infection Simulation
New Hospital Admission Forecast
Cumulative Hospital Admission Forecast with Recommendation
Forecast Modeling- Country Specific Prediction
Access to Content
For accessing the demo URL or Vimeo Link, you would need credentials. The credentials are hosted in the given Github repository and invitation has been sent to
[email protected]
to access it. Please refer to the **ReadMe
* document in GitHub for accessing all contents.*
Inspiration
COVID-19 outbreak
has clearly shown how a pandemic can paralyze our modern healthcare system. As the number of infections sky-rocketed, it became a tough job to properly distribute healthcare resources & equipment across geographic areas and hospitals. Authorities didn't have forecast information about upcoming infections and the number of equipment or arrangements needed in a certain city, area, town to tackle that. Specifically, hospitals were struggling to identify the time when they won't be able to serve any new patient, instead re-route the patient to a different hospital.
It was necessary to determine the
pattern of infection
, and get a forecast of upcoming infection ranges so that healthcare professionals can prepare them with arrangements. Not only COVID-19, but it can happen during any other infectious disease outbreak. Can we develop something which will derive such a pattern and give a forecast? And this question inspired us to leverage Pega for developing this solution.
What it does
Any infectious disease follows a mathematical model called
S-I-R
. This is a model of
Susceptibles, Infected, and Recovered
out of a certain population. Epidemia is a simulation tool that can take certain information like total population, statistics about currently infected and hospitalized patients, social distancing effectivity, acceleration of the infection-spread (doubling time), the current capacity of the hospital in terms of beds and equipment, etc. Based on the given inputs it evaluates those parameters through the SIR model and creates forecast information about the disease spread in that geographical location. It can provide an estimate of the number of new infections and patient influx to the hospital. It can also provide suggestions about the time when a certain hospital would run out of its resources. It can also provide a forecast about total infection today, based on the trend of the last week.
This helps the hospital management to do proper capacity planning beforehand.
How we built it
The proof of concept was done by Penn State Data Scientists through Python programming
. We had to spend significant time decoding the logic built through various functions and methods spread across a large number of files. The idea was to derive the modified version of the
SIR Modeling
technique and cross-validate the result. Formulas were prepared in excel and validation was done for accuracy. Then the similar functions and libraries were built inside Pega PRPC 8.4, to leverage this model. Additional data tables were built for generating simulation reports. Finally, ample time was spent on doing UI elevation. The target was to make the UI self-explanatory for any user, without prior knowledge.
Challenges we ran into
It was a complex task to
convert complex python functions into Pega-specific functions and utilities
. Specifically, it was a bit challenging to build a series of large data analogous to 2 or 3-dimensional statistical data analysis in Python. Also, the precision of data had to be managed to maintain the accuracy of the forecast. For a large data set this precision can make a stark difference in values.
Accomplishments that we're proud of
The basic version of the tool with the end-to-end scenario was prepared in just 2 days
. Thanks to Pega's rapid development platform, which allowed us to speed up coding, and integrate java libraries for complex processing.
What we learned
The development of this tool helped us learning the
mathematical model and statistics about any epidemic in the world
. Any form of infectious disease can be plotted into a mathematical model and can be assessed for its impact on the population. While developing this tool, we were able to establish that in Pega through java functions and activities complex mathematical models can be built for custom requirements.
What's next for Epidemia
This tool is a plug-and-play capability
that can be integrated with any healthcare application, which requires similar forecasts for any epidemic/infectious disease. Such a forecast would help in determining upcoming healthcare coverage costs, equipment orders, hospital capacity planning, etc. This tool can be extended as well for any other infectious disease by adding new templates.
The plan is to make this tool available for Healthcare Clients, Government Authorities to help and defeat such pandemics in the future.
Built With
css
java
pega
Try it out
dev-pega-hc.eastus.cloudapp.azure.com
github.com | Epidemia | A Pega Powered Forecasting & Hospital Impact Modeling Solution for Epidemics. The model creates best- and worst-case scenarios to assist with hospital capacity planning – crucial for response team. | ['Jayanta Dutta'] | [] | ['css', 'java', 'pega'] | 73 |
9,937 | https://devpost.com/software/advanced-xml-mapping-framework-for-pega | XSLT-template definition custom rule.
Results of Clipboard streaming to XML with help of XSLT-template.
Results of performance comparison between classic Clipboard-to-XML streaming approach and streaming with help of XSLT-template.
Full demo video
Full demo video is accessible by the next link -
Advanced XML Streaming Framework for Pega (full demo)
. In addition to basic project introduction, it provides advanced demo scenarios for such features as parameterized and multi-page transformations, XSD-driven transformations, transient properties and pages, performance comparison test and others.
Inspiration
From my previous experience almost each company-wide Pega implementation deals with XML- or SOAP-based services integration. And each project has its own specifics: huge XML-data amount to be transferred to/from the service, frequent data model changes, complicated and time consuming data transformation to be done and so on. In some cases, classic Pega approach for Clipboard-to-XML streaming during XML-based services integration is not giving the best possible result. That is why I started thinkig about alternative solution, which can be used in such situations.
Classic Pega Clipboard-to-XML streaming approach is represented on the next picture:
It consists of the next steps:
Two types of data model are created: Business data model and Integration data model.
Clipboard page is transformed from Business data model into Integration data model with help of Data Transform rules.
Then Clipboard page is streamed from Integration data model into XML with help of XML Stream rules.
Motivation for this project was to improve this streaming process from the next prospective:
Performance:
there are two processing stages – mapping to Integration data model and steaming to XML. For big Clibpboard structures two stages are giving a performance overhead.
Is it possible to have only one processing stage?
Memory consumption:
both Business and Integration data models are kept in memory during the processing.
Is it possible to have only one data model in memory?
Maintainability:
even to add a new single property, all the layers must be modified – Data Transform rules, Integration data model and XML Stream rules.
Is it possible to have only one point of modification?
What it does
To achieve improvements mentioned above, this project applies
Extensible Stylesheet Language Transformations technology (XSLT)
:
XSLT is an XML-based language, which can transform one
XML Document Object Model (DOM)
into another one.
XSLT has enough expressiveness to perform transformation of any complexity.
From performance prospective, JDK-embedded XSLT-processors have an
XSLTC extension
, which can generate native Java-code from XSLT-template and compile it into executable Java-class "on-the-fly".
XSLT-technology fits perfectly into overall Pega concept of reusability and specialization: one XSLT-template can import all the transformation rules from another one and specialize any of them.
Finally, this approach increases maintainability: XSLT-template is doing both transformation and streaming into XML, representing this way a single point of modification in the case of transformation changes.
The solution proposed applies XSLT-technology for efficient Clipboard pages streaming into XML.
How I built it
For XSLT-templates definition storage inside Pega a special custom Pega rule
Integration-Mapping -> XSLT Template
was developed. This rule enables XSLT-template content editing, as well as its validation with help of compilation attempt:
Main XSLT-transformation functionality is implemented as a reusable Java-function, which executes JDK-embedded XSLT-processor for transformation purposes (it supports Oracle JDK, IBM JDK and Open JDK):
@ANUtilities.StreamClipboardToXML(
myStepPage,
D_XSLT[Template: "ANOrg-Components-Work.T002_Manual_Basic"].Template,
null,
null
)
In the example above this function is called to transform
myStepPage
Clipboard page with help of XSLT-template, defined by custom rule
ANOrg-Components-Work.T002_Manual_Basic
. Access to XSLT-template is implemented through
D_XSLT
node-level Data Page rule. This Data Page compiles XSLT-template "on-the-fly" and caches its instance, so it can be reused for multiple transformations later.
XSLT-transformation function implements two execution approaches:
Model-first approach:
in this case application data model and XSLT-template to stream it to XML are created manually.
XSD-first approach:
in this case XSLT-template can do automatic transformation with help of output format description by
XML Schema Definition (XSD)
.
XSD-first approach idea is originating from the next question: what if we have already an output XML description in the form of XSD-schema? Is it possible then to simplify XSLT-template development?
XSD-schema in Pega can be used to generate automatically data model and XML Stream rule. This data model then can be extended during the development with some additional properties, but an output XML format remains strictly defined by XML Stream rule. During the transformation phase this XML Stream rule can be used to automate processing:
In this scenario next logic is executed:
XSLT-transformer function is able to read XML Stream rule definition.
And then it can automatically transform a Clipboard page according to this definition, which means – according to XSD-schema.
During this XSD-driven transformation the function is doing multiple things: renaming elements, sorting them, adding required fields and so on. That is an example, how XSLT-transformation function is called in this case:
@ANUtilities.StreamClipboardToXML(
myStepPage,
D_XSLT[Template: "ANOrg-Components-Work.T006_Automatic_Basic"].Template,
D_Stream[Template: "ANOrg-Components-Work.Order.MapFrom"].Template,
"sort|skip_default|required|set_default"
)
In this scenario the function receives two additional parameters:
Reference to XML Stream rule to be used. Access to XML Stream rule is implemented through
D_Stream
node-level Data Page rule. This Data Page parses XML Stream rule definition "on-the-fly" and caches it as a
java.util.Map
class instance, so it can be reused for multiple transformations later.
Optionally, a list of additional transformation modes can be provided, which controls such aspects as elements sorting, preserving required fields, setting default values and so on.
Challenges I ran into
Unfortunately XSLT-approach has one major performance issue, which is represented on the next picture:
This problem happens because of the next reason:
JDK-embedded free XSLT-processors can only use DOM model as an input for transformation.
To convert Clipboard data model into DOM model we need at first to stream Clipboard page into Clipboard XML, then parse this XML into DOM model, and only after we can apply XSLT-transformation.
These intermediate streaming and parsing steps neglect all the performance benefit, which can be achieved from XSLT-technology usage.
To mitigate this problem, next cornerstone solution was implemented:
Its main idea is:
At first XSLT-transformer Java-function "wraps" Clipboard page with DOM interfaces. Particular Clipboard property or page is wrapped "on-the-fly" – only if (and when) it is used by the transformation.
And then this function applies compiled XSLT-template to this "wrapped” Clipboard page, as if it was an ordinary DOM structure.
This way all the intermediate steps with streaming and parsing are eliminated, keeping performance at the highest possible level.
The first big challenge during this solution implementation was to understand, how XSLT-processor uses DOM interfaces to perform a transformation (which DOM interfaces and methods are used, in which sequence). I had to do a lot of extensive debugging and logging to find out, which DOM interfaces methods are really relevant for XSLT-transformation and must be implemented.
After getting this understanding, next complicated step was to implement these relevant DOM interfaces methods on top of a Clipboard object model - so XSLT-processor can use these methods transparently without any knowledge, that in reality it works with a Clipboard object model beneath. For me this task was a "deep dive" into Clipboard object model structure.
And finally, as long as XSLT-transformation should be able to work on top of Clipboard pages with thousands of properties without lack of efficiency, it was really challenging to "fine-tune" performance. I had to optimize every code block for the best efficiency: even with a single inefficient "if" condition, when it is used in thousand evaluations for thousand Clipboard properties, performance overhead can be really big.
Accomplishments that I'm proud of
As the main project achievements I consider:
Better performance.
A decrease in streaming duration for XSLT approach in comparison with a classic one ranges from 50% for simple demo scenario and up to 90% for real productive data model and complicated transformations. And XSLT approach efficiency increases continuously with an increase of data model and transformations complexity. This way the solution proposed helps to build very scalable applications, which can better utilize computational power and decrease overall infrastructural costs.
Lower memory consumption.
As long as XSLT transformation runs on top of the Business data model only, it consumes smaller memory amount, than a classic streaming approach. This way, application, which is doing in parallel a lot of calls to XML-based services, becomes more stable – it has a smaller probability to run "out-of-memory". And of course, lower memory consumption reduces infrastructural costs – it is especially important for Cloud-based solutions, when infrastructural costs are often calculated by providers on the basis of memory consumption.
A single point of modification in the case of transformation changes.
XSLT approach helps to reduce a complexity of integration solution maintenance. With a classic approach, a task of application switching to the new version of XML-based service for a complicated integration solution is usually assigned to senior developers, who are doing changes in all the integration layers. XSLT approach makes integration maintenance task available not only for senior developers, but for junior developers as well, reducing this way overall project costs.
Both model-first and XSD-first approaches are supported.
XSD-driven transformation approach makes maintenance of the integration solution even easier. Switching to the new version of XML-based service now is just generation of an updated data model and XML Stream rules from the new version of XSD-schema. And all the transformation rules, previously defined by XSLT-template, in the most cases will stay the same.
Fits perfectly into overall Pega concept of reusability and specialization.
When a company has a wide network of region-based or country-based divisions, it is highly important to have a central reusable application framework, and to be able to specialize it, if needed. And from integration layer prospective, XSLT approach gives a full flexibility in this area: it is possible to define generic transformation rules for company-wide data model in framework layer and specialize them for each division with a high level of granularity – up to a single property mapping rule.
What I learned
For me it was the first experience of the latest Pega 8.4 version usage, and I got very positive impression about new features of the Development Studio. Especially I would like to mention Unit Testing - now it is really easy to create comprehensive Unit Test scenarios and use them to control application quality!
During this project I got a deep knowledge about internal structure of Pega Clipboard: how to use Pega Engine API for Clipboard navigation, how to work with different types of properties, how to open Pega rules definitions and place them to Clpboard programmatically.
Another great opportunity for me was to learn how XSLT-processor works with DOM interfaces to perform transformation: which methods of which interfaces are called, in which sequence, how often. From this prospective it was a pleasant surprise for me how similar Pega Clipboard object model and XML DOM model are - so it was possible to "wrap" Clipboard page with DOM interfaces.
And finally, it was the first great experience for me with demo-movies making :-) So I know now which tools to use to record them, convert to desired format, combine from several parts and, finally, publish on the Internet - I am thankful to Pega Hackathon for this knowledge as well! I am sure, that any new experience is very valuable and can be applied in the future!
What's next for Advanced XML Streaming Framework for Pega
As next plans I would like to mention:
Implement a direct parameterization of XSLT-transformer function by XSD-schema as an alternative to parameterization by XML Stream rule.
XSLT is an open standard, so there are a lot of visual tools available for XSLT-templates editing – both free and commercial. So one of the next tasks can be to integrate some free tool for XSLT-templates visual editing into Pega.
As the most important extension, I plan to implement a similar solution for an input XML parsing into Clipboard Business data model, improving this way an existing approach from performance, memory consumption and maintainability prospective as well.
XML parsing extension will finalize implementation of the full "end-to-end" solution for Pega, which allows efficient integration with XML-based services.
Finally, XSLT-framework can be extended to work with JSON as an input or output format for transformation too as long as XSLT 3.0 has a support for XML-to-JSON and JSON-to-XML conversion (
https://www.w3.org/TR/xslt-30/#json
).
This way the solution proposed can bring additional efficiency for integration with REST/JSON services as well.
And the last one, and from my prospective a very promising new idea:
wrapping of Pega Clipboard page with DOM interfaces "opens a door" for application of other XML-based technologies, like XPath or XQuery.
For example, next possible usage can be implementation of reusable Java-function for fast access to specific property value inside a complicated Clipboard page with help of just a single XPath expression:
.ClientAddress = @xpath(
"Order/Client[FirstName = 'John']/Addresses/rowdata[City = 'Munich']/LineAddress"
)
Built With
dom
java
pega
xalan
xpath
xslt | Advanced XML Streaming Framework for Pega | Project goal is to improve a classic Pega Clipboard-to-XML streaming approach from the performance, memory consumption and maintainability prospective with help of XSLT-technology. | ['Alexey Nesterenko'] | [] | ['dom', 'java', 'pega', 'xalan', 'xpath', 'xslt'] | 74 |
9,937 | https://devpost.com/software/mysafety | Inspiration
COVID Threat
What it does
Helps anyone to do a self assessment on covid infection. Depending on the outcome ,medical assistance can be arranged. Also this data is captured against the geo location of the person. It helps in marking high risk areas around 10 kms based on the geo location
How I built it
Pega 8,geolocation, haversine,chatbot
Challenges I ran into
calculating distance around geo location (OOTB implementation of haversine made it very simple)
Accomplishments that I'm proud of
Contribute something to a social cause
What I learned
Amazing features of PEGA which really cuts down development time (truly a low code platform)
What's next for MySafety
Built With
chatbot
gps
haversine
pega
Try it out
drive.google.com | MySafety | MySafety is a chatbot supported app to do self assessment on virus infection. | ['George Jacob'] | [] | ['chatbot', 'gps', 'haversine', 'pega'] | 75 |
9,938 | https://devpost.com/software/dejana | Example of a conversation with chatbot Dejana 3
Example of a conversation with chatbot Dejana 1
Example of a conversation with chatbot Dejana 2
Inspiration
Parents of 20 000 children with disabilties in Croatia don’t have skills to take over the role of the teachers during distance schooling. At the same time, every 3rd teacher in Croatia reported on needing additional support for working with children with disabilities during distance schooling. To make sure children with disabilities are learning during the pandemic, we have decided to support parents and teachers by development of a training on learning with children with disabilities via a chatbot called Dejana.
What it does
Dejana gives parents and teachers expert advice on learning by a disability. It covers all disability categories listed in the national Guidelines on Primary and Secondary Education of Students with Disabilities. Dejana is at parents' and teachers' service any time of the day.
How I built it
We have built the MVP through a chatbot business platform Chatbot.com.
Challenges I ran into
The most challenging parts were:
creating a conversation scenario, due to peculiarities of every disability
creating a business model
creating a video
What I learned
about chatbots
about business model development
about inclusive education
about concept development
about hackathons | Chatbot Dejana | Training on learning with children with disabilities developed by inclusive education experts to support parents and teachers during distance learning. | ['Ivan Krešić', 'Mirela Džafić'] | ['Top 5'] | [] | 0 |
9,938 | https://devpost.com/software/green-community-rooftops-for-a-better-life | Inspired by the current presence of the virus, isolation and uncertainty, but also by the lingering environmental and social challenges that cities face, the rooftop and balcony gardening project can offer many benefits to the individual, community, city, and beyond. A city-led project would improve the air-quality, improve biodiversity, retain rainwater, reduce energy consumption in buildings and total GHG emissions. By devising a model of implementation and sharing the necessary materials such as wood, gravel, seeds or gardening equipment, the city would encourage citizens to cooperate and arrange when arranging their gardens on their roofs, terraces, balconies, windows and loggias. At the same time, by building their own gardens and enjoying its cultivation, newly created gardeners would feel more fulfilled and certainly eat healthier.
Built With
oxford-english-dictionary
Try it out
docs.google.com | GREEN COMMUNITY ROOFTOPS FOR A BETTER LIFE | Inspired by the current presence of the virus, isolation and uncertainty, the rooftop can offer many benefits to the individual and community. | ['Gordana Mikulčić Krnjaja'] | ['Top 5'] | ['oxford-english-dictionary'] | 1 |
9,938 | https://devpost.com/software/naucime-online | Inspiration
What it does
How I built it
Challenges I ran into
Accomplishments that I'm proud of
What I learned
What's next for naucime.online
Inspiracija za projekt je došla od zajednice ljudi koja se nakon potresa i u tijeku krize spontano počela okupljati na društvenim mrežama pružajući besplatnu pomoć oko domaćih zadaća i učenja. Za njih smo željeli napraviti alat sa svim potrebnim mogućnostima koje bi im mogle zatrebati. Napravljena je web stranica
www.naucime.online
pomoću Wordpressa sa osnovinim i nekim naprednim funkcionalnostima. Ova stranica je baza za daljnji razvoj platforme, ali i mobilne aplikacije sa sličnim mogućnostima. Iako smo se susreli sa kratkim vremenskim rokom, ponosan sam što smo uspjeli napraviti potpuno funkcionalnu stranicu koja se već sada može koristiti. Naučio sam da ne treba predavati projekt u zadnji čas jer te može tražiti različite formate u kojima nisi radio :)
Built With
wordpress
Try it out
naucime.online | naucime.online | Razvoj web platforme za online učenje | ['Matej Peranić'] | ['Top 5'] | ['wordpress'] | 2 |
9,938 | https://devpost.com/software/stay-in-sane-parenting-hub | ppt
Inspiration
Inspiraciju smo pronašle u svakodnevnom životu, suočene s pandemijom kada su preko noći prestali raditi vrtići, a poslovi su se preselili u naša 4 zida shvatile smo koliko je teško organizirati se u izvanrednim situacijama. Odlučile smo pronaći rješenje za taj problem sa svojim projektom i implementirati u njega stvari koje roditelje muče u svakodevnom životu.
Everyday life was our inspiration, faced with pandemic overnight with closed kindergardens and jobs moved to our homes, after we have started to realise it is very difficult to get organized under extraordinary circumstances. With this project we have decided to find a solution for this problem and to be out of help to any parent with everyday life struggles.
What it does
Glavne funkcionalnosti Stay (in)sane parenting hub portala:
Google kalendar koji roditeljima pomaže da si organiziraju dan tako da putem sadržaja animiraju svoju djecu dok svoje vrijeme mogu iskoristiti za druge potrebe, kao npr. odradu službenog posla ili kućanskih poslova. Klikom na dan u mjesecu roditelj dobiva pristup materijalima koji tematski odgovaraju određenom danu i dobi djeteta s popisom razrađenih aktivnosti.
Mogućnost povezivanja s Google kalendarom i dobivanja notifikacija o eventima
Kategorizirani materijali koji pomažu djetetu da razvija samostalnost, svijest o okolišu i koji podržavaju njegov psihomotorni razvoj
Stvaranje potražnje za visokokvalitetnim materijalima iz čega slijedi i produkcija takvih materijala te iz čega slijedi i povećanje ponude takvih materijala na hrvatskom jeziku
The main features of Stay (in)sane parenting hub website are:
Google calendar with aim to help parents to get to organize their day by sharing events and links to entertain their kids, leaving them time to focus on their jobs or household chores
Option to connect with Google calendar to recieve event notifications
Content categorized by intention to encourage child's independence, enviromental awareness and psychomotor learning
Demand for quality content will raise its production and its offer on croatian language
How we built it
Izgradili smo ovo uz puno rada u 48 sati i malo sna :)
Koristile smo Google alate koji su nam dostupni i s kojima znamo raditi. Naglašavamo da niti jedna od nas nema tehnički background.
We've built this with a lot of effort in 48 hours and little sleep :)
Just by using free available Google tools we managed to work with.
None of us is experienced in technical skills.
Challenges we ran into
Usuglašavanje oko ideje, rok izrade, definicija izgradnje mockup stranice.
Agreement over idea, deadline, the definition of building the website mockup.
Accomplishments that we're proud of
Mockup stranica, video i uspješna organizacija u 48h.
Website mockup, video and organisation accomplished in 48 hours.
What we learned
Naučile smo koliko lijepo može biti surađivati s potpuno nepoznatim ljudima kad imaju isti cilj.
How beautiful it is to cooperate with complete strangers to achieve a common goal.
What's next for Stay (in)sane parenting hub
Crowdfunding kampanja.
Crowdfunding campaign.
Built With
adobe-premier
google-drive
google-sites
Try it out
sites.google.com | Stay (in)sane parenting hub | Edukativne i kreativne poveznice za djecu i roditelje / Educational and creative links for children and parents | ['Marija Trcol', 'Martina Furlanis', 'diana cehaja', 'Sandra Ružić', 'Marija Renić', 'ana-fornazar'] | ['Top 5'] | ['adobe-premier', 'google-drive', 'google-sites'] | 3 |
9,938 | https://devpost.com/software/tilda | Inspiration
The inspiration for this project was the current situation we are facing, regarding the COVID-19 and the obligation of keeping the social distance. We were thinking about the ways on how we can help and how we can give our contribution to fight against the COVID-19. We wanted to include as many people as we can and also give them the possibility to help from their homes.
What it does
Tilda enables users to meet the celebrities via video chat by donating a symbolic amount of money to active charity causes. Users can also use this platform to stay in touch with their family and friends or just for making a donation without using video chat. In order for the video call to be established, it is necessary to donate a symbolic amount that goes to charity.
How I built it
Our lead developer Raul came up with this idea and we immediately started to work on it. Developers were responsible for coding, and the rest of the team was working on marketing and social media strategy as well as on the approach to celebrities.
Challenges I ran into
The biggest challenge is to obtain the state permission for running charity event due to the very complex bureaucracy.
Accomplishments that I'm proud of
We are really proud of our teamwork and how we managed to develop the platform in quite a short period of time. Dedication and hard work of all team members was really admiring and that gives a lot of encouragement and hope that this will be a successful project
What I learned
We learned that with hard work it is possible to deliver quite complex project in a short period of time.
What's next for Tilda
Next for Tilda is testing in order to be sure that everything works perfectly without bugs. Before public release, we also need to polish the whole platform and if needed make some design changes and make it intuitive for users. Our volunteers will start contacting the celebrities and media to spread the word about Tilda.
Built With
apollo
express-graphql
node.js
postgresql
react
Try it out
tilda.care
app.tilda.care
www.facebook.com
www.instagram.com | Tilda | Tilda is an online fundraising platform that allows users to meet celebrities via video call by making a donation for causes they care about. | ['Renato Poljak'] | ['Top 5'] | ['apollo', 'express-graphql', 'node.js', 'postgresql', 'react'] | 4 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.