System Assumptions Sample Clauses

System Assumptions. Most debatable assumption in our system model is reliable communication. In fact, many cryptographic protocols for peer-to-peer ad hoc networks, most notably, group key agreement protocols [3, 4, 21], also make this assumption. This can be justified by relying on reliable group communication services, such as [18, 19]. Another assumption is the ability of the parties to digitally sign their messages. This requires a public-key infrastructure, such as described, e.g., in [14]. For an overview of authentication mechanisms in ad hoc networks, including issues related to the public key infrastructure, see [1].
AutoNDA by SimpleDocs

Related to System Assumptions

  • Project Assumptions The following assumptions are specific to this project:

  • Self-Assumption Any self-insured retention, deductibles and exclusions in coverage in the policies required under this Article shall be assumed by, for the account of and at the sole risk of Seller or the subcontractor which provides the insurance and to the extent applicable shall be paid by such Seller or subcontractor. In no event shall the liability of Seller or any subcontractor thereof be limited to the extent of any of the minimum limits of insurance required herein.

  • Installation and Acceptance 4.1 Unless otherwise agreed in the Proposal, SDSD shall install the Product and other Licensed Materials on the Equipment.

  • Testing and Acceptance Designer will exercise commercially reasonable efforts to test Deliverables requiring testing and to make all necessary corrections prior to providing Deliverables to Client. Client, within five (5) business days of receipt of each Deliverable, shall notify Designer, in writing, of any failure of such Deliverable to comply with the specifications set forth in the Proposal, or of any other objections, corrections, changes or amendments Client wishes made to such Deliverable. Any such written notice shall be sufficient to identify with clarity any objection, correction or change or amendment, and Designer will undertake to make the same in a commercially timely manner. Any and all objections, corrections, changes or amendments shall be subject to the terms and conditions of this Agreement. In the absence of such notice from Client, the Deliverable shall be deemed accepted.

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

  • Records Maintenance and Access Grantee must maintain all financial records relating to this Grant in accordance with generally accepted accounting principles. In addition, Grantee must maintain any other records, whether in paper, electronic or other form, pertinent to this Grant in such a manner as to clearly document Grantee’s performance. All financial records and other records, whether in paper, electronic or other form, that are pertinent to this Grant, are collectively referred to as “Records.” Grantee acknowledges and agrees Agency and the Oregon Secretary of State's Office and the federal government and their duly authorized representatives will have access to all Records to perform examinations and audits and make excerpts and transcripts. Grantee must retain and keep accessible all Records for a minimum of six (6) years, or such longer period as may be required by applicable law, following termination of this Grant, or until the conclusion of any audit, controversy or litigation arising out of or related to this Grant, whichever date is later.

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

  • Additional Facilities If the CAISO determines that it requires Operational Control over additional transmission lines and associated facilities not then constituting part of the CAISO Controlled Grid in order to fulfill its responsibilities in relation to the CAISO Controlled Grid then the CAISO shall apply to FERC pursuant to Section 203 of the Federal Power Act, and shall make all other regulatory filings necessary to obtain approval for such change of control and shall serve a copy of all such applications on the affected Participating TO and the owner of such lines and facilities (if other than the Participating TO). In the event that a Party invokes the dispute resolution provisions identified in Section 15 with respect to the transfer of Operational Control over a facility, such facility shall not be transferred while the dispute resolution process is pending except pursuant to Section 4.5.2.

  • No Assumption No approvals or acceptances by, or on behalf of, TFC shall be deemed to be an assumption of any responsibility by TFC for any defect, error or omission in said Deliverables or Professional Services.

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