Parking Access and Revenue Control System Sample Clauses

Parking Access and Revenue Control System. (PARCS) and sub-systems. The Contractor shall operate the PARCS at the Airport as part of the Operating Equipment. The Contractor will be responsible for the maintenance activities associated with the PARCS as defined by the Authority in Exhibit B-3. The Contractor will train its employees in the proper use of the Authority’s PARCS. The PARCS includes software and data contained therein that was developed at the Authority’s expense for use in the Contractor’s operations that is proprietary to the Authority. The Contractor shall not copy, assign, sell, or disclose the software or use the software for purposes that are not authorized by this Contract, except with the prior written approval of the Authority. At any time during the Contract Term, the Authority reserves the right to modify, and/or replace all or any part of the PARCS system at the Airport. Any such modification or replacement of the PARCS system by the Authority shall not alter or cancel the Contractor’s responsibility for the system’s operation and/or maintenance as provided herein unless otherwise provided in writing by the Authority. During the Contract Term the Authority may consolidate the system at Xxxxxx Xxxxxx Washington National and Washington Dulles International Airports to provide a single consolidated system remotely hosted through the Authority’s data center; the Contractor shall support the Authority’s implementation efforts as directed by the Authority, which may require the Contractor to manage and operate certain consolidated parking systems for both airports.
Sample 1
AutoNDA by SimpleDocs
Parking Access and Revenue Control System or PARCS shall mean the mechanical, electronic, and computerized equipment provided by the County from time to time, to control and record entrances and exits from the AEP, as well as other Airport parking facilities, which may include, but not be limited to, loop detectors, gate arms, ticket dispensers, cash registers, fee indicators, computerized data management systems card access systems, license plate inventory system ("LPI"), license plate recognition system ("LPR"), pay-on-foot terminals ("POF"), SunPass Plus System, parking reservation system, proximity card system, software and license, and any other administrative or management systems related to the PARCS.
Sample 1
Parking Access and Revenue Control System. Concessionaire shall be responsible to operate and maintain and ensure the accuracy and integrity of the Parking Access and Revenue Control System (Amano System) in its operation of the Public Parking Concession at the Airport. Concessionaire shall develop and implement a written preventive maintenance schedule and procedure to ensure the reliable and continuous performance of all equipment contained in such Parking Access and Revenue Control System. The schedule and procedures must be submitted to the SFRAA for written approval prior to the Effective Date of this Concession Agreement and whenever any modifications to the schedule or procedures are made. In addition, Concessionaire shall be responsible for all necessary repairs to the Parking Access and Revenue Control System. The SFRAA reserves the right to be present during such maintenance and repair procedures, and to perform periodic inspections to assure all Parking Access and Revenue Control System equipment is functioning properly and adequate safeguards appear to be in place. Concessionaire shall maintain a log of all such procedures including date, time, identity of equipment, and name of staff member or contractor who performed the procedure. Cashiers shall not be permitted to perform repair or maintenance to any portion of the Parking Access and Revenue Control System, including but not limited to cash registers, ticket dispensers, etc., unless otherwise approved in writing by the SFRAA.
Sample 1

Related to Parking Access and Revenue Control System

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

  • CONTROL SYSTEM (a) SELLER shall provide and maintain a quality control system to an industry recognized Quality Standard and in compliance with any other specific quality requirements identified in this Contract. (b) Records of all quality control inspection work by SELLER shall be kept complete and available to LOCKHEED XXXXXX and its customers.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Building Access The authorized representatives of the Union shall upon request have access to the District’s premises at any reasonable time for the purpose of adjusting grievances, investigating working conditions, or ascertaining that provisions of this Agreement are being adhered to; provided the representatives check in with the front office, following school protocol to receive a visitor’s badge, they do not interfere with employees in the performance of their duties. The Union shall furnish the District with the names of its authorized representatives.

  • Management and Control Systems Grantee will: 1. maintain an appropriate contract administration system to ensure that all terms, conditions, and specifications are met during the term of the contract through the completion of the closeout procedures. 2. develop, implement, and maintain financial management and control systems that meet or exceed the requirements of Uniform Statewide Accounting System (UGMS). Those requirements and procedures include, at a minimum, the following: i. Financial planning, including the development of budgets that adequately reflect all functions and resources necessary to carry out authorized activities and the adequate determination of costs; ii. Financial management systems that include accurate accounting records that are accessible and identify the source and application of funds provided under each Contract of this Contract, and original source documentation substantiating that costs are specifically and solely allocable to a Contract and its Contract and are traceable from the transaction to the general ledger; iii. Effective internal and budgetary controls; iv. Comparison of actual costs to budget; determination of reasonableness, allowableness, and allocability of costs; v. Timely and appropriate audits and resolution of any findings; vi. Billing and collection policies; and vii. Mechanism capable of billing and making reasonable efforts to collect from clients and third parties.

  • Emergency Operator Access Registry Operator shall provide bulk access to the zone files for the TLD to the Emergency Operators designated by ICANN on a continuous basis in the manner ICANN may reasonably specify from time to time.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!