THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: April 23, 2003 04:05 PM Wednesday; Rod Welch

Telecon with Gary on record of TEM on 030415 for combat project.

1...Summary/Objective
.....9...PERL is proving to be a big plus for SDS support.


..............
Click here to comment!

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

SUBJECTS
Reviewed Gary's SDS Record on 030415 First Day of Meetings

0403 -
0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 12 0000, ref SDS 10 KT5M.
040502 -
040503 - We reviewed following from initial analysis on 030421. ref SDS 12 KX6H
040504 -
040505 -     1.  The record looks good so far; key milestone is to get initial
040506 -         record for all three meetings. ref SDS 12 L86L
040507 -
040508 -     2.  Attendees need not be listed in contacts.
040509 -
040510 -            Gary decided to make this a separate file and link to it
040511 -            instead of putting everyone in Contacts.  This sounds
040512 -            reasonable.
040514 -          ..
040515 -     3.  Need heading for "Discussion" or possibly "Administration"
040516 -         that separates some of the house keeping stuff, and to create
040517 -         a field for a narrative that will be constructed when the
040518 -         record is completed that summarizes what was done in a story
040519 -         linked to the details.
040521 -          ..
040522 -         Gary's record has a major heading for Administration,
040523 -         ref SDS 7 QS4O, but not for Discussion, so it is not really
040524 -         clear where the actual talking starts, although the
040525 -         description of Agenda is likely the location. ref SDS 7 6R6K
040527 -          ..
040528 -         When people start talking, need heading for "Discussion"
040529 -
040531 -          ..
040532 -     4.  The Agenda seems to be listed in References, which is good,
040533 -         but there is no sense in the record of how it is applied,
040534 -         i.e., there is no evident correlation in the language of the
040535 -         record to the agenda, but I have only briefly glanced at it so
040536 -         far.
040538 -          ..
040539 -         One way to make both the agenda and Powerpont subjects evident
040540 -         is to incorporate the langauge in headlines.  Maybe I can work
040541 -         on this.  Gary related that right now he is concentrating on
040542 -         pulling together a good record on how the discussion related
040543 -         to objectives, requirements and commitments, and that is
040544 -         definitely the first priority, as shown on 001219. ref SDS 4
040545 -         4W4L
040546 -
040548 -          ..
040549 -     5.  Record segments are introduced based on the powerpoint file
040550 -         structures; need subject indexes for agenda and the
040551 -         powerpoint files.
040553 -          ..
040554 -         Gary asked about progress on converting subjects from initial
040555 -         account structure for combat, 04 00001, to the project structure
040556 -         set up for 03 00101.
040558 -          ..
040559 -         Advised this has been slow, but will get more done today and
040560 -         tomorrow.  He said there is not a rush.  I should get cracking
040561 -         though so there is a foundational structure in place for
040562 -         growing the garden of knowledge on this thing.
040564 -          ..
040565 -         We did not take time for this today, but, per analysis on
040566 -         030421, ref SDS 11 5G6J, Gary and I should talk and coordinate
040567 -         on where he is putting the Powerpont files.  My initial effort
040568 -         on 030420 was to put the Powerpoint files as documents in a
040569 -         directory for the meeting itself. ref SDS 9 BS5O  Gary's idea
040570 -         seems better to treat them as "received" documents.
040572 -          ..
040573 -         Gary's record for 030415 shows for Other Files three....
040574 -
040575 -            F: 03 00101 60 03 04 1501         Technical Exchange Meeting (TEM)
040576 -            F: 03 00101 60 03 04 1502         Technical Exchange Meeting (TEM)
040577 -            F: 03 00101 60 03 04 1503         Technical Exchange Meeting (TEM)
040578 -            F: 03 00101 60 03 04 1504         Technical Exchange Meeting (TEM)
040580 -          ..
040581 -         Gary explained the names of the files are all the same because
040582 -         the same subject was assigned to all of them.
040584 -          ..
040585 -         We need some differentiation of file descriptions so the user
040586 -         can tell at a glance how they are different.  This could be
040587 -         done at SI level, but not essential.  Just edit the
040588 -         description.
040590 -          ..
040591 -         These seem to be three different Powerpont files that are
040592 -         located based on the structure for formal correspondence.
040594 -          ..
040595 -         What about making them formal correspondence, rather than
040596 -         Other Files, since they were received or presented by specific
040597 -         people?
040598 -
040599 -             We can horse around with this later, but needs more
040600 -             thought.
040602 -          ..
040603 -         During our call we decided not to spend a lot of time this
040604 -         week to sort out such issues, so that focus stays on getting
040605 -         the records into shape for distribution.  That is priority.
040607 -          ..
040608 -     6.  Lessons learned, Gary wants to organize the record to pull a
040609 -         report on lessons learned.
040610 -
040611 -             This is a good idea.  Everything in SDS is organized as a
040612 -             "case study."  One approach is to make lessons learned a
040613 -             Function, and then it can be assembled based on specific
040614 -             subjects, i.e., lessons learned in legal practice, medical
040615 -             practice, engineering, on the  combat project, etc., to any
040616 -             degree of detail desired.
040617 -
040618 -                [On 040102 Gary raises idea of handling lessons learned
040619 -                like action items. ref SDS 14 A15M
040621 -              ..
040622 -             He is flagging this kind of material now in the record for
040623 -             TEM on 030415, e.g., ref SDS 7 6Q7K,
040625 -              ..
040626 -             We could create a special report system for lessons
040627 -             learned that complements the report on Action Items that
040628 -             supports periodic review meetings.
040629 -
040630 -                [On 040102 added new subject for lessons learned that
040631 -                may facilitate getting a report. ref SDS 14 PY9L
040632 -
040634 -          ..
040635 -     7.  Need links showing correlation between discussions at
040636 -         different times that refer back to other comments.
040638 -          ..
040639 -         Gary noted he is doing this where needed, an example is shown
040640 -         on the discussion concerning Kent Brookins, ref SDS 7 ZZ7K;
040641 -         and there is another one. ref SDS 7 6Q6K
040642 -
040643 -              Examples showing the process of "connecting the dots" to
040644 -              understand cause and effect, to verify accuracy and
040645 -              maintain alignment can be seen from the record of
040646 -              meetings at SRI in 2000 that support the OHS/DKR project,
040647 -              listed on 001017. ref SDS 3 1575
040649 -          ..
040650 -     8.  Coherence is not clear on problems, opportunities and action
040651 -         items flagged for follow up by specific individuals and
040652 -         organizations.  Sometimes dependencies are discussed.  This
040653 -         may be evident to attendees.  For others who did not attend,
040654 -         the story may need to be fleshed out in some places.
040655 -
040656 -             [On 030508 Gary's record of CS Staff meeting shows a lot
040657 -             of improvemnt. ref SDS 13 0001
040659 -              ..
040660 -             [On 040102 annual review cites progress using SDS for Com
040661 -             Metrics. ref SDS 14 529F
040663 -          ..
040664 -         Headlines and record segments help with this by summarizing
040665 -         the story in relation to objectives.
040667 -          ..
040668 -         Part of this issue relates to "style," where I favor a "story"
040669 -         narrative format, illustrated by the meeting with USACE on
040670 -         970320, ref SDS 1 3851, at SRI for the OHS/DKR project on
040671 -         000324, ref SDS 2 0001, and with Pat Lincoln on 010517,
040672 -         ref SDS 5 4Q5I  Gary is using a format that is familiar to
040673 -         Aerospace company for major projects.
040674 -
040675 -             [On 030508 discussed this again. ref SDS 13 FC6O
040677 -              ..
040678 -             [On 040102 Gary making progress adding headlines, and
040679 -             working on integrating record segments into his work
040680 -             practice using SDS for Communication Metrics. ref SDS 14
040681 -             UM5I
040683 -          ..
040684 -         Adding some outline structure using indents to visually show
040685 -         when the narrative changes, or when subsidiary and support
040686 -         information is provided may help.
040688 -          ..
040689 -         Seems like the record for each day should be summarized to
040690 -         explain accomplishments in relation to objectives, similar to
040691 -         the record on 020729. ref SDS 6 0001
040692 -
040693 -             [On 040102 progress on this part of Communication Metrics
040694 -             has been slow to develop. ref SDS 14 UM5I
040695 -
040696 -
040697 -
040698 -
040699 -
040700 -
0408 -

SUBJECTS
PERL Script Convert Powerpoint Files Converted to Text with Anchors f
PERL Script Improve SDS Created New Directory c: 01 05

0604 -
060501 -          ..
060502 -     9.  PERL is proving to be a big plus for SDS support.
060503 -
060504 -         This provides another method for developing support tools, as
060505 -         Gary has demonstrated with ws_ftp clean up and now with
060506 -         formatting Powerpoint files for incorporation into the SDS
060507 -         record.  Medit and PERL are complementary methods for
060508 -         continuing to experiment and devleop SDS capabilities in the
060509 -         current mode, per analysis on 030421. ref SDS 10 AF8I
060510 -
060511 -
060512 -
060513 -
060514 -
060515 -
060516 -
060517 -
0606 -
Distribution. . . . See "CONTACTS"





























NT>