We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

System Attributes Sample Clauses

System Attributes. Except as may be provided in the Special Terms and Conditions hereto, System Owner shall at all times during the Term of this Agreement own and retain exclusive rights· to any and all Capacity, Ancillary Services, Tax Benefits, Environmental Credits and all other products or economic benefits of the System.
System Attributes. A System Attribute is a specific attribute related to GPS metadata. If you add one or more of these types of attributes to your feature, the attributes will be logged automatically using the data available from your GPS receiver, and cannot be edited by the field user. Examples of system attributes include PDOP, # of Satellites Used, etc. When logging multiple points for a feature in progress, you are only prompted for the feature and attributes for the first point. All future points for that feature are automatically associated with the original feature and attributes selected. As mentioned earlier, if no feature file is selected for a project, the project is automatically given a generic point, a generic line, and a generic area to choose from when logging points. Each of these features has one alphanumeric attribute associated with it titled Comment, which has a limit of 40 characters.
System Attributes. The LGC Wireless designed Xxxx 0, 0, xxx 0 XXXX, utilizing multiple LGCells, has the following system attributes: · Lower Cabling Cost — The LGCell’s ability to use existing multi-mode fiber for installation or expansion (when it is available) can greatly reduce the overall cost of implementation. · Faster Deployment—In the typical LGCell implementation, the only cable infrastructure work is the installation of CAT 5 runs for each, antenna. Since this work can be performed by any LAN (TIA 568A) certified cabling contractor, turn around time and complexity is significantly reduced when compared with installing a coax or single mode fiber cable plant. In addition, no AC power is required at the XXX (antenna), greatly simplifying RF design, antenna placement and installation. Cable length independent design means that antenna placement locations can be chosen without having to calculate cable loss and balance the system. · Centralized Equipment — An LGCell has a nominal “wingspan” of 2 kilometers. This large reach of the LGCell system allows all the main hubs to be co-located with other communications equipment in a central location. Since the LGCell is using the same TIA 568A standards as LANs, the Expansion Hubs can typically be co-located with data hubs and routers in existing dispersed equipment closets. The ability to centralize many of the components and co-locate with data equipment means easier planning, simplified maintenance and greater equipment security. Only the LGCell Bubs, located in the equipment rooms, need AC power. The XXX’x are powered by the CAT 5 and are easily and inexpensively installed and moved (if necessary). · Double Star Topology — The first star in an LGCell design is the MMF cabling from the Main Hubs to the Expansion Hubs. The second star is the CAT 5 from the Expansion Hubs to the XXX’x. A single MMF pair will support 4 antennas, reducing the fiber runs required between buildings. When LGCell Hubs are co-located with LAN equipment, the fiber runs originate and terminate in the same locations as the LAN and that fiber can be utilized without jumpering (or running new fiber). Lastly, the use of Expansion Hubs as an XXX power source means that the antenna locations do not need to be wired for AC power. · Add Capacity Easily — Once an LGCell is in place, it is relatively simple to add more capacity as demand increases. First, capacity can be increased by adding additional carriers. If demand requires even more capacity, it is easy...
System Attributes. You understand and agree that, subject to the requirements of the Program and applicable law, all credits (including tax credits, emission reduction credits, renewable energy credits, and carbon offset credits, but excluding any Bill Credits allocated to You), benefits, incentives, attributes, and rebates, howsoever entitled, derived, or attributable from or to the System, whether existing now or in the future (the “System Attributes”), are the property of and for the benefit of SPC (or its designee), usable and transferable at its sole discretion. You agree to reasonably cooperate with SPC (or its designee) so that it may claim the System Attributes. You agree to assign and transfer to SPC (or its designee) any and all System Attributes in which You acquire an ownership interest. You agree to refrain from entering into any agreement that would entitle You or a third party toclaim the System Attributes.
System Attributes. The ECSwin program described below is used primarily for configuring and setting parameters for type U16xx summators (U1600, U1601, U1602, U1603 and U161x) within an Energy Control System (ECS LAN). Beyond this, the program is capable of acquiring energy consumption data, and visualizing them in the form of measurement value tables and graphic representations. The 32 bit programs can be used with all 32 or 64 bit versions of the Microsoft Windows operating system (Windows 95/98/ME, Windows NT/20xx/XP/Vista/7/8). Data exchange with the summators within the ECS LAN is not accomplished directly, but rather by means of a special server program which saves data from the clients to intermediate storage, maintains communication with the ECS LAN via a serial RS 232 interface (including protocol, checksum etc.) and finally forwards response data to the client. In light of this, ECSwin must be viewed as a client program. The server program can be installed to a different network PC than the client program if desired, although this is not necessary. The TCP/IP network protocol is used for communication between the server and the client. ECSDIENST.EXE or FELANIP.EXE can be used as a server program. A dedicated COM server (e.g. from W & T, which however usually only permits one client connection) can be used instead of a server program. Figure 1 provides a basic overview of the system’s expansion options.
System AttributesSubject to § 3.2, Seller shall be entitled to receive the SGIP Deposit and all System Attributes, including SGIP Incentives, with respect to the System, consistent with Exhibit C and Exhibit D.

Related to System Attributes

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

  • 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

  • Outputs Analogue and digital outputs of protected content are allowed if they meet the requirements in this section and if they are not forbidden elsewhere in this Agreement..

  • Switching System Hierarchy and Trunking Requirements For purposes of routing PNG traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to PNG, the subtending arrangements between PNG Tandem Switches and PNG End Office Switches shall be the same as the Tandem/End Office subtending arrangements that PNG maintains for the routing of its own or other carriers’ traffic.

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

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Disconnection Upon termination of this Agreement, Developer and Connecting Transmission Owner will take all appropriate steps to disconnect the Developer’s Large Generating Facility from the New York State Transmission System. All costs required to effectuate such disconnection shall be borne by the terminating Party, unless such termination resulted from the non-terminating Party’s Default of this Agreement or such non-terminating Party otherwise is responsible for these costs under this Agreement.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the ISO OATT.

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation 35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases 6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.