Pi-EV 2022 Information Rules Document - V2 - March 16 2022

Pi-EV 2022
THE 6TH ANNUAL FS ELECTRIC

VEHICLE CONCEPT CHALLENGE
BY FORMULA BHARAT
Document Version
Version 2 / March 16, 2022

Pi-EV 2022 - 6th ANNUAL FSEV CONCEPT CHALLENGE
BY FORMULA BHARAT
Revision Log
Date Status Description Initials
February 22, 2022 Release FSEV 2022 Information Rules Book C.F.
March 16, 2022 Name Change FSEV is now renamed to ‘Pi-EV’ C.F.
Curiosum Tech Private Limited Released: February 22, 2022 C.F. Page 2 / 19
Revised: March 16, 2022 C.F.
BY FORMULA BHARAT
TABLE OF CONTENTS
ADMINISTRATIVE REGULATIONS 4
COMPETITION OVERVIEW 4
Competition Purpose 4
Competition Objective 4
Competition Procedure 4
Definition of EV Powertrain 6
Competition Awards 6
Competition Registration 7
RULES OF CONDUCT 8
General Officials Authority 8
Concerns and Complaints 8
GENERAL REQUIREMENTS FOR TEAMS 8
Teams per University 8
Team Members 8
Student Status 9
Team Member Registration 9
Participation Certificates 9
GENERAL RULES 9
Forfeit for Non-Appearance 9
Negative Scoring 10
Testing and Work Safety 10
Q&A Slots Scheduling 10
Technical Issues 10
DOCUMENTATION AND DEADLINES 10
Required Documents and Forms 10
Submission Notes 11
Submission Guidelines 11
Penalties 12
COMPETITION EVENTS 13
Procurement Strategy 13
Procurement Report (PR) 13
Procurement Q&A 14
Team Management Strategy 14
Team Management Report (MGMT) 14
Team Management Q&A 15
Software and Intelligence Integration 15
BY FORMULA BHARAT
Purpose of the Software and Intelligence event 15

Software Architecture Report (SA) 15
Algorithm Development Report (AI) 16
Software and Intelligence Q&A 16
Scoring 16
Engineering Design 16
Purpose of the Engineering Design event 16
Failure Mode and Effects Analysis (FMEA) 16
Design Specifications Sheet (DSS) 17
Engineering Design Presentation (EDP) 17
Engineering Design Supporting Document (SUP) 17
Engineering Design Q&A 18
BY FORMULA BHARAT
A ADMINISTRATIVE REGULATIONS
A.1. COMPETITION OVERVIEW
A.1.1. Competition Purpose

A.1.1.1. Under the Paris Agreement at the UN Climate Conference in May 2017, India declared that
only electric cars will be on sale in 2030. In light of this push by the government to move
away from fossil fuels and to embrace electric technology, the host organization has put
together a series of initiatives under the Formula Bharat banner to build a platform for
students interested in switching to the Formula Student Electric category. The steps include
hosting a Formula Student (FS) Electric Vehicle Concept Challenge to prepare teams
interested in participating in the Electric Category at the Formula Bharat competition.
A.1.2. Competition Objective

A.1.2.1. The objectives of the challenge include the following:
● To provide a platform for Indian students interested in building an FS Electric Vehicle to

compete in India.
● To assist teams with mentors who will be able to guide them through the process of
designing and manufacturing an FS Electric Vehicle.
● To provide interested teams considering the electric category in Formula Bharat 2024
with a 2 year lead to design their vehicle, procure resources, manufacture the prototype
and gain testing time.
● To improve the level of Indian FS Electric teams to the Global Formula Student
competition level.
A.1.3. Competition Procedure

A.1.3.1. The competition is organized by Curiosum Tech Private Limited, and shall be hosted online.
A.1.3.2. The competition shall be based around the EV Powertrain of a typical Formula Student
Electric Vehicle.
A.1.3.3. Unlike a typical Formula Student competition, a physical prototype of the vehicle is not
required for this challenge, however, it is recommended to present any physical components
/ assemblies, if available.
BY FORMULA BHARAT
A.1.3.4. The design and rules guidelines for the EV Powertrain shall be followed from the most recent
Formula Bharat released rules booklet, specifically the sections [T] General Technical
Requirements and [EV] Electric Vehicles. The Formula Bharat rules booklet can be
downloaded from www.formulabharat.com/downloads.
A.1.3.5. The following scored events are involved in the competition:
Category Aspects Points
Procurement Strategy Procurement Strategy Report + Q&A 75
Team Management Team Management Strategy Report + Q&A 75
Software and Intelligence Software Architecture Report + Algorithm 50

Integration Development Report + (Q&A for finalists only)
Engineering Design FMEA + Engineering Design Presentation + 200

Supporting Document + Q&A
TOTAL 400
There shall be no semi-finals.
A.1.3.6. The events shall also involve its own Q&A session with the relevant judging groups in
scheduled time slots.
A.1.3.7. All submission portals, deadlines, scheduling slots and scoring rubrics related to the
competition shall be located on www.formulabharat.com/fsev.
A.1.3.8. Any changes to the competition details shall be communicated with the Team Captain from
formulabharat@gmail.com.
A.1.3.9. The competition and its organizers will operate from India. In all communication, any dates
and time slots mentioned will be considered as Indian Standard Time (IST) unless stated
otherwise.
A.1.3.10. Queries with regards to the competition’s various aspects must be directed to the relevant
emails listed below:
● Financial related queries (registration fees, payment etc.): info@curiosumtech.in

● General Pi-EV related (administration, competition events) rule-queries, participation
certificates: formulabharat@gmail.com
● EV-specific technical rules queries: formulabharat-electric@googlegroups.com
● Non-EV technical rules queries: formulabharat-rules@googlegroups.com
Additionally, teams may also post their queries on www.formulabharat.com/forum.
BY FORMULA BHARAT
A.1.4. Definition of EV Powertrain

A.1.4.1. The EV Powertrain for the purpose of the FSEV Concept Challenge is defined as follows:
● Tractive System Energy Storage (Battery Pack)
○ Accumulator Container
○ Cells
○ Accumulator Management System ( Temperature /Voltage /Current Sensors)
○ AIR’s, Fuse’s, Bus Bars, Maintenance Plugs, Pre-Charge Circuit, Voltage
Indicator.
● High Voltage Wiring and Connectors
○ High Voltage Cables , Conduits ,Connectors and High Voltage Disconnect
● Electric Motor and Motor Controller
● Transmission
● Charging
○ Charger, charging port
● Vehicle Supervisory Controller
○ Accelerator and Brake Pedal Sensor
○ APPS Plausibility and APPS/Brake Plausibility
○ Torque Control, Power Limitation Control, Ready to Drive Mode
● EV Safety Circuits
○ Discharge Circuit
○ Shutdown Circuit
○ Interlock’s and Insulation Monitoring Device.
○ TSAL, Ready to Drive Sound.
● Low Voltage System
○ DC –DC Converter
○ LV Battery
○ Thermal Management and Cooling
○ Additional Circuits (Data loggers, extra indications etc.) *optional
A.1.5. Competition Awards

A.1.5.1. The following are a list of tentative awards (however, not limited to) that will be provided by
the competition:
Overall:
● Winner / 1st Place

● 2nd Place
● 3rd Place
● 4th Place
Procurement Strategy:
BY FORMULA BHARAT
● 2nd Place
Team Management:

● 2nd Place
Software and Intelligence Integration:

● 2nd Place
Engineering Design:

● 2nd Place
● 3rd Place
● Best Battery Design
● Best Powertrain Package
● Best FMEA Report
Any additional or special awards shall be mentioned on www.formulabharat.com/fsev
A.1.5.2. Winners of the above categories will receive physical awards by mail.
A.1.5.3. The Overall Top 4 teams will have a spot reserved on the registration list at Formula Bharat
2024 Electric Category without having to participate in the registration quiz, provided that the
teams submit the pre-registration information required at the time of registration for the
Formula Bharat 2024 competition.
A.1.5.4. The Overall Top 4 teams will also receive a subsidy towards the registration fees at the
Formula Bharat 2024 Electric Category in the following manner:
● 1st Place: INR 15,000

● 2nd Place: INR 10,000
● 3rd Place: INR 7,000
● 4th Place: INR 4,500
A.1.6. Competition Registration

