DEPLOYMENT AT FLAME INFRASTRUCTURE Sample Clauses

DEPLOYMENT AT FLAME INFRASTRUCTURE. Gnome Trader’s virtual game world consists of shops, which allow the players to interact with the gnome characters. The physical real-world location of these shops can be entirely defined by the developers. In FLAME empowered cities such as Bristol and Barcelona these shops should be placed close to access points or computing nodes to enable low-latency, high-bandwidth, and, most importantly, localized access to the game data. In Barcelona, all FLAME access points are placed along a single street. In the game, a shop would be installed at each access point. While the main trading activities for players are hence confined to this street in Barcelona, players could still create gardens in other areas of the city. In Bristol, FLAME access points and nodes, and hence the Gnome Trader shops, are placed in a wider circle around the city centre. This forces the players to move around the city to interact with the game, which is intended. This deployment scenario is more interesting for Gnome Trader as presumably a higher dynamic and larger variety can be observed in the game’s economy.
Sample 1Sample 2
AutoNDA by SimpleDocs
DEPLOYMENT AT FLAME INFRASTRUCTURE. The deployment of the PMM experiment in the Barcelona FLAME infrastructure is planned to use some key media functions to be delivered for integration as per following summary: • Origin Streaming Server (based on Symphony media server by Nextworks) o Virtual machine characteristics: ▪ Processors: 4vCPU Intel type, 2.4 GHz or better ▪ Memory: minimum 8GB RAM ▪ Storage: minimum 200 GB for central media library ▪ OS: at least Ubuntu 16.04 LTS ▪ Networks: 1 interface gigabit network equivalent for streaming + 1 interface for server control o Number of instances: 1 • Local Cache (based on Apache Traffic Server) o Virtual machine characteristics: ▪ Processors: 2vCPU Intel type, 2.4 GHz or better ▪ Memory: minimum 2GB RAM ▪ Storage: minimum 100 GB for local media library ▪ OS: at least Ubuntu 16.04 LTS ▪ Networks: 1 or 2 interfaces gigabit network equivalent for streaming + 1 interface for server control o Number of instances: 3 • Transcoding, transrating for MPEG-DASH (based on ffmpeg) o Virtual machine characteristics: ▪ Processors: 2vCPU Intel type, 2.4 GHz or better ▪ Memory: minimum 2GB RAM ▪ Storage: minimum 30 GB for local media library ▪ OS: at least Ubuntu 16.04 LTS ▪ Networks: 1 interfaces gigabit network equivalent for streaming + 1 interface for server control o Number of instances: 3 o Media application for Android/IOS connect to the cached media server o Number of instances: as many as end-users The planning of the experiment at the time of writing this deliverable is based on the deployment of local caches in VMs to be hosted in the four NAPs instantiated virtually in the server in the FLAME street cabinet in Calle Pere IV; origin media server and transcoding/transrating hosted in VMs deployed in the main DC in Omega Building. For scenario 2 and 3 discussions are ongoing to identify a local business in the Calle Pere IV where to host a fixed instance of the NAP to run the scenario in aggregation areas. Use of foundation media functions from FLAME WP4 is also under evaluation to complement and/or preliminarily test media distribution functionalities in FLAME platform with FLIPS.
Sample 1
DEPLOYMENT AT FLAME INFRASTRUCTURE. The City-wide Storytelling experiments aim to create a branching, interactive narrative within a branching city environment. The FLAME infrastructure in Bristol offers a branching topology of coverage in the city centre. BRISTOLOPEN is supporting scenario development by providing details about physical infrastructure utilized by FLAME as well as surrounding physical city infrastructure that may be integrated within the creative concept of the interactive narrative. FLAME infrastructure in Bristol offers both Wi-Fi and LTE-based coverage over several high-traffic pedestrian areas within the city centre. The City-wide Storytelling experiments will steer users to locations in close proximity to these coverage zones in order to utilize maximal bandwidth and low latency access to multimedia assets stored in the FLAME NAPs. The Bristol City Council provides a web application (xxxx://xxxx.xxxxxxx.xxx.xx/pinpoint/) that offers a map-based interface to historical information about Bristol. Images and text are integrated to describe the historical significance of physical locations and entities within Bristol. BRISTOLOPEN is supporting the identification of physical entities, including buildings and objects (e.g. statues and signs), that are located in proximity to FLAME infrastructure NAPs. Some of the physical entities are being integrated into the narrative as part of the creative concept while others are being utilized to provide visual cues supporting AR visualizations.
Sample 1

Related to DEPLOYMENT AT FLAME INFRASTRUCTURE

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • 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 CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC 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 CSTC 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 CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC 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 CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Deployment (a) In filling a position vacancy at a location NAV CANADA may proceed by the transfer of an employee at the same level. (b) For the purposes of this Article, a “transfer” shall be considered to be a lateral change in position. (c) Transfer requiring relocation under the NCJC Travel Program shall be subject to the employee’s written consent.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!