Simple Video about system maps

This is a short video which explains how and why to create a systems map from the connections made between indicators at GINManila2012

Influence diagrams for Business

Format for an influence diagram

Purpose

An influence diagram represents the main structural features of a situation and the important relationships that exist among them. It presents an overview of areas of activity or organizational and other groupings and their main interrelationships. It is used either to explore those interrelationships, perhaps leading to a regrouping and redefinition of the system and its components, or to express a broad view of how things are in the territory you are considering. Influence diagrams can be developed from a systems map by adding arrows and can be used as the starting point for a multiple cause diagram by clearer definition of the type of influence.

Elements:

• blobs of varying sizes;
• assorted arrows;
• words labelling blobs and possibly also labelling arrows;
• key for arrows;
• title.

Conventions

1. As in systems maps, blob lines represent component boundaries. Inclusion of blobs and a system boundary is optional but highly recommended.
2. An arrow (e.g. 1 or 2 in the figure above) joining component aaa to component bbb or ccc shows that aaa can or does influence bbb or ccc.
3. A double-headed arrow (e.g. 3) should never be used to denote a two-way influence unless the influence is identical. Two separate arrows (e.g. 4) are preferable (see guideline 5).
4. Words (e.g. aaa, bbb, ccc, ddd, etc.) label components and system (if shown). They may also label arrows, if the nature of the influence is not obvious from the context. Alternatively, different influence can be represented by dotted (e.g. 5) or bold (e.g. 6) lines as long as a key is given.
5. Arrows do not show material flows.
6. An influence diagram, like a systems map, is a snapshot.
7. Arrows denote capacity to influence, not a sequence in time.
8. A title defining the system of interest is essential.

Guidelines

1. Avoid using arrows from features in the environment to the system boundary. By definition factors in the environment affect the system, so such arrows are superfluous. Arrows from environmental factors should terminate at a specific system component where possible. Arrows to the system boundary carry information only if they distinguish different types of influence (see guideline 3 below).
2. Different thicknesses of lines can indicate different strengths of influence. Thus in the figure above, 6 denotes a stronger influence than 1.
3. It is possible to distinguish different types of influence (e.g. influence via finance, information, supply of materials). Do so only if such distinctions are important and not self-evident, by the use of different lines (colour, dashing) to show this, and a key to explain them.
4. Resist the temptation to overload the diagram with information. It may be helpful to you to put down all influences you can think of at first, but for communication to others, select the significant ones.
5. Resist the temptation to use double headed arrows. Use them only when the influence is truly reciprocal and of the same type. If you are not careful the use of a double headed arrow can obscure important differences in the types of influence and their magnitude, which is seldom, if ever, equal. Use two arrows pointing in opposite directions instead.
6. Space and relative distance can also be used to suggest things about the nature of the relationships shown, e.g. an important but remote relationship.

Examples for Influence Diagrams:

An interconnections, interoperability and communication between components on a Systems Map

Content Source: http://systems.open.ac.uk/materials/T552/pages/influence/influenceAppendix.html
Image Source: http://www.mbanotes.org/files/Slide1_6.jpg

Systems maps guidelines for Business

Format for a systems map

Purpose

A systems map is essentially a snapshot. It shows components of the system and environment at a point in time. Unless some components are grouped into sub-systems and/or there are significant overlaps, a map conveys no more information than a list of components. But it carries much more impact, and is easier to grasp.

The main uses of systems maps are to help you to decide how you are going to structure a situation and to communicate to others just what system you have chosen to study. In particular, systems maps are used to:

• clarify thoughts at an early stage of analysis;
• decide upon structural elements for a more detailed diagram;
• experiment with trial boundaries;
• decide upon the level of your system of interest (focusing);
• communicate to others the basic structure of the system you are describing.

Elements:

• blobs of varying sizes;
• words;
• title.

(Note linking lines, arrows etc. are not permitted elements.)

Conventions

1. The blob lines in the figure above represent boundaries of system components.
2. Words (e.g. aaa, bbb, ccc, ddd, etc.) are used to name each system or component.
3. Blobs (5 and 6) outside the main system boundary (1) represent components of the environment.
4. Blobs (2, 3 and 4) inside the system boundary represent components of the system. Components (e.g. 3) can be shown as grouped into sub-systems (2). Undifferentiated components may themselves be sub-systems.
5. Blobs may overlap only if some components (which need not be depicted) are seen as common to both in the early stages of identifying a system of interest.
6. A title defining the system of interest is essential.

Guidelines

1. It should be clear which is the system boundary. The system boundary can be emphasized by colour, or by a thicker line. A dashed line can be used to emphasize that the boundary is subjective and tentative.
2. Irregular blobs are normally preferable to regular boxes. Boxes imply that (sub-)systems are clearly defined, which is seldom the case, and have the practical disadvantage that the eye finds it hard to distinguish between a series of parallel lines.
3. Use overlaps sparingly. They reduce the impact and clarity of the map when trying to establish a system of interest. Overlap only when the sharing of components is important from your particular viewpoint or when you are still uncertain as to where a component should lie. This applies equally to components within and spanning the boundary. Multiple overlaps should be avoided at all costs as this goes against the aim of clearly identifying a system of interest.
4. Aim for consistency between components. For example, avoid representing system properties as elements.
5. Although the size of blob used is not determined by size, importance, or other characteristics of the component that it represents, it makes sense to show important sub-systems at a reasonable size and less important ones somewhat smaller, as this is the way relative size is likely to be interpreted by a reader.
6. Similarly, although there are no firm rules on positioning of components (other than nesting and overlapping) it makes sense to put important components in a fairly central position and to place related components close together. This will facilitate subsequent additions of sub-system boundaries.
7. It is a good idea to leave some space within your map. Not only does this allow components to stand out clearly, but it leaves room for any components you may wish to add later.
8. Partitioning within a blob (6) is to be avoided unless fff and ggg contain all possible members of hhh and this fact is important. Normally blobs within blobs are preferable to partitions.

Examples for System maps :

The purpose of systems map is to show a decompositional breakdown between a system and its layers of subsystems.

Content Source: http://systems.open.ac.uk/materials/T552/pages/system/systemAppendix.html
Image Source:http://www.mbanotes.org/files/Slide1_5.jpg