NO PURCHASE NECESSARY TO ENTER OR WIN. VOID WHERE PROHIBITED. IT IS CLARIFIED THAT BY ENTERING THIS HACKATHON YOU WILL BE BOUND BY AND COMPLY WITH THESE RULES AND THE DECISIONS OF THE POSTER, AND/OR THE JUDGES WHICH ARE BINDING AND FINAL IN ALL MATTERS RELATING TO THE HACKATHON (all terms are defined below).
1.1. The “Administrator” “Poster” - Kryon Systems Inc.,135 East 57th Street, NY, NY 10022, United States;
1.2. “Entry” - Submitting the Submission (as defined below) to the Hackathon on the Hackathon Website;
1.3. The “Hackathon” - Kryon Bot Camp 2020;
1.4. The “Hackathon Website” - kryon-botcamp.devpost.com;
1.5. The “Judges” - panel of judges selected by the Poster to evaluate;
1.6. The “Maker/s” - as defined in section 4 below;
1.7. The “Rules” - this Kryon Bot Camp rules and regulations;
1.8. “Submission” - all acts and documents constitutes the proposal for the Hackathon, as set in section 7.4 below;
1.9. “Wizard” - as defined in section 6 below.
2. THE HACKATHON PURPOSE
This Hackathon purpose is automating a complete business process using Kryon Studio that helps organizations solve today’s business challenges and/or is within specific themes of Bot Camp as described below.
3. GENERAL RULES
3.1. The entire idea need not be fully implemented however, the Submission should be functional so that it can be reviewed by the judges.
3.2. The developer/developers of the solution will have all rights and own the IP of the Wizard. However, all code needs to be in public domain (open source) so that it can be evaluated by the Judges.
4.1. In order to enter the Hackathon you must be one of the following:
4.1.1. Individuals who are at least the age of major and citizen of an Authorized State* as of the time of Entry (the “Eligible Individuals”);
4.1.2. Teams of Eligible Individuals (the “Team/s”);
4.1.3. Organizations (including corporations, not-for-profit corporations and other non-profit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated in an Authorized State at the time of Entry. (the above are collectively called “Makers”)
* Authorized State - any state except of the following: Brazil, Quebec, or any country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, Cuba, Sudan, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control);
4.2. 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 is entering the Hackathon, they must appoint and authorize one individual (the “Team Leader”) to represent, act, and enter a Submission, on their behalf. The Team Leader and each Team member who participates in the Hackathon must meet the eligibility requirements above. By performing an Entry behalf of a Team you represent and warrant that you are the Team Leader of your Team.
4.3. The Hackathon is not open to Poster’s employees, Judges, or any company or individual involved in the organization of the Hackathon, and the relatives of all of the above first class (spouses, parents, siblings, children).
4.4. Any individual or organization whose participation in the Hackathon would create, in the sole discretion of the Poster, a real or apparent conflict of interest, shall be prevented from participating the Hackathon.
5.1. Makers shall submit their Submissions in the period from July 15, 2020 (9:00am Eastern Time) to August 18, 2020 (11:45pm Eastern Time) (the “Hackathon Submission Period”)
5.2. Judges shall examine and score the Submissions in the period from August 19, 2020 (00:15am Eastern Time) to August 30, 2020 (11:45pm Eastern Time) (the “Judging Period”)
5.3. The announcement of the Hackathon winners shall be on or around September 3, 2020 (7:00am Eastern Time).
5.4. The Poster may decide at any time, for any reason and at its sole discretion, to cancel the Hackathon, to postpone the dates and timing listed above. It is recommended that Makers will check the Hackathon Website for any updates regarding to the Hackathon schedule.
6. LANGUAGE REQUIREMENTS
All materials submitted in connection with the Hackathon must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.
7. SUBMISSION REQUIRMENTS
7.1. Wizard Requirements
(i) What to Create for Submissions: Makers must develop a new solution using Kryon Studio that helps organizations solve today’s business challenges and/or is within the themes of Bot Camp:
- Banking & Finance
- Remote Work
(each a “Wizard”).
(ii) Functionality: The Wizard 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) New: Wizards must be newly created by the Maker after the start of the Hackathon Submission Period.
(iv) Testing: The Maker must make the Wizard available free of charge and without any restriction, for testing, evaluation and use by the Poster and Judges (as defined below) during the Hackathon and until the Judging Period ends. If the Wizard includes software that runs on proprietary or third party hardware/software that is not widely available to the public, the Poster reserves the right, at its sole discretion, to require the Maker to provide access upon request. For Wizards running on widely available desktop computers, Makers may make their Wizard available using one of the following methods:
(vi) Public Distribution: The Maker may make the Wizard available to the public via a website or online store, but is not required to do so.
(vii) Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Maker’s other Submissions, as determined by the Poster.
(viii) SDKs, APIs, & Data: Wizards may integrate SDKs, APIs and data, provided the Maker is authorized to use them.
(ix) Intellectual Property: Makers of Idea Submissions consent to having their ideas utilized by developers to build a technical solution. However, Wizards must: (a) be your (or your Team’s or Organization’s) original work product or (b) be solely owned by you, your Team, or 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. A Maker may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Maker’s work product and the result of the Maker’s ideas and creativity, and the Maker owns all rights to them. A Maker may use, but not claim, the IP of an open source Idea Submission. A Maker may submit a Submission that includes the use of open source software or hardware, provided the Maker 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.
(x) Financial or Preferential Support: A Wizard must not have been developed, or derived from a Wizard developed, with financial or preferential support from the Administrator. Such Wizards include, but are not limited to, those that received funding or investment for their development, or were developed under contract, from the Administrator any time prior to the end of Hackathon Submission Period. The Poster, at their sole discretion, may disqualify a Wizard, if awarding a prize to the Wizard would create a real or apparent conflict of interest.
7.2. Text Description, Image, and Video Requirements
(i) Text Description: The text description should explain the features and functionality of your Wizard.
(ii) Images: The image(s) should be photographs or screenshots of your working Wizard including advanced commands.
(iii) Video: The required video portion of the Submission:
a. should be less than three (3) minutes;
b. must include footage that clearly explains the Wizard’s features and functionality through a comprehensive demo of the wizard;
c. must be uploaded to YouTube, Vimeo, or Facebook Video, , and a link to the video must be provided on the submission form on the Hackathon Website; and
d. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.
7.3. Submission Modifications
(i) 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 Competition 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.
(ii) Modifications after the Submission Period. The Poster may permit you to modify part of your Submission after the Submission Period for the purpose of removing 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 Poster permits. The Administrator may add the Competition hashtag to the demonstration video on behalf of the submitter.
7.4. Submission Procedure
Makers must do the following to participate in the Hackathon (the “Submission”):
7.4.1. Register for the Hackathon on the Hackathon Website by clicking the “Register for this Hackathon” button. To complete registration, sign up to create a Devpost account, or log in with an existing Devpost account. There is no charge for creating a Devpost account. This will enable you to receive important updates and access the “Enter a Submission” page.
7.4.2. Be a Certified Kryon RPA Developer. If you are not currently a Kryon Certified RPA Developer, you can complete the free training in the following address: https://academy.kryonsystems.com/account/login/?LP=69730. There is no charge for the training. By completing the training you will know best how to leverage the Kryon Solution.
7.4.3. Access to the full version of Kryon Studio 20.3 is provided via email as part of the automated Starter Kit sent to all registrants upon registration to the Hackathon. Makers’ access and use of Kryon Studio is subject to the terms and conditions of Kryon’s Standard End User License Agreement at: http://www.kryonsystems.com/CompanyFiles/Kryon-Systems-Inc.-End-User-License-Agreement-EULA.pdf
7.4.4. Develop a new solution (Wizard) using Kryon Studio that helps organizations solve business challenges and/or is within the themes of Bot Camp.
7.4.5. Create a video that includes footage that clearly explains your wizard’s features and functionality through a comprehensive demonstration. Maximum of 3 minutes.
7.4.6. Submit your wizard as a zip file that contains an exported word file with screen shots of advanced commands and a .lwiz file.
7.4.7. Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website during the Hackathon Submission Period, and follow the requirements below.
8. SUBMISSION RIGHTS
8.1. Maker Rights: Subject to the licenses described below, any applicable intellectual property rights to a Submission and/or Wizard will remain with the Maker.
8.2. Poster Rights: By entering the Hackathon, Maker grants to the Poster, each of their parent companies, subsidiaries, and affiliates, and any other third parties acting on behalf of any of the foregoing, and the successors, licensees and assigns of each of the foregoing (all of the foregoing, collectively, the “Contest Entities”), a royalty-free, non-exclusive, worldwide perpetual license to display publicly and use for promotional purposes the Submission and/or the Wizard, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission and/or the Wizard on websites and applications of the Poster and the Contest Entities, including the Hackathon Website, and display and promotion of the Submission and/or the Wizard in any other media, worldwide.
8.3. Submissions may 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.
8.4. Makers represent and warrant that the Contest Entities are free to use Makers’ Submission and/or Wizard in the manner described above, as provided or as modified by the Poster, without obtaining permission or license from any third party and without any compensation to Makers.
9.1. Eligible Submissions will be evaluated by the Judges. Judges may be employees of the Poster or external, 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 Poster.
9.2. The Judges will score eligible Wizard submissions using the following equally weighted criteria (the “Judging Criteria”):
9.2.1. Impact (Impact of particular Wizard on today’s real-world problems);
9.2.2. Comprehensiveness (Does the Wizard comprehensively address the problem it sets to solve? Does the Wizard represent a full-business process?);
9.2.3. Platform Use (Does the Wizard have both visual and advanced command steps? Does the wizard use advanced commands from 5 different categories?);
9.2.4. Resiliency (Does the Wizard adapt to changes in an environment where it is deployed or behaviour of the user? How complex is the wizard?);
9.2.5. Reusability (Is the Wizard built with modularity and reusability in mind?);
9.2.6. Scalability (Does the Wizard rely on user inputs/interactions (hybrid automation) or can it run completely independently?
9.3. The Maker(s) whose Submissions achieved the highest overall scores based on the applicable Judging Criteria, will become potential winners of a Prize.
9.4. It is clarified that Judges are not required to test the Wizard and may choose to judge based solely on the text description, images, and video provided in the Submission.
9.5. In the event of a two or more Submissions for each Prize listed in Section 9 below achieved the same overall score, the 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.
9.6. Bonus points may be earned in the following scenarios:(up to 3 points)
9.6.1. By posting about the Wizard in the Developer Corner of KryoNet, Kryon’s Community for RPA developers;
9.6.2. Using an integrated script (Java, Python, etc) in Wizard;
9.6.3. Using OCR capabilities such as Microsoft AI Booster.
9.7. All expenses or costs associated with the acceptance or use of the prize or any component of the prize are the responsibility of the winner. The prize is awarded “as is” and without any warranty.
First prize - Gold
Cash prize of USD 5,000 for the winning Maker/s
Second prize - Silver
Cash prize of USD 3,500 for the runner-up Maker/s
Third prize - Bronze
Cash prize of USD 1,500 for the 2nd runner-up Maker/s
10.1. Prizes will be payable to the Maker, if an individual, to the Maker’s Team Leader, if a Team, or to the Organization, if the Maker is an Organization. It will be the responsibility of the winning Maker’s Team Leader, to allocate the prize among their Team or Organization’s participating members, as the Representative deems appropriate. Prizes are payable via any means of the Poster's choosing, whether electronic or not, and are payable only after receipt and verification of the Winner’s Verification Documents (as described below). A winning Maker may be required to provide a mailing address, bank information, and/or create an account with an electronic payment provider of the Poster’s choosing in order to receive payment. Any failure to provide correct information on the Verification Documents (as described below), or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification or the Maker, or forfeiture of a Prize, at the sole discretion of the Poster.
10.2. In order to receive a Prize, Potential Winners required to fill verification documents, such as affidavit(s) of eligibility and liability/publicity release(s), and any applicable tax forms (the : “Verification Documents”) and send it to the Administrator within 10 days of receipt. The Delivery Timeframe of the Prize is within 45 days of the Administrator’s receipt of the Required Forms verification documents
10.3. Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a Prize, including but not limited to, wiring fees and applicable taxes in their jurisdiction of residence.
10.4. The award of a Prize to a potential winner is subject to verification of the identity, qualifications, and role of the potential winner in the creation of the Submission.
10.5. The final decision to designate a winner shall be made by the Poster.
11. ENTRY CONDITIONS AND RELEASE
11.1. The Poster is not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Makers. Proof of sending or submitting will not be deemed to be proof of receipt by the Poster.
11.2. By entering the Hackathon you release, indemnify, defend and hold harmless each of the Contest Entities, the Prize suppliers and any other organizations of the Hackathon, from and against any and all claims, expenses, and liabilities in the matter of this Hackathon.
11.3. Each Maker acknowledges that each of the Contest Entities engages and has engaged and will in the future engage in the development, preparation, production, acquisition and dissemination of software, technology and other material (collectively, “Materials”), including without limitation Materials that may be similar or identical to a Maker’s Submission, and that other people may previously have submitted to one or more of the Contest Entities Materials that are similar or identical to a Submission. Each Maker agrees that it will not be entitled to any compensation or credit in connection with, and will not have any other legal, equitable or other rights of any nature with respect to, the use by any of the Contest Entities of any Material that is similar or identical to any Submission or any component thereof. As an inducement to Poster to accept the Maker’s Entry, each Maker hereby waives any claim or right of action against any of the Contest Entities in connection with the Contest Entities’ use of any Materials (or any portions thereof), whether or not such Materials are similar or identical to an Maker’s Submission or contain any features, ideas, material and/or elements that are similar or identical to those contained in an Maker’s Submission. Without limitation of the foregoing, the Contest Entities will have the right to use, without any payment or other obligation whatsoever to any Maker, any part of any Submission, and any idea or concept contained therein, that (a) is similar or identical to, or contains elements encompassed in, any material or concept that has been developed, produced or disseminated or is under consideration or in development by or for any of the Contest Entities before or at the time of the Maker’s submission of the Submission, (b) is not unique, novel, original and concrete so as to be entitled to protection under applicable laws, (c) has been made public by anyone at the time of its submission in the Hackathon or otherwise is in the public domain, (d) would be freely usable by a third party if it had not been submitted as a Submission or the subject of any agreement, (e) is not protected by United States copyright law or (f) is similar or identical to, or contains elements encompassed in, an idea, concept or material that is independently created by any Contest Entity or any third party. Acceptance of a Submission is not an admission by any Contest Entity of the novelty or originality of the Submission.
12.1. By participating in the Hackathon you consent to the use of personal information about you, if you are a winner, by the Poster and third parties acting on its behalf. Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes advertising and promotional purposes.
12.2. The duration of said consent is for a period of one year following the conclusion of the Hackathon. This consent applies, as applicable, to all members a Maker’s Team that participated in the winning Submission.
13.1. Except where prohibited by law, as a condition of participating in this Hackathon, Maker agrees that:
13.1.1. Any and all disputes and causes of action arising out of or connected with this Hackathon, or any Prizes awarded, shall be resolved individually, without resort to any form of class action lawsuit, and exclusively by final and binding arbitration under the rules of New York, NY, USA.
13.1.2. The laws of the State of New York, USA shall govern the interpretation, enforcement and all proceedings at such arbitration; and
13.1.3. Judgment upon such arbitration award may be entered in any court having jurisdiction.
14. GENERAL CONDITIONS
14.1. Poster reserve the right, in its sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, including the Rules, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control. It is recommended that Makers will check the Hackathon Website for any updates regarding to the Hackathon schedule and terms.
14.2. Poster may decide, at its sole discretion, to not declare any of the Makers as the winners/runners-up/2nd runners-up, in the event to their opinion all of Submissions failed to meet any of the requirements of the Hackathon.
14.3. Poster reserve the right in their sole discretion to disqualify any individual or Maker it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.
14.4. The terms and conditions of the Rules shall prevail any other document and/or statements regarding the Hackathon.
14.5. If a Maker or prospective Maker believes that any Rule is or may be unclear or ambiguous, they must submit a written request for clarification within the Submission Period.
14.6. The Administrator’s failure to enforce any term of these Rules shall not constitute a waiver of that provision. Should any provision of these Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to a Maker, such illegality or unenforceability shall leave the remainder of these Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid.