In a previous article, I discussed what Systems Engineering (SE) entails – in particular how it differs from Project Management (PM) – and the ways in which SE can benefit you, regardless your business sector. This article sets out the case for the importance of the Systems Engineering Management Plan (SEMP) and its necessary dual, together forming a unique tool to gain a quick and high-level, systematic, and systemic perspective on the operations of cross-functional, inter-departmental or systems engineering projects and programmes.
A systemic perspective is typically achieved through the combination and integration of multiple perspectives. In a SE setting, the SEMP plays a crucial role in ensuring that all relevant perspectives are considered and integrated. This underscores the pre-eminence of its uniqueness. Furthermore, I propose that a dual of the SEMP be created based on the relationships between maps and territories as well as summaries and books. From the outset, one might also consider Project Management Plan (PMP). For a description of the relationship between a PMP and a SEMP on a specific real programme, please refer to section 1.4 of (3).
I will not go into the definitions of a map or a summary/outline here, but it is clear why they are important for a territory (in the broad sense, e.g. an organisation, a geographical territory, etc.) and a book or document. I will simply quote Alfred Korzybski:
« A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness. »;
and Kent D Palmer (1):
« It [the table of contents, or better, the outline of a book] gives access to the relevant and significant parts of the book’s content on demand. Without the table of contents and the index, if you need to find something in the book, then you are forced to read the book again, or skim it, perhaps missing the things you are looking for! […] The contents with outlines and the indexes are extrinsic to the text and we consider it an essential part of the book product if the subject matter is technical and complex. »
In light of the above, I would like to enquire as to how an organisation that is running cross-departmental, cross-functional or systems engineering operations can obtain a comprehensive overview of these operations. To put it another way, what would be the equivalent of a map or summary if one were to consider these operations as a territory or a book?
One might consider PMP, SEMP or the various existing modelling, visualisation, and management tools. In the following, I will focus on systems engineering to address this question.
“The Systems Engineering Management Plan (SEMP) is the foundation document for the technical and engineering activities conducted during the project. The SEMP conveys information to all of the personnel on the technical integration methodologies and activities for the project within the scope of the project plan. SEMP content can exist as a stand-alone document or, for smaller projects, in higher-level project documentation. […] The SEMP communicates to the team itself, managers, customers, and other stakeholders the technical effort that will be performed by the assigned technical team.” (2)
The SEMP is therefore a comprehensive and dynamic plan that describes how systems engineering should unfold. However, it does not provide direct access to work products produced throughout different phases and related activities. For instance, while the SEMP may indicate how system architecture artefacts will be connected to problem definition artefacts, it does not provide direct access to such actual connections or artefacts. In essence, there is a lack of a dual of the SEMP that would correspond to produced structural artefacts.
One might consider utilising product lifecycle management tools or other lifecycle tools for that purpose. However, it should be noted that these tools do not address all structural concerns involved in a SEMP. In fact, they are not as comprehensive or systemic as the SEMP itself. Besides, one could also consider navigating specialized tools to get access to produced structural artefacts: this would be tantamount to dive into the “territory” or “book” which is not what is sought after. These tools typically address a specific set of domains, including planning, requirement, concept of operation, architecture, interface, verification, validation, risk, trade-offs, technical review, budget, traceability, configuration, change management, production, and more.
Consequently, a map view of the aforementioned operations would be a dual of the SEMP, taking into account the fact that, even at the organisational level of the SEMP, a question of granularity might be raised.
In view of the above, what can Timeinx offer your business?
Timeinx provides users with the ability to build the dual of the SEMP, offering all stakeholders the chance to gain rapid, high-level, and comprehensive visibility of the various structural products from different domains involved in the aforementioned operations. From this, users can access specialised repositories to obtain further details. In essence, Timeinx provides all stakeholders with a comprehensive, high-level overview that encourages open communication, the valuation of contributions from all departments or domains, and genuine and trusted collaboration, which may ultimately result in timely alignments.
Thank you for taking the time to read. You can also follow our LinkedIn page.
1. Palmer, K. D. (2014). The essential nature of product traceability and its relation to agile approaches. Procedia Computer Science, 28, 44-53.
2. https://www.nasa.gov/reference/appendix-j-semp-content-outline/ (Accessed 11/2024)
3. SMART COLUMBUS. Systems Engineering Management Plan for the Smart Columbus Demonstration Program. The Smart City Challenge Demonstration, U.S. Department of Transportation https://rosap.ntl.bts.gov/view/dot/34764/dot_34764_DS1.pdf (Accessed 11/2024)
