Platform Architecture Sample Clauses

Platform Architecture. The Jive Cloud platform architecture is unique to the market and based on a distributed (not centrally hosted) model. It offers our customers a single, transparent experience that is at the same time limitlessly scalable, natively redundant, and extremely fault tolerant. Jive Cloud is the engine behind Jive’s industry-leading uptime, world-class customer satisfaction, and unmatched call quality and user experience. DATACENTERS Jive Cloud is a cloud-based platform, operating from several dispersed, worldwide datacenter locations. Jive chooses datacenter facilities that are essential to the markets we serve, enabling us to provide highly available service and resilient network access to any geographic market. Jive’s global datacenter footprint includes tier one centers in: Los Angeles, CA, New York, NY, Dallas, TX, Chicago, IL, and the United Kingdom. Jive has sufficient coverage diversity to ensure our customers have enough redundant access points to deliver consistent service and high availability. Jive only partners with tier one datacenters, which have shown a commitment to a professional standard of conduct, integrity, and ethical values. All Jive selected datacenters have successfully completed AT-101 SOC II security audits. These audits stringently evaluate datacenter management, security, and controls over infrastructure and information, as well as the the people, procedures, and systems which operate and support them. All datacenter facilities perform proactive maintenance on all critical security systems, and include fully redundant UPS, backup generators, and cooling systems. Each datacenter also includes scalable bandwidth options, business continuity solutions, managed firewalls, remote hands, load balancing and a variety of security related services. HARDWARE Jive’s computing platform is built on x86-based hardware, ensuring easy access to additional components as necessary. Computing resources are virtualized and clustered to create a true cloud computing environment. Top-quality network equipment (e.g., Cisco, Brocade, and Juniper) provide highly available access to all computing resources. CALL INFRASTRUCTURE The call infrastructure component of Jive Cloud is where call processing, routing, and endpoint registration take place. Different subcomponents are responsible for managing PSTN integration, delivering specific call functionality, and managing the actual media streams and handsets involved in making internal and external calls. Call rout...
Sample 1Sample 2
AutoNDA by SimpleDocs
Platform Architecture. 5 2.1. High Availability .................................................. 5 2.2. Scalability ........................................................ 6 2.3. Access Control ..................................................... 6 2.4. Interface Support .................................................. 6 2.5. Protocols .......................................................... 6 2.6. Latency Performance ................................................ 6 2.7. Server support ..................................................... 6
Sample 1Sample 2
Platform Architecture. 2.1. HIGH AVAILABILITY The ASN-GW should have the following HA features: - System should be designed to provide carrier class with 99.999% availability - No Single Point of failure. - Hitless software upgrades. - Hitless failover for non-stop forwarding. - ASN-GW should have messaging if a connection limit has been reached to communicate to the BS to contact another ASN-GW.
Sample 1Sample 2
Platform Architecture. This category covers the general requirements for the entire PLATOON platform reference architecture that defines its scope and characteristics: for instance, PLATOON architecture must avoid vendor lock-in providing a technologically agnostic environment leveraging open source components and public standard. The PLATOON reference architecture will be also compliant with other public initiative as the COSMAG reference architecture (3), FIWARE (2), SGAM (4) and IDS (1). In particular IDS reference architecture ensures data sovereignty, security and privacy when sharing data/tools among platform users. In order to be compatible with IDS, PLATOON reference architecture must be able to integrate the main mandatory components of IDS reference architecture, i.e. the connector and the identity provider (a.k.a DAPS). The PLATOON reference architecture must allow some of the components of the reference architecture to be hosted at the component level (e.g. edge computing), on premise and in the cloud. Finally, the PLATOON reference architecture must enable the exploitation of digital services (both data and data analytics tools) through a Marketplace.
Sample 1
Platform Architecture. This section provides a component-level overview as an introduction for the component-level interfaces and sub-components presented in Section 3 and 4, respectively. It also outlines the relationships in the overall platform and the scopes of orchestration of resources and services that exist in the overall system.
Sample 1
Platform Architecture. 6.1 OVERVIEW Figure 14 shows the FLAME platform architecture, operating on top of an infrastructure such as the one provided in our deployments in Bristol and Barcelona. In this figure, we focus on the main layers of the overall architecture, including the FLAME platform, while showing crucial inter-layer interfaces for explanation of the overall workings. Detailed descriptions on the internal functions of the various layers are deferred here to Section 6.6. At the very bottom, we assume the existence of the infrastructure (provider), exposing an ETSI MANO compliant interface [NFV] to the FLAME platform for resource management at the wholesale level, i.e. the FLAME platform is reserving platform resources in the compute, storage and networking domain. We assume such infrastructure resource exposure to follow our observed emerging infrastructure view, as discussed in Section 2.3, with the ability to reserve resources for the FLAME platform as part of a longer-lived relationship between FLAME platform provider and infrastructure provider, realized with an infrastructure slice. Figure 14: FLAME Platform Architecture Resources of the infrastructure provided to the FLAME platform are in turn provided as retail resources to the media services at the top of the platform through management interfaces exposed to media services. In other words, the FLAME platform orchestrates the deployment of media components as well as internal service functions. In addition, a monitoring interface allows for information exchange between media services and FLAME platform, which in turn will drive the decisions taken for the management input via the former interface. This combination of management and monitoring interfaces effectively provide the experiment API towards media services, allowing for defining and placing the compute, storage and network resources for the specific tests in the experiment. The experiment API is complemented at the data plane through standard HTTP/IP data plane interfaces of the existing Internet through which media services realize their functionality. The management interfaces allow for initiating the orchestration of (retail) resources from the media service provider side. We see these interfaces and therefore the dialogue between media services and the FLAME platform evolving over time. In an initial realization, we see media services heavily relying on the ETSI MANO compliant interface, providing details on compute, storage and network resources bei...
Sample 1
Platform Architecture. 6.1 OVERVIEW Figure 14 shows the FLAME platform architecture, operating on top of an infrastructure such as the one provided in our deployments in Bristol and Barcelona. In this figure, we focus on the main layers of the overall architecture, including the FLAME platform, while showing crucial inter-layer interfaces for explanation of the overall workings. Detailed descriptions on the internal functions of the various layers are deferred here to Section 6.6. At the very bottom, we assume the existence of the infrastructure (provider), exposing an ETSI MANO compliant interface [NFV] to the FLAME platform for resource management at the wholesale level, i.e. the FLAME platform is reserving platform resources in the compute, storage and networking domain. We assume such infrastructure resource exposure to follow our observed emerging infrastructure view, as discussed in Section 2.3, with the ability to reserve resources for the FLAME platform as part of a longer-lived relationship between FLAME platform provider and infrastructure provider, realized with an infrastructure slice.
Sample 1
AutoNDA by SimpleDocs
Platform Architecture. The City has a multi-cloud strategy. The City prefers the Solution is hosted outside of the City’s data centers and maintained by the Contractor. The hosting facilities must meet the requirements provided in Exhibit F-1 Information Technology and Security Requirements.
Sample 1
Platform Architecture 
Sample 1Sample 2Sample 3

