SAFE PROJECT PLAN CONTRACT NO. 83B-805200-000 29 JULY 1983

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP85B01152R001001310002-2
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 104
• Document Creation Date: December 21, 2016
• Document Release Date: June 11, 2008
• Sequence Number: 2
• Publication Date: July 29, 1983
• Content Type: REPORT

Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2 _
o v- vr+
% No
CDRL D-002
9 A On
SAFE Project Plan
Contract No. 83B-805200-000
29 JULY 1983
Harry E. Fitzwater
Deputy Director for
Administration
CONCURRED BY
25X1
Assistant Director for
Resources and Systems
CONCURRED BY CONCURRED BY
Director o Data
Processing
APPROVED BY APPROVED BY
SAFE Project Director
Prepared By: APPROVED BY
4 OEOCVO "OC 0
6551 Loisdale Ct., Springfield, Va. 22150 Suite 800
RC/1 Government Communications Systems
ep. Ass vi r. ior
DIA Systems
25X1
Deputy SAFE Project
Director
25X1
Geodynamics Corporatioi
QA Contractor
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION
TITLE
1.
GLOSSARY OF ACRONYMS AND TERMS ......................
INTRODUCTION ........................................
viii
1-1
1.1
Purpose ............................................
1-1
1.2
Scope .............................................
1-1
1.3
Description .......................................
1-2
1.4
Assumptions and Restrictions ......................
1-3
1.5
Reference Documents ...............................
1-3
2.
PROJECT DEVELOPMENT .................................
2-1
2.1
System Objective ..................................
2-1
2.2
Technical Approach ................................
2-4
2.3
Development Approach ..............................
2-5
2.4
System Hardware ...................................
2-6
2.5
Software Development............. ..................
2-12
2.5.1
Application Software ............................
2-13
2.5.2
Operating System Software .......................
2-16
2.5.2.1
Multiple Virtual Storage (MVS) ................
2-16
2.5.2.2
Virtual Machine/System Product (VM/SP)........
2-16
2.5.2.3
Management Information System/Support
Management Facility (MIS/SMF) ................
2-17
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SECTION
SF-U-CA-G-008
29 July 1983
CDRL D-002
TITLE PAG E
2.5.2.4
Job Entry Subsystem (JES) .....................
2-17
2.5.2.5
Tape Management System ........................
2-17
2.5.2.6
Communications Processor ......................
2-18
2.5.2.7
Houston Automatic Spooling Program/Channel-
to-Channel (HASP/CTC) ........................
2-18
2.6
Integration and Test ..............................
2-18
2.6.1
Preliminary Qualification Test (PQT)............
2-19
2.6.2
Formal Qualification Testing (FQT) ..............
2-20
2.6.3
Acceptance Testing (AT) .........................
2-21
2.6.4
Operational Evaluation ..........................
2-21
2.7
Operations and Maintenance .........................
2-22
2.8
Training ..........................................
2-22
3.
PROJECT MANAGEMENT ..................................
3-1
3.1
User Organizations ................................
3-1
3.1.1
CIA Directorate of Intelligence .................
3-1
3.1.1.1
Analytic Support Group/DI .....................
3-2
3.1.2
DIA-SAFE User Group .............................
3-2
3.2
CSPO Organization and Responsibilities............
3-3
3.2.1
CSPO Project Director/Deputy Director...........
3-6
3.2.2
System Development Segment (SDS) ................
3-6
3.2.3
Quality Assurance Segment (QAS)....... ..........
3-7
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION
TITLE
3.2.4
Operational Support Segment (OSS) ...............
3-8
3.2.5
Support Staff ...................................
3-9
3.2.6
Contracting Officer .............................
3-9
3.3
CSPO Supporting Organizations and
Responsibilities .................................
3-10
3.3.1
CIA Organizations ...............................
3-10
3.3.1.1
Office of Data Processing/DA ..................
3-11
3.3.1.1.1
Engineering Division (ED/ODP) ...............
3-11
3.3.1.1.2
Systems Programming Division (SPD/ODP)......
3-11
3.3.1.1.3
Operations Division (OD/ODP) ................
3-12
3.3.1.1.4
Production Division (PD/ODP) ................
3-13
3.3.1.1.5
Customer Services Staff (CSS/ODP)...........
3-13
3.3.1.1.6
Systems Development Division/Applications
ODP ........................................
3-14
3.3.1.2
Office of Training and Education/DA...........
3-14
3.3.1.3
Office of Communications/DA ...................
3-15
3.3.1.4
Office of Security/DA ................. .........
3-15
3.3.1.5
Office of Central Reference/DI ................
3-15
3.3.1.5.1
SAFE User Representative Element (SURE)/OCR.
3-16
3.3.2
DIA Organizations ...............................
3-16
3.3.2.1
Deputy Assistant Director for Intelligence
Systems (RSD) ................................
3-16
3.3.2.2
Executive Director for DoDIIS Management
(RSM) ........................................
3-17
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION
TITLE
3.3.2.3
Executive Director for DoDIIS Engineering
(RSE) ........................................
3-17
3.3.2.4
Executive Director for DIA Systems (RSO)......
3-18
3.3.2.4.1
RSO-2 ........................:..............
3-19
3.3.2.4.2
RSO-4 .......................................
3-19
3.3.2.4.3
RSO-6 .......................................
3-20
3.3.2.5
Defense Intelligence College (AIS)............
3-20
3.3.2.6
Deputy Assistant Director for Communications
(RCM ) ........................................
3-21
3.3.2.7
Office of Security (OS)........ ... o ... o .......
3-21
3.3.2.8
Customer Support Group (CSG) ..................
3-21
3.4
CSPO Development Contractors ......................
3-22
3.4.1
TRW .............................................
3-23
3.4.2
TRW/CCA .........................................
3-24
3.4.3
CRW .............................................
3-25
3.4.4
INFODATA ........................................
3-25
3.4.5
LOGICON .........................................
3-26
3.4.6
MITRE... oo ................. .. ...................
3-26
3.4.7
ODP.............................................
3-27
3.5
CSPO Quality Assurance Contractor .................
3-28
3.5.1
Geodynamics/RCA.................................
3-28
3.6
Project Control ...................................
3-31
3.6.1
Reviews .........................................
3-32
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION
TITLE
3.6.1.1
Formal Design Reviews .........................
3-32
3.6.1.2
Management Reviews ............................
3-34
3.6.1.3
Documentation Reviews .........................
3-35
3.6.2
Tests ...........................................
3-35
3.6.3
Schedules .......................................
3-36
4.
SYSTEM DESCRIPTION ..................................
4-1
4.1
Incremental Deliveries ............................
4-1
4.1.1
SAFE Early Capability: SAFE-C, March 1983;
SAFE-D, June 1983 ..............................
4-2
4.1.2
Delivery 1: SAFE-C; SAFE-D, Fall 1983..........
4-3
4.1.3
Delivery 2: SAFE-C, November 1984 ..............
4-4
4.1.4
Delivery 3: SAFE-D, March 1985; SAFE-C,
June 1985 ......................................
4-7
4.1.5
Delivery 4: SAFE-D, August 1985................
4-9
4.1.6
Delivery 5: SAFE-C, December 1985, SAFE-D,
February 1986 ..................................
4-11
5.
RISK ASSESS14ENT AND MANAGEMENT ......................
5-1
5.1
Programmatic Risk .................................
5-2
5.1.1
Lack of Technical Definition ....................
5-3
5.1.2
Lack of Interface Definition ....................
5-4
5.1.3
Integration Risk ................................
5-4
5.1.4
Coordination of Development Efforts .............
5-5
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION
TITLE
5.2
Technical Risk ....................................
5-6
5.2.1
Database Management System Implementation.......
5-7
5.2.2
Prototyping .....................................
5-8
5.2.3
Performance Analysis ............................
5-8
5.2.4
DIA Resources ...................................
5-9
APPENDIX A
PROJECT SCHEDULES ...................................
A-1
NUMBER
TITLE
SAFE Development Schedule .........................
2-7
SAFE Hardware Configuration .......................
2-9
SAFE Hardware Configuration .......................
2-10
CSPO Organizational Structure .....................
3-4
vi
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
TABLES
NUMBER
TITLE
2-1
MVS Application Software ..........................
2-14
2-2
VM Application Software ...........................
2-15
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
GLOSSARY OF ACRONYMS AND TERMS
ADP - Automated Data Processing
AFB - Automatic File Build
AIF - Automated Intelligence File
AIM - Automatic Information Management
AIS - Defense Intelligence School
AISF - Analyst Intelligence Support functions are logical subsets of
functions that pertain to the dissemination of incoming (or
internally composed) intelligence messages and documents, and
to the creation, storage, retrieval and exchange of documen-
tary intelligence.
ASG - Analytic Support Group
AT - Acceptance Test
bpi Bits Per Inch
CCB - Configuration Control Board
CDR - Critical Design Review
CIA - Central Intelligence Agency
CM - Configuration Management
CMS - Conversational Monitor System (operator-command language
interface)
COINS - Community On-Line Information Network System
COTR - Contracting Officer's Technical Representative
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
CPC - Computer Program Component
CPCI - Computer Program Configuration Item
CRD - Central Reference Division
CSD - Communication Security Division
CSG - Customer Support Group
CSPO - Consolidated SAFE Project Office
CSRD - Consolidated SAFE Requirements Document
CSS - Customer Service Staff
CTC - Channel-to-Channel
DA - Directorate of Administration
DAP - Dissemination Analysis Process
DASD - Direct Access Storage Device
DATEX - Data Exchange
DBMS - Data Base Management System
DCI - Director of Central Intelligence
DI - Directorate of Intelligence
DIA - Defense Intelligence Agency
DIAC - Defense Intelligence Analysis Center
DIAOLS - DIA On-Line System
DIOBS - DIA Order of Battle System
DND - Domestic Networks Division
DoD - Department of Defense
DoDIIS - DoDIIS is an integrated intelligence information handling
system supporting the Unified and Specified commands, the
Services and other members of the military intelligence
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
community. Military intelligence organizations at all levels
of the comand structure provide information specific to the
needs of their parent organization. DoDIIS is the collection
of data processing systems developed and managed by these
organizations plus the interconnecting telecommunications
network.
DSSCS - Defense Special Security Communications System is responsible
for handling all codeword message traffic between the SAFE
system and AUTODIN subscribers. All communications functions
necessary to interface with AUTODIN will be performed by
DSSCS.
EC - Early Capability
ED - Engineering Division
ELINT - Electronics Intelligence
EMI - External Message Interface
FQT - Formal Qualification Test
CHIP - General Defense Intelligence Program
HASP - Houston Automatic Spooling Program
HUMINT - Human Intelligence
IC - Intelligence Community
ICD - Interface Control Document
ICDC - ICD Coordinator
IDF - Intelligence Data Files (Four DIA-unique file types)
INQUIRE - Indexed File DBMS
JCS - Joint Chiefs of Staff
JES - Job Entry Support Subsystem
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
M204 - Model 204 (Structured File) DBMS
MAP - Message Analysis Processing
MIS - Management Information System
MVS - Multiple Virtual Storage (operating system)
NFE - Network Front End
OC - Office of Communication
OCR - Office of Central Reference
OD - Operations Division
ODP - Office of Data Processing
OE - Operational Evaluation
OS - Office of Security
OSS - Operational Support Segment
OT&E - Office of Training and Education
PCTCS - Pentagon Consolidated Telecommunications Center System is
responsible for handling all GENSER message traffic between
the SAFE system and DoD network subscribers.. All communica-
tions functions necessary to interface with DoD networks will
be performed by PCTCS.
PDR - Preliminary Design Review
PERT - Project Evaluation and Review Technique
PMO - Pilot Mail Operation
PQT - Preliminary Qualification Test
QA -. Quality Assurance
QAS - Quality Assurance Segment
RCM - Deputy Assistant Director for Communications
RSD - Deputy Assistant Director for Defense Intelligence Systems
(DoDI IS )
xi
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
RSE - Executive Director for DoDIIS Engineering
RSM - Executive Director for DoDIIS Management
RSO - Executive Director for DIA Systems
SAFE - Support for the Analysts File Environment
SDR - System Design Review
SDS - System Development Segment
SEC - SAFE Early Capability
SEG - Systems Engineering Group (within SDS)
SETA - Systems Engineering Technical Assistance
SNF - Support Management Facility
SOW - Statement of Work
SPD - System Programming Division
SS - System Services
SUIM - SAFE User Interface Manual
SURE - SAFE User Representative Element
TEMPEST - Electromagnetic isolation and sanitization security measures.
Transaction Files - Transaction files logically store updates (adds,
changes, deletes) to the Central Index and Branch/Private
Index Files.
UDB - User Data Base
UIRS - User Interface Requirements Specification
VM - Virtual Memory (operating system)
VP - Director of Foreign Intelligence
V&V - Validation and Verification
WBS - Work Breakdown Structure
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION 1
IN TROD UCT ION
1.1 Purpose
The purpose of the SAFE Project Plan is to define the SAFE system in
terms of what is to be accomplished, who will perform the detailed tasks,
how all SAFE activities will be managed, and when major events are sched-
uled for completion.
1.2 Scope
The SAFE Project Plan applies to all SAFE project participants and gov-
erns the technical development, project management, testing and implemen-
tation of the incremental deliveries, and training of user and mainten-
ance personnel. The Plan defines roles, responsibilities, and interrela-
tionships for all organizational entities including a description of
project monitoring methods and controls which will be used to manage and
evaluate the progress of SAFE. The plan further describes the first five
incremental deliveries from two points of view. First, the plan summar-
izes capabilities in each incremental delivery from a high level perspec-
tive; secondly, the plan defines the development strategy for each deliv-
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
1.3 Description
The SAFE Project Plan is organized into five main sections and one appen-
dix. The first section provides an introduction to the Project Plan by
defining the purpose, scope and format of the document, to include a
listing of related SAFE documentation.
Section Two presents the SAFE system objective from a functional require-
ments viewpoint, and describes the technical approach to project develop-
ment.
Section Three contains a detailed description of the Consolidated SAFE
Project Office (CSPO), user organizations, contributing contractors, and
other organizations involved in the SAFE Project. This section also de-
scribes management responsibilities, control mechanisms and the interre-
lationships between organizations.
Section Four provides an overview of the SAFE system by describing the
system and functional capabilities included in each of the incremental
deliveries.
Section Five describes the methods for identifying and managing potential
risk areas. Risk is divided into two broad categories: programmatic risk
and technical risk. The discussion of each of the two risk categories
includes a definition of the category and an identification of associated
risk.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
Appendix A addresses the project scheduling and monitoring for project
control. Gantt charts are used to show activity milestones and time-
lines. The framework for planning, scheduling, and reviewing project
events is facilitated through use of a project management tool, PAC II,
which provides a critical path analysis. The critical path analysis will
reveal schedule sensitivities and will thus assist CSPO in optimizing
project resources.
1.4 Assumptions and Restrictions
This plan is produced by the CSPO Quality Assurance Segment and is prom-
ulgated by the Director and Deputy Director of the CSPO. Strict adher-
ence to the plan is required by all participants. Modifications to the
plan must be approved by the Director or Deputy Director of CSPO.
1.5 Reference Documents
The following documents have been approved and placed under project con-
figuration control. These documents should be referred to for additional
detail regarding specific subjects.
SF-U-CA-G-003B Quality Assurance Plan
SF-U-CA-G-001 A Configuration Management Plan
SF-U-CA-G-002A Documentation Plan
SF-U-CE-001B-01 System Requirements Specification
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SF-U -CE -720 0E -01
User Interface Requirements Specification
SF-U-NE-0070-01
Requirements Traceability Matrix
SF-U-NE-0085-01
System Design Document
SF-U-NE-0089-01
Interface Control Document
SAF-D005A/79
Consolidated SAFE Requirements Document
SF-S-DE-0011-01
Conversion Requirements Specification (Vol.
1)
SF-S-DE-0011-02
Conversion Requirements Specification (Vol.
2)
SF-U-NE-0086-01
Hardware Configuration Document
SF-U-NE -0088-01
ECA-O1
SAFE Project Conversion Plan
Early Capability Project Plan
ECD02
SAFE-C Project Early Capability Interface Specifi-
cation to External Systems
SAFE-D Project Early Capability Interface Specifi-
cation to External Systems
ECD05
Early Capability Software Definition Document
ECD10
SAFE-C Communication Plan
E CD11
SAFE-D Communication Plan
ECL03
Early Capability Software Maintenance Plan
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION 2
PROJECT DEVELOPMENT
2.1 System Objective
The purpose of SAFE is to provide the needed data processing support to
assist the intelligence analyst in coping with the myriad of sources and
large quantities of data available on given subjects.. Emphasis over the
past few years has been given to providing more coverage, increased ca-
pacity and greater sophistication to our information collection capabil-
ity. We have been so successful that in many instances the intelligence
analyst has been overwhelmed with information. SAFE will assist the ana-
lyst in the time-consuming tasks of collecting, organizing, collating,
editing and coordinating data.
To significantly improve the flow of intelligence, SAFE will provide
automatic processing and dissemination of incoming electrical messages.
Users of SAFE will develop lists of words or phrases called profiles
which will be used to direct relevant traffic to the individual or of-
fice. These user profiles may also be structured to alert the analysts
when specific intelligence data of topical sensitivity is received by
their respective agency (CIA/DIA).
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
In addition to accelerating the dissemination of electrical messages,
SAFE will provide the capability for a user to read, annotate, route (to
other analysts or offices) and index intelligence electronic documents.
SAFE will facilitate analysts' electronic communications with one another.
Individually created electronic work files will be provided. Work files
can be defined and structured by the user to meet individual data storage
and retrieval requirements. The user also can define output formats so
that data presentation at the workstation focuses attention on relevant
information.
By providing rapid communication between the managers of collection re-
sources and the intelligence analysts, SAFE will provide, for DIA, the
opportunity for more effective exploitation of collection resources.
Another major improvement to the analysts' environment provided by SAFE
will be the provision of a single access language to support the current
intelligence function as well as historical research of reference data.
On-line access to reference data will allow the SAFE user to research not
only the indexed files, structured records, order of battle files or in-
stallation files, but also to research abstracts of documents, and full
texts of electrical messages, all through a single user language. The
SAFE User Language (SUL) will provide rapid and effective query and file
maintenance across diverse data bases.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The SAFE user interface is being developed based on a model of the intel-
ligence analysts' work environment. The SAFE User Language will, allow
the user to perform background and foreground functions simultaneously,
thus improving analytical efficiency by allowing greater attention to be
paid to foreground analysis functions and less attention to background
support tasks.
Many existing DIA data bases contain data duplication, and lack data
standardization and data integrity. One of the objectives of SAFE is to
integrate intelligence data bases where feasible in an effort to optimize
on-line data base maintenance and retrieval while at the same time reduc-
ing data redundancy and the risk of data inconsistency.
Finally, SAFE will significantly improve the mechanism for producing fin-
ished intelligence. For both agencies, the user will have the capability
to compose and print finished intelligence reports. The provision for
on-line text composition will allow the user to write memoranda, arti-
cles, or reports, and then print the textual or structured data in a var-
iety of output formats. The ability to route intelligence documents
electronically to other analysts or supervisors will greatly facilitate
the coordination process and will thus serve to compress the production
cycle. In addition, the intelligence agencies will more effectively re-
spond to ad-hoc requests for information through the more efficient on-
line research, composition, and dissemination capabilities available in
SAFE.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
In summary, SAFE provides a needed set of processing tools to assist the
analyst/manager in producing finished intelligence for national level
policy makers.
2.2 Technical Approach
The fundamental precepts governing SAFE development are: maximum use of
commercial and government available off-the-shelf software packages to
satisfy SAFE requirements and incremental delivery of functional capabil-
ities to the users. SAFE will be built utilizing government furnished
IBM compatible hardware for the optimal use of applicable commercial and
government software. The technical approach is predicated on SAFE's re-
quirements bearing strong resemblance to commercial products in the areas
of data base systems, electronic mail and text processing.
SAFE's requirements cannot be fulfilled soley by these sources, therefore
software augmentations will be necessary to satisfy the total set of SAFE
requirements. Augmentations to software packages will be made only after
careful analysis of cost, schedule and technical risk, and the priority
of the requirements which drive the software augmentations. Trade-offs
will be developed in consultation with user-representatives (DIA-SAFE
Users Group; Analytical Support Group/DI) as part of the decision process.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
2.3 Development Approach
The following represents specific integration concepts/tasks necessary to
support the SAFE system development approach:
o The incremental delivery of capabilities to the users involves
the identification of software packages that provide some portion
of the SAFE functions. A software package may require augmenta-
tion to achieve the desired functional capability. In turn, a
set of packages may require integration to achieve some composite
set of capabilities for each of the respective incremental deliv-
eries. The development of each incremental delivery will be mon-
itored by CSPO's System Development and Quality Assurance Seg-
ments for adherence to the project standards and responsiveness
to requirements. Each delivery will be baselined upon acceptance
and then turned over to the Operational Support Segment.
The commercial market is expected to be active in solving many
SAFE-like problems through improved performance of hardware and
software; or through software with increased capabilities. The
incremental development approach allows continuous monitoring of
improved products and services.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
Activities generally defined as system integration encompass the
melding and testing on several levels of various pieces of soft-
ware that make up a system. These activities range from the
interweaving of small pieces of software into modules followed by
the aggregation of modules into applications and finally the or-
chestration of the applications into a system. System Integra-
tion will assure that the incremental deliverables are introduced
into the operational environment with maximum coordination and
minimal disruption.
o In the SAFE Management Approach, the System Development Segment,
with assistance from an integration support contractor, will be
responsible for system integration.
o The development phases for integrating capabilities into the SAFE
environment are shown in Figure 2-1. The diagram shows a clas-
sical software system development including the major design re-
view milestones and delivery dates in a timeline-oriented chart.
2.4 System Hardware
The hardware supporting SAFE is expected to evolve and keep pace with
expanding capabilities. The intent is to take full advantage of advances
in technology where appropriate and feasible. As the SAFE user connunity
expands, the system hardware will be upgraded. The initial SAFE system
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
0
EVENTIACTIVITY
'44ASE
SLIVERY ONE
earn S S O
-o
?Et1vEwY
CY 84
J FY. MA J A 8 O N D
?tia~
DELIVERY TWO
*Avg s
DELIVERY TM11EI
SAVE C A C
CY 83
J F M A M ,4 J A 8 0 N D
DELIVERY FOUR
SAVE S
SAFE C - ----A-
PDll
DELIVERY FIVE
SAFE C A 0
FDA - Pr?11wl..rp S..IVn Review AT - Acceptance Test - DELIVERY
can - Cr1110.1 Design Review OP - OPer.tlen.l
POT - --.Mm..rv O.,?1111e.1le. ?...
Figure 2-1 SAFE DEVELOPMENT SCHEDULE
CY 88
J FM A MJ J AS ONQ_
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
CY 88
JFMAM J.JA $ 0 N D
S's.
AT
colt POT
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CD RL D-002
hardware configuration, as described in the SAFE Hardware Configuration
Document, is viewed as three separate systems: CIA (SAFE-C), DIA
(SAFE-D) and this Development System. Figure 2-2 consists of the three
views of this SAFE hardware configuration concept. Note that the Devel-
opment System is a back-up, virtual memory system to the SAFE-D system.
The hardware configuration document identifies the projected configura-
tion for each delivery subsequent to the SAFE Early Capability.
a) SAFE-C SYSTEM
The initial hardware configuration for the SAFE-C system consists
of three IBM 3083 model J processors. All three processors are
used for production with two operating under control of the MVS
operating system and one operating under the control of the VM
operating system. One of the MVS processors also serves as the
back-up VM machine. An IBM 3211 printer is switchable to any of
the processors. The processors share access to a pool of eight
IBM 3420 tape drives (6250/1600 BPI) through four IBM 3803 con-
trollers. All remote communications facilities are provided
through three COMTEN 3690 front-end processors, each with dedica-
ted interfaces to each of the 3083 processors. The SAFE-C pro-
cessors share the access to thirteen IBM 3380 direct access stor-
age systems with a total of 32.5 gigabytes, sixteen IBM 3350 Di-
rect Access Storage Devices (DASD) with a total of 9.6 gigabytes,
and two STC 4305 solid state drum systems, each with 45 megabytes.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CD RL D-002
COMB
PERIPHERALS
(TAPES. DISKS.
PRINTERS.
OPERATOR
Cold")
PERIPHERAL
SWITCHING NETWORK
Is"
3083) PROCESSOR
(MIS)
3083) PROCESSOR
C+w1
Im
3083) PROCESSOR
(MS/8ACKIW)
Comm
SWITCH
Cop TER
SWITCH
TERMINAL
NETWORK
TERMINALS
CONTEN
SWITCH
Figure 2-2 SAFE HARDWARE CONFIGURATION
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
COMPUTER
PERIPHERALS
(TAPES. DISKS.
PRINTERS.
OPERATOR
CON50LES)
PERIPHERAL
SNITCHING NETWORK
IMP
3013.( PROCESSOR
ION
30831(N)PROCESSOR
ISOLATED
(VP BACKUP)
SYSTEM
TO SAFE-0
PERIPHERAL
EOUIPHENT
SWITCHING
NETWORK
TO .
SAFE-D
COIMINICATIONS
SWITCHING
NETWORK
CMI
SNITCH
COREN
SWITCH
TERMPINAL
SWITCH NETWORK
(TEIH.ALS
Figure 2-2 SAFE HARDWARE CONFIGURATION
COIWUTEN
PERIPHERALS
(TAPES.DISKS.
PRINTERS.
OPERATOR
CONSOLES)
11SOLATED BACKUP PROCESSOR i
Approved For Release 2008/06/11: CIA-RDP85BO1152 R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
b) SAFE-D SYSTEM
The SAFE-D system initial hardware configuration consists of two
IBM 3083 model J processors. Both processors are used for pro-
duction with one operating under control of the MVS operating
system and one operating under the control of the VM operating
system. An IBM 3211 printer is switchable with either processor,
and a pool of eight IBM 3420 tape drives (6250/1600 BPI) are ac-
cessible through two controllers. Nine IBM 3380 storage systems
with a total of 22.5 gigabytes, six IBM 3350 DASD with a total of
3.6 gigabytes, and two STC 4305 solid state drum systems with a
total of 90 megabytes are shared by the DIA processors. The re-
mote communications facilities are provided through two COP?1TEP!
3690 front-end processors.
c) DEVELOPMENT SYSTEM
An additional IBM 3803 model J processor initially serves both as
a DIA back-up processor and as a software development system for
both the CIA and DIA systems. This processor runs in MVS mode
under control of the VM operating system. This processor has
access to four IBM 3420-8 tape drives, seven IBM 3380 storage
systems with a total storage capacity of 17.5 gigabytes, four IBM
3350 DASDs with a total of 2.4 gigabytes, and an STC 4305 solid
state drum system with total storage capacity of 45 megabytes.
The development system utilizes the DIA front-end processors for
communication.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
2.5 Software Development
A key factor in managing the integration capabilities into the SAFE en-
vironment is the identification and control of individual software ele-
ments comprising a delivery. Standard development and configuration man-
agement policy and procedures define the Computer Program Configuration
Items (CPCIs) and the Computer Program Components (CPCs) as elements for
configuration accounting and management:
o Within the SAFE structure, CPCIs are software packages identified
by specific procurement or development specifications and are
separately testable. The definition, procurement/development,
integration and test of each CPCI will be controlled by indivi-
dual task agreements.
o Once software is completely designed, the total structure is de-
composed into smaller, modular units called Computer Program Com-
ponents. The CPCs facilitate the isolation of problems and help
to ensure that modifications and upgrades do not have unforeseen
consequences throughout the systen. Development of the CPCs can
be easily tracked and responsibilities for development can be
clearly defined. These units are the basic blocks for which code
is developed and integrated to form the completed CPCIs.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o The set of CPCIs comprising an application will be integrated and
tested within the current baseline configuration. At the comple-
tion of the integration tests, formal turnover demonstration will
be performed. Successful execution of the demonstration and
benchmarks will verify the full system operation including the
added capabilities.
2.5.1 Application Software
Application software is written to solve specific problems, generate spe-
cified reports, and/or to update designated files. SAFE applications
software includes all of the CPCI modules directly involved in supporting
the mission of SAFE. Table 2-1 lists the set of CPCIs comprising SAFE-
application software which will reside within the MVS system, while Table
2-2 lists those modules which will reside within the VM system.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
Table 2-1. MVS Application Software
MVS HOST PROCESS CPCI
Message Input (EMI)
Message Analysis
Mail
Profile Compilation
Data Base Management
Message Analysis Process (MAP)
Message Analysis Process (MAP)
Dissemination Analysis Process
(DAP)
Dissemination Analysis Process
(DAP)
o Index Files INQUIRE
o Structured Files M204
Special Output Control Data Management
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
Table 2-2. VM Application Software
VM HOST PROCESS
User Interface Process
Data Management
Message Analysis Process
(MAP)
User Data Process User Data Base (UDB)
INQUIRE
Network Communications Process System Services
Automatic Information Management
Service Process
Message Analysis Process
(MAP)
AIM Data Base
System Services
Management Information
Systems (MIS)
DoDIIS Network Interface DoDIIS Communication
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
2.5.2 Operating System Software
System software is concerned with the translation, loading, supervision,
maintenance, control, and running of computers and computer programs. A
distinction is usually made between operating system software and appli-
cation software, although this distinction is not always obvious nor
clearly defined. The operating system software supporting SAFE consists
of components of the IBM Multiple Virtual Storage (MVS) and Virtual Mem-
ory (VM) systems assisted by the Job Entry System (JES), Management In-
formation System (MIS), Support Management Facility (SMF), and a Tape
Management System (TMS). Communications switching is handled by the
NCR/COMTEN 3690 Communications Processor.
2.5.2.1 Multiple Virtual Storage (MVS)
MVS provides support for batch usage on a large virtual storage environ-
ment. MVS is a large-scale operating system, designed to handle multi-
processor configuration.
2.5.2.2 Virtual Machine/System Product (VM/SP)
VH/SP consists of the Control Program (CP) and Conversational Monitor
System (CMS) components. Each user of VM/SP has the functional equival-
ent of a real, dedicated computing system. Virtual machines and virtual
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
storage are provided with each virtual machine referring only to its own
virtual storage. This restriction protects each virtual machine's stor-
age from the activities of other virtual machines. The size of each vir-
tual storage space is defined in the virtual machine directory entry and
may differ among virtual machines.
2.5.2.3 Management Information System/Support Management Facility
(MIS/SMF)
The MIS/SMF provides timely information to the parent agencies for secur-
ity audit and operational management.
2.5.2.4 Job Entry Subsystem (JES)
The Job Entry Subsystem acts as the scheduler for computer jobs, control-
ling the time and space resources within the system. All data destined
for the system will be routed through the JES subsystem, which provides
networking protocol for machine-to-machine communications.
2.5.2.5 Tape Management System
A UCC One automated Tape Management System protects data stored on mag-
netic tape and automates functions associated with controlling and manag-
ing the tape library in OS and OS/VS installations.
2-17
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
2.5.2.6 Communications Processor
NCR/COMTEN 3690 Communications Processors provide the network control for
the on-line user community.
2.5.2.7 Houston Automatic Spooling Program/Channel-to-Channel(HASP/CTC)
The CIA currently supports the HASP protocol that communicates between
the VM and MVS processors via Comten processors using a bisynchronous
interface. This inter-machine communication facility will be replaced by
an IBM 3088 C-T-C device. The 3088 device provides a larger number of
subchannels for communication flexibility to handle all of SAFE's growth
and a much higher data rate than currently provided by the Comten bisyn-
chronous interface.
2.6 Integration and Test
For each SAFE delivery, two or more development contractors are tasked to
design, code, unit test and debug specific subsets of the software re-
quired for the delivery. These subsets of software are then formally
tested by the respective development contractors. Tests performed at
this time are designed to satisfy CSPO that the contractors have imple-
mented their design, satisfying all functional requirements included in
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
their respective tasking agreements. Integration and test of all soft-
ware for each delivery is then performed to assure compatibility of its
component parts and to assess the capability of the integrated software
to meet desired performance requirements.
The formal test milestones and Operational Evaluation are described in
the following subparagraphs.
2.6.1 Preliminary Qualification Test (PQT)
The PQT is a formal test performed by each development contractor for
each SAFE incremental delivery.
Objectives of the PQT include:
validation that the development contractor has implemented his
design to meet the functional requirements included in his task-
ing agreement for each delivery
- demonstrating readiness of the software to be integrated with
previously and/or concurrently delivered software.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
Following successful completion of the PQT, software will be placed under
control by Configuration Management (CM). Controlled copies of all soft-
ware media will be available to the system integration support contractor
only through the CM process. Test plans, procedures and reports will be
utilized by CM personnel to conduct required configuration audits.
2.6.2 Formal Qualification Testing (FQT)
The FQT is a formal test conducted by the system integration support con-
tractor after all delivery software has been integrated. The FQT plan
will be developed as a part of the Integration Plan required for each
SAFE delivery. The FQT procedure is also prepared by the system integra-
tion support contractor and will use test cases from the PQTs, modified
as needed, to reflect the presence of working interfaces between the
software component parts.
Objectives of the FQT include validation that CPCIs, as built, satisfy
all of the functional requirements specified for the delivery and that
deficiencies in interface compatability are identified and resolved. FQT
will be performed using software media compiled and certified by the CH
process. These software media will contain all approved changes imple-
mented since the conclusion of PQT. Having passed the FQT, the integra-
tion and test phase shifts in orientation toward demonstrating that the
heretofore delivered components perform under system-load conditions.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The Quality Assurance Segment assumes responsibility for testing, signi-
fying the completion of the system test phase and the beginning of the
acceptance test phase.
2.6.3 Acceptance Testing (AT)
The AT is a formal test conducted by QAS personnel following the system
test phase. The AT Plan and procedures are prepared by the Chief, QAS.
The detailed test cases will be similar to those developed for FQT with
added stress testing intended to simulate the operational environment.
Objectives of the AT are to demonstrate the readiness of the integrated
delivery software for operational use and to assess the capability of the
software to meet desired performance requirements.
The AT will be performed using software media compiled and certified by
the CM process. These software media will contain all approved changes
implemented since the conclusion of PQT.
2.6.4 Operational Evaluation
Following the Acceptance Test is a 45-day period of system operational
evaluation conducted by QAS personnel with support from the user conmun-
i ty. The object of this evaluation is to demonstrate the capability of
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
the software to perform in the actual user environment. This can be both
qualitative and quantitative.
2.7 Operations and Maintenance
Support of hardware and software for SAFE during the operational phase of
each delivery requires careful planning. Procedures currently in effect
for CIA computer operations must be reviewed by the Operations Division,
Office of Data Processing (see 3.3.1.1.3) to ensure optimum compliance
with SAFE operational requirements. An Operations and Maintenance Plan
will reflect current, applicable CIA computer operations procedures and,
as required, will detail procedures for DIA to effect an efficient
change-over to the DIA operations.
2.8 Training
SAFE training will have to be accomplished for several components; the
requirements for which differ significantly. Training will have to be
provided for CIA, for DIA, and for DoDIIS users external to DIA. Train-
ing will also have to be provided for functional users, system operators,
and maintenance personnel. The complexities and scope of the training
required precludes reliance on traditional classroom instruction or on-
the-job training. It is anticipated that SAFE training will include mo-
bile training teams, self-paced text, classroom instruction, video tape
presentations, computer aided instruction, and the SAFE system itself.
2-22
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The Chief, QAS will produce a SAFE Training Plan identifying the specif-
ics of training responsibilities; including types of courses, numbers of
trainees, locations, and type of material required. The Chief, QAS will
designate a SAFE training coordinator to work with all other project ele-
ments in defining and implementing the SAFE Training Plan.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION 3
PROJECT MANAGEMENT
3.1 User Organizations
The Consolidated SAFE Project Office, under the auspices of the CIA's
Deputy Director of Administration and the DIA's Assistant Director for
Resources and Systems, is developing the SAFE System to support the an-
alytical requirements of the intelligence analysts within the CIA, DIA
and DoDIIS. The user organizations within the respective agencies are the
CIA's Directorate of Intelligence and primarily the DIA's Directorate of
Foreign Intelligence with DIA users also in the offices of the Assistant
Vice Director for Collection Management, the Assistant Director for JCS
Support, and the Assistant Director for Resources and Systems. This sec-
tion delineates the responsibilities of these organizations.
3.1.1 CIA Directorate of Intelligence
The Directorate of Intelligence (DI) is the research, analysis, and pro-
duction element of the CIA and supports the U.S. national security policy
process by providing relevant and timely intelligence products.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.1.1.1 Analytic Support Group/DI
The Analytic Support Group (ASG) of the Directorate of Intelligence will
represent all DI users. As such, it will identify DI's SAFE require-
ments, obtain DI support for development and maintenance activities, and
serve as the point-of-contact for DI user acceptance of each incremental
delivery. ASG, in coordination with CSPO's Quality Assurance Segment,
will review and approve all implementation planning that impacts DI
users. This includes certification (via user testing) that the respec-
tive system deliveries and any future enhancements to the SAFE system are
acceptable based on the criteria specified in the QAS-developed Accep-
tance Test Plan. Desired enhancements, resulting from user experience
with the SAFE system, will be documented and prioritized by ASG and sub-
mitted to the SAFE Configuration Control Board as recommendations for
incorporation into the SAFE system.
3.1.2. DIA-SAFE User Group
The DIA SAFE Users Group will represent all DIA and DoDIIS users and will
be the point of contact for DIA user acceptance of each incremental de-
livery. In particular, in coordination with CSPO's Quality Assurance
Segment, the DIA-SAFE Users Group will review and approve all implementa-
tion planning that impacts DIA and DoDIIS users. This includes certifi-
cation (via user testing) that the respective system deliveries and any
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
future enhancements to the SAFE system are acceptable based on the cri-
teria specified in the QAS-developed Acceptance Test Plan. Desired en-
hancements, resulting from user experience with the SAFE system, will be
documented and prioritized by the DIA-SAFE Users Group and submitted to
the SAFE Configuration Control Board as recommendations for incorporation
into the SAFE system.
3.2 CSPO Organization and Responsibilities
The Consolidated SAFE Project Office is responsible for the development
and delivery of the SAFE System in accordance with the CIA and DIA user
requirements as defined and validated by each Agency in the Consolidated
SAFE Requirements Document (CSRD). This effort encompasses not only com-
mon requirements, but also those unique to each agency. The effort is
directed toward maximizing cost savings through common development, pro-
curement and service for both Agencies.
CSPO is jointly staffed by CIA and DIA, is housed within CIA facilities,
and is administratively supported by CIA. As shown in Figure 3-1, CSPO
is organized with a Project Director, Deputy Project Director, Quality
Assurance Segment, System Development Segment and Operations Support Seg-
ment. There is also a support staff and a contracting officer to handle
administrative and formal contractual matters related to SAFE.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
DEPUTY PROJECT
DIRECTOR
CONTRACTING
OFFICER
OPERATIONS
SUPPORT
SEGMENT
OUALITY
ASSURANCE
SEGMENT
ADMINISTRATIVE
SUPPORT
STAFF
SYSTEMS
DEVELOPMENT
SEGMENT
Figure 3-1. CSPO Organizational Structure
Approved For Release 2008/06/11: CIA-RDP85B0l 152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The Director and Deputy Director of CSPO have the authority and responsi-
bility to manage all aspects of the SAFE Project. Development contrac-
tors from private industry and from other government organizations exter-
nal to CSPO have been tasked to support this effort. Formal contractual
agreements (memoranda of understanding for government organizations),
backed by detailed statements of work for development contractors, will
provide the basis for CSPO control over all development contractors.
In order to effectively manage contractual tasks, the Director of CSPO
has assigned contracting officer technical representatives (COTRs) to
each development contractor. Each COTR is responsible for closely moni-
toring and reporting the status of all tasks within his assigned area.
To avoid misunderstandings and possible conflicts in day-to-day direc-
tion, the COTR will be the single point of contact for development con-
tractors on all technical issues.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.2.1 CSPO Project Director/Deputy Director
Management responsibility for the development of the SAFE System rests
with the CSPO Project Director and the CSPO Deputy Project Director.
3.2.2 System Development Segment (SDS)
The Chief of the System Development Segment is responsible for managing
the acquisition and integration of off-the-shelf software packages and
the development of software to achieve required SAFE capabilities. In
this capacity, Chief, SDS will oversee the execution of the development
contractors' project tasks required to place in operation each of the
system deliveries. A principal contractor will support the Chief, SDS in
performing the necessary engineering for software integration, user in-
terface design, testing, file conversion, software installation, appro-
priate engineering specifications and planning for the respective system
deliveries.
The Chief, SDS is responsible for identifying and evaluating available
software packages that meet SAFE requirements. Analyses will be per-
formed to determine what augmentations are required to bring the package
into compliance and when packages do not meet SAFE requirements. Users
will participate in evaluating trade-offs when required augmentations are
considered not feasible or when they impact cost and schedules.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The development of each delivery will be monitored by an SDS delivery
manager to insure adherence to project standards and responsiveness to
requirements. The delivery will subsequently be placed under configura-
tion management and turned over to the Operational Support Segment.
3.2.3 Quality Assurance Segment (QAS)
The Chief of the QAS, with support from the QA Contractor, is responsible
for administering the quality assurance program and will use contractual
support for the various quality assurance functions, to include Configur-
ation Management (CM), Validation and Verification (V&V), and System En-
gineering and Technical Assistance (SETA). The Chief of QAS is responsi-
ble for insuring that appropriate system design and software development
standards. are adhered to by SAFE Development Contractors. This segment
will maintain all software and documentation baselines. Acceptance test-
ing will be conducted to insure that the deliveries meet the requirements
baseline. The QA Contractor is responsible for defining and executing
acceptance test plans and procedures. The Chief of QAS will also main-
tain liaison with user organizations within both the CIA and the DIA.
There will be a single point of contact within the CIA and DIA for user
requirements. Areas of liaison will include training requirements, ter-
minal allocation, user feedback from operational system usage, user lan-
guage scenarios in support of interface prototyping, and the identifica-
tion of new or changed functional requirements.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
The Chief of QAS will be the executive secretary to the project's Config-
uration Control Board (CCB). The QA Contractor will provide support to
the Chief of QAS in administering the SAFE Project's CCB and executing
the SAFE Configuration Management Plan. The SAFE CCB will be chaired by
the Director of the Consolidated SAFE Project Office. The Deputy Direc-
tor of CSPO will be the Vice Chairman. The board will consist of the
Chief and Deputy Chief of the SDS, the Chief of CIA's Analytic Support
Group, the Chief of the DIA SAFE User Group, and the Quality Assurance
Segment Chief, assisted by the Quality Assurance Contractor.
The QA Contractor, will prepare and maintain a master schedule, i.e.,
Program Evaluation and Review Technique (PERT) for all project activi-
ties. Progress against the master schedule will be reported to CSPO man-
agement at least monthly, or as requested by the Project Director (see
Section 3.6).
3.2.4 Operational Support Segment (OSS)
The Chief of the OSS is responsible for operating and maintaining the
hardware/software deliveries developed by SDS and accepted by QAS. The
Chief, OSS will be the COTR for all SAFE operations and maintenance con-
tracts. Operations and maintenance contracts will be written and execu-
ted by this segment. At the appropriate time (to be determined) respon-
sibility for operating and maintaining SAFE-C and SAFE-D will be accepted
by CIA (ODP) and DIA (RSO) respectively.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.2.5 Support Staff
The Chief of the Support Staff is responsible for providing budget, fi-
nancial program, and resource accounting support; and for producing an
audit trail for the expenditure of funds to the respective agencies when
requested. The Chief of the Support Staff is also responsible for main-
taining a project library for document control, and for facility plan-
ning. In addition, the Chief of the Support Staff will provide appropri-
ate reports (congressional, status, etc.) in support of the Project Di-
rector and Deputy Director. He will also be responsible for office ad-
ministration and personnel and physical security.
3.2.6 Contracting Officer
The Contracting Officer is assigned to CSPO from the Procurement Divi-
sion, Office of Logistics and serves as a member of the management staff.
In this capacity, the Contracting Officer participates in the realignment
of Development Contractors from subcontractor status to associate con-
tractor status based on SAFE redirection. In addition, the Contracting
Officer negotiates and administers resulting contracts.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3 CSPO Supporting Organizations and Responsibilities
The Director and Deputy Director of CSPO are responsible for coordinating
matters relating to SAFE with appropriate organizations within the CIA
and/or the DIA. Coordination will be through comments on appropriate
documents, management reviews, technical reviews, participation in vari-
ous standing and ad hoc committees and boards, and other appropriate ve-
hicles to insure smooth transition of SAFE into the respective agencies.
When direct support, such as personnel resources of an organization with-
in CIA or DIA is required, a contractual arrangement will be established
with the organization external to the CSPO. The vehicle for this con-
tractual arrangement will be a memorandum of understanding and/or project
tasks, which will identify the kind of support, amount of resources and
schedule for which the support is required.
Those organizations within CIA and DIA which will be affected appear in
the following subparagraphs (list not all inclusive and will change as
necessary).
3.3.1 CIA Organizations
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.1.1 Office of Data Processing/DA
3.3.1.1.1 Engineering Division (ED/ODP)
This Division is responsible for providing reliable and stable computer
and teleprocessing hardware for ODP computer systems and for ensuring
that the capacity of these systems is sufficient to meet customer re-
quirements. This Division is responsible for the acquisition of all
hardware required by SAFE and for providing operational and maintenance
support for the hardware deliveries after they are placed into operation.
An Engineering Coordinator is responsible for developing hardware config-
urations and a hardware installation plan and will report to the Director
of CSPO through the Chief of SDS. The Engineering Coordinator draws sup-
port from Processing/ODP, CSPO, and contract resources in carrying out
these responsibilities.
3.3.1.1.2 Systems Programming Division (SPD/ODP)
This Division is responsible for providing stable and reliable operating
systems, database management systems and systems related software for ODP
computer systems.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
This division will be tasked to: (1) design and implement augmentations
to AIM, (2) develop the CTC/HASP component of the Communications Services
CPCI providing intermachine communication between the VM and MVS proces-
sors, and (3) develop software for the VM virtual machine to communicate
with the M204 DBMS on the MVS processor.
A System Programming Coordinator will serve as the COTR for contract sup-
port and will report to the Director of CSPO through the Chief of the
Systems Development Segment. CSPO will provide contractor support funds
and contractor personnel will be integrated into the appropriate Systems
Programming Division organizational components to augment existing staff
as agreed. The effect of the contractor support obtained will be to aug-
ment support required for implementation of the SPD/ODP project tasks.
3.3.1.1.3 Operations Division (OD/ODP)
This Division manages and operates the Northside Computer Center. An
Operations Division Coordinator will be assigned to the CSPO's Operations
Support Segment and will be responsible for the management and operation
of systems housed in the Northside Computer Center.
3-12
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.1.1.4 Production Division (PD/ODP)
This division is responsible for managing selected production ADP appli-
cations and database management systems processed on ODP computers to
ensure that major data processing services are provided to CIA organiza-
tional components and certain members of the intelligence community; and
that data base administration support for production applications is also
provided. In addition, this division establishes and executes procedures
to control application software that has been placed into production
operational status.
3.3.1.1.5 Customer Services Staff (CSS/ODP)
This organization is responsible for assigning system and storage access
privileges to users of ODP services. Likewise, it will be responsible
for assigning system and storage access privileges to the SAFE systems'
users. This staff also provides consulting services for general system
services questions such as job control language, utility software, and
executive procedures. CSS also provides user documentation for ODP's
services.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.1.1.6 Systems Development Division/Applications/ODP
This Division developed the SAFE-D DATEX Emulation Program to support the
PCTCS and DSSCS (DIA) message traffic in the SAFE Early Capability. This
software is based in the VM/CMS system and emulates the CIA's Data Ex-
change (DATEX) message switch. This division will be responsible for
providing programming and consulting support for modifications as re-
quired for the SAFE-D DATEX Emulation Program. In addition, this divi-
sion must provide long range support of SAFE deliveries and provide sup-
port to Logicon in the development of the External Message Interface
(B41) CPC of the Message Analysis Processing (MAP) CPCI.
3.3.1.2 Office of Training and Education/DA
The Information Science Center of OT&E provided the necessary training of
initial users of the SAFE Early Capability. This was done in concert
with the CSPO and coordinated with user representatives of both agencies
(OCR and ASG of CIA and the SAFE Users Group of DIA). OT&E will assist
CSPO in the future by providing inputs to the SAFE Training Plan.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.1.3 Office of Communications/DA
The Domestic Networks Division (DND), within the Office of Communications
(OC), is responsible for CIA domestic communications. OC currently over-
sees the operations of a Data Exchange (DATEX) which will provide SAFE
with data communications to/from community organizations and other intel-
ligence community resources. The Communications Security Division (CSD),
within the Office of Communications, is responsible for TEMPEST testing/
approval of all terminals and printers accessing the CIA SAFE system.
3.3.1.4 Office of Security/DA
The Information Systems Security Group within the Office of Security (OS)
insures that the requirements set forth in DCID 1/16, Security of Foreign
Intelligence in ADP Systems and Networks, are executed and adhered to.
OS will play a major role in the approval of all CIA SAFE system termi-
nals and printers.
3.3.1.5 Office of Central Reference/DI
The Office of Central Reference (OCR), of the Directorate of Intelli-
gence, is the CIA's primary library, both for traditional library func-
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
tions (e.g., as a repository for books) and for reference services. OCR
is responsible for creating and maintaining the large Subject Reference
File that will become the Central Index in the CIA SAFE system.
3.3.1.5.1 SAFE User Representative Element (SURE)/OCR
SURE is directly involved in supporting the SAFE user. SURE trains users
on-site and sends personnel to assist in the formal training by the Of-
fice of Training and Education. SURE assists users on a day-to-day basis
in constructing dissemination profiles and in resolving trouble calls.
SURE creates the menus that users see when they use the system, and per-
forms access procedures for new users and other user-oriented functions.
In addition, SURE monitors hardware and software problems and resource
planning requirements.
3.3.2 DIA Organizations
3.3.2.1 Deputy Assistant Director for Defense Intelligence Systems (RSD)
The Deputy Assistant Director for Defense Intelligence Systems (RSD) man-
ages and coordinates all DoD intelligence information system programs and
insures that such systems interface with the intelligence community and
3-16
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
DoD systems. The Vice Deputy Assistant Director for Defense Intelligence
Systems is the Deputy Director of CSPO.
3.3.2.2 Executive Director for DoDIIS Management (RSM)
The Executive Director for DoDIIS Planning and Management is responsible
for effective execution of the SAFE Program with respect to the following:
1. Adequate definition of DoDIIS community requirements.
2. Planning for SAFE implementation with the DoDIIS community (in-
cluding DoDIIS user training).
3. Development and transmission to the DoDIIS community of the in-
formation required to implement necessary SAFE/DoDIIS functional
interface.
4. Justify GDIP resources to the DIA/DG staff, IC staff and Congres-
sional Oversight Committees.
3.3.2.3 Executive Director for DoDIIS Engineering (RSE)
The Executive Director for DoDIIS Engineering provides engineering man-
agement and support for the development and enhancement of the DoD Intel-
ligence Information System (DoDIIS). RSE's responsibilities to the DIA
SAFE Project include:
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Procuring Network Front End (NFE) devices necessary for the SAFE
node to attach to the DoDIIS network. (RSE-2)
o Developing the DoDIIS standard protocol specifications. (RSE-2)
o Providing NFE hardware and software installation assistance to
the SAFE-D. (RSE-2)
o Providing DoDIIS technical information to CSPO to assist the SAFE
DoDIIS interface contractor to design and implement the inter-
face. (RSE-2)
o Developing the security program in support of SAFE-D processing
of foreign intelligence. (RSE-4)
3.3.2.4 Executive Director for DIA Systems (RSO)
The Executive Director for DIA systems will provide general technical
support to the CSPO supporting SAFE system development and will prepare
to take over the responsibility for operation and maintenance of deliv-
ered SAFE system hardware and software. Additionally, RSO has the re-
sponsibility for the conversion of the DIAOLS files as specified in the
DIA project tasks.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.2.4.1 RSO-2
This entity manages and operates Agency Automatic Data Processing equip-
ment, including auxiliary support equipment, remote batch terminals, as-
sociated communications interface devices and computer output microfilm
equipment. This office will be responsible for operating and maintaining
the SAFE system for DIA. RSO-2 will supervise the installation and con-
duct operational acceptance testing of SAFE hardware and maintains docu-
mentation to validate equipment reliability and vendor invoices. This
office also manages and operates a central tape library and the alternate
repository for data bases, data systems and operating programs stored on
magnetic tape, disk packs, microfilm or punched cards.
3.3.2.4.2 RSO-4
This office designs, develops and implements general ADP systems to sup-
port all aspects of DIA operations, and functions as the DIAOLS system
manager. This office also has the responsibility to assist CSPO in the
maintenance of the SAFE conversion baseline to include monitoring those
changes to the existing DIAOLS system that could impact the SAFE conver-
sion schedule or cost. RSO-4 and CSPO have defined responsibilities and
procedures to expedite coordination in support of the SAFE conversion
task. RSO-4 also has the primary responsibility to conduct the conver-
sion for those selected DIAOLS files/applications not included in the
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
existing SAFE conversion task. RSO-4 will administer data base produc-
tion and quality control for the SAFE system.
3.3.2.4.3 RSO-6
This office acts as the DIA Authority and Coordinator for system program-
ming and integration activities for SAFE Early Capability. This office
will be responsible for managing and maintaining all system support soft-
ware for the SAFE system.
3.3.2.5 Defense Intelligence College (AIS)
The Defense Intelligence College educates and trains selected DoD mili-
tary and civilian personnel for the performance of command, staff and
policy-making positions in the DoD, national and international intelli-
gence structures.
The Defense Intelligence College's role in SAFE training will be de-
scribed in the SAFE Training Plan.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.3.2.6 Deputy Assistant Director for Communications (RCM)
The Deputy Assistant for Communications is responsible for the planning,
designing, installation, and maintenance of DIA communications facilities
required to support the SAFE system and its user population. This in-
cludes terminal installations, terminal to host communications, and com-
munications to external systems such as DoDIIS, PCTCS, and DSSCS.
3.3.2.7 Office of Security (OS)
The Office of Security develops and administers DIA's physical, informa-
tion, document and personnel security programs. In addition, OS manages
DoD sensitive compartmented information programs and serves as the prin-
cipal DoD advisor on TEMPEST matters. The OS will be responsible for
administering DIA SAFE security.
3.3.2.8 Customer Support Group (CSG)
The Customer Support Group provides the interface between the SAFE end-
user and the technical support personnel who operate and maintain the
SAFE system.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.4 CSPO Development Contractors
Development contractor tasks will be described in definitive statements
of work (SOWs). Detailed task descriptions, defining technical tasks to
be performed, contractor support required, and documentation and products
to be delivered are delineated in the development contractors' project
tasks. When these tasks are negotiated and incorporated into contractor
SOWs, they will become contractual agreements between CSPO and the re-
spective development contractor.
Within CSPO there will be a COTR for each contractual effort. COTRs will
monitor the progress of their respective contractor and assist the con-
tractor in obtaining information necessary to perform the contracted
tasks. The CSPO System Engineer will coordinate all changes to the SAFE
design in accordance with the SAFE Configuration Management Plan. The
Chief of the Systems Development Segment will designate managers for each
specific delivery who will ensure that all actions associated with that
delivery are coordinated and accomplished.
The CSPO Development Contractors are identified in the remainder of this
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.4.1 TRW
TRW is responsible for:
o Project planning and management support to CSPO
o System development and systems engineering design support to CSPO
o Supporting CSPO in integrating and testing system hardware and
software.
o Developing a SAFE User Interface Model (SUIM) in support of the
SAFE User Language (SUL).
o Maintaining the User Interface Requirements Specification (UIRS)
and supporting development and refinement of the SAFE User Proto-
cols and Interface Model (SUIM).
o Providing SAFE-C conversions of PMO save files to AIM save files.
o Providing SAFE-C conversion of AIM save files to INQUIRE index
files.
o Designing and developing software components of the Data Manage-
ment CPCI for deliveries 3, 4 and 5.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
o Converting CRD and HUMINT files to SAFE-D.
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Designing and developing software components of the DoDIIS and
MIS CPCIs.
o Converting AIF, DIOBS, ELINT, and Crisis Management files to
o Providing SAFE-C conversion of AEGIS and RECON formatted files to
INQUIRE.
o Defining and developing a prototype test data base in support of
DIA's Integrated Data Base (IDB).
o Creating the SAFE Functional Overview Document (SFOD).
3.4.2 TRW/CCA
TRW/CCA are responsible for:
o Providing Model 204 support to DIA and CIA system programming and
computer operations personnel.
o Developing the Delivery 4 M204 Augmentation CPC.
3-24
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.4.3 CRW
CRW is responsible for:
o Project planning and management support to CSPO
o System engineering support to CSPO
o Developing a Dissemination Analysis Processing (DAP) system to
support dissemination of electrical messages to SAFE analysts,
mail files and support of the Message Analysis Processing (MAP)
CPCI and augmentations for Mail File Create.
o Incorporating Second Pass Dissemination.
o Developing software components of the System Services (SS) CPCI.
o Developing software components of the User Data Base (UDB) CPCI.
3.4.4 INFODATA
INFODATA is responsible for:
o Project planning and management support to CSPO
3-25
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Providing general INQUIRE support to DIA and CIA systems program-
ming and computer operations personnel.
o Adapting and augmenting INQUIRE to support deliveries 1, 2, 3,
and 5.
3.4.5 LOGICON
Logicon is responsible for:
o Project planning and management support to CSPO
o Supporting MAP processing of incoming electrical message traffic.
o Designing and developing software components for MAP to meet full
SAFE integration functional capabilities.
3.4.6 MITRE
MITRE is responsible for:
o Project planning and management support to CSPO
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Supporting the continuous definition of interface requirements
and design detail for SAFE deliveries to CIA and DIA.
o Designing the DIA SAFE interface to DoDIIS Network for future
deliveries.
3.4.7 ODP
ODP is responsible for:
o Project planning and management support to CSPO
o Providing operating system and utility software support
o Designing and implementing augmentations to AIM for deliveries 2,
3, and 5.
o Developing intermachine communications (HASP/CTC) between the VM
and MVS processors.
o Developing software for the VM virtual machine that will communi-
cate with M204 on the MVS processor.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
3.5 CSPO Quality Assurance Contractor
3.5.1 Geodynamics/RCA
The Quality Assurance Contractor (Geodynamics/RCA), in providing support
to the Quality Assurance Segment is responsible for defining and execu-
ting test plans and procedures, providing administrative support to the
SAFE CCB, preparing and maintaining the SAFE Configuration Management
Plan, and providing a master schedule (PERT) for all project activities.
The Quality Assurance Contractor will advise and support the Chief of QAS
in Configuration Management, Validation and Verification and System En-
gineering and Technical Assistance.
a. The Configuration Management tasks include:
o Preparation of a Configuration Management Plan specifying config-
uration management policies and procedures for all SAFE contrac-
tors and government software developers.
o Providing Configuration Control Board (CCB) support and adminis-
tration, including technical coordination of design requirements
changes, test changes, deviations and deficiencies.
o Managing release and storage of software and documentation.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Preparing and maintaining configuration status accounting reports.
o Developing and maintaining a configuration item identification
tracking system.
b. The Verification and Validation task includes:
o Preparation of a Quality Assurance Plan specifying quality assur-
ance policies, procedures and standards.
o Reviewing development contractor's design and development docu-
o Conducting design reviews, product reviews and critical Computer
Program Component/Configuration Item reviews and audits.
o Monitoring and validating system integration and test.
o Reviewing and validating requirements traceability matrices pre-
pared by development contractors.
o Monitoring resolution and closure of action items and scope is-
sues on behalf of all quality assurance functions.
o Attending, and where specifically directed by the government,
organizing and conducting technical interchange meetings.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Verifying design and critical software code versus requirements.
o Reviewing and evaluating system integration and test plans, pro-
cedures and reports developed by TRW, the principal contractor.
o Preparing an Acceptance Test Plan, procedures, and test cases,
performing acceptance tests and preparing acceptance test reports.
o Performing an Operational Evaluation (OE) subsequent to success-
ful completion of system acceptance tests and preparing OE brief-
ings and reports.
c. The System Engineering and Technical Assistance Task includes:
o Preparation of a System Integration Support Plan, specifying pol-
icies and procedures for conducting CSPO and QA contractor system
integration activities.
o Preparing program management review reports.
o Attending, and where specifically directed by the government,
organizing and conducting technical reviews, design reviews, pro-
gress reviews and other designated meetings.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
o Reviewing CSPO technical planning documentation.
o Preparing and maintaining the Master Program Schedule.
o Reviewing and evaluating acceptance test plans, procedures and,,
reports.
o Monitoring acceptance tests performed by the QA/V&V Staff.
o Preparing a Transition Plan for each phase reflecting the results
of the Operational Evaluation and including recommendations for
future phase capabilities.
o Monitoring, in conjunction with the Verification and Validation
function, system integration and test.
3.6 Project Control
Identification of a measurable set of project milestones and development
standards provides the foundation for maintaining project control through
all phases of the system's life cycle. In order to assess and control
the progress of SAFE development, a series of reviews, audits and tests
will be conducted by CSPO. Progress will be measured against milestone
events. These milestone events will be scheduled as control points
3-31
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
throughout the development cycle. These controls are directive in nature
and require CSPO authorization for any deviations or waivers.
3.6.1 Reviews
SAFE project reviews consist of formal design reviews, management re-
views, and documentation reviews.
3.6.1.1 Formal Design Reviews
a. System Design Review (SDR)
The purpose of the SDP, is to conduct a final review prior to pro-
ceeding with the development of preliminary design specifica-
tions. Included in the agenda is a summary review of the System
Engineering Management activities. The SDR ensures that (a)
system specifications are updated and complete; (b) configur-
ation items allocated to them are complete and traceable; (c)
subsystem development specifications are valid and consistent
with system requirements; (d) technical risks are identified; (e)
adequate cost trade-offs are conducted relative to special design
considerations; and (f) approved design criteria will meet the
system's performance requirements, and reliability, availability
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
and maintainability requirements. The SAFE SDR was accomplished
in February 1983. A series of documents were reviewed. The SAFE
Project System Design Document, the Hardware Configuration Docu-
ment, the SAFE Project Conversion Plan, and the System Require-
ment Specification Traceablity Matrix constituted the allocated
baseline. These documents will be used in subsequent project
planning and formulation to establish the system architecture and
design. Post-SDR design activity is now underway.
b. Preliminary Design Review (PDR)
The purpose of the PDR is to: (1) review all CPCIs for each de-
livery and assess associated risk (technical, cost, and schedule)
for the selected design approach, (2) determine compatibility
with performance and allocated functional requirements of the
CPCI Specifications, and (3) establish the existence of the phys-
ical and functional interfaces among the CPCIs and other items of
equipment, facilities, computer programs, and personnel.
c. Critical Design Review (CDR)
The CDR will be conducted for all CPCs for each delivery when the
detailed design is essentially complete. The purpose of the CDR
will be to: (1) determine that the detailed design of the CPCs
under review satisfies the performance and functional require-
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
ments of the CPCI Specifications, (2) establish the detailed de-
sign compatibility among. the CPCs and other items of equipment,
facilities, computer programs and personnel, (3) assess produci-
bility and risk areas (on a technical, cost, and schedule basis),
and (4) review the preliminary Computer Program Component Speci-
fications.
3.6.1.2 Management Reviews
a. Weekly status reports will be provided to ODP and RSD by Direc-
tor, CSPO and Deputy Director, CSPO respectively.
b. Monthly Program Management Reviews will be presented by the SAFE
QA contractor to the Director and Deputy Director, CSPO and sen-
ior staff.
c. Monthly SAFE status reviews will be presented to CIA's Deputy
Director for Administration and DIA's Assistant Director for Re-
sourc es and Systems.
d. The Deputy Director DIA, the Deputy Director of Central Intelli-
gence, and the Director, IC Staff will receive a status briefing
quarterly.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
e. The Director of Central Intelligence and the Director, DIA will
receive a SAFE status briefing annually, or more frequently as
required.
3.6.1.3 Documentation Reviews
All SAFE Documentation will be submitted in accordance with the SAFE Doc-
umentation Plan. The procedures for reviewing and controlling documenta-
tion are outlined in the SAFE Configuration Management Plan.
3.6.2 Tests
In order to assure that the defined system and user requirements are sa-
tisfied, it is essential to develop a rigorous testing program. The for-
mal testing process begins in the development phase and continues until
the system is certified operational by the Director, CSPO on the recom-
mendation of Chief, Quality Assurance Segment and accepted by the cus-
tome r.
Test plans will be provided by development contractors as specified in
the SAFE Documentation, Quality Assurance, and Configuration Management
Plans. Test plans provide guidance for the management and technical ef-
forts necessary throughout the test. The objectives of these plans are
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
to identify all functions and requirements encompassed within each deliv-
ery and to assure they are comprehensively tested. Test performance will
be monitored by the Chief, QAS. Test reports will be prepared in accor-
dance with the SAFE Documentation Plan documenting test results.
3.6.3 Schedules
A SAFE Master Schedule will be developed using the automated system PAC
II. All SAFE activities, milestones, dependencies and resource estimates
will be input. Major milestones (Appendix A) will be used to reflect the
required dates for activities and events which must be met to achieve the
desired deliveries. Resource estimates for accomplishing an activity and
the resources available will be obtained from the development contrac-
tors. PAC II will utilize this information to develop a PERT schedule
and the critical path for the SAFE Project. If an activity has a re-
quired start date or a definite finish date, this will be identified for
the activity and will force the schedule to accomodate these dates.
The PERT schedule will be maintained using monthly status data for all
activities. The actual expenditure of resources, milestones accom-
plished, and estimates of resources to complete a task will be input.
PAC II will then identify any schedule deviations and the effect of these
deviations on the critical path and overall project. To assist in the
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CD RL D -00 2
impact analysis, other schedules will also be produced. A specific de-
velopment contractors' schedule and a schedule by delivery will be avail-
able.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D -00 2
SYSTEM DESCRIPTION
System implementation will be conducted in incremental deliveries. Each
delivery, building on an exisiting, preliminary capability, provides ad-
ditional functionality to the user. The Project Plan describes the five
deliveries which have been identified to date. The plan will be expanded
as subsequent deliveries are defined.
4.1 Incremental Deliveries
SAFE development begins with Early Capability which became effective in
March, 1983. Project development is scheduled to continue through Feb-
ruary, 1986. During that time span five incremental deliveries are plan-
ned for implementation. A summary of the functional capabilities inclu-
ded within each incremental delivery as well as proposed delivery dates
for both CIA and DIA are documentated in the remaining paragraphs of this
section. In the process of generating the SAFE Early Capability (SEC)
the existing VM system residing within CIA was duplicated for SAFE.
Thus, application software over and above what was originally identified
to support SEC became available for user access. However, SAFE is not
committed to support this additional software. Unless otherwise noted as
part of the integrated SAFE software design, these VM application pack-
ages are not considered part of the SAFE development.
4-1
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
4.1.1 SAFE Early Capability: SAFE-C, March 1983; SAFE-D, June 1983
The SAFE Early Capability provides both DIA and CIA users a SAFE-like
capability supported by several separate applications packages: Profile,
Mail, Text, and Automatic Information Management (AIM). The Profile
software allows users to list words and phrases in "interest profiles"
and then logically associate these profile elements in a query expres-
sion. These profiles, which may represent either individuals or organi-
zations, serve to select electrical messages for dissemination to respec-
tive users "mail files". Once messages (documents) are placed in mail
files, the user may permanently "save" messages for retention. He may
also annotate and route messages to other users. Messages may also be
deleted from mail files or printed to provide hard copy. The third soft-
ware package, Text, allows the user to search the complete text of all
documents maintained in a master data base or individual private files.
These data bases have been created as a result of messages "saved" during
the users' review of his mail file. In addition to these three software
packages supporting message processing and dissemination, the SAFE Early
Capability through the use of AIM, also provides the user text editing
functions that allow for the creation, editing, formatting, routing and
printing of intelligence reports, memorandums and other documents.
Access to SEC data and user services is via the Delta Data 7260T CRT
which provides a standard keyboard and an array of function keys, some of
which are terminal specific and some of which can be programmed to per-
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
form different tasks relevant to unique SEC functional capabilities.
User access to SEC is accomplished through three separate "log-ons" for
Profile, Mail and Text.
The software packages which constitute the SAFE Early Capability provide
many functional capabilities similiar to SAFE requirements. These pack-
ages will not be referenced beyond SAFE Delivery 2. Depending on the
extent to which SEC packages satisfy the System Requirements Specifica-
tion, these packages will be integrated or further enhanced as part of
the CPCI/CPC software units identified in Delivery 2 and subsequent
deliveries.
4.1.2 Delivery 1: SAFE-C; SAFE-D, Fall 1983
Delivery 1 will provide an improved algorithm for electrical message dis-
semination processing and one level of interprofile logic (ability of a
user's interest profile to reference another interest profile). In addi-
tion, Delivery 1 will provide access to INQUIRE, text data base manage-
ment system (DBMS) and M-204, structured file DBMS. The access to these
commercial DBMSs will be limited to a small subset of the user population
as well as system development personnel.
The INQUIRE DBMS will be utilized for initial prototyping of data struc-
tures to optimize search of messages (documents) filed in the system.
Access to INQUIRE will be via the INQUIRE User Language. The M204 DBMS
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
will be utilized to support the conversion of those DIA data bases, pro-
grams and products for which DIA/RSO has assumed responsibility. These
data bases are currently supported on the DIA on-line system (DIAOLS).
Access to M-204 will be via the M-204 User Language or a Higher Order
Language (HOL) application program.
4.1.3 Delivery 2: SAFE-C, November 1984
Delivery 2 provides for the initial integration of comprehensive routing
and filing functions with user mail files. In addition to being able to
generate and edit text data, users will be able to route messages and
associated annotations to other SAFE users. Documents may be identified
by a user to route to another user during the browse of his respective
mail file. Documents stored in mail files can be listed and, by user
selection directly displayed. In Delivery 2, SAFE users will also be
able to store predefined queries as well as access lists to mail files.
These access lists are maintained by the individual owners of mail files.
SAFE text editing capabilities will be enhanced by a host-based word pro-
cessor. The text editing capability will be integrated with that SAFE
software which provides for the routing of messages and internally com-
posed documents.
The INQUIRE DBMS will be used for the Document and System Catalog files
and will provide the capabilities to search the documents by zone or sys-
tem catalog data. The user may search any number of sources for any spe-
4-4
Approved For Release 2008/06/11: CIA-RDP85BO1152 R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
cified data ranges. Documents sent to Mail Files may be searched for
user-specified date ranges. The SAFE Message Analysis Processing (MAP)
CPCI will be available and will provide a significant increase in the
identification of SAFE message zones and system catalog data which can be
used in search and display.
The basic SAFE workstation screen configuration specified for the user
interface will be available except when the user is accessing AIM or us-
ing the host-based word processor. Predetermined terminal screen config-
urations will be available but will not be dynamically reconfigurable by
the user. The SAFE User Language (SUL) command structure will be used
for interaction with Mail Files, and the Document File in INQUIRE. Menus
will be available for most user interactions.
In addition to all previously delivered capabilities, the following CPCIs
and CPCs will be developed for Delivery Two:
CPCI CPC
AIM Display
AIM Central
Host Based Word Processor
(Simplified Interface)
AIM Import/Export Communications Virtual
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
COMMUNICATIONS SERVICES CTC/HASP
DISSEMINATION ANALYSIS Dissemination Analysis
PROCESS (DAP)
Profile Compilation and Maintenance
Data Base Maintenance
Grand Central Virtual
User Companion Virtual
User Search Virtual
Terminal Virtual
DAP Network Communication Virtual
MESSAGE ANALYSIS PROCESS External Message Interface
(MAP) Message Resolution Process
Message Error Correction
MAP Sequencing and Control
INQUIRE
INQUIRE DBMS and AUGMENTATIONS
INQUIRE Network - Communications
Virtual
SAFE C CONVERSION SAVE File Conversion Software
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
4.1.4 Delivery 3: SAFE-D, March 1985; SAFE-C, June 1985
Delivery 3 will include the augmentations to the capabilities introduced
in Delivery 2 and an initial capability for DIA to reprocess indexed mes-
sages through the SAFE system in support of DIA's DoD message retransmis-
sion function (Second Pass Dissemination). CRD and HUMINT files will be
brought up on the SAFE-D system. However, a subset of CRD and HUMINT
files will remain on DIAOLS to support DoD access. This condition will
exist until there is SAFE connectivity to the DoD commands. A prototype
DoDIIS Network Front End will be available to support connections to
other DoDIIS test sites. DIA/RSE will be responsible for the DoDIIS NFE
to include an interface that will connect the DoDIIS NFE to the existing
IDHSC-2 network and COINS.
Delivery 3 for CIA and DIA will allow the user to file and maintain docu-
ments in an INQUIRE index file. In addition to filing documents in AIM
data bases, INQUIRE supports data inversion which allows the user to ra-
pidly search and maintain individual document data bases. Users will be
able to enter free text annotations to index records or specific terms to
keyword fields. Access lists to INQUIRE files will allow the file owner
to control read/write access to individual files or, delegate that respon-
sibility to other users. Additionally, a command history log which main-
tains a history of each command or series of commands entered into the
system by 'a user during an interactive session will be available.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
In addition to those CPCIs and CPCs identified in Delivery 2, the follow-
ing listing of CPCIs and CPCs will be developed or enhanced. Those CPCs
annotated with an asterisk indicate enhanced software. All other CPCs
are initially developed in Delivery 3.
CP C
AIM Display *
AIM Central *
DISSEMINATION ANALYSIS Second Pass Dissemination
PROCESS (DAP) Data Base Maintenance
Profile Compilation and Maintenance
User Companion Virtual *.
Terminal Virtual *
Index File Maintenance Virtual
DAP Network - Cormiunications Virtual
DoDIIS COMMUNICATION DoDIIS Terminal Support
DoDIIS Network Services
DoDIIS Interactive Support
DoDIIS File Transfer
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
CPCI CPC
DATA MANAGEMENT DIA Mail
SAFE D CONVERSION HUMINT Conversion Software
INQUIRE
SAFE C CONVERSION
CRD Conversion Software
INQUIRE DBMS and Augmentations
SAVE file conversion software
4.1.5 Delivery 4: SAFE-D, August 1985
The DIA interface to DoDIIS will be completed in this delivery. All of
the AIF, DIOBS, ELINT, and crisis management files and products will be
brought up on the SAFE-D system. These files will also remain in DIAOLS
for a period of time to provide for parallel operations and to insure the
integrity of the conversion effort. In addition, the user interface will
be enhanced to include connectivity to the structured files in M204 under
a single user log-on and user language construct.
Command procedures (sequence of SAFE User Language commands) will enhance
the user interface. Under certain conditions command usage within a cer-
tain context may be prohibited to prevent deadlock and data inconsis-
tency. Additional capabilities will be added to support system health
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
monitoring and recording MIS information that will be used in MIS report
generation. Maintenance transactions can be stored and maintained in
transaction files for application to DIA's production data bases based on
user initiation.
In addition to capabilities previously delivered, the following listing
of CPCIs and CPCs will be developed or enhanced. Those CPCs annotated
with an asterisk indicate enhanced software. All other CPCs are initial-
ly developed in Delivery 4.
CPCI CPC
M204 M204 DBMS and Augmentations
Terminal Virtual *
User Companion Virtual
Background Activity Control
AIM DATA BASE AIM Display *
AIM Central *
DoDIIS COMMUNICATION DoDIIS Terminal Support
DoDIIS Network Service
DoDIIS Interactive Support
DoDIIS File Transfer
Approved For Release 2008/06/11: CIA-RDP85BO1152 R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
DATA MANAGEMENT
CPC
Structured Data Base
Data Base Control *
Offensive Search
Data Base Reports *
Collateral Filter *
Batch Processing Services
SYSTEM SERVICES Directory Services
MANAGEMENT INFORMATION User MIS Collection
SERVICES User MIS Reporting
SAFE D CONVERSION AIF Conversion Support
DIOBS Conversion Support
ELINT Conversion Support
COMMUNICATION SERVICES M204 Network - Communications Virtual
4.1.6 Delivery 5: SAFE-C, December 1985; SAFE-D, February 1986
The SAFE Index File capabilities will be completed for this delivery.
Full index fields and the ability to relate multiple occurrences of index
phrases to one another will be provided.. Transaction files will exist to
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D -00 2
allow for delayed processing of transactions to those files supporting
message processing and dissemination. Validation criteria will support
file maintenance. The CIA Central Index File previously maintained in
CIA on a separate system, will be brought up on SAFE-C along with its
products (e.g. keyword occurence lists).
The user interface will be enhanced to support multiple activities in
multiple screen configurations (e.g., document in one split and transac-
tion in another split). Synonym list files (i.e., named collection of
one or more synonyms logically "ORed" together) will be available. The
text composition function (i.e., host-based word processor) will be to-
tally integrated into the user interface and enhanced based upon require-
ments generated from preliminary use during previous deliveries. Elec-
trical messages that arrive in multiple sections will be combined and
processed as a single document for message dissemination and storage.
In addition to the CPCIs and CPCs provided in Deliveries 2, 3, and 4, the
following CPCs will be developed or enhanced. Those CPCs annotated with
an asterisk indicate enhanced software. All other CPCs are initially
developed in Delivery 5.
CPCI CPC
INQUIRE INQUIRE DBMS and Augmentations *
DATA MANAGEMENT INDEX Data Base
Document Data Base
4-12
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
USER DATA BASE
User Companion Virtual
Terminal Virtual *
AISF Data Dictionary
SAFE C CONVERSION Index File Conversion
Software
AIM DATA BASE
Host Based Word Processor
AIM Display *
AIM Central *
By completion of Delivery 5 the major functions and files will have been
introduced to both CIA and DIA SAFE users. With the basic system provi-
ded, additional sophisticated functional capabilities and performance
enhancements will be provided to the users. The objective of performance
enhancements will be to reduce response time for multiple data base and
complex data structure search. Functionally, the user will be provided
more direct control over his terminal screen configuration. Users will
have complete control over the input and output formatting capabilities.
Threshholds in the system will be both system and user, controlled. Addi-
tional route logs will be available defining the exact status of routed
items and items a user will be receiving.
The system will provide for automatic generation of candidate index re-
cords for file update or user edit. Teleconferencing will be enhanced by
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
allowing multiple terminals to maintain common images of data. High le-
vel graphics output may be generated and displayed on graphics terminals.
The system will be able to subset messages, in SAFE mail files, and index
files for the purpose of controlling access based on security and need to
know.
4-14
Approved For Release 2008/06/11: CIA-RDP85 BO 1152 R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
SECTION 5
RISK ASSESSMENT AND MANAGEMENT
Successful development of a major software system involving many users
and developers requires a concentrated effort on the part of the Project
Office to identify and manage risk. The objective of all risk management
programs can be simply stated as the identification and reduction of all
potentially high risk elements of a project at the earliest possible date
to minimize overall impact on schedule and cost. The risk reduction
techniques that will be applied to all deliveries by the Consolidated
SAFE Project Office include prototyping, formal design reviews for each
delivery with all development contractors participating, early definition
and centralized control of interfaces, close surveillance over develop-
ment contractors by CSPO COTRs, and the designation of a single individ-
ual from CSPO to manage and coordinate each delivery. Transcending all
risk management methods is the creation of a Quality Assurance Segment as
an integral part of CSPO, who will be assisted by an independent Quality
Assurance Contractor.
The following subparagraphs describe risks that are known to exist for
the SAFE Project and also describe steps that have been initiated by CSPO
to effectively manage and contain these risks.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
5.1 Programmatic Risk
Programmatic risks are defined as risks that are inherent to all large-
scale software development projects. Programmatic risks existing within
the SAFE Project include, but are not limited to, the following:
o Lack of complete and precise technical definition of tasks that
can be directly traced to system requirements.
o Lack of complete functional and physical definition of interfaces
between large software subsystems (CPCIs) being developed by mul-
tiple development contractors.
o Risk associated with the major software integration effort re-
quired for SAFE Delivery Two and all subsequent deliveries.
o Risk associated with the coordination of multiple development
The sections that follow expand on these known risks and describe the
specific management strategies that have been planned by CSPO to minimize
their possible impact on the achievement of all SAFE objectives.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
5.1.1 Lack of Technical Definition
A number of factors which combine to reduce, but not altogether elimi-
nate, this risk are:
a) From previous work on the SAFE Project, CSPO retains a signifi-
cant "corporate memory" in the form of technically qualified
people with a thorough understanding of SAFE. Some of these in-
dividuals have become specialists in a certain area of SAFE and
their continuity is expected to make an invaluable contribution
in the linking of task statements to firm SAFE requirements.
b) CSPO is dedicated to having a single Preliminary Design Review
and a single Critical Design Review for each delivery. These
reviews will bring. all development contractors together to de-
scribe individually their approaches to preliminary and detailed
design and are expected to do much to resolve problems in under-
standing of tasks. Design documentation required to support PDR
and CDR, available for CSPO and QA contractor review 30 days-
prior to each review, will go far toward accomplishing the objec-
tives of a formal "project definition phase".
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
5.1.2 Lack of Interface Definition
The lack of complete and unambiguous functional and physical definitions
for all interfaces between Computer Program Configuration Items being
developed by different contractors can lead to serious problems of incom-
patibility which heavily impact both cost and schedule if major software
"fixes" are required.
This risk, and its possible negative consequences, are recognized by
CSPO. An early and high priority task to define these interfaces has
been assigned to Systems Engineering within the CSPO System Development
Segment. CSPO with contractor support is responsible for preparation of
an Inter-CPCI Interface Control Document (ICD), with the objective of
having a complete physical definition of all interfaces ready for final
approval by PDR for Delivery Two. This task will be monitored by an ICD
Coordinator (ICDC) from the System Engineering Segment of CSPO. As a
matter of policy, all questions involving interfaces will be required to
be resolved or coordinated by the ICDC.
5.1.3 Integration Risk
Delivery Two will require the first major integration of CPCIs from mul-
tiple development contractors. While a system integration support con-
tractor has been selected, the personnel that the contractor will assign
5-4
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
to the integration task are not expected to have in-depth experience with
SAFE, nor with the environment and controls that will be in place for
integration work.
To reduce the risk inherent in the integration effort for Delivery Two,
the system integration support contractor will be required to have his
full integration team selected and in place by CDR for Delivery Two.
Members of this integration team will be required to participate in the
Development Contractor's Preliminary Qualification Tests (PQTs) to begin
to familiarize themselves with the CPCIs that will be integrated. Beyond
Delivery Two, most of the risks associated with subsequent integration
efforts are expected to involve specific technical issues which are not
presently identified.
5.1.4 Coordination of Development Efforts
CSPO was required to assume a broader role with the redirection of SAFE.
This role now requires that CSPO assume substantial new responsibilities
in addition to giving overall direction to all other SAFE activities.
The task of monitoring and coordinating the day-to-day progress of mul-
tiple development contractors to assure that all are proceeding toward a
common objective is beyond the capability of CSPO, staffed as it was
prior to redirection.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
CSPO recognizes and understands the broader role it is now obligated to
assume. A first step in the direction of adjusting to this new manage-
ment concept was contracting for the services of an independent QA con-
tractor to bring to CSPO special expertise in the areas of validation and
verification, change management, and systems integration support. A sec-
ond step is in the designation of several individuals from SDS to, serve
as Contracting Officer Technical Representatives for each development
contractor. These COTRs have been issued clear instructions that will
require frequent coordination with their assigned development contractor
and written weekly status summaries. This effective use of COTRs will
lead to early warnings of technical or schedule problems that in turn
will permit CSPO to shift priorities or resources in a timely manner to
minimize the potential impact on other SAFE tasks. A third step is the
designation by SDS of a single CSPO individual to manage each delivery.
It is understood that the increased manpower requirements implicit in
CSPO's new management responsibilities must be offset by significant new
staff additions. A major augmentation in the SDS staff has been approved
and is in the process of being implemented.
5.2 Technical Risk
Technical risk is that risk inherent in implementing a functional re-
quirement with a specific design approach. Unlike programmatic risks,
technical risks will vary widely from system to system. Since the redi-
rection of SAFE, most of the technical risks have not been identified
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
because of the small amount of SAFE-specified detailed design and imple-
mentation that has taken place. One area of special concern has been
identified and is discussed in the following section.
5.2.1 Database Management System Implementation
The redirection of SAFE required CSPO to evaluate candidate "off-the-
shelf" software subsystems for SAFE use to the maximum possible extent.
Following extensive literature search and personal interviews with users,
the M204 and INQUIRE DBMSs were selected for structured and text DBMSs
respectively. While the study that led to these selections made a con-
vincing case that both would perform, the SAFE DBMS functions satisfactor-
ily, there remains a possibility that one or both subsystems will not
meet all functional or performance requirements in the SAFE environment.
CSPO has recognized this potential risk and has taken steps to reduce the
risk at the earliest possible date. Delivery One has, as its sole objec-
tive, the prototyping of sufficient interfacing software to permit both
M204 and INQUIRE to be brought up, in the SAFE operational environment,
for evaluation of their actual performance. In Delivery One, these DBIISs
will be available to a small subset of the analyst community, who will
receive sufficient training in the M204 and INQUIRE native languages to
perforri this evaluation and feed the results back into the development
effort.
Approved For Release 2008/06/11: CIA-RDP85B01152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
5.2.2 Prototyping
The Government has identified two major areas where prototype development
will significantly reduce design risk. First, a model will be developed
for the SAFE User Language (SUL) and placed on the SAFE development sys-
tem. Test scenarios have been identified with which to test the validity
of user interface concepts as well as specifics of the connand language.
Test results based on user feedback will be used to modify the SAFE User
Interface Requirements Specification, (UIRS). Secondly, SAFE will develop
a prototype data base design in support of DIA's Integrated Data Base
(IDB). The IDB supports the Director, DIA, War Planning, War Fighting
data base requirements. The prototype will provide the opportunity to
optimize data base design for both functional and performance require-
ments. The results of the prototype effort will be a conversion plan
that will assist in defining the cost and scheduling of IDB conversion
subsequent to the current SAFE conversion (post 1985).
5.2.3 Performance Analysis
The SAFE system implementation strategy is one of maximizing the use of
existing software packages in order to achieve an early functional capa-
bility with minimal risk. System performance, therefore, is somewhat
dependent on the design of the existing packages. The overall approach
to achieving acceptable system performance is to implement the basic sys-
tem, collect performance data, and adjust the design. as necessary. The
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-G-008
29 July 1983
CDRL D-002
primary design adjustment will consist of hardware upgrades in later de-
livery releases. However, some software development is projected to in-
tegrate the existing packages and necessitates some performance tradeoffs
as the software design progresses.
5.2.4 DIA Resources
The ability of CSPO to adequately discharge those management and develop-
ment responsibilities dedicated by the project redirection is directly
impacted by the availability of Government resources. In the past, DIA
has been unable to staff CSPO in a timely manner. The inability to pro-
vide the necessary manpower when needed can jeopardize the progran sched-
ule. This is especially true for those project activities which involve
data base conversion, transition planning, DBMS augmentations and system
operation and maintenance. Project management cannot minimize this risk
factor, only DIA can address this issue.
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
SF-U-CA-6-008
29 July 1983
CD RL D-002
PROJECT SCHEDULES
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
DELIVERY ONE
ACTIVITIES
DEVELOPMENT SYSTEM
INQUIRE TEST
M204 TEST
AUGMENTES INQUIRE TEST
SAFE C SYSTEM
DAP TEST
INQUIRE TEST
DAPIINQUIRE TEST
AUGMENTED INQUIRE TEST
SAFE 0 SYSTEM
DAP TEST
M204 TEST
CY 83.
J J A S O N D
PDR - Prliminary Design. Raviewl
CDR - Critical Design Review
PQT - Prliminary Qualifation Test
FQT - Final Qualification Test
STC - System Testing Completes
AT'- Acceptance Test (delivery to customer).
OP - Operational
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
DELIVERY TWO
CY as
CV. 84
CY 85
CY as
(SAFE C)
J J A N D
M J S N D
J A
F
MILESTONES
L O
AT
PDR
DR POT FO ST
PRELIMINARY 011181001
DETAILED DESIGN
COOI.DtUS.UNIT- TEST
~-~
SYSTEM INTEGRATION
SYSTEM TEST
ACCEPTANCE TEST
OPERATIONAL EVALUTION
DELIVERY THREE
(SAFE C 8 D)
SAFE D
FOR
CDR PO CT
TC AT 0
MILESTONES
QQ
PRELIMINARY DESIGN
SAFE C
DATA BASE CONVERSIONSIONS
D
C
(D ED)
DETAILED DESIGN
COOR.DEDUE.UNIt TEST
SYSTEM INTEGRATION
h--1
SYSTEM TEST
m
ACCIPTANCE TEST
+--y
OPERATIONAL EVALUATION
SYSTEM INTEGRATION
SYSTEM TEST --- T
~I
Cr
,Z7C
r-~
1 J
S o
Approved For Release 2008/06/11: CIA-RDP85BO1152R001001310002-2
 Approved For Release 2008/06/11: CIA-RDP85BO1152ROO1001310002-2
DELIVERY FOUR
CY 83
J J ASOND
CY 84
F A M J A
L
CY 8$ _
M A JA S O
CY 88,
(SAFE D)
MILESTONES
-
~5fR84 STA 1 ililv\
PRELIMINARY DE31GN
I
DETAILED DESIGN.
000s.0E9U..UN-T TEST
DATA SASE CONVERSIONS (O)
SYSTEM INTEGRATION
I I
SYSTEM TEST
ACCEPTANCE TEST
OPERATIONAL EVALUATION
DELIVERY FIVE
SAFE C
(SAFE C a 0)
Ad
~
~
P011
A
OT
C PO
TF
MILESTONES
PRELIMINARY DESIGN
gCs
S
FQ
O'
DETAILED DESIGN
SAFE 0
COOE.DESUG.UNIT TEST
DATA SASE CONVERSION$ (0)
SYSTEM INTEGRATION
SYSTEM TEST
ACCEPTANCE TEST M
I I
n
OPERATIONAL EVALUATION
SYSTEM.INTEGRATION
I--y
SYSTEM TEST
RI
ACCEPTANCE TEST
O
Approved For Release 2008/06/11: CIA-RDP85BO1152ROO1001310002-2