308 lines
11 KiB
Plaintext
308 lines
11 KiB
Plaintext
|
English French Notes Complete/Exclude
|
||
|
|
% are NX, about
|
||
|
|
% are BSE, about
|
||
|
|
% are EXP,
|
||
|
|
and about
|
||
|
|
% are of unknown TYPE.
|
||
|
|
DEVICES THAT HAVE BEEN UPDATED TO FULL Y2K COMPLIANCE:
|
||
|
|
Estimated Cost ($)
|
||
|
|
Actual Cost ($)
|
||
|
|
DEVICES THAT ARE SCHEDULED TO BE UPDATED TO FULL Y2K COMPLIANCE:
|
||
|
|
DEVICES THAT HAVE BEEN REPLACED DUE TO Y2K ISSUES:
|
||
|
|
DEVICES THAT ARE SCHEDULED FOR REPLACEMENT DUE TO Y2K ISSUES:
|
||
|
|
DEVICES THAT HAVE BEEN RETIRED DUE TO Y2K ISSUES:
|
||
|
|
DEVICES THAT ARE SCHEDULED FOR RETIREMENT DUE TO Y2K ISSUES:
|
||
|
|
DEVICES THAT ARE Y2K NON-COMPLIANT BUT ARE TO BE USED 'AS IS'.
|
||
|
|
** FUNCTIONAL CLASSIFICATIONS **
|
||
|
|
MED => Medical equipment PC => General purpose computer equipment
|
||
|
|
FS => Facility management equipment TEL => Telecommunications equipment
|
||
|
|
Y2K Cum by Functional Classification as of
|
||
|
|
FUNCTIONAL CLASSIFICATION:
|
||
|
|
<There are no equipment records with outstanding Y2K issues>
|
||
|
|
COUNT FOR ALL STATIONS
|
||
|
|
TOTALS FOR ALL STATIONS
|
||
|
|
Detailed Y2K Equipment Report
|
||
|
|
by EQUIPMENT CATEGORY
|
||
|
|
by CATEGORY STOCK NUMBER
|
||
|
|
by CMR
|
||
|
|
by SERVICE
|
||
|
|
by MANUFACTURER
|
||
|
|
by LOCAL ID
|
||
|
|
by RESPONSIBLE SHOP
|
||
|
|
for ENTIRE EQUIP FILE
|
||
|
|
Manufacturer~Model
|
||
|
|
Y2K Est Date Act Date Est Cost Act Cost Action
|
||
|
|
Y2K: FC=>Fully Compliant NC=>Noncompliant CC=>Conditionally Compliant NA=>Not Applicable Null=>No Y2K Information
|
||
|
|
ACTION (Noncompliant Only): REP=>Replace RET=>Retire UPD=>Update to Full Compliance USE=>Use Without an Update
|
||
|
|
UTILITY EQUIPMENT DETAILED REPORT
|
||
|
|
Select an IDENTIFIER
|
||
|
|
The first 15 characters of whichever field you select as your IDENTIFIER
|
||
|
|
will be printed with system components in order to help you know what you're
|
||
|
|
looking at. Please choose whichever field is likely to be most helpful.
|
||
|
|
Detailed Util Systems Report
|
||
|
|
This Utility Component is
|
||
|
|
This Utility System is
|
||
|
|
Detailed Report of Utility Systems as of
|
||
|
|
System Entry Number
|
||
|
|
System Family
|
||
|
|
UTILITY EQUIPMENT SUMMARY REPORT
|
||
|
|
Summary Util Systems Report
|
||
|
|
<There are no Utility Systems on which to report>
|
||
|
|
Utility System
|
||
|
|
in this data base.
|
||
|
|
System
|
||
|
|
FC System
|
||
|
|
NC/CC System
|
||
|
|
Family
|
||
|
|
No Family
|
||
|
|
<There is no Utility Equipment on which to report>
|
||
|
|
Component
|
||
|
|
FC Component
|
||
|
|
NC Component
|
||
|
|
CC Component
|
||
|
|
Est Comp
|
||
|
|
Summary Report on Utility Equipment as of
|
||
|
|
NATIONAL ROLL-UP OF Y2K INFORMATION
|
||
|
|
ENY2K_ROLL_UP
|
||
|
|
You must hold security key ENY2K_ROLL_UP in order to execute this option.
|
||
|
|
Please enter starting and stopping dates for activity reporting
|
||
|
|
(or '^' to escape...)
|
||
|
|
Starting date:
|
||
|
|
Stopping date:
|
||
|
|
Cumulative information will be transmitted anyway.
|
||
|
|
The system is now prepared to send a Y2K report to VACO.
|
||
|
|
ENDATE(
|
||
|
|
Y2K National Roll-up (equipment)
|
||
|
|
A national roll-up of Y2K information has been tasked to run via NetWork
|
||
|
|
Mail. You will receive a copy of the message.
|
||
|
|
Roll-up of Y2K Information
|
||
|
|
>>> Mailgroup already exists...nothing added
|
||
|
|
This mail group was added for use in the Police and Security package.
|
||
|
|
It will receive confirmation messages from Q-VAP where the crime
|
||
|
|
reports are sent.
|
||
|
|
>>> VAP mail group added successfully!
|
||
|
|
>>> You have been added as a member of this mail group.
|
||
|
|
Please add members or remove yourself as appropriate.
|
||
|
|
>>> NOTE: Mail group not added!!!
|
||
|
|
Please check your file and type D EN^ESP116PT to try again.
|
||
|
|
...Searching for duplicate SSNs in file #910
|
||
|
|
IEN SSN
|
||
|
|
**** NO DUPLICATE SSN ENTRIES WERE FOUND ****
|
||
|
|
...Duplicate entry search Completed.
|
||
|
|
...Deleting non-Fileman soundex x-ref on file #910
|
||
|
|
...Creating FileMan soundex x-ref on file #910
|
||
|
|
...Adding identifiers to subfile #916.05
|
||
|
|
...Creating FileMan
|
||
|
|
x-ref on file #910.2
|
||
|
|
x-ref on file #912.09
|
||
|
|
x-ref on file #910.85
|
||
|
|
DUP SSN REPORT ON #910
|
||
|
|
Type of report to print:
|
||
|
|
Print ES*1*22 Conversion Report
|
||
|
|
Press ANY Key to Exit
|
||
|
|
There is no data in ^XTMP(
|
||
|
|
, to print.
|
||
|
|
File #912 ien:
|
||
|
|
UOR#
|
||
|
|
DATE/TIME RECEIVED:
|
||
|
|
DATE/TIME OF OFFENSE:
|
||
|
|
INVESTIGATING OFFICER:
|
||
|
|
CASE STATUS:
|
||
|
|
COMPLETED FLAG:
|
||
|
|
DELETED/REOPENED FLAG:
|
||
|
|
DATE/TIME:
|
||
|
|
PREVIOUS ID#:
|
||
|
|
LOST/STOLEN PROPERTY:
|
||
|
|
LOSS: $
|
||
|
|
Converted to:
|
||
|
|
Converted by:
|
||
|
|
Date/time:
|
||
|
|
Original
|
||
|
|
Classification:
|
||
|
|
Patch ES*1*22 Conversion Report
|
||
|
|
List of Converted Entries in File #912
|
||
|
|
Patch ES*1*22 Conversion Completion Report (cont.)
|
||
|
|
Completed by:
|
||
|
|
List of Unconverted Entries in File #912
|
||
|
|
to be Reviewed by User
|
||
|
|
ABOVE $100 (GOV'T)
|
||
|
|
ABOVE $100 (PERSONAL)
|
||
|
|
ABOVE $1000 (GOV'T)
|
||
|
|
BELOW $1000 (GOV'T)
|
||
|
|
ABOVE $1000 (PERSONAL)
|
||
|
|
BELOW $1000 (PERSONAL)
|
||
|
|
That record doesn't need to be converted. Try again...
|
||
|
|
Patch ES*1*22 Conversion Utility
|
||
|
|
LOST/STOLEN PROPERTY:
|
||
|
|
(No information available.)
|
||
|
|
Converted by:
|
||
|
|
You may modify the following sub-record(s) --
|
||
|
|
Sub-record #
|
||
|
|
Current Subtype
|
||
|
|
Select sub-record #:
|
||
|
|
The subrecord selected may be converted
|
||
|
|
to one of the following:
|
||
|
|
Select (a) or (b):
|
||
|
|
Patch ES*1*22 Conversion Completion
|
||
|
|
Continuing with this process will 'COMPLETE' the conversion process
|
||
|
|
for patch ES*1*22.
|
||
|
|
This means that --
|
||
|
|
(1) The records in the ESP OFFENSE REPORT file (#912)
|
||
|
|
will no longer be available for conversion.
|
||
|
|
(2) The menu option Conversion Management for ESP*1*22
|
||
|
|
[ESP CONVERISON FOR ES*1*22] will be placed out-of-order.
|
||
|
|
(3) The Conversion Completion Report will be printed with your
|
||
|
|
name as Completer.
|
||
|
|
(4) A mail message will be sent to Police management (i.e.,
|
||
|
|
through the ESP VACO 48 HR CRITERIA Mail Group) regarding
|
||
|
|
this conversion completion.
|
||
|
|
(5) A mail message will be sent to IRM staff (i.e., through
|
||
|
|
the IRM and/or PATCHES Mail Group) which instructs IRM to
|
||
|
|
delete the conversion routines from the system.
|
||
|
|
Do you wish to proceed with Completion?:
|
||
|
|
Proceeding with Completion...
|
||
|
|
Patch ES*1*22 Conversion queued for Completion.
|
||
|
|
Patch ES*1*22 Conversion will NOT be completed.
|
||
|
|
The Conversion process on the ESP OFFENSE REPORT file (#912)
|
||
|
|
for patch ES*1*22 has been completed.
|
||
|
|
Completed on:
|
||
|
|
The List of Converted Entries in File #912 and
|
||
|
|
the List of Unconverted Entries in File #912 reports follow.
|
||
|
|
Completed by user#
|
||
|
|
ESP CONVERSION FOR ES*1*22
|
||
|
|
Conversion Completion for ES*1*22
|
||
|
|
G.ESP VACO 48 HR CRITERIA@
|
||
|
|
ESPMSG(
|
||
|
|
No further conversion will be allowed on file #912
|
||
|
|
using ES*1*22 routines.
|
||
|
|
The Crime Statistics report for each month since October 1, 1997,
|
||
|
|
**must** be regenerated. Use the Generate Crime Statistics
|
||
|
|
[ESP GENERATE CRIME STATISTICS] option to accomplish this.
|
||
|
|
Delete Routines for ES*1*22
|
||
|
|
The following routines may be deleted from your system:
|
||
|
|
Print Conversion Reports;EN^ESP122P1
|
||
|
|
User Conversion of File #912 Records;MANUAL^ESP122P2
|
||
|
|
Patch ES*1*22 Conversion Completion;COMPLETE^ESP122P3
|
||
|
|
Patch ES*1*22 Conversion Management
|
||
|
|
You may select one of the following options:
|
||
|
|
You have opted to
|
||
|
|
Conversion Reports queued as Task #
|
||
|
|
Unable to queue Conversion Reports.
|
||
|
|
Use the Conversion Management print option later.
|
||
|
|
File #912.9, filing entry #
|
||
|
|
was unsuccessful.
|
||
|
|
File #912.9, entry #
|
||
|
|
was successfully filed.
|
||
|
|
BELOW $100 (GOV'T)
|
||
|
|
BELOW $100 (PERSONAL)
|
||
|
|
effective October 1, 1997.
|
||
|
|
has not been properly inactivated.
|
||
|
|
THEFT-GOVERNMENT PROPERTY
|
||
|
|
File #915, entry #55
|
||
|
|
...not updated.
|
||
|
|
Field #.01'=THEFT-GOVERNMENT PROPERTY
|
||
|
|
File #915, entry #55 - THEFT-GOVERNMENT PROPERTY
|
||
|
|
...successfully updated.
|
||
|
|
THEFT-PERSONAL PROPERTY
|
||
|
|
File #915, entry #56
|
||
|
|
Field #.01'=THEFT-PERSONAL PROPERTY
|
||
|
|
File #915, entry #56 - THEFT-PERSONAL PROPERTY
|
||
|
|
>>Entry for this time is in use.
|
||
|
|
To create an additional entry for this time, enter time in quotes.
|
||
|
|
Try later to edit same entry.
|
||
|
|
Select Facility:
|
||
|
|
*********Must key a full date, (Month, Day, Year) ***********
|
||
|
|
DATE not found. Please try again.
|
||
|
|
COMPLAINANT DATA
|
||
|
|
VICTIM DATA
|
||
|
|
OFFENDER DATA
|
||
|
|
WITNESS DATA
|
||
|
|
to add a new entry
|
||
|
|
to add a new entry.
|
||
|
|
Is this an unknown offender
|
||
|
|
Which name do you want to delete from the Master Name Index?
|
||
|
|
** PLEASE NOTE **
|
||
|
|
Entries in the Master Name Index file are referenced from many other files.
|
||
|
|
Before you are allowed to delete a duplicate entry you must first indicate
|
||
|
|
the correct entry to keep so that all references in all files can be changed
|
||
|
|
to the correct entry.
|
||
|
|
Which entry do you want to keep?
|
||
|
|
You must select a different entry!
|
||
|
|
Select a name:
|
||
|
|
Replace
|
||
|
|
and then delete
|
||
|
|
This option will allow the editing of Badge Number and Rank on those
|
||
|
|
people holding the ESP POLICE security key.
|
||
|
|
Select POLICE NAME:
|
||
|
|
AK.ESP POLICE
|
||
|
|
Only employees who hold the ESP POLICE security key can be edited.
|
||
|
|
This evidence record is now sensitive.
|
||
|
|
Do you want to make it nonsensitive
|
||
|
|
Answer NO if you want the report to remain sensitive. Answer YES if you want the report to be nonsensitive.
|
||
|
|
This evidence record is now nonsensitive.
|
||
|
|
OUTPUT FROM WHAT VA POLICE FILE:
|
||
|
|
ESP*
|
||
|
|
DAILY JOURNAL
|
||
|
|
RECORD DOESN'T EXIST!
|
||
|
|
SECTION I - PERIOD COVERED
|
||
|
|
FROM:
|
||
|
|
SECTION II - ASSIGNMENTS
|
||
|
|
SECTION III - SPECIAL INSTRUCTIONS
|
||
|
|
REVIEW (Chief, Police Service)
|
||
|
|
VA POLICE DAILY OPERATIONS JOURNAL
|
||
|
|
(Automated VA Form 10-1433)
|
||
|
|
VA Facility
|
||
|
|
Date/Time Printed
|
||
|
|
(Automated VA Form 10-1433a)
|
||
|
|
SECTION IV - ENTRY SUMMARY
|
||
|
|
Enter the name in'Last,First Middle' format [<30 characters]. You may also enter part of the name for lookup purposes
|
||
|
|
Do you want to add this name
|
||
|
|
NO UPDATING HAS OCCURRED!!!
|
||
|
|
This name is already in the Master Name Index file.
|
||
|
|
RACE:
|
||
|
|
Is this the correct one
|
||
|
|
Do you want to edit this record
|
||
|
|
Now returning to the Offense Report!
|
||
|
|
Now returning to the Violation Notice!
|
||
|
|
POLICE OFFICER
|
||
|
|
NO ^___ ALLOWED!
|
||
|
|
Do you want to enter another AKA
|
||
|
|
You must enter Yes or No.
|
||
|
|
Height:
|
||
|
|
Hair Color:
|
||
|
|
Eye Color:
|
||
|
|
Skin Tone:
|
||
|
|
Scars/Marks:
|
||
|
|
DL#:
|
||
|
|
Place of Employment:
|
||
|
|
Work Address:
|
||
|
|
Work Address [line 2]:
|
||
|
|
City:
|
||
|
|
Zip:
|
||
|
|
ID:
|
||
|
|
Office Phone:
|
||
|
|
Home Address:
|
||
|
|
Home Address [line 2]:
|
||
|
|
Home Phone:
|
||
|
|
ALIAS
|
||
|
|
Updating
|
||
|
|
This entry already exists!
|
||
|
|
Another user is editing this record!!
|
||
|
|
NO ^'S ALLOWED!
|
||
|
|
Driver's License #:
|
||
|
|
ID Badge:
|
||
|
|
4) Place of Employment:
|
||
|
|
5) Home Address:
|
||
|
|
Home Address [Line 2]:
|
||
|
|
Address [Line 2]:
|
||
|
|
Alias:
|
||
|
|
Alias
|
||
|
|
Enter: <RET> to continue or 1-7 to edit:
|
||
|
|
NUMBER MUST BE 1-7
|
||
|
|
Record is in use. Try later.
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|