External interfaces Sample Clauses

External interfaces. The physical layer external interfaces of the Internet FWA system are: o Analogue line interface at the RSS o Packet data interface at the RSS
AutoNDA by SimpleDocs
External interfaces. 4.7.1 [****]
External interfaces. The PATHS system architecture is self-contained in that it does not have any external extension points beyond the capability of the application layer to communicate with the end- user applications in the client layer via web services. The interfaces between the different system architecture layers are: • Communication Between data layer and application layer o JDBC over TCP/IP o ODBC over TCP/IP o SMB over TCP/IP o SPARQL/HTTP over TCP/IP • Between the application layer and the client layer o RESTful XML and JSON Web Services Figure 5.4-1 PATHS SOA (external) interfaces UML class diagram 6 SUBSYSTEM SPECIFICATIONS While chapter 5 above is concerned with providing a logical overview of the system, this chapter provides detailed technical specifications of the modules of each of the sub-systems of the PATHS SOA application layer. The sub-systems of the data layer are described in chapter 7 below.
External interfaces. 6.9.1.1.7. Details of the subsystem functions
External interfaces. | How will connections to third party applications be upheld? Where the App provides options to integrate third-party applications, as may be further described in the Documentation, (an “Interface”), HRForecast will maintain the core functionality of such Interface, throughout Subscription Term or replace it by a successor interface providing similar functionality. Where the Interface connects to a specific interface as counterpart, this relates to that specific counterpart only and, for the avoidance of doubt, HRForecast is not responsible for any third party’s interface, API or other means to integrate and the effect thereof on interoperability.
External interfaces 

Related to External 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)

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

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

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • PORTAL At the Closing Time, the Securities shall have been designated for trading on PORTAL.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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