# 5 - Systems Engineering

A lot of ressources are widely available on Systems Engineering. Whereas most books on this subject talk about methods for analysis performance, defining requirements and architecture, this article will discuss the process framework for implementing the methods of engineering a system.
In today’s increasingly competitive environment, many companies are turning to systems engineering to work more efficiently. Application of systems engineering requires a commitment to make it work, to avoid the easy solution, and to stand firm when necessary. 

Systems Engineering (SE) is the process that control the technical system development effort with the goal of achieving  an optimum balance of all system elements. It is a process that transforms stakeholder’s needs into clearly defines requirements and allocates and integrates those requirements to the various development disciplines needed to realize the system products and processes. Then, using specific methodology, the process attempts to optimize the effectiveness and cost of the systems.
Using SE process fulfills two fundamental purposes:
  • First, it makes sure we understand the question before designing the answer.
  • Second, it coordinates, focuses, and balances the technical efforts of all involved throughout the development process.
« Understanding the question » is accomplished through various forms of disciplined analysis, focused on functions. Requirements are linked to design solutions through the allocation process in order to support traceability. Trade studies document the decision process.
The coordination and management aspects of SE include integration of disciplines as well as integration of system elements, risk management, technical progress monitoring, Design To Cost control, technical reviews and overall planning and control of the technical effort.
SE solves complex problems, and requires extensive communication between and among the various engineering disciplines. The SE process involves a multi-disciplined, integrated, concurrent effort.
Concurrent engineering attempt to solve the problem of numerous, expensive design change late in the development cycle. Design change earlier in the development phases are much less expensive to correct by several order of magnitude.

Systems Engineering Data
Although it is common for the engineering data to be organized into documents, the interesting part is actually the data itself. Focusing on the documents (writing, signing off, etc.) often leads to poor management practices such as refusing to update a signed off document just because the data it contains have been proven to be wrong (yes, this does actually happen). If, instead, we focus on getting the engineering data correct and consistent, system engineering practice will be improved. Furthermore, the traceability we need for most projects is not between document themselves but between statements within those documents.

Comments

Post a Comment

Popular posts from this blog

# 11 - Model-Based Systems Engineering (MBSE)

The best way to understand the MBSE approach is to begin by understanding the alternative: what modeling partitioners call the document-based approach to engineering (and what nonpractitioners call "the way we have always done things!"). With the document-based approach, engineers manually generate some subset of the following artifacts: concept of operations (ConOps) documents, requirements specifications, requirements traceability and verification matrices, interface definition documents, systems design specifications and speciality engineering analysis such as analyses of reliability, FMEA, etc. Document-based systems engineers produce these artifacts in a form of a disjoint set of text documents, spreadsheet, diagrams, presentations (and configuration-manage them in a disjoint set of repositories). The document-based approach is expensive. More precisely, it's more expensive than it needs to be; you incur a significant percentage of total life cycle cost maintaining t...
Read more

# 10 - Principles of Dynamic Work Design

Image
Consider a well-known example of work and organizational design, Toyota’s Andon cord. In the Toyota scheme, a worker noticing such an issue is supposed to pull what’s known as the Andon cord (or push a button) to stop the production line and fix the problem. While the management literature has correctly highlighted the importance of allowing employees to stop the line, what happens after the cord is pulled might be more important. When one operator on the factory floor is struggling to complete a task in the allotted time, and so hit a yellow button, causing an alarm to sound and a light to flash. Within seconds, the line’s supervisor arrived and assisted the operator in resolving the issue that was preventing him from following the prescribed process. In less than a minute, the operator, now able to hit his target, returned to his normal routine, and the supervisor went back to other activities. A visual of this process can be seen below: What, from a work design perspective, happened...
Read more

# 12 - MOEs, MOPs and TPMs

Let's start by defining these acronyms: - MOEs: Measures Of Effectiveness - MOPs: Measures Of Performance - TPMs: Technical Performance Mesures Following a recent discussion on this topic, I've come to realize that there is a lot of confusion around these concepts, so let's try to bring some clarification! MOEs, which are stated from the acquirer (customer/user) viewpoint, are the acquirer's key indicators of achiving the needs for performance, suitability and affordability across the life cycle. The MOEs are used to validate the system at each stage of the design process and provide insight into some of the more subjective qualities desired by the acquirer that are not, or can not, be captured by hard requirements. Many of the "ilities" are used in MOEs where, for example, it may be very difficult to generate a shall statement on operability, but operability nevertheless remains an important characteristic. MOPs measure attributes considered as important to e...
Read more