A.1.6.1. The registration fees, methods of payment and relevant deadlines shall be outlined on
www.formulabharat.com/fsev.
A.2. RULES OF CONDUCT
BY FORMULA BHARAT
A.2.1. General Officials Authority

A.2.1.1. The officials reserve the right to revise the schedule of the competition and/or interpret or
modify the competition rules at any time and in any manner that is, in their sole judgment,
required for safe, fair and efficient operation.
A.2.1.2. All team members are required to cooperate with, and follow all instructions from the officials.
A.2.2. Concerns and Complaints

A.2.2.1. For any concerns and complaints with regards to the event execution, teams must write in an
email to formulabharat@gmail.com.
A.3. GENERAL REQUIREMENTS FOR TEAMS
A.3.1. Teams per University

A.3.1.1. A university may register more than one team.
Note: This is not applicable to the Formula Bharat competition where a university may
register only one team per competition category (CV / EV). Teams must take this into
account prior to registering for the competition.
A.3.1.2. Teams which are formed with members from two or more universities are treated as a single
team. In such a case, the team must inform the organizers upon registration as to which
university will be represented.
A.3.1.3. In the case where multiple colleges located in multiple cities or districts are grouped under a
common University, either autonomous or through affiliation, the team must register under
their College name.
A.3.2. Team Members

A.3.2.1. A team member may only be part of one team and take part in the competition events for
only one team.
A.3.2.2. Each team must have one team member identified as the team captain. The team captain is
the main contact person for the officials during the registration process and the competition.
A.3.2.3. Persons who have previously attended any official event as a judge are not allowed to
participate as team members.
A.3.2.4. The team captain must have a “current‟ student status at the attended College or University,
at the time of the competition.
BY FORMULA BHARAT
A.3.2.5. In the case that the team decides to build and test a physical model, all team members are
required to have basic electrical safety training to ensure they are aware of the risks and
know how to respond in the event of an incident. Teams must follow the ESO requirements
as mentioned in the Formula Student rulebook.
A.3.3. Student Status

A.3.3.1. Team members must be enrolled as degree seeking undergraduate or graduate students in
any university.
A.3.3.2. Team members must have a graduation date of 2024 and above. To attest this, a faculty
member must email in a letter stating the list of registered team members, their years of
graduation and a confirmation that all members are registered students at the institution with
a graduation year of 2024 and above.
A.3.3.3. Students who have already graduated from a degree program and are seeking another
degree of the same level or below are not allowed to participate.
A.3.3.4. Students seeking a PhD degree/PhD students or equivalent are not allowed to participate.
A.3.4. Team Member Registration

A.3.4.1. The competition allows for a complimentary registration of 15 members per team.
A.3.4.2. A maximum of 25 team members may participate on a team.
A.3.5. Participation Certificates

A.3.5.1. All registered team members will receive electronic participation certificates after the end of
the competition, post verification of A.3.3.2.
A.3.5.2. Each team will be required to submit a Team Member Information (TMI) document to the
organizers to avail the certificates. The organizers shall make the template available during
the competition.
A.4. GENERAL RULES
A.4.1. Forfeit for Non-Appearance

A.4.1.1. It is the responsibility of each team to be in the right place at the right time.
A.4.1.2. If a team is not present and ready to compete at the scheduled time, they forfeit attempt at
that event.
A.4.2. Negative Scoring
BY FORMULA BHARAT
A.4.2.1. Should the team’s total score or individual static score result in a negative score (as in below
0 points) due to late submission or other penalties, the specific result will be capped at 0
points.
A.4.3. Testing and Work Safety

A.4.3.1. Competition organizers are not responsible for the use of the equipment and vehicles
outside of their competition.
A.4.3.2. The competition officials disassociate themselves from all activities of the teams besides
their own competition and associated events.
A.4.3.3. All teams are advised to follow common practices and common sense when working on the
vehicle and high-voltage related systems when operating the vehicle and systems, before,
during and after a competition.
A.4.4. Q&A Slots Scheduling

A.4.4.1. Teams will have the opportunity to schedule slots for their participation in the time frame as
mentioned on www.formulabharat.com/fsev.
A.4.4.2. It is not required for all team members to attend each Q&A session that the team is assigned
to.
A.4.5. Technical Issues

