Systems Engineering - Revision history

DanielRavenNest at 15:51, 3 May 2011

2011-05-03T15:51:32Z

← Older revision		Revision as of 15:51, 3 May 2011
Line 7:		Line 7:
	Over the years a number of tools have been developed to aid in designing complex systems.		Over the years a number of tools have been developed to aid in designing complex systems.

	===Requirements Analysis===		===[[Requirements Analysis]]===

	A system as a whole has a statement of what we want it to do. This is in the form of goals, values, mission description, performance requirements and such. It also needs ways to measure how good a given design is. These can be things like "minimum cost", "minimum waste output", and "maximum efficiency". These statements and measures are often in verbal form. '''Requirements Analysis''' is the process of putting them in numerical form, breaking them down to more detail, and assigning them to functions who will perform them. The assignment ensures that somewhere in the system the top level goals are met.		A system as a whole has a statement of what we want it to do. This is in the form of goals, values, mission description, performance requirements and such. It also needs ways to measure how good a given design is. These can be things like "minimum cost", "minimum waste output", and "maximum efficiency". These statements and measures are often in verbal form. '''Requirements Analysis''' is the process of putting them in numerical form, breaking them down to more detail, and assigning them to functions who will perform them. The assignment ensures that somewhere in the system the top level goals are met.
Line 62:		Line 62:

	* '''ISO/IEC 15288'' - "Systems and software engineering - System Life Cycle Processes" - 2nd Edition, Feb 1, 2008. This is an international standard to provide a common process framework covering the life cycle of man-made systems. The purpose of the standard is to provide a common way to communicate among various people involved with a project. This is similar to having a common language for text, or common symbols for mechanical or electrical drawings.		* '''ISO/IEC 15288'' - "Systems and software engineering - System Life Cycle Processes" - 2nd Edition, Feb 1, 2008. This is an international standard to provide a common process framework covering the life cycle of man-made systems. The purpose of the standard is to provide a common way to communicate among various people involved with a project. This is similar to having a common language for text, or common symbols for mechanical or electrical drawings.

			[[Category:Systems Engineering]]

DanielRavenNest at 14:45, 3 May 2011

2011-05-03T14:45:52Z

