Basic System Trouble-Shooting Sample Clauses

Basic System Trouble-Shooting. The Contractor shall provide theoretical and practical instruction on basic trouble shooting procedures for the following systems: • Diesel Engines (Electricians/Power Plant Managers/QA) • Fuel Oil Systems (Power Plant Operators/QA) • Engine Intake and Exhaust Systems (Electricians/Power Plant Managers/QA) • Domestic Water Systems (WTP Managers/Plumbers/QA) • Refrigeration and Air Conditioning Systems Over 5 Tons (HVAC Technicians/QA) • Refrigeration Systems (HVAC Technicians/QA) o Principles of Refrigeration o Oil in Refrigeration Systems o Contaminants in Refrigeration o Desiccants and Driers o Foods and Their Preservation o Cabinet Construction and Repairs o Piping o Insulation o Refrigerants o Use of Refrigerant Charts o Refrigerant Cylinders o Vacuum Pumps o Moisture in Air o Electricity o Wiring Diagrams o System Components  Compressors  Condensers  Evaporators  Refrigerant Flow Controls o Motors o Controls Electric o Air Filters o Heat Pump Systems o Chillers o Brazing o Tubing and Fittings/Flaring o Seasonal Maintenance Checklists o Retubing Refrigeration Heat Exchangers o Refrigerant o Safety Relief Devices • Sanitary Waste Systems (Plumbers/WWTP Managers/QA) • Generators (Electricians/Power Plant Managers/QA) • Primary Electrical Distribution (Electricians/Power Plant Managers/QA) • Secondary Electrical Distribution (Electricians/Power Plant Managers/QA) • Motor Generators (Electricians/Power Plant Managers/QA) • Fire Protection (Electricians) C-4.14.7 Use of Proper Tools and Materials, to Include Personal Protective Equipment (PPE) The Contractor shall emphasize the proper use of tools, materials, and equipment throughout the duration of the course and ensure students conducting practical exercises wear required level of PPE. C-4.14.8 Service Contract Management – COR/QA Technician Focused Based on the Afghan Procurement Law and GIRoA Procurement Processes and Procedures The Contractor shall develop a two-week block of training designed to instruct Plant Managers and Quality Assurance Technicians on the following task/topics: • Afghan Procurement Law • GIRoA Specific Procurement Processes and Procedures • GIRoA Service Contract Boiler Plate • Developing a Statement of Requirements for GIRoA Service Contracts • Developing an Independent Government Estimate for GIRoA Service Contracts • Developing a Statement of Work for GIRoA Service Contracts • Developing a Quality Assurance Surveillance Plan for GIRoA Service Contracts • Duties, functions, ...
AutoNDA by SimpleDocs

Related to Basic System Trouble-Shooting

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Troubleshooting Please contact our tech support 24/7 for service issues at 0 (000) 000-0000 relating to internet and telephone.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Staging In addition to the staging categories listed in paragraph 1 of Annex 2-A, this Schedule contains staging categories 20-A, 20-B, PR-1 and PR-130:

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

Time is Money Join Law Insider Premium to draft better contracts faster.