REVISIONS/EXPANSION OF THE DATA REQUIREMENTS DOCUMENT FOR PRIM RELEASE 2

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP88-00893R000200060002-5
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 30
• Document Creation Date: December 16, 2016
• Document Release Date: July 19, 2005
• Sequence Number: 2
• Publication Date: June 21, 1984
• Content Type: MF

Approved Focelease 2005/08/02: CIA-RDP88-0089OR000200060002-5
21 June 1984
MEMORANDUM FOR : C/ C S D/ O C
SUBJECT . Revisions/Expansion of the Data Requirements Document
for PRIM Release 2
2.1.2 Component Data has been expanded for Release 2 of the
PRIM System.
The following items were revised or deleted from the overall
document:
1. Remove'reference to MAINID and SFN data lists.
2. Remove references to COMVAD Dictionaries in
Release 2. -
3. Revise the number of_COMVAD Dictionaries in
Release 1.
4. Delete the section of statement that said
CEMLOC will be moved to HRS2 data base
"in 1983".
5. C ange normal hours of accessibility to the
PRIM System from 0800-1800 to 0700-2000.
6. Reflect new ODP organizations where applicable.
7. Change references from CAPER and CAPER/OP to IAPS.
8. Change references from PROGRAMDOC to PG'UIOC.
9. Change reference to query statements executing
longer than 3 minutes to 1 2/3 minutes.
PRIM TEAM
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
 Approved For RJase 2005/08/02 : CIA-RDP88-00893840200060002-5
C O N F I D E N T I A L
Personnel Resource Information Management
(PRIM)
Data Requirements Document
(DRD-C20-1B)
by
PRIM Project Team
ODP/MISG/ISD
OP/ID/ADRB
25X1
Approved For Release 2005/08/02 : CIA-RDP88-00893R000
 Approved For el&spe 0b510i)0i :bITA-hD'Ph-0089 0020 b
984
0p b-~ A - 1 B
CHAPTER
PAGE
1.1
Purpose . . . . . . . . . . . . .
. . . . . . . . . . . .
1
1.2
Scope . . . . . . . . . . . . . .
. . . . . . . . . . .
1
1.3
References . . . . . . . . . . . .
. . . . . . . . . . . .
2
2.1
Input Data . . . . . . . . . . . .
. . . . . . . . . . . .
5
2.1.1 External Systems . . . . .
. . . . . . . . . . . .
6
2.1.2 Component Data (Release 2 &
4) . . . . . . . . . .
18
2.2
Output Data . . . . . . . . . . . . . . . . . . . . . . .
20
2.2.1 Data Transfer Between Components (Release 1) . . .
20
2.2.2 Queries and Reports . . . . . . . . . . . . . . . .
20
TABLE PAGE
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L ii
 Approved For R %21Q05i/(j8/]P2r fql FTDRB?-00893RQ0 209469993- 984
DRD-C20-1B
Chapter 1
1.1 PURPOSE
The purpose of the Data Requirements Document (DRD) is to identify
during the Initiation Phase of software development, data groupings
applicable to the PRIM System's data requirements. This approved DRD
establishes a foundation for the definition and design of the Initial
Operating Capability (IOC) of the PRIM System. This document will be
used in developing the PRIM Data Specifications Document during the
Preliminary Design Phase.
1.2 SCOPE
This DRD addresses data requirements in terms of groups and types of
data input to and output from the PRIM System.
All of the requirements will not be satisfied in the IOC of PRIM.
Some of the data requirements from external systems are not within the
current scope of the PRIM System; consequently, they are excluded from
the requirements to be satisfied by the PRIM System at this time. The
data requirements to be satisfied but not included in the IOC will be
satisfied in a phased approach with each phase identified as a new re-
lease of the PRIM System. This DRD will be updated with the appropri-
ate detail requirements for each release of the PRIM System. The IOC
is Release 1 of the PRIM System.
This DRD consists of two Chapters:
This chapter presents the purpose and scope of the PRIM DRD and
all references applicable to the contents of the DRD.
2. Data Description
This chapter describes the input and output data requirements
logically grouped by functional use and subject matter of the
data.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L
1
 25X1A Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
 Approved For Rye@s@ 2,PQ5/08t0% :1CIA-RgrQ$ -00893RW02Q Q0Q(} Q,2-?i984
DRD-C20-1B
In addition to the documents identified in Table 1, the PRIM
Project Team utilized the following Publications and Reference materi-
al in writing this Data Requirements Document:
1. ODP Applications Documentation Standards
2. FIPS PUB 38, U. S. Dept of Commerce (NBS), 15 Feb 1976,
'Guidelines for Documentation of Computer Programs and
Automated Data Systems'
3. Data Catalogue II, System Overview Manual, 25X1A
F __1
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 3
 Approved F5rRe"eN2QOq/G/Q2N CTiPq Wl~ 88-008 00014099990444
