Application Solution Sample Clauses

Application Solution. A1 Scout Enterprise is an on-premise offering. A2 CONTRACTOR must provide for application management and design standard for all technology platforms and environments for the application solution (Development, Staging, Productions, DR, etc.) The CONTRACTOR Scout Enterprise software development process includes requirements, architectural review, design documents, implementation tracking, unit test plans, code reviews, acceptance test plans, and defect tracking. All code versioning is maintained in a source control system. Regarding test time, during six three-week iterative cycles the function is developed and tested interactively followed by a five- week Red Zone test phase. Red Zone entrance criteria (no high severity defects, development complete on features, lab updated and artifacts complete) may cause delays into Red Zone. Once Engineering exits the Red Zone, typically six weeks is allotted for Controlled Deployment to customers seeking a specific feature or are willing to test the first release. Issues found during that time are assessed and patches are created, if necessary. After exit from the Controlled Deployment phase, the version becomes Generally Commercially Available (GCA) and available for upgrades to all existing customers or for new project implementations. A3 CONTRACTOR must engage the State of Vermont using Service Level Agreements for system and application performance, incident reporting and maintenance. A4 The State owns any data they enter, migrate, or transmit into the solution and the vendor shall allow the State to pull or copy this data at any time free of charge. There are no additional charges for the State to pull or copy any data they have entered in the solution.
AutoNDA by SimpleDocs

Related to Application Solution

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • FABRICATION Making up data or results and recording or reporting them.

  • Construction Sequencing In general, the sequence of the proposed dates of Initial Operation of Interconnection Customers seeking interconnection to the Transmission System will determine the sequence of construction of Network Upgrades.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Server Use This agreement does not permit you to install or Use the Software on a computer file server. For information on Use of Software on a computer file server please refer to xxxx://xxx.xxxxx.xxx/go/acrobat_distribute for information about Adobe Reader; or xxxx://xxx.xxxxx.xxx/go/licensing for information about the Adobe Runtimes.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • 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 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 CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

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