Attachment_4_-_Sample_TORFP_PWS_1_-_NDC_NAVIGATION_OM.pdf

Attachment 4: Sample Task Order Request for Proposal (TORFP) #1 NDC Navigation Systems O&M

PERFORMANCE WORK STATEMENT (PWS)

1. BACKGROUND

Institute for Water Resources (IWR) is a United States Army Corps of Engineers (USACE) Field Operating Activity (FOA) located within the Washington, DC National Capital Region (NCR), in Alexandria, VA and with satellite centers in New Orleans, LA, Davis, CA, Golden, CO, and Pittsburgh, PA. IWR was created in 1969 to analyze and anticipate changing water resources management conditions, and to develop planning methods and analytical tools to address economic, social, institutional, and environmental needs in water resources planning and policy. IWR is currently responsible for a number water resources activities or programs, including evaluation of Civil Works (CW) strategic plans, CW policies and programs, investment and financial analysis, performance measurements and evaluations, infrastructure analysis, climate change and other water related activities. IWR provides technical assistance to Corps divisions, districts, laboratories, Federal agencies, international organizations, financial institutions and other countries, in encompassing a broad range of topic areas related to levee and dam safety, risk assessment, dredging requirements, port/waterway transport, aquatic ecosystem restoration, environmental stewardship, flood and drought risk management, emergency preparedness, watershed planning, regulatory, multipurpose water resources including hydroelectric power, water supply and reallocation, recreation, and other water and related land resources issues.

The Navigation and Civil Works Decision Support Center (NDC) within IWR was created to help maintain congressionally authorized Federal Navigation projects in a safe, efficient and environmentally sustainable manner. To accomplish this mission, navigation data is essential in order to support sound defensible decisions. NDC has developed national navigation databases of lock, dredging, and “Notice to Navigation Interests” data in response to this data requirement. To maintain and enhance the systems, IWR seeks services and support in the continued development and operations and maintenance (O&M) of NDC’s following navigations systems, all of which utilize Oracle database and are hosted on Solaris or Linux servers:

Lock Performance Monitoring System (LPMS): This system is used at each lock site operated by USACE to account for all traffic. This system is comprised of multiple database instances that segregate the user experience: LPMS Production for data entry and live reporting; an Oracle Spatial (AISEP) module that analyzes near real-time vessel positions using Automatic Identification System (AIS) signals to auto-fill some data entry date fields based off of spatial triggers; LPMS Training for new users and the introduction of new features;

LPMS Warehouse(s) for long term storage and analytics; and the Corps Locks public website that is used to disseminate information to the public and industry.

Additional information on LPMS can be found at:

http://corpslocks.usace.army.mil/lpwb/f?p=121:1:0

Dredging Information System (DIS): The DIS is used to keep track of information as it relates to USACE dredging jobs, to include both Corps and industry executed jobs, and data from the planning process through the completion of the job. Additional information on IWR dredging program and DIS can be found at: http://www.navigationdatacenter.us/dredge/dredge.htm

Notice to Navigation Interests (NTNI): The NTNI system is used to track and make available all USACE work/issues, or work/issues as identified by USACE Regulatory, which may affect navigation in Federal harbors and channels. This system is comprised of two pieces: the NTNI data entry site available only internally to USACE, and the NTNI public site. Additional information on NTNI can be found at: http://ntninotices.usace.army.mil/lpwb/f?p=150:1:0

2. SCOPE

The contracting team will be expected to develop and provide O&M for the LPMS, DIS, and NTNI navigation systems as well as their subcomponents, as described in the tasks below. The contracting team should provide code that is accurate, understandable, and well documented. The code should be in accordance with and acceptable to the DoD code repository Defense Intelligence Information Enterprise (DI2E), which will be used as the main code repository and task tracking tool (through the use of Bitbucket and Jira respectively). The deliverables and any recommendations should recognize and adhere to current USACE IT policy. The contracting team is expected to work with the Contracting Officer Representative (COR) and/or the Technical Point of Contact (TPOC) to ensure technical accuracy, clarity and appropriateness of key software and documentations while balancing project tasks, deadlines, and deliverables.

All code and deliverables developed are the property of USACE.

The contracting team should be familiar with the USACE Civil Works Program, specifically the navigation mission. The contracting team should have a basic understanding of tow and barge operations. The contractor team should understand the basics of lock operations and data requirements of the shippers and carriers. The contractor shall have extensive technical knowledge of programming in Oracle and APEX (Corps standards) to make the necessary revisions to the program. In addition to these general skills and experience, the contracting team should also possess the following:

