Standard Interfaces Sample Clauses

The "Standard Interfaces" clause defines the requirement for parties to use established, widely-accepted technical or operational interfaces when interacting with each other's systems or services. In practice, this means that any data exchange, communication, or integration must conform to industry standards, such as specific APIs, data formats, or communication protocols. By mandating the use of standard interfaces, the clause ensures compatibility, reduces the risk of integration errors, and streamlines collaboration between parties, ultimately minimizing technical disputes and facilitating smoother operations.
Standard Interfaces. ‌ 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.
View SourceView Similar (10)
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...
View Source
Standard Interfaces 
View SourceView Similar (2)

Related to Standard Interfaces

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central ▇▇▇▇▇▇ Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the customer’s premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two (2) independent ▇▇▇▇▇▇▇▇ or divisions that separate the service provider’s network from the customer’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the customer each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 2.7.2 BellSouth shall permit NewPhone to connect NewPhone’s Loop facilities to the customer’s premises wiring through the BellSouth NID or at any other technically feasible point.