～プレゼンテーションイベントについて～ · 2018-03-02 · ＝ BUSINESS LOGIC CASE ... Be sure to read and understand the 2014 FSAE Rules for the Presentation Event

～プレゼンテーションイベントについて～

プレゼンテーション審査統括リーダー

馬場雅之（株）本田技術研究所

ブレゼンテーション審査サブリーダー

宮崎知之ＮＳＫワーナー（株）

2016/10/29 静的審査勉強会＠上智大学 1/63

目次

１．大会設立の趣旨

２．車両開発の現場と学生フォーミュラ大会の比較

３．プレゼンテーションとは？

４．資料作成のポイント

５．発表のポイント

６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

2/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

3/63

1. 大会設立の趣旨

自動車産業の競争力低下人材不足

ものづくりの機会不足

創造性に満ちた技術者育成

背景

実際の車両開発に即した内容を体験

少子化による学生の減少若者の理科離れ

工学系大学における実習・設計・製図のカリキュラム減少

全日本学生フォーミュラ大会開催

4/63

1. 大会設立の趣旨

学生自動車関連企業に就職希望

企業即戦力となる人材が

欲しい

学生フォーミュラ大会

スポンサー

スポンサースタッフ派遣

技術習得

参加就職

・ビジネスモデル(企画)が描ける・設計ができる・原価計算ができる・車を製作できる・運転評価ができる

Win Win

5/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

6/63

2. 車両開発の現場と学生フォーミュラ大会の比較

商品企画：コンセプト、市場、ユーザー、販売価格を決定

↓ 試作：設計、原価集計、製作

↓ 評価：性能試験、信頼性試験

↓ 量産移行審査：性能、販売計画、利益等、承認を得る

↓ 生産販売

＝ BUSINESS LOGIC CASE

＝デザイン審査・コスト審査

＝車検・動的審査

＝プレゼンテーション審査

実際の車両開発に即した内容 7/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

8/63

3. プレゼンテーションとは？

1) プレゼンテーションの誤解

「説明すること」である「紹介すること」である

「プレゼンテーション」とは

「あなたは、何がしたいの？」「我々は、何をしたらいいの？」

？？？

説明や紹介だけでは不十分

9/63

3. プレゼンテーションとは？

2) プレゼンテーションの定義

プレゼンターが聞き手を説得し、聞き手がプレゼンターの考えに同意し、決断して実行に移すように仕向けること

プレゼンテーション＝依頼行為 ※ビジネスの世界では当たり前

「〇〇して欲しい、〇〇してください」が必要

10/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

11/63

統一感のあるデザイン・背景・ロゴマークの位置・タイトル，サブタイトルの位置

補足資料

総括

本文

章扉

目次

前書き

4. 資料作成のポイント

1) 資料の基本構成

表紙プレゼンテーションの目的を提示

全体の概要と流れを提示

目的に対する背景・根拠・手段等の詳細説明

目的の再提示意思決定のお願い

目的と流れを分り易く

構成する

質疑応答用

12/63


2) 本文レイアウト

人の視線に合わせた配置を心掛ける

(1) 本文頁の基本レイアウト

タイトル

サブタイトル

頁番号

本文

○ 見やすい配置

× 見にくい配置

(2) 配置

サブタイトルで本文を簡潔に

紹介する（1枚完結が理想）

13/63


3) 配色

色の基本を良く知って、見やすい配色を心掛ける

見やすい配色

見やすい配色

見やすい配色

見えにくい配色



見やすい配色

見やすい配色

見やすい配色


見て疲れる配色




部屋の明るさも配慮したい

14/63


4) 図解手法

素早く理解してもらうためビジュアル化を心掛ける

論理図解構造・構成・関係

絵図解イメージ・写真

データ図解表・グラフ

部品名メーカ

タイヤ GoodYear

ホィール VOLK

ブレーキ brembo

情報の構造化情報のビジュアル化数値の可視化

文章＜箇条書き＜図解

理解スピード

アニメーションや動画も効果的

15/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

16/63

5. 発表のポイント

1) 発表準備

準備万端で望むこと【想定外は無いように】

発表原稿の作成

リハーサル

スライド下部のノートペインを利用話す速度の目安・・300～400字/分

発表時間の確認タイムシート作成原稿・資料の確認、修正

time

0’00 スライド頁発表原稿

1

0’05 2

5’05

20 8’50

9’40 finish

