Deployment Model. StreamSets offers certain Products as Software and certain Products as a Service. In the event the same Product is offered as either Software or a Service (otherwise referred to as “Hybrid”), Customer may use either version provided that Customer: (i) notifies StreamSets Support personnel in advance of any switch between versions (including to receive any additional necessary Credentials) and (ii) acknowledges that StreamSets will not be responsible for any delays or interruptions associated with switching between versions.
Deployment Model. This implementation of Atlas Insight will be deployed in Selectron’s single-tenant hosted environment. Selectron’s hosting facility is a co-located data center featuring keyed entry and individual server locks for security. With a hosted solution, Selectron owns all hardware and is responsible for security, ongoing maintenance, and proactive support. As such, Selectron will be providing the necessary hardware and software. Selectron will work with Missoula to build a secure VPN tunnel for real-time read/write functionality between the hosted Atlas Insight server and the application database. Secure connection options may include client-level TLS or a persistent IPSec VPN. Each option requires specific ports to be opened for communication. Depending on the application database integration, these ports vary. The mobile server stores inspection results and then transfers inspection information to the permitting database. Communication between the field application and the server occurs whenever the device is connected to the internet. For virtual or physical servers, Atlas Inspections requires these minimum specifications: • Quad-Core Intel Processor • 16gb RAM • MS Windows 2016 • ESXi v6.5 (or newer) or Hyper-V Gen 1 SQL • Selectron can provide SQL or Missoula can provide an existing instance of Microsoft SQL Express or SQL Server 2012 (or newer). Browsers • Atlas Insight supports the most recent versions of major browser applications; primarily Chrome and Internet Explorer. When using Internet Explorer, “Compatibility Mode” is not supported. Geographic Information System • ESRI 9.3+ (and others supported by Leaflet)
Deployment Model. Most of the modern programming languages try to exploit abstraction in order to reduce complexity. That means that when we program rather complex systems it is towards the best of our interest to modularize to the finest/smaller component the work and at a second phase to write code that will be the abstract possible to accommodate all possible situations. The abstraction characteristic primarily focuses on the functional behaviour and the logical composition of software. Also we must say that the new modern programming languages are based in specific paradigms in order to deploy new software. The most prominent that we also use in our system are the multithreading and the concurrent objects. These two types of data types have the special characteristic of using interaction mechanisms such as method calls, message passing, and shared resources in order to share the same data repository. In our novel DSS we have developed a number of techniques to enable the compositional development of modular systems such as the spatiotemporal database management and the web services repository and the flexible reuse of these components whenever it is needed. For example, the development of the set of algorithms for the DSS and the set of web services for the case of one of the pilot cities and the reuse of them for the development of the other pilot city or the future inclusion of any other pilot city in our system justifies the reuse development mechanism of concurrent objects. However the aforementioned techniques suffer from a small deficiency that is, they still overlook how software’s deployment influences its behaviour. This is not always the case for concurrent objects and multithreading but in our case we faced the above problem especially when concurrent web services tried to modify data resources during execution. We resolved this issue by introducing virtualization on the methodology to concurrently access the same data and concurrently trying to modify the same data repository through concurrent objects. We had to separate the application model, which requires resources, and the deployment scenario, which reflects the virtualized computing environment and elastically provides resources. The next step that we are going to test during the evaluation phase of this software (i.e. the third year of the project) is the performance and scalability of a service for many different deployment scenarios already at the modeling level Deployment support provided by method...
Deployment Model. This implementation of Relay will be deployed on premise at Chula Vista. The Customer has elected to provide the components necessary to run the Relay solution. As such, Chula Vista will be providing 1 virtual server for the solution. For virtual or physical servers, Relay requires these minimum specifications: • Quad-Core Intel Processor • 16gb RAM • 250gb RAID 5 drives • MS Windows 2012 R2, 64-bit • ESXi v5.1 (or newer) or Hyper-V Gen 1 Chula Vista’s solution is licensed for: • Four (4) inbound IVR ports allowing for up to four concurrent calls
Deployment Model. This implementation of Field Portal will be deployed in Selectron’s single-tenant hosted environment. Selectron’s hosting facility is a co-located data center featuring keyed entry and individual server locks for security. With a hosted solution, Selectron owns all hardware and is responsible for security, ongoing maintenance, and proactive support. As such, Selectron will be providing the necessary hardware and software. Selectron will work with Chula Vista to build a secure VPN tunnel for real-time read/write functionality between the hosted Field Portal server and the Application Database. Secure connection options may include client-level TLS or a persistent IPSec VPN. Each option requires specific ports to be opened for communication. Depending on the application database integration, these ports vary. The Field Portal is a lightweight web application, optimized for desktop use. Browsers • The Field Portal supports the most recent versions of Chrome and Internet Explorer. Geographic Information System • ESRI 9.3+ (and others supported by Xxxxxxx)
Deployment Model. This implementation of Relay will be deployed in Selectron’s single-tenant Relay Managed Services environment. Relay Managed Services is a single-tenant hosted application, located in Selectron’s local hosting facility. Selectron’s hosting facility is a co-located data center featuring keyed entry and individual server locks for security. With a Managed Services solution, Selectron owns all hardware and is responsible for security, ongoing maintenance, and proactive support. Xxxx Point’s solution is licensed for: • Four (4) inbound IVR ports allowing for up to four concurrent calls • 25,000 inbound calls
Deployment Model. CFPL shall make its software product, known as "Hubbi" available to Company pursuant to the terms of this Agreement during the Subscription Term. Hubbi is an online, web-based platform and applications that are hosted by CFPL or a third party hosting facility designated by CFPL and provided as a service. Hubbi is currently hosted by CFPL’s approved hosting partners.
Deployment Model. The integrated solution must be implemented within 3 months of signing the contract. The solution will be registered on the name of MCGM and should be operational for a period of 5 years. The design modelling software system should be available on annual license subscription basis. While IPCS should be in a cloud- based software as a service (SaaS) model where it is hosted and maintained by the Vendor.
Deployment Model. As a standard, we host our services on our platform (direct deployment model) and pro-actively provide initial setup, upgrades, release updates and hotfixes as part of the subscription. Alternatively, you can also choose to host our services on your own platform. In this case, you are solely responsible for the initial setup, upgrades, release updates and hotfixes at your own costs.
Deployment Model. SugarCRM shall make the SugarCRM
