Page History

...

1. Keep corporate introductions and similar to a minimum or skip, in the interest of time.  Get to the meat of things.
2. Present a technical challenge (and if the talk abstract already presents it, this too can be short, but you may prefer to focus on a particular aspect)
3. Then present solutions.  Do not be afraid to be opinionated here, since these sessions are for "several companies unique view on a subject".
4. We have a technical audience and this is not a "business track".  Some tips:
   
   1. Use the opportunity to describe different solution approaches (if you have experience trying them),
   2. include criteria for choosing one method over another
   3. ... and try to include hard technical data which is useful to guide a technically minded audience: Memory footprint, size, lines of code, performance benchmarks, and so on. 
   4. Finally, including negative experiences, mistakes, or reasons why an alternative did not work out, is also extremely useful for everyone.  While that requires courage, please remember that these sessions are about sharing of real-world experience!
5. RoE should when possible try to describe production experience.  If you have experience from putting your ideas into actual car production, make sure to show this.  If you don't, then of course you will rather present your opinion of how things should be done, and then it's rather your experience from evaluating ideas.
6. Finally your company is absolutely free to Finally your company can of course take this opportunity to mention a solution you may have in your portfolio - (i.e. a solution to the presented challenge -  but as , not other irrelevant products).  As you can see above , the presentation is not expected to be a plain "sales pitch".  It should ought to explain technical rationale for the offered product, and the rest of the presentation material should overall add to the shared body of technical knowledge.
7. While considering the above, you may interpret the topic quite freely. We are grouping together diverse aspects in this session and as you can see, the abstract for this session is a shared one.  But different speakers will have different things they feel are important to highlight and if you are presenting something on the boundary of the presnted topic, that's OK!  We selected your company for a reason.
8. If the shared abstract completely does not match your intentions at all, just let us know, but be aware there is some flexibility built in.
9. Finally, there might not be time for Q&A, but in many AMM setups we have a related workshop time in which we can follow up on what was presented.  That is where most audience/participant discussion is expected to happen.
   Let's use this guideline for speaker slot length:
   * =< 20 minutes –> no Q&A
   * more than 20 minutes -> optional Q&A, speaker decides (but stay within alotted time)

...