Mall of America MOA Request for Proposals The

Mall of America (MOA) Request for Proposals • The Mall of America in Minneapolis, MN has designated an area of mall space to construct an indoor mini-golf course. • Mall of America executives have placed a call for design concepts from the leading design firms across the United States. • Your design team will be one of several teams who will pitch a design concept to MOA execs. • The winning concept will receive the contract to design and build a state of the art mini-golf course in the MOA.

Learning Objectives • Be able to work in an environment that includes remote team members. • Be able to use the Engineering Design Cycle to develop a high quality proposal for a client. • Be able to use Inventor 2015 to create part files and working drawings supporting your proposal. • Be able to present your proposal

Design Statement: • Competing design teams will submit a concept design containing 5 mini-golf holes illustrating the team’s overall idea for a mini-golf theme that will attract mall patrons.

Constraints: • All holes within a group/zone must have a consistent theme. • The concept design cannot exceed 25’ x 20’. Create your hole on a 25’ by 20’ by 1’ base. You will work in pairs on each hole. Most will be working with a partner from Pendleton HS. • Holes can be elevated up to 5’, but appropriate safety precautions must be taken. • All components of the hole must be less than 5’ tall. • Pathways as needed to move from hole to hole must be a minimum of 36” wide. • Holes can have some moving or animated parts. (optional) • All holes will have a standard tee off pad and scoring podium (these parts will provided by the project manager). • All 3 D modeling should be done to FULL SCALE. Be mindful of scale and units!

Team Role: Design Engineer (DE): • Each design engineer pairs will provide: – Preliminary brainstorm sketches describing the layout of the 5 hole course/zone. This preliminary sketch should include: – the pattern of play – where the players will enter and exit each area • 3 D model assembly of a themed hole including: – moving or animated parts – tee-off pad and scoring podium (provided by the PM). – walking paths providing access to the hole (must be a minimum of 36” wide)

Team Role: Project Manager (PM): • The project manager is responsible for: – – – assigning teams of 2 (from different sites if possible) provide a team layout diagram, assigning teams space the design of a scoring podium the design of a tee off pad the design of 150 sq. foot equipment/retail office one final team layout as an assembly drawing showing: • each hole designed by the team • a pattern of play outlining where players will enter and exit each area – assigning a team member(s) to put together the final presentation

Suggestions for New Themes and Examples Sports • Logos and teams • Olympic Sports • Professional Sports • Sports equipment • Arenas and fields • Fans • Games and Toys • Board games (Monopoly, Candyland, etc. ) • Legos, Blocks or building sets • Card games • Video games (Super-Mario etc. ) • Checkers, chess • • • Holidays and Celebrations 4 th of July Halloween Thanksgiving St. Patrick’s Day New Year’s Eve Birthdays Christmas Hannukah

Selling Your Proposal • Upon completion of your proposal your team will present it to the class. • The class will vote on which proposal to send on to Mall of America.

• • • Team members/Schools (Monday-Wednesday 5/24) Project Name (Wednesday 5/24) Team Norm Summary (Wednesday 5/24) – – • • – Look at extensions, and enhancements that go beyond the minimum requirements – – Create a CAD model and complete set of working drawings for your solutions Put Screen Captures into the Power. Point Assembly (6/5) Showing how all of the parts fit together and interchangeability of enhancements as appropriate Screen Capture of Assembly included in the Power. Point Create a Team Power. Point Presentation and tri-fold brochure (optional) marketing your solution (Monday 6/7) – • Use a decision matrix to evaluate the design proposals based on your Specifications and Constraints Include Decision Matrix in Power. Point Delegate who will be doing what Start Creating Part files in Inventor Construct and Test a Prototype (5/31 - 6/5) – – • At least three sketches/member on Isometric Paper for proposals Take pictures of your proposals in include in Power. Point and share with partners Develop a Solution (5/26) – – • Use the design brief to generate Constraints and Specifications Constraints: What it can’t do/be (Team picks top 4 -5) Specifications: What it can do/be (Team picks top 4 -5) Generate Concepts (5/24 – 5/26) – – • Interaction: File/Folder Naming Standards Define the problem (Wednesday 5/24) – – – • 5 th Period Schedule Prepare your presentation to the Shark Tank Class Presentations (6/9)

