Cloud Engine Sample Clauses

Cloud Engine a. Cloud computation of the processing of raw signals for the expressed purpose of wellness visit (fetal and maternal heart tone capture, and BP readings). b. Cloud computation available during predefined Virtual Visit hours (e.g. 9am – 2pm EST, and defined in the Pre-Pilot Activities)
Cloud Engine. The Service is accessed by Customer via the Graphical User Interface (“GUI”) or via API providing centralised management with the ability to perform a variety of actions as set out below. i. Creation of server or application blueprints: Pre-created server configurations or entire application stacks can be defined for the purposes of automation and orchestration within the Service environment. ii. Provide a holistic view of all resources within the Media Cloud: Visibility into all technology components and allows action against discovered resources, resulting in better performance, cost effectiveness, and the power to reallocate and optimize environments. Discovered assets are synchronized directly from each region within the Service providing a simple global view of the ‘Cloud’. iii. Blueprints to support IT in creating repeatable processes for delivering servers and services: All processes for deployment get encapsulated into a blueprint, allowing authorized users to order multiple services using one method. IT can make blueprints available to users via a catalogue, enabling them to instantiate their own resources. iv. Role Based Access Controls (RBAC): Role creation and delegation with capability to enforce quotas and authorization workflows.