想定Q&A作成想定質問集作成 ⇒回答用補足資料の準備

役割分担発表メンバーの役割を決める発表者、パソコン操作、タイムキーパー

機材の準備プロジェクタ操作方法・動作確認パソコン、データ予備

Step1

Step2

１分/１枚

Step3

Step4

Step5

タイムシート例

17/63


2) プレゼンテーションの実践

機器の設置

自己紹介目的と概要の説明

発表メンバー全員を紹介する

目的の再確認意思決定のお願い

回答は結論から、簡潔に

プロジェクタ調整「向き・ピント」は入念に実施

スライド一覧表示で質問し易く

慌てない、焦らないこと

設営

導入

本論

まとめ

質疑応答

18/63


3) プレゼンターの立振る舞い

プレゼンターの立振る舞いで、台無しになることもある

服装

姿勢・態度

話し方

表情

派手すぎず、清潔感のあるもので

身振り、手振りを交えて・・・ゆったりと

熱意を感じる、明るく大きな声で、間の取り方も考えて

笑顔と真剣さを両立させる

アイコンタクト

チームワーク発表者一人に任せない

プレゼンター≠ナレーター ≠キャスター

聞き手の表情、態度を感じ取るように

19/63

評価項目

20/63

APPENDIX S – 6 PRESENTATION JUDGING

The Presentation by the team should reflect back to the team’s Business Logic Plan Submission. While conditions may

have changed since the initial project commencement, these can be covered in the team’s Presentation, with changes in

business or technical factors being recognized and the team demonstrating well considered consequential actions.

Scores should be assigned in five categories on the basis of 0-10 points each according to the following scale (any

number or fraction along this scale may be used).

0.0 = inadequate or no attempt 2.5 = attempted but below expectation

5 = average or expected

7.5 = above average but still lacking

10 = excellent, perfectly meets intent

CONTENT: Was there recognition of the original BLP targets and rationale? Were the concepts presented appropriate

and adequate to explain how the car meets the wants of the customer? Were enough technical details

presented without being boring? ORGANIZATION: Were the concepts presented in a logical order progressing from the initial BLP concept? Does it

show how the engineering addresses the business and functional targets in order to deliver the concept?

Was it clear to the audience what was to be presented and what was coming next? Were distinct

introduction and overviews as well as summary and conclusions given? VISUAL AIDS: Were visual aids used or clear visual references made to the car? Were the illustrations visible for all of

the audience? DELIVERY: Did the presenter speak in a clear voice? Did the presenter show enthusiasm and promote confidence in

the technical aspects? Did the presenter maintain eye contact? QUESTIONS: Did the answers illustrate that the team fully understood the questions? Is there doubt that the team

understood the answer? Did the team create a feeling of complete confidence in their response to the

questions? Did the team readily accept the validity of the judges’’ question? Did they appear to be prepared

for questions? TOTAL = PRESENTATION POINTS (50 points maximum)

評価項目

評価項目評価内容

CONTENT

「内容」

• 車が顧客の要求を満たす事、又はその方法を十分に説明しているか？

• BLCの内容を認識しているか？

• 技術的な内容を説明しているか？

ORGANIZATION

「構成」

• BLCのコンセプトが論理的な順序で説明されているか？

• そのページで何を伝え、次に何が来るのかが明確か？

• 導入・概要～内容～要約・結論の流れができているか？

VISUAL AIDS

「ビジュアル資料」 • 審査員全員が見えるか？

• 見やすいか？

DELIVERY

「発表」

• 聞き取りやすいか？

• 話し方、身振り、手振り、アイコンタクト、ポインターの使い方

• プレゼンターの熱意や自信はあるか？

QUESTIONS

「質疑応答」

• 審査員の質問を理解しているか？

• 自信を持って回答できたか？

• 質問に対して事前準備をしているか？

21/63

参考 2014_fsaem_suggestions

Do:

