Ellery Wong Senior Systems Engineer, Xerox Corporation Co-Team Leader, Team 191 Xerox/Joseph C. Wilson Magnet HS X-Cats (Est. 1992 – Rochester, NY)

Slides:



Advertisements
Similar presentations
Beach Cities Robotics – Team 294 Andrew Keisic Dec 2008
Advertisements

I FORMATION OFFENSE. Philosophy If the other team does not have the ball, they cant score. If they cant score, they cant win. That is the fundamental.
Role of Senior Management
QFD From Chaos to Organization to Success! TEAM 3641 – The Flying Toasters Ron Weber Michigan State Championships April 2013 theflyingtoasters.org.
Developing mobile apps for businesses and brands.
Offensive/defensive evaluation: Define all functionalities of the game brainstorm early designs, evaluate feasibility, resource requirements Shooting (High.
PRESENTED BY USHA GHIMIRE. Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
AME Senior Design Group E3: Hewlett-Packers Concept Design Review April 24, 2008 Caitlin Feely Ben Nelessen JJ Rees Jamie Rowland Patrick Tennant.
W5HH Principle As applied to Software Projects
Stepan Potiyenko ISS Sr.SW Developer.
Robotic Football Group E1 CDR Team Top Gun April 22 nd, 2008.
FIRST Robot Design: a team- based process Andy Baker Mechanical Engineer, Delphi Corporation Co-Owner, AndyMark.biz Lead Engineer, team 45.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Fundamentals of Engineering for Honors - Team Project P. 1 Spring Quarter 2003 Engineering H193 Project Notebook & Brainstorming Sketches Week 1 Day 2.
Teaching materials to accompany:
PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
Fundamentals of Information Systems, Second Edition
FIRST Robotics A view from the Systems Engineering Perspective Chris Mikus January 2, 2006 Rev 0.2.
Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Week 1 Strategy and Brainstorming Paul Ventimiglia, Student at WPI.
Software Process and Product Metrics
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
Organizational Learning Approaches to Mergers & Acquisitions New Horizons Research Conference: George Washington University October 8-9, 2010 Jim Sanders,
Benchmarking at Saudi Aramco
Charting a course PROCESS.
Effective Methods for Software and Systems Integration
1. 2 Why is the Core important? To set high expectations –for all students –for educators To attend to the learning needs of students To break through.
Collaborative Problem Solving Bill Hommes. What am I going to tell you about? b b Creative Process we have used for the past 6 years to develop the concept.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Copyright 2002 Prentice-Hall, Inc. Lecture 5 Identifying and Selecting Systems Development Projects 5.1 COSC4406: Software Engineering.
Design Tips Navigational Aids for the Journey of Creation.
Week 5 – Special Topics. Risk Management Best Practices.
What is Marketing?  Marketing is about meeting the needs and wants of customers;  Marketing is a business-wide function – it is not something that operates.
Tournament Day!. Arriving Check in! – Find out inspection/judging times – Match schedule is released when all teams have arrived! Set up! – Pits, robot,
COMMUNITY AWARENESS / EMERGENCY RESPONSE BEST PRACTICE EXAMPLES AND TOOLS David Sandidge Director, Responsible Care American Chemistry Council May 31,
ECE 2799 “The Engineering Design Process” Prof. Bitar and Prof. Michalson Last Update – 3/18/15.
OVERALL ROBOT DESIGN, FTC STYLE PRESENTED BY: ANDY BAKER Sept
Value-based Empirical Study for IV&V ISERN2005 Masa Katahira, JAXA Daniel Port, Univ. of Hawaii.
System Development Life Cycle. The Cycle When creating software, hardware, or any kind of product you will go through several stages, we define these.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Applying “Engineering Processes” to solve problems Learning to apply project management systems Tools to manage time and resources Accessing information.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Team 8712 EPIC Season Building Your First Robot.
Survival 101: What to Expect at Your First Competition Thomas Gill, Team 6705 Motorbolts.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
IBM Service Oriented Modeling and Architecture TM (SOMA) Licensed Materials - Property of IBM © Copyright IBM Corporation All rights reserved. Introduction.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Developing a Winning Notebook. What is the Notebook? Notebook Specifications Notebook sections What is the Engineering Design Process? Notebook Evaluation.
Strategic Design FROM THE GAME TO CONCEPT DANNY BLAU ANDYMARK, INC 1.
Bridging the Gap FROM STRATEGIC ANALYSIS TO DETAILED DESIGN DANNY BLAU ANDYMARK, INC 1.
7 November 2006Program Management Basics Purdue FIRST Programs Slide 1 Program Management Basics Purdue FIRST Programs Chris Fultz Rolls-Royce Corporation.
Risk Mitigation Submitted By, S. Anitha Devi, M.E-CSE.
Systems Engineering Beach Cities Robotics – Team 294 Andrew Keisic Dec 2008.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1Spring Quarter Engineering H193 Project Notebook & Brainstorming Sketches Week.
CSE784 – Software Studio Jim Fawcett Fall 2002.
Scouting and Alliance Selection Ohio FTC Kickoff
Risk Management.
Developing a Winning Notebook
Architecture & System Performance
Architecture & System Performance
CSE784 – Software Studio Jim Fawcett Fall 2006.
System Development Life Cycle (SDLC)
Designing for a Strategy
Chapter 2 The Process of Design.
System Development Life Cycle (SDLC)
Chapter 12 EIN 6392, Product Design Fall 2009
Presentation transcript:

Ellery Wong Senior Systems Engineer, Xerox Corporation Co-Team Leader, Team 191 Xerox/Joseph C. Wilson Magnet HS X-Cats (Est – Rochester, NY)

Key Points Preseason -Get structured and understand roles ***Benchmark and learn from the past Understand game & brainstorm “Killer App” Requirements for maximum scoring strategies Strategy & Architecture team develops sub- team requirements Systems integration and testing

Team Organization

Preseason Teambuilding Walk through schedule and team roles Basic shop, CAD, and safety training Benchmarking Mechanical Systems –Lessons learned from prior seasons Develop team theme for the season 2006 Theme “Keep It Super Simple In Technology”

Benchmarking & Learning from the Past Re-use proven technology – it accelerates design cycle Lessons Learned are critical to avoid repeating mistakes during a busy build season

Brainstorming Understand Game play and goals (Entire Team) Break down all scoring elements to calculate maximum scoring strategy (Sub-Teams) Brainstorm “Killer App” characteristics –What is the attribute that would consistently win the game? –Don’t design just think of functional goals Game elements were ranked by scoring potential and level of design effort.

Requirements for Maximum Scoring Strategy Strategy & Architecture Team consolidates team strategies and performs risk assessment S&A ranks and chooses top 2 game strategies (Includes both offense and defense) Attempt to identify “Killer App” in game Requirements characteristics developed based by functions needed to be achieved by chosen game strategies Sub-Team Leaders buy-in to requirements and delivery schedule

Requirements Chart Functions Design RequirementsRampShootAcquireStoreBlockingCorner Score High Traction & ManeuverabilityX X 2 Speed - High Torque & SpeedX X Low C.G.X X X +/- 6 " accuracy X Farthest starting range X 90% Acquisition Rate X Min 10 Ball capacity X Open Visible Storage X Multiple Autonomous ModesXX XX Preferred Dumping Capability X X

Sub-Teams Receive requirements and develop functional prototypes to meet them On-going CAD integration of various design concepts Designs focus on K.I.S.S.I.T theme and “Lessons Learned” Working Prototype is integrated for S/W trial by end of 2 nd Saturday.

Testing & Refinement Drivers test functionality based on meeting requirements and strategy Once prototype is evaluated for critical parameters final build begins.

Hardware/Software Integration Final robot hardware is completed and evaluated towards inspection checklist Mechanical & electrical teams continue refinements Software team implements code to adjust to new system

System Test Stress testing of robot in simulated match environment Prepare for pre-ship event for initial competition testing with driver practice

Tips and Suggestions Use CAD and Math models effectively Benchmark and document past experiences to build up a team design diary Think hard outside of the box for the “Killer App” “Simplicity is the ultimate form of sophistication.”- Leonardo da Vinci