← Older revision		Revision as of 14:45, 3 May 2011
Line 1:		Line 1:
	~~{{under construction}}~~

	[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.		[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.

Line 8:		Line 6:

	Over the years a number of tools have been developed to aid in designing complex systems.		Over the years a number of tools have been developed to aid in designing complex systems.

			===Requirements Analysis===

			A system as a whole has a statement of what we want it to do. This is in the form of goals, values, mission description, performance requirements and such. It also needs ways to measure how good a given design is. These can be things like "minimum cost", "minimum waste output", and "maximum efficiency". These statements and measures are often in verbal form. '''Requirements Analysis''' is the process of putting them in numerical form, breaking them down to more detail, and assigning them to functions who will perform them. The assignment ensures that somewhere in the system the top level goals are met.

			At the most detailed level a subset of the requirements are assigned to a single function box. This now becomes the conditions that a specific engineering design needs to meet.

	===Input/Output Model===		===Input/Output Model===

DanielRavenNest at 14:21, 3 May 2011

2011-05-03T14:21:54Z

← Older revision		Revision as of 14:21, 3 May 2011
Line 3:		Line 3:
	[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.		[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.

	The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is ~~in development, but will cover~~ some of the basics of Systems Engineering as it can be applied to the GVCS, and point to further references for people who want more depth on the subject.		The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is lists some of the basics of Systems Engineering as it can be applied to the GVCS, and will point to further references for people who want more depth on the subject.

	==~~Definitions~~==		==Systems Engineering Tools==

	~~These are technical engineering definitions, which are not the same as general common use of the same words.~~

	~~'''Architecture''' - Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.~~

	'''Concern''' - Interest in a system relevant to one or more of its stakeholders. It pertains to any influence on a system in its environment including: developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological, and social influences.		Over the years a number of tools have been developed to aid in designing complex systems.

	~~'''Environment''' - Context determining~~ the ~~setting and circumstances of all influences upon~~ a ~~system from outside the defined system boundary.~~

	~~'''System''' - The combination~~ of ~~elements that function together~~ to produce the capability to meet a need, but which do not do so as separate elements. The elements include all hardware, software, equipment, facilities, personnel, policies, processes, documents, and procedures needed for this purpose. A system as a whole exhibits qualities, properties, characteristics, functions, behavior, and performance. The value added by a system as a whole, beyond that contributed by its elements, is created by the relationship of its parts, in ~~other words how they are interconnected~~.

	~~==Systems Engineering Tools==~~

	===Input/Output Model===		===Input/Output Model===
Line 25:		Line 15:
	===[[Functional Block Diagrams]]===		===[[Functional Block Diagrams]]===

	A complex system is too hard to design as a whole. By breaking it down into smaller components, you reach a level that can be designed in practice. Functional ~~block diagrams~~ are a way to display the component parts of a system from a functional perspective. In other words, what does it do? It also shows the flows among the parts of the system with each other, and also with the external environment. In other words, how does it interact? Flows can contain any sort of item, including information, matter, energy, labor, etc, or a combination thereof.		A complex system is too hard to design as a whole. By breaking it down into smaller components, which is called '''Functional Analysis''' you reach a level that can be designed in practice. [[Functional Block Diagrams]] are a way to display the component parts of a system from a functional perspective. In other words, what does it do? It also shows the flows among the parts of the system with each other, and also with the external environment. In other words, how does it interact? Flows can contain any sort of item, including information, matter, energy, labor, etc, or a combination thereof. Please see the linked page for more detail.

	A given function can be satisfied by one or more designs, which are evaluated and optimized according to the goals and requirements of the project. Choosing among alternative designs should be done via objective evaluation against a set of numerical measures, i.e. a scoring system. The measures should be derived directly from the project goals and requirements and applied consistently across the whole system.		===Trade Studies===

	A ~~system that is too complex~~ to ~~design as~~ a ~~whole is also too complex to display as a whole on a single diagram~~. ~~Therefore the block diagrams~~ are ~~broken up into multiple pages for the purpose~~ of ~~manageable display~~, ~~but the~~ system ~~is still a single interconnected whole~~. ~~Flows, function boxes,~~ and ~~pages are given unique numbers so that people can trace from one page to~~ the ~~next~~. A ~~box or arrow at one level becomes enlarged into~~ a ~~page at the lower~~, ~~more detailed level~~ and ~~keeps~~ the ~~identical number. Notes are added as needed~~ to ~~describe~~ the ~~functions and flows. Diagrams should fit on a single page each. Notes which overflow the diagram page go on additional pages labeled with the same number + a following A,B,C,..~~.		A given function can be satisfied by one or more designs, which are evaluated and optimized according to the goals and requirements of the project. Choosing among alternatives and optimizing a given alternative are formally done with '''Trade Studies'''. Different designs are objectively compared using a set of numerical measures, i.e. a scoring system. The measures should be derived directly from the project goals and requirements and applied consistently across the whole system. A single design is optimized by varying a feature, such as power output, and then using the same scoring system to find the best value.

	===Connecting Block Diagrams and Input/Output Models===		===Connecting Block Diagrams and Input/Output Models===

	Functional analysis is a continuing task done incrementally, rather than done once with a static product. A change in any one component, such as a new design, ~~can be examined to see the impact on~~ the system as a whole. By summing the flows of the component functions in ~~an input/output~~ model spreadsheet, you can find the ~~total inputs and outputs. Using the same numbering system for both maintains the relationship between them.~~		Functional analysis is a continuing task done incrementally, rather than done once with a static product. The block diagrams are a way to record and communicate the structure of a system. A model, such as an Input/Output Model lets you actively see how a change in any one component, such as a new design, impacts the system as a whole. By summing the flows of the component functions in a model spreadsheet (or other computer model) you can immediately find changes to the rest of the system components and the totals for the entire system.

	~~Here is an early example~~ of the ~~top level block diagram, showing the Global Village~~ system ~~as a single box. The flows from~~ the ~~environment are shown at the first level of detail. Environment is meant in the technical sense of "the rest of the world outside~~ the system~~". Likely some flows are still missing~~.

	~~[[File:Block_Diagram_0~~.~~0_Environment_V0~~.~~1.jpg]]~~		Using the same numbering system and structure for the diagrams and models maintains the relationship between them. They are both representing the same system, just different aspects.

	==Design Variables==		==Design Variables==
Line 52:		Line 40:

	If possible a progressive sequence should be designed into the system. This would define minimal "starter sets", and then optional add-ons, growth paths, second generation more specialized machines built using the first generation, etc. Depending on circumstances, people can then follow a growth path from some starting point to a desired end goal without needing to do it all at once.		If possible a progressive sequence should be designed into the system. This would define minimal "starter sets", and then optional add-ons, growth paths, second generation more specialized machines built using the first generation, etc. Depending on circumstances, people can then follow a growth path from some starting point to a desired end goal without needing to do it all at once.

			==Glossary==

			These are technical engineering terms as used in the Systems Engineering field, which are not the same as general common use of the same words.

			'''Architecture''' - Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

			'''Concern''' - Interest in a system relevant to one or more of its stakeholders. It pertains to any influence on a system in its environment including: developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological, and social influences.

			'''Environment''' - Context determining the setting and circumstances of all influences upon a system from outside the defined system boundary.

			'''System''' - The combination of elements that function together to produce the capability to meet a need, but which do not do so as separate elements. The elements include all hardware, software, equipment, facilities, personnel, policies, processes, documents, and procedures needed for this purpose. A system as a whole exhibits qualities, properties, characteristics, functions, behavior, and performance. The value added by a system as a whole, beyond that contributed by its elements, is created by the relationship of its parts, in other words how they are interconnected.

	==References==		==References==

DanielRavenNest: /* Functional Block Diagrams */

2011-05-02T21:07:28Z

Functional Block Diagrams

← Older revision		Revision as of 21:07, 2 May 2011
Line 23:		Line 23:
	This can be visualized as a spreadsheet with various machines in the GVCS as columns, and inputs and outputs as rows. Each machine requires inputs such as steel, lubricants, assembly labor, fuel, etc. It also produces some kind of output. The purpose of a model is to see if your system as a whole has closure and balance. In other words, are all the inputs matched by outputs? Are there missing machine types identified by missing inputs? Is the size or quantity of a particular machine in the kit the correct size/productivity? Will the system as a whole produce a surplus, and if so how much? These are really all questions of accounting. Rather than counting everything in money, this type of spreadsheet does the accounting of each type of input/output/resource/supply separately as categories. Note that human labor for manufacturing, assembly, maintenance, and operation is one of the input types.		This can be visualized as a spreadsheet with various machines in the GVCS as columns, and inputs and outputs as rows. Each machine requires inputs such as steel, lubricants, assembly labor, fuel, etc. It also produces some kind of output. The purpose of a model is to see if your system as a whole has closure and balance. In other words, are all the inputs matched by outputs? Are there missing machine types identified by missing inputs? Is the size or quantity of a particular machine in the kit the correct size/productivity? Will the system as a whole produce a surplus, and if so how much? These are really all questions of accounting. Rather than counting everything in money, this type of spreadsheet does the accounting of each type of input/output/resource/supply separately as categories. Note that human labor for manufacturing, assembly, maintenance, and operation is one of the input types.

	===Functional Block Diagrams===		===[[Functional Block Diagrams]]===

	A complex system is too hard to design as a whole. By breaking it down into smaller components, you reach a level that can be designed in practice. Functional block diagrams are a way to display the component parts of a system from a functional perspective. In other words, what does it do? It also shows the flows among the parts of the system with each other, and also with the external environment. In other words, how does it interact? Flows can contain any sort of item, including information, matter, energy, labor, etc, or a combination thereof.		A complex system is too hard to design as a whole. By breaking it down into smaller components, you reach a level that can be designed in practice. Functional block diagrams are a way to display the component parts of a system from a functional perspective. In other words, what does it do? It also shows the flows among the parts of the system with each other, and also with the external environment. In other words, how does it interact? Flows can contain any sort of item, including information, matter, energy, labor, etc, or a combination thereof.

DanielRavenNest: /* Connecting Block Diagrams and Input/Output Models */

2011-05-02T16:08:27Z

Connecting Block Diagrams and Input/Output Models

← Older revision		Revision as of 16:08, 2 May 2011
Line 35:		Line 35:
	Functional analysis is a continuing task done incrementally, rather than done once with a static product. A change in any one component, such as a new design, can be examined to see the impact on the system as a whole. By summing the flows of the component functions in an input/output model spreadsheet, you can find the total inputs and outputs. Using the same numbering system for both maintains the relationship between them.		Functional analysis is a continuing task done incrementally, rather than done once with a static product. A change in any one component, such as a new design, can be examined to see the impact on the system as a whole. By summing the flows of the component functions in an input/output model spreadsheet, you can find the total inputs and outputs. Using the same numbering system for both maintains the relationship between them.

	Here is an early example of the top level block diagram, showing the Global Village system as a single box. ~~Some of the~~ flows from the environment are shown. Environment is meant in the technical sense of "the rest of the world outside the system".		Here is an early example of the top level block diagram, showing the Global Village system as a single box. The flows from the environment are shown at the first level of detail. Environment is meant in the technical sense of "the rest of the world outside the system". Likely some flows are still missing.

	[[File:Block_Diagram_0.0_Environment_V0.1.jpg]]		[[File:Block_Diagram_0.0_Environment_V0.1.jpg]]

DanielRavenNest: /* Systems Engineering Tools */

2011-05-02T13:54:37Z

Systems Engineering Tools

← Older revision		Revision as of 13:54, 2 May 2011
Line 19:		Line 19:
	==Systems Engineering Tools==		==Systems Engineering Tools==

	* '''Input/Output Model''' - This can be visualized as a spreadsheet with various machines in the GVCS as columns, and inputs and outputs as rows. Each machine requires inputs such as steel, lubricants, assembly labor, fuel, etc. It also produces some kind of output. The purpose of a model is to see if your system as a whole has closure and balance. In other words, are all the inputs matched by outputs? Are there missing machine types identified by missing inputs? Is the size or quantity of a particular machine in the kit the correct size/productivity? Will the system as a whole produce a surplus, and if so how much? These are really all questions of accounting. Rather than counting everything in money, this type of spreadsheet does the accounting of each type of input/output/resource/supply separately as categories. Note that human labor for manufacturing, assembly, maintenance, and operation is one of the input types.		===Input/Output Model===

	* '''Functional Block Diagrams''' - These display the ~~component parts of a system from a functional perspective~~. ~~In other words, what does it do? It also shows the flows between the parts of information~~, ~~matter~~, ~~energy~~, ~~labor~~, etc. ~~A given function can be satisfied by one or more designs, which are optimized according to the goals and requirements~~ of ~~the project~~. ~~A complex system~~ is ~~too hard~~ to ~~design~~ as a whole. ~~By breaking it down into smaller components~~, ~~you reach~~ a ~~level that can be designed~~ in ~~practice. Then by summing~~ the ~~component functions, you can find~~ the ~~total inputs and outputs.~~ ~~Functional analysis is~~ a ~~continuing task done incrementally~~, ~~rather than done once with a static product~~. ~~A change~~ in ~~any one component~~, ~~such~~ as ~~an new design~~, ~~can be examined to see the impact on~~ the ~~system as a whole~~.		This can be visualized as a spreadsheet with various machines in the GVCS as columns, and inputs and outputs as rows. Each machine requires inputs such as steel, lubricants, assembly labor, fuel, etc. It also produces some kind of output. The purpose of a model is to see if your system as a whole has closure and balance. In other words, are all the inputs matched by outputs? Are there missing machine types identified by missing inputs? Is the size or quantity of a particular machine in the kit the correct size/productivity? Will the system as a whole produce a surplus, and if so how much? These are really all questions of accounting. Rather than counting everything in money, this type of spreadsheet does the accounting of each type of input/output/resource/supply separately as categories. Note that human labor for manufacturing, assembly, maintenance, and operation is one of the input types.

	Here is an early example ~~which needs more work:~~		===Functional Block Diagrams===

			A complex system is too hard to design as a whole. By breaking it down into smaller components, you reach a level that can be designed in practice. Functional block diagrams are a way to display the component parts of a system from a functional perspective. In other words, what does it do? It also shows the flows among the parts of the system with each other, and also with the external environment. In other words, how does it interact? Flows can contain any sort of item, including information, matter, energy, labor, etc, or a combination thereof.

			A given function can be satisfied by one or more designs, which are evaluated and optimized according to the goals and requirements of the project. Choosing among alternative designs should be done via objective evaluation against a set of numerical measures, i.e. a scoring system. The measures should be derived directly from the project goals and requirements and applied consistently across the whole system.

			A system that is too complex to design as a whole is also too complex to display as a whole on a single diagram. Therefore the block diagrams are broken up into multiple pages for the purpose of manageable display, but the system is still a single interconnected whole. Flows, function boxes, and pages are given unique numbers so that people can trace from one page to the next. A box or arrow at one level becomes enlarged into a page at the lower, more detailed level and keeps the identical number. Notes are added as needed to describe the functions and flows. Diagrams should fit on a single page each. Notes which overflow the diagram page go on additional pages labeled with the same number + a following A,B,C,...

			===Connecting Block Diagrams and Input/Output Models===

			Functional analysis is a continuing task done incrementally, rather than done once with a static product. A change in any one component, such as a new design, can be examined to see the impact on the system as a whole. By summing the flows of the component functions in an input/output model spreadsheet, you can find the total inputs and outputs. Using the same numbering system for both maintains the relationship between them.

			Here is an early example of the top level block diagram, showing the Global Village system as a single box. Some of the flows from the environment are shown. Environment is meant in the technical sense of "the rest of the world outside the system".

	[[File:Block_Diagram_0.0_Environment_V0.1.jpg]]		[[File:Block_Diagram_0.0_Environment_V0.1.jpg]]

Syk0 saje at 17:14, 1 May 2011

2011-05-01T17:14:32Z

← Older revision		Revision as of 17:14, 1 May 2011
Line 1:		Line 1:
	~~'''NOTE: Page is an early draft~~ under construction ~~as of 30 Apr 2011'''~~		{{under construction}}

	[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.		[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.

Syk0 saje at 17:14, 1 May 2011

2011-05-01T17:14:13Z

← Older revision		Revision as of 17:14, 1 May 2011
Line 1:		Line 1:
	'''NOTE: Page is an early draft under construction as of 30 Apr 2011'''		'''NOTE: Page is an early draft under construction as of 30 Apr 2011'''

	[[Systems ~~engineering~~]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.		[[Systems Engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.

	The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is in development, but will cover some of the basics of Systems Engineering as it can be applied to the GVCS, and point to further references for people who want more depth on the subject.		The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is in development, but will cover some of the basics of Systems Engineering as it can be applied to the GVCS, and point to further references for people who want more depth on the subject.

Syk0 saje at 17:13, 1 May 2011

2011-05-01T17:13:30Z

← Older revision		Revision as of 17:13, 1 May 2011
Line 1:		Line 1:
	'''NOTE: Page is an early draft under construction as of 30 Apr 2011'''		'''NOTE: Page is an early draft under construction as of 30 Apr 2011'''

	Systems engineering is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.		[[Systems engineering]] is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management.

	The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is in development, but will cover some of the basics of Systems Engineering as it can be applied to the GVCS, and point to further references for people who want more depth on the subject.		The GVCS qualifies as a "complex engineering project", and can therefore benefit from applying this engineering discipline/specialty. This page is in development, but will cover some of the basics of Systems Engineering as it can be applied to the GVCS, and point to further references for people who want more depth on the subject.

DanielRavenNest at 15:57, 1 May 2011

2011-05-01T15:57:38Z

@@ Line 1: / Line 1: @@
 '''NOTE: Page is an early draft under construction as of 30 Apr 2011'''
@@ Line 27: / Line 26: @@
 [[File:Block_Diagram_0.0_Environment_V0.1.jpg]]
 ==References==