1. Be sure to read and understand the 2014 FSAE Rules for the Presentation Event. (This sounds simplistic,

but some past presentations strongly suggest that teams either didn't read or understand them).

2. Check out your group’s equipment for proper operation prior to arriving at the competition. Perform a

trial run of your presentation using the equipment you plan to use at the event.

3. Be on time.

4. Introduce yourself and your co-presenters to the judges.

5. Your business case needs to cover all appropriate areas. See the Formula SAE rules for clarification.

6. Sell your FINAL product, not the specific prototype (if you’re confused about what the difference is,

reread the intent of the Formula SAE competition: it’s listed in the rules).

7. Speak to the content on the slide(s).

8. Maintain eye contact with your audience.

9. Include an outline of the presentation and pictures of the product.

10. Remember; the judges are acting as officers of a company and they are trying to decide if they want to

invest its capital in your product. Don’t forget about their ROI.

11. Be confident. Rehearse. Then rehearse again. And again. And again.

12. Use backup slides (if necessary) to address potential questions.

やるべき事

22/63

参考 2014_fsaem_suggestions

Don't:

1. Don’t spend most of the time on one specific topic – this is not a design presentation, nor is it a

finance presentation, nor is it a marketing presentation. It is all of these (and more).

2. Don’t talk too quickly. If you feel that you need to; rethink how you’ll present the information in order

to allow yourself to speak at a nominal pace.

3. Don’t fill each slide with tons of data. Remember; a picture is worth a thousand words. Choose your

pictures wisely.

4. Don’t read each slide from top to bottom. Your primary focus is your audience.

5. If have more than one presenter, don't bounce back-and-forth between them with every other line.

Choose a transition point(s) that make sense.

6. Don’t be apologetic during questions from the judges. Speak with confidence.

7. Don’t be afraid to deflect questions to other team members if you are the primary spokesperson. You

are not expected to know all the answers.

8. Don’t forget that any person who will be speaking must be identified per the FSAE rules.

9. Don’t exceed the 10 minute time limit; you will be cut off. Don’t make the presentation too short,

either. Your goal should be to make the most of the 10 minutes that you have to present.

やってはいけない事

23/63

目次






６．ルール解説 (2016) (2017-18)

７．まとめ

８．質疑応答

24/63

6. ルール解説 (2016)

1)大会関連ルール一覧 (1) 2016 Formula SAE®Rules (2) 2016 FSAE®BUSINESS LOGIC CASE (3) 第14回全日本学生フォーミュラ大会 ①大会規則 ②日本大会ローカル規則 (4) チームハンドブック

最新のルールを確認することが重要 ※加筆訂正部は、確認しやすいが、削除部は、内容を確認しないと判らない

25/63

3. ルール解説 (2016) http://www.jsae.or.jp/formula/jp2/about/rules.html 最新ルールの入手

26/63

3. ルール解説 (2017-18)

www.fsaeonline.com ⇒ Rules 最新ルールの入手

27/63

http://www.fsaeonline.com/

■ プレゼンテーションに関わるルール (1) 2016 Formula SAE®Rules

A1.2 Vehicle Design Objectives S3 BUSINESS LOGIC CASE S5 PRESENTATION EVENT APPENDIX S-6 PRESENTATION JUDGNIG

(2) 2016 FSAE®BUSINESS LOGIC CASE

(3) 第14回全日本学生フォーミュラ大会 ①大会規則 ②日本大会ローカル規則第3号J2016-28,39,40,41

6. ルール解説 (2016)

28/63

A1.2 Vehicle Design Objectives

For the purpose of the Formula SAE competition, teams are to assume that they work for a design

firm that is designing, fabricating, testing and demonstrating a prototype vehicle for the non-

professional, weekend, competition market.

A1.2.1 The vehicle should have very high performance in terms of acceleration, braking and handling and

be sufficiently durable to successfully complete all the events described in the Formula SAE Rules

and held at the Formula SAE competitions.

A1.2.2 The vehicle must accommodate drivers whose stature ranges from 5th percentile female to 95th

percentile male and must satisfy the requirements of the Formula SAE Rules.

A1.2.3 Additional design factors to be considered include: aesthetics, cost, ergonomics, maintainability,

manufacturability, and reliability.

A1.2.4 Once the vehicle has been completed and tested, your design firm will attempt to “sell” the design

to a “corporation” that is considering the production of a competition vehicle. The challenge to the

design team is to develop a prototype car that best meets the FSAE vehicle design goals and which

can be profitably marketed.

A1.2.5 Each design will be judged and evaluated against other competing designs to determine the best

overall car.

チームはアマチュアの週末レース市場のための試作車両を設計、製作、テストおよびデモンストレーションをおこなう設計会社で働いていることが前提

一度車両が完成し、テストされると、チームの設計会社は競技車の生産を考えている企業にその設計の売り込みを試みる。設計会社の挑戦はFSAE車両設計の目標にベストマッチし、収益性のある売込みが可能な車両を開発することである。