Knowledge and experience in developing and maintaining a relational database operated from a data center or the Amazon Web Services (AWS cloud).

Knowledge and experience of data entry and options to increase automation and efficiency, including hand held and scanning technology.

Knowledge and experience with data systems, social media operations, and the development of applications for smart phones and tablets.

Knowledge and experience in optimizing the performance of existing Oracle based applications, including procedures, functions, etc.

Knowledge and experience with creating REST services utilizing common data dissemination formats.

3. GENERAL REQUIREMENTS

The following sub-sections provide details of various general requirements for this effort.

3.1. Non-Personal Services

The contractor shall provide strictly non-personal services and contractor employees are not subject to direct supervision and control by the Government. The contractor shall advise and support the Government but shall not make final decisions or certifications on behalf of the Government nor perform any inherently governmental functions. The contractor and its employees shall not represent the Government nor appear to represent the Government in performance of these contract services.

Contractor personnel shall clearly identify themselves as contractor employees in all interactions during contract performance.

3.2. Place of Performance

All work will be performed at the contractor’s site.

3.3. Period of Performance

The period of performance is from date of award through 6 months.

3.4. Materials

All materials, minus expendable supplies, purchased by the contractor with funds from this task order and used under this task order, become and remain the property of the Government. This is to include all created or altered source code.

3.5. Travel

The contractor shall provide services necessary to plan and schedule travel and travel shall be reimbursed in accordance with Federal Acquisition Regulation (FAR) 31.205-

46. The contractor shall be reimbursed for actual allowable costs and not to exceed the amount allowed in the Joint Travel Regulations (JTR). No fee is allowable on travel costs. Two, three-day trips for one personnel are to be expected. The destination is TBD, but can be expected to be at one of IWR’s offices.

4. PERFORMANCE REQUIREMENTS (TASK AREAS)

4.1. Maintain existing environments for LPMS, NTNI, DIS and their subcomponents on required versions of software stack. The responsibility of administering USACE servers and networks will be handled by the USACE IT department (ACE-IT). These systems are currently housed on Solaris and/or Linux servers utilizing Oracle software, including but not limited to Oracle 11g/Oracle 12c, Apex 4/5, PL/SQL, and MOD_PLSQL. This task is intended to provide testing and solutions related to environmental changes required by USACE, and specifically ACE-IT (e.g. patches, network and firewall changes, Oracle database upgrades, etc.). An example system diagram has been provided in Appendix A.

4.2. Maintain the current applications, including frontend and backend, for DIS, LPMS, NTNI, and their subcomponents. Current applications are written in Apex and PL/SQL. An example data schema has been provided in Appendix B, and example data entry screens have been provided in Appendix C.

4.3. Implement changes to LPMS, NTNI, DIS and their subcomponents as approved by the Change Control Board, Corporate Change Board, or IWR leadership.

These changes generally fall into the categories of new fields, new reports, and new data extracts. Introduction of new data input methods (e.g. entry of a latitude and longitude via map click) may be required. Additional changes may include applications of social media for data outreach and communications, as well as crowd sourcing opportunities. Changes are requested on an as-needed basis.

4.4. Provide minor helpdesk services to assist IWR in feedback, diagnoses, and fixes for issues and errors as reported by users. The helpdesk will monitor group email boxes, where four to eight emails can be expected each day. Requests generally fall into three categories: 1) user account assistance, 2) user errors, and 3) feature requests. Feature requests are to be forwarded to IWR.

4.5. Participate in one hour IPRs, via teleconference, on a bi-weekly basis to review current work and prioritize tasks with the COR and TPOC.

4.6. Provide required documentation to comply with ACE-IT, Army, DoD, etc.

requirements.

4.7. Develop new training materials and user guides for the LPMS, DIS, and NTNI systems to better train new data entry personnel, and more easily lookup refresher information.

4.8. Optional Task 1 – Resident Management System (RMS) Integration Through TPOC and COR, provide database links and additional database structures needed to link between the DIS and RMS databases. Both systems capture similar dredging information, and in an effort to reduce data entry requirements, this task is intended to pull information from RMS into DIS where it will be stored in non-editable fields.

4.9. Optional Task 2 – Common Access Card (CAC) Enabling

All PL/SQL and APEX applications will be setup to utilize CAC authentication instead of a username and password. This solution needs to be seamless for users and must maintain current permissions granted to users. This task will require coordination with the IT contractors that manage the USACE database and application servers; this coordination with be managed by the COR and/or

TPOC.

5. GOVERNMENT FURNISHED PROPERTY (GFP)

