# 1 - Big Picture

This blog talks about ideas and processes, how to go from point A to point B the most effectively with the best results.
This blog is primarily intended for design engineers, systems engineers, project managers, senior management, executives but could be useful to anyone who might be curious. 



Big Picture

Product development, especially when the system or project is complex enough that conventional development techniques cannot deal with the development project’s uncertainties needs some well-structured processes. 
A lot of books and resources are widely available, discussing project management techniques, systems engineering processes but very little resources are available regarding how to combine efficiently these methods to look at the Big Picture and what we need to do if we are dealing with complex problems, complex technologies or unprecedented solutions.
First of all, we must understand the problem before designing the solution. That sounds like common sense and pretty straightforward. When it comes to complex products, IT’S NOT. Too many companies devote far too little time to it. 
Most engineers and managers come out of the university all geared up to solve the problems of the world. It is a rude shock for them to discover that the problems they are to solve have not been defined yet! There are no « professors » in the real world to neatly spell out the problem for them. Often, we end up with engineering solutions looking for a problem!
There is a famous quote that I love: "If you don't know where you are going, you'll probably end up someplace else!"

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