6. ルール解説 (2016)

29/63

試作車：高性能な車両設計要件：見栄、コスト等

売込み可能なプロト車開発

市場=SCCA soloを含む

顧客=アマチュア週末レーサー

チーム=設計会社競技車両製造を考えている会社

プレゼン

販売

プレゼンテーションイベントに係わる前提条件 A1.2 解説

Will attempt to “sell” the design to a “corporation”

6. ルール解説 (2016)

30/63





6. ルール解説 (2016)

31/63

6. ルール解説 (2016) ARTICLE 3: BUSINESS LOGIC CASE S3.1 The Objectives of the Business Logic Case are to: a. Teach participants about the factors that need to be considered when a company embarks on development of a new product. These include: cost; identification of market and likely sales volume; profitability; the key features applicable to the selected vehicle concept and target market size. b. Ensure teams develop the concept of their entry with all of these aspects correctly considered, from the outset. c. Ensure that all three static events are approached with a single common concept and presented to each set of static judges in the same manner. d. Ensure that participants gain experience in producing a business case and balancing potentially conflicting attributes. S3.2 The Design, Cost and Business Presentation judges will use the business logic case to verify that the information presented at each static event is consistent with the overall objectives as outlined in the Static Events Rules. a. In the Design event, the business logic case will be used to identify how the team determined the trade-off between design for performance and design for manufacture and cost, how these requirements were considered in the overall concept and whether these were achieved in the final vehicle. b. In the Cost event, the business logic case will be used to determine that the cost target was met for the same design solution and how Cost was integrated into the overall concept and the iterative design process. c. In the Business Presentation event, the business logic case will be used to assess whether the business presentation is appropriate for the market and business strategy that the team has identified d. For some Formula Student/FSAE Events, if the event is oversubscribed, then the entry selection process may include assessment of the quality of the Business Logic Case supplied.

プレゼン審査

デザイン審査コスト審査

日本大会ではBLCはプレゼンテーション審査においてのみ使われる

32/63

6. ルール解説 (2016) S3.3 All teams must submit a Business Logic Case report in accordance with the general format

applicable for the year of competition “FSAE Business Logic Case 201X”. The report must be

submitted on the template. Refer to the applicable competition website to acquire the template.

This report must be submitted by the deadline which will generally be ~ 6-9 months before the

competition. Refer to the deadlines posted on the website for each specific competition.

2016日本大会 7月5日14:00

提出期限

33/63





6. ルール解説 (2016)

34/63


6. ルール解説 (2016)

www.fsaeonline.com COMPETE/Download Forms

35/63


6. ルール解説 (2016)

Integrated Systems Design Commencing with the 2013 year Formula SAE Competition, a new integrated business/design concept summary is to be submitted by all teams, 6-9 months ahead of the competition. This summary (entitled The FSAE Business Logic Case) should not be an onerous task and will assist teams to follow an integrated systems approach. In order to give students the maximum benefit, it is intended that this task is completed before the design process is engaged with the objective to define an integrated overall vehicle concept with consideration of but not limited to: vehicle performance, cost and target market. It will assist students understanding of, and correlation with, the real world approach to vehicle design, whereby a Total Systems Overview and Vehicle Level Targets are developed (Cost; Price; Profit; Volume; Performance), and a sanity check completed, before any detail design is undertaken. This approach can help avoid conflicts later in the design process between systems and ensure realistic targets for your total vehicle are set which can then be deployed into the function and cost targets for each of the vehicle Systems and Sub-Systems. Why Make this Change? At various events worldwide a rise has been observed in the number of entrants that appear to have lost their way with regards to cost, value and the logic of design for manufacture and profit. These aspects are critical in the real world you will encounter within the global automotive OE and Supplier industry. The intent of this additional submission is to help you to guide yourselves to produce a better vehicle and advance your education in line with future reality. Seldom is the biggest budget or most expensive and technologically advanced vehicle the best solution. Getting the balance right is the key. Thinking at the higher (overall vehicle) level before plunging into the detail (the front suspension or monocoque body) will help you produce the best result within the resources available to your team. The aim of the event series is to improve a student’s knowledge in a manner that will be real world useful, as soon as possible, and thus provide a shortcut of “experience” to the benefit of the student, their educational establishment and also their first employer. Uniquely, everyone wins here.


36/63

