CONTACTS 

SUBJECTS
Chips, Using SDS for
Management Support
Support, Schedule Summary
Subject & Contact Reports
Report by Subject/Contact,
910523

0508 -    ..
0509 - Summary/Objective
0510 -
051001 - Finished entering the record of the meeting with Morris today,
051002 - ref SDS 1 0001
051003 -
051004 - Made a new subject to consider doing reports on the Schedule Summary.
051005 -
051006 - Loaded Morris' SDS files to cpu #4 to study his Schedule Summary.
051007 - Deleted the files for Morrie and Jeff for 1990, since these are not
051008 - likely to be needed for anything and we are running out of memory.
051009 -
051010 - Decided to delete all of their files, since they are backed up
051011 - otherwise.  This leaves 10 MB on #4, even though we Added Morris
051012 - stuff.
051013 -
051014 -
0511 -
0512 -
0513 - Analysis
0514 -
051401 - Idea
051402 -
051403 - First, doing a schedule report should be very simple to do, because
051404 - all we have to do is look at the "00" directory, except we do not
051405 - store the pointers.  Still with a single dir to examine, it should be
051406 - fast.  Will need a separate processor, but will call it from same
051407 - report screen, with a different function, or maybe just the menu.
051408 -
051409 - Another aspect of this same area, is drawing a Schedule Coordination
051410 - report, or analysing Schedule Summary for staff members to see what
051411 - they are working on and how they are doing.
051412 -
051413 -
0515 -

SUBJECTS
Chips, Using SDS for Management Support
Make new records/link records
Learning time, Create SI, Contacts DB
Convert Schedule to Diary, Conflicts
with Present Practice
Learning period/difficulty
Convert Schedule to Diary, 910523
Conflict with Existing Methods
Difficult to Understand

1612 -   ..
161201 - Follow up ref SDS 2 9009, ref SDS 2 2736.
161202 -
161203 - My general sense is that Morris has not grasped the concept of
161204 - integrated scheduling and reporting, ref SDS 2 2736.  When he meets
161205 - with a group to discuss how they are doing on things to be
161206 - accomplished in the future, he feels intuitively the data should come
161207 - from the Schedule side because it is still pending.
161208 -
161209 -    [On 911121 Morris gave up using SDS. ref SDS 3 7420, because it
161210 -    takes too much time to create links. ref SDS 3 5699
161211 -
161212 - SDS is intended to evaluate the future based on the past.
161213 -
161214 - Thus, regardless of what is in his or anyone's schedule, the issue
161215 - should be what was requested or agreed upon, and that requires looking
161216 - at the source event, which is the diary.  It should contain the needed
161217 - context and the why and wherefore to the extent it is important.
161218 -
161219 - Still it seems to me it would be helpful to have the ability to cull
161220 - from a large Schedule like Morris' particular things in the manner he
161221 - suggests, so we need the feature.  How people apply it is then up to
161222 - them.
161223 -
161224 -
161225 -
161226 -
161227 -
1613 -

SUBJECTS
Chips, Using SDS for Management Support
Learning time, Create SI, Contacts DB
Subject Index, 910906
Organizational Functions
Subject Indexing

2008 -
200801 - I believe the primary key should be "subject" because that is what
200802 - generates revenue, i.e. completing a product or some task required to
200803 - complete some aspect of a product which is the purpose of the
200804 - enterprise.
200805 -
200806 - Thus management needs to structure a subject index that reflects
200807 - specific assignments.  The level of detail can be whatever is needed,
200808 - but should be minimized to avoid blurring distinctions and causing
200809 - confusion.  This is not an easy task.  It requires careful analysis to
200810 - build a practical Subject Index, and it inevitably entails making
200811 - revisions as relationships emerge over time that were too fuzzy in the
200812 - beginning, for the reasons on 890523. ref SDS 1 SQ5L
200813 -
200814 -
200815 - Functions
200816 -
200817 - This relates to the type of activity that is performed with respect to
200818 - a particular subject.
200819 -
200820 - Making an "assignment" is a an example of an SDS function under
200821 - "Management" (code 0104).
200822 -
200823 - Another type of function is "reviewing progress" so it is possible to
200824 - separate out in SDS the part of the record that pertains only to the
200825 - making of an assignment, where it is defined and target completion
200826 - dates are given or offered.
200827 -
200828 - Thus, the Function Control Field can be used to assemble reports for
200829 - progress review meetings.
200830 -
200831 -
2009 -

SUBJECTS
Chips, Using SDS for Management Support
Contacts Data Base

2205 - Summary/Objective
2206 -
220601 - This is a third selection criteria.  Each Control Field permits
220602 - entering off screen in column 89 either an orgz or indiv contact which
220603 - can be entered automatically through the Menu Contact system, by
220604 - placing the cursor in the appropriate field.  This is intended for the
220605 - Doc Log system, but the function works just as well on the Control
220606 - Field.
220607 -
220608 - SDS permits assembling reports on the basis of subjects and
220609 - individuals, so this is another way to obtain a record of dealings
220610 - with particular individuals on particular subjects.
220611 -
220612 -
220613 -
220614 - Reports support only 2 Criteria
220615 -
220616 - At this time you can do a report on Subjects and Functions, or
220617 - Subjects and Contacts, but not Subjects, Functions and Contacts.
220618 -
220619 -
220620 -
220621 -