Master Data Setup Sample Clauses

Master Data Setup. TCS proposes to use the SAP Inbuilt tool, Data migration cockpit for data upload in TCS Application System. TCS shall follow the following process for data upload. Process Activities TCS Responsibility Client Responsibility Joint Responsibility Scope Definition Identify Data Elements for upload at destination systems Yes Agree on data template Yes Configuration changes Configure TCS Application Systems as needed to consume data coming from source systems Yes Configure source systems as needed to extract data from Source systems Yes Data Loading Data load in the UAT system Yes Data Validation in UAT system Yes Data Load in Production System Yes Data Validation in Prod system Yes Data Upload Signoff Yes TCS recommends Client to provision complete set of production Master data as per TCS shared data upload template before the Deploy phase to avoid any potential project delays. The final production data provided by Client shall be first time right and available within two (2) weeks of UAT start date, as given in Annexure D. TCS will be responsible to upload this data which has to be validated and signed off by Client in the production environment. TCS shall not be responsible for any liability resulting from failure to meet the timeline in case Client fails to perform its obligations of submitting good quality data as per the agreed schedule. Any such delay, whether in receipt of Client data or delayed due to corrections to the data, may also result in re-baselining of Go-Live schedule and evaluated and managed through Change Management procedure.
AutoNDA by SimpleDocs

Related to Master Data Setup

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

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Data Services In lieu of any other rates or discounts, the Customer will receive discounts ranging from 25% to 55% for the following Data Services: Access: Standard VBSII Guide local loop charges for DS-3 Network Services Local Access Services.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Processing of Data You acknowledge and agree that with each use of the Service initiated by your xxxxxxxxxx.xxx authenticated Users the Service will access Your xxxxxxxxxx.xxx account to retrieve, store, manipulate, process and modify Customer Data based on Your configuration of the Service (“Process”) and You expressly consent to such access solely as is necessary to provide the Service or Support Services. If the Service cannot for any reason access Your xxxxxxxxxx.xxx account, Conga will be excused from any nonperformance of the Service. You acknowledge that to provide the Service, Customer Data leaves the xxxxxxxxxx.xxx system. Xxxxxxxxxx.xxx is not responsible for Customer Data when it is outside of the xxxxxxxxxx.xxx system.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

  • Data Segregation a. DSHS Data must be segregated or otherwise distinguishable from non-DSHS data. This is to ensure that when no longer needed by the Contractor, all DSHS Data can be identified for return or destruction. It also aids in determining whether DSHS Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation.

  • END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

  • Data Security The Provider agrees to utilize administrative, physical, and technical safeguards designed to protect Student Data from unauthorized access, disclosure, acquisition, destruction, use, or modification. The Provider shall adhere to any applicable law relating to data security. The provider shall implement an adequate Cybersecurity Framework based on one of the nationally recognized standards set forth set forth in Exhibit “F”. Exclusions, variations, or exemptions to the identified Cybersecurity Framework must be detailed in an attachment to Exhibit “H”. Additionally, Provider may choose to further detail its security programs and measures that augment or are in addition to the Cybersecurity Framework in Exhibit “F”. Provider shall provide, in the Standard Schedule to the DPA, contact information of an employee who XXX may contact if there are any data security concerns or questions.

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