CONTACTS 

SUBJECTS
Publish SDS Records on Aerospace company Intranet Gary Looking for Meth  s
Aerospace company Intranet Server Not Available at this Time for Distri  ting SD
Transformation to SDS Takes Time Strategy Build Experience Base Impro
Links Accessible in Meeting Notes Distribute SDS Records on Aerospace c  pany In
Steady-as-she-goes 3-layer Architecture Strategy Build Experience Bas
Customer US Army Rep Requested Documentation of Progress Reported in
SDS Distribute Record on Aerospace company Intranet Aerospace company C  tomer US Army Rep

2009 -
2009 -    ..
2010 - Summary/Objective
2011 -
201101 - Follow up ref SDS 9 0000, ref SDS 8 2T5J.
201102 -
201103 - Sent a letter to Gary confirming understandings from a call yesterday
201104 - on progress getting SDS used on  combat project.
201105 -
201106 -    1.  Subject: SDS Action Item Review at Aerospace company
201107 -        Date: Thu, 28 Aug 2003 13:30:58 -0700
201108 -        From: Rod Welch
201121 -         ..
201122 -    2.  Gary,
201123 -
201124 -        Good to hear that yesterday an Army person on the customer
201125 -        side, presumably representing the Contracting Officer under FAR
201126 -        requirements for surveillance  asked if the explanation of
201127 -        progress presented during the meeting is "documented?"  Very
201128 -        pleased to see people who are paying the bills are also making
201129 -        demands that people follow requirements for good management,
201130 -        (see for example review of FAR on 020504. ref SDS 4 AM5L
201132 -         ..
201133 -        This demonstrates further progress on changing the culture from
201134 -        information to knowledge tools and practices, which is an
201135 -        action item discussed just two days ago on 020826 using the
201136 -        3-layer architecture for empowering others to work
201137 -        intelligently without having to learn anything new. ref SDS 9
201138 -        BM8G
201140 -         ..
201141 -    3.  As I understand it, yesterday afternoon your boss, Steve,
201142 -        suddenly showed up at your desk and asked you to attend a
201143 -        meeting in order that you could brief the customer on progress,
201144 -        because you have a stronger awareness of the situation on
201145 -        project history, i.e., you have "situational awareness," more
201146 -        commonly called "knowledge," within the meaning of CFISR,
201147 -        because you have command and control of the record, as called
201148 -        out in POIMS, ref OF 6 1113, and required by CFISR, by FAR and
201149 -        by industry standards, reported for example on 950721.
201150 -        ref SDS 1 1740  Awareness that you have better command of
201151 -        project history than others was reported to Steve during a
201152 -        meeting a week earlier shown in the record on 030821, when
201153 -        Steve asked for a "history" button to improve meetings, and
201154 -        Paul Lowe noted that "Gary is the history button on the  combat
201155 -        project. ref SDS 8 NH5N  Previously, on 030730 Steve asked
201156 -        about activating the links in SDS records. ref SDS 5 TT9O
201157 -
201158 -           [On 031008 Morris commended Gary's progress using SDS to
201159 -           write up the record and noted that adding analysis improves
201160 -           memory, which is better than forgetting. ref SDS 12 KR6X
201162 -            ..
201163 -           [On 031211 Steve asks for Gary to put SDS record on company
201164 -           intranet so that access to links in the record will turn on
201165 -           the lights of "intelligence" for the team. ref SDS 13 5U6J
201166 -
201167 -            [On 040116 Steve asks Gary to restore SDS record for access
201168 -            by company and customer on the project. ref SDS 14 4L73
201170 -         ..
201171 -    4.  This shows continuing evolution on the project that presents a
201172 -        strategic opportunity. and also a critical issue for your boss,
201173 -        Steve, to review status on action items, as well as others,
201174 -        like Paul, whom you plan to brief next week, per your letter
201175 -        yesterday.
201177 -         ..
201178 -    5.  Evidently, at the behest of the customer, Steve gave a
201179 -        commitment to the brass that documentation of the project
201180 -        record would be stored on the ACE system for review by others.
201181 -        Steve should therefore be given timely notice that the record,
201182 -        which will be subject to review by the customer, has some
201183 -        pending action items.  Some of these have doubtless been
201184 -        accomplished, and others have not.  The project can put its
201185 -        best foot forward by showing in the record follow up activity
201186 -        is underway and/or scheduled to be performed on pending
201187 -        matters, in order to avoid the trap that ensnarled NASA of
201188 -        making commitments and not taking action.
201190 -  ..
201191 - This record demonstrates customers care about timely access to an
201192 - accurate record of organizational memory, answering the question
201193 - Morris asked on 000706, ref SDS 2 RX3K, and Gary asked the same
201194 - question two (2) years ago on 020217. ref SDS 3 425M
201196 -         ..
201197 -        [On 040326 Gary discusses intranet support for SDS with the
201198 -        Operations Manager, Gil. ref SDS 15 NK4O
201200 -  ..
201201 - Letter to Gary continues...
201202 -
201203 -    6.  Mention that you and Paul plan to sit down next week to check
201204 -        off some of the tasks, and to report progress on others, as
201205 -        Gary discussed on 030826. ref SDS 9 VV5I  Does Steve want to
201206 -        participate in order to have input on a matter that may come
201207 -        under scrutiny by the customer, and other elements within
201208 -        Aerospace company?
201210 -         ..
201211 -    7.  This notice gives Steve an alert about ramifications of a
201212 -        commitment he made which may not have been evident during the
201213 -        meeting yesterday.  It further positions you as having notified
201214 -        management of a core responsibility for allocating resources
201215 -        and directing the work.  If Steve attends the meeting on action
201216 -        item review, or if he elects to merely review and comment on
201217 -        the results of the meeting between you and Paul, this presents
201218 -        an opportunity to mention the Nancy Bucher initiative, per
201219 -        prior planning on 030804, ref SDS 6 N486, and discussed on
201220 -        030826. ref SDS 9 JT5O
201222 -         ..
201223 -        There was discussion on 030826 that people don't care about
201224 -        action items to accomplish commitments. ref SDS 9 M49F  Earlier
201225 -        on 030813 Gary related that people do care about meeting
201226 -        commitments. ref SDS 7 IY3J  Typically, this conflict between
201227 -        not caring generally about meeting commitments and good
201228 -        management practice to follow up on action items is resolved in
201229 -        part where personal interests are involvied, as with Steve's
201230 -        situation, per above. ref SDS 0 SF3X
201231 -
201232 -            [On 030830 Gary related that culture is changing at Aerospace company
201233 -            to care about good management when this can be accomplished
201234 -            without making any effort. ref SDS 11 WJ5N
201236 -         ..
201237 -    8.  Along the same vein you planned to notify Abacus about the
201238 -        visit from Steve a few days ago with comments on the mistaken
201239 -        publication of records on the web, also, discussed on 030826.
201240 -        ref SDS 9 VW48
201242 -         ..
201243 -    9.  Again, congratulations on good work making progress getting SDS
201244 -        records published on a Aerospace company Intranet, ACE or otherwise.  This
201245 -        will increase the value of "intelligence" being "documented"
201246 -        per request by the customer and thereby accelerate the
201247 -        awakening that enables transformation of the culture at Aerospace company
201248 -        and in the Army toward a culture of knowledge.
201250 -         ..
201251 -   10.  Rod
201252 -
201253 -
201254 -
201255 -
2013 -

SUBJECTS
Default Null Subject Account for Blank Record

2803 -
280401 -         ..
280402 -        Subject Null Account to Increase Context Management Improve Reporting
280403 -
280404 -
280405 -   11.  PS.  Thinking about providing a default subject that would come
280406 -        with every record, so that a user can get something down even
280407 -        when there is not enough time to figure out the subjects, as
280408 -        reported on 030826. ref SDS 9 VV4P  This provides a resource
280409 -        for linking to records where subjects are assigned.  Reporting
280410 -        could then expand span of attention by providing access to
280411 -        records with links to other records which were included in the
280412 -        report, because there wasn't enough time to assign subjects.
280413 -        This is an intermediate, or fall back, position.  Additionally,
280414 -        a report on the null subject would make it fast and easy to
280415 -        find records that need further work when time permits.  This
280416 -        offers a work around on the issue that stumped us the other
280417 -        day, and provides greater flexibility for allocating the
280418 -        analysts time using the eight (8) steps for Com Metrics that
280419 -        add intelligence for converting information into knowledge.
280420 -
280421 -            [On 030828 developed new scheme for default null subject
280422 -            that is always entered when a blank record is created or a
280423 -            new record segment is created. ref SDS 10 9U75
280424 -
280425 -
280426 -
280427 -
280428 -
280429 -
280430 -
280431 -
2805 -