PROPOSED DEVELOPMENT OF AN OFFICE OF LOGISTICS (OL) CAPABILITY FOR SYSTEMS ANALYSIS, DESIGN, AND PROGRAMMING

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP79-00498A000400050052-5
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 18
• Document Creation Date: December 12, 2016
• Document Release Date: May 8, 2002
• Sequence Number: 52
• Publication Date: January 8, 1976
• Content Type: MF

Approved For Release 2002/06/05: CIA-RDP79-00498A000 Q~, g0 2
8 JAN 1976
NORM FOR: Deputy Director for Administration
DTI/'A i egistry
2-'QO,7
Proposed Development of an Office of Logistics (OL)
Capability for Systems Analysis, Design, and.
Programing
REFERENCES . (a) Memo dtd 23 Jul 75 to DD/A fm D/L, same subject
(b) Memo dtd 30 Jun 75 to DD/A fm D/OJCS, same subject
(c) Memo dtd 22 May 75 to DD/A fin D/L, same subject
1. ActionBg~uested: This memorandum requests your approval of a
proposal. That request is contained in paragraph 3.
2. Backiround Information:
a. This memorandum constitutes a refinement and resubmission
of reference (a) proposal to reorganize Office of Logistics (OL)
ADP assets. Based on discussions between the undersigned, we have
reached an understanding regarding the development of an OL in-
house ADP systems analysis, design, and programming capability.
b. Management and organizational aspects of this proposal are
as follows:
(1) The OL ADP Staff will be established within OL. The
Staff will be responsive to tasking by the Director of Logistics
(D/L) and to technical supervision by the Director of Joint
Computer Support (D/QTCS), as described in the attachment.,
(2) The D/L will provide the positions for the Staff
which will be filled by OJCS professionals on a rotational
basis.
(3) Initially, the Staff will be comprised of six pro-
fessional positions ranging from GS-09 to GS-14 system analysts
and programmers and one GS-05 clerical.
(4) Further description of the Staff organization and its
management may be found in the attachment.
OL 6 10,001
Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
 Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
