Infrastructure logic Sample Clauses

Infrastructure logic. The logic of the Infrastructure, i.e. the way resources should interact to support special community applications, will be modified to support the notions of: • Regions: set of resources defining the interaction boundaries of such resources. A resource is activated in the context of a region and can only interact with the resources in the same region at that moment in time. For example, an UI belongs to one region; a query execution can only be demanded to the Search Services available in the same region of the User Interface at search-time. • Groups: set of resources bound together by particular application-oriented properties. Groups do not define any interaction boundaries between the resources they contain; a group is used to support actions on sets of resources. For example, an Index Service should be designed to run a query on a group of Index DSs, rather than on an explicit list of such DSs. The overall organization of the system can be notably simplified by this simple and natural notion. • API contracts: a Service implements an API whose contract establishes its method’s signatures and semantics. WSDL and Java Stub of the Services are available from the support site. • Sub-Services: Services implementing only a part of an API contract. The existence of sub-Services must be declared as an explicit dependency in the IS. Examples are: the embedded ResultSet of the ICM Index obeys only to a sub-part of the ResultSet Service contract, that of ResultSet access. As such, is a sub-ResultSet. • Moving from Repository Services to Repository Data Structures. Indeed, Repositories are not DRIVER Services, but rather Data Structures to be managed by a special Service, called Repository Management Service. The Service operates as a generic OAI-PMH Repository harvester, returning result sets of the harvesting results. It therefore operates independently of the Aggregation Service, which will deal with input/output ResultSets, and can be reused for other purposes by other Services.
Sample 1
AutoNDA by SimpleDocs

Related to Infrastructure logic

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Acquisition Services (i) Serve as the Company’s investment and financial advisor and provide relevant market research and economic and statistical data in connection with the Company’s assets and investment objectives and policies; (ii) Subject to Section 4 hereof and the investment objectives and policies of the Company: (a) locate, analyze and select potential investments; (b) structure and negotiate the terms and conditions of transactions pursuant to which investments in Properties, Loans and other Permitted Investments will be made; (c) acquire, originate and dispose of Properties, Loans and other Permitted Investments on behalf of the Company; (d) arrange for financing and refinancing and make other changes in the asset or capital structure of investments in Properties, Loans and other Permitted Investments; and (e) enter into leases, service contracts and other agreements for Properties, Loans and other Permitted Investments; (iii) Perform due diligence on prospective investments and create due diligence reports summarizing the results of such work; (iv) Prepare reports regarding prospective investments that include recommendations and supporting documentation necessary for the Directors to evaluate the proposed investments; (v) Obtain reports (which may be prepared by the Advisor or its Affiliates), where appropriate, concerning the value of contemplated investments of the Company; (vi) Deliver to or maintain on behalf of the Company copies of all appraisals obtained in connection with the Company’s investments; and (vii) Negotiate and execute approved investments and other transactions, including prepayments, maturities, workouts and other settlements of Loans and other Permitted Investments.

  • Critical Infrastructure Subcontracts For purposes of this Paragraph, the designated countries are China, Iran, North Korea, Russia, and any countries lawfully designated by the Governor as a threat to critical infrastructure. Pursuant to Section 113.002 of the Business and Commerce Code, Contractor shall not enter into a subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business and Commerce Code, in this state, other than access specifically allowed for product warranty and support purposes to any subcontractor unless (i) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is majority owned or controlled by citizens or governmental entities of a designated country; and (ii) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is headquartered in a designated country. Contractor will notify the System Agency before entering into any subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business & Commerce Code, in this state.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Information Systems The Customer is aware that vehicles manufactured, supplied or marketed by a company within the Volvo Group are equipped with one or more systems which may gather and store information about the vehicle (the “Information Systems”), including but not limited to information relating to vehicle condition and performance and information relating to the operation of the vehicle (together, the “Vehicle Data”). The Customer agrees not to interfere with the operation of the Information System in any way.

  • Mobility The ability to move indoors from room to room on level surfaces at the normal place of residence.

  • Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

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