[davidfv]

My first post in this thread outlined my objectives and reasons for wanting to discuss systems engineering:
1. Develop an understanding of the systems engineering process
2. Construct a System Engineering Plan
3. Help teams succeed
Also in the first article I proposed five phases for the Robotics Lifecycle (season).
1. Formulation
2. Organization
3. Construction
4. Competition
5. Recognition.

This second article is a general discussion on what is systems engineering and what systems make up a team.

So proceed at your own discretion but please read my disclaimer:
These writings are just my thoughts and do not represent any official FIRST, any team or NASA opinions. You may not always agree, but that is OK because your team has to develop your best practices and I am just here to help.

What is Systems Engineering?
You have all heard about Aerospace, Electrical, Civil, and Mechanical Engineers, who specialize in certain area, but what is a system engineer and what do they do? A systems engineer takes a look at the “Big Picture” and defines, develops, and implements the systems. They work with a group of experts in various areas of specialization to achieve a common goal. It is part management and part technical. Many different definitions are out on the web on systems engineering, I Googled (is that a verb in the dictionary yet?) Systems Engineering and got 363 Million hits. Let’s look at a simple example of what a systems engineer would do.

An aircraft manufacture wants to build a huge jumbo jet, bigger than anything else built. It will seat 600 people. They put all their resources into the design and manufacturing but find out that no one will buy it. Why? Well they found out that no airport could accommodate that big of an aircraft, the air space system would have to have larger separation due to wake turbulence (less landings), and loading and unloading the passengers would take way too long. A systems engineer would have looked at the initial design of the aircraft and then all the other systems like the airports, air space, and passenger systems and realized that just building the jumbo jet is not going to make it successful, the infrastructure would have to be redesigned too.

A lot of concentration in robotics is given to the design and building of the robot, but is the robot the only system you have to design? I would say NO, the robot is only one subsystem of the FIRST system at a team level. So what is the FIRST team system? The elements of the FIRST system will be different for each team, but here are some subsystems that I feel need dedicated design efforts. I am only looking at the system from a team level. The Team Handbook on the FIRST FRC website has great discussions on several of the items that I will be outlining in these articles. (http://www.usfirst.org/community/frc...t.aspx?id=966). A must read for rookie and veteran teams alike. So here are my thoughts on the six subsystems that make up the FIRST team system. Each subsystem has its own subsystems that will be discussed in future articles.

Safety System: Working around the tools, the metals, and the robot could create safety hazards that have to be identified and managed. Establishing a good safety system within your team is important within the total FIRST system. Plan, design, and implement safety in all that you do.
The Team System: The team system is how you are going to design your team. The handbook on the FIRST website is an excellent resource on some team structures. Also part of your team is the mentors, advisors, and community supporters. What is your team philosophy and rules of conduct? The design and building of a great team system is the foundation to your future success. Is your team organization during the construction phase the same as the organization during the competition phase? (I will discuss this in another post)
Archive System: What? Well as you are designing your robots, your safety system, and your team, you have to really be thinking about how you are going to document the success and failures. Does your team document its software from last year, what worked for fund raisers; do you have a design notebook that future teams can use? Documentation is vital to a good systems engineering approach to any design, take some time to think about this system and I am sure you will not be sorry.
The Robot System: Well this system is probably given the most time and dedication during the course of the year. A good robot system will give your team recognition during competitions and could bring home a competition championship. The ultimate high to win the Chairman’s award will take more than just a great robot.
The Outreach System: This system is a little more abstract but how is your team designing your community outreach? Do you have plans for media events, elementary and middle school demonstrations, sponsoring Lego and/or VEX teams. The vision of Dean Kamen is to “…to create a world where science and technology are celebrated…where young people dream of becoming science and technology heroes….” How does your community outreach system inspire others?
Financial System: Well this one is required for every team. With potential budgets running from $10,000 to $20,000, a well run financial system will be vital to building a robot, traveling to competitions, recognition banquets, etc.... How do you develop your budget, how do you get corporate sponsors, and how do you do fund raising?

Working for the Government, we have tons of acronyms and of course I developed one for the Systems Engineering (SE). So, if you want to be a FIRST STAR OF SE, remember these team subsystems Safety, Team, Archive, Robot, Outreach, and Financial. (well, I thought it was funny)

How do these subsystems work together in each phase of the lifecycle (season)? In further discussion, I will describe how the systems could work together for a successful season during the robot build and competition phases.