oposed Develo tt of an Office of Logistics (OL)
Capability for Systems Analysis, Design, and Programing
tab s me ADP Staff in OL as outlined in paragraph 2
c tion : Your approval is requested to proceed with
Michael J. Malanick
Director of Logistics
STATINTL
WRY E. PITZKAI'EA
Director of Joint Computer Support
Att
fL/ Jc_z. F. ? ?> 12 JAN 1 476
Approved For Release 2002/06/0: CIA-RDP79-00498A000400050052-5
 ^5 ` J LASS! F! ED
^ ,, CONFIDENTIAL".
3~
FFUI
"
- -
R
ZU
SUBJECT: (Optional) Proposed Development of an Office of Logistics (OL) Capabi,li,t~ for
O
`
Systems Analysis, Design, and Programtning
FROM:
EXTENSION
NO.
tor of Lo
istics
Di
--
g
rec
-
1206 Ames
0
DATE JAN 1Q,176 STA I
$
TO: (Officer designation, room number, and
buildin
)
DATE
?._
OFFICER'S
COMMENTS (Number each comment to shrew from whom
g
INITIALS
to whom. Draw a ine across column after each comment.)
RECEIVED
FORWARDED
t ? D/CITCS
Jack:
2E29 Hdqs.
7
'
Although we have identified
2 Mf=
ceiling positions to staff this
new function, we may have to seek
F.;
some relief on "points" for the
3. DD/A
1976
,----
positions. We have basically
7D26 Hdqs.
1 2 JA
agreed with OJCS proposal for the
-
following grade structure for the
4.
six professional positions (subject
to Pbi? review and approval , of
course).
5.
1 GS-14
1 GS-13
6.
2 GS-12
1 GS-11
,_
-
1 GS-09
7.
To put these posit-1071S on our
T/0 at these grade levels will
8.
require an additional 10 '"points"
and a slight increase in 9L
average grade, but this 'IS an
9.
entirely new function ]'-'Or OL and
I think an exception can be STAT
justified.
10.
_
____.
-----
----
i
k
h
l J
M
l
Mi
t t .
c
c
ae
.
a
an
12.
13:
14.
-
`
15
G"
.
L
R
gaanp 2
1OV06
FORM
3-62
6,10 USEDITIONSU5 [] SECRET [] CONFIDENTIAL ^ USE ONLY ^ 114CLASSIFIED
INTERNAL
USE ONLY
1:] SECRET
 Approved: For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
ME1.1C_RA'1 ~"iUM OF UNDERSTANDING
8 JAN 1976
SUBJECT: Plan for Establishing an OL ADP Staff
1. ~.~,rpose
An ADP Staff will be established within the Office of
Logistics (OL) which will:
Et. Be responsive to the requirements and priorities
of OL for the enhancement of existing, and development
of new, computer applications supporting the OL mission;
b. Be subject to the standards and technical super-
vision of the Office of Joint Computer Support (OJCS).
2. PPoo ponsibilities
The OL ADP Staff will be responsible for all. EDP develop-
ment work (from problem definition through program installation)
in support of OL. This includes:
a. ICS and CONIF maintenance and follow-on development.
b. P&PD applications.
c. "Stand--alone. applications.
a. All maintenance work for other OL ongoing or newly
developed applications, including those presently run
by the User Support Division of OJCS.
The ADP Staff will conduct an inventory and review of all OL
systems at least once a year. The review will include account-
ing information provided in the OJCS PRISI.1 reports.
Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
 Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
3. Organization and Staffing
The IMP Staff will be an organizational cc:-'i onen.t of OL.
OL will include the personnel slots as pat of CL st:aL_-:-:_complement and will budget for the salaries
slots will be filled with MZ careerists assigned .:y OJCS ~n a
rotational two year assignment. Initially, those OL employees
who are currently performing ADP work for OL will be assigned
to the ADP Staff if they are found to be qualified for tr_ans--
fer to the NZ Career Service by the MZ Career Board. OJCS will
provide qualified personnel. for the remaining professional
slots and for all slots in the future when rotations are
required. (All scheduled rotations back to OJCS will be
reviewed six months in advance to ensure that such rotation
does not adversely impact any major OL projects.)
The ADP Staff will consist initially of six professionals
ranging in grade from a junior programmer level to the Chief,
who will be a senior systems analyst/programmer at the GS-14
level.
4. Management Controls
Basically, the ADP Staff will be under the tasking direction
of the Director of Logistics, who will determine that is to
be done and when. For technical matters, the Staff will be
under the direction of the Director of Joint Computer Support,
who, through his Applications Division, will determine the,
technical manner in which the work will be accomplished.
Approved For Release 2002/06/05.: CIA:RDP79-00498A1 00400050052-5
 Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
The Director of Logistics, through his Plans and Programs
Staff, will identify the requirements to be satisfied by the
ADP Staff and assign priorities to these requirements. The
ADP Staff will perform feasibility studies and prepare project
proposals on the stated requirements in accordance with the
standards specified by OJCS. All feasibility studies and
project proposals will be reviewed for technical soundness by
the Applications Division, OJCS. Any objections of OJCS will
be corrected by the OL ADP Staff to the satisfaction of OJCS
and submitted to the user for approval. Project proposals will
be approved by the user prior to initiation of programming
tasks. New GIM applications will be evaluated by the GIM
Review Board of OJCS to determine their impact on other GIM
systems and to estimate the response time these systems will
provide when in production. OJCS will schedule new applications
into production. All work will be documented in accordance
with OJCS standards. Formal documentation will be submitted
to the Central Documentation Library maintained by OJCS.
OL will evaluate and determine the acceptability of en-
hancements and new applications developed by the OL ADP Staff
in meeting the stated requirements.
Since the ADP Staff will be responsible for all OL-related
work presently done within the Applications Division of OJCS,
a plan will be drawn up by OJCS and OL to handle the transition
of work. The plan will include all present tasks and will
cover the necessary training for the ADP Staff to assume re-
sponsibility for all applications, including GIM development
Approved For Release 2002/06/05 CIA-RDP79-00498A000400050052-5
 Approved For Release 2002/06/05 : CIA-RDP79-00498A000400050052-5
and maintenance. A joint implementation plan will be developed
for management purposes to track the progress of the
5. Performance Evaluation
Fitness reports for the Chief of the OL ADP Staff will
be prepared by OL and reviewed by OJCS. Fitness reports for
the ADP Staff members will be prepared by the Chief, OL ADP
Staff and reviewed by OJCS.
Director cif Logistics
STATINTL
STATINTL
Director of /Joiri\t Co4uter Support
Approved For Release 2002/06/05 : CIA-RDP79-00498A0:00400050052-5
 Approved For Rai ~Q~2~4Q6//5 C r pP~ -QQ, 8 400050052-5
2 3 JUL 1975
MEMORANDUM FOR: Deputy Director for Administration
SUBJECT : Proposed Development of an Office of Logistics (OL)
Capability for Systems Analysis, Design, and
Programming
REFERENCES : (a) Memo dtd 30 Jun 75 to DD/A fr D/OJCS, same subj
(OJCS 1635-75)
(b) Memo dtd 22 May 75 to DD/A fr D/L, same subj
(DD/A 75-2525)
1. We are in receipt of a copy of reference (a) and are somewhat sur-
prised and disappointed with the comments presented to you by the Office of
Joint Computer Support (OJCS). However, we do have some points of agree-
ment which we feel should be examined:
. a. Paragraph 3 of reference (a) states, in part, ". . . customers
of OJCS can easily perceive infinite future requirements beyond the
finite support planned by OJCS. . . ." We agree, and feel that OJCS
should not be expected to perceive future requirements of users. On
the other hand, we should have learned some lessons from the past--
from the SIPS era, in particular--in that our major problem area in any
system development is communications at the system design level. A
? substantial portion of time is spent in the education of computer sys-
tem analysts in logistics systems and such communications/education
time can substantially increase the OJCS workload and draw down on
human resources. OJCS, in recognizing this communications problem, has
repeatedly requested that OL personnel with "computer background" be
assigned to the Inventory Control (ICS) and Contract Information (CONIF)
.systems. While OJCS has, in the past, established a branch devoted to
OL systems, and did develop excellent logistics programmer skills, its
current policy appears to be to discourage the development of any long-
term programmer association with a project. As an example, the last
of the ICS programmers will be reassigned to nonlogistics projects in
December; therefore, all of the enhancements to the ICS will be tasked
to programmers who are new to the ICS. Again we face a loss of time
while those programmers are indoctrinated in logistics systems.
b. Paragraph 3 also states, in addressing our proposed potential
application areas, "Most or all of these are reasonable requests, and
would help OL, but also they are low priority in the total DD/A
scheme. . . ." We are not suggesting any changes to the DD/A scheme
as we understand that scheme. Instead we-.are suggesting a planned
Approved For Q~ f9 /05 : f7~004 A 0040005~~5?-53740
i C Ids :zu.sA n
 Approved For FJ( W 0 /d6r35" 1- RJ9~&8 4 6%400050052-5
SUBJECT: Proposed Development of an Office of Logistics (OL)
Capability for Systems Analysis, Design, and
Programming
course of action which will allow OL to capture the full and effective
use of modern computer technology in the fulfillment of its Agency
mission and remove some of the burden from OJCS at the same time. We
should not be expected to limit our automation of logistics functions
only to those areas which require integration with other DD/A offices.
Most of the applications under discussion are those which involve only
OL and which would improve OL operations, We would Sioe, further, that
0+1 5_1 s _a.s.s.ig_ning._DD/A_ prior.:iti_es-unass i d o it iQut consulting
t,: h._us_i.n.g._off-ices. Unless we have misinterpreted the "DD/A scheme,"
we see ourselves as users telling OJCS what we want in the way of
systems rather than having.C tell_us what we can or cannot have.
2. The question of centralization has always been controversial, but
the advances in computer technology have been so rapid that centralization
must be subject to re-examination. The use of minicomputers, and now micro-
computers, can substantially reduce demands on OJCS while allowing the
individual components of the Agency to take advantage of the newer tech-
nologies. In any move to the newer technologies, however, we would expect
OJCS to be the focal point for current information and standards. OJCS
has, since the middle sixties, supported the indepth (4-6 months full-time)
training of both OJCS and non-OJCS personnel in programming and associated
data processing courses. To date, there have been at least 14 ADEPT courses
resulting in an estimated production of over 300 programmers within the
Agency. All of those programmers completing the ADEPT course did not return
to positions within OJCS. Many returned to their parent organizations and
continued to program applications which were not only beneficial to the
Agency but assumed a substantial workload which otherwise would have fallen
on OJCS. This is the basis for our_proposal and we do not f .el that it
ity ." Traditionally we
eDD1A conceit of fu tiona1 r pons bi
"rtialates t6_
have had personnel assigned to us, in OL slots, from the Offices of Finance,
Personnel, and Security to perform their special.ized functions on our behalf.
We see a parallel in the proposal under discussion. We are not arguing that
the slots in the proposed organization be filled by OL careerists with auto-
mated systems skills, although there would be obvious advantages in that
arrangement. What we are asking for is that the slots, whether filled by
OJCS careerist