Provider File Load Sample Clauses

Provider File Load. Each weekend ACS compiles the provider files and loads it to the Provider table. During this process an error file is created for each plan identifying the records that do not load to the table. IF the plan does not send a new file, then the previous file is used for this load. The tables are RELOADED not refreshed. Therefore, a file is needed for each plan. If the file attempts to load and all records error off, there will not be providers for that plan in the database. Weekly files are due by end of business on Thursday. ACS does not correct records provided by the plan. All records are loaded as they are received. The plans are responsible for ensuring the data provided is correct and complete. All data in the file is loaded in upper case for use by BESST. All zip codes are abbreviated to the first 5 digits of the zip code to facilitate searches.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Provider File Load

  • THIRD-PARTY CONTENT, SERVICES AND WEBSITES 10.1 The Services may enable You to link to, transfer Your Content or Third Party Content to, or otherwise access, third parties’ websites, platforms, content, products, services, and information (“Third Party Services”). Oracle does not control and is not responsible for Third Party Services. You are solely responsible for complying with the terms of access and use of Third Party Services, and if Oracle accesses or uses any Third Party Services on Your behalf to facilitate performance of the Services, You are solely responsible for ensuring that such access and use, including through passwords, credentials or tokens issued or otherwise made available to You, is authorized by the terms of access and use for such services. If You transfer or cause the transfer of Your Content or Third Party Content from the Services to a Third Party Service or other location, that transfer constitutes a distribution by You and not by Oracle.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):

  • Data Processing System, Program and Information (a) The Investment Company shall not, solely by virtue of this Agreement, obtain any rights, title and interest in and to the computer systems and programs, including all related documentation, employed by FTIS in connection with rendering services hereunder; provided however, that the records prepared, maintained and preserved by FTIS pursuant to this Agreement shall be the property of the Investment Company.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Customer Cooperation 3.2.1. Customer shall provide and make available all Customer personnel as may be further addressed in an applicable Order Form or that SAP reasonably requires in connection with performance of the Services.

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

  • Supplier Selection If Customer selects a seat or galley supplier that is not on the Boeing recommended list, such seat or galley will become BFE and the provisions of Exhibit A, Buyer Furnished Equipment Provisions Document, of the AGTA will apply.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Customer Materials 11.1. The Supplier including any of its employees, agents, consultants, contractors and any third party shall:

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

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