Platform Architecture Sample Clauses

The PLATFORM ARCHITECTURE clause defines the structure, components, and technical framework of the platform being provided or developed under the agreement. It typically outlines the key elements such as software, hardware, interfaces, and integrations that make up the platform, and may specify standards or requirements for interoperability and scalability. By clearly delineating the platform's architecture, this clause ensures that both parties have a shared understanding of the system's design, reducing the risk of misunderstandings and facilitating smoother implementation and future upgrades.
Platform Architecture. 6.1 OVERVIEW
View SourceView Similar (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.
View SourceView Similar (2)
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
View SourceView Similar (2)
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. 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. 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. 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 routing in Jive Cloud utilizes a microservice...
View SourceView Similar (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.
View SourceView Similar (2)
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.
View Source
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.
View Source
Platform Architecture 
View SourceView Similar (3)

Related to Platform Architecture

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

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

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

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