OIT/OIR KICKOFF MEETING

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP91B00060R000100280008-7
• Release Decision: RIPPUB
• Original Classification: U
• Document Page Count: 8
• Document Creation Date: December 27, 2016
• Document Release Date: April 15, 2013
• Sequence Number: 8
• Publication Date: June 14, 1988
• Content Type: MEMO

Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
MEMORANDUM FOR: Edward J. Maloney
14 June 1988
STAT
FROM:
SUBJECT:
OIT/OIR Kickoff Meeting
Ed, in preparing the following list of topics to be included in an
OIT/OIR Memorandum of Agreement, the Group Chiefs and I have made
two basic assumptions: 1) OIR and/or the DI expects (not
necessarily wants) OIT to continue to performs its traditional
role with regard to operations, hardware planning & acquisition,
operating system software and licensing, etc. and, 2) The new
Program Management Division within OIR will perform for the SAFE
program essentially the same functions now done by CSPO. Even if
these two assumptions are correct, we still have some major issues
which need resolution via negotiation. We all believe that a
clear delineation of roles and responsibilities between the
respective Offices is mandatory so that every issue does not
require front office involvement to resolve. What follows is a
summary list of topics which we feel should be covered in an MOA.
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
o Initial Agreement to transfer 15 OIT position to OIR
-Should PD/CAB slots (circa 6) be included as they are in direct
support of SAFE?
o Will the Position Service Designation always remain MZ?
o Are people assigned or rotated to these positions?
o Is an individual rotational assignment agreement necessary or will
MOA suffice?
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
ADMINISTRATIVE - INTERNAL USE ONLY
o OIT has agreed to carry OIR software development contracts for
one year.
- One competitive procurement for SE/SI -- 84,000 manhours for 14 mos
- One Sole Source to INFODATA -- Inquire support
- One Sole Source to LOGICON -- Del 3 Maintenance and Site Support
- One Sole Source to TRW -- System Testing
- One Sole Source to HADRON -- SAFE Training
o Rumor has it that OIR is willing to give OIT 2-3 positions so
the OIT contracts team can handle OIR contracts forever.
o OG/RAMS will continue to provide computer hardware/licensing
acquistion support
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
o OIT will continue to operate and maintain all SAFE systems including
VMU
o OIT will continue to provide 24-hour support for SAFE in the Data
Base Control Center (DBCC). OIR needs to provide some $$ to
improve Operations support.
o The Operations Scheduling Panel (OSP) will continue as is with
the same responsibilities. OIR will provide a representative
replacing the current CSPO representative as soon as the OIR
SAFE Program Office is active.
o OIT will retain control over space in all OIT centers. OG/TSD
is the responsible component within OIT.
o OIR must commit to capping on-line DASD growth.
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
o OIT will remain responsible for SAFE's telecommunications support.
This support should be merged in with the standard telecommunications
support function rather than keeping it separate. This is especially
true when VMU becomes a classified system with KG-84's.
o OIT and OIR must agree on a plan to classify VMU.
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
o OIT remains responsible for all operating systems and AIM. This
includes installation, maintenance, configuration (i.e. what runs
where).
o OIT remains responsible for Systems Performance Measurement. OIT
will perform SAFE applications performance measurement for additional
$$ or slots from OIR.
o OIT requires funding for AIM Performance Enhancements, AIM SSI
Phase 3, and the AIM Applications Program Interface (API).
o OIR must commit to fund and develop the Applications side of the AIM API.
o OIT will be responsible for the development and maintenance of
the SAFE Terminal Manager which will become part of the AIM
configuration.
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
o Future Plans -- OIT will make system level decisions regarding
all applications currenly running or planned for the OIT Network as
OIT is responsible for the health and end-to-end levels of service on
the Network. With regard to SAFE, OIT definitely needs a review role
and/or veto power. Consulting goes without saying. What is at issue
here is the degree of OIT involvement. This is the tough one!
o OIT is committed to performance enhancements and maintaining/improving
level of service standards--OIR must commit to performance enhancements
on the SAFE applications side.
o OIT must maintain currency of Operating Systems and AIM -- OIR must
commit to keep SAFE software as current as the Operating System.
(VM/XA is a good example).
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
 Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7
STAT
STAT
o Configuration Management -- Whole series of boards (CCB, ERB, ORB)
in existence -- Need to develop a board structure with fair and
equitable representation for all concerned parties.
o OIR SE/SI Contract plus new Program Management Division totals about
60+ people. OIT does not have the resources to match or feed a
program structure of that size. What is expected?
o D1 to D3 Transition -- Who is in charge? Can't earnestly transition
from D1 to D3 if D3 can't support its current population.
ADMINISTRATIVE - INTERNAL USE ONLY
Declassified in Part - Sanitized Copy Approved for Release 2013/04/15: CIA-RDP91 B00060R000100280008-7