What will be turned in by the team • Create a Trifold Brochure • Team Power. Point Presentation marketing your solution • Team Presentation (This will be the final for Seniors)

How can you work in teams? • Developing team norms.

Developing Team Norms “The way our team will do things. ”

Learning Objectives • To understand be able to develop team norms for… • Interaction with teammates • File structure and organization • Communication how and when • Today you will create proposals to share with the rest of your team.

Team Norms • Team norms are a set of rules or guidelines that a team establishes to shape the interaction of team members with each other and with employees who are external to the team. • What is a worst case scenario if team norms are not established?

Stagnant Pond or Flowing River • Ken Blanchard, of One Minute Manager fame, said that a river without banks is a pond. Likewise, a team without relationship norms leaves itself open to potential interpersonal problems On the next slide are the potential teams. There could be some shifting when we get the final numbers from North.

The Teams 1) Introductions 2) Left Person = Scribe (Enter norms) 3) Right Person = Project Manager (Lead discussion) 4) Open Team Norms Template 5) Discuss Team Norms as a Class then 6) Develop a team norm proposal for your group

Create Code of Conduct team norms for your group. • Code of Conduct Examples: • Listen to what others are saying • Strive to understand each other's perspectives, rather than jumping to conclusions • Try to resolve problems without blaming • Send an acknowledgement in response to important email messages • Respect "do not disturb" signs on people's cubicles • When you've made a commitment you can't keep, let the other party know as soon as possible • If you don't understand something, ask for clarification • If you see a problem that others haven't noticed, bring it to someone's attention • Treat clients' issues and concerns as valid even if you don't agree with them • If you think team members have a conflicting understanding of a project issue, bring it to their attention • Focus on the positive: what's working well, not on what's going wrong

Team Norms: Communication • With your team come up with suggestions for… • How often to communicate with your virtual team. • Each team will have a shared folder in Google Drive for this project. • What method you will propose using for communicating. (email, shared drive, …) • How will you handle if a team member is not contributing. • As a team, create a proposal for your Communication Team Norm

Team Norms: Organizing Files • • • File names Folders Revisions …. Why would setting standards for these be important?

File Name Recommendations The important take-away points from this article are: 1. The file-naming convention that your business uses needs to be understood by everyone in the organization. 2. File-naming conventions should help people find information quickly by scanning names or by looking for dates or other signifiers in the name. 3. Files that are "naturally-ordered" are easier to scan and sort. 4. Be consistent with naming conventions (Jill Duffy PC Mag)

Team Norms: Organizing Files • FIRST, A NOTE ON NAMING… • As different software uses different processes for naming and organizing, it’s best to avoid using things like special characters, symbols, and spaces in your naming. • Things to avoid include stuff like: !, @, #, $, %, &, *, (, ), /, ” and ? Here a couple of examples of good and not so good names to use: BAD: 2013 Jill+Brian GOOD: 2013_Jill. Brian • BAD: Jill Brian Highlights GOOD: Jill. Brian. Highlights • BAD: Jills & Brian’s First Class GOOD: Jill. Brian. First. Class

Things to consider including in your file structure • A file name that establishes… – – Who created the file Description of the part Date created Which modification Develop a proposal for file naming structure • Consider a folder structure that will also help organizing information. • Types of files you will be working with: Part files, Drawing files, Individual and Group Powerpoints, Brochure, … • How will/can you use folders to keep your project organized?

Process for Making Decisions • Decision matrix for evaluating proposals based on specifications and constraints • How will your team come to a final decision? Complete the Process for making design decisions section

