Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
vessel number barges tonnage. 20. ABSTRACT (cismbus so reverse oidf v nmceein mod Ddeatif by bloc0k nmbe). *. Lock Performance-Monitoring--s.em-User's ...
Typology: Exercises
1 / 208
This page cannot be seen from the preview
Don't miss anything!
AD-A165 848 LOCK PERFORMANCE MONITORING SYSTEM USER'S MANtL FOR in DATR MATER (^) RNRLYSIS(U) RESOURCES (^) SUPPORTCORPS OF CENTER ENGINEERS n Y (^) FORT FLEMING SELVOIR ET AL. VA UNCLRSSIFIED NOV 85 MRSC-9B-UH-2 FIG 13/2 NL
IIIIIIIIIIIIIl
lflflflflflflflflflflflfl
I ' p.-,
C..
Loo-
'4,
_6 IL
W.12.
=L~j125 (^) --- (^) L 1 4 111.
MICROCOPY (^) RESOLUTION (^) TEST (^) CHART , (^) , ', Al S l q (^) ,
4.;. C'. (^). .-i
C+ + -,
____ _______ ___ ____ ____ ___ ___ ____ ___--
UNCLASSIFIED SECURITY CLASSIFICATION OF THIS PAGE (Whn Data tm4 RR O
V. REPORT NUMBER. GOVT ACCESSION NO S. RECIPIENT'S CATALOG NUMBER User Maniual 85-UM- K. TITLE (and Subtitle) S. TYPE OF REPORT & PERIOD COVERED
Lock Performance Monitoring System User's Manual for Data Analysis User Manual
6. PERFORMING ORG. REPORT NUMBER User Manual 85-UM- 7. AUTHOR(,) S. CONTRACT OR GRANT NUMBER(&) Marilyn V. Fleming Donna Wood Robert J. Goodwin 9. PERFORMING ORGANIZATION NAME AND ADDRESS 10. PROGRAM ELEMENT, PROJECT. TASK Institute for Water Resources (WRSC-IWR) AREA S WORK UNiT NUMBERS Casey Building Ft. Belvoir, Virginia **22060-
ML9TIBUIO2NSAT ErA Approved fat pubi n1@ Diodbution Unlimited
17. DISTRIBUTION STATEMENT (olethe abstrt e tered i Stock", Itf filamuntkon Repi)
Approved for public release--distribution unlimited.
*** IS. SUPPLEMENTARY NOTES**
19. KEY WORDS (Continue on reveree side 1i nsceear and identi y by block nimbor) PMS Inland waterway waterway traffic lock lockage lock capacity . lock statistics vessel lock process __ tows vessel number barges tonnage 20. ABSTRACT (cismbus so reverse oidf v nmceein mod^ Ddeatif^ by^ bloc0k^ nmbe)
DO '," 1473 EDITION OF I OV SS IS OBSOLETE UNCLASSIFIED SECURITY CLASSIFICATION OF THIS^ PAGE^ (When^ Data^ Entered)
:< .,. ~~.........L..... ........... .........-..... ...... ,... " .:: .,......
By
Marilyn V. Fleming Institute for Water Resources
Donna E. Wood Engineer Automation Support Activity
and
Robert J.^ Goodwin Engineer Automation Support Activity
U.S. Army Engineer Institute for Water Resources Casey Building Fort Belvoir, Virginia 22060-
November 1985 User Manual^ 85-UM-
TABLE OF CONTENTS
Backgrund fPAGE
- C. Hardward and Software Requirements B. Overview and Uses Of Pt4S (Figure 1) - D. Scope and Intent of Guide .0............. TABLE OF CONTENTS (Continued)
PAGE
Appendix
UA (^) PMS System Flowchart .............................. (^15) B Sample Input Forms ......................... ........ 21 C (^) Record Layouts ............................................ (^25) D Valid District EROC Codes ................... (^69) E (^) PMS Control and Option Commands ............................ (^73) F Sample Report Outputs ................................... G* Detailed Report Descriptions ................... (^) 141 H PMS Look-up (^) Tables ........................................ 175 .. (^) I Glossary of Terms ......................................... 201
Table
1 Sample Batch Initiation .................................... (^6) 2 Example Interactive (^) Initiation........................ 7
Figure
1 PMS Overview ........................................... (^) 2 2 Sample of District (^) Reporting Status, CHART2 ................ 10
. data collected at locks (^) '.
lock data co~hined at district -^ c..
inu ero^ re
trnato rascinat
Natan NazerrdO
in
reporats^ i^ sss^
t
r i'^ e^ t
Figure 1il fileOvrve 2il
.. -.^.^.^. .5 .5.. 5 S^ *****^ *^ .,^ 5routine..
software, but some tape handling and job control commands are unique to the p CDC NOS system. The job set-ups In this document reflect this dependence and are specifically for use on the CDC NOS system.
D. Scope and Intent of Guide. This User's Guide has been prepared in two parts to^ provide^ basicP.^^4 instruction for the collection, preparation and analysis of PMS data. The recording and editing of data are discussed in the User Manual for Data 'I Collection and Editing. (^) This Manual provides instruction for data analysis and contains formats for data preparation and formats for the final data files as well as descriptions and formats of the various program look-up tables and instructions for processing the PMS reports. The overall structure of the system, it's components and their relation to the system are explained. A system flowchart is contained in Appendix A. The Guide is not intended to
algorithms, execution times and listings are not included.
II. The PMS Library
The PMS library consists of three data files used as input to the report programs: the detail lockage data file (LCKAGE), the summary data file *(SUMMRY) (^) and the standards information file (STNDRD). Monthly district master files added to the (^) central library are run through a program which updates the
For an interactive session enter: "GET,TAPES/UN=CEW2PD." carriage return "COPY,TAPES." carriage return
*For batch execution, the commands remain the sane but must be preceded by the appropriate "Job" and "User" cards.
A. Detail Data File. (^) (LCKAGE)
Records on the detail lockage data file contain the information
- - - - - - - - - - - - - -.--. *. 1. Batch Initiation
Table 1 is an example batch initiated report. (^) Using Appendix E, decide which computer (^) control statements and PMS parameters will be needed to produce the desired report or data file. Punch cards or create a card image job stream on disk and submit it. It is PMSEXEC which actually creates the report or data file. It is necessary to know how to use the computer to make effective use of the batch approach.
Table 2 is an example session for an interactively initiated report. Refer to Appendix E as necessary. While less computer knowledge (^) is required, it is still necessary to be familiar with log on procedures. (^) To initiate the run, log onto the computer terminal and enter the following:
GET,GENINT ,TAPES,PARMOO1/UN=CEW2PD GENINT
The ensuing prompts will provide further instruction.
! (qjT'
5'/
I".
'I.;
TABLE 1
Sample Batch Initiation
JOB,TO120,CM200000,P3. USER ,XXXXXX,YYYYYY,KOE CHARGE,WWWWWWW,PPP. GET ,GENFILE/UN=CEW2PD. GENFILE. r SKIP,LBL (^) 1. EXIT. ENDIF,LBL1. EXIT. ENDIF,LBL1. DAYFILE ,GENDAY. REPLACE ,GENDAY. end of file indicator USERXXXXXXYYYYYYKOE. CHARGE,WWWWWWW,PPP. CURRENT MONTH IS 0584 DISTRICT H NO INFORM REPORT FILE IS P RUN PROGRAM 501P5P SELECT DATA FOR H2 FROM 0983 TO 0983
For this example: I..
o No INFORM file will be^ saved. o The report will be written to a file named P24833 rather than printed. o The report to be produced is PMS 22 (commodity tonnage summary report). o The report will contain data on traffic using locks in the Louisville district in September 1983. o All other^ report^ processing^ options^ will^ be^ those^ defined^ by^ Appendix G as default.
Be sure the^ proper^ user^ name,^ password,^ charge^ and^ project^ codes^ are^ used^ in^ "- the two USER and CHARGE statements or the job will not run.
-7-"
6
TABLE 2 Continued
THEN HIT A CARRIAGE RETURN, THIS WILL RUN YOUR REPORT(S). 2 " END* OF INTERACTIVE SESSION - TT75, ASSIGNED TO ZZZZZOU. /SUBMIT,PMSEXEC, E 15.10.06. SUBMIT COMPLETE. JOBNAME IS AAQJBBK
For this example -!
o User entries are underlined. o The INFORM file is not a part of the output. o The report is saved as a file and not printed. The file ia named P22834. o The processing time limit is increased to 500 seconds. o The report produced (^) is PMS22 (commodity tonnage report). o The report contains information on traffic using locks in the Lousville District in December of 1983.
Be sure to use the proper user id, password, charge and project codes.
The session will create a file named PMSEXEC which must be submitted when the session is complete. It is PMSEXEC which actually creates the report or data file.
8' ..
rb.~
-.. - --.... ' *... .. ,
.. (^) B. The INFORM File.
each time a PMS edit, report or data extraction job (^) is run. This file contains information on recent changes (^) or additions to the PMS system and should be read periodically. The file may be printed without (^) running the PMS edit or reports by accessing the file INFORM (^) under CEW2PD and printing it
C. District Reporting Status, CHART2 (Figure 2)
The (^) district reporting status chart (CHART2) shows for which months
. each (^) reporting district has submitted data to the PMS central library. (^) Refer to it to ensure that selected (^) data are available.
D. Interpreting Report Outputs.
1. (^) Errors. When a report run does not work, the reason could be that the initial run was set (^) up improperly, that specified data could not be found, that (^) the data contained zeroes or letters in fields where it should (^) not or the job was not given enough (^) time and memory to execute.
a. Improper Set-up. When the job is improperly set up, the report output file will contain only an explanation of the (^) errors in the set up of the initial (^) deck. Correct this and re-run.
b. No Data Selected. Before (^) running a report, make sure the data you are going to extract are on the central (^) library and determine whether to select the "bypass (^) historic tapes option." The extraction program will search for specified data, but the run will terminate (^) if no matches are found. Since the search portion of a run is generally the most expensive, (^) this situation should be avoided. (^) If there is a question as to whether certain data are on the library or if data that should be there apparently (^) are not, contact the PMS coordinator (^) at either the Engineer Automated Support Activity
-" (^) (EASA) or the Navigation Division of the Institute for Water (^) Resources.
c. Bad Data. This problem usually causes the job to terminate when (^) the report program tries to perform an arithmatic operation with alphabetic (^) data or divide by zero. Although the PMS edit checks for these (^) L--. conditions and prints error messages when they (^) occur, it does not prevent them from being written to the final monthly transaction file and (^) entered in the library. If a report cannot be run because (^) of bad data, either redesigr "SELECT DATA" parameters (^) or have the month (^) containing the data removed (^) from the central library or contact (^) the PMS Coordinator at EASA for help.
4.' -7 42 9[
16F
occur each time a file is searched. A given^ report^ may^ require^ a^ search^ of the detail, summary, standards or temporary files created during the^ run.
fall into four categories: chamber^ reports,^ commodity^ reports,^ tow^ transit 1% analysis reports and summary reports.^ A^ description^ of^ some^ conmmon computations follows; a detailed explanation of output components for each report is in Appendix G.
Three terms require special note: vessel operation time, lock operation time, and processing time. The time represented by each of these terms depends upon whether a lockage is single-cut, double-cut, multi-cut, or *multi-vessel, and, in the case of multi-vessel, whether the computation is performed for a vessel oriented report (e.g., tow transit) or a lock oriented report (e.g., chamber and summary reports).
a. Single-cut Lockages.^ For^ single-cut^ lockages,^ vessel operation timre is the sum of the approach, entry, and exit times. Lock
vessel operation^ time^ plus^ lock^ operation^ time.
b. Double-cut Lockages. For double-cut lockages, vessel LI *operation time^ is^ the^ sum^ of^ the^ approach,^ entry,^ and^ exit^ times^ of^ the^ first
c. Multi-cut Lockages. Since only the first cut and the last cut are recorded, vessel operation time is a multiple of^ the^ average^ time
*required by the first and last cuts.^ The^ sum^ of^ the^ approach,^ entry,^ and^ exit
d. 'Multiple Vessel Lockages. For multiple vessel lockages, the vessel operation, lock operation, and processing times recorded can be interpreted in two different ways. A multiple vessel lockage is recorded separately for each vessel served. From the standpoint of individual vessels, the various times spent in a lockage cycle are those calculated as previously stated. The sum for n vessels, likewise, is the sum of the n recordings of
Vessel operation time is:
(latest end of entry - earliest start of lockage) + (latest end of lockage - earliest start of exit).
Lock operation time is:
(latest start of exit - earliest end of entry) + any turnbacks.
*Processing time, (^) again, is vessel operation time plus lock operation time.
IV. Commnon Problems and Restrictions
A. Indirect Access (^) File Size.
A part of most PMS computer jobs is to retrieve a subset of'
B. Reports Requiring Special (^) Handling.
There are (^) forty standard reports in PMS. Thirty-eight can be generated by following the instructions in part III. Two reports, (^) PMS20 and PMS25 must be requested by phoning the PMS coordinator at the Engineer Automation Support (^) Activity (EASA).
PMS20 requires the tow company name. Spelling of (^) owner names in ther Coast Guard vessel file is not consistent; therefore, the (^) same company may appear with a variety of spellings (e.g., B&B Towing or B and B Towing). The search is on vessel name and exact name matching is required, so special intervention and processing is necessary to (^) ensure accurate reporting. PMS requires the structuring of a special parameter file for locks to be compared. Do not try to run these reports (^) without contacting EASA; there will be no report output.