Escolar Documentos
Profissional Documentos
Cultura Documentos
Systems Engineering
Executive Summary
Achieving sustainable growth and profitability in an environment of constant change and
increasing complexity motivates companies to find better ways to develop and produce
innovative products. Systems engineering (Figure 1)1 helps address these needs through its
capacity to improve a companys design, manufacture and support of complex, highly
integrated products.
While systems engineering is widely discussed and
implemented in some form at many companies, the
actual practice tends to fall short of the ideal. Most
companies that develop complex products have
systems methodologies in use. However, the
development and engineering practices relating to
these, and the abstract whole systems models that are
at the heart of the systems definition process, are not as
well integrated into the product development lifecycle
as they could be.
Systems engineering is an
interdisciplinary process that
ensures that the customer's needs
are satisfied throughout a system's
entire life cycle..to produce
systems that satisfy the customers'
needs, increase the probability of
system success, reduce risk and
reduce total-life-cycle cost.
Source: A consensus of senior systems
http://www.sie.arizona.edu/sysengr/whatis/whatis.html
Page 1 of 8
In turn, companies systems engineering approaches must mature to leverage this new layer
of software as it emerges. As a foundation, executives must create clear visions for holistic
systems approaches within their operations. They should actively engage in programs that
ensure improved knowledge sharing across many development and operational disciplines.
Importantly, their support for changes needed in company working cultures and habits will
be critical to the success of these programs.
Page 2 of 8
A relatively recent military example highlights problems exacerbated though poor systems
development. The Phoenix2 drone was ordered by the British military and delivered in the late
1990s. To quote one press source Its troubled 1990s development history is now used as a
how-not-to-do-it example in university systems engineering coursesThe Phoenix was
especially renowned for its Rube Goldberg/Heath Robinson recovery method, in which it
descended to land hanging upside down beneath a parachute. This was in order to
safeguard sensitive sensor gear in a belly pod. Unfortunately, the upside-down landings were
found to wreck the fuselage, so exasperated engineers finally added a dorsal airbag to
cushion the shock Attempts to remedy this and other faults in the Phoenix resulted in
significant added costs and ultimately a re-assessment of the militarys choice of drone.
Historical investments in domain-specific applications, workflows and data sets have resulted
in islands of domain competence. Even use of multi-faceted systems such as PLM for
electronics and mechanical design, and SCM or ALM for software can result in disconnects.
Although these are fundamental to the successful operation of the complex system, their
somewhat isolated use can create challenges, particularly around successful integration of
sub-systems to deliver the final product. Thats not to say, of course, that these domain
technologies, knowledge or workflows exist in isolation, far from it. However, historically there
has been a heavy reliance on manual or proprietary interfaces.
http://www.theregister.co.uk/2008/03/26/phoenix_says_goodbye/
http://current.com/community/89197208_mod-scraps-227m-phoenix-spy-drone-that-hated-heat-and-landedupside-down.htm
http://openlearn.open.ac.uk/mod/oucontent/view.php?id=397849§ion=1.2
http://3mr.me/1-2-the-phoenix-project/
3
http://www.darpa.mil/Our_Work/TTO/Programs/AVM/AVM_Design_Tools_(META).aspx
Page 3 of 8
requirements from the earliest stages of the development process. They provide a
better means for all stakeholders in their various disciplines to remain mindful of
primary business and product objectives and overarching product requirements.
Page 4 of 8
Quality
There have been many high profile and costly quality failures in the press of recent
years. Quality is a testament, in part, to the competence of a company's product
development lifecycle programs which includes, of course, systems strategies. Any
disconnect in the development process from issues such as common data reuse and
domain interface act as inhibitors to improving overall product quality. Eminently
highlighted by the Phoenix drone example above, the complex relationship between
systems, sub-systems and their constituents can obviously be fractious on large
projects. This makes it all the more important that quality and testability be intimately
integrated throughout the overall development process from the kick-off.
Developing a vision
Systems methodology should, by its nature, form the basis for improvements that span the
entire development lifecycle, encompassing areas such as requirements definition, design,
optimization, variation, quality and test. Any re-definition or re-focus of systems engineering
approaches will obviously require careful consideration of opportunities balanced against
cost and risk.
To move forward, companies need a more integrated vision of systems engineering. This
vision is one that defines a holistic systems approach that delivers a better understanding of
how and why decisions were made, and what influence these have on the products and
processes.
If this vision is deeper than the one you work to today, youre in the majority. For most
development organizations, change in both working practice and technology solutions will
be essential to fully deliver on the goal of more integrated development structures. As with
other broad reaching initiatives, change is most successful when driven by a vision from
upper levels of management. Executive support and participation to provide guidance and
encourage collaboration is essential to making the organization much more capable than
the sum of its parts.
It almost goes without saying that due diligence in establishing the vision is important in any
change program. Yet it is often skipped over or rushed through on internal change projects
without the support and advice of trusted advisors. Software suppliers, consulting and service
providers are amongst the many organizations that have a wealth of knowledge and
practical domain experience to help define practical routes forward. These organizations
can help companies understand the opportunities and risks of potential investments and
provide insights into best practices and technologies that may better address development
needs.
Page 5 of 8
artifacts. This should be one that ultimately maintains the abstract whole systems model as a
constant integrated reference, and one that delivers effective and integrated sub-system
developmentin short, one that achieves the promise of a true systems approach.
In practice, more effective developmental strategies supported by appropriate technology
investments will help to drive positive change in your business. With this in mind, some of the
activities that you may wish to consider on the road to improvement include:
Page 6 of 8
sub-system and ultimately component level. While quality by design is a decadesold concept, systems engineering can bring it to a next level of effective deployment.
Seek to apply integrated quality and test processes that leverage the benefits of the
top-down strategic systems model to deliver a more auditable and ultimately
valuable strategy for quality processes.
Conclusions
With a background of economic unrest, uncertainty in product demands and an
increasingly savvy customer base, there is pressure on businesses to deliver better, more
profitable products. Delivering these in the context of increasing development complexity
continues to focus discussions on technologies in use and strategies employed to deliver
product to market. Companies must move to better utilize all aspects of their knowledge and
asset base.
Evolution from accepted development paradigms is rarely straightforward. Faced with the
task of moving from well-established, often discrete domain-driven workflows, to a top-down
approach that is at once transparent and collaborative, businesses will inevitably require
change in both corporate and individual cultures. Nonetheless, the vision of a truly
integrated multidisciplinary development lifecycle arguably may only be achieved through
a more strategic view of both product definition and its development from the offset,
leveraging the values of the business as a whole to generate value beyond the mere sum of
its parts.
Of course this wont be easy, but there are actions that all large producers of complex
products can take now. A pragmatic re-assessment of existing systems engineering strategies
as a starting point would undoubtedly help companies better appreciate any disconnects
between their overall corporate goals and their in-use technologies. Within this task,
companies have the opportunity to assess the relationship between departments, workflows,
and data to help define and influence future activities.
4
5
http://www.autosar.org
http://open-services.net/
Page 7 of 8
In line with the holistic systems engineering approach advocated by this paper, any
technology investments must act to support corporate objectives - not define them.
Customers, especially larger ones, have a valuable part to play by inciting software vendors
to deliver more valuable, open and collaborative working environments. Having said this,
software innovation is ongoing and there are some interesting developments coming from a
number of software vendors. Indeed the realization of systems engineering as an overarching
and integrated practice throughout the development lifecycle, along with upcoming
solutions to support it, may well be closer than one thinks.
Page 8 of 8
RAL14060-USEN-00