Sei sulla pagina 1di 24

Efficycle 2016

Project Plan
Duration
Task ID Task/Activity Description Start Date
(Days)

A Part Selection 14 4/4/2016


A.1 Analysing the appropriate material 7 4/4/2016

A.2 Cost analysis(online & vendors) 7 4/11/2016

B Desiging, analysis and various 5/2/2016

system selection.

B.1 Frame (cad model)

B.2 Breaking system

B.3 Suspension

B.4 Steering And Wheel alingment

B.5 Electrical system

B.6 Ergonomics
B.7 Analysis

E Ordering And Procurment


of parts

D Frame Production

D.1 Dimensioning and cutting of steel

D.2 Weilding

D.3 Joints

D.4 Casting of nuckle

E Electrical Work

E Assembly

F Vehicle Testing
Team ID 16060
Team Name Samarthya 2.0

April Ma
End Date Responsible W14 W15 W16 W17 W18
4 11 18 25 2
4/18/2016 Faisal khan
4/11/2016 Ankit pawar
Gagandeep singh
4/18/2016 Prajwal Thakre
Amit singh

6/13/2016 Faisal khan


Gagandeep singh

Faisal Khan
Gagandeep singh
Amit Singh

Kalyan singh
Ankit pawar
Vinith Korra

Kalyan Singh
Rahul Sarma

Gagandeep Singh
Rajan Lad
Prajwal Thakre

Ankit Pawar
Kalyan singh
Rahul Sarma

Faisal Khan
Ankit Pawar
Vinith Korra

Gagandeep
Kalyan Singh
Faisal Khan

Ankit Pawar
Rajan Lad

Faisal Khan
Ankit Pawar
Gagandeep

Kalyan Singh
Rajan Lad
Rahul Sarma

Faisal Khan
Vikas Verma
Prajwal Thakre

Gagandeep
Vinith Korra

Gagandeep

Kalyan Singh
Ankit pawar

Faisal khan
Ankit Pawar
Main Task/ Activity
Legends Sub Task/ Activity
Milestone
Text Milestone Details

May June Jul


W19 W20 W21 W22 W23 W24 W25 W26 W27
9 16 23 30 6 13 20 27 4
July August Septem
W28 W29 W30 W31 W32 W33 W34 W35 W36
11 18 25 1 8 15 22 29 5
September October
W37 W38 W39 W40 W41
12 19 26 3 10
Efficycle 2016
Project Plan
Duration
Task ID Task/Activity Description Start Date
(Days)

A Designing 30 4/5/2016
A.1 Hand Sketch Preparation 6 4/5/2016
A.2 CAD/Modeling 9 4/11/2016
A.3 CAE Analysis 5 4/13/2016
A.4 Optimization 15 4/20/2016

B Procurement 46 4/18/2016
B.1 Frame Material 14 4/18/2016
B.2 Motor & Controller Unit 37 4/27/2016
B.3 Tire, Rim etc 17 4/21/2016

C Fabrication 106 4/28/2016


C.1 Prototype 8 4/28/2016
C.2 Material Testing & Analysis 7 5/2/2016
C.3 Frame Building 21 5/9/2016
C.4 Seat Fabrication 6 5/16/2016
C.5 Assembly 38 7/5/2016
Team ID 16xxx
Team Name Insert Team Name

April Ma
End Date Responsible W14 W15 W16 W17 W18
4 11 18 25 2
5/4/2016 Deepak
Design Ready
4/10/2016 Nisha
4/19/2016 Prakhar
4/17/2016 Deepak
5/4/2016 Pooja

6/2/2016 Prakash
5/1/2016 Srikant
6/2/2016 Animesh
5/7/2016 Suraj

8/11/2016 Kumar
5/5/2016 Pooja
5/8/2016 Prakhar
5/29/2016 Srikant
5/21/2016 Nisha
8/11/2016 Kumar
Main Task/ Activity
Legends Sub Task/ Activity
Milestone
Text Milestone Details

May June Jul


W19 W20 W21 W22 W23 W24 W25 W26 W27
9 16 23 30 6 13 20 27 4

Design Ready
July August Septem
W28 W29 W30 W31 W32 W33 W34 W35 W36
11 18 25 1 8 15 22 29 5

Vehicle Complete
September October
W37 W38 W39 W40 W41
12 19 26 3 10
Project Plan Guidelines
1. Introduction
1.1 Project Planning is an important document for the effective planning and smooth execution of project.
Many professional applications are used in the industry for making project plans. But for the ease of
1.2
generic MS Excel format has been given.

