Environments corrections . Concerns and complaints, which remain unresolved after committee recommen- dations have been issued, will be referred directly to the chief operating officer who, within 30 duty days of receiving a complaint, shall investigate and render a final and binding decision .
Environments. The U.S. signatories will provide to the foreign signatories, as part of the LV-to- Spacecraft Interface Control Document, the Loads/Shock/Vibration/Acoustic Environmental inputs for the spacecraft. The environments as specified in the LV- to-Spacecraft IRD will be used as the baseline for the spacecraft design. Any updates of LV environments will be coordinated with NSPO in a timely manner to assure the spacecraft design is not affected.
Environments. The Parties will check the cell in Table 1 below for a particular Product if Silver Spring is to install that Software module in the specified environment. Silver Spring will provide Application Management services as described in Task 4 of this SOW, for each environment for the term listed in Table 1. The term is further described in the next section of this Attachment. Table 1: Basic Setup Information for Each GridScape Environment Environments: Env’t / Application Management and DA Communication Network Management Term** Software Product: (Y months after GridScape Availability requested by (X wks after SOW S.D.*) Availability begins) Production *** *** *** Other, if any: *** *** *** * SOW S.D.= SOW signature date, which is the date of last signature of this SOW. Numbers shown reflect the time Silver Spring requires to set up environments, since work will only start after this SOW’s execution. ** Solution Services begins upon the accessibility of the environment by ComEd, and may be renewed or terminated at the end of the term noted (see next section for xxxxxx description). The term should be noted with an estimated term (e.g., “est. 12” for a one-year term) for temporary environments.
Environments. SAP Shall provide one development, one test, and one production environment for the Cloud Services currently referred to as SAP SuccessFactors Environment (Employee Central and Employee Central Payroll)
Environments. As part of the project, Tyler and the City will establish the following environments. All hardware specifications, requirements, and required staffing will support development of all listed environments. Testing Training Production/Live
Environments. SunGard will provide two (2) separate environments to Customer. All updates and releases will be deployed to the Customer’s TEST environment with notification sent to the Customer’s representative identified in Annex 2, Item 3. Once an update is reviewed by Customer, formal notification must be sent to SunGard to deploy the update or release to the LIVE system. Testing is the responsibility of the Customer prior to roll-out among all users. SunGard will provide VPN credentials to the Customer for the purpose of accessing and maintaining TRAKiT reports in the hosted TEST environment. Customer shall contact SunGard to request that tested reports be migrated to Customer’s hosted PRODUCTION environment. Colocation cabinet in a location served by secured surveillance systems, a 24x7 Network Operations Center, and redundant power, UPS’s, cooling and network service providers. 24x7 monitoring of the environmental services for the hosting colocation cabinet, including: cooling, power, UPS’s and network availability. Subject to Scheduled Downtime described below, a 99.99% uptime goal for the network backbone. Private Cloud Server environment dedicated to SunGard Customers, including: Redundant Cisco enterprise class firewalls. Redundant servers in the shared hosting environment, with load balancing and fail over protection. 50 Gb of storage for Customer data FTP access for exports/imports. SMTP for emails outbound from TRAKiT. Encryption of the TRAKiT database at rest in the Private Cloud Server shared environment via SQL Transparent Data Encryption. Management of the Private Cloud Server environment consistent with industry standard practices.
Environments. (a) The Supplier shall create and maintain the following environments:
Environments. Database administration services are restricted to three TYLER environments: one live environment, one training environment, and one test environment.
Environments. Vendor will maintain separate development, quality assurance, and production environments in Via. At no time will the processing of any test data impact the production environment.
Environments. The [Standard / Premium / Enterprise] SaaS Tier includes access to one (1) Production Environment and access to [one (1) [For Standard/Premium] / two (2) [For Enterprise] Non-production Environments. Customer shall receive access to ## additional Non-production Environments. If required, Customer will receive a Data Validation Environment at no charge through the period ending thirty (30) days after the Go-Live date. At the end of such period the Data Validation Environment will be automatically terminated by Anthology.