Conflict Resolution • What norms will you establish for engaging in healthy conflict? • That is, what can you all agree are acceptable or unacceptable behaviors when you’d like to – a) disagree with another person’s views or – b) have issues with another team member’s contribution to the team. • As a team, watch the video ‘Finding a Strategy for Conflict Resolution’ from the class website and come up with team norms for conflict resolution.

Virtual Design Teams Team West North A 1 Nathan Faust (Project Manager) Fidel Delgado (Project Manager) A 1 Jarvis Buczynski Joseph James A 1 Logan Johnson Aaliyah Tucker A 1 Liam Todd Adrian Sierra A 1 Conner Shattuck Bennie Munroe A 2 Alejandra Barajas-Navarro (Project Manager) Yesenia Ramos(Project Manager) A 2 Nathaniel Dela Cruz Nathan Snyder A 2 Matthew Brock Keril Obyedkov A 2 Jorge Marquez Jorge Gandara A 2 Linus Fairbrother Anthony Ramos Travis Burger (Project Manager) A 3 Beau Randall Nathan Compton A 3 Noah Davis Yoselin Barocio A 3 Ethan Weathers Joey Bartsch A 3 Bryce Comer Oscar Hernandez Shauna Swindle (Project Manager) A 4 David Quintana Chanti Manon. Ferguson A 4 Nicholas Fielder Lucas Fromherz A 4 Noah Gonzalas Austin Shackelford A 4 Calvin Pugmire Elijah Nguyen Prom

• To do Today On a piece of paper give Smith your school email address and team (A 1, …) – I will share a folder with you for you to copy your team norm proposal • Finalize your Team Norm Proposal – Placed you final proposal into your shared folder so the North Salem Students can see it and add/modify as needed. • Open your team folder and add your contact information • Define the problem your team will be solving. – As a team, read over the requirements and use this information and what your team would like to consider for a successful design to determine specifications and constraints – Start Developing Specifications/Constraints for your design proposals. (2+ per Person) – Specifications (Things the product can do) – Constraints (Limits, things you can’t do) – Project Manager: Insert columns as needed. Replace sample names with names from your team. • Start Developing Concepts for the entire course – Team Brainstorm different themes. – Each person put together a different proposal for the entire course that includes pathways through the course. – Isometric Graph Paper ( 1 proposal per Student) – On Friday you will be sharing your proposals with the team and use the decision matrix to help determine which design direction to take.

Friday • Communication – Email partners from North – Establish a communication protocol as aligned with the team norms established earlier. • • • Share your design proposals Add information, your name and proposal names, to the decision matrix Start evaluating the proposals that have been shared Check to see if your partners understand how to use the decision matrix. Finalize who will be working together on each hole Each team determine which elements you will be adding. – Green – Trees – Obstacles • Start working on Inventor Files

• • • Team members/Schools (Monday-Wednesday 5/24) Project Name (Wednesday 5/24) Team Norm Summary (Wednesday 5/24) – – • • – Look at extensions, and enhancements that go beyond the minimum requirements – – Create a CAD model and complete set of working drawings for your solutions Put Screen Captures into the Power. Point Assembly (6/5) Showing how all of the parts fit together and interchangeability of enhancements as appropriate Screen Capture of Assembly included in the Power. Point Create a Team Power. Point Presentation and tri-fold brochure (optional) marketing your solution (Monday 6/7) – • Use a decision matrix to evaluate the design proposals based on your Specifications and Constraints Include Decision Matrix in Power. Point Delegate who will be doing which hole. Developing features, elements, … Start Creating Part files in Inventor Construct and Test a Prototype (5/31 - 6/5) – – • One proposal from each team member. Take pictures of your proposals in include in Power. Point and share with partners Develop a Solution (5/26) – – • Use the design brief to generate Constraints and Specifications Constraints: What it can’t do/be (Team picks top 4 -5) Specifications: What it can do/be (Team picks top 4 -5) Generate Concepts (5/24 – 5/26) – – • Interaction: File/Folder Naming Standards Define the problem (Wednesday 5/24) – – – • 5 th Period Schedule Prepare your presentation to the Shark Tank Class Presentations (6/9)