6. ルール解説 (2016) Remember that this is not a motorsports competition but the development of expertise and understanding of what is necessary to design, build and develop an actual vehicle that can be compared to others but which recognises the importance of cost and understanding of design and function, inside a reasonable business case. The small open wheeler with specification limits is chosen as it provides a vehicle type which can realistically be designed and built within the available time, and its actual performance then demonstrated vis a vis design intent. This document will not be formally marked and no specific points will be allocated but it will be used to aid the Design, Cost and Business Presentation process and help teams to represent themselves consistently across the 3 static events The Integrated Plan The general rules which apply to this submission are summarised on Page 2. The general steps vehicle project teams would follow in developing their Business Case and related initial vehicle concept and features (in Business as well as for this event) are outlined on Page 3 along with the instructions for filling in the 1 page submission (Page 4). The organisers appreciate that things may change; it is not intended to limit or restrict the benefits of “learning by doing” but rather to ensure that changes which arise are recognised and related back to the overall objectives. This will assist explanations to Judges at the event in a logical (and desirably documented) manner and avoid being surprised by obvious questions on the rationale for various design or feature selections.


37/63

(2015 Formula SAE® Rules S3と同内容)

6. ルール解説 (2016)

Rules Business Logic Case The Objectives of the Business Logic Case are to:

Teach participants about the factors that need to be considered when a company embarks on development of a new product. These include: cost; identification of market and likely sales volume; profitability; the key features applicable to the selected vehicle concept and target market size. Ensure teams develop the concept of their entry with all of these aspects correctly considered, from the outset. Ensure that all three static events are approached with a single common concept and presented to each set of static judges in the same manner. Ensure participants gaining experience in producing a business case and balancing potentially conflicting attributes.

The Design, Cost and Business Presentation judges will use the business logic case to verify that the information presented at each static event is consistent with the overall objectives as outlined in the Static Events Rules.

In the Design event, the business logic case will be used to identify how the team determined the trade off between design for performance and design for manufacture and cost, how these requirements were considered in the overall concept and whether these were achieved in the final vehicle. In the Cost event, the business logic case will be used to determine that the cost target was met for the same design solution and how Cost was integrated into the overall concept and the iterative design process. In the Business Presentation event, the business logic case will be used to assess whether the business presentation is appropriate for the market and business strategy that the team has identified For some Formula Student/FSAE Events, if the event is over subscribed, then the entry selection process may include assessment of the quality of the Business Logic Case supplied.

All teams must submit a Business Logic Case report in accordance with the general format applicable for the year of competition “FSAE Business Logic Case 201X”. The report must be submitted on the 1 page template. Refer to the applicable competition website to acquire the templates This report must be submitted ~ 6-9 months before the competition. Refer to the deadlines posted on the website for each specific competition.


38/63

6. ルール解説 (2016)

General Requirements

The steps in developing the case generally will consist of

- benchmarking (analysis of previous competition results, competitor vehicle specifications and costs etc.)

- short listing preferred concepts

- assessing your team (company) capability to deliver different concepts recognising the budget and team

that you have

- selecting your initial concept and developing targets to be achieved by the total vehicle (these will include

target overall cost; likely sales potential; major performance and handling targets; timing plan for

progressing the project;)

- deciding on how to break down the total vehicle cost into different areas of the vehicle, recognising the

performance targets you have set.

- commencing your design to deliver the design concept and related targets recognising that the ensuing

process will often be iterative and trade-offs will be necessary but if you have never defined the overall

concept and what you plan to achieve, you will not be able to control your program and measure your

progress

Instructions: Complete the information request fully but the submission is to be only a single A4 page. Please

replace all text which is highlighted with a yellow background.

You can re-allocate space between sections versus the indicated box sizes on the pro-forma.

This case outlines the team’s decisions made throughout the overall design process and will be used in all static

events at the competition.


39/63

コスト審査で与えられる企画台数とは異なる

6. ルール解説 (2016)

Market Data

Table 1 below defines the maximum number of autocross vehicles that can be sold annually for a given price, but this can only be

achieved if the vehicle has sufficiently high performance. 1,000 units per annum is the maximum volume available.

Your selection of Price and Volume must correlate to this table. (Interpolate as necessary). Obviously your target Vehicle Cost must

also relate to your planned Price.

Table 1 – Volume of sales vs. sale price

Vehicle Sale Price vs Volume

0.0

10.0

20.0

30.0

40.0

50.0

60.0

0 50 100 150 200 250 300