With the help of this project plan, teams can break the entire project into different activities and make the
1.3 & monitoring perfect. This tool can also be used by the teams for the continuous monitoring of the activiti
of planned vs. actual execution as per their own requirements.

2. Project Plan Data


First of all, it is important to understand the items given in this project Plan Format:
2.1 Task/Activity:
Every work performed during the execution of project shall be counted as a task. In the project plan, te
those tasks which are significant for monitoring of the project.
2.2 Main Task/Activity:

A task which defines the major work areas of the entire project shall be considered as Main Task. E.g. D
Material & Parts Procurement, Testing, Documentation etc. These are denoted with Alphabets. Refer Ex

2.3 Sub Task/Activity:

The breakdown of major tasks into minor activities will give the sub activities. These are denoted by Alph
numeral. E.g. Under Designing following can be considered as sub-activity:- sketching, CAD Modelling,

2.4 Task ID:

An alphabet is asigned to a Main Task/Activity. The Sub task/activity is denoted by the alphabet of its m
by a number/numeral. This numeral shows the sequence to that sub task in the project plan sheet.

2.5 Start Date, End Date and Duration of Activity:


Every major and minor task shall be assigned a start date and an end date. The total number of days for th
mentioned.
2.6 Task Responsible:
Every task shall be assigned to some team member. The responsible for the Main Task shall take care o
assigned under that main task/activity, whereas the sub-activities can be assigned to different members, as
team.
2.7 Legends:
The activites shall be denoted with the following legends:-
Main Task/Activity shall be displayed with the Double Arrow Line (Colour-Blue, Type-Continuous Line,

Sub Task/Activity shall be denoted with the Double Arrow Line (Colour-Black, Type-Continuous Line, W

Milestones, if any, shall be shown with upward triangle (Colour-Orange, Outline-Black). The description
be given in the TEXTBOX provided adjacent to it in your project planning sheet.
Text

However, teams may use any other legends as per their choice for addition information. Use of call out
done for effective display of information.
2.8 Timeline:
The weekwise timeline has been shown along with the week numbers of Calendar Year 2016. Teams m
timeline starting from the week when team has started working for project.
The timeline, activities shown in the format and the example sheets are only representative for the under
Teams must enter their actual data.
3. Format
3.1 The same format must be used by the teams. No other formats shall be accepted.
3.2 Enter the team ID and the team Name at the boxes given at the top of the sheet.
Mention all the activities and sub-activities with maximum details and provide dates, duration, responsibl
3.3
insert the shapes representing your activities accordingly.
3.4 Assign a task ID to each main task and sub-task.

3.5 In case of any problem faced related to format, teams must immediately write to efficycle.technical@saen

4. Submission & Deadline


Project plan must be submitted in the MS Excel file format only. Any other fromat like word document
4.1 presentation files etc are not acceptable. Even if any teams has gained the knowledge of project planning
MS Project etc, then also for the uniformity purpose, they should submit their project plan in MS Excel fo

Deadline for the project plan submission is Friday 20-May-2016 till 05:00pm. No request for deadli
4.2
be entertained.

Team must send the project plan to efficycle.reports@icat.in only (also mentioned under rule 10.7
4.3
Rulebook). If the project plans are not received at this email ID, it will be considered as non-submis

Mail Subject Line and the File Name of Document should be given as Team ID_Team Name_Efficy
4.4
Plan.
4.5 Teams must strictly adhere to all the deadlines given above.
xecution of project.
s. But for the ease of the participants, a

activities and make the project execution


onitoring of the activities and comparison

In the project plan, teams must mention

d as Main Task. E.g. Design, Fabrication,


th Alphabets. Refer Example Sheet.

ese are denoted by Alphabet followed by a


hing, CAD Modelling, CAE etc.

by the alphabet of its major task followed


ect plan sheet.

al number of days for that activity shall be

n Task shall take care of all sub-activities


o different members, as found suitable by

Type-Continuous Line, Weight-3)

ype-Continuous Line, Weight-1.5)

Black). The description of milestone shall

mation. Use of call out boxes etc may be


ar Year 2016. Teams may use their actual

esentative for the understanding of teams.

es, duration, responsible person name and

ficycle.technical@saenis.org

mat like word document, PDF documents,


edge of project planning software such as
ect plan in MS Excel format only.

No request for deadline extension shall

ioned under rule 10.7 of Efficycle 2016


sidered as non-submission.

D_Team Name_Efficycle 2016 Project