Volume Database. A database of the volume of dry and reefer cargo moved by the Parties in each direction in the Trade, capable of generating reports for various periods of time and various portions of the Trade.
Volume Database Sample Clauses
Related to Volume Database
Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Month, Assuming Institution shall provide Receiver:
Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.
Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.
Web Portal If you elect to link to and use the web interface provided by us (the “Web Portal”), you agree that the Web Portal is for the sole purpose of enabling Recipients to update and add their contact information. If you elect to use the Web Portal, we grant for the period of the Term (as defined below) to you a limited non-exclusive, worldwide, royalty-free license to place a digital image of the applicable sign-up Logo, which will be presented to you (the “Image”), on an appropriate page of your Internet site, with a hyperlink to our Web Portal site (the “Link”) currently at xxxxx://xxxxxx.xxxxxxxxxxxxxxxxxxx.xxx/. You may not use any other trademark or service xxxx in connection with the Image without our prior written approval. The Link may not be used in any manner to provide an Authorized User with access to the Web Portal via any framing, layering or other techniques now known or hereafter developed that permit display of the Web Portal with any materials posted by you or anyone other than us. You may not allow the Image to be linked to any other web site. You may not use the Image in any manner not permitted hereunder, modify the Image, or copy, or create a derivative work from, the “look and feel” of the Image. We will have the right to review all uses of the Image for quality control purposes and proper compliance. We reserve the right to modify permission to use the Image and/or the Link at any time.
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
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.
Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:
