Software Scope Sample Clauses

Software Scope. Covered software does not include hardware, hardware vendor operating systems and/or other system software, Customer developed software, or third-party software. CentralSquare will deliver computer software and database structure for SQL/Server database. The following list depicts the software and number of licensed users associated with the Agreement. • Accounts PayableAccounts ReceivableFixed AssetsStores InventoryGeneral LedgerGrants Management • Job/Project Ledger • Project Allocation • Punchout
AutoNDA by SimpleDocs
Software Scope. Superion shall provide maintenance service, technical support, and software updates. Covered software does not include hardware, hardware vendor operating systems and/or other system software, “Customer” developed software, or third-party software. Superion will provide to the Customer a Community Development software to enhance local government operations through flexibility in managing inspections and regulating land use. Superion will deliver computer software and database structure for SQL/Server database. The following outlines the software modules included as part of the Agreement. The following further defines certain modules:
Software Scope. Oracle indicates that the Oracle Cloud Application Modules listed below provide relevant functionality for the Appendix A Requirements Eligible for Implementation. • Oracle Enterprise Resource Planning Cloud Service (ERP Cloud) ■ General LedgerAccounts PayablesAccounts ReceivablesFixed AssetsCash Management ■ Automated Invoice Processing ■ Purchasing ■ Self Service Procurement ■ Procurement ContractsSupplier PortalProject Financials, Contract Billing, and Grants Management ■ Expenses ■ Financial Reports Center • Oracle Human Capital Management Cloud Service (HCM Cloud) ■ Human Resources ■ Benefits ■ Payroll ■ Time & Labor ■ Absence Management (including Absence, Benefits) ■ Goal and Performance ManagementHealth and Safety Incidents ■ Employee/Manager Self-Service ■ Payroll ■ Recruiting/Onboarding • Oracle Enterprise Performance Management Cloud Service (EPM Cloud) ■ Planning & Budgeting ■ Narrative Reporting • Oracle Supporting Technologies (PaaS) ■ Oracle Integration Cloud (OIC) ■ Autonomous Transaction Processing database The organizational scope for the project includes the following entities: APS entities and any affiliated entities within the existing APS EBS system. APS and Sierra-Cedar will leverage the data conversion tools Oracle provides for populating Oracle Cloud Applications modules with data from systems being replaced. The tasks and responsibilities for data conversion are set forth in greater detail in Deliverable 6: Technical Strategy. The primary tools leveraged will be File-Based Data Import and HCM Data Loader. APS and Sierra-Cedar will jointly complete the following data conversions: Vendor is responsible for conversions and APS will assist for data mappings. APS will document the crosswalks from legacy values to new values in Oracle Cloud. For any non-E-Business Suite data extracts that will be used in data conversions, APS will provide. Attachment H &I Reference No. Data Source Data Type Attachment H &I - Total Fiscal Years of Data to Convert (Master Records) Sierra-Cedar Notes for the Conversion 1 Oracle General Ledger Chart of Accounts All Only the current Chart of Accounts information will be converted to support General Ledger History. 2 Oracle General Ledger Journal Transactions 3 +current Beginning balance* plus monthly (period) net activity for the prior three years and the current fiscal year prior to the Go-Live month / period. Beginning balance* (Balance Sheet accounts only) will be loaded into the last...
Software Scope. Design software configurations (Functional diagrams) on the DCS as per Control & Instrumentation Engineering specified philosophy. • Interface with equipment room (FUM 230- Analogue input modules), as per Table 1 • Design Human Machine Interface (HMI) on existing DCS for plant monitoring.
Software Scope. Unless otherwise contractually agreed, the scope of services of the Software is described in Appendix 1 (Scope of Services). The Provider is entitled to change the agreed scope of the Software at any time, if this results in an improvement of the Software concerned, a change in the legal situation requires such changes, such a change due to practical experience is appropriate or if the change is customary and taking into account the mutual interests of the Customer is reasonable. If Provider supplies any additional, complimentary Software or any other Service within the Quotation, then this can be withdrawn at any time and will pose no future obligation.
Software Scope. Superion shall provide maintenance service, technical support, and software updates. Covered software does not include hardware, hardware vendor operating systems and/or other system software, Customer developed software, or third-party software. Superion will deliver computer software and database structure for SQL/Server database. The following checked items outlines the software updates included as part of the Agreement. ☒ General LedgerHuman Resource Workflow ☒ Project Accounting ☒ Personnel ☒ Budgeting ☒ Position Control ☒ Personnel Budgeting ☒ Employee BenefitsAccounts Receivable ☒ Attendance ☒ Cash Receipts/Management ☒ Accounts Payable ☒ Purchasing ☒ Purchasing Card Interface ☒ Warehouse InventoryFixed Assets ☒ Fixed Assets Communicator ☒ Miscellaneous Billing ☒ Payroll, Deductions, Fringe Management ☒ Salary Projections ☒ Tools – Workflow ☒ Tools – Standard Interfaces ☒ Tools – Regulatory Reporting ☒ Tools – Standard Reports ☒ Superion Analytics Reporting

Related to Software Scope

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

  • Software Licensing Contractor represents and warrants that the software, if any, as delivered to City, does not contain any program code, virus, worm, trap door, back door, time or clock that would erase data or programming or otherwise cause the software to become inoperable, inaccessible, or incapable of being used in accordance with its user manuals, either automatically, upon the occurrence of licensor-selected conditions or manually on command. Contractor further represents and warrants that all third party software, delivered to City or used by Contractor in the performance of the Contract, is fully licensed by the appropriate licensor.

  • Software Licenses Seller has all necessary licenses to use all material third-party software used in Seller's business, and Seller's use of third-party software does not infringe the rights of any Person.

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Software License The SOFTWARE is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE is licensed, not sold.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Software Licence The following licence terms apply whether HP provides software to Customer as part of a managed service or as a separate software transaction.

  • Software Warranty We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

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