Integration Interfaces Clause Samples

Integration Interfaces. Licensee must develop, use and maintain all Integration Interfaces in compliance with applicable specifications and compatible with the most current version of the ▇▇▇▇▇▇ ▇▇▇ application. Licensee shall not transfer data via an Integration Interface if the Integration Interface is out of compliance for more than 120 days. Licensee must make available to ▇▇▇▇▇▇ Mae qualified personnel to promptly respond to technical questions pertaining to its Integration Interfaces.
View SourceView Similar (34)
Integration Interfaces. Different modules of the On-Time Architecture will communicate using standard inter- faces. For sake of clarity, we will represent these interfaces as standard UML interfac- es definitions but, in most of the cases, they have to be interpreted as web Services interfaces of distributed systems. Since the rise of Web 2.0 technologies, the difference between static and distributed interfaces are becoming more and more subtle, some languages doesn’t make any dif- ▇▇▇▇▇▇▇ between the two, since communication frameworks and high-level program- ming languages can abstract the communication layer from the functional specifica- tions. Since the architecture is conceived to be modular and flexible, remote interfaces can become native and vice-versa, the architecture definition poses no limit on how the modules can be coupled. Functionally, the On-Time architecture adhere to a minimalist design pattern. Even though there are several guidelines that the modules must comply to, they are very simple building blocks that can be used in different ways to achieve the desired re- sults. In addition, the technology used allows for cross-language, cross-OS and cross- technologies integration without too much effort. The architecture will distinguish modules. Modules have been conveniently named against the WP name of the project. A single WP can have multiple modules and dif- ferent implementations (for example different WP4 Modules can exists, with different kind of optimization and planning algorithm). It is responsibility of the architecture to keep communications between the modules and forward data and messages to the correct endpoints. Basically, a module must carry on these functions:  Be able to subscribe for events.  Be able to publish events.  Be able to access the Static and Operational Data Provider of the architecture. These three functional characteristics are the basics at which a module must adhere to be able to carry out its functions. To be able to receive events, a module need to implement the EventConsumer Inter- face. The EventConsumer Interface it is the basic requirement to process messages and it is shared both by modules than by the architecture (since also the architecture must be able to receive messages from modules). To access Operational and Static Data a module must know the location of a Data Pro- vider Service. This service is an abstraction between different systems that stores and manages data for railway systems, called Train Control Sys...
View Source

Related to Integration 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.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Integration The Company shall not sell, offer for sale or solicit offers to buy or otherwise negotiate in respect of any security (as defined in Section 2 of the Securities Act) that would be integrated with the offer or sale of the Securities for purposes of the rules and regulations of any Trading Market such that it would require shareholder approval prior to the closing of such other transaction unless shareholder approval is obtained before the closing of such subsequent transaction.