Contractor will be supplied with government furnished laptops in order to connect to the USACE network. Contractor shall not use GFP for any work outside the scope of this PWS. The contractor is responsible for all GFP during the performance of this PWS and upon termination the contractor shall return all GFP to the Government.

6. SECURITY

The work will be UNCLASSIFIED. Network access is required, but facility access is not required except for participation in meetings. Contractor access supporting meetings at a government site shall be coordinated by the government technical point of contact (TPOC) or the contracting officer representative (COR). The contractor(s) will require a Common Access Card (CAC) or the contractor shall provide personnel who are capable of obtaining a CAC on the date of contract award and must immediately provide replacement employees, with the same capability. The COR is the liaison between the security office and the contractor.

Minimum Background Check. All contractors and subcontractors must have a valid and favorably adjudicated National Agencies Check Credit Check Law Enforcement Check (NACLC) before performing work on this contract. Periodic reinvestigations are not authorized under current policy.

AT Level I Training. All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: http://jko.jten.mil/courses/atl1/launch.html; or it ca be provided by the RA ATO in presentation form which will be documented via memorandum.

Access and General Protection/Security Policy and Procedures. All contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office.

Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

Common Access Card Requirements: The contractor and all sub-contractors employees will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an interim CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

Access for Contractors without a CAC: Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05 / AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative, as NCIC and TSDB are available), or, at

OCONUS locations, in accordance with status of forces agreements and other theater regulations.

Suspicious Activity Reporting Training (e.g. iWATCH, CorpsWatch, or See Something, Say Something). The contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the project manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.

Contractor Employees Who Require Access to Government Information Systems. All contractor employees with access to a government info system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the information systems and then annually thereafter in accordance with personnel security standards listed in AR 25‐2 (Information Assurance), an appropriate background investigation will be conducted prior to accessing the government information systems.

For Contracts that Require an OPSEC Standing Operating Procedure/Plan.

The Contractor shall develop an OPSEC SOP/Plan within 90 days of contract award. The OPSEC SOP/Plan must be reviewed and approved by the RA OPSEC Officer. The SOP/Plan will include the government's critical information, why it needs to be protected, where it is located, who is responsible for it and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator.

For Contracts that Require OPSEC Training. All new contractor employees will complete Level I OPSEC Training within 30 calendar days of their reporting for duty. Additionally, all contractor employees must complete annual OPSEC awareness training. The contractor shall submit certificates of completion for each affected contractor and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training. OPSEC awareness training is available at the following websites: https://www.iad.gov/ioss/ or http://www.cdse.edu/catalog/operations-security.html; or it can be provided by the RA OPSEC Officer in presentation form which will be documented via memorandum.

For Information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

Information Assurance Certifications: All contractor employees supporting IA/IT functions shall be appropriately certified upon contract IAW DoD 8570.01- M, DFARS 252.239- 7001 and AR 25-2. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

Will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas. All contract employees, including subcontractor employees who are not in possession of the appropriate security clearance or access privileges, will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas.

Pre-screen candidates using E-Verify Program. Proposed language: The Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award.

Personal Identity Verification of Contractor Personnel:

(a). The Contractor shall comply with agency personal identity verification procedures identified in the contract that implement Homeland Security Presidential Directive-12 (HSPD-12), Office of Management and Budget (OMB) guidance M-05-24 and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

(b) The Contractor shall account for all forms of Government-provided identification issued to the Contractor employees in connection with performance under this contract. The Contractor shall return such identification to the issuing agency at the earliest of any of the following, unless otherwise determined by the Government:

(1) When no longer needed for contract performance.

(2) Upon completion of the contractor employee's employment.

(3) Upon contract completion or termination.

(c) The Contracting Officer may delay final payment under a contract if the Contractor fails to comply with these requirements.

(d) The Contractor shall insert the substance of this clause, including this paragraph (d), in all subcontracts when the subcontractor's employees are required to have routine physical access to a Federally-controlled facility and/or routine access to a Federally- controlled information system. It shall be the responsibility of the prime Contractor to return such identification to the issuing agency in accordance with the terms set forth in paragraph (b) of this section, unless otherwise approved in writing by the Contracting Officer.

7. APPLICABLE DOCUMENTS

Enter any documents, regulations or policy that are applicable to the effort. If there are applicable documents or regulations that the contractor must adhere to; they have to be listed and in some cases provided to the contractor.

8. CONTRACTING OFFICER REPRESENTATIVE AND/OR TECHNICAL POINT OF

CONTACT (TPOC)

A contracting officer representative (COR) and/or technical point of contact (TPOC) will be appointed on each task order. The COR and TPOC have no authority to direct the contractor in any way to alter the contractual obligation. The contracting officer is the only individual authorized to make changes to the contract.

