CONTACTS 
0201 - Boeing                                                                                                                                                             O-00000816 0505
020101 - Mr. Garold L. Johnson
020103 - Modeling and Simulation                                                                                                                                          O-00000816 0505

SUBJECTS
Technical Exchange Meeting (TEM)
Architecture and Requirements
Summary Gary Requests Comments and Suggestions on Summarizing

0505 -
0505 -    ..
0506 - Summary/Objective
0507 -
050701 - Follow up ref SDS 12 0000. ref SDS 11 0000.
050702 -
050703 - Gary wants some feedback on how to summarize the record on the TEM
050704 - held on 030417, the 3rd day, perhaps in relation to guidance on using
050705 - SDS reported in the record on 030518. ref SDS 15 XT9F
050707 -  ..
050708 - We looked at this briefly and I noticed the record seemed to be only
050709 - about 280 lines. ref SDS 12 O939  This correlated with prior
050710 - understandings that day three (3) of the meetings was shorter than the
050711 - first two.  Gary pointed out that there are 1400 lines, ref SDS 12
050712 - P863, and I was able to confirm this to establish that I have the
050713 - current record.
050715 -  ..
050716 - Told Gary I am working on something now, and so cannot get to this new
050717 - task right away.  He said that is okay.
050718 -
050720 -  ..
0508 -
0509 -
0510 - 2043
0511 -
051101 - Took a quick look through the record, beginning with Discussion,
051102 - ref SDS 12 559I, and found a lot of acronyms, somtimes three or four
051103 - in one sentence.  Sent Gary a letter asking for a list of acronyms on
051104 - the project for interpreting the record.
051105 -
051106 -     [On 030523 Gary will submit list of acronyms. ref SDS 17 0001
051108 -      ..
051109 -     [On 030526 received list of acronyms. ref SDS 18 0001
051111 -  ..
051112 - The record on TEM for 030417 seems more like a verbatim transcript of
051113 - what was said, with limited to no express direction and assignment of
051114 - responsibilities.  There is limited "intelligence" that adds value by
051115 - making the meeting productive regardless of what actually transpired,
051116 - which is a core goal of Communication Metrics, as related in POIMS,
051117 - and discussed recently on 030507, ref SDS 13 IA7H, and again on 030508
051118 - explaining an expanded methodology for "facilitating" a meeting.
051119 - ref SDS 14 PL44
051121 -  ..
051122 - None of the people who contributed during the TEM on 030417 seem to
051123 - commit to do anything, and there is not a lot of evident coordination
051124 - of the kind, that... "After so and so does x, Paul and his group will
051125 - do y, then Bruce will seek approval on z.  Once z is approved, this
051126 - will release M&S to begin work; etc., etc."  A lot of people and
051127 - organizations are said to require notice to do things, but no one was
051128 - assigned to give notice, and no one seemed to volunteer to notify and
051129 - follow up.
051131 -  ..
051132 - The record of TEM on 030417 has no headlines that organize what is
051133 - being said into multiple views based on objectives, discussed
051134 - yesterday on 030521 in a "Tip of the Day." ref SDS 16 QX48
051136 -  ..
051137 - There are no links showing alignment with authority of contracts,
051138 - specs, reports, correspondence, planning from prior records, guidance
051139 - from users, policy, procedures; everything seems ad hoc.  Surely, some
051140 - work product exists that gave rise to the meeting.
051142 -  ..
051143 - These are not criticisms of Gary, but rather reflect lack of command
051144 - and control, some of which is inherent in research work.  On the other
051145 - hand,  combat seems to be intended to produce something, and so there must
051146 - be a record on which to align current thinking and planned actions.
051148 -  ..
051149 - A key question is whether this record provides a basis for guiding
051150 - future work and communciations?
051152 -  ..
051153 - A major task holding up everything else is getting requirements from
051154 - users. ref SDS 12 IN63 and ref SDS 12 GW53
051155 -
051156 -     Is there a record on having requested requirements from specific
051157 -     people, organizations and commands in a way that users can
051158 -     respond?
051160 -      ..
051161 -     Can users be notified that work is proceeding based on estimates
051162 -     of requirements and will be adjusted based on input from users?
051163 -     ref SDS 12 XB99  Bruce says  combat can't wait for complete
051164 -     requirements. ref SDS 12 SG86
051166 -      ..
051167 -     Does recent planning on budgets and schedules imply performance of
051168 -     some estimate of requirements?  Gary was frustrated recently that
051169 -     this planning was not well supported, but possibly budgets and
051170 -     schedules can be used to pry action on requirements out of the
051171 -     system.
051172 -
051174 -  ..
051175 - Looks like the approach in the summary for 030417 is to select
051176 - specific things people say and repeat them, ref SDS 12 FG9I, per
051177 - review of TEM on 030415 shown in the record on 030519. ref SDS 15 MR8H
051178 -
051179 -     Will call Gary in the morning to touch base on this.
051180 -
051181 -
051182 -
051183 -
051184 -
051185 -
051186 -
051187 -
051188 -
051189 -
051190 -
051191 -
0512 -