|
|
| (32 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Project Management]] | + | [[Benefits of systems engineering]] |
| − | [[Category:Systems Engineering]]
| + | |
| − | [[Category: management concepts in engineering]]
| + | |
| − | =Summary=
| + | |
| − | | + | |
| − | The scope for this Wiki article is to explore the possibilities of systems engineering being more beneficial compared to other management concepts. In this article a presentation of the basic concept of systems engineering will be made followed by a comparison with other management approaches such as:
| + | |
| − | | + | |
| − | * Project management
| + | |
| − | | + | |
| − | * …
| + | |
| − | | + | |
| − | and a reflection on their different mind-sets and frameworks.
| + | |
| − | The inspiration for this article are the need for knowledge and understanding in how the different management approaches can influence a project and how these concepts can contribute to the building process being more efficient.
| + | |
| − | | + | |
| − | (Insert final result of the comparison)
| + | |
| − | | + | |
| − | =Introduction to systems engineering (SE)=
| + | |
| − | ==Fundamentals of concept==
| + | |
| − | The basic concept of systems engineering is to have an interdisciplinary approach by involving knowledge, methods, terminology and expertise from different kinds of disciplines and by this allow successful systems. The focus is to define customers required functionality and needs for a specific project in an early stage while also considering the complete project lifecycle. This includes operations, performance, cost and schedule, training and support, test, disposal and manufacturing. The goal is to form a structured development process that proceeds from concept to production to operation by integrate all different disciplines and speciality groups involved in a project into a team. By doing this, all customers needs, both the technical requirements and the business side of a project, will be considered. The goal of providing a quality product that fulfils the needs of the user will likely be realised. [1]
| + | |
| − | | + | |
| − | A system can be defined as a collection of different elements that produces a better result put together then what can be obtained by the elements alone. These different elements can be all the things required to obtain system results, for example people, software or hardware, facilities, policies and documents. The system is a result of the high level of quantities, properties, characteristics, functions, behaviour and performance obtained by the collection of elements. This system-level result is created by the connection made among the elements. [2]
| + | |
| − | | + | |
| − | An engineered system is an open system made out of technical or sociotechnical elements which is created by or for people with a purpose to satisfy key stakeholders and has a life cycle. The engineered system has a boundary and an external environment and is a part of a system-of-interest hierarchy. [3]
| + | |
| − | | + | |
| − | ==Method of practice==
| + | |
| − | Systems engineering is used to ensure that the needs of the customer and the stakeholders are satisfied and that a high quality, trustworthy, cost efficient and schedule accommodating manner is used throughout the system’s entire life cycle. This process is described by the acronym SIMILAR with consists of the following seven tasks:
| + | |
| − | | + | |
| − | * '''S'''tate the problem
| + | |
| − | | + | |
| − | * '''I'''nvestigate alternatives
| + | |
| − | | + | |
| − | * '''M'''odel the system
| + | |
| − | | + | |
| − | * '''I'''ntegrate
| + | |
| − | | + | |
| − | * '''L'''aunch the system
| + | |
| − | | + | |
| − | * '''A'''ssess performance
| + | |
| − | | + | |
| − | * '''R'''e-evaluate
| + | |
| − | | + | |
| − | The SIMILAR Process is visualized by Figure 1. It is important to note that the systems engineering process is executed in a parallel and iterative manner between all elements. [1]
| + | |
| − | | + | |
| − | [[Image:TheSimilarProcess.png|center|30x]]
| + | |
| − | | + | |
| − | By stating the problem a description of the top-level functions that is required by the system is made. All requirements should be traceable to this problem statement. A problem statement should be in terms of what must be done, not how it should be done. Inputs for this statement comes from end users, operators, maintainers, suppliers, etc. Based on performance, schedule, cost and risk, different designs are created for evaluation of which alternative is preferred. All alternatives should be judged for how they accomplish the set requirements to reduce project risk and to clarify the problem statement. Models will be developed for most of the alternative designs but the most preferred alternative model will continuously be expanded and used to help manage the system throughout the entire life cycle. For this, many types of system models are created to help along the process. These models can help to study scheduling changes, create PERT charts and to perform different analyses and also to explain the system. As explained earlier in this article, the fundamentals of systems engineering is to integrate different disciplines and to make them integrate with each other and work as a whole. It is important to define and to create interfaces between subsystems to minimize the amount of information that will be exchanged between them. This contributes to easier manageable information and also to more efficient processes. To launch the system means running it and making it produce outputs. In this phase the preferred alternative will be designed in detail and the processes used for this are developed. The process of designing and producing the system is iterative as knew knowledge are developed along the way can cause a re-consideration and modification of the preferred alternative. Measurement is the key, if you cannot measure it, you cannot control it. If you cannot control it, you cannot improve it. It is highly important to assess the performance of the system and to manage its resources throughout the system life cycle. As one of the most fundamental engineering tools, re-evaluation of the system is a continuous process and will do many parallel loops throughout the entire process. This means observing outputs and using that information to modify the system. This is revealed in Figure 1.
| + | |
| − | | + | |
| − | It is also important when using systems engineering that the whole process should be documented, measurable, and stable and have a low variability. The concept should be used the same why by all disciplines. [1]
| + | |
| − | | + | |
| − | ==Pros and cons with SE==
| + | |
| − | | + | |
| − | ===Pros===
| + | |
| − | When incorporating the methods and tool in Systems Engineering the concept can improve the quality and management of requirements in a project. These methods and tools results in better work breakdown structures and plans that deliver enhanced specifications to e.g. suppliers and sub-contractors. Project management and Systems Engineering have the same project goals, but they differ in approaching them. Project management defines them and Systems Engineering knows how to deliver them. Due to the fact that Systems Engineering fix foreseen errors in the concept stage, it is possible to stop the cost rising exponentially. Systems Engineering is a way of working less chaotic and stressful. It brings people benefits as well. [4]
| + | |
| − | | + | |
| − | ===Cons===
| + | |
| − | While there are several beneficial contributions with Systems Engineering there are also some significant root problems that are external to Systems Engineering. The external problems can limit the benefits that can be achieved by Systems Engineering. These problems are, to a large degree, issues of management, organization, incentives, subject matter expertise and previous experience of Systems Engineering. These external problems are more problems of implementation, integration and execution of Systems Engineering than of the methods and tools of Systems Engineering. The highly central issue with Systems Engineering is the overoptimistic estimates in a project and the lack of clear lines of the ownership and accountability. External input requirements to the program can be unrealistic and incomplete which undermine Systems Engineering execution and confidence in this management concept. [5]
| + | |
| − | | + | |
| − | ===Conclusion===
| + | |
| − | To be successful with Systems Engineering, it is important to understand the problem, investigate alternative solutions, agree and manage the requirements and interfaces, prepare the test and support systems and track progress against a plan.
| + | |
| − | | + | |
| − | It is not difficult to notice when Systems Engineering fails, because when something important goes wrong it usually appears fast. But when Systems Engineering is successful, no one usually notice – which is how it should be. [4]
| + | |
| − | | + | |
| − | =Approach of other management concepts in relation to Systems Engineering=
| + | |
| − | ==Project management==
| + | |
| − | Project management is defined as the application of knowledge, skills, tools and techniques to project activities to meet the specific requirements of a project.
| + | |
| − | | + | |
| − | A project is a temporary investment to create a unique product, service or a result. It is temporary in that it has a defined beginning and end in time. Which lead to the project having a defined scope and resources. You can define a project as to be unique in that it has not a routine operation, but a specific set of operations designed to accomplish one goal.
| + | |
| − | | + | |
| − | Project management can be divided into different processes which are; initiating, planning, executing, monitoring and controlling and closing. [6] The first process is to carefully examine the project idea to determine whether or not it is beneficial to the organization. A decision making team is identifying if the project can realistically be completed. After the project conception and initiation the project definition and planning begin. A project plan, charter and/or scope may be created to outline the work that has to be performed. A team will prioritize the project, calculate the budget and schedule, and define needed resources for completing the project. It is now time to execute and launch the project. This is done by distributing the tasks to the resources and inform teams with their responsibilities. In this phase important information related to the project will be addressed. During the project performance, project managers will compare project status and progress with the actual plan. During this phase, changes to the project schedule may be done by the project managers to keep the project on track. When the project is completed and the client has approved the result of the project, an evaluation is made to highlight the project success and to learn from its history. This is called the project close. [7]
| + | |
| − | | + | |
| − | The knowledge of Project management covers ten fields
| + | |
| − | * Integration
| + | |
| − | * Cost
| + | |
| − | * Human resources
| + | |
| − | * Stakeholder management
| + | |
| − | * Scope
| + | |
| − | * Quality
| + | |
| − | * Communications
| + | |
| − | * Time
| + | |
| − | * Procurement
| + | |
| − | * Risk management
| + | |
| − | | + | |
| − | Projects and project management processes differ from different industries. But the idea is that Project management creates a unique focus on shaping the goals, resources and schedule for a specific project despite where it is used. [6]
| + | |
| − | | + | |
| − | ==…==
| + | |
| − | | + | |
| − | =Reflection=
| + | |
| − | =References=
| + | |
| − | <references/>
| + | |
| − | [1] http://www.incose.org/AboutSE/WhatIsSE
| + | |
| − | | + | |
| − | [2] Rechtin, E., W. Maier, M. (2000) “The art of systems architecting”, CRC Press
| + | |
| − | | + | |
| − | [3] SEBoK (2015) “Guide to the Systems engineering Body of Knowledge”, BKCASE, June 2015
| + | |
| − | | + | |
| − | [4] http://www.incoseonline.org.uk/Documents/zGuides/Z3_Why_invest_in_SE.pdf (2009), UK Chapter, International Council of Systems Engineering
| + | |
| − | | + | |
| − | [5] Ali K . Kamrani and Maryam Azimi (2010) “Systems Engineering Tools and Methods”, CRC Press Taylor & Francis Group
| + | |
| − | | + | |
| − | [6] http://www.pmi.org/About-Us/About-Us-What-is-Project-Management.aspx (2015) “What is Project Management?”, Project Management Institute, Inc.
| + | |
| − | | + | |
| − | [7] http://www.projectinsight.net/project-management-basics/basic-project-management-phases (2015) “5 Basic Phases of Project Management”, Project Insight by Metafuse, Inc.
| + | |