9. OTHER

The Contractor shall take no direction from any Government employee or any other person other than the Government Contracting Officer that changes the terms and conditions of this contract actions, the scope, or any change that impacts the cost, price or schedule. Changes authorized by the Contracting Officer will be in the form of a written, official, signed modification to the contract action received by the Contractor before the Contractor will act upon those changes. The Contractor will comply with

Changes clause of this contract when the Contractor believes direction has been given from persons other than the Government Contracting Officer that equate to a change by notifying the Contracting Officer as directed by the clause. Any direction given by any Government employee or any other person outside their authority must be reported to the Contracting Officer. Contracting Officer Representatives (CORs) are limited to the authorities stated in the COR appointment letters.

High Level LPMS System Diagram

The above representation is a very high level overview of the entirety of the LPMS system as it pertains to this contract:

1) Information is captured at USACE locks via data entered by personnel. This data is provided over radio or by using physical lockage slips. Lock personnel enter the data into LPMS data entry screens.

a. In some cases timing information is pre-filled for personnel by utilizing AIS timestamps and Oracle Spatial to determine when a vessel physically passes over virtual zones at each lock.

2) LPMS data is consumed by other entities within USACE for planning, budget, and other purposes.

3) LPMS data is also added to the Enterprise Data Warehouse (EDW) on a weekly basis. The EDW acts as a central repository for USACE data and is accessible to all those within the firewall possessing a Common Access Card (CAC).

4) LPMS data is also sent to the USACE DMZ every 15 minutes, where it is used to serve the public at http://corpslocks.usace.army.mil

Appendix A http://corpslocks.usace.army.mil/