A.4.5.1. In case of technical issues from the organizer’s end during the Q&A sessions which cause
the session to stop abruptly, the affected teams shall be contacted via email and a new slot
shall be provided. This is to the discretion of the competition organizers.
A.5. DOCUMENTATION AND DEADLINES
A.5.1. Required Documents and Forms

A.5.1.1. The following documents and forms must be submitted by the action deadlines defined on
www.formulabharat.com/fsev:
● Group A: FMEA, PR, MGMT, DSS, EDP, ED Supporting Document

● Group B: SA, AI
● Group C: TMI, Faculty Letter
BY FORMULA BHARAT
A.5.2. Submission Notes

A.5.2.1. Uploaded documents may only be viewed by members of the submitting team, authorized
judges and officials.
A.5.2.2. By submitting documents via the competition website, the team agrees that they may be
reproduced and distributed by the officials, in both complete and edited versions, for
educational purpose.
A.5.2.3. Documents that are largely incomplete or not readable will be considered as not submitted.
A.5.3. Submission Guidelines

A.5.3.1. A submission portal will be made available on www.formulabharat.com/fsev. Documents
must be named correctly and uploaded in the correct format by the deadline.
A.5.3.2. Documents must be named as ‘Team#_TeamName_PiEV -DocumentName_Year_V#’. Eg:

E09_Infiniti Racing_PiEV -FMEA_2021_V1.
Note: V# is considered as a Version number. All consecutive files sent in as corrections or

updates must proceed with V2 and so on.
A.5.3.3. Unless stated otherwise, the page size for documents submitted will be restricted to A4
paper size.
A.5.3.4. Teams are required to make the submissions in the following formats:
Submission Abbr. Template Format Max* File

Available Size
Failure Modes and Effects Analysts FMEA Y .xls / .xlsx 500 KB
Procurement Report PR N .pdf 10 MB
Team Management Report MGMT N .pdf 7 MB
Software Architecture Report SA Y .xls / .xlsx 7 MB
Algorithm Development Report AI Y .xls / .xlsx 7 MB
Design Specifications Sheet DSS Y .xls / .xlsx 500 KB
Engineering Design Presentation EDP N Refer to C.4.4. -

and C.4.5.
Engineering Design Supporting Document SUP N .pdf 7 MB
A.5.3.5. The following are guidelines for non-template documents:
BY FORMULA BHARAT
● Header of every page (where applicable) must contain the Team Number, Registered
Team Name, Institution Name and Document Name.
● Footer of every page (where applicable) must include Page Number and Total Number
of Pages (Example: Page 1/3 if referring to the 1st page out of 3 pages etc.)
● Format file based on table mentioned above (Column 4: Format).
A.5.4. Penalties
A.5.4.1. Late submissions:
For submissions of Groups A later than the initial deadline, 5 penalty points are deducted for
every commenced 24 hours they are overdue. These will be deducted from the team’s
overall score up to a maximum of 35 points for each deadline independently.
For submissions of Groups B later than the initial deadline, 5 penalty points are deducted for
every commenced 24 hours they are overdue. These will be deducted from the independent
event’s score up to a maximum of 35 points for each deadline independently.
A.5.4.2. No submission:
Teams which miss the initial deadlines of Group A by more than 168 hours (7 days) will
receive zero points for the related event and shall forfeit the opportunity to participate in the
related event’s Q&A session. In that case, no additional penalty points are given.
Teams which miss submission of more than two of Group A documents by more than 168
hours (7 days) will be de-registered from the competition.
Teams which miss the initial deadlines of Group B by more than 168 hours (7 days) will
receive zero points for the related event. In that case, no additional penalty points are given.
A.5.4.3. Incorrect File Naming:
For submissions of Groups A and B with incorrect file naming, 2 penalty points will be
deducted from the team’s overall score for each submission independently.
A.5.4.4. Incorrect Format
For submissions and related events of Groups A and B with incorrect file format (type, page
limit, time limit, etc.), the following number of points will be deducted from the team’s overall
score for each submission or event independently.
● Incorrect file type: 5 penalty points

