Software Setup Sample Clauses

Software Setup. This document the setup code used by the organization to support the implementation. This does not include “bulk” imported data for accounts, employees, or property. It does include sample data for use during testing and demos. Application Administration County agrees that once County accepts the developed business processes and SOP, any changes to the processes due to County decisions and/or changes will be the responsibility of County and may require the initiation of the change request process as described in paragraph 10 of Contract. SOP review process
AutoNDA by SimpleDocs
Software Setup. The Tutor will provide free extra time in the first few lessons to set up teleprogramming software. This may take up to 20 minutes. After the setup time, Tutor will provide a lesson for the agreed-upon duration.
Software Setup. KEV implements the information from the district that was provided during the project planning. The system is installed on KEV’s servers and updates are made to the database with school information including student information data. Testing is performed on the system to ensure that funds are transferred to the correct bank accounts. This includes eCheck, credit cards, and a bank account verification check.
Software Setup. This documents the setup code used by the organization to support the Application Administration implementation. This does not include “bulk” imported data for accounts, employees, or property. It does include sample data for use during testing and demos. County agrees that once County accepts the developed business processes and SOP, any changes to the processes due to County decisions and/or changes will be the responsibility of County and may require the initiation of the change request process as described in paragraph 10 of Contract. Software Code Configuration and Set-Up/AiM Module Setup Contractor’s AiM software is code-driven and will be configured based on County’s unique environment and business processes. Contractor works interactively with County to enter all set-up code required to create a fully functional system. This interactive approach assures that County understands and is capable of modifying the configuration if needed in the future. The set-up code will be Orange County Information Technology Page 50 of 122 Redline_MA-017-18010489 AssetWorks, LLC Folder No.:C003855 Computerized Maintenance Management System based on the BPA and the initial SOP, which will determine the initial configuration of the AiM system. The system configuration may be further refined after the Workflow Walk-through and Data Conversion efforts are complete. The County AiM System Administrator must participate in the code set-up so that he/she is prepared to make modifications to the configuration on an ongoing basis. County will be responsible for the sustainment of the system and will input actual codes and County- specific data that is not being converted and w i ll make modifications to the setup a s identified bot h pre- and post-Go-Live. As noted above, AiM is code driven and configurable to model the desired business processes. The AiM modules involved in this project will be setup and configured by Contractor. This will involve Contractor working interactively with County to develop the configuration that will support the desired business operations. Both Contractor and County will work in a hands-on manner to set-up and configure each module. The set-up activities listed below are provided as an example of typical set-up configurations. • Operations and Maintenance – AiM must be configured to support maintenance operations for all County departments that plan to implement CMMS as part of this project and to, based on currently known parameters, not preclu...
Software Setup. There is one basic setting which must be done in order for the software to work. You need to set up the ODBC connection to the database.
Software Setup. Chapter 2 Standard
Software Setup. Once set up, BoSS-21 is designed to be easy to use with little or no training. In the following sections we describe each step in detail. You can successfully run the system by following the sequence described below. The setup sequence, described in the previous chapter, consists of turning the system on and launching the BoSS-21 application, adjusting system settings (you will rarely need to do this, if ever), and calibrating the system. These are usually only done once each day, when the system is first turned on. It doesn’t need to be repeated until the next time the system is started up. The measuring procedure described in the next chapter is what needs to be performed each time someone is measured. Launch BoSS-21 BoSS-21 Standard, with its semi-permanent installation, can begin measuring less than 10 minutes after the system is turned on. Typically the system is turned on and calibrated at the beginning of each day, so it is always available for use. The computer is typically powered down at the end of each day, though it could be put into Sleep or Hibernate modes instead. Once the system is up and running, the total measuring time per person can be less than 5 minutes.
AutoNDA by SimpleDocs

Related to Software Setup

  • Software Services If elected by Customer, the following Software Services will be made available for Customer’s use.

  • SOFTWARE SECURITY If applicable, BA warrants that software security features will be compatible with the CE’s HIPAA compliance requirements. This HIPAA Business Associate Agreement-Addendum shall supersede any prior HIPAA Business Associate Agreements between CE and BA. EXHIBIT E

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Urgent Care Services All Medically Necessary Covered Services received in Urgent Care Centers, Retail Clinics or your Primary Care Physician’s office after-hours to treat an Urgent Medical Condition will be covered by AvMed. Any request for reimbursement of payment made by a Member for services received must be filed within 90 days or as soon as reasonably possible but not later than one year unless the Member was legally incapacitated. If Urgent Medical Services and Care are required while outside the continental United States, Alaska or Hawaii, it is the Member’s responsibility to pay for such services at the time they are received. For information on filing a Claim for such services, see Part XIII. REVIEW PROCEDURES AND HOW TO APPEAL A CLAIM (BENEFIT) DENIAL.

  • Core Services The Company agrees to provide those Core Services to the Municipality as set forth in Schedule “A” and further agrees to the process contained in Schedule “A”.

  • Use of Verizon Telecommunications Services 2.1 Verizon Telecommunications Services may be purchased by Connectel under this Resale Attachment only for the purpose of resale by Connectel as a Telecommunications Carrier. Verizon Telecommunications Services to be purchased by Connectel for other purposes (including, but not limited to, Connectel’s own use) must be purchased by Connectel pursuant to other applicable Attachments to this Agreement (if any), or separate written agreements, including, but not limited to, applicable Verizon Tariffs.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

Time is Money Join Law Insider Premium to draft better contracts faster.