PRODUCTION MANAGEMENT AND CONTROL SYSTEM INTEGRATED STATUS REPORTING SYSTEM

• Document Type: CREST
• Collection: NGA Records (Formerly NIMA)
• Document Number (FOIA) /ESDN (CREST): CIA-RDP73T00325R000100030001-9
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 105
• Document Creation Date: December 28, 2016
• Document Release Date: June 4, 2008
• Sequence Number: 1
• Publication Date: June 1, 1967
• Content Type: REPORT

Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
PRODUCTION MANAGEMENT
AND CONTROL SYSTEM
INTEGRATED STATUS
REPORTING SYSTEM
USERS GUIDE
June1967
USAF AERONAUTICAL CHART AND INFORMATION CENTER
ST. LOUIS, MO. 63118
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
216
PRODUCTION MANAGEMENT
AND CONTROL SYSTEM
INTEGRATED STATUS
REPORTING SYSTEM
STAT
USERS GUIDE
June 1967
USAF AERONAUTICAL CHART AND INFORMATION CENTER
ST. LOUIS, MO. 63118
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
The information contained in this publication is presented for the
guidance of ACIC personnel in preparing the input documents required for
Phase I of the Integrated Status Reporting System. At the present time,
the guide is incomplete. It will be complete with the addition of the
section explaining the error codes.
As explained in the preceding paragraph, the Users Guide has been
developed to assist in the preparation of the input documents and handling
of the discrepancy reports. It does not attempt to affix the responsi-
bility for the completing of the various forms; this information will be
supplied in the division and plant procedures being developed by members
of the PROMACS, ISRS Phase I Implementation Team.
The sample Job Plan designed for photo services is not included
in this paper. It was still undergoing final coordination at the time the
exhibits were drawn.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
TABLE OF CONTENTS
Section
Pa
e
g
1.
Introduction
1
2.
Input Documents
3
2.1
Introduction
2.2
Record of New Assignments
4
2.3
Authorized Job Master Change Record
7
2.4
Completion/Cancellation/Suspension Record
12
2.5
Job Plan Record
15
2.6
Job Plan Change Record
22
2.7
Cost Change Record
28
2.8
Milestone Change Record
32
2.9
Movement Routing Record
36
2.10
Status Record
39
2.11
Daily Labor Card
2.12
Skill Extension Card
2.13
Production Schedule Card
2.14
Program Category Card
2.15
Skill Rate Card
2.16
Validity Tables
2.17
Allocation Adjustment Record
2.18
Chart Completion Card
2.19
A B Card
3.
Discrepancy Codes and Reports
3.1
Introduction
72
3.2
General Information
72
3.3
Discrepancy Codes
75
3.4
Discrepancy Reports
89
3.5
Discrepancy Reports Template
91
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
i
Exhibit Page
2-1 Record of New Assignments 6
2-2 Authorized Job Master Change Record 11
2-3 Completion/Cancellation/Suspension Record 14
2-4 Job Plan Record 21
2-5 Job Plan Change Record 27
2-6 Cost Change Record 31
2-7 Milestone Change Record 35
2-8 Movement Routing Record 38
2-9 Status Record 41
2-10 Daily Labor Card 44
2-11 Skill Extension Card 47
2-12 Production Schedule Card 50
2-13 Program Category Card 53
2-14 Skill Rate Card 55
2-15 Quality Table 58
2-16 Operation Table 59
2-17 Function Table 60
2-18 Skill Table 61
2-19 Organization Table 62
2-20 CIP Line-Item Table 63
2-21 Allocation Adjustment Record 66
2-22 Completion Card ATM 69
2-23 A B Card 71
3-1 Activity Edit Discrepancy Report 92
3-2 Status Master Discrepancy Report 94
3-3 Resource Allocation Edit Discrepancy 97
3-4 Resource Allocation Master Discrepancy Report 98
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
1. Introduction
1.1 Purpose
The purpose of this document is to provide ACIC personnel with
information concerning the input required for PROMACS, Integrated Status
Reporting System, Phase I. The document is designed to provide the user
with the information necessary to prepare the input documents and to
interpret the error messages that result from the edit and update routines.
1.2 Organization
The paper is divided into three main sections. The Introduction
briefly summarizes how the system works. The Input Document Section
describes the purpose of the input documents, what the data fields. should
contain, and how the information will be edited. The Discrepancy Section
will list the error codes assigned by the edit and update programs, explain
the meaning and significance of the error message and explain the necessary
corrective action.
1.3 System Objectives
Phase I of the Integrated Status Reporting System is designed
to provide status information concerning individual assignments and the
fiscal year program. The status of individual assignments is shown on
weekly reports. Resource utilization and fiscal year progress is reported
on a series of monthly and quarterly reports.
The'status of an assignment or the fiscal year program will be
reported by the comparison of planned data and actual data. Planned data
is entered into the system by means of the Job Plan Record and the Skill
Extension Card. Actual data is entered by means of the Daily Labor Card,
Completion/Cancellation/Suspension Record and the Movement Routing Record.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
is
?
Authorization is given for a new job identification code by
means of the New Assignment Record. This record must be received before
any other records are accepted. Before any actual charges are accepted,
the planning data for the job identification code-organization combina-
tion must be on file. This means that a job Plan Record must be prepared
by an organization before the other input records will be accepted. The
type of plan determines the amount of checking that will be done on the
various input records.
The type of Job Plan Record will also determine the level of
detail displayed on the output reports. Cost charges will be accumulated
and shown on the output reports at the same level of detail as the Job
Plan Record.
1.4 Related Documents
The Users Guide is one of a related series of publications.
For the complete documentation and procedures concerning Phase I of the
Integrated Status Reporting System, the following should be consulted:
1.4.1 The Programmers Documentation
1.4.2 The P&D Plant and Division Procedures
1.4.3 ACIC Regulation 171-1
1.4.4 Air Force Regulation 171-10
1.4.5 ACC Keypunch Procedures
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
2. Input Documents
2.1 Introduction
The purpose of this section of the Users Guide is to provide
a sample of each input document, explain the purpose of the document,
and define the system requirements for the document.
The sample input forms included in this document represent
the ACIC forms. There may be some difference between the sample documents
aid those issued by the Forms Control Office. However, the representation
is for all practical purposes, the same as the ACIC form will be when it
is printed.
The purpose of each input document is stated in general terms.
The mechanics of how the data is used, or who is responsible for the data is
not given. This information is given in other publications.
The system requirements explains each data element of the input
that is used by PROMACS. If the data element is not explained, it is not
keypunched from the form. The editing of the data elements is also explained.
?
3
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
?
2.2 Record of New Assignments
2.2.1 Purpose
The purpose of the Record of New Assignments is to:
o authorize a new job identification code
o provide a description for the job identification code
2.2.2 Requirements
The Record of New Assignments must be submitted prior to or
along with the submittal of any other input type. This is necessary because
all input records, except the type 2 Job Plan Records, are checked to see that
the job identification code was authorized.
2.2.3 Input Preparation
When preparing the Record of New Assignments, the following
should be observed:
2.2.3.1 Date
Enter as month, day and year. Only the last character
of the year should be used. The date will be used to help identify the input
record if it is rejected. It will also be used to indicate the date that
the job was opened. It will be checked for valid characters.
2.2.3.2 Job Identification
Use the standard eight character identification code.
All eight positions must be used. This is the code that all other input
records, except type 2 Job Plans, are compared to. The first 5 positions
are checked for a valid CIP line item. The last 3 positions are checked for
proper alpha-numeric characters,
2.2.3.3 Job Description
Any alpha-numeric combination may be used. Columns'
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
41, 42., and 43 of the description field are reserved for indicating
items that are to appear on the Plant Status Nav-Plan Report and the security
classifications or restrictions of these assignments.
In Column 41, use a 1 to indicate a new base assignment,
other than a 1:250,000 scale. Use a 2 to indicate a 1:250,000 scale new
base assignment. Use a 3 to indicate a revise/reprint assignment other than
1:250,000 scale. Use a 4 to indicate a revise/reprint 1:250,000 scale
assignment. For any chart series that is not to appear on the Nav-Plan
Report., use any number 5 through 9.
In Column 42, indicate the security classification of
In column 43, indicate the security handling restrictions
?
If the assignment is other than a chart series, the
positions should be blank. When writing the Job Description, care should be
exercised so that the description is not classified higher than SECRET.
Unclassified titles are desirable.
The Job Description field is checked to see that it
contains some data. It cannot be blank.
?
5 Revised 21 June 1967
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
PPOMACS RECORD OF NEW ASSIGNMENTS
DATE
MO DAY VR
ORGN FROM
CONTROL NO.
PAGE OF _._
JOB IDENT
JOB DESCRIPTION
ORGN TO
6
1
91
01
10
it
12
13
14
15
14
17
18
19 1
,201
21
22
23
u
25
2L
27
28
29
30
31
32
331
341
35
3L
37
30
39
40
41
42
43
i
i
~
i
i
i
I
I
I
i
' I
L
L
NAME E TITLE
SIGNATURE
ACIC JUONE 67 17 TEST
EXHIBIT 2-1 RECORD OF NEW ASSIGNMENTS
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
?
2.3 Authorized Job Master Change Record
2.3.1 Purpose
The purpose of the Authorized Job Master Change Record is to:
o reinstate cancelled, or completed.jobs provided
that they have not been cancelled or completed for more than two weeks,
o reinstate suspended jobs
o delete all the information associated with a job or job
identification organization combination, and
o change the job status, status date, job description, type
completion, completion date, or quantity fields.
2.3.2 Requirements
The Authorized Job Master Change Record must be used to reinstate
a cancelled, suspended or completed job. However, if the job has been cancelled
or completed for more than two weeks, it is removed from the data base. Therefore,
it is necessary to reinstate the job by means of the New Assignment Record.
Existing records may be changed or deleted but new records
may not be added to the file with this record.
When a job identification or a job identification-organization
combination is deleted from the master file, it is desirable that the cost
data associated with these records be removed first.
2.3.3 Input Preparation
When preparing the Authorized Job Master Change Record, the
following should be observed.
2.3.3.1 Transaction Date
Enter as month, day, and year. Use only the last
character of the year. The field should be all numeric. The transaction date
is used to help identify the card should it be rejected. The field is checked
for valid characters.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.3.3.2 Job Identification
Enter the standard eight character job identification.
All eight positions must be used. This field is used as a control field
for the record. It must match an existing job identification code on the
master file. This field cannot be changed or deleted with the type change C.
2.3.3.3 Organization From
Enter the code of the organization submitting the input.
This field will be blank if the change or deletion is to apply to
the entire job and not just the job identification-organization combination.
When the organization code appears, it must match with an existing organization
on the master file for the job identification code. This field cannot
be changed or deleted with the type change C.
2.3.3.4 Job Status
Enter one of the following numbers:
1 = open
2 = suspended
3 = cancelled
4 = completed
This field may be blank, or it must contain one of the above numbers. This
field may not be deleted with the use of the type change C.
2.3.3.5 Status Date
Enter as month, day, and year. Use only the last
character of the year. This field may be blank. It cannot be deleted with
the use of the type change C. It is checked for valid numbers.
2.3.3.6 Job Description
Any alpha-numeric combination may be used. The same
considerations described in the New Assignment Record should be observed.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
This field may be blank.
2.3.3.7 Type Completion
Enter one of the following numbers?
1 = section completion
2 = branch completion
3 = division completion
This field may be blank. If the Completion Date field is not blank, this
field cannot be blank. When the type completion is changed to a lower
level completion, all organizations involved with the change must submit
this change. The field is checked for valid numbers or blanks.
2.3.3.8 Completion Date
Enter as month, day, and year. Use only the last
character of the year. This field may be blank. It is checked for valid
numbers.
2.3.3.9 Quantity
Enter any number of six digits or less. The field
may be blank. It is checked for numeric characters. The numbers must be
right justified.
2.3.3.10 Type Change
Enter either a C or D. To change any field other
than the Job Identification or Organization From, enter the correct data in
the proper field and use the type change C. To delete one or more fields,
but not those stated above, use the type change C and enter a zero (0) in the
appropriate field. The zero must be right justified.
To delete the job identification or the job identification
organization combination, use the type change D. Other than the control fields,
the rest of the card must be blank.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
When the type change D is used, all data associated with
the job identification or the job identification-organization combination will be
deleted from the master file. Cost data that is still on the master file will be
removed and the deleted records will be printed on the Discrepancy Report.
2.3.3.11 Transaction Code
Enter 01. This field cannot be blank.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
CONTROL No.
EXT.
PROMACS AU
TlORIZED JOB MASTER CNANGE RECORD
ANS
DATE
JOB I D
OR6N
J STATUS
DATE
CO
D
MPL
ATE
T
y
M
O
D Y
A E
Y A
R
LINE
ITEM
S
P
E
C o
B
D
I
V
S
o
BS
RE
N T
C I
N
N
B M
S 0
a T
T N
S
D Y
A E
Y R
JOB DESCRIPTION
MM
N
T
D
Y A
R
QUANTITY
E
H
A
6
E
A
N
S
c
?
E
1
2 3
4 5
6 7
8 9
10 11
1213
1415
16 17
18 19
120121
122
123 2
25 26
27 28
830
31 32
33134
135136
137138
139
40 41
142143
144145
146147
IB 6
50 51
52 53
54 55
56 $7
359
61
62 63
64 65
66 61
68 6
9 7071
72 73
174
175176
177178
79 80
NAME & TITLE LEGEND. JOI.OPEENUS TYPE CSECTION COMPLETION CPE CCHANGE
HANGE
2,-SUSPENDED 2.- BRANCH D = DELETE
&-CANCELLED 3.- DIVISION
4.-COMPLETED
EXHIBIT 2-2 AUTHORIZED J?B MASTER CHANGE RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
?
2.4 Completion/Cancellation/Suspension Record
2.4.1 Purpose
The purpose of the Completion/Cancellation/Suspension Record
o section, branch, division, and plant completions,
o the quantity of items produced,
o cancellations, and
o suspensions.
2.4.2 Requirements
This form is required whenever a P&D Plant completion occurs,
or a job is suspended or cancelled. It may be used in lieu of a Movement
Routing Record to record section, branch, or division completions.
After a job is completed, or cancelled, input records will be
accepted for two weeks. After this period, all input documents referencing
the completed or cancelled assignment will be rejected. If the job is
suspended, charges will be accepted, but the user will receive a message on
the Discrepancy Report saying that the job is suspended.
2.4.3 Input Preparation
When preparing the Completion/Cancellation/Suspension Record,
the following should be observed.
2.4.3.1 Date
Enter month, day, and year. Use only the last character
of the year. The field should be all numeric. This date is used as the
completion, cancellation, or suspension date. It is checked for valid
numeric characters.
2.4.3.2 Organization From
This is the code of the organization that is responsible
for the completion, cancellation, or suspension. The code should consist of
12
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
two alphabetic and two numeric characters.
2.4.3.3 Job Identification
Enter the standard eight character job identification.
All eight positions must be used. This code must match a job identification
that had been previously established.
2.4.3.4 Action Code
This field is used to indicate what the input is to
1 = section completion
2 = branch completion
3 = division completion
4 = plant completion
S = suspension
C = cancellation
These are the only characters that can be used in
2.4.3.5 Remarks
Enter the number of items produced. The quantity
is used for the Resource Accountability System. This field will be checked
for numeric characters or blanks.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
PRO M ACS COMPLETION/CANCELLATION SUSPENSION RECORD
DATE ORGN FRot 1
CONTROL NUMBER
1
2
3
4
5 6
7?
a
9
PAGE OF
MO
DAY
YR DIVISION
BR
SEC
JOB IDENT
JOB DESCRIPTION
CODE
REMARKS
10
11 1
121
131
14
15
16
f7
18
NAME & TITLE
ACTION CODE LEGEND
I = SECTION COMPLETION
2 = BRANCH COMPLETION
3 = DIVISION COMPLETION
SIGNATURE
AC IC JUONE 67 19 TEST
4 = PLANT COMPLETION
S = SUSPENSION
C= CANCELLED
EXHIBIT 2-3 COMPLETION/CANCELLATION SUSPENSION CARD
/4
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.5 Job Plan Record
2.5.1 Purpose
The purpose of the Job Plan Record is to provide planning
data for the output reports, determine the level of editing of the other
input records, and to determine the level of detail appearing on the output
reports. This purpose is accomplished through three types of Job Plans.
2.5.1.1 Type 1 Job Plan is used to estimate the -nanhours
required for the job identification and/or function codes that make up the
assignment within one organization.
2.5.1.1.1 If the Job Plan is submitted for the
assignment by job identification and organization, the input records will
be compared to the appropriate validity tables for validation. The data
will be summarized by job identification and organization for reporting on
the weekly status reports.
2.5.1.1.2 If the Job Plan is submitted for the
assignment by job identification, function code and organization, the input
records will be compared to the Authorized Job Master File on these fields.
The remaining portion of the labor identification code, (operation, quality,
and skill codes) will be compared to the appropriate validity tables for
validations. The data will be summarized by job identification, function
code, and organization for reporting on the weekly status reports.
2.5.1.2 Type 2 Job Plan is used to estimate the manhours
required or to be allocated to a CIP sub-line item within one organization.
2.5.1.2.1 The input records will be compared to
the Authorized Job Master file for validation on the CIP line item and
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
organization. The labor identification code will be compared to the
appropriate validity tables for validation. The data will be summarized
by CIP line item and organization for reporting on the weekly status
reports.
2.5.1.3 Type 3 Job Plan is used to estimate the manhours
required for the job identification and operations that make up. any assign-
ment within one organization.
2.5.1.3.1 The input records will be compared to
the Authorized Job Master on job identification, labor identification and
organization for validation. The data will be summarized by job identifi-
cation, labor identification and organization for reporting on the weekly
status reports.
2.5.2 Requirements
2.5.2.1 There must be a job plan.for every organization
that is charging time to an assignment, both production and open assign-
ments.
2.5.2.2 Any one assignment can have a combination of type
plans submitted for it provided they are for different organizations.
2.5.2.2.1 An organization can have a combination
of a type plan 2 and any other type plan. A type plan 1 and 3 cannot be
submitted for the same job identification and organization.
2.5.2.3 All jobs that are to appear on the Plant Status
Nav-Plan Report require a type 1 plan with the function code or a type 3
plan.
2.5.2.4 Because of the nature of their work and their method
estimating jobs, job plans for photo services branches, will be additive.
16
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
This means that the manhour estimates submitted for a job, labor identi-
fication and organization combination will be added to the manhour estimate
for any like plan.
2.5.2.5 To change from type of plan to another type of
plan will require the following action.
2.5.2.5.1 To change from a Type Plan 2 to a
Type Plan 1 or 3 will require the submittal of the new plan.
2.5.2.5.1.1 If the change is to
replace the type 2 plan record, then submit a Job Plan Change Record
(See 2.6) to delete the Type 2 plan.
2.5.2.5.1.2 If the change is to
break out a specific assignment to permit detail reporting, then submit a
Job Plan Change Record (See 2.6) to reduce the number of estimated manhours
reported for the CIP line item through the type 2 Job Plan.
2.5.2.5.2 To change from a type Iplan to a type
3 Job Plan simply requires the submittal of the type 3 Job Plan records.
The computer will automatically adjust the data base.
2.5.2.5.3 To change from a detail plan (3 to 1,
1 to 2, or 3 to 2) to a gross plan will require the submittal of Job Plan
Change records (See 2.6) to delete the detail plans.
2.5.2.6 After the job plan has been submitted, any additions
or corrections must be submitted on the Job Plan Change Record or the Mile-
stone Detail Change Record (See 2.8).
2.5.3 Input Preparation
When preparing the Job Plan Record the following should be
observed.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
2.5.3.1 Date
The date the job plan is prepared. Enter the numeric
month, day, and the last digit of the year. The date is used to help identify
the record should it be rejected.
2.5.3.2. Job Identification
If a type 2 Job Plan, enter the five character CIP
line item code, leaving the last three or low order positions blank. If
a type 1 or type 3..plan, enter the eight character job identification code as
shown on the Daily Record of New Assignments.
2.5.3.3 Type Plan
Enter the type plan code of 1, 2, or 3. This field
cannot be blank.
2.5.3.4 Organization
Enter the Division, Branch and Section code of the
organization that will be working on the assignment.
2.5.3.5 Line Code
This field is numeric and is used to sequence the
data within job and organization for reporting on the Section-Branch Status
Report. This field will be blank for all Job Plans except type 3. The Line
Code consists of three characters. The first two positions should be used to
sequence the known or planned operations required to accomplish the assignment,
the last position should be reserved to permit inserting of milestones and
unplanned or unknown operations at a later date.
2.5.3.6 Labor Identification
This field is composed of four separate code groups:
function, operation, quality and skill. This field will not be used if the
type plan is 2. Type 1 plans will only use the function code segment of the
18
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
?
2.5.3.6.1 Skill
This field may be blank for a type 3
plan. If the field is not blank, it must contain one of the standard single
character skill codes.
2.5.3.6.2 Function
This field may be blank if the type plan
is 1; however, if the Job Plan is for a job which appears on the Nav-Plan
Status Report, the function cannot be blank. The field must be completed
for-type 3 plans. Only the standard function codes may be used.
2.5.3.6.3 Operation
The field may not be blank for type
plan 3. Only the standard quality codes may be used.
2.5.3.6.4 Quality
If a type plan is 3, the field may not
be blank. Only the standard quality codes may be used.
2.5.3.7 Milestone Description
This field only applies to a type 3 plan when the
labor identification field is blank. Any alpha-numeric combination may
be used. If the labor identification field is not blank, this field will
not be keypunched.
2.5.3.8 Manhour Estimate
Enter the manhour estimate for the job-organization
combination. If the type plan is 3, each labor identification must have a
manhour estimate. Tenths of an hour may be entered. This field is blank
only for milestone events.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
2.5.3.9 Schedule Start
Enter the month, day, and year that the job or
phase of the job is expected to begin. Use only the last character of
the year. This field may be blank. However, to make the status reports
more meaningful, the schedule start date should be entered.
2.5.3.10 Schedule Stop
Enter the month, day, and year that the job or
phase of the job is scheduled for completion. Use only the last character
of the year. This field may be blank. However, to make the status reports
more meaningful, the schedule stop date should be entered.
2.5.3.11 Organization To
Enter the code of the organization that will work
on the job next. Any level of organization may be used. The field may
be blank.
20
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
,qw
PROMACS JOB PLAN
- __DATE
-
MO DAY Y ?YR
1 2T3 4 5
JOBIDENT T
6 7 8 9 , fo 1 12 113
IP
14
JOB DESCRIPTION /
CONTROL
EXTENSION
ORGAN]'
2ATION
LABOR IDENT
MANHOUR
ESTIMATE
SCHEDULED
START
SCHEDULED
COMPLETION
ORGN
TO
PREPARED
BY
O
O
u1
>
D
i
U
Z
?
m
=
O
F
U
N
LINE
CODE
J
vYi
Z
Z
4
W
O a
>
J
OPERATION AND/OR MILESTONE DESCRIPTION
T
E
N
' T
:H
S
i
Z
F
>
O
<
W
Z
f
0
O
>
O
U
m
O
I-
U
uWi
NAME AND
EXTENSION
15.
16
17
18
19
20
21
22
23
24
25
26
27
28
291
301
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
EXHIBIT 2-4 JOB PLAN RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
2.6 Job Plan.Change Record
2.6.1 Purpose
The purpose of the Job Plan Change Record is to:
o add planning data to a Job Plan that has been submitted
previously.
o change planning data that has been previously submitted, or
o delete planning data that has been submitted .,previously.
2,6.2 Requirements
The Job Identification, Line Code, Labor Identification, and
Organization From fields are used as the control fields for this card. They
can be deleted, but they cannot be changed. When changing or deleting data
on the master file, the control field of the input must match exactly with
the master file.
After a Job Plan has been established, this record must be
used to add additional data to the master file. The type plan must be the
same as that on the file. When new data is added to the file, the same
restrictions as described for the Job Plan Record apply.
2.6.3 Input Preparation
When preparing the Job Plan Change Record, the following
should be observed.
2.6,3.1 Transaction Date
Enter month, day, and year. Use only the last
character of the year. The date is used to help identify the r.ecord, should it
be rejected. This field is checked for valid numeric characters.
2.6.3.2 Job Identification
If a type plan is a 1 or 3, enter the standard eight
character job identification code. If the type plan is 2, enter the standard
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
five character OIg sub-line item identification. The last three positions
should be blank, for the type 2 plan. This field is used as a control field.
It must match a job identification code that has been previously established.
?.6.3.3 Line Code
If the type plan is a 1 or 2, this field must be
blank. If the type plan is 3, and the type change is A, enter any three
digit number that was not used on the original plan which will place the data
in the desired position on the Section-Branch Status Report. If the type plan
is 3, and the type change is C or D, the field may be blank. The line code
is used to sequence the Section-Branch Status Report. It is checked for
numeric characters pr blanks.
2,6,3,4 Labor Identification
The labor identification is a control field.
2.6.3.4.1 Skill
If the type plan is a 1 or 2, this field
must be blank. If the type plan is 3, the field may be blank. If it is not
blank, one of the standard skill codes must be used.
2.6.3.4.2 Function
If the type plan is 1, the function may
be blank. If the assignment is to appear on the Nav.Plan Status Report, the
function cannot be blank. If the type plan is 2, the function must be blank.
If the type plan is 3, the function cannot be blank, Only the standard function
codes may be used,
2.6.3.4.3 Operation
If the type plan is 1 or 2, the operation
must be blank. If the type plan is 3, the field may not be blank. Only the
standard operation codes may be used.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.6.3.4.4 Quality
If the type plan is 1 or 2, the quality
must be blank. If the type plan is 3, the field may not be blank. Only the
standard.quality codes may be used.
2.6.3.5 Organization From
Enter the standard organization code. This code must
be two alphabetic characters and two numeric characters. It must be the same
level of organization that will be charged on the Daily Labor Card. It must
match with an organization that had been previously established for the job.
This field is a control field.
2.6.3.6 Schedule Start
Enter the month, day, and year that the job or phase
of the job is expected to begin. Use only the last character of the year.
This field may be blank. It is checked for valid numeric characters or blanks.
2.6.3.7 Schedule Stop
Enter the month, day, and year that the job or phase
of the job is scheduled for completion. Use only the last character of the
year. This field may be blank. However, to make some of the status reports
more meaningful, the schedule stop date should be entered. The field will be
checked for valid numeric characters or blanks.
2.6.3.8 Estimated Manhours
If the type change is A, enter the manhour estimate
for the job-organization combination. If the type plan is 3, each labor
identification must have a manhour estimate. Tenths of an hour may be entered.
If the type change is C, the field may be blank. The field is checked for
numeric characters or blanks.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
2.6.3.9 Actual Start
Enter the month, day, and year. Use only the last
character of the year. The field may be blank. It is checked.for valid
numeric characters or blanks.
2.6.3.10 Actual Stop
Enter the month, day, and year. Use only the last
character of the year. The field may be blank. It is checked for valid
numeric characters or blanks.
2.6.3.11 Status Note
Any seven position alpha-numeric combination may be
2.6.3.12 Organization To
Enter the standard organization code. This code must
be two alphabetic characters and two numeric characters. It will be checked
for validity.
2.6.3.13 Type Plan
Enter a 1, 2, or 3. These are the only allowable
characters. This field cannot be blank for a type change A.
2.6.3.14 Type Change
Enter an A, C, or D. When the type change A is used,
the same considerations described for the Job Plan should be observed. The
type change A must be used to add additional phases to a type 3 plan or to add
additional functions to a type 1 plan. To change a field, use the type change
C. Enter the correct data in the appropriate field along with the control
fields. The control fields depend on the type plan that was originally sub-
mitted. To delete one or more fields but not the control fields, enter a zero
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
? in the appropriate field along with type change C. To delete all the planning
data associated with the job organization or the phase of the job, use the
type change D. Only the control fields should contain data.
2.6.3.15 Transaction Code
Enter 07.
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
Control No.
Ext.
PRO
MACS STAT
US MA
STER JOB PLAN
CHANGE RICQRD
TRANS
GATE
Job 1D.
LINE
CODE
LABOR
IDENT
ORGN.
FROM
SCHEDU
DATES
LE
EST
M/INKS.
ACTUAL DATES
ORGN.
TO
STATUS
NOTE
T
Y
T
R
M
O
D Y
LINE
S
S F
K u
o Q
D
D
8 5
R E
START
STOP
START
STOP
R E
E E
IN
N
T
H
A E
Y A
R
ITEMS
D
E
C
0
B
{
I N
L C
L T
I
N
E A A
R. L
1
T
Y
V
I
5
N
A C
N T
C 1
H O
N
M
O
N
T
H
D Y
A E
Y A
R
M
O
N
T
N
D Y
A E
Y A
M
o
N
T
H
D
A
Y
Y M
E O
A N
R T
H
D V
A E
y A
V
I
S
I
N
A C
N T
C I
N o
4J
'
P
L 64
A
A
N
S
C
O
D
E
1121
3 4 15
6
7 8
9
10 11
11 131
14115
16 11 18
19
20 21
2T
23 24
25 26
27 28
29 30
31
32 33
34 35
36 37
38 39
40 41
42 43
44 45
46 41
48 6
50 511
521 53
541551
56157
58 59
60 61
62 63
64 65
66 67
68 69
70 11
72 73
74
75 76
77 78
A 80
l
i
I
I
I
1
1
1
j
I
i
t
~
I
I
i
I
I,
~
1 j
I
I
j
I
I
I
I
~
~
i
~
I I
I
I
~
I
NAME X TITLE
LEGEND: TYPE CHANGE
ADD
A
SIGNATURE
-
C - CHANGE
D DELETE
ACIC 32 TEST
EXHIBIT 2-5 JOB PLAN CHANGE RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.7 Cost Change Record
2.7.1 Purpose.
The purpose of the Cost Change Record is to change the regular,
overtime, and military manhours and manhour dollars for the current month,
fiscal year, and cumulative to date.
2.7.2 Requirements
This record must be used to change any cost data associated
with the current month, fiscal year, or cumulative to date. It cannot be used
to change the current week. Only the Daily Labor Card can be used to add cost
data to the current week. Whenever the manhours are changed, the associated
manhour dollars must also be changed.
2.7.3 Input Preparation
When preparing the Cost Change Record, the following should be
observed:
2.7.3.1 Transaction Date
Enter as month, day, and year. Use only the last
character of the year. The field will be checked for valid numeric
characters.
2.7.3.2 Job Identification
Enter the standard eight character job identification
code. This field must match with a job identification code previously established.
2.7.3.3 Labor Identification
This field cannot be blank and must match with one
previously established on the master file. The only exception is for a type
change A and a Job Plan type 1 or 2 that has been submitted for the job identifi-
cation-organization combination.
Revised 21 June 1967
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
2.7.3.3.1 . Skill
Enter the standard one character skill code.
2.7.3.3.2 Function
Enter the standard one character function
2.7.3.3.3 Operation
Enter the standard two character operation
2.7.3.3.4 Quality
Enter the standard one character quality
?
is
2.7.3.4 Organization
Enter the standard four character organization code.
The codes used must conform to those used on daily labor cards. This field
must match with one previously established for the job identification.
2.7.3.5 Change Period
The following codes apply:
1 = current period, fiscal year and cumulative to date.
2 = fiscal year, and cumulative to date.
3 = cumulative to date.
These are the only allowable characters.
2.7.3.6 Actual Manhours
2.7.3.6.1 Regular
Enter the number of regular manhours that
are to be added or subtracted from the change period indicated. This field
may be blank.
29 Revised 21 June 1967
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
2.7.3.6.2 Overtime
Enter the number of overtime manhours
that are to be added to or subtracted from the change period indicated.
This field may be blank.
2.7.3.6.3 Military
Enter the number of military manhours
that are to be added or subtracted from the change period indicated. This
field may be blank.
2.7.3.7 Actual Manhour Dollars
2.7.3.7.1 Regular
Enter the number of regular manhour
dollars that are to be added or subtracted from the change period indicated.
This field may be blank.
2.7.3.7.2 Overtime
Enter the number of overtime manhour dollars
that are to be added or subtracted from the change period indicated. This field
may be blank.
2.7.3.7.3 Military
Enter the number of military manhour dollars
that are to be added or subtracted from the change period indicated. This field
may be blank.
2.7.3.8 Type Change
Use A to add the data to the file and an S to subtract
the data from an existing record.
2.7.3.9 Transaction Code
Enter '08.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
PRO
MACS
CUNTROL NO.
EXT.
STATUS MASTER COST CHANGE RECORD
TRANS
DATE
JOB ID
LABOR
ID
ORGN
H ACTUAL MANHOURS
A
ACTUAL MANHOUR
R
A
M
D E
LINE
S O
E
KU
E UA
D
R
A
E REGULAR
OVERTIME
MILITARY
REGULAR. OVE
RTIME
MILITARY
N
C.
Y A
R
ITEM
.
C B
L C
L T
O
N
R L
A I
I Y
N
I
V
N
H
P Ir
E HOURS IN
R IH
D IS
IT
HOURS le
IT
IS
Ir
HOURS IN
IH
IS
I
I
I
I
I
I
$ I
I
I
N
0
D
E.
1
2 3
4 5
6 7
8 9
10 11
1213
14,151
16117
18 19
20 21
22
23 24
25 26
27 28
29130
131 32
133134
135136
37138
139 40
4112
0 44
1010
47 48
49 50
51152
15315
4 55 56
57 58
5910
161162
63 64
65 66
67 68
69 70
71 72
73 71
75 76
77 18
19 80
I
H
1-1
T
N AME_ TITLE LEGEND: TYPE CHA
A -ADD
S -SUBTR
NGE CHANGE PERIOD
I = CURRENT "PERIOD
ACT 2
FISCAL YEAR
SIGNATURE
=
3 = CUMULATIVE TO DATE
EXHIBIT 2-b COST CHANGE RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
2.8 Milestone Change Record
2.8.1 Purpose
The purpose of the Milestone Change Record is to:
o add a milestone event to an existing job plan.
o change an existing milestone event, or
o delete an existing milestone event.
2.8.2 Requirements
When a new milestone event is added, the same restrictions as
explained in the Job Plan Record apply. A milestone record applies only to
a type 3 plan.
2.8.3 Input Preparation
When preparing a Milestone Change Record, the.following should
Enter month, day, and year. Use only the last
character of the year. The date is used to help identify the record, should
it be rejected. It is checked for valid numeric characters.
2.8.3.2 Job Identification
Enter the standard eight character job identification
code. It must match a previously established job identification code. This is
a control field.
2.8.3.3 Line Code
Enter the corresponding line code from the original
job plan. If this is an add record (an A in the type change field) enter a
previously unused line code. This is a control field.
2.8.3.4 Organization
Enter the standard organization code. This code must
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
is
be two alphabetic characters and two numeric characters. This field must
match a previously established organization code for the job identification.
This is a control field.
2.8.3.5 Milestone description
Any alpha-numeric combination may be used. This
field cannot be blank if the type change is A.
2.8.3.6 Organization To
Enter the code of the organization that will work on
the job next. Any level of organization may be used. The field may be blank.
It is checked for validity.
2.8.3.7 Schedule Start
Enter the month, day, and year that the job or phase
of the job is expected to begin. Use only the last character of the year.
This field may be blank. It is checked for valid numeric characters or blanks.
2.8.3.8 Schedule Stop
Enter the month, day, and the year that the job or
phase of the job is scheduled for completion. Use only the last character of
the year. This field may be blank. However, to make the status reports more
meaningful, the schedule stop date should be entered. It is checked for valid
numeric characters or blanks.
2.8.3.9 Status Note
Enter any 7 position alpha-numeric combination. This
field may be blank.
2.8.3.10 Type Change
Enter either-A, C, or D. When the A code is used, a
new milestone event will be added to the Job Plan. Use the type change C to
change the milestone description, organization to, schedule start, schedule
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
stop, and status note fields. To delete one or more fields, but not
the control fields, enter a zero in the appropriate field along with the
type change C. Use the type change D to delete complete milestone event.
2.8.3.11 Transaction Code
Enter 09.
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
CoPi*TROL NO.
EXT.
PROMACS STATUS MASTER MILESTONE CINANGE RECORD
j
D A T E
JOB I D
ORGN
?T?a
Y
A
D
A
MY
H A
T R
LINE
ITEM
S P E C
JOB
LINE
CODE
DI
\'
R S
T
MILESTONE
DESCRIPTION
D
I
$ S
R E
7
SCHED
STOP
ACTUAL
STOP
STATUS E
NOTE H
G
1EI
D
E
1 2
3 4
5 6
7
8 9 1
101111
12 U
14 15
1 6
17 18
19 20
21 22
23 24
:25 26
Z 7 28
29 30
31
32 33
34 35
36 37
38 39
40 41
a 43
4 4 . 1 4 5 1
4 64 7
Q4 9
5 05 1 5
2 531
54 55
56 57
581591
W 61
62 63
64 651
661671
01691
70171
72 73
74
75 76
77 78
19 80
I
T
F
TI
T
TE,
i
j
NAME k TITLE
LEGEND: TYPE CHANGE .
A- ADD`
SIGNATURE
c- CNAN:GE ...
D- DELETE
ACIC ;,,,,E? 32b TEST
EXHIBIT 2-7 MILESTONE CHANGE RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
2.9 Movement Routing Record
x,9.1 Purpose
The purpose of the Movement Routing Record is to record phase
or milestone completions and section, branch, or division completions.
2.9.2 Requirements
The Movement Routing Record can be used in lieu of the Daily
Completions Record to report section, branch, or division completions. Plant
completions cannot be reported with this record.
2.9.3 Input Preparation
When preparing the Movement Routing Record, the following
should be observed:
2.9.3.1 Date
Enter the month, day, and year. Use only the last
character of the year. The date is used to help identify the record should
it be rejected. It is also used as the completion date.. It is checked for
valid numeric characters.
2.9.3.2 Job Identification
Enter the standard organization code. This field
must match with one already established on the master file.
2.9.3.3 Line
Enter the line number from the Job Plan. It is
required only for reporting the completion of a milestone event. It is checked
for numeric characters and blanks.
2.9.3.4 Labor Identification
2.9.3.4.1 Function
Enter the standard function code. This
field is required only for reporting a phase completion. It must match a
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
corresponding field on the master file or else be blank.
2.9.3.4.2 Operation
Enter the standard operation code. This
field is required only for reporting a phase completion. It must match a
corresponding field or the master file or else be blank.
2.9.3.4.3 Quality
Enter the standard quality code. This
field is required only for reporting a phase completion. It must match a
corresponding field on the master, file or else be blank.
2.9.3.5 Organization From
Enter the standard organization code. If a phase
completion is reported, the organization code must match a corresponding field
on the master file. If a section, branch, or division completion is reported,
the field is checked for validity.
2.9.3.6 Movement/Completion
If a phase completion (movement) is reported, the
field must be blank. For other than a phase completion, the following must
1 = a section completion.
2 = a branch completion.
3 = a division completion.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04 CIA-RDP73T00325R000100030001-9 ?
PR0MACS MOVEMENT ROUTING RECORD
1 2 3 ? S
DATE
7 S q to 11 [12.113
JOB IDENT.
JOB DE
iw iS '16
Li INEi
SCRIPTION
f? 181191,L61 sf it if 24 is
L L
G fV
F OP FROM 1OR
REMARKS
SUBMITTED BY
RECEIVED BY
EXHIBIT 2-8 MOVEMENT ROUTING RECORD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.10 Status Record
2.10.1 Purpose
The purpose of the Status Record is to record the status of a job,
phase, or milestone event.
2.10.2 Requirements
The use of the Status Record Card is optional. It can be used
for a job if a type 1 plan had been submitted or for a phase or milestone event
if a type 3 plan had been submitted. Any 7 position alpha-numeric code can be
used to indicate status.
2.10.3 Data Preparation
When preparing the Status Record, the following should be observed:
2.10.3.1 Date
Enter the month, day, and year. Use only the last
character of the year. The date is used to help identify the record, should
it be rejected.
2.10.3.2 Organization From
Enter the standard organization code. This code must be
two alphabetic and two numeric characters. This field must match a corresponding
field on the master file.
2.10.3.3 Job Identification
Enter the standard eight character job identification
code. This field must match a job identification code that had been previously
submitted on a Job Plan.
2.10.3.4 Line Number
This field is required only when the status applies to
a milestone event. It is checked for numeric characters or blanks.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.10.3.5 Labor Identification
2.10.3.5.1 Skill
Enter the standard skill code. This
field is required only if skill was submitted on the job plan for the job-
organization combination. If the field is not blank, it must match the corres-
ponding field on the master file.
2.10.3.5.2 Function
Enter the standard function code. This
field is required only if the status applies to a phase of a type 3 Job Plan.
If the field is not blank, it must match the corresponding field on the master
file.
2.10.3.5.3 Operation
Enter the standard operation code.
This field is required only if the status applies to a phase of a type 3 Job
Plan. If the field is not blank, it must match the corresponding field on the
master file.
2.10.3.5.4 Quality
Enter the standard quality code.
This field is required only if the status applies to a phase of a type 3 Job
Plan. If the field is not blank, it must match the corresponding field on the
master file.
Enter any seven position alpha-numeric code. The
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
P ROMACS
STATUS RECORD
D T O G FROM o TR L HUM
JOB IDENT
13 11415
Q1 STATUS
NAME ~ TITLE
AC IC FORM
SIGNATURE
EXHIBIT 2-9 STATUS RECORD
41
Approved For Release 2008/06/04: CIA-RDP73T00325R00010003
o1v L1NE M
JOB DESC * S F 'OP
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
. 2.11 Daily Labor Card
2.11.1 Purpose
The purpose of the Daily Labor Card is to record manhour
expenditures.
2.11.2 Requirements
The detail requirements for the Daily Labor Card can be found
in ACIC Reg 171-1.
A Job Plan Record must be submitted for the job identification-
.organization combination before Daily Labor Cards will be accepted.
Overtime hours worked must be reported on a green striped card.
If the Daily Labor Card has been determined invalid, re-submit
the correct information on a red striped card.
2.11.3 Input Preparation
2.11.3.1 Date
Enter month, day, and year. Use only the last
character of the year. The date is used to help identify the record, should
it be rejected. This field is checked for valid numeric characters.
2.11.3.2 Organization
Enter the standard organization code. This code must
be two alphabetic characters and two numeric characters. It must match a
previously established organization code for the job identification.
2.11.3.3 Rate
Enter the applicable hourly rate. This field is
checked for numeric characters.
2.11.3.4 M/I
Indicate M or I where applicable. The field is
checked for M, I, or blank.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 . Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
?
Enter the applicable standard skill. It is
checked for validity.
2.11.3.6 Job Identification
Enter the standard eight character job identification
code. This field must match a previously established job identification code
for the above organization.
2.11.3.7 Labor Identification
2.11.3.7.1 Function
Enter the applicable standard function
code. In all cases this code must be valid. If the Job Plan that was submitted
was a type 1 with a function code, it must match. If the Job Plan was a type 3
the function code must match the function code of the Job Plan.
2.11.3.7.2 Operation
The applicable standard operation
code. In all cases this code must be valid. If a type 3 Job Plan had been
submitted it must match the operation code of the Job Plan.
2.11.3.7.3 Quality
Enter the applicable standard quality
code. In all cases this code must be valid. If a type 3 Job Plan hao. been
submitted, it must match the quality code of the Job Plan.
2.11.3.8 Night Differential Rate
Enter the applicable night hourly rate. It is checked
for numeric characters or blanks.
2.11.3.9 Time
Enter the hours worked. It is checked for numeric
characters. It cannot be blank.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
MONTH I DAY I YR
DATE
PREVIOUS EDITION OF THIS FORM WILL BE
USED UNTIL STOCK IS EXHAUSTED
JOB IDENTIFICATION
JOB DESCRIPTION
LABOR ID.
N/D RATE
TIME
F
OP
EMPLOYEE'S NAME
DATAILED FROM
SUPERVISOR'S CERTIFICATION
TOTAL
DAILY LABOR RECORD
EXHIBIT 2-10 DAILY LABOR CARD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
I I
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
2.12 Skill Extension Card
2.12.1 Purpose
The purpose of the Skill Extension Card is to enter the fiscal
year manhour and contract dollar allocations, and the program rate into the
system.
2.12.2 Requirements
A skill extension card is required whenever there is a change in
the CIP allocations or rates. At the present time only fiscal year 68 for
ACIC St. Louis cards are required.
2.12.3 Data Preparation
This card is presently being prepared by ACODA and their procedures
should be followed. The fields that PROMACS uses are explained below:
2.12.3.1 ACIC Unit
Enter any number 1 through 6. One (1) is the only number
used by PROMACS.
2.12.3.2 Fiscal Year
Enter the last character of the fiscal year. The number
8 is the only one used by PROMACS at this time.
2.12.3.3 Skill
Enter the two digit skill code used by ACODA.
2.12.3.4 Line Item
Enter the standard 5 character CIP line item code.
2.12.3.5 Number Jobs
Enter the number of new jobs to be completed during the
fiscal year.
2.12.3.6 Completion Manyears
Enter the number of manyears allocated for the number
of jobs in 2.12.3.5.
45
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
?
2.12.3.7 Number Jobs Inventory
Enter the number of jobs currently in the pipeline
that will be completed during the fiscal year.
2.12.3.8 Inventory Manyears
Enter the number of manyears allocated for the number
of jobs in 2.12.3.7.
2.12.3.9 Contract Dollars
Enter the number of contract dollars allocated for new
jobs to be completed during the fiscal year.
2.12.3.10, Contract Dollars Inventory
Enter the number of contract dollars allocated for
completing jobs currently in the pipeline during the fiscal year.
2.12.3.11 Transaction Code
Enter 50.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
AI
C15
CA
L
NE
N
A
T R
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
SKILL EXTENSION CARD
COMPLETION
MANYEARS
LINE
ITEM
NO.
JOBS
20121122 123 : 24
NO.
JOBS INVENTORY CONTRACT
INV. MANYEARS
INVENTORY
CONTRACT,
DOLLARS'
?
T
R
A
N
Sc
0
D
E
25 26127 28' 23 301'31 32 '33 :34:35 36 37138 39.10141142 43 44 15 146 147; 48 19 50131:52 ,53,54 55156 57156 59 60 61;,62 ~ s 64 6566 X67 d68 691;7017i i 72 T 1 71175 1F rfl F Jv n
'! i t 1 i ~ I t s i t I i 1 I ~ r
I ~ I j f I I i 1 ! I
j 1'
-06
i 1 ~ I I ,
1
f I
I i t
~I
I i l ' I l I I l i l l ' i l I l l I I I i l 1 11 !~ LJ will
I i ' I 1 I 1
I 1 1 I I I ~ I I I I I I I 1 I
j I f I I i I i I i I I 1 l i I i i i I
' I i ; I ' I I I
i l l i 1 1 I i I I I I I
EXHIBIT 2-11 SKILL EXTENSION CARD
j i t I I . l
,
I 1 1
~ I ,.i _- ~ I I I 1 1 1 1 1 I
11 FFFT
I ilIil ~I III 1 ~! 11111H111111
ii
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
2.13 Production Schedule Card
2.13.1 Purpose
The purpose of the Production Schedule Card is to enter the
scheduled completions by month, division, and skill for a CIP line item.
2.13.2 Requirements
The Production Schedule Card is required to supply schedule
data for the Resource Utilization Analysis Reports. If the card is not submitted,
the schedule fields will remain blank.
The input card is designed so that the production schedule is
a sliding arrangement. The first month field on the card always represents
July. However, it always represents the next July. For example,-during July
1967 the month represented is July 1967. During the month of August, the same
field represents July 1968.
2.13.3 Data Preparation
When preparing the Production Schedule Card the following should
be observed:
2.13.3.1 Date
Enter the month, day, and year. Use only the last
character of the year. The date is used to determine the applicable year
for the production schedule. This field is checked for valid numeric characters.
2.13.3.2 CIP Line Item
Enter the standard 5 character CIP line item code.
This is a control field. It must match a corresponding field created by the
Program Category Card.
2.13.3.3 Organization
Enter the first two characters of the standard 4
character code. This-field is checked for proper alphabetic characters.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
2.13.3.4 Skill
Enter the standard alphabetic skill code. This field
is checked for proper alphabetic characters.
2.13.3.5 Production Schedule by Month
Enter the number of items scheduled for completion
during the next 12 months. These fields are checked for numeric characters
or blanks.
Enter A, C, or D. Use A to add a new CIP line item,
?
?
division, skill combination to the file. Use C to change the production
schedule. Use D to delete the schedule for the CIP line item, division, and
skill combination.
2.13.3.7 Transaction Code
Enter- 52.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
?
2.14 Program Category Card
2.14.1 Purpose
The purpose of the Program Category Card is to group the CIP
sub-line items into program categories, and to enter the CIP sub-line item
description and the program category description into the PROMACS system.
2.14.2 Requirements
A Program Category Card is required whenever a CIP line item is
added or deleted from the available codes. It is also required whenever the
program categories change.
2.14.3 Data Preparation
When preparing the Program Category Cards the following should
2.14.3.1 CIP Subline Item Code
This is the standard five character alpha-numeric code.
All authorized sub-line item codes must be included on these cards.
2.14.3.2 CIP Subline Item Description
A twenty character description of the sub-line item.
2.14.3.3 Program Category Code
This is a three position alpha-numeric code used to
identify the program category. It should be the same as one of the sub-line
item codes that are being summarized to form the program category. A program
category code must be shown for each sub-line item code.
2.14.3.4 Program Category Description
A twenty character description of the program category.
This description needs to be entered only once for each program category code.
2.14.3.5 A-C-D
Use A to add information to the file, C to change
information, and D to delete information. The C code can only be used to
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
change one of the description fields or the Program Category Code. The CIP
? Subline item code must contain information regardless of what indicator is
used.
2.14.3.6 Transaction Code
The transaction code for the Program Category Card
?
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73TOO325R000100030001-9
CIP
SUB'-
LINE
ITEM
CODE
CIP SUB-LINE ITEli DESCRIPTION -.
PROGRAML PROGSAK
CA2EGOEY C~F608Y
cxmE- 1' D E&CHIPTEM
?S
_G=6r
D C
D
E-
2 3
4 5
6 7
B 9
10 I t
1 2 17
14 1 5
16
17 1B
19 20
21 22i
2J 24 ?
5 20
i7~28
2c JO
71 J2
73 7a
75
70 77 78
79 a0
11 ai
a7; aa; a31
a0 a7
a8
a9 SO
31 Si
33 Sa
53 30
37 SB
59 00
OI Oi
O7 Ot
OS 00
07 08
09 70
71 72
77 7r
7S 70
77 78
79
i
i
-PROGRAM CATEGORY CARD
PUNCH CARD TRANSCRIPT
EXHIBIT Z-13 PROGRAM CATEGORY CARD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
?
2.15 Skill Rate Card
2.15.1 Purpose
The purpose of the Skill Rate Card is to enter a rate and
description for each skill.
2.15.2 Requirements
The Skill Rate Card is required to calculate the manhour dollar
fields on the Resource Utilization Analysis Reports. It is also used to furnish
a description of the skill.
2.15.3 Data Preparation
When preparing the Skill Rate Card the following should be
2.15.3.1 Skill
Enter the standard one character alphabetic skill code.
This field is checked for alphabetic characters only.
2.15.3.2 Rate
Enter the manhour to manhour dollar conversion rate
that applies to the skill. This field is checked for numeric characters only.
2.15.3.3 Description
Enter any combination of alpha-numeric characters.
Ten positions are allowed for the description. This field is not checked
except it cannot be blank for type change A record.
2.15.3.4 A-C-D
Enter either A, C, or D. Use A to add a new skill to
the file. Use C to change or add to a skill already in the file. Use D to
delete a skill already in the file.
2.15.3.5 Transaction Code
Enter 54.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73TOO325ROO01
SKILL RATE CARD
S
K
I
L
L
RATE
DESCRIPTION
TT
YR
E N
cs
N
N C
G 0
E D
E
1 2 3 4 5 6 J B 9 10-11 11' 13 II 1 5 ' 16 17 18 !.19 ID 11 11 23 24 E
16
D a 8 30:31 31 33 34 35 3631 38 39 40 41 4243 44 45:46 47 01's 50 51 Si Si S4 55 .56:;57 58 59 i 6 0 61 61 63 64' 65 i 66 67 68169 70 71 71
73 14 75 76 77
78 i 79
80
?
EXHIBIT 2-14 SKILL RATE CARD
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?'
?
2.16 Validity Tables
2.16.1 Purpose
The purpose of the Validity Tables is to provide data for the
edit program to check input records for proper codes.
2.16.2 Requirements
There will be six tables established. The tables can be updated
whenever it is required.
2.16.3 Data Preparation
2.16.3.1 Quality Control Record
This card will be used to enter the authorized quality
control codes. All the current quality codes can be entered on a single card.
Additions or deletions will be possible with the use of the add (A) or delete (D)
codes. The transaction code for this card is 94.
2.16.3.2 Operation Description Record
This card will be used to enter the authorized operation
codes and their descriptions. The operation codes will become part of the
validity tables. The operation codes and their descriptions will be used for
preparing the Section Status Report. Four codes and their descriptions may be
entered on each card. Operation codes may be added or deleted with the use of
the add (A) or delete (D) code. Operation descriptions may be added with the
use of the add (A) or change (C) codes. The transaction for this card is 95.
2.16.3.3 Function Code Record
This card will be used to enter the function codes
associated with the cost charge number. All the current function codes may be
entered on a single card. Additions or deletions will be possible with the use
of the add (A) or delete (D) codes. The transaction code for this card is 96.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
2.16.3.4 Skill Code Record
This card will be used to enter the authorized skill
codes. All the current skills may be entered on a single card. Additions or
deletions will be possible with the use of the add (A) or delete (D) code.
The transaction code for this card is 97.
2.16.3.5 Organization Code Record
This card will contain the four alpha-numeric character
organization code. Nineteen organization codes may be entered on each card.
The add (A)-delete (D) code will be used to indicate whether the organization
codes are to be added to or deleted from the table. The transaction code for
this card is 98.
2.16.3.6 CIP Sub-Line Item Code Record
This card will contain the five character CIP Sub-line
Item Identification. It is possible to enter fifteen sub-line item codes on a
single card. The add (A)-delete (D) code will be used to indicate whether the
sub-line item codes are to be added to or deleted from the table. The
transaction code for this card is 99.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04 CIA-RDP73T00325R000100030001-9
i
-1 4
4 4
PYFY
A
U
7
C
P q
pp
4
1
2 3
? 3
617
8 9
1 0 11
112111
114115
16
1 7 IB
19 70
2112J
123 7.
75;76
17 79
79 )0'31
37 33
34 35
136137
30 39
?O 4/
47 ?3
?.45
46147
149 ?9
50 51
57 53
15415
51-'6157
158159
60 61
67. 163
164165
166167
68 69
70 71
72 73
74 75
7617;,
"J"
1801
1
i
i
EXHIBIT 2-15 QUALITY TABLE
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
0
P
R OPERATION DESCRIPTION
0
P
R
p
OPERATION DESCRIPTION
0
P
R OPERATION DESCRIPTION
P
R
OPERATION DESCRIPTION
T
A R
N
S
A
T
I
T
A
I
A
I
BLANK
C C
0
N
N
N
N
D D
E
x 7
a 1 5
a 7
a a 110 !I12 171. ,5:1o 17
18119
20: 7,1 2223!x.123 2 i 271 20 3C 3,'32:7'3
. 75!3 37.38 3:.eO!
! ax
.7 .a 5I6 id
7.8 X19 50.
s, 3x!53 s
.'s5
s0 571
58159i60:
61 ax
.33;.111
65 JJ
6716.3
.6 9 7,11
71 7 2
77 71
73 /a
77 73
798
7 -
T
j!i
l
I I
I i! i! j
I
r!
~~)
I
_
i~ill~i
~
M
!
i l t
Ii
lil
!
F
!
M
it
!
1
III
;I
II!I
F
FL
I
EXHIBIT 2-16 OPERATION TABLE
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
F
u
N
C
T
I
0
N
F F
u u
NN
C C
T T
II
0 0
NN
F
U
N
C
T
I
0
N
F
u
N
C
T
I
0
N
A T .~
q l
S
S
E
1
2 7
1 5
6 7
8 9
10 11
12
11311 1
15 16
t7118
19 120
121122
23 21
25126
127 79
29130
,.317i
J.
35
6 77.79
s0
11 12
a3;14
:1S46
1F
F
COUNTRY
CODE
1 Z 3 4 5 6 7 9 1 9 110
INTEL!
DATA
w
aZ
W
~
X
w
JOB
(DENT.
~I LINE SPEC
ITEM JOB
1
2 3
4 5 6
7
0 9
10111
112113
114 15
116 17
219
2D 21
22 23
2 25
26 2l
20 29
30 31
32 33
341351
36137
12[B
10 41
121,0
14414
514147
10 19
50 SI
52 53
54 55
56 57
51 B
60 61
62 63
61 B
66 67
68 B
A 7I
72 73
71
75 76
7) 70
A BD
I
PT
- -
-
1
I I
I I
f I
EXHIBIT 2?22 COMPLETION CARD ATM
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
2.19 AB Card
2.19.1 Purpose
The purpose of the AB Card is to supply information necessary
for the DIA ATMP Production Management System.
2.19.2 Requirements
The AB Card is required for all products included in the DIA
ATMP Production Management system. The card is required prior to the completion
of the product.
2.19.3 Input Preparation
For detailed information concerning the preparation of the AB
Card see DIAM 65-5-1.
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
s
'AB" CA
RD INPUT
WAC
NO.
TARGET S
NQ.
ERIES
SHEET
NQ
o
LL0'
LOF
o
p EDITION
o DATE
W
MY
CHANGE
ACTION C
DATE
DDMMYY
AR --
TM e
O
Z
og
-
gg
D
PROD
ASSIGN.
DATE
DOMMYYi
PROD
ASSIGN
?o NO.
n'
JOB
IDENTITY
*ASSIGNED
a LINE $PEC
ITEM JO
OPER
PLAN
ID
NO
1
2 3 ;1
IS 6
)
8 9 tO~ll~1
2 lll/}I
S 16!7;18 1
9120~21
~22j2312
_Y
E 26
n m29 3
0 31 32 333
1 3536
3) 31
39 10/ljQ
1
431N
45
16
Q 18 01
50 51
52 53
51
1 8
56 5
7 58 1159
68 611
62 63
6/ 6S
66 67
a
A 71 7
2 73
74
75,76
n 18
I
i
i
!
i
!
I
I
~ i
I
I I
I
I
I
I I
'
I
I
~
I
I
I
,
~
i
EXHIBIT 2-23 AS CARD DIA
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
3. Discrepancy Codes and Reports
3.1 Introduction
The purpose of this section of the User's Guide is to provide
general information that must be considered when correcting the errors
printed on the discrepancy reports. It will also define the error codes
that will appear on the discrepancy reports, explain why the input was
considered to be in error, and give suggested courses of action to
correct the error. Sample discrepancy reports will also be provided.
3.2 General Information
Four discrepancy reports are produced by the edit and updating
cycles of the processing. These reports will contain the image of the
input card that has been rejected. The maximum number of error codes
printed will be six. If there are more than six errors in a card, error
code 99 will be printed on the reports. The complete card must be checked
manually to determine all the errors.
Some of the input cards are reformatted during the processing
to tape. If an error is encountered in these records, the tape record is
printed. The Daily Labor Card, Completion/Cancellation/Suspension Card,
and the Movement Routing Cards are reformatted as follows:
o Multiple entries on the Daily Labor Card appear as
separate tape records.
o The Completion/Cancellation/Suspension Card is divided
into a Completion Record, a Cancellation/Suspension
Record and/or Movement Routing Record.
o The Movement Routing Card appears as two separate
tape records.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
The Completion Record and the Cancellation/Suspension tape
formats are similar to the input document. When the input document is
used to record a section, branch, or division completion, a Movement
Routing Record is generated. If this portion of the input record is in
error, the discrepancy reports will contain the image of a Movement
Routing Record (Transaction Code 10) even though a Completion/Cancellation/
Suspension Card (Transaction Code 02) was input.
To facilitate sequential file processing of the Movement Routing
Card for section, branch, or division completions, two tape records are
generated. The first record processed will contain only Job ID, Organiza-
tion and Type Completion data. The second record will be identical to
the input card except type completion will be blank. The discrepancy
reports may contain one or both of these records, depending on the error(s)
encountered. The Transaction Date of the first record will be established
as the Completion Date for the section, branch, or division completion
action reported.
Part of the card image on the discrepancy reports will be a
transaction code which is used to identify the input record. The following
transaction codes apply:
00 New Assignment Record
01 Authorized Job Master Change Record
02 Completion Record
04 Cancellation/Suspension Record
06 Job Plan Record
07 Job Plan Change Record
08 Cost Change Record
09 Milestone Change Record
?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
10 Movement Routing Record
12 Status Record
20 Daily Labor Card
50 Skill Extension Card
52 Production Schedule Card
?
?
54 Skill Rate Card
55 Program Category Card
94 Quality Table
95 Operation Table
96 Function Table
97 Skill Table
98 Organization Table
99 CIP Line Item Table
Unmatched Daily Labor Cards should be corrected as soon as the
discrepancy reports are received. This will allow the status reports to
show the exact amount of hours spent during the reporting period. Correc-
tions should be submitted on a yellow striped Daily Labor Card. If it is
impossible to submit these corrections in time to be processed in the
proper period, a Cost Change Record should be used to enter the manhours
and the manhour dollars in the proper accounting period.
At the end of each processing of the PROMACS Status Master Update
program, cost totals are printed on the discrepancy report. These totals
will show the hours this week, hours this month, dollars this month, hours this
fiscal year, dollars this fiscal year, hours to date, and dollars to date for
the following:
o Old Status Master Total - the sum of the cost data at
the beginning of the processing.
74
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
o Daily Labor Card Total - the sum of the cost data
added to the master file by means of the Daily Labor
Cards.
o Adjustment Total - the sum of the cost data added or
subtracted from the master file by means of the Cost
Change Record or the Authorized Job Master Change Record.
o Cancellation-Completion Total - the sum of the cost data
?
?
removed from the master file because the job was
cancelled or completed for more than two weeks.
o New Status Master Total - the sum of the cost data
that is written on the New Status Master. It should
equal the algebraic sum of the other four totals.
3.3 Discrepancy Codes
The following is a list of Error Codes utilized in the PROMACS
Discrepancy Reports. The Error Code Column corresponds to the cause for
an input card to be printed on the report. The Process/Reject column
signifies that a card was either rejected (R) or processed (P). A card
is entered into the processing as long as validity is insured. The cause
for the error is explained in terms of what has been determined by the
computer program as being invalid. Corrective action suggesting how to
successfully process the data in error is presented.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04 CIA-RDP73T00325R000100030001-9 ?
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
01
Invalid CIP Line
R
The first five characters of the
If the first five characters of the job
Item Code
job identification code were com-
identification code are invalid, correct
pared against a table of valid CIP
the input card and resubmit it.
line item codes and found to be in
error.
If the first five characters of the job
identification code are valid, add the
CIP line item to the Validity Tables
and the Program Category Table, and
resubmit the input card.
02
Invalid Specific
R
The last three positions of the
Correct the input card and resubmit it.
Job Number Code
job identification code were in
error. The last three characters
must be AAN (alphabetic, alpha-
betic, numeric). Type Two Job Plan
must be blank.
03
Invalid Function Code
R
The function code was compared
If the function code is invalid, correct
against a table of valid function
the input card and resubmit it.
codes and found to be in error.
If the function code is valid, add the
function code to the Validity Tables
and resubmit the input card.
04
Invalid Operation
R
The operation code was compared
If the operation code is invalid,
Code
against a table of valid operation
correct the input card and resubmit it.
codes and found to be in error.
If the operation code is valid, add the
operation code to the Validity Tables
and resubmit the input card.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
05
Invalid Quality Code
R
The quality code was compared
If the quality code is-invalid., correct
against a table of valid quality
input card and resubmit it.
codes and found to be in error.
If the quality code is valid, add the
quality code to the Validity Tables and
resubmit the input card.
06
Invalid Organization
R
The organization code was compar-
If the organization code is invalid, correct
Code
ed against a table of valid
the input card and resubmit it.
organization codes and found to
be in error.
If the organization code is valid, add the
organization code to the Validity Tables
and resubmit the input card.
07
Invalid Skill Code
R
The Skill code was compared
If the skill code is invalid, correct the
against a table of valid skill
input card and resubmit it.
codes and found to be in error.
If the skill code is valid, add the skill
code to the Validity Tables and resubmit
the input card.
R
The skill code for a Job Plan,
Correct the input card and resubmit it.
Types 1 and 2, was not blank.
08
Invalid Transaction
R
The transaction code is incorrect.
Correct the input card and resubmit it.
Code
09
Invalid Line Code
R
The line code was not of the
Correct the input card and resubmit it.
proper format. It should be NNN,
NN blank, or all blank.
10-
Item already in table
R
An attempt was made to add an
If the desired action was to add the code
existing code to the table.
to the tables, no corrective action is
required.
If the desired action was to change or
delete a code in the table, correct the
input card and resubmit it.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
ERROR
OE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
11
Cost Record did not
R
A Type 3 Job Plan was entered for
If the charge number on the input is correct,
match for the Type 3
the job identification-organization
submit a Job Plan Change Record for the
Job Plan
combination, but it did not auth-
charge and resubmit the Daily Labor Card or
orize the charge number appearing
the Cost Change Record.
on the Daily Labor Card or the Cost
Change Record.
If the charge number on the input card is
incorrect, correct the input card and
resubmit it.
12
No planning informa-
R
A Type 1 Job Plan was entered for
If the charge number on the input is correct,
tion for the charge
the job identification-organization
submit a Job Plan Change Record for the
number with a Type 1
combination, but it did not auth-
charge and resubmit the Daily Labor Card or
Job Plan
orize the charge number appearing on
the Cost Change Record.
the Daily Labor Card or the Cost
Change Record.
If the charge number on the input card is
incorrect, correct the input card and
resubmit it.
13
No planning informa-
R
No planning information has been
If the charge number on input card is correct
tion for the cost
entered for the job identification-
submit a Job Plan Record for the charge and
record
organization combination.
resubmit the original input.
If the charge number on the input card is
incorrect, correct and resubmit.
14
Invalid transaction
R
Date field contains an invalid
Correct the transaction. date and resubmit
date
character or is later than the
the activity in the same format.
processing date.
15
Invalid status date
R
Status date field contains invalid
Correct the status date and resubmit the
character or is later than the
activity in the same format.
processing date.
16
Incorrect labor
R
Depending on the type of input in-
Correct the input card and resubmit it.
identification
volved, either there was a labor
identification and should not be,
or there was no labor identifica-
tion and there should be.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
ERROP~
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
17
Invalid Type Authori-
R
Invalid character in type authori-
Correct the type authorization code and
zation or Plan
zation or plan field.
resubmit in the same format.
18
Invalid Type
R
Invalid character in type comple-
Correct the activity record and resubmit
Completion
tion field.
in the same format.
19
Invalid Quantity
R
Invalid characters in quantity
Correct the field and resubmit the input
field.
in the same format.
20
Invalid Cancelled or
R
Invalid character in this field.
Correct the activity and resubmit the input
Suspended Code
in the same format.
21
Non-blank Data Fields
R
The data fields for a deletion
If the desired action was to delete the
for a delete
were not blank.
control fields, only the control fields
activity
may contain data.
If the desired action was to add or change
information associated with the control
fields, correct the type change field on
the input card and resubmit it.
22
Invalid Manhour
R
Invalid characters in estimated
Correct activity and resubmit in same
Estimate
manhour field. This field must
format.
be blank or numeric.
23
Invalid Scheduled
R
Invalid characters in scheduled
Correct activity and resubmit the input
Start Date
start date field or scheduled
in same format.
start is later than scheduled
stop. This field may be blank or
numeric.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
w
is
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
24
Invalid Scheduled
R
Invalid characters in the scheduled
Correct the activity and resubmit the input
Stop Date
stop date field or the stop date is
in the same format.
earlier than the scheduled start
date.
25
Line or Phase Code
R
,Type 2 Job Plan record was sub-
Correct the input record and resubmit it.
for Type 2 Job Plan
mitted with a line code or a labor
identification code.
26
No match on the
R
The control fields of the input
Reference Section 2 of the User's Guide to
Master File
record did not match any corres-
determine the control fields on the input
ponding fields on the Master File.
card involved. Check the fields on the
input card and correct them if necessary.
May need a New Assignment Record or Job
Plan Record.
27
Not Used
28
New Assignment Record
R
The job identification code has
None required.
Submitted Against
already been authorized by a
Previously Authoriz-
New Assignment Record.
ed Job
29
Description Field in
R
The New Assignment Record must
Add the description field to the input
Error
have a description.
record and resubmit it.
30
Job has been cancel-
R
Activity was submitted against a
The only way this activity can be added to
led or completed for
job identification code that has
the file is to reopen the job identification
:more than two weeks
been cancelled or completed for
code with a New Assignment Record. All
more than two weeks.
past charges should be re-entered by means
of the Cost Change Record.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
w
?
CODER)
DESCRIPTION
[REJECT CESS
CAUSE
CORRECTIVE ACTION
31
Invalid Job Status
R
The job status field did not
Correct the job status field and resubmit
Code
contain the proper code (1, 2, 3,
the input card.
4, or blank).
32
Duplicate Job Plan
R
A Job Plan Record of the same type
No corrective action required.
Record
for the job identification-organi-
zation combination has already
been submitted.
33
Incorrect Job Plan
R
A Job Plan Record was used in an
Use the Job Plan Change Record to correct
Conversion
attempt to change the type plan
or add to the original Job Plan Record.
originally submitted. The Job
Plan Record can only be used to
change a Type 1 plan to a Type 3
plan.
34
Changing Job Plan
R
A Job Plan Change Record was used
Verify and correct, if necessary, the
that does not exist
in an attempt to change or delete
control fields of the input record. Be
a job plan record that does not
sure the type change field is correct.
exist.
35
Milestone event was
R
A milestone event was submitted
Verify the control fields of the input
submitted in error
against a type 1 or 2 Job Plan.
document and correct them if necessary.
36
Line and Skill Codes
R
The Line Code and Skill Code for a
Correct the input card and resubmit it.
are not blank
Type 1 plan were not blank.
37
Type plan does not
R
The type plan field on the change
Correct the input card, and resubmit it.
agree
record does not agree with the
type plan field on the master file.
38
Duplicate Authorized
P/R
Duplicate Authorized Job Master
No corrective action required.
Job Master Change
Change Records were submitted.
Record
The first record is processed.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
w
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE _
I
CORRECTIVE ACTION
39
Organization field
R
The Authorized Job Master Change
Correct the input card and resubmit it.
should be blank
Record was not the proper format.
When the organization field contains
data, the change record must apply
to the type completion and
completion date only.
40
Invalid Actual Start
R
The characters in the Actual Start
Correct the input card and resubmit it.
Date
Date field were not valid or the
date was after the processing date.
41
Invalid Actual Stop
R
The characters in the Actual Stop
Correct the input card and resubmit it.
Date
Date field were not valid or the
date was after the run date.
42
Invalid Type Change
R
The Type Change Field contained an
Consult Section 2 of the User's Guide for
Code
invalid character.
the allowable characters in the Type Change
Field. Correct input card and resubmit it.
43
Invalid Change Period
R
The Change Period Field contained
Consult Section 2 of the User's Guide for
an invalid character. Only 1, 2,
the change period codes. Correct the
or 3 can be used.
input card and resubmit it.
44
Manhour Field must be
R
The manhour field was not numeric.
Correct the input card and resubmit it.
numeric
45
Manhour Dollar Field
R
The manhour dollar field was not
Correct the input card and resubmit it.
must be numeric
numeric.
46
Invalid date
R
The date field contained invalid
Correct the input card and resubmit it.
characters.
47
Incorrect suspension,
R
An attempt was made to suspend,
No corrective action required.
cancellation, or
cancel, or complete a job that has
completion
already been deleted from the
master file.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ERROR
CODE
?
Authorized Job Master
Change Record after
completion/cancell-
ation/suspension
Invalid suspension or
cancellation
Activity against a
cancelled or com-
pleted assignment
Status field was
blank
Invalid employee
number
Non-numeric Rate
Invalid M/I Code
Invalid time
Invalid type hours
Invalid Completion
Date
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
'qW
PROCESS
REJECT
An Authorized Job Master Change
Record was submitted after a
Completion/Cancellation/Suspension
Record.
An attempt was made to suspend a
job that had already been can-
celled.
Activity was submitted against a
job that was cancelled or com-
pleted for less than two weeks.
The status field on the Status
Record card cannot be blank.
The employee number field was not
blank.
The employee rate contained
alphabetic characters.
The M/I field did not contain a
blank, M, or I.
The hours worked field contained
other than numeric characters.
This is a keypunch mistake.
The completion date field con-
tained invalid characters.
?
No corrective action is required. The
Authorized Job Master Change Record is
processed.
No corrective action required.
No corrective action required.
Correct the input card and resubmit it.
Resubmit the data on a Daily Labor Card.
Resubmit the data on a Daily Labor Card.
Resubmit the data on a Daily Labor Card.
Resubmit the data on a Daily Labor Card.
Resubmit the data on the proper colored
card.
Correct the input card and resubmit it.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
w
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
58
Invalid Job Plan
P
Job Plan Change Record removed.
If the cost data is correct, submit a Job
Change Record
planning data from the Master File
Plan or Job Plan Change Record for the
even though cost data existed in
cost data.
the record.
If the cost data is incorrect, submit a
Cost Change Record to remove the cost data.
59
Both the manhour and
P
Either the manhour or the manhour
No corrective action required.
manhour dollar fields
dollar fields contained data.
did not contain data.
60
Cost fields became
R
After performing the calculations
Correct the input card and resubmit it.
negative
indicated by the Cost Change
Record, one or more of the cost
fields on the master file became
negative.
61
Cost data became
R
After performing the calculations
Correct the input card and resubmit it.
invalid
indicated by the Cost Change
Record, the cumulative figures
became less than the fiscal year
or the fiscal year became less
than the current period.
62
Not Used
63
Not Used
64
Attempt to delete a
P
The input card deleted a field
No corrective action required.
blank field
that was already blank.
65
Duplicate Completion
P
An-actual stop date has already
No corrective action required.
Date
been entered for this phase.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
w
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
66
Cost charges on file
P
A job identification or a job
if the transaction was correct., no further
for deleted job.
identification-organization
action is required.
combination was deleted from the
file even though cost data existed
If the transaction was in error, reinstate
on the file.
the job with a Record of.New Assignments,
Job Plan Record and a Cost Change Record.
67
Not Used
68
Invalid Type Change
R
An attempt was made to add data to
Correct the Type Change Field and resubmit
Field
an already filled field.
the input card.
69
Deletion of a blank
P
A blank field was deleted by the
No corrective action required.
field.
change record.
70
Unplanned charges
P
Charges already on the master file
Submit the necessary Job Plan Change Records
occurred when going
became unplanned as the result of
to plan for all the costs on the master file
from type plan 2 to
changing the job plan to type 1.
type plan 1
71
Unplanned charges
P
Charges already on the Master File
Submit the necessary Job Plan Change Records
resulted when the
became unplanned as the result
to plan for all the costs on the Master File
Job Plan Record was
of changing the job plan to type 3.
changed to Type 3
72
Changed type plan
R
An attempt was made to change a
The type 3 plan must be deleted with the
from 3 to 1
type 3 job plan to type 1 plan.
Job Plan Change Record before the type 1
plan is submitted.
73
Changed to existing
P
An attempt was made to add
Use a Job Plan Change Record to add the
type plan
additional planning information
new data.
to a job plan that had already
been submitted.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
'qW
?
ERROR
PROCESS
CODE
REJECT
The
skill
on
the
input
card was
If the
skill
code is correct, add the skill
not
in the
Skill
Rate
Table.
to the
Skill
Rate Table and resubmit the
input
card.
If the skill code is not valid, correct
the input card and resubmit it.
Incorrect Production
Schedule Card
Incorrect change code
Incorrect Adjustment
Unplanned allocation
data
Unknown Program
Category Code
An attempt was made to change or
delete a production schedule that
has never been submitted.
An attempt was made to add a
production schedule to one that
has already been submitted.
An Allocation Adjustment Card was
submitted for-which no data exists
on the Master File.
Charges were accrued against a
CIP Line Item-Division-Skill for
which no allocation planning data
exists.
Correct the ACD code and resubmit the
input data.
Correct the change code and resubmit the
input data.
Correct the input card and resubmit it.
Submit a Skill Extension Card to allocate
resources to the CIP Line-Item Division-
Skill combination.
80-80 Duplication
Duplication through
sort field
The CIP Line-Item has not been
assigned a Program Category Code.
P/R lIdentical cards were submitted.
The control fields of two or more
of the same type cards were
duplicates.
Submit Program Category Card.
The first card is processed. All other
duplicates are rejected. No corrective
action is required.
Correct the input card and resubmit it.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
83
Invalid Skill Code
R
The skill code was invalid.
Inform
ACCD
of the new
skill code and re-
submit
the
input card.
84
Invalid Rate Entry
R
The rate entry was incorrect.
Correct
the
input card
and
resubmit
it.
85
Invalid Line Item
R
The line item identification was
Correct
the
input card
and
resubmit
it.
Identification
not of the proper format.
86
Description is Blank
R
An attempt was made to add a new
Add the
description to
the
input record
for Add
entry to.the Skill Rate Table or
resubmi
t it
.
the Program Category Table without
the proper description.
87
Invalid Program
R
The program category code was not
Correct
the
input card
and
resubmit
it.
Category Identifica-
of the proper format.
tion
88
Invalid Organization
R
The organization code was not
Correct
the
input card
and
resubmit
it.
Code
alphabetic.
89
Invalid Manhours
R
The manhour field was not numeric.
Correct
the
input card
and
resubmit
it.
Entry
90
Invalid Completions
R
The completions field was not
Correct
the
input card
and
resubmit
it.
Entry
numeric or blank.
91
Invalid Cancellations
R
The cancellations field was not
Correct
the
input card
and
resubmit
it.
Entry
numeric or blank.
92
Invalid ACIC Unit
R
The ACIC Unit field contained a
Correct
the
input card
and
resubmit
it.
Number
character other than 1, 2, 3, 4,
5, or 6.
93
Invalid Fiscal Year
R
The number 8 is the only allowable
When th
e fiscal year should
be 9, notify
character.
ACCD.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
w
?
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
94
Invalid
Jobs Number
R
The number of new jobs scheduled
Correct
the
input
card
and
resubmit
it.
for completion was in error. The
field contained an alphabetic
character.
95
Invalid
Completion
R
The Completion Manyears Value
Correct
the
input
card
and
resubmit
it.
Manyear
s Value
field contained an alphabetic
character.
96
Invalid
Inventory
R
The Inventory Jobs value contained
Correct
the
input
card
and
resubmit
it.
Jobs Va
lue
an alphabetic character.
97
Invalid
Inventory
R
The Inventory Manyears field con-
Correct
the
input
card
and
resubmit
it.
Value
tained an alphabetic character.
98
Invalid
Completion
R
The Completion Dollars field con-
Correct
the
input
card
and
resubmit
it.
Dollars
Value
tained an alphabetic character.
99
More tha
n 6 errors
R
More than six errors were found
Correct
the
input
card
and
resubmit
it.
in the
card
in the input card. Five are
The complete
card
must
be checked manually
listed on the report.
to determine
all
the errors.
100-
Invalid
Inventory
R
The Inventory Dollars field con-
Correct
the
input
card
and
resubmit
it.
Dollars
Value
tained an alphabetic character.
101
Invalid
Quantity
R
The Quantity field contained an
Correct
the
input
card
and
resubmit
it.
alphabetic character.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ? MW -
ERROR
CODE
DESCRIPTION
PROCESS
REJECT
CAUSE
CORRECTIVE ACTION
94
Invalid
Jobs Number
R
The number of new jobs scheduled
Correct
the
input
card
and
resubmit
it.
for completion was in error. The
field contained an alphabetic
character.
95
Invalid
Completion
R
The Completion Manyears Value
Correct
the
input
card
and
resubmit
it.
Manyear
s Value
field contained an alphabetic
character.
96
Invalid
Inventory
R
The Inventory Jobs value contained
Correct
the
input
card
and
resubmit
it.
Jobs Va
lue
an alphabetic character.
97
Invalid
Inventory
R
The Inventory Manyears field con-
Correct
the
input
card
and
resubmit
it.
Value
tained an alphabetic character.
98
Invalid
Completion
R
The Completion Dollars field con-
Correct
the
input
card
and
resubmit
it.
Dollars
Value
tained an alphabetic character.
99
More tha
n 6 errors
R
More than six errors were found
Correct
the
input
card
and
resubmit
it.
in the
card
in the input card. Five are
The complete
card
must
be
checked manually
listed on the report.
to determine
all
the errors.
100'
Invalid
Inventory
R
The Inventory Dollars field con-
Correct
the
input
card
and
resubmit
it.
Dollars
Value
tained an alphabetic character.
101
Invalid
Quantity
R
The Quantity field contained an
Correct
the
input
card
and
resubmit
it.
alphabetic character.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
?
3.4 Discrepancy Reports
Four discrepancy reports are produced at critical points in
the processing cycle. These reports list the activity data that has
not met the tests to insure accurate updating of the Data Base. Correc-
tive action should be taken and the data resubmitted within the same
processing cycle. This will insure the accuracy of the Data Base, thus
enhancing its value. Reports produced will portray factual and complete
status only if the activity data are current and correct.
3.4.1 The first discrepancy report (PCN 91329) is a product
of the Activity Edit Program. A card image is printed followed by the
error codes defining the discrepancy or discrepancies (See Exhibit 3-1).
This report is in sequence by Transaction Code within Job ID for each
organization. If an organization had no errors reported, the discrepancy
report will be one page, identifying the organization followed by the
message, "YOU HAD NO ERRORS IN YOUR INPUT."
3.4.2 The Status Master Discrepancy Report (PCN 11305) is
a product of the Status Master Update Program. This report reflects the
image of the input record, followed by error codes relating to the dis-
crepancies encountered (See Exhibit 3-2). In addition, a Status Master
Record will be printed if cost charges are present for a deleted job (See
Exhibit 3-2.1). The format will show actual hours and dollars this month,
fiscal year, and cumulative totals for the categories of Regular, Overtime,
and Military. The total hours for this week are printed to the right of
the monthly totals. This condition is identified by Error Code 66. The
(M) print line references the monthly totals, (F) the fiscal, and (C) the
cumulative totals. Cost totals will appear on the last page of the
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
0
?
?
Discrepancy Report (See Exhibit 3.2.2). Heading information is printed
to identify the vertical columns of totals by hours and dollars for this
week, this month, fiscal year, and accrued to date. The horizontal lines
are identified by heading information to the left of each print line.
There will be one print line for each of the following: Old Status,
Daily Labor, Adjustments, Cancel-Complete, and New Status. These totals
may be used to cross-check with previous run totals plus current activity
by Daily Labor, Adjustment, and Cancel-Complete categories. The New
Status should be a net result of processing all activity against the Old
Status data file. This report may also provide a quick look at plant
activity during the current processing cycle.
3.4.3 The Resource Allocation Edit Discrepancy Report
(PCN 91306) is a product of a Card-to-Tape and Edit Program. The error
code and description are printed, followed by the image of the record in
error. These input records are critical to the Resource Allocation
Processing Cycle. Errors should be corrected and resubmitted within the
current processing cycle to achieve realistic and true reports for the
month.
3.4.4 The Resource Allocation Master Discrepancy Report
(PCN 51308) is a product of the Resource Allocation Update Program. The
record image is followed by errors encountered in attempting to update
the Resource Allocation Master File (See Exhibit 3-4). The inputs appli-
cable to this processing are the Production Schedule, Skill Rate, Program
Category, and Allocation Adjustment Records. Corrective action may be
taken by determining the error and following the recommended procedures.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
3.5 Discrepancy Reports Template
This template is included as an aid in interpreting the PROMACS
Discrepancy Reports. It is utilized by lining up the Transaction Code on
the printed line with the corresponding code on the template. For example,
--- (Transaction Code 00) on the template is lined up with the corresponding
transaction code on the discrepancy report. The data fields, Date, Job ID,
and Job Description, consequently appear in the appropriate windows. The
windows identify the data fields by name and size. In researching the error
codes, the user has, in plain view, the fields referenced as being, in error.
The record description appears to the far right of each code to assist the
user in identifying the record and relating data fields. The proper format
for each field is defined in this manual. Corrective action may be taken
by determining the error and referencing the input record definition to
determine the correct methods to employ.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9 ?
SECURITY CLASSIFICATION SECURITY CLASSIFICATION SECURITY CLASSIFICATION
PCN 91329 PAGE XXX
STATUS ACTIVITY DISCREPANCY REPORT ORGANIZATION CODE XXXX PERIOD ENDING MM-DD-YY
06217 3CRCPCD9 LUNAR MOSAICS 1:1,000,000 COMP 00 *** XX,XX,XX,XX,XX,XX
06227 3CRCPCD9 DBO1 1 06217 LUNAR MOSAICS 1:1,000,000 COMP 0 06217 0 C 01 XX,XX,XX,XX,XX,XX
06227 DR10 3CRCPBD4 4 1900 02 *** XX,XX,XX,XX,XX,XX
06227 DBO1 3CRCPBE5 04 *** XX,XX,XX,XX,XX,XX
06227 3CRCPCD9 3 DC41 010 C CD9P TERRAIN EMBOSS 8670 06257 08307 DRO1 06 *** XX,XX,XX,XX,XX,XX
06237 3CRCPCD9 015 C CC4P DC41 06257 08307 5210 C 07 *** XXsXX,XX,XX,XX,XX
06237 3CRCPCD9 C CD9P DC41 1 900 95000 A 08 *** XX,XX,XX,XX,XX,XX
06237 3CRCDCD9 021 DC41 PHOTO SERVICE 06227 C 09 *** XX,XX,XX,XX,XX,XX
06237 3CRCPCD9 CD9P DC41 10 *** XX,XX,XX,XXXX,XX
06237 DC41 3CRCPCD9 021 07 12 *** XX,XX,XX,XX,XX,XX
06237 DC41 535 C 4CRCPCD9 CD9P 800 20 *** ) Xx, Xx, XX, Au,
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
EXHIBIT 3-1 ACTIVITY EDIT DISCREPANCY REPORT
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
?
SECURITY CLASSIFICATION SECURITY CLASSIFICATION'
STATUS ACTIVITY DISCREPANCY REPORT ORGANIZATION CODE * **
SECURITY CLASSIFICATION
PCN 91329 PAGE XXX
PERIOD ENDING MM-DD-YY
P
A
94 *** XX,XX,XX,XX,XX,XX
D9
TERRAIN EMBOSS
95 *** XX,XX,XX,XX,XX,XX
'E
A
96 *** XX,XX,XX,XX,XX,XX
C
A
97 *** XX,XX,XX,XX,XX,XX
98 *** XX,XX,XX,XX,XX,XX
99 *** XX,XX,XX,XX,XX,XX
08
SECURITY CLASSIFICATION
EXHIBIT 3-1.1
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
w
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
*** PROMACS MASTER UPDATE PROGRAM --- ERROR CONDITIONS AND POSSIBLE ERROR CONDITIONS
SECURITY CLASSIFICATION
PCN 11305 PAGE 999
06237 3CRCPCD9 015 C CC4P DC41 06257 08307 5210 C 07 *~'* 69,68,67
06227 3CRCPCD9 DBO1 1 06217 LUNAR MOSAICS 1:1,000,000 COMP 0 06217 0 C 01 *** 64
06237 DC41 3CRCPCD9 021 07 12 *** 26
06237 3CRCDCD9 021 DC41 PHOTO SERVICE 06227 C 09 *** 64
06237 3CRCPCD9 C CD9P DC41 1 900 95000 A 08 *** 60,61,58,59,62,63
3CRCPCD9 CD9P DC41 C *** 70,71,72,73
06237 DC41 535 C 3CRCPCD9 CD9P 800 20 *** 11,12,19
06237 3CRCPCD9
CD9P DC41 - 10 *** 65,26
06227 3CRCPCD9 3 DC41 010 C CD9P TERRAIN EMBOSS 8670 06257 08307 DRO1 06 *** 32
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
EXHIBIT 3-2 STATUS MASTER DISCREPANCY REPORT
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
*** PROMACS MASTER UPDATE PROGRAM --- ERROR CONDITIONS AND POSSIBLE ERROR CONDITIONS
XXXXXXXX XXXX XXXX X XXX M XXXXXX.X XXXX.X XXXX.X XXXXXXX.XX XXXXX.XX XXXXX.XX XXXXXX?X
F XXXXXX.X XXXXX.X XXXXX.X XXXXXXXX.XX XXXXXXX.XX XXXXXX.XX
C XXXXXX. X XXXXX.X XXXXX.X XXXxxxxX.XX XXXXXX.XX XXXXXX.XX
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
SECURITY CLASSIFICATION
EXHIBIT 3-2.1
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
SECURITY CLASSIFICATION
HOURS
THIS WEEK
OLD STATUS
DAILY LABOR
ADJUSTMENTS
HOURS DOLLARS HOURS
?
SECURITY CLASSIFICATION
PCN 11305
DOLLARS HOURS
FISCAL YEAR TO DATE
DOLLARS
TO DATE
SECURITY CLASSIFICATION
EXHIBIT 3-2.2
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ? Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
PROMACS RESOURCE ALLOCATION EDIT DISCREPANCY REPORT
08 UNRECOGNIZABLE CARD
A 35:7' AIR INFO S
85 INVALID LINE ITEM ID
6CMXXMISCELLANEOUS JOB 6CMMISCELLANEOUS
102 INVALID CHANGE CODE
051073CRCDDAA000010000I0000I000010000100001000010000100001000010000100001
83 INVALID SKILL CODE
3CRCDDCC00000105000010000A
94
INVALID JOBS NUMBER
95
INVALID
COMPLETION MAN YRS
96
INVALID
INVENTORY JOBS NO.
97
INVALID
INVENTORY MAN YRS
98
INVALID
COMPLETION DOLLARS
100
INVALID
INVENTORY DOLLARS
3018063CRCD A000A000000A000000A000A000000A000000A000A000000A
SECURITY CLASSIFICATION
PCN 91306
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 ?
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
DISCREPANCY REPORT OF RESOURCE ALLOCATION MASTER UPDATE
E 435 ENGRAVER A
3EHAU JOG REVISE/REPRINT 3EH JOG REVISE/REPRINT A
2
06237 3EHAU DC C 90 88 84 51 51 19 22
3EHAU DC C 0 980 760
3EHAV DC C 25 0 435 20
3EHAZ
SECURITY CLASSIFICATION
PCN 51308 PAGE XX
PERIOD ENDING DA MTH YR
54 *** 10
55 *** 10
** 74
0 0 0 0 A 52 *** 75
5 677
*** 78
*** 79
SECURITY CLASSIFICATION SECURITY CLASSIFICATION
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
 Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9
P R o c ~ c s ~ScQ ?c cy IREPoQT
-- 4~1~1111
Sarno
s~oo.
1-110-111 its 11111=111 Ili II
1t~6e oq3 qcwlmff
..~ i~ESU Od K
Jo r~~oME ao
8=D
3og ~EScR.~PT~o~1
EQito COPS
S
v zw. Aga S'.' ost aov 3 T~ ~4
a roar a~scawrda_
~1L J Qtsl%av~at~~..~V
~.Yt+100..tr6~ 'Sorb
~R CND
Sow Q '1' C~1swm*I'
C~~t cMp1~1~
ST~vS ~Ecoa~
~A%'..~t `,Ac3o0.
QQoOVCt~o~?l SGNEO.~`E
Srt~~.~. ~w~E
QgoG~lwh? C%' E.6-DRj
Q~`uxAt~ow1 ~4~1v'~tt~l~htT
oR~AN~~,gT~O~I 't11~1.E.
Approved For Release 2008/06/04: CIA-RDP73T00325R000100030001-9