Standard Interfaces Sample Clauses

Standard Interfaces. ‌ These are interfaces provided by asynManager or interfaces implemented by all or most port drivers. The interfaces are: asynManager provides services for communicating with a device connected to a port. asynCommon is an interface that must be implemented by all low level drivers. The methods are: • report - Report status of port. • connect - Connect to the port or device. • disconnect - Disconnect from the port or device. asynTrace is an interface for generating diagnostic messages. asynLockPortNotify is an interface that is implemented by a driver which is an asynUser of another driver. An example is a serial bus driver that uses standard serial support. asynManager calls asynLockPortNotify whenever it locks or unlocks the port. asynDrvUser is an interface for communicating information from device support to a driver without the device support knowing any details about what is passed.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Standard Interfaces. Standard interfaces are classified as integrations to third-party systems that are common in the public safety technology industry AND have been previously developed by Contractor. Facilitating standard interfaces, a SOMA integration specialist will conduct review sessions, during the discovery phase of the project, of the OSD to ensure the understanding of operational, scenario-based use cases of the integration. A high level scope for each interface is described below and will be the basis for the scope of detailed functionality objectives. Any modifications to the OSD post approval are subject to the change management process. The discovery process may be performed at different times for each integration throughout the lifecycle of the project as determined by the project implementation teams. Standard interface OSDs are not County specific documents, and are not subject to edits, changes, etc. County specific configuration for standard interfaces are documented as part of the OSD and must be approved by the County, the County’s third-party provider and Contractor. Standard interfaces are developed, maintained and enhanced within the SOMA Platform product version process. Changes to standard interfaces will require adherence to the development lifecycle therein. Each interface is evaluated during the discovery phase of the project to determine the viability of the desired integration. In some cases, it may be determined that integration to a third-party application is not achievable due to circumstances outside of Contractor’s control, or it may be determined by the stakeholders that the integration is no longer desired. In such an event, the interface will be removed as a deliverable of the Project. Unless explicitly stated within this SOW, the discovery phase will be used to determine which Application Programming Language (API) is best suited for the integration, the third-party’s or Contractor’s. During evaluation, the SOMA integration specialist may determine the best option for integrating to the SOMA Platform is by use of the SOMA, standards-based, RESTful Web API or a real-time WebSocket API to be utilized by the third-party provider to integrate their application to the SOMA Platform. In such an event, the SOMA integration specialist will assist the third-party provider in their integration with the SOMA Platform. Review sessions must include all stakeholders to include the County’s operations subject matter expert, the County’s technology expe...
Sample 1
Standard Interfaces 
Sample 1Sample 2

Related to Standard Interfaces

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Maintenance Services Subject to Client’s timely payment of the applicable maintenance fees, Accenture will make available the following maintenance services (“Maintenance Services”):

  • Data Access Services State Street agrees to make available to the Fund the Data Access Services subject to the terms and conditions of this Addendum and such data access operating standards and procedures as may be issued by State Street from time to time. The Fund shall be able to access the System to (i) originate electronic instructions to State Street in order to (a) effect the transfer or movement of cash or securities held under custody by State Street or (b) transmit accounting or other information (the transactions described in (i)(a) and (i)(b) above are referred to herein as “Client Originated Electronic Financial Instructions”), and (ii) access data for the purpose of reporting and analysis, which shall all be deemed to be Data Access Services for purposes of this Addendum.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.

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

  • Maintenance and Support Services As long as you are not using the Help Desk as a substitute for our training services on the Tyler Software, and you timely pay your maintenance and support fees, we will, consistent with our then-current Support Call Process:

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

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