Volume of Manufacture

Sa

le P

ric

e, 1

00

0$

Volume of

cars sold

per year

Sale Price,

$

20 50000

35 42000

50 36000

75 30000

100 26500

125 24000

150 22000

250 17900

500 14600

750 13400

1000 12600

年間生産台数と販売価格


40/63

定型書式：2016日本大会では専用フォーマット有

市場分析

会社の戦略

車両の戦略と性能

6. ルール解説 (2016)

41/63

本シート＝プレゼンテーションの骨子

性能・コスト・製造を満足させる工夫/計画

6. ルール解説 (2016)

42/63

２．プレゼンテーションに関わるルール (1) 2016 Formula SAE®Rules




6. ルール解説 (2016)

43/63

2 - (3) 第14回全日本学生フォーミュラ大会- ①大会規則

6. ルール解説 (2016)

44/63

2 - (3) 第14回全日本学生フォーミュラ大会- ①大会規則第12条書類選考

チームから提出された「デザインレポート」、「デザインスペックシート」、「コストレポート」、

「ビジネスロジックケース」を審査し、書類選考を実施する。

書類選考結果は、7月29日(金)に発表する。

1）書類選考通過チーム

（1）大会当日の静的審査に出場できる。

（2）書類選考結果発表にてデザイン審査、コスト審査、プレゼンテーション審査のいずれかの審査項

目が当日審査対象外となった場合、その審査項目（デザイン審査、コスト審査、プレゼンテーション

審査）についての当日審査は実施しない。なお、コスト当日審査対象外となったチームは、コスト審

査のフォローアッププログラムに参加できる。

2）書類選考不通過チーム、書類未提出チーム

（1）本大会には出場できないが、本大会開催期間中に行われるフォローアッププログラムに

参加できる。

（2）フォローアッププログラムの内容(予定)

①模擬車検

②デザイン審査

③コスト審査（当日審査対象外チームのみ参加可）

④プレゼンテーション審査（詳細は別途発表）

⑤EV製作・車検相談

6. ルール解説 (2016)

45/63

２．プレゼンテーションに関わるルール (1) 2016 Formula SAE®Rules




6. ルール解説 (2016)

46/63

2 - (3)第14回全日本学生フォーミュラ大会-

②日本大会ローカル規則第3号J2016-28,39,40,41

J2016-39 ビジネスロジックケースの書類選考

（関連規則2016大会規則第11,12条、2016FSAE® S-5.1.5、S-5.2.2、S-5.6.3）

提出期限内に提出した場合でも、事前審査の結果によっては、大会当日のプレゼンテーション審査が受けられない場

合がある。この場合、プレゼンテーション審査のポイントはマイナス75ポイントが与えられる。

なおチームの都合により大会当日のプレゼンテーション審査が受けられなかった場合も、プレゼンテーション審査のポ

イントはマイナス75ポイントが与えられる。

J2016-28 事前提出資料の書類選考（関連規則2016大会規則第11,12条）

デザイン審査、コスト審査、プレゼンテーション審査は、事前に提出された資料に基づき事前審査を行う。事前審査の

結果、大会当日のデザイン審査、コスト審査、プレゼンテーション審査の全てに出場できない場合は、書類選考不通

過となり大会参加資格を失う場合がある。

J2016-40 プレゼンテーション審査のための提出物（関連規則2016FSAE® S-3.3）

ビジネスロジックケースは、チームページからダウンロードできる日本大会用のフォーマットを用い、電子データで提出

すること。その他のフォーマットは受け付けない。

J2016-41 提出物の書式（関連規則2016大会規則第11条）

書式は本ローカル規則で定めるもの以外は2016FormulaSAE®Rulesに準拠し、各書式を変更してはならない。

6. ルール解説 (2016)

47/63





6. ルール解説 (2016)

48/63

(1) 2016 Formula SAE Rules S5 PRESENTATION EVENT S5.1 Presentation Event Objective – Business Case

S5.1.1 The objective of the presentation event is to evaluate the team’s ability to develop and deliver a

comprehensive business case that will convince the executives of a corporation that the team’s design

best meets the demands of the amateur, weekend competition market, including Sports Car Club of

America (SCCA) Solo, and that it can be profitably manufactured and marketed. (See also A1.2)

S5.1.2 The judges should be treated as if they were executives of a corporation.

S5.1.3 Teams should assume that the “executives” represent different areas of a corporate organization,

