OS LONG RANGE PLANNING GROUP MEETING - 25 JULY 1969

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP83B00823R000600260061-7
• Release Decision: RIPPUB
• Original Classification: S
• Document Page Count: 3
• Document Creation Date: December 9, 2016
• Document Release Date: March 14, 2000
• Sequence Number: 61
• Publication Date: July 31, 1969
• Content Type: MFR

Approved For Releas00/09/02 : CIA-RDP83B00823R00060061-7
31 July 1969
SUBJECT: OS Long Range Planning Group Meeting - 25 July 1969
MEMORANDUM FOR THE RECORD:
in the OS Conference Room. In attendance were:
Planning Group held between 1430 and 1550 hours on 25 July 1969
1. The undersigned attended a meeting of'the OS Long Range
2. . The bulk of the meeting was taken, up with another review
.of the proposed Career Continuity Record Form. At the suggestion
of different members, ' several changes were made in the form.
on the IBM 360/67 has the following fields:
11
3. Prior to the close of the 'meeting, the undersigned reported
on his initial efforts with reference to. identifying possible methods
of computerizing the proposed Career Continuity Record. He reported
that he had determined that the OCS personnel file currently programmed
SECRET
GROUP 1
Exc! ed fra;n aascmatl,
dun;radin; and
derleasNi?saflgn
 Approved For Release 9000/09/02 : CIA-RDP83B00823R00060W061-7
Employee Number . .
First Name
Last Name
Grade
Step
Date of Grade
Overtime
Service Computation Date
SJex
CIA EOD Date
OCS EOD Date
Total QSI
Date Departed from OCS
Grade of Slot
Annual Salary
Current Education
Education Sponsorship
Position Title
Date of Last Step Increase
Date of Birth
Career Designation
Violations
Contract Employee Indicator
:Reason for Leaving OCS (150 characters)
OCS Component
Education (a multiple entry field showing
degree, major & year)
Fitness Reports (a multiple entry field
showing date & rating)
Examinations (a multiple entry field
showing test type & score)
CIA Training (a multiple entry field
reflecting type & date).
.The undersigned pointed out that the above fields would not be sufficient
to handle all the data proposed for the Career Continuity Record.
specifically called attention to the memorandum forwarded to the
Director of Security by the DDS in October 1968 on this subject.
4, The undersigned also reported that about 75-80% of the data
proposed for the Career Continuity Record are already planned for
various parts of th'ystem. The undersigned also emphasized
the need for coordinating even at the proposal study level any new
systems with the Information Processing Coordinator of the DDS, He
5. The undersigned also related the possibility of developing
a file of Career Continuity Records in punch card form. This. file could
be prepared utilizing OS assets in SR&:CD, and manipulated computer-
wise on a'case-by-case basis with support from OCS.
6. In summary, the undersigned saw three possible alternatives
for the automation of the proposed Career Continuity Record:
a. proposing implementation of a specific system
to'satisfy OS requirements in establishing and maintaiking
SE C; F! E ; T
2
Approved For Release 2000/09/02 : CIA-RDP83B00823P,000600260061-7
 Approved For Release 1060/09/02 : CIA-RDP83B00823R00060061-7
25X1A
a Career Continuity Record on all OS professional
personnel.
25X1A ' b. dependence upon- sub systems for providing
and maintaining the data considered necessary for.A&TS
and Career Board support throw h the subsystems being
25X1A planned currently as part of thdM project, and levying
requirements inclusion of additional fields in such
~25X1A Owsubsystems to cover those data included in the
Career
1uity Record Form, but not currently planned for
'25X1A
.25X1A.
25X1A;
The undersigned pointed out that alt t .i
c. development of a Data Base within OS in punch
card format with occasional input :from OCS in the form
of sorts and selective printouts.
undersigned, would stand the best change of obtaining DDS support.
Alternative c. might possibl be approved on an interim basis pending
the implementation of
erne ive a. , in all probability,
would be difficult to obtain approval from the DDS, the IPC or
-project management. 'Alternative b. in the o info f th
. ! 7. No decisions were reached at the instant m t
1-
e l
pose
Y a to obtain approval for automation of the
file.
g ge o implementation.
11 t was recognized by him
that it ma not b
reference to the automation e? sdg wiL
planning ? indicated a desire
to determine the exact format of the record form before proceeding
to the nlannin eta f
25X1A-
Chief, Information Processing Branch
EPD/OS
SE R ;T
Approved For Release 2000/09/02 : CIA-RDP83B00823R000600260061-7