Welcome to the SOuthern ARizona (SOARizona) INCOSE chapter website. The chapter is centered in Tucson, Arizona. Anyone whose interests intersect with the profession of Systems Engineering is welcome to participate. This includes those in the profession of Project Management for engineering content as described on the wiki for the Guide to the Systems Engineering Body of Knowledge (SEBoK). Get involved with the chapter through chapter meetings, speaker series, working groups, conferences, the U of A, and support to pre-college development of interest in Systems Engineering. SOARizona is also actively engaged with mentoring in the College of Engineering at the University of Arizona.
The SOARizona Chapter is a not-for-profit membership organization founded to develop and disseminate the interdisciplinary principles and practices that enable the realization of successful systems.
To share, promote and advance the best of systems engineering from across the globe for the benefit of humanity and the planet.
Contact us at soar@incose.net
We want to hear from you!
Do you have an interest in supporting the chapter? It provides a great way to get involved, provides continuing professional development units (for certification), and gives you a strong voice in the chapter.
Do you want to hear about system engineering concepts, trends, and topics? Recommend to us something you want to hear.
Join our mailing list to get updates on the chapter, upcoming events, and ways you can participate.
Sign up for our e-mail list here (Google group).
We actively collaborate with regional chapters to gain proficiency in the practice of systems engineering. The availability of effective online tools enables us to participate in events hosted by other chapters. Chapter members also have opportunities to participate in INCOSE Working Groups. Our collaboration partners include:
Oct 13, 2021 4:45 PM - 5:45 PM Mountain Standard Time
Abstract: INCOSE has expressed interest in the application of systems engineering principles and practices in industries outside of the classic aerospace, communications, and other large system developments commonly related to the discipline. In this case, a visit to the kitchen at the Inn at Little Washington triggered thinking about how and why it was so different from other commercial kitchens. The resulting analysis of how systems engineering has significant relationship to the design of a wide variety of commercial kitchens is provided in this paper. The objective is to learn how we can see systems engineering in places it isn’t normally found to both find other ways it can be applied and to help others improve their results by using systems engineering discipline. Speaker Biography: Jim Armstrong has practiced systems engineering for 54 years, performing various roles including configuration management, test, deployment, chief engineer, program manager, and program element monitor. For the last 30 years, he taught, consulted, and appraised systems engineering in industry and government. Jim was on the author teams for most of the systems engineering standards and is a frequent presenter at INCOSE events. He has a BS in Mechanical Engineering from Rensselaer Polytechnic Institute, an MS in Systems Management from the University of Southern California, and a PhD in Systems Engineering from Stevens Institute of Technology. He has an INCOSE Expert Systems Engineering Professional certification.
Read More
Ever wonder why some people seem stuck in their jobs, with little advancement and with little joy in their careers, while others seem to thrive and move forward? Thinking about your career as you might think about your customers' challenges can provide insight into how to avoid the ruts and find your path to success.
SOAR members, there are many ways to get involved in the chapter and the organization, benefiting you as a member and others with your knowledge, energy, and creativity.
Yammer is INCOSE's social media platform for members. Use your INCOSE-issued Microsoft credential to login and join the conversation. INCOSE credentials are in the form of first.last@incose.net or first.last@incose.buzz.