Behavior at the ground level is an incredibly important consideration for successfully meeting mission. This is what I was/am going to touch on this week. Third 'section' of the draft slide stack....
B/r K.
From: mphise-talk-bounces@xxxxxxxxxxxxxxxx on behalf of Caneva, Duane C.
Sent: Mon 3/30/2009 9:28 AM
To: [mphise-talk]
Subject: Re: [mphise-talk] the MPHISE Conference - Day-1 Panel-1 Briefing-4 - preparation
I like this as a simple explanation of complexity in systems. It is an
Army document that was used to understand the complexity of developing a
counter-insurgency program for Iraq. The challenge is in understanding
the differences in "structural complexity" and "interactive complexity".
(1) Structural complexity is based upon the number of parts in a system.
The larger the number of independent parts in a system, the greater its
structural complexity.
Structural Complexity. It is possible for a system to have many parts
and therefore great structural complexity, but to exhibit almost no
interactive complexity. Machines function this way. A microchip may have
billions of internal circuits and therefore great structural complexity,
but its responses to a wide range of inputs are entirely predictable. It
is therefore interactively simple. Similarly, an automobile driver knows
when he puts his foot on the accelerator that his vehicle, which is
constructed from thousands of parts, will go faster.
(1) Such systems demonstrate linearity, because they exhibit
proportionality, replication, additivity, and demonstrability of cause
and effect. Proportionality means that a small input leads to a small
output, a larger input to a larger output. Push down lightly on the
accelerator, the car will go slowly, but push down heavily and its speed
will increase. Replication means that the system will respond the same
way to an input under the same conditions. Replication also allows cause
and effect to be demonstrated. Thus, a driver knows that changing the
position of the accelerator causes the speed to change.
(2) Additivity means that the whole is equal to the sum of the parts.5
The additive nature of linear systems legitimizes analysis. Analysis
reduces the system into progressively smaller components in order to
determine the properties of each. In a system that exhibits little
interactive complexity, the properties of the whole system can be
understood based upon the properties of the components. The most
effective way to study such a system is systematically6 and
quantitatively using the analytical problem solving. Unfortunately, the
operational problems confronting commanders at all levels are rarely
linear.
(2) Interactive complexity is based upon the behavior of the parts and
the resulting interactions between them. The greater the freedom of
action of each individual part and the more linkages among the
components, the greater is the system's interactive complexity.
Interactive Complexity. Interactive complexity makes a system more
challenging and unpredictable than structural complexity. These systems
are non-linear because they are not proportional, replicable, or
additive, and the link between cause and effect is ambiguous. They are
inherently unstable, irregular, and inconsistent. The most complex
systems are those that are both structurally and interactively complex.
However, even a structurally simple system can be interactively complex
and therefore unpredictable. Take for example, the highly interactive
dynamics associated with a small group of friends. A system composed of
people is inherently interactively complex because people have great
freedom of action and links to many others in their society.
(1) Reductionism and analysis are not as useful with interactively
complex systems because they lose sight of the dynamics between the
components. The study of interactively complex systems must be systemic7
rather than reductionist, and qualitative rather than quantitative, and
must use different heuristic approaches rather than analytical problem
solving.
5 Thomas Czerwinski, Coping with the Bounds: Speculations on
Nonlinearity in Military Affairs (Washington, D.C.: DoD Command and
Control Research Program, 1997), pp. 8-9.
6 Systematic: A methodical process dependant on an expectation of
prescriptive cause and effect within a closed system.
7 Systemic: A holistic approach that draws from systems theory, aimed at
understanding and influencing change in an open system. Note that system
is derived from a Greek word meaning "to combine." A systemic
understanding means combining components of a system in a context and
establishing the nature of their behavior and relationships. Systemic is
not equivalent to systematic.
(2) Since warfare represents a clash between societies or cultures,
most operational problems are both structurally and interactively
complex. Several features of the current and future operational
environment have magnified the non-linear complexity inherent in all
warfare. War amongst the people has increased the number of linkages
within the operational environment, and made the freely-formed opinions
of large groups of people on all sides-to include neutrals-important to
the outcome. The media carry images and perceptions of the ongoing
operations and each action carries an implicit message. Each Soldier
thus has potential links to the members of a global audience, and
therefore his actions can "directly impact on the outcome of [a] larger
operation."8
(3) The ways that adversaries are organized add to the complexity of the
operational environment. In many cases, the adversaries are
indistinguishable from the rest of the population. Their organizations
and objectives are not just different than the regular armies of states;
they have a completely different logic, one that makes the recognition
of cultural narratives and the study of anthropology, history, and
language essential for a more complete understanding of the nature of
the conflict.
Best,
Duane
Duane C. Caneva, MD, FACEP
Director, Medical Preparedness Policy
White House Homeland Security Council
202-456-2171 (o)
202-503-5439 (c)
202-456-6024 (f)
DCaneva@xxxxxxxxxxx
-----Original Message-----
From: mphise-talk-bounces@xxxxxxxxxxxxxxxx
[mailto:mphise-talk-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Eva K. Lee
Sent: Monday, March 30, 2009 4:59 AM
To: [mphise-talk]
Subject: Re: [mphise-talk] the MPHISE Conference - Day-1 Panel-1
Briefing-4 - preparation
George, I too have the same problem, I can login with the password to
view subscription list etc, but cannot login to view the mphise-talk
Archives. Best, Eva
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Sun, 29 Mar 2009, George wrote:
> Unable to gain access to view the draft slides. Encounter a userid and
> password.
> Regards,
> George
>
> -----Original Message-----
> From: mphise-talk-bounces@xxxxxxxxxxxxxxxx
> [mailto:mphise-talk-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Peter Yim
> Sent: Saturday, March 28, 2009 10:39 AM
> To: mphise-talk
> Subject: [mphise-talk] the MPHISE Conference - Day-1 Panel-1
Briefing-4 -
> preparation
>
> Mark, Leo, Steve, Bob, Ram, Susan (and Duane),
>
>
> Further to my earlier message
> (http://ontolog.cim3.net/forum/mphise-talk/2009-03/msg00024.html#nid06
> ) ...
>
> I have just posted a strawman into the wiki, comprising a draft
> outline for our presentation and the process to get us ready for that.
> See:
>
http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE_Conference_Panel_114_Prep#
nid7
> 9W
>
> (repeating the initial post here) ...
>
> Proposed Briefing Outline: (8 content slides; max 10) (7A2)
>
> 1. cover slide (7AB)
> 2. outline (7AC)
> 3. what is an ontology? (7AD)
> 4. why are ontologies, ontological engineering, ontology-based
> standards and semantic technologies relevant to MPHISE? (7AE)
> 5. why are virtual communities of practice crucial to MPHISE? (as a
> co-evolving human-tools capability infrastructure; examples) (7AF)
> 6. what (institutions, standards, projects, communities, ...) is
> already in place that is relevant to MPHISE (7AG)
> 7. what is missing (7AH)
> 8. recommendations (7AI)
> 9. references (7AJ)
>
> Proposed process: (7A3)
>
> * review outline, tweak and adopt [All: via mailng list] (7A4)
> * (in parallel) provide input, thoughts, resources [All: via
> mailng list, wiki & shared-file workspace] (7A5)
> o suggestion: maybe everyone can send in a slide deck (or
> two) they have used before that are relevant to the needs here
> (7AK)
> * confirm partitioning and task assignments [All: via mailng list]
> (7A6)
> * LeoObrst & RamSriram puts together the draft slide deck [Leo &
> Ram] (7A7)
> o LeoObrst & RamSriram discuss and decide on how they would
> present it at the panel session [Leo & Ram: subsequent to Mon
> 2009.03.30 conference call] (7A8)
> * team review and tweaks, and finalizes slide deck [All: via Mon
> 2009.03.30 conference call] (7A9)
> * team discuss and possibly adopt positions (especially on
> contentious issues) that we may take, going into the conference
> discussion [All: via Mon 2009.03.30 conference call, as well as in
> parallel on the mailing list] (7AA)
>
> Ideas, comments, suggestions ... ?
>
> Let's use this thread and that wiki page (at:
>
http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE_Conference_Panel_114_Prep
> ) to get ready for the briefing.
>
>
> Best. =ppy
> --
>
> _________________________________________________________________
> To Post: mailto:mphise-talk@xxxxxxxxxxxxxxxx
> Msg Archives: http://ontolog.cim3.net/forum/mphise-talk/
> Community Wiki: http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE
> Community Files:
http://ontolog.cim3.net/file/community/project/mphise-talk/
> Community Portal: http://ontolog.cim3.net/wiki/
>
>
> _________________________________________________________________
> To Post: mailto:mphise-talk@xxxxxxxxxxxxxxxx
> Msg Archives: http://ontolog.cim3.net/forum/mphise-talk/
> Community Wiki: http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE
> Community Files:
http://ontolog.cim3.net/file/community/project/mphise-talk/
> Community Portal: http://ontolog.cim3.net/wiki/
>
_________________________________________________________________
To Post: mailto:mphise-talk@xxxxxxxxxxxxxxxx
Msg Archives: http://ontolog.cim3.net/forum/mphise-talk/
Community Wiki: http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE
Community Files:
http://ontolog.cim3.net/file/community/project/mphise-talk/
Community Portal: http://ontolog.cim3.net/wiki/
Mission1.pptx
Description: Mission1.pptx
_________________________________________________________________
To Post: mailto:mphise-talk@xxxxxxxxxxxxxxxx
Msg Archives: http://ontolog.cim3.net/forum/mphise-talk/
Community Wiki: http://cosine.cim3.net/cgi-bin/wiki.pl?MphISE
Community Files: http://ontolog.cim3.net/file/community/project/mphise-talk/
Community Portal: http://ontolog.cim3.net/wiki/ (01)
|