Automation Anywhere makes it easy to remove mundane tasks from every employee’s life with Robotic Process Automation (RPA). RPA is helping businesses better serve their customers, improve operational efficiency, and empower employees to build the career of their dreams.
Be a part of the future of work. Bot Games is the RPA developer bot building contest that helps organizations go be great by building AI-powered, cloud-native, web-based intelligent automation. We invite developers from around the world to showcase bots to help employees return to a better, more creative workplace for a chance to win $5000 and other valuable prizes.
Automation 360 cloud is robust for professional programmers, yet easy enough for those new to automation. Build advanced automation using the built-in capabilities of Automation 360 along with your own custom code that you may write in Python, JavaScript, .NET, or Java. Built-in integration capabilities make it easy to leverage your own machine learning models, 3rd party AI services, or integration with REST/SOAP APIs. If you are new to RPA, cloud-based automation is designed for ease-of-use, with intuitive drag-and-drop actions and visual flow charts. Cloud RPA enables users to automate any process via a web-based interface accessed in their browser.
In addition to this hackathon, join us at our Bot Wars weekly challenges for a chance to win additional prizes, uplevel your RPA skills, and get inspired by the RPA community.
We encourage you to build and submit bots that can help employees return to a better, more creative workplace, along any of the 5 themes below. See each theme for automation use case examples. These examples are only offered for inspiration. You’re by no means restricted to these use cases.
Front Office
Front-office workers are individuals who directly generate revenue for the company. The front office is largely made up of client-facing duties, which can include those commonly found in Marketing, Sales, or Customer Service. This is a great place to use Automation Anywhere Robotic Interface, or AARI. Example use cases include:
Supply Chain
The world has a long way to go to stabilize the supply chain and get product where it needs to go. Build automation that helps suppliers and buyers exchange goods in a timely manner. Example use cases include:
Human Resources
As the world re-opens, rapid hiring and onboarding is critical to meeting a surge in demand. Build automation that helps human resources secure and retain top talent. Example use cases include:
Finance
As the economy recovers, spending is returning as well. Build automation that helps organizations manage more invoices, vendors, accounts or payments. This is a great opportunity to use AI/ML using IQ Bot. Example use cases include:
Surprise Us!
Removing repetitive, mundane tasks is critical to returning to work with a more creative, innovative career. Automation can also be used in other creative ways in other departments or lines of business, across multiple departments or even outside of the office. Show us your creative ideas on how to use intelligent automation using Automation 360, IQ Bot, Discovery Bot and/or AARI. Example use cases include:
The judging process for the software submissions of the hackathon will be in 2 phases:
Phase 1: All the submissions will be evaluated by the judges and the top 10 submissions will be shortlisted.
Phase 2: The shortlisted teams will be invited to present to a panel of judges on a Zoom video meeting.
The top 3 teams or individuals, as determined by the panel of judges, as well as the top submissions for the innovation awards will be announced on September 13, 2021.
$18,000 in prizes
First Prize
Cash prize of $5,000 USD for the winning team
Second Prize
Cash prize of $3,000 for the runners-up team
Third Prize
Cash prize of $2,000 USD for the second runners-up team
Innovation Awards (4)
To inspire the automation community, we are providing additional valuable prizes for your entries. Show us your creative use of automation to win $500 USD in cash for up to four winners.
Innovation Awards (4)
We are also providing up to four additional prizes for your innovative bots. Inspire the automation community by showing your creative use of automation to win a free one-year individual Automation Anywhere University Learning Subscription (a value of $1,500 USD)
Your submission must be in the English language and consist of:
Also, please note:
Multiple submissions: You can submit multiple projects to the hackathon, as a part of the same team or a different team. However, you are eligible to win only a single prize.
Re-submission/editing of submissions: You can re-submit or edit your submission until the submission deadline. Your latest version of a submission before the deadline will be considered for judging.
For a complete list of submission requirements, please check out the Official Rules.
Laura Della Torre
Sr. Director, Customer Lifecycle Marketing, Automation Anywhere
micah smith
Director, Developer Evangelism, Automation Anywhere
NO PURCHASE OR PAYMENT NECESSARY. A PURCHASE OR PAYMENT OF ANY KIND WILL NOT INCREASE YOUR CHANCES OF WINNING.
1. Dates and Timing
Hackathon Submission Period: July 25, 2021 (8:30pm Pacific Time) – August 31, 2021 (5:00pm Pacific Time) (the “Hackathon Submission Period”)
Judging Period: September 7, 2021 (12:15am Pacific Time) – September 16, 2021 (11:45pm Pacific Time) (the “Judging Period”)
Winners Announced: On or around September 21, 2021 (10:00am Pacific Time)
2. Sponsor & ADMINISTRATOR
Sponsor (the “Sponsor”): Automation Anywhere Inc.; 633 River Oaks Parkway, San Jose, California 95134, United States
Administration (the “Administrator”): Devpost, Inc. (“Devpost”), 226 Prospect Park West, #171, Brooklyn, NY 11215
3. ELIGIBILITY
A. The Hackathon IS open to:
● Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”)
● Teams of Eligible Individuals (“Teams”)
● Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry
(the above are collectively, “Entrants”)
An Eligible Individual may join more than one Team, or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis.
If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Site on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.
B. The Hackathon IS NOT open to:
*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year.
**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.
***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.
4. How To Enter
Entrants may enter by visiting https://botgames.devpost.com (“Hackathon Website”) and the following the steps:
Project Requirements (i) What to Create: Entrants must build and submit bots that can help organizations automate tasks and processes in the following categories below. (each a “Project”).
(ii) Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description. (iii) Platforms: A submitted Project must run on the platform for which it is intended, and which is specified in the Submission Requirements. (iv) New & Existing: Projects must be either newly created by the Entrant or, if the Project existed prior to the Hackathon Submission Period, must be able to demonstrate significant adaptations or changes made during the submission period if this is an existing idea or product after the start of the Hackathon Submission Period. (v) Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them. (vi) Testing: The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. If the Project includes software that runs on proprietary or third-party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request. For Projects running on widely available smartphones, tablets, or desktop computers, Submission Requirements. Submissions to the hackathon must meet the following requirements:
Language Requirements All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. Team Representation If a team or organization is entering the hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a team or organization you represent and warrant that you are the Representative authorized to act on behalf of your team or organization. Intellectual Property: Your Submission must: (a) be your (or your Team, or Organization’s) original work product; (b) be solely owned by you, your Team, your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. An Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Hackathon, you represent, warrant, and agree that your Submission meets these requirements. Financial or Preferential Support: A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest. |
5. Submission Modifications.
A. Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the submission materials to the hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your submission, but you may continue to update the project in your Devpost portfolio.
B. Modifications After the Submission Period. The Sponsor and Devpost may permit you to modify part of your submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified submission must remain substantively the same as the original submission with the only modification being what the Sponsor and Devpost permits.
6. Judges & Criteria.
Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the sponsor or third parties, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the sponsor.
Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the project reasonably fits the theme and reasonably applies the required tools featured in the Hackathon.
Stage Two) All submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):
Entries will be judged on the following equally weighted criteria, and according to the sole and absolute discretion of the judges:
The scores from the Judges will determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.
Tie Breaking. For each Prize listed below, if two or more submissions are tied, the tied submission with the highest score in the first applicable criterion listed above will be considered the higher scoring submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more submissions are tied on all applicable criteria, the panel of Judges will vote on the tied submissions.
7. Intellectual Property Rights.
All submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an entry, entrants agree that the sponsor will have a fully paid, non-exclusive license to use such entry for judging the entry. Entrants agree that the sponsor and Devpost shall have the right to promote the submission and use the name, likeness, voice and image of all individuals contributing to a submission, in any materials promoting or publicizing the hackathon and its results, during the Hackathon Period and for three years thereafter. Some Submission components may be displayed to the public. Other Submission materials may be viewed by the sponsor, Devpost, and judges for screening and evaluation. By submitting an entry or accepting any prize, entrants represent and warrant that (a) submitted content is not copyrighted, protected by trade secret or otherwise subject to third party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless entrant is the owner of such rights or has permission from their rightful owner to post the content; and (b) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.
