System Configuration Diagram‌ Sample Clauses

System Configuration Diagram‌. System example
AutoNDA by SimpleDocs
System Configuration Diagram‌. LAN Hub COM ID: 06 CAN extension cable (max. 100 m) COM ID duplication not allowed (communication module) 2353 LAN MODULE • Set within the range 01 to 89. • Make sure that there are no duplicate COM ID settings. • Set within the range 01 to 63. • Make sure that there are no duplicate MODULE ID settings within the same CAN bus. • If the communication module is different, duplicate MODULE ID settings are allowed. *1 Communication module: Collective name for 2351 AIR MODULE, 2352 WIRE MODULE, 2353 LAN MODULE *2 Measurement module : Collective name for 2301 HUMIDITY MODULE to 2305 INSTRUMENTATION MODULE, 2331 POW- ER METER MODULE, 2332 POWER METER MOD- ULE, 2341 INPUT MODULE, 2342 OUTPUT MODULE, 2343 RS LINK MODULE • Make the ID setting with the rotary switches on the rear of the module. • When the POWER LED of a module flashes in red, MODULE ID duplication has been detected within the CAN bus. Change the settings so that all MODULE IDs in the same CAN bus are unique. Operation (Basics) 3‌

Related to System Configuration Diagram‌

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • AIRCRAFT CONFIGURATION The guarantees defined below (the “Guarantees”) are applicable to the A319-100 Aircraft as described in the Standard Specification Ref. J 000 01000 Issue 6 dated 1st March 2007 equipped with:

  • 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. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass xxxxxx. In addition to runoff conveyance, the grass xxxxxx also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off-site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12-inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1- 2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after [Municipality Name] accepts verification of construction from the project engineer.

  • 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.

  • Service Description 2.1 General

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