including engineering, production, marketing and finance, and thus may not all be engineers.

S5.1.4 Presentations will be evaluated on the contents, organization and visual aids as well as the presenters’

delivery and the team’s response to questions.

S5.1.5 The presentation must relate to the car entered into the competition and although the actual quality of

the prototype itself will not be considered as part of the presentation judging, the presentation must be

consistent with the Business Logic Case that is submitted prior to the competition.

6. ルール解説 (2016)

49/63

S5.1 Presentation Event Objective – Business Case

S5.1.1 The objective of the presentation event is to evaluate the team’s ability to develop and deliver a

comprehensive business case that will convince the executives of a corporation that the team’s design

best meets the demands of the amateur, weekend competition market, including Sports Car Club of

America (SCCA) Solo, and that it can be profitably manufactured and marketed. (See also A1.2)

S5.1.2 The judges should be treated as if they were executives of a corporation.

S5.1.3 Teams should assume that the “executives” represent different areas of a corporate organization,

including engineering, production, marketing and finance, and thus may not all be engineers.

S5.1.4 Presentations will be evaluated on the contents, organization and visual aids as well as the presenters’

delivery and the team’s response to questions.

S5.1.5 The presentation must relate specifically to the prototype vehicle as entered in the competition

S5.1.6 The presentation must be consistent with the Design and Cost events, and any documentation

submitted prior to the competition.

S5.1.7 The actual quality of the prototype itself will not be considered as part of the presentation judging

6. ルール解説 (2017-18)

(1) 2017-18 Formula SAE Rules S5 PRESENTATION EVENT

50/63

試作車：高性能な車両設計要件：見栄、コスト等

売込み可能なプロト車開発

市場=SCCA soloを含む

顧客=アマチュア週末レーサー

チーム=設計会社競技車両製造を考えている会社

プレゼン

販売

プレゼンテーションイベントの目的 S5.1 解説

チームの考えるビジネスケースを納得させ、明確な依頼をする

審査員=会社役員 Will attempt to “sell” the design to a “corporation”

6. ルール解説 (2016)

51/63

S5.2 Presentation Schedule

S5.2.1 Presentations will be made on the static events day. Presentation times will be scheduled by the

organizers and either, or both, posted in advance on the competition website or released during on-site

registration.

S5.2.2 Teams that fail to make their presentation during their assigned time period will receive zero (0)

points for the event.

S5.3 Presentation Format

S5.3.1 One or more team members will give the presentation to the judges.

S5.3.2 All team members who will give any part of the presentation, or who will respond to the judges’

questions, must be in the podium area when the presentation starts and must be introduced to the

judges. Team members who are part of this “presentation group” may answer the judge’s questions

even if they did not speak during the presentation itself.

S5.3.3 Presentations are limited to a maximum of ten (10) minutes. The judges will stop any presentation

exceeding ten minutes.

S5.3.4 The presentation itself will not be interrupted by questions. Immediately following the presentation

there will be a question and answer session of up to five (5) minutes.

S5.3.5 Only judges may ask questions. Only team members who are part of the “presentation group” may

answer the judges’ questions.

S5.4 Data Projection Equipment

S5.4.1 Projection equipment is not provided by the organizers.

S5.4.2 Teams planning to use data projectors, or any type of projectors, as part of their presentation are

responsible for bringing, or otherwise arranging for, their own projection equipment.

6. ルール解説 (2016)

52/63

S5.2 Presentation Schedule

S5.2.1 Presentations will be made on the static events day.

S5.2.2 Presentations may take place in conjunction with the Cost event. If this applies, additional details will

be published prior to the competition.

S5.2.3 Teams that fail to make their presentation during their assigned time period will receive zero (0)

points for the event.

S5.3 Presentation Format

S5.3.1 One or more team members will give the presentation to the judges.

S5.3.2 All team members who will give any part of the presentation, or who will respond to the judges’

questions, must be in the podium area when the presentation starts and must be introduced and

identified to the judges. Team members who are part of this “presentation group” may answer the judge’s

questions even if they did not speak during the presentation itself.

S5.3.3 Presentations are limited to a maximum of ten (10) minutes. The judges will stop any presentation

exceeding ten minutes.

S5.3.4 The presentation itself will not be interrupted by questions. Immediately following the presentation

there will be a question and answer session of up to five (5) minutes.

S5.3.5 Only judges may ask questions. Only team members who are part of the “presentation group” may

