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. There are two basic settings which must be done in order for the software to work. You need to set up the ODBC connection to the database, and you need to set up the serial port connected to the card readers. There are two main programs in the Xxxx Software. The Xxxx L9 program, called TCLevel9.exe, is the main communication program which must be running all of the time. The Xxxx Command Central program, called ToyeMS.exe is the programming interface and does not have to be running for the system to operate. There are also two optional programs, TCLevel8, referred to as L8, for monitoring only, and TCLevel10, referred to as L10, for operating a remote site over a LAN connection.
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
AutoNDA by SimpleDocs
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.

Related to Software Setup

  • 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 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.