Related to Platform Architecture

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

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

  • Design At no cost to SCE, Seller shall be responsible for:

  • Platform (i) Each Loan Party agrees that the Administrative Agent may, but shall not be obligated to, make the Communications (as defined below) available to the Lenders by posting the Communications on Debt Domain, Intralinks, Syndtrak or a substantially similar electronic transmission system (the “Platform”).

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

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

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

  • Hosting 46.7.4.1 At CLEC’s request, SBC-SWBT and SBC-AMERITECH shall perform hosting responsibilities for the provision of billable message data and/or access usage data received from CLEC for distribution to the appropriate billing and/or processing location or for delivery to CLEC of such data via SBC-SWBT’s and SBC-AMERITECH’s internal network or the nationwide CMDS network pursuant to the applicable Appendix HOST, which is/are attached hereto and incorporated herein by reference.

  • Engineering Forest Service completed survey and design for Specified Roads prior to timber sale advertisement, unless otherwise shown in A8 or Purchaser survey and design are specified in A7. On those roads for which Forest Service completes the design during the contract, the design quantities shall be used as the basis for revising estimated costs stated in the Schedule of Items and adjusting Timber Sale Account. Forest Service engineering shall be completed according to the schedule in A8. Should Forest Service be unable to perform the designated survey and design by the completion date or other agreed to time, upon written agreement, Purchaser shall assume responsibility for such work. In such event, Contracting Officer shall revise:

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