<p>Every now and then I feel the need to defend systems engineering. (Actually, my field is OR, but it's close enough.)</p>
<p>Mechanical, electrical, and computer engineers focus on designing the system right. Systems engineers focus on designing the right system. We have a wide range of tools to help optimize this design process. These include some of those big-boy mathematical functions. In the past few months, I've had occasion to work with the Hessian, the Jacobian, and the Reimann Zeta function. We, too, eat z-transforms for breakfast.</p>
<p>Of course, to gravitate toward math-intensive solutions is a typical rookie mistake. My clients and customers have problems that quickly exhaust the tools of closed-form mathematics. You try to write the Lagrangian as part of solving for the Kuhn-Tucker conditions, but it just doesn't reduce to a workable set of equations. Modern complex adaptive systems need and use numerical approaches such as systems dynamics, and advanced simulations like agent-based models.</p>
<p>Any large-scale enterprise needs both component engineers and systems engineers. Both are necessary, neither is superior. If you arrive in the workforce with that chip on your shoulder, you will not build an effective team. You will lose out to teams that are built on mutual respect. </p>
<p>Is there a market for systems engineers? A search of the Washington Post last month showed over 700 vacancies that listed "systems engineer". </p>
<p>My son followed my advice, and will soon graduate with a degree in systems engineering. (It did not take much: he enjoyed the field and he doesn't read CC). Tomorrow morning he will go to his tenth interview. He is struggling to choose among an embarrassingly wide range of different specialties.</p>
<p>A search of salary.com shows that "operations research" job title peaks out at $125K, far above other engineering titles. </p>
<p>So, call us what you will. We're "ISE'ing" all the way to the bank.</p>