Operational Environments Clause Samples
Operational Environments. As part of the Subscription and for use with the SaaS Service, Licensor will provide Buyer: i) one (1) “Test Environment” for Buyer’s use in testing the integration of SaaS Service; ii) one (1) “Development Environment” for Buyer’s use in integrating the operation of Buyer’s software with the SaaS Service; and iii) one (1) “Production Environment” for use with Buyer’s production data. The Test Environment and the Development Environment will be limited to ten percent (10%) of the Licensed Quantity, and will only be used in support of the Production Environment. The Test Environment, the Development Environment and the Production Environment are collectively referred to herein as the “Operational Environments”.
Operational Environments. We currently provide testing and technology support for VA’s EHRM Program as key members of the Test and Evaluation (TE) team for major COTS program implementations that consist of architecture, integration, interoperability, VistA Data Service (VDS), and service virtualization functionality. As a result of this hands-on experience, EMKS’s resources can apply their unique perspective to provide detailed test environment logical requirements (TELRs), architecture diagrams, test data, service virtual components, and test environment configurations for both large and small testing projects. EMKS can provide the operational environment support needed for testing activities, including but not limited to software testing, system testing, and project testing, which includes project-level integration testing, development testing, and operations support for environments and systems.