PENDING_DATES (LPMS(5) (

OPS_ID

SIGNAL_DATE

DEPARTURE_DATE

PENDING_CUTS (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

VESSEL_NO

FLOTILLA_NO

BARGE_ID

NUMBER_BARGES

BARGE_TYPE

LINE_SEQ_NO

PROCESS_FLAG

P_BARGE_COMMODITIES (L

EROC

RIVER_CODE

LOCK_NO

VESSEL_NO

FLOTILLA_NO

BARGE_ID

COMM_CODE

NUMBER_BARGES

BARGE_TYPE

COMMODITY_TONS

LINE_SEQ_NO

PENDING_FLOTILLAS (LPMS(5)

EROC

RIVER_CODE

LOCK_NO

VESSEL_NO

FLOTILLA_NO

DIRECTION

ARRIVAL_DATE

FLOT_LENGTH

FLOT_WIDTH

FLOT_DRAFT_FT

FLOT_DRAFT_IN

STOP_CODE

HAZARD_CODE

NUM_LOADED_BRG

NUM_EMPTY_BRG

PENDING_BARGES (LPMS(5) (

EROC

RIVER_CODE

LOCK_NO

VESSEL_NO

FLOTILLA_NO

BARGE_ID

NUMBER_BARGES

BARGE_TYPE

BARGE_WIDTH

BARGE_LENGTH

LINE_SEQ_NO

INCLUDE_FLAG

PENDING_ARRIVALS (LPMS(5

EROC

RIVER_CODE

LOCK_NO

VESSEL_NO

DIRECTION

ARR_DATE

VESSEL_NAME

SEQ_NO

VESSEL_LENGTH

VESSEL_WIDTH

HAZARD_CODE

INCLUDE_FLAG

COMMODITIES (LPMS(5) (3))

COMM_CODE

COMM_DESC

EROC

HAZARD_INDICATOR

VESSELS (LPMS(5) (3))

VESSEL_NO

EROC

VESSEL_TYP

VESSEL_NAME

VSL_FOREIGN_FLAG

VESSEL_OWNER

VESSEL_HP

USER_STAMP

FLOTILLAS (LPMS(5) (3))

PVESSEL_NO

FLOTILLA_NO

EROC

FLOT_LENGTH

FLOT_WIDTH

FLOT_DRAFT_FT

FLOT_DRAFT_IN

STOP_CODE

HAZARD_CODE

NUM_LOADED_BRG

NUM_EMPTY_BRG

BARGE_COMMODITIES (LPM

PVESSEL_NO

FLOTILLA_NO

EROC

COMM_CODE

BARGE_ID

NUMBER_BARGES

BARGE_TYPE

COMMODITY_TONS

BARGES (LPMS(5) (3))

PVESSEL_NO

FLOTILLA_NO

EROC

BARGE_ID

NUMBER_BARGES

BARGE_TYPE

BARGE_WIDTH

BARGE_LENGTH

BARGE_TRAFFIC (LPMS(5)

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

OPS_ID

LOCKAGE_TYPE

VESSEL_NO

PVESSEL_NO

FLOTILLA_NO

BARGE_ID

NUMBER_BARGES

BARGE_TYPE

NUMBER_PROCESSE

LINE_SEQ_NO

ASSISTING_VSL (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

OPS_ID

LOCKAGE_TYPE

VESSEL_NO

ASST_VSL_NO

ASST_CODE

ASSISTANCE_TYPE (LPM

ASST_CODE

ASST_DESC

ASST_TYPE

TRAFFIC (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

OPS_ID

LOCKAGE_TYPE

VESSEL_NO

FLOTILLA_NO

SOL_DATE

ARRIVAL_DATE

END_OF_LOCKAGE

BOW_OVER_SILL

END_OF_ENTRY

START_OF_EXIT

NUM_CMRCL_PASSGRS

ASST_CODE

SIGNAL_DATE

DEPARTURE_DATE

LINE_SEQ_NO

OPERATIONS (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

OPS_ID

DIRECTION

MULTI_VESSEL

NUM_LIGHT_BOATS

NUM_REC_BOATS

STALL_STOPPAGE (LPMS(5) (

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

BEG_STOP_DATE

END_STOP_DATE

SCHEDULED

REASON_CODE

NUM_HW_CYCLES

CHAMBERMSTR (LPMS(5) (3

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

CHMBR_NAME

CHMBR_LENGTH

CHMBR_WIDTH

CHMBR_DRAFT

CHMBR_TYPE

PEOPLE_PERMISSIONS (LPMS

USER_ID

PROGRAM_NAME

PEOPLE_GROUPS (LPMS(5) (

USER_ID

GROUP_ID

PEOPLE (LPMS(5) (3))

USER_ID

USER_PW

USER_NAME

GROUP_ID

PHONE

EMAIL

NO_OF_LOGONS

GROUP_PERMISSIONS (LPMS(5) (3))

GROUP_ID

PROGRAM_NAME

GROUPS (LPMS(5) (3))

GROUP_ID

GROUP_NAME

EROC

LOCK_NO

RIVER_CODE

PARAMETER (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

CHMBR_NO

LOCKAGE_TYPE

APP_FLY_MIN

APP_EXH_MIN

APP_TRN_MIN

ENTRY_MIN

CHAMBER_MIN

EXT_FLY_MIN

EXT_EXH_MIN

EXT_TRN_MIN

APP_FLY_MAX

APP_EXH_MAX

APP_TRN_MAX

ENTRY_MAX

CHAMBER_MAX

EXT_FLY_MAX

EXT_EXH_MAX

EXT_TRN_MAX

STOP_FLAG

LOCKMSTR (LPMS(5) (3))

EROC

RIVER_CODE

LOCK_NO

LOCK_NAME

NUMBER_OF_CHMBRS

BEG_SHIFT1

BEG_SHIFT2

BEG_SHIFT3

TIMEZONE_STANDARD

TIMEZONE_DAYLIGHT

MAX_NO_PERS

MAX_WAIT

BRG_LOG

RIVER_MILE

DISTRICTS (LPMS(5) (3

EROC

DISTCODE

DISTNAME

DISTTYPE

RIVERMSTR (LPMS(5) (3

RIVER_CODE

RIVER_NAME

P A

R M

_D

IS

T_

FK

LO

C

K _D

IS

T_

FK

LO

C

K _R

IV

R

_F K

P A

R M

_R

IV

R _F

K

GROUPS_LM_FK

P G

P _G

R P

_F K

P E

O P

LE

_G

R O

U P

S _F

K

G P

_G R

O U

P S

_F K

P P

_P E

O P

LE

_F

K

P G

P _P

E E

_F K

C H

M B

R _L

O C

K _F

K

STALL_CHMBR_FK

OPS_CHMBR_FK

TR

A

FF

_O

P S

_F K

TRAFFIC_AT_FKAV_AT_FK

AV_TRAFFIC_FK

BT_TRAFFIC_FK

B A

R G

E _F

LO

TI

LL

A

_F K

BT_BARGES_FK

B C

_B A

R G

E S

_F K

FL

O

TI

LL

A _V

E S

S E

L_

FK

VSL_DIST_FK

TR

A

FF

IC

_V E

S S

E

LS

_F K

BRGCOM_COMM_FK

P A

R R

V _V

S

LS

_F K

PB_PF_FK

PBC_PB_FK

PBRGC_COMM_FK

Appendix B

Appendix C