DRD;C20-1B
Chapter 2
Overview
The PRIM System must.be a centralized data base for use by the ?erson-
nel Officer, areer Management Officer, Office Director, or Training
Offi:er of a omponerit:' in direct support of the component's day-to-
day :personnel management activities.
The query and reporting requirements for the PRIM System n~ed
data related to organizational structure, position information,, and
employee date. The majority of this data currently exists in the Hu-
man Resources System (HRS2 Data. Base) of the Office of Personnej (OP),
and -;herefore2 is considered data. to be transferred from an external
system into the PRIM System. Eight other external systems also'
t:ain data requested to satisfy these .requirements. Other query and
repo:.-t requirements identified by many of the components surveyed are
for data not urrently available for all components in a computerized
system. The: queries and reports of component data will be us4d by
the componen for planning personnel assignments, Career Management
tasks, and Di ectorate-'Level reports. See Section 2.1 on Page
Components must have the capability to generate their own online
queries or re orts, offline reports, or graphs. Office of Personnel
reports will onti:nue to be the official reporting mechanism forcom-
ponents repo-- ing to Directorate-Level. See Section 2.2 on Page 20
This centralized data base will be used for decentralized query
by component ffices for all people assigned to their component lor
haying that c, mponent's career service designation. Security must
control all 1,1e read and/or write accesses to the PRIM Data Base as
appropriate.
All of 1: ese Requirements will not be satisfied in the IOC of the
PRIM System ( elease 1). The requirements will be satisfied in a
phased approach with each phase identified as a new release of the
PRIM System. This will provide the basic capabilities early an( 3 build
upon those ca abilities until a final operating capability (FOC)I is
operational. This methodology will deliver a viable system to the
L The term co onent in the. context of this document is defined ~as a
separate en ity :in the Agency's organizational structure be it a di-
rectorate vel, an office, a staff, a division, a service, or a
center.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D :B N 'T I A :L 4
 Approved For RWgase 4015/Q84922: gl4c-FIDR8j-00893RQg020 P6%9 -?984
DRD-C20-1B
user in a much shorter time frame than if all of the capabilities were
developed as one release.
2.1 INPUT DATA
General
The PRIM requirements identify the need for a centralized data base of
organizational, position and employee data currently resident in ex-
ternal systems. The centralized data base must have the capability
for components to access the data for queries and reports, as well as,
the capability for components to enter, update, and retrieve their own
component data2.
External Systems
The majority of the data. needed to satisfy the query and reporting re-
quirements of the PRIM System exists in the Human Resources System
(HRS2 Data Base) of the Office of Personnel (OP). To ensure the in-
tegrity and performance of the HRS2 Data Base, the data must be trans-
ferred from the HRS2 Data Base and loaded into the PRIM Data Base.
This data loaded into the PRIM Data Base cannot be updated by the com-
ponents and can only be changed by another extract from the HRS2 Data
Base. See Section 2.1.1 on Page 6 for the detailed requirements.
The requirements for data resident in the eight other computer
systems external to the HRS2 Data Base will not be satisfied in the
current planned releases of the PRIM System. See Section 2.1.1.5 on
Page 17 for more detailed information.
Component Data
Other requirements identified by many components are for data not cur-
rently resident in a computerized system available to all components.
Some components have systems to support a portion of their needs, but
these systems are strictly for their use. The components need work
files to assist them in their activities related to:
1. Planning and projecting personnel assignments into the future,
2. Directorate-Level reporting such as resources expended for de-
fined target areas over a specific period of time, and
2 The term component data refers to any data not transferred into
the PRIM System from an external system thereby, requiring data en-
try by the components of their own data.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 5
 Approved F e--W-(N2p0 /Q18/.Q2N (;IA-WQ88-00893R000240 90944
DRD41320-1B
i
3. Career
rankin
The PRIM
to enter, updi
Because
will not be s
t.er.
Refer to
ment,s.
Management tracking of competitive. evaluation ratings/
S.
System must provide an online capability for a component
to (add, change, delete), and retrieve this data.
f limited requests, some component data requirements
tisfied in the current planned releases of the PRIM Sys--
Section. 2.1.2 on Page 18 for the Component Data require-
Data File Sum
The DBMS must
support queries and reports requesting data from illy to
30 different
ser data fil
s utili
i
a
f 70
i
i
dit/
alidati
e
z
ng
m
n
mum o
e
v
on
dictionaries.
These are not all. needed. in Release 1; the following
list identifi
s the projected number
o
f files for each release:)
1.
Releas
2.
Rele.a;s
3.
Releas
11
data
files,
5
dictionaries
4.
Releas
1
data
file.
5.
Releas
2
data
files.
This is
exclu
ive of any data
files
required to satisfy the Security
:Requirements .
.2. 1. 1 Extern a
The data requ
formation res
i.nfo:cmation rr
Online read/w
potent level.
from the Off.i
quireaments fo
HRS2 Data wil
the HRS2 Data
the :?RIM Sys:
Systems
reme:nts for the PRIM System covers a wide range of in-
dent in a large number of systems. The majority of the
quired for the PRIM System is in the HRS2 Data Base.
ite access to the HRS2. Data is not available at the com?-
Howcaver, components do receive reports of the HRS2 Data
e of Personnel on a periodic basis. To meet the e-
queries and reports at the component level, specific
be transferred to the PRIM Data Base. The transfer of
must be phased to correspond to the planned releases of
M.
Apprdved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
I C O N F I D E N T I A L 6
 Approved For R*lie;fs? 2QOS/Q8/102E: CIA-RDR
A. HRS2 Online Access
-00893R4020ff6QQ -J 984
DRD-C20-1B
The HRS2 Data Base is a GIMS II online system resident in the Ruffing
Computer Center at Headquarters Building. Online access to the HRS2
Data Base is limited to:
1. Office of Personnel employees responsible for Data Collection,
2. Nine Offices responsible for Data Collection of Training data,
3. Office of Personnel employees responsible for the data integri-
ty,
4. Office of Personnel employees responsible for online updating
5. Office of Personnel employees responsible for online reporting
and ad hoc queries,
6. Office of Training and Education for updating Language Incen-
tive Awards and requirements for Language Units.
7. Central Cover Staff for query of selected files,
8. Office of Finance for query of selected files, and
9. Office of Communications for extracting data for OC personnel
from selected files.
B. HRS2 Reports
The official OP reports are produced from PL1 programs and from a
RAMIS Data Base generated by loading an extract tape from the HRS2
Data Base. These reports are used by all components and are produced
on a predetermined schedule. Unfortunately, the shortest frequency
for the PL1 reports is every two weeks. The components require this
information on a more current basis.
C. HRS2 Data to be Transferred
The PRIM Data Base will be comprised of data from the following HRS
projects:'
1. PERSIGN - Personnel Assignment and Status Information
2. STAFFING - Organizational and Position Structure
3. PERFIT - Performance Appraisal Callup and History
Records
3 PERSTEP and COMCON are part of the HRS2 Data Base, however, they
will not be included in PRIM. Some selected items from PERSTEP are
resident in PERSIGN, and therefore, they will be available in PRIM.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 7
 Approved Fr ebeaq 2100i5/Q8L2N: (PIAi-F DE88-008J R0002DQA00OII354
DRDC20-1B
4.. CENQUAI~ - Central Qualifications (Experience, Language
Capabilities, Education, etc.)
6. PERSEA
7, TRAIN
8. COMVA])
- CIA Retirement and Disability System
- Historical Record of Overseas Assignments
of CIA Employees
- A data collection file for Internal and
External Training
Common Validation dictionaries for input
data validations and to retrieve text
fields for queries and reports.
- Career Training Program
D. Phased D; a Trans.fc:r
The -transfer
must be accom
this data to
leases of thi3
1. The mo
ed for
ORGCOD
tionar
(Sect i
3. The re
Proje,:
(QUACO
HRS2.
(Secti
4. The pl
cat ego
(Secti
Other P
external to t
the :PRIM Syst
from existing
Non.-::: RS data
1. CENBAD
2. CENCO
3. MEDSI3
f data from the HRS2 Data Base to the PRIM Data Base
lished by identifying groups of data, and then prdviding
orrespond with the phased approach of the multiple re-
PRIM System. The groups of data are:
t frequently requested HRS2 Data and the HRS2 data need--
query: NAME, PERSIGN, QUAL (Active), HPOSNR, LREQID,
, POSNR, STRENGTH, and supporting COMVAD validation dic-
es.
n 2.1.1. can Page 9)
ragraph deleted.
u.ested HRS2 Data, resident in the following HRS
s: CEMLOC, CIARDS, CTP, PERFIT, PERSEAS, CENQUAL
), and TRAIN. CEMLOC is scheduled to be made par
n. 2.1.1.3 on Page 13)
nned/new HRS2 Data. LAPS is the only project in this
y at this time.
n 2.1.1.4 on Page 16)
M data requirements were identified from eight systems
e HRS2.Data Base. At this time, the current plans for
m do not include satisfying the requirements for data
computer systems outside of the HRS2 Data Base. The
equeste'd resides in. the following systems:
- Central Badging and Credentials
- Central. Cover Computer System
- Medical Assignability and Examinee Control System
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
I C O N F I D E N T I A L 8
 Approved For RJ se 2QQ5/Q8t0Z: gig-FAD? -00893144O20p6A% 2-4984
DRD-C20-1B
4.
MINIGAP
- Abbreviated General Archives-History File
5.
Payroll
- Automated and Non-Official Cover Pay
6.
PERINSUR - Hospitalization and Insurance
7.
VIP
- Voluntary Investment Plan
8.
4C
- Community Wide Computer Assisted Compartmentation
Control System
Refer to Section 2.1.1.5 on Page 17
2.1.1.1 Data Transfers from the HRS2 Data Base (Release 1) - (M)
The PRIM System must receive data values from the most frequently re-
quested HRS2 data. lists, HRS2 Data Lists needed for query, and sup-
porting validation dictionaries. They are NAME, PERSIGN, QUAL (Ac-
tive), COMVAD, HPOSNR, LREQID, ORGCODE, POSNR, and STRENGTH.
1 1. This section deleted. 4
2. NAME - This Data List provides a cross-reference from the last
and first name to the individual's identifying number (SSN).
In the PRIM System, it will provide user access, via last and
first name, to various data lists which have the identifying
number as the data list identifier.
The previous and current names will reside in this data
list for a period of three years when there is a name change at
the employee's request, by court order or marriage, or change
from one pseudo to another. After three years the old name re-
cord will be deleted from the data list.
Approximate number of records currently are
pected growth per year ism (records.
4. PERSIGN - This Data List provides data on Agency employees for
basic status, assignment, pay and selected items on cover. The
file is organized primarily for online query but serves as the
basic report data list for current status, assignment and
--------------------
" This footnote deleted.
25X1 C
25X9
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 9
 Appr ved F e(sq42Q0?p/QQ/Q2N QlA-WL)88-008 0002Q0Q$_bQO$ 44
DRD+C20-1B
strength reports. The status and assignment data in MAI[TID for
active employees is updated only by PERSIGN.
Approximate number of records currently are
pectei growth per year is minimal.
5. QUAL (Active) - This Data List provides CENTRAL QUALIFICATION
DATA a active and some former Agency employees i.e., general
qualif cation data, geographic area knowledge, foreign language
abilit , personal,, dependent., and foreign relative data;'.nodern
langua e aptitude test scores (PLAT), military service qu.es-
tionna re information, and language incentive awards data. It
also c ntairis data necessary for Biographic Profiles. Tike file
is organized for online query. Data is maintained in code form
only. Release :l will provide PRIM users access to 5 QUAL-re-
lated OMVAD dictionaries (identified below) which will allow
the cc ponents to retrieve the text fields for queries and re-
ports rom the dictionary codes.
Approximate number of records currently are for
QUAL active employees. Expected growth per year is minirhal.
1 6. COMVADI Dictiona:-ries
1. $9 E Age Group Code and Text for Ages 15 to 99
2. $A LV Annual Leave Category
3. $A TYST Annuity Status
4. $A EA Geographic Knowledge Specialization
5. $A EXT Extent of Area Knowledge
6. $C DREL Relationship Code
7. $C STAT
8. $ti PCL
9. $D VCO
10. $D AFTS
11. $E TENT
12. $F G
13. $F SA
14. $F CALL
Status Code
Career Training Program Class Number
Development Complement
Draft Codes
Extent of Education or Experience
Federal Employee Group Life Insurance.
Fair Labor Standards Act.
Annual Fitness Report Call-Up Schedule
25X9
25X9
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
I C 0 N F :[ D E N T I A L I 10
 Approved For Fagsg 2Q5/Q8#Q2: elf@--F DPU-00893RQ802(A0QP2-f)984
DRD-C20-1B
15. $FRQCON
16. $FTNE
17. $FUNCTN
18. $GAPOCC
19. $GAPOFF
20. $GAPSD
21. $GEOG
22. $GOVT
23. $HCAP
24. $HQS
25. $LANG
26. $LANSCR
27. $MARST
28. $MILSEP
29. $MILSVC
30. $MOBCAT
31. $NATION
32. $NEWLOC
33. $NOTACT
34. $OCCSTA
35. $OCCUP
36. $OSCAT
37. $PBASIS
38. $PERACT
39. $PERAFF
40. $PERCIT
41. $PERSAL
Frequency of Contact
Position Footnote
Function
Occupational Code and Sequence Number
Codes and Texts of Office Acronyms
Historical Data on Service Designations
Geographic Knowledge/How Acquired
Government Organization
Handicap
Headquarters
Language Specialty/Proficiency
Foreign Language Scores
Marital Status
Military Separation
Military Service
Mobilization Category
Nation
Location Code
Notification of Action
Occupational Status For Dependents
Occupational Series
Overseas Category
Pay Basis
Action Required
Affiliation
Citizenship
Schedule, Grade, Step Concatenated
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 11
 Approved Fr 1Re"eN2@0q/q$/Q2j7 QlPt g,88-0081
42. $P RSCH.
43. $P VT
44. $P A
45. $P OJNC
46. $R CE
47. $R LATN
48. $R MT
49. $S C
50. $S HGR
51. $S
52. $S CCL
53. $S PC0
54. $S PG0
55. $S PREA
56. $S URCE
57. $S ECS
58. $S REF
59. $S FFIX
60. $'r UR
61. $'r ANSL
62. $':C MSEP
63. $'V T
ooo qoN, 904 g4
DRDI-C20-1B
Pay Schedule
Previous Civilian Government Service
Personnel Rank Assignment.
Project Numbers
Race Code
Foreign Relatives Relationship
Retirement System
Subcategory
Schedule Grade Concatenated
Career Service. Designation
Security Clearance. Type
Separation Contact:
Separat ion Where Going
Separation Reason
Source of Experience or Area Knowledge
Education or Work Specialty
Special Reference
Occupational. Series Text Suffix
Duty Tour
Translator Experience Code
Type of Military Separation
Veterans Preference
7. HPOSN3 - The HPOSNR (Position History) Data List contain all
the d3 eted pds:.tion records in the Agency. These records are
mainta ned from the system start-date (August 1974) only, The
identi ier cif each record is the, position. number.
A-3 proximate number cords currently arel Expect-
ed growth per year is ,:n records.
Appr ved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 12
25X9
 Approved For RQjp?se 2QQ5/Q8t0Z: cIi -I DW
-00893RQQ0200UM-?984
DRD-C20-1B
8. LREQID - The LREQID (Language Requirements) Data List contains
all the valid organization units with Language Requirements in
the Agency. The identifier is the organization code (ORGCODE)
concatenated with the identification number for organization
language records.
Approximate number of records currently are
ed growth per year is minimal.
Expect-
9. ORGCODE - The ORGCODE (Organizations) Data List contains all
the valid organization records in the Agency (8 levels), plus
deleted office records that still have PERSIGN employee records
associated with the office. In addition, it identifies Agency
position personnel ceilings levied on Directorate (Level 1) and
Office (Level 2) organizations, together with the Language Re-
quirements imposed on various organizations.
Approximate number of records currently are
pected growth per year is minimal.
10. POSNR - The POSNR (Positions) Data List contains all the valid
position records in the Agency and identifies the personnel as-
signed to them. It is a unique number assigned to each posi-
tion on the Staffing Complement that is used to identify the
position and also used for assigning personnel to the position.
These numbers will never be re-used. The identifier of each
record is the POSITION NUMBER.
Approximate number of records currently are
pected growth per year is minimal.
11. STRENGTH - This Data List contains a MATRIX of CEILINGS,
POSITIONS and STRENGTH COUNTS of all active Agency employees by
ceiling count, by type and location of assignment by selected
types of employees by Office. The STRENGTH MATRIX is computer
generated as a result of ceiling/staffing changes and personnel
action processing.
Approximate number of records currently are 86. Expected
growth per year is 1 record.
1 2.1.1.2 This section deleted
2.1.1.3 Data Transfer of Remaining HRS2 Data (Release 3)
The PRIM System must receive data values from the remaining requested
HRS Projects: CEMLOC, CIARDS, CTP, PERFIT, PERSEAS, CENQUAL (QUACOM)
and TRAIN. CEMLOC is scheduled to be part of the HRS2 Data Base.
25X9
25X9
25X9
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 13
 Appr ved F~irRlRelpau;eN2Q0j/Q$/Q2M C IA- F 1?,88-008 R0002Q0QQq@0$5g4
DRD~C20-1B
1. CEMLOC - This p:coject contains Centralized Emergency and Loca-
tor Records for Agency personnel. (active and separa.ted).I, PRIM
users will have access to the following CEMLOC Data list
CE LOC data list provides information needed to locate,
contac or address personnel. at work or at home. It is used to
identi y and locate the person to be contacted in the event of
an emp oyee's illness, injury or other emergency.
LD LNAME data List contains the individual's last name and
social security number. It is used primarily to conduct'a
quick earch of a last name in the CEMLOC record.
A FIL, BLDG, KIN, ORG, and TITLE are data lists, but when
they c me into the HRS2 Data Base they will become COMVAD dic-
tionar es.
1. AFFIL data :List indicates the code and clear text of the
individual's relationship to the Agency.
2. BLDG data last:: contains abbreviated rnarne and full teat of
al Agency buildings or Agency occupied office space,withi:n
th greater Washington area..
3. KIi~ data list indicates the code and clear text of the re-
laf{ionship between emergency designee to the individual.
4. Oft data list contains the code, abbreviated text and full
tot of the individual's organizational code at the Office
le el.
5. TI LE data :List contains abbreviated titles and. clear text
us d to add:--ess an individual in business letters or'in an
in roduction, i.e., Mr., Mrs.., Dr., etc.
The CEMLOC 'project currently contains
II
2. CIARDS - The CIA Retirement and Disability System project is
comprised of 2 Data Lists.
T e CRDMAST contains active participants and employees re-
moved from the system.
Atproximate number of records are
II
'tHHIST contains CIARDS annuitants and deceased former
CIARD3 members, their survivors and terminated participants.
Approximate number of records are
3. CTP - this project provides basic data on all staff and 'on-
tract 4mployees (including both separated, employees and those
currea ly on duty) who have been enrolled in the Career trainee
25X9
25X9
25X9
Apprdved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
I C O N F I D E N T I A L 14
 Approved For R gsg 4VQ5/@8tQZ: Pig-RQR"-00893RQ?020XQ -?984
DRD-C20-1B
Program (CTP). The data list is designed to accommodate online
queries and the generation of CTP reports.
Approximate number of records are
II
4. PERFIT - This project tracks the Performance Appraisal records
by Social Security Number of record. PRIM users will have ac-
cess to FRCALLUP and FRHISTORY.
FRCALLUP has current and delinquent callup records along
with personnel information associated with the individual at
time of callup, (i.e., Schedule, Grade, Alpha Org).
Approximate number of records are
II
FRHISTORY contains fitness report response data (i.e.,
overall rating) and personnel data associated with that partic-
ular reporting period. Data is retained for 14 months and then
purged. The complete FRHISTORY file is maintained on an OP
offline data base and updated monthly.
Approximate number of records are
5. PERSEAS - This project contains all the Overseas Service that
has been reported to the Office of Personnel on an individual.
It is used to alert the Retirement Operations Branch of an em-
ployee who has 60 months of Overseas Service and could possibly
be a candidate for the CIA Retirement and Disability System.
PRIM users will have access to OSINDEX and OSHIST data lists.
OSINDEX is an index to the overseas history data list as
well as total overseas time to date. It contains data elements
that point to a specific OSHIST record as well as overseas data
elements that are unique to the individual and not to each of
his/her tours.
Approximate number of records are
OSHIST contains a separate record on every individual's
overseas tour(s). It also states whether the tour was credita-
ble or non-creditable.
Approximate number of records are
6. CENQUAL - The Central Qualifications Project contains six data
lists on active and terminated Agency employees. Release 1
provides data from the QUAL (Active) Data List. For a further
definition of the CENQUAL Project see Section 2.1.1.1 on Page
9, Item 5, QUAL (Active). Release 3 contains the QUACOM Data
List.
QUACOM data list provides free form text describing an em-
ployee's Special Awards, Commendations and listings of papers
25X9
25X9
25X9
25X9
25X9
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 15
 Appr
7. TRAIN
9 offi
ternal
ed qua
intern
offlin
peopla
from 3
or art
accomn
ployee
The ra
Person
ved Fd"r RelpOW290~/QQ/Q2N CTIAS We88-008000?Q0g?0Q0?fA4
DRD*C20-1B
Iles written, etc. The data list is designed to
date onl=ine queries and the data is reflected on the em-
s Biographic Profile Report.
proximate :number of records currently are
aining CENQUAL Data Lists are used only by the Office of
el and will not be transferred to the PRIM Project.
The TRAIN Project has online data collection files that
es presently have the capability to input completed in-
and external course data. The information is then load-
terly to the offline TRAIN file which contains completed
1 and external course data for Agency employees. The
file also contains internal courses taken by non4Agency
The o:ffline TRAIN! file contains training information
June 1975 to present.
line. TRAIN file contains approximately
II
Discussions a
HRS2 Data Bas
is developed
2.1.1.5 .
TAPS is
meat and the
I capability to
cessing from
Cancellation.
sential for
Transfer cif Planned/New HRS2 Data (Release 5)
e underway to have the TAPS System developed within the
The PRIM Project Team must plan for this system if it
ithin HRS, otherwise, TAPS will came under Section
preemployment processing system. TAPS provides manage-
perating levels within the Office of Personnel wily the
monitor and more effectively control preemployment pro-
nitial contact or resume to Entrance on Duty (EOD or
TAPS is designed to provide a statistical data base es-
e analysis of:
(1) Agen
(2) sped-
TAPS con
(AF S and CAPE,
terly basis.
AFS Data
data (30 item
mated growth
dividuals who
mate number o
is
Appr
y recruitment planning and control; and
al purpose research projects.
ains two years of data and is comprised of 2 Data,ists
). ;Records over two years are dumped to tape on a quar-
List basically contains interview, resume and status
). Approximate number of AFS records are Esti?-
a List contains biographic (PITS) and status data n in-
have been put: in process to EOD (113 items). Ap :roxi-
CAP1ER records a.relI Estimated growth for Y-82
imated growth for FY-83 and forward is rec :-ds
ved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I DEN 'T I A L 16
25X9
25X9
25X9
25X9
 Approved For Rjs@ gj0@5/p8fflg :?FQ-gC)P$,8-00893RW2QQOQQQQ2 t84
DRD-C20-1B
This requirement will be defined in detail in Release 5 of the
PRIM System.
Data requirements were identified from eight systems external to the
HRS2 Data Base. The data volumes were very low except for Payroll
data; however, a new Payroll System is under development and a query
capability is planned. For each of the systems, a separate interface
procedure would be required, in addition to separate coordination ef-
forts to plan and authorize each interface. Considering all of the
above, the current plans for the PRIM System do not include satisfying
the requirements for data from existing computer systems outside of
the HRS2 Data Base. However, since the requirements were surfaced,
the appropriate offices, as indicated below, will be notified of these
data. requests:
1.
Office of Security
1.
CENBAD
2.
4C
2.
Office of Personnel
1.
PERINSUR
2.
MINIGAP
3.
Office of Finance
1.
Payroll Systems
2.
VIP
4.
Office of Medical Services
1. MEDSIGN
5.
Central Cover Staff
1. CENCO
Data requirements were also identified for a small group of com-
ponent data that will not be satisfied in the current planned releases
of the PRIM System. Refer to Section 2.1.2 Component Data (Release 2
& 4) on Page 18 Item 'Unique Data Requirements'.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 17
 Appr ved Fir ReL~@0/0i$/f$2N Q1AgFR,88-008000QO( 90$44
DRDC2O-1B
2.1.2 Compoent Data (Release 2 & 4)
2.1.2.1 Pla ning; and Projecting Personnel Assignments (Release 2)
The requirement is to have a mirror like image of the Offilial
j file fields (ERSIGN, POSNR, ORGCODE) moved to the component fie
area. Based. n the selection criteria for that particular comp, rent,
data lists wo tld be created of PERSIGN, POSNR, and ORGCODE with new
fields (from elease 2 questionnaire) and reserve fields. The ompo-
nents require the add, change, and delete capability to key infprma-
Lion into the 3e fields if they wish the data to be different from the
official reco d. When the component acids a potential reassignment-in
record to the component file, a check must be made to ensure the SSN
is in the corn onents's SEGACCESS segment. If it is not then the los-
ing component must transfer the record to the gaining component which
would permit access to the record. If it is a potential. new EOD, a
check of SEGA LESS and PERSIGN would indicate no official record of
the SSN and t en the component could add the SSN. A flag would'',be
generated on field that,. is being changed by the component. Over the
weekend the linking procedure would be initiated and the offici l
files would b made current. The: fields in the official and the com-
ponent files ould then be compared. If the fields are different and
the component fields have no flag, the component. fields would be
changed to equal the official fields. If the fields are equal and the
I component fie ds have it flag, the flag would be deleted. If th
fields are different, ; and the component, fields have a flag, the compo-
nent fields are not changed.
A compare of the active SEGACCESS segment to the components
SEGACCESS segment would either add new SSNs (EODs) or delete SSNS
(separations which moved from PRIM PERSIGN to PRIMSEP). These rfecord.s
respectively would be added to or deleted from the component PERSIGN
file. This c mpare would also apply to POSNR and ORGCODE.
The comc vents require a user-friendly method of updating their
component fil s such as general purpose update menus which allow the
I users to sim_3 y enter the changes desired to their record fields.
There is a requirement: for a menu to enable the components to es-
tablish edits and validations for their reserve fields. This menu
would permit he components to use the same fields created for the
component fil s but establish unique edits and validations, e.g
length of fie d, rename the fields, alpha/numeric, for their specific
fields and s, --ore them in a file with a unique name using their S:ignon
I org. There should be a tie-in of their signon org to this fileHEor
I :retrieval purposes. Upon. updating their component: files, the update
menus must call in this, specific edit/validation file unique to,rrhe
component and use in conjunction with the input menu.
Apprcjved For Release 2005/08/02 : CIA-RDP88-00893R000200069002-5
II C 0 N F I DENT I A L 18
 Approved For Fd ese 4q5/Q8.tDZ: tq' lA-1RQP"-00893 2( 010QftW-?984
DRD-C20-1B
There needs to be a skeletal manning table menu that would
produce a basic manning table sorted by orgcode, position sequence
I number similar to the current Staffing Complement produced by the Of-
fice of Personnel. There is a requirement for the capability to add
or change the fields that print out on the manning table. Menus are
needed to simplify this capability. The requirement for creating a
component manning table is to pull both official and component data.
together to produce a management tool for planning purposes.
There is a requirement by some Directorates to utilize the compo-
nent data. There are also requirements from some components that the
Directorates not have access to their component data.
1. Career Management Activities (Release 4)
Components have levied requirements to store and track competi-
tive evaluation ratings/rankings for their careerists.
Approximate number of items are 60.
2. Unique Data Requirements
Some components would like to enter, update, and retrieve data
unique to their needs. These requirements are categorized as
unique because only one or a very few components requested the
data. Unique component requirements should be considered as
enhancements following the last planned release.
These previous requirements will be defined in detail in the appropri-
ate releases of the PRIM System.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 19
 Appr ved FiSr e"eM2Q0 /Q$/Q2N QIq We,,88-00 000 0 0
DRDrC20-1B
2.2 OUTPUT. ATA
The requireme is to provide data outside of the PRIM System are,
grouped into wo categories. Data must. be passed between components
for reassignn nt processing, and data is required for queries and re-
ports.
2.2.1 Data Trans.fer Between Components (Release 1)
Security rega rements for the PRIM System limit the access to individ-
ual records within. the PRIM Data Base; consequently, this has ienti-
fied the rega rement to pass data between components for indivi uals
being consider e.d for reassignment. Components must have access',to
data on employees who have been nominated for assignment to their com-
p one;lt .
2.2.1.1 Pot4ntial Reassignments - (M)
When an emplo ee has been nominated for reassignment consideration to
another compo ent, the losing component must be able to electro.ically
provide requa ted employee data from the PRIM System to the gaining
component. T is request must be initiated by the gaining compoz ant
and is limiter to the data available in the PRIM System. The roquest-
ed data will le basic employee data as is normally found in a Bio-
graphic Profi e Report.
2. 2.2 Quer i s and Reports
The output ree
data lists ar
the Personnel
Training Offi
tem :-eport ing
repo:-ti:ng reel
1, Compon
Sectio
2, Compon
Sectio
Compon
Sectio
4 Career
Sectio
Appr
uirements for reporting data from the components' ?RIM
varied. These outputs represent working tools used by
Officer, Career Management Officer, Office Directp:r, or
er of a component. Components plan to use the PRIM Sys.-
capabilities in their day-to-day management. Theloutput
irements are for:
nt generated online queries (Release 1),
2.2.2.1 on Page. 21 ,
nt generated offline reports (Release 1),
2.2.2.2 on Page 2.2 ,
nt generated basic graphics capability (Release l',
2.2.2.3 on Page 23
Management Reports (Release 4),
2.2.2.4 on Page 23 ,
ved For Release 2005/08/02 : CIA-RDP88-00893R00020006Q002-5
C 0 N F I DENT I A :L 20
 Approved For IjIigaW 0105109/ NG AjRPP?8-00893ti4002W4&MZ584
DRD-C20-1B
5. Directorate-Level Reports (Release 1),
Section 2.2.2.5 on Page 23 ,
6. Data Base Reports (Release 1),
1. Statistics,
Section 2.2.2.6 on Page 23
2. Exceptions, and
Section 2.2.2.7 on Page 24
3. Security,
Section 2.2.2.8 on Page 24
7. Data Dictionary Reporting
Section 2.2.2.9 on Page 25
Office of Personnel reports will continue to be the official
mechanism for components reporting to Directorate-Level.
reporting
2.2.2.1 Component Generated Online Queries (Release 1) - (M)
Components must generate their own online queries utilizing the stan-
dard User Language of the DBM System.
All components must be instructed to use Agency standard control/
classification labels for all online reports.
Examples of the type of online queries are:
1. List the Position, Schedule, and Grade of an employee to insure
the proposed assignment conforms to OP mandated Assignment Con-
trols.
2. Count Positions of a selected Occupational Series.
3. Counts of LWOP Cases and NTE Dates.
4. List date of last change to a Position.
5. Count of vacant positions.
6. List the date a position was officially deleted.
7. List Daily strength for:
1. Part Time
2. Full Time
3. Dev Comp
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I D E N T I A L 21
 P 8-0089'3'R'0002 0
Appr ved For ele[agp. RO954OJO TCkp4 Pl? ++ q4
992I;84
DR! -C20-1B
4. ?mot OP
5. 1) tails In/Out
6. Sick Leave (Approved for Disability Retirement)
8. List he Service Designation of a position versus the .iIcum-
bent.
9. List he Subcategory Code of a position.
'.0. List elected Cover Items.
1.1. List LSA Designation of :Employee.
12. List rojected WGI to ascertain whether to hold a promotion un-
til t e WG] is granted.
2.2.2.2 C4onerit Generated Offline Reports (Release 1) - (M)
All PRIM offl
tion labels.
Componen
writer is req
lizing an Eng
guage. The r
levels, arithi
ing the basic
Examples
To pry
analyt
and
2. Compoz
To pro
duty
with
schedu
To pro
sorted
ployee
Appr
ll
the reports must use Agency standard control/class
ifica-
s must generate their own off line reports. A report
ired capable of simple listings and complex formats uti-
ish??like language similar to the RAMIS Reportwri.t r La.n-
port: writer must support: sorting and totaling of ip to 6
etic calculations, and unlimited selection logictiliz-
Booleai operators, e.g., AND and. OR.
of the types of off line reports needed are:
rate-Level Statistics
uce reports such as a Branch's production activities or
cal resource expenditures for a given period of tme,
nt Level Reports
uce reports of a component's active employees with a
ur of part-time, sorted alphabetically by last na e,
e emE:cloyee's type of duty tour and number of hour
ed to be worked, and
uce a report of a component's active staff employes,
by station location, and sorted alphabetically by,em-
s last name, and.
Management Reporting
ved For Release 2005/08/02 : CIA-RDP88-00893R00020006QO02-5
C O N F I D E N T I A L 22
 Approved For ReiedF;e(2005108/Q2 EQ~AfRk)P 3 00893RQQ5200R60Y0 251984
DRD-C20-1B
To produce reports such as a listing of a particular schedule
and grade level with a specific career service designation, as-
signed to a particular area, and sorted by date of grade.
2.2.2.3 Component Generated Basic Graphs (Release 1) - (M)
A basic graphics capability is required to produce very simple graphs
utilizing 2 dimensions (x,y axes), and portraying either bar or con-
nected point-plot representation of multiple variables in a vertical
or horizontal layout. This capability must not be less than what is
available in the RAMIS Basic Graphics package.
An example of a typical graph is a Competitive Evaluation Profile
Graph. The graph lists the evaluation criteria on one axis, the point
values on the other axis. All evaluated employees are identified to a
particular peer group. Each peer group is represented by a graph
showing the total counts for that group of how people were rated and
printed at the appropriate intersection of the x and y axes.
2.2.2.4 Career Management Reports (Release 4) - (M)
The PRIM Project Team must develop and format standard Career Manage-
ment Reports to be used Agency-wide. This requirement will be defined
in detail in Release 4 of the PRIM System.
2.2.2.5 Directorate-Level Reports
Directorate-Level Reporting is available in Release 1 by utilizing the
component retrieval capability with the HRS2 data transferred into the
PRIM System. Release 2 extends the capability to include the data en-
tered by the components for planning personnel assignments. Release 4
continues to extend the capability to include the data entered by com-
ponents for Career Management activities.
2.2.2.6 Data. Base Statistics (Release 1) - (M)
Daily Data Base statistics are required for the PRIM Data Base Manag-
er. The PRIM Data Base must be in sync with the HRS2 Data Base at the
beginning of business each day for each data list loaded to the PRIM
System.
This report should be similar to the current GIMS II Data Base
Statistics Report for the HRS2 Data Base. The list should be alphabe-
tized by the PRIM Data List name of all Data Lists loaded into the
PRIM System, and identify the Data Base and Data List names of the
Approved For Re"e N2005/0D8/0E 2~: CIA-RDP88-00893R000200060002-5
23
 Appr ved Rpl"r fQ> JOB :7CIA 2f P88-008 3R000200A6 002
DRD- 20-1B
originating sy tem. This list should include at a minimum the number
of items in ea h Data List on the PRIM Data Base..
2.2.2.7 Data Base Exception Report (Release 1) - (M)
A daily Data Base Exception Report is required to identify query'
he re--
st~te:ments executing longer than 1 2/3 minutes (100 seconds).
port should -- elude at a minimum the following data:
1. Data 13 se Name,
2. Data List Name,
3, User Went if icat; ion,
4. Termia 1. Ident i icat ion,
5. User Organization,
6. Date aid Time of exception,
7. Transa tionn numbe:c, and
8. Verb e ecut:ing.
2.2.2.8 Df_ta Base Security Reporting (Release 1) - (M)
The PRIM Sys
ager identif
PRIM System
The vio
similar to
identify who
lations. T'1
1. Data 1
2.. User
3. Termi:
4. Date
5., If ap
Appr
em must provide daily reports to the PRIM Data Base Man-
h
e
ing any violations of established access control Io t
nd the standard ACF2 violations report.
ations of established access control report should be
e HR52 Data Base report. It should. be provided daily and
has been forced off the PRIM System after 3 security vio-
report should list at a minimum:
ase Name,
dent if icat:i_on,
al Ident if:ication,
nd Time of violation,
ropr. iate,
ransacticn Number, and
ved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
CONF 1I)ENTIAL 1 24
 Approved For RJase ZQQ5/Q802 : CI A-.F DR8jo-00893RQ,p020:0Q6 ,Q,?-$984
DRD-C20-1B
2.2.2.9 Data Dictionary Reporting (Release 1) - (M)
The PRIM System must have a Data Dictionary software package to store
and report information about data entities, definition entities (ob-
jective, requirement, function, specification) and associated. data
processing functions. It must provide a means of relating entities
and functions similar to the current DATADOC and PGMDOC. It must also
provide for:
1. longer narratives on all entities,
2. security restriction, allowing only authorized updating, and
3. provide a more flexible reporting capability.
These requirements are similar to the capabilities available in the
Data Catalogue 2 System. This dictionary will assist ODP and OP ad-
ministrators in maintaining the system by serving as a tool in analyz-
ing the effects of proposed changes or needed corrections in the fu-
ture.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C O N F I D E N T I A L 25
 Approved Ffir Retews(N2p0f)/
17 (PWRPP88-00, 000_290,0Q,909944
DR:D-,C20-113
The classific Lion of this document is CO 'IDENTTAL because of the re-
cord sizes sp cif Led for the files within tl-,,a I-JRS2' Data Base. 111
othe:c section of this document are UNCLASSIFIED.
Approved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
C 0 N F I DEN 'T I A L 26
 STA
T
STAT
ROUTING AND RECORD SHEET
SUBJECT: (Optional)
Initiation Phase Documents for PRIM Release 2
FROM:
EXTENSION
NO.
PRIM Tram
2-E-21
DATE
STATIN
22 June 1984
TO: (Officer designation, room number, and
building)
DATE
OFFICER'S
COMMENTS (Number each comment to show from wh
NTL
RECEIVED
FORWARDED
INITIALS
om
to whom. Draw a line across column after each comment.)
1?C/CS
VCS
2-B-
Attached are the revised
2.
and/or expanded documents
for the Initiation Phase of
of PRIM Release 2. Any
3.
,questions, please call
4.
5.
6.
7.
B.
9.
STATINTL
11.
12.
13.
ATTACHMENTS:
Detailed System Require-
14.
ments Document
Data Requirements Document
15.
FORM
I-79610 "EDITION?s"Fpproved For Release 2005/08/02 : CIA-RDP88-00893R000200060002-5
ase 2005/68/02 CIA-RDP88-00893R\00 200060002-5
L