hat better context for discussing knowledge manage ment with systems engineers than a conversation about managing the information contained within the Guide to the Systems Engineering Body of Knowledge (SEBoK)? One of the hallmarks of the maturation of a discipline is an agreement by the professional community regarding what knowledge is included in the discipline and how that knowledge should be captured and organized to facilitate its use by practitioners, researchers, and educators (i.e., a guide to its body of knowledge). With this goal in mind, this article is intended to spur community involvement and support for the SEBoK development currently underway, through constructive and lively conversations about the management of the body of knowledge of systems engineering. The Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) team has been evolving a body of knowl edge for systems engineering since December 2009 (Squires et al. 2009) when the first author workshop was held. At this author workshop, 21 authors and team members developed an initial structure for the SEBoK based on the existing INCOSE Systems Engineering Handbook (Haskins 2010) and the ISO/IEC 15288 stan dard (ISO and IEC 2008); they then subdivided the work and began to write. Other key references for the team’s initial efforts included previous work completed by INCOSE members and documented across three editions of INSIGHT (Axelband et al. 2006; Friedenthal 2006; Harwell 2006; Leibrandt et al. 2002). At the second workshop in March 2010, 29 authors and team members expanded the contents of the SEBoK to include applicable knowledge outside of the system life cycle process space, including systems thinking and concepts. The authors organized the SEBoK around knowledge areas, topics, and subtopics, an approach simi lar to that used by the Software Engineering Body of Knowledge (Abran et al. 2004). At the third workshop in July 2010, 35 authors and team members agreed on the final content areas for the first draft version 0.25 of the SEBoK (Pyster et al. 2010a). The fourth workshop in October 2010 focused on the finalization of the accompanying Graduate Reference Curriculum for Systems Engineering (GRCSE), version 0.25 (Pyster et al. 2010b). The fifth workshop in January 2011 marked the return of the community review comments on SEBoK version 0.25 and the development of a new structure to the SEBoK that was adopted by the 32 author and team members in attendance. In this phase of the evolution, the expansion of knowledge areas that had previously occurred was now reorganized into a higherlevel structure, comprised of “parts,” with some additional missing pieces identified. This current knowledge structure is outlined next.