answer the judges’ questions.

S5.4 Data Projection Equipment

S5.4.1 Teams planning to use data projectors, visual display devices (tablets, computers, etc.), or other

communication means, as part of their presentation are responsible for bringing, or otherwise arranging for,

their own projection equipment.

6. ルール解説 (2017-18)

53/63

6. ルール解説 (2016) S5.5 Evaluation Criteria

S5.5.1 Presentations will be evaluated on content, organization, visual aids, delivery and the team’s response

to the judges’ questions. The scoring criteria are detailed in Appendix S-6 “Presentation Judging”.

S5.5.2 The criteria are applied only to the team’s presentation itself. The team that makes the best

presentation, regardless of the quality of their car, will win the event.

S5.6 Scoring Formula

S5.6.1 The Presentation Events score is based on the average of the judges’ scores.

S5.6.2 There is a maximum of fifty (50) points from the Presentation Judging Form.

PRESENTATION SCORE = 75 x Pyour/Pmax

Where:

“Pmax” is the highest score awarded to any team

“Pyour” is the score awarded to your team

S5.6.3 It is intended that the scores will range from near zero (0) to seventy-five (75) to provide good separation.

S5.6.4 The Presentation Event Captain may at his/her discretion; normalize the scores of different judging teams.

S5.7 Presentations without a Completed Car

Teams that unable to bring a vehicle to the competition may participate in the Presentation Event and

will receive a score for that event.

NOTE: Participating in the Presentation event without bringing a vehicle to the competition will not

affect the status of the car you have under construction at your school. When you finish it and bring it

to a competition it will still be a first year vehicle under Rules A6.6 and A6.8

54/63

6. ルール解説 (2017-18) S5.5 Evaluation Criteria

S5.5.1 Presentations will be evaluated on content, organization, visual aids, delivery and the team’s response

to the judges’ question.

S5.5.2 Presentation Judging Score Sheet – The Presentation Judging Score Sheet is available at http://fsaeonline.com.

S5.5.3 The criteria are applied only to the team’s presentation itself. The team that makes the best

presentation, regardless of the quality of their car, will win the event.

S5.6 Scoring Formula

S5.6.1 The Presentation Events score is based on the average of the judges’ scores.

S5.6.2 There is a maximum of fifty (50) points from the Presentation Judging Form.

PRESENTATION SCORE = 75 x Pyour/Pmax

Where:

“Pmax” is the highest score awarded to any team

“Pyour” is the score awarded to your team

S5.6.3 It is intended that the scores will range from near zero (0) to seventy-five (75) to provide good separation.

S5.6.4 The Presentation Event Captain may at his/her discretion; normalize the scores of different judging teams.

S5.7 Presentations without a Completed Car

Teams that unable to bring a vehicle to the competition may participate in the Presentation Event and

will receive a score for that event.

NOTE: Participating in the Presentation event without bringing a vehicle to the competition will not

affect the status of the car you have under construction at your school. When you finish it and bring it

to a competition it will still be a first year vehicle under Rules A6.6 and A6.8

55/63

S5.2 スケジュール S5.3 フォーマット S5.4 プロジェクタ装置 S5.5 評価基準 S5.6 スコアの計算式 S5.7 完成車のないプレゼンテーション

S5 解説-2

最低限守って欲しいルール

6. ルール解説 (2016)

56/63





6. ルール解説 (2016)

57/63

下記審査項目毎に採点【各10点満点】

「内容」

「構成」

「ビジュアル資料」

「発表」

「質疑応答」

コメント欄には、

良かった点

不足していた点を記載

APPENDIX S-6

6. ルール解説 (2016)

大会４日目希望チームに対し、審査フィードバックを予定

58/63

目次






６．ルール解説

７．まとめ

８．質疑応答

59/63

7. まとめ

プレゼンテーションイベントの基本：

1) ルールを理解する

2) ビジネスにおけるプレゼンテーションであることを理解する

3) 依頼事項を明確に伝える

4) 解りやすい資料を用意する

5) 熱意ある共感を得る話し方で納得させる

プロジェクトリーダー・チーフエンジニアになったつもりで

60/63

目次






６．ルール解説

７．まとめ

８．質疑応答

61/63

Documents

～プレゼンテーションイベントについて～ · 2018-03-02 · ＝ BUSINESS LOGIC CASE ... Be sure to read and understand the 2014 FSAE Rules for the Presentation Event