● Incorrect template: Considered as non-submission
● Incorrect EDP link within ED supporting document: Considered as non-submission
● Exceeding page / slide limit: 10 penalty points
● Exceeding time limit: 10 penalty points
● (For non-template files) Missing Team Number, Team Name, Institution Name,
Document Name in Header and Page number, Total Number of pages in Footer: 0-5
penalty points
BY FORMULA BHARAT
● Missed Q&A Session with less than 48 hour notice: 50 points
While there is no penalty for file size, teams are requested to keep to the minimum possible
size to ensure that judges can easily download or review the file on any device and to also
ensure that the team avoids uploading issues.
C COMPETITION EVENTS
C.1. Procurement Strategy
C.1.1. Procurement Report (PR)

C.1.1.1. The purpose of the Procurement Report (PR) is to determine whether the team is aware of
the necessary timeline and costs involved to procure components required for the
manufacture and build of the EV Powertrain system.
C.1.1.2. The report shall be judged on strategy, budget allocation, cost vs. performance decisions,
timeline, detail and completeness of report, risk management strategy and presentation of
contents of the document.
C.1.1.3. The report shall be divided into two sections: Main and Appendix.
C.1.1.4. The Main section shall have no cover page. This section is restricted to a maximum of 4
pages:
● Page 1: Procurement, manufacture and build timeline of EV Powertrain. A team may

use the following tools (however not restricted to) Gantt Chart, Project Network, Project
Management Timeline, Kanban Board, Cross-Functional Flowchart, Scrum Board etc.
● Page 2: A table with list of components, costs for purchase and delivery, possible list of
vendors etc. The more detailed the table, the better the chances of success in reporting.
● Page 3: EV Powertrain Budget
● Page 4: This page is dedicated to reasoning or explanations where the team can
expand on certain decisions that had to be made due to circumstances.
C.1.1.5. The Appendix section may contain any supporting documents such as receipts, quotations,
etc. which may aid the contents provided in the Main section of the report.
C.1.1.6. The Appendix section is located after the Main section and must contain a cover page
stating ‘APPENDIX’.
BY FORMULA BHARAT
C.1.1.7. The Appendix section must contain a ‘Table of Contents’ which is either linked or contains
page numbers. If linked, please ensure that links are working after the document has been
converted to .pdf format.
C.1.1.8. There is no page limit to the Appendix section. However every title or heading number in the
Appendix must be referenced in the Main Section.
C.1.1.9. The Main and Appendix Sections can contain ‘external links’ to assist with decluttering of the
report.
Note: The longer the Appendix section, the less reviewed it will be. So only include relevant
information in the Appendix that will directly assist the Main section of the report, and provide
external links to information that may be helpful but is not critical to the judging of the report.
C.1.2. Procurement Q&A

C.1.2.1. The Q&A session dedicated to Procurement Strategy shall be of a total of 20 minutes.
● 5 mins - Setup
● 10 mins - Judges’ clarifications and queries
● 5 mins - Judges’ feedback
C.1.2.2. The team may introduce themselves at the session, however, no formal presentation is
required.
C.2. Team Management Strategy
C.2.1. Team Management Report (MGMT)

C.2.1.1. The purpose of the Team Management (MGMT) Report is to determine whether the team
has a structured approach to categorize, assign and realise its tasks.
C.2.1.2. The report shall be judged on the presence of areas mentioned in C.2.1.4, detail and
completeness of report, and presentation of contents of the document.
C.2.1.3. The report shall be divided into two sections: Main and Appendix.
C.2.1.4. The Main section must include the following areas (but is not limited to):
● Team Goals, Objectives and Philosophy, Success Criteria etc.

● Team Structure, Hierarchy, Voting, Decision-making process, Conflict Management etc.
● Project Timeline: Planning timeline with risk analysis, assumptions, constraints and
mitigation, tools used etc.
● Human Resource capability: Recruitment, Retention, Change Management etc.
● Financial Management: Budget, Expense and Reimbursement Protocols etc.
● Communication Methods and Protocols
● Media and Marketing Strategies and Protocols
BY FORMULA BHARAT
C.2.1.5. The Main section is restricted to a maximum of 10 pages.
C.2.1.6. The Appendix section may contain any supporting documents such as team photos, chat
logs etc., which may aid the contents provided in the Main section of the report.
C.2.1.7. The Appendix section is located after the Main section and must contain a cover page
stating ‘APPENDIX’.
C.2.1.8. The Appendix section must contain a ‘Table of Contents’ which is either linked or contains
page numbers. If linked, please ensure that links are working after the document has been
converted to .pdf format.
C.2.1.9. There is no page limit to the Appendix section. However every title or heading number in the
Appendix must be referenced in the Main Section.
C.2.1.10. The Main and Appendix Sections can contain ‘external links’ to assist with decluttering of the
report.
Note: The longer the Appendix section, the less reviewed it will be. So only include relevant
information in the Appendix that will directly assist the Main section of the report, and provide
external links to information that may be helpful but is not critical to the judging of the report.
C.2.2. Team Management Q&A

C.2.2.1. The Q&A session dedicated to Team Management Strategy shall be of a total of 20 minutes.
● 5 mins - Setup
required.
C.3. Software and Intelligence Integration
C.3.1. Purpose of the Software and Intelligence event

C.3.1.1. The purpose of the software and intelligence event is to evaluate the team’s capabilities in
architecting, developing, testing and deploying software and intelligence in their electric
vehicle powertrain concept.
C.3.1.2. The team will be challenged on their software architecture concept and the algorithm
development for the same.
C.3.2. Software Architecture Report (SA)
BY FORMULA BHARAT
C.3.2.1. The template can be downloaded from www.formulabharat.com/fsev.
C.3.3. Algorithm Development Report (AI)

C.3.4. Software and Intelligence Q&A

C.3.4.1. Only selected teams who have been considered for the finals, post report review, will be able
to participate in the Q&A session of the Software and Intelligence event.
C.3.4.2. The Q&A session dedicated to Software and Intelligence shall be of a total of 25 minutes.
● 5 mins - Setup
required.
C.3.5. Scoring
C.3.5.1. A maximum of 40 points can be awarded to the highest scoring non-finalist team in the
Software and Intelligence event.
C.3.5.2. Finalists may receive a score of between 41 to 50 immediately after the finalists Q&A by all
judges.
C.4. Engineering Design
C.4.1. Purpose of the Engineering Design event

C.4.1.1. The purpose of the engineering design event is to evaluate the team’s engineering process
and effort that went into the design of an EV Powertrain system, meeting the intent of the
competition and alignment with the Formula Bharat rules book.
C.4.1.2. Proprietary components and systems that are incorporated into the design as finished items
are not evaluated as a student designed unit, but are only assessed on the team’s selection
and application of that unit.
C.4.2. Failure Mode and Effects Analysis (FMEA)

C.4.2.1. The purpose of the Failure Modes and Effects Analysis (FMEA) document is to review as
many components, assemblies, and subsystems as possible to identify potential failure
modes in a system and their causes and effects.
BY FORMULA BHARAT
C.4.3. Design Specifications Sheet (DSS)

C.4.4. Engineering Design Presentation (EDP)

C.4.4.1. The EDP must be considered as the team’s design pitch to a senior-level Engineering
Design group.
C.4.4.2. The EDP must be presented by registered team members only.
C.4.4.3. The EDP is a maximum 15 minute recorded video presentation which should contain a brief
description of the overall EV Powertrain system with a review and derivation of the team’s
design objectives. Any information to scope, explain or highlight design features, concepts,
methods or objectives to express the value and performance of the vehicle to the judges
shall be included at the teams’ discretion.
C.4.4.4. The EDP could contain but is not limited to:

● Team Introduction
● Goals and Design Objectives for the season
● Cover major points in each subsystem within the EV Powertrain system:
❖ Design elements
❖ Design reasoning and considerations (benefits, constraints, restrictions etc.)
❖ Any improvements from previous year's design
TIP: Do not cram too many slides within a minute of presentation. Try to keep the slides less
heavy on text.
C.4.4.5. The EDP must be uploaded on a video sharing platform of your choice (Youtube, Vimeo
etc.). Please do not upload on Google Drive. The video link must be publicly accessible. If
uploaded on Youtube, the privacy setting of the video must be changed to 'Unlisted' so that
only those with the link can view the video and it will not be displayed publicly on your
channel as well.
C.4.4.6. The EDP link is submitted within the supporting document. Refer to C.4.5 for details.
C.4.5. Engineering Design Supporting Document (SUP)

C.4.5.1. The supporting document may contain additional detail such as simulations, calculations,
flow charts etc. that would allow the judges to understand design considerations made,
including any further research and analysis conducted by the team.
C.4.5.2. The cover page of the supporting document must contain the link to the EDP video.
BY FORMULA BHARAT
C.4.5.3. The supporting document must contain a ‘Table of Contents’ which is either linked or
contains page numbers. If linked, please ensure that links are working after the document
has been converted to .pdf format.
C.4.5.4. The supporting document is limited to a maximum of 50 pages, not including the cover page
and the Table of Contents.
C.4.5.5. The supporting document can contain ‘external links’ to assist with decluttering of the
document.
Note 1: The longer the supporting document, the less reviewed it will be. So only include
relevant information in this area, and provide external links to information that may be helpful
but is not critical to the judging of the EDP.
Note 2: The supporting document may or may not be reviewed in its entirety. It solely
depends on whether the judge wants to seek additional clarification that isn't already
provided in the presentation.
C.4.6. Engineering Design Q&A

C.4.6.1. The Q&A session dedicated to Engineering Design shall be of a total of 25 minutes.
● 5 mins - Setup
required.

Pi-EV 2022 Information Rules Document - V2 - March 16 2022

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pi-EV 2022 Information Rules Document - V2 - March 16 2022

Uploaded by

Copyright:

Available Formats

Pi-EV 2022

THE 6TH ANNUAL FS ELECTRIC

Version 2 / March 16, 2022

Date Status Description Initials

Purpose of the Software and Intelligence event 15

A.1. COMPETITION OVERVIEW

A.1.1. Competition Purpose

A.1.2. Competition Objective

● To provide a platform for Indian students interested in building an FS Electric Vehicle to

A.1.3. Competition Procedure

A.1.3.5. The following scored events are involved in the competition:

Category Aspects Points

Procurement Strategy Procurement Strategy Report + Q&A 75

Team Management Team Management Strategy Report + Q&A 75

Software and Intelligence Software Architecture Report + Algorithm 50

Engineering Design FMEA + Engineering Design Presentation + 200

There shall be no semi-finals.

● Financial related queries (registration fees, payment etc.): info@curiosumtech.in

Additionally, teams may also post their queries on www.formulabharat.com/forum.

A.1.4. Definition of EV Powertrain

A.1.5. Competition Awards

● Winner / 1st Place

● Winner / 1st Place

● Winner / 1st Place

Software and Intelligence Integration:

● Winner / 1st Place

● Winner / 1st Place

Any additional or special awards shall be mentioned on www.formulabharat.com/fsev

● 1st Place: INR 15,000

A.1.6. Competition Registration

A.2. RULES OF CONDUCT

A.2.1. General Officials Authority

A.2.2. Concerns and Complaints

A.3. GENERAL REQUIREMENTS FOR TEAMS

A.3.1. Teams per University

A.3.2. Team Members

A.3.3. Student Status

A.3.4. Team Member Registration

A.3.4.2. A maximum of 25 team members may participate on a team.

A.3.5. Participation Certificates

A.4. GENERAL RULES

A.4.1. Forfeit for Non-Appearance

A.4.2. Negative Scoring

A.4.3. Testing and Work Safety

A.4.4. Q&A Slots Scheduling

A.4.5. Technical Issues

A.5. DOCUMENTATION AND DEADLINES

A.5.1. Required Documents and Forms

● Group A: FMEA, PR, MGMT, DSS, EDP, ED Supporting Document

A.5.2. Submission Notes

A.5.3. Submission Guidelines

A.5.3.2. Documents must be named as ‘Team#_TeamName_PiEV -DocumentName_Year_V#’. Eg:

Note: V# is considered as a Version number. All consecutive files sent in as corrections or

Submission Abbr. Template Format Max* File

Failure Modes and Effects Analysts FMEA Y .xls / .xlsx 500 KB

Procurement Report PR N .pdf 10 MB

Team Management Report MGMT N .pdf 7 MB

Software Architecture Report SA Y .xls / .xlsx 7 MB

Algorithm Development Report AI Y .xls / .xlsx 7 MB

Design Specifications Sheet DSS Y .xls / .xlsx 500 KB

Engineering Design Presentation EDP N Refer to C.4.4. -

Engineering Design Supporting Document SUP N .pdf 7 MB

A.5.3.5. The following are guidelines for non-template documents:

A.5.4.3. Incorrect File Naming: