Product Functions Sample Clauses

Product Functions. Accounts will be created in MyUsage as Participating Customers are enrolled in Customer’s prepaid program. An initial payment (as determined by the Customer) will be posted to the account and displayed as service credits. Usage is monitored daily and the calculated cost for such usage is deducted from the Participating Customer’s current balance. Participating Customers can keep abreast of their balance through receipt of notifications for which they select the method and frequency during account creation. An order is created to disconnect the service when the service credit balance reaches zero. If a payment is received prior to the actual disconnection being completed, the order is automatically cancelled in MyUsage; therefore, disconnection can be avoided provided the cooperative utilizes the “Order Status” feature of MyUsage as opposed to a disconnection process outside of MyUsage. If the customer has already been disconnected, a reconnect order will be generated. Additional fees or charges will also be applied when applicable such as disconnect charges or reconnect charges. Participating Customers will have 7/24 access to their account via the internet or an IVR.
Sample 1
AutoNDA by SimpleDocs
Product Functions. Function Description Features Query Query collision report database • Employee Identity authentication by Date and Driver Name then • Search database using criteria supplied any of the following parameters: by Requestor • Driver Name (Last, First, MI) • Provide redaction depending on • Driver License Number Requestor authorization • Date of Birth • Log transactions for public disclosure • Location (City and or County) and record retention • • • • Roadway Date Collision Number Injury Indicator • • Capture Requestor information -log transaction Audits • Fatality Indicator • Agency Identifier Payment Process payment before collision • Bank Card processing report is allowed to be viewed • • • • Automated Clearing House (ACH) processing Billable Account processing Received Check [s] / Money Order[s] Audits Redaction Redact collision report based on • Based on Requestor Identity information provided by • Log transaction for public disclosure Requestor and business and record retention requirements provided in 5.2 of • Log image for record retention this document • Audits Import/Export Exchange data with external • Import collision report file from WSDOT systems • Export billable account transactions to Office of Financial Management (OFM) Accounts Receivable system • Export ACH transactions to Office of State Treasure (OST) Reports Typical types of Reports • Format for on on-screen viewing, • Invoices printing and downloading • Summary Reports • Daily Bank Card transaction • Forms reconciliation • Transactions logs • Monthly Billable Account invoices • Statistic Reports • Audits System Maintain system tables • Billable Account administration Administration • • • Report administration Purge administration Searches without payment Planning and Project Office SRS version 2.1 WRECR Software Requirements Specification
Sample 1
Product Functions. The VTRAS solution proposes a university-wide electronic research system which would unify distributed processes and systems across the campus. The system is intended to provide a full range of electronic services from initial identification of funding opportunities to final award including on-going tracking and historical reporting. The high-level functional areas include: • Proposal and Budget Preparation • Routing and Approval • Proposal Submission • Award Negotiation • Reporting and Status Tracking • Compliance • Workload Management
Sample 1

Related to Product Functions

  • Operating Functions Acquiror and Acquiror Bank shall cooperate with the Company and the Bank in connection with planning for the efficient and orderly combination of the parties and the operation of the Bank and Acquiror Bank, and in preparing for the consolidation of the banks’ appropriate operating functions to be effective at the Effective Time or such later date as the parties may mutually agree.

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Products and Services General Information The Vendor Agreement (“Agreement”) made and entered into by and between The Interlocal Purchasing System (hereinafter “TIPS”) a government cooperative purchasing program authorized by the Region 8 Education Service Center, having its principal place of business at 0000 XX Xxx 000 Xxxxx, Xxxxxxxxx, Xxxxx 00000 and the TIPS Vendor. This Agreement consists of the provisions set forth below, including provisions of all attachments referenced herein. In the event of a conflict between the provisions set forth below and those contained in any attachment, the provisions set forth shall control unless otherwise agreed by the parties in writing and by signature and date on the attachment. A Purchase Order (“PO”), Agreement or Contract is the TIPS Member’s approval providing the authority to proceed with the negotiated delivery order under the Agreement. Special terms and conditions as agreed between the Vendor and TIPS Member should be added as addendums to the Purchase Order, Agreement or Contract. Items such as certificate of insurance, bonding requirements, small or disadvantaged business goals are some, but not all, of the possible addendums.

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