Description of the Match Sample Clauses

Description of the Match. VA establishes records for all individuals who have applied for benefits and must verify their eligibility under the ▇▇▇▇▇▇▇▇▇▇ GI ▇▇▇▇ — Active Duty, the ▇▇▇▇▇▇▇▇▇▇ GI ▇▇▇▇ — Selected Reserve, Reserve Educational Assistance Program, and the Post-9/11 GI ▇▇▇▇ program. DMDC, as the source agency, will provide to VA the eligibility records on DoD individuals consisting of various data elements set forth in Attachment 2 which contains specific data relating to the requirements for eligibility including data on member contribution amounts, service periods, and transfer of entitlement. VA will match on several attributes, including SSN, DoD EDIPI (or VA_ID), Date-of-Birth, Last Name, and File Identification Number. Service submissions showing new eligibility records and changes in Chapter 30 eligibility statuses are processed daily/weekly/monthly at DMDC and transmitted electronically to VA weekly, while Chapter 33 service submissions are transmitted electronically to VA nightly via database replication in VA/DoD Identity Repository (VADIR) These files are loaded on VA computers and matched with VA benefit records to determine any adjustments to benefits that are necessary as a result of changed eligibility status. VA processes applications from claimants for educational benefits at t h r e e (3) Regional Processing Offices located throughout the country. The data are accessed through VA’s Benefits Delivery Network, and entered into the VA automated claims processing system to establish or change a benefit record for the claimant. VA benefit records are established on an ongoing real-time basis. For the ▇▇▇▇▇▇▇▇▇▇ GI ▇▇▇▇ — Active Duty, the ▇▇▇▇▇▇▇▇▇▇ GI ▇▇▇▇ — Selected Reserve, Reserve Educational Assistance Program, and the Post-9/11 GI ▇▇▇▇ program, a match is accomplished between the application data entered in the benefit record and the enrollment and/or eligibility record submitted by DMDC. After an initial benefit record is established in the VA system, any changes in the enrollment and/or eligibility record provided by DMDC will result in a notification to VA by means of a computer match. On a monthly basis, a copy of all VA benefit records is provided to DMDC so that DoD is aware of the payment status of recipients.
View SourceView Similar (5)
Description of the Match. The match will be based on the following list of data elements: last four digits of Social Security Number, date of birth, last name and first name. CHFS will match the USAC Data elements to its SNAP and Medicaid data. There are two (2) scenarios for the CHFS match process, which will be returned to USAC as a binary yes/no response. CHFS will not release any other information from the SNAP or Medicaid recipient’s records. The scenarios are: 1. Positive CHFS match – CHFS finds a match in its respective system for the USAC Data provided. 2. No CHFS match – CHFS finds no match in its respective system for the USAC Data provided.
View SourceView Similar (2)
Description of the Match. The match will be based on the following list of data elements: Full First Name, Full Last Name, Date of Birth, and Last Four Digits of the Social Security Number. DSHS will match the USAC data elements to its SNAP and Medicaid data. There are two (2) scenarios for the DSHS match process, which will be returned to USAC as a binary yes/no response. DSHS will not release any other information from the SNAP or Medicaid recipient’s records. The scenarios are: 1. Positive DSHS match – DSHS finds a match in its respective system for the USAC data provided. 2. No DSHS match – DSHS finds no match in its respective system for the USAC data provided.
View SourceView Similar (2)
Description of the Match. The match will be based on the following list of data elements: last four digits of Social Security Number, date of birth, last name or first name. PDHS will match the USAC Data elements to its SNAP and Medicaid data. There are two (2) scenarios for the PDHS match process, which will be returned to USAC as a binary yes/no response. PDHS will not release any other information from the SNAP or Medicaid recipient’s records. The scenarios are: 1. Positive PDHS match – PDHS finds a match in its respective system for the USAC Data provided. 2. No PDHS match – PDHS finds no match in its respective system for the USAC Data provided.
View Source
Description of the Match. The complete list of data elements are listed in the Interface Control Document (attached as Appendix A). A disaster survivor completes a FEMA assistance registration after a disaster. The IA System stores data provided by the disaster victim on a FEMA 90-69 online form. FEMA processes the registration. During the FEMA processing period, the registration status will change status to ‘VR’ (Valid Registration) in the IA System. This means that the registration has been processed through the data completeness and identity verification. The FEMA registration data as per Appendix A Section 2.2.2 is sent to HUD for initial verification via a secure web service. HUD will match the IA/IHP data elements to its CPD, EIV, IMS/PIC, and TRACS databases. There are two scenarios for the HUD match process. The scenarios are: 1. Positive HUD match – HUD finds a match in their respective system for the DHS/FEMA data provided i. If a record submitted by DHS/FEMA to HUD results in a match by HUD, DHS/FEMA becomes a recipient of HUD Housing Assistance information as listed in Appendix A Section 2.2.3.2. ii. DHS/FEMA will use the information it receives from HUD to independently evaluate and determine its applicants’ eligibility for its housing programs under 42 U.S.C. § 5174(c)(1), according to Section VII of this Agreement. iii. DHS/FEMA will compare the HUD data with the FEMA registration data using the survivor’s Social Security Number and unique registration ID. The comparison process will be an automated process in IA System. The IA program will also be able to manually verify the comparison results using database queries. The registration ID is required to ensure the FEMA and HUD data can be aggregated in IA Systems as it is a unique primary key for the separate data sets. iv. Once DHS/FEMA confirms that match, the complete data set for the potential duplication of housing benefits is sent to FEMA’s Program Review process for manual evaluation of any duplication of benefits. If FEMA review staff determines that there is a duplication of benefits, the duplicated amount is deducted from the eligible award. FEMA applicants receive a letter that indicates the amount of their eligible award and their ability to appeal. 2. No HUD match - HUD does not find a match in their respective system for the DHS/FEMA data provided i. If the initial verification record submitted by DHS/FEMA to HUD does not result in a match by HUD, DHS/FEMA becomes the source agency and sends additional F...
View Source
Description of the Match. The match will be based on the following list of data elements: last four digits of Social Security Number, date of birth, last name and first name. DHS will match the USAC Data elements to its SNAP data. There are two (2) scenarios for the DHS match process, which will be returned to USAC as a binary yes/no response. DHS will not release any other information from the SNAP recipient’s records. The scenarios are:
View Source
Description of the Match. The match will be based on the following list of data elements: last name, date of birth, and last four digits of Social Security Number. DSS will match the USAC data elements to its SNAP data. There are two (2) scenarios for the DSS match process, which will be returned to USAC as a binary yes/no response. DSS will not release any other information from the SNAP recipient’s records. The scenarios are: 1. Positive DSS match – DSS finds a match in its respective system for the USAC data provided. 2. No DSS match – DSS finds no match in its respective system for the USAC data provided.
View Source
Description of the Match. The match will be based on the following list of USAC Data elements: address, date of birth, last name, and first name for the veteran and/or the survivor, as applicable. The VA will match the USAC Data elements to its Veterans Pension and Survivors Pension benefits data. The VA’s data system will respond in real-time to the match requests of each application or annual recertification for the Lifeline or FCB programs, by providing the following list of VA Data elements: VA Program Awards name, VA Program Awards code. The VA will not release any other information from the Veterans Pension or Survivors Pension recipient’s records. There are two (2) scenarios for the VA match process, which will be returned to USAC: 1. List of VA Program Awards for the veteran/survivor based on a VA match – The VA finds a match in its respective system for the USAC Data provided. 2. No VA match – The VA finds no match in its respective system for the USAC Data provided.
View Source

Related to Description of the Match

  • Description of the service 10.1.1 Automatic transfer service implies a transfer by the bank of the funds from the client’s account without further consent of the client, on the basis of fixed amount determined by the client in its application form or of information provided by the client’s creditor to the bank on the client’s debt. 10.1.2 The parties agree that the payment order created (generated) by the bank for the purposes of automatic transfer services shall have the legal force equal to the document having been printed on the paper and executed by the person(s) authorized to manage of the account. 10.1.3 The bank shall carry out the automatic transfer services in accordance with requirements and conditions stipulated in this agreement, the application on registration for automatic transfer service and the sources disseminated by the bank. 10.1.4 For the purposes of obtaining automatic transfer services the client shall apply to the bank with the application as per paragraph 1.2 of this agreement.

  • Description of Service 2.9.1.1 BellSouth shall make available to <<customer_short_name>> LMU information with respect to Loops that are required to be unbundled under this Agreement so that <<customer_short_name>> can make an independent judgment about whether the Loop is capable of supporting the advanced services equipment <<customer_short_name>> intends to install and the services <<customer_short_name>> wishes to provide. LMU is a preordering transaction, distinct from <<customer_short_name>> ordering any other service(s). Loop Makeup Service Inquiries (LMUSI) and mechanized LMU queries for preordering LMU are likewise unique from other preordering functions with associated SIs as described in this Agreement. 2.9.1.2 BellSouth will provide <<customer_short_name>> LMU information consisting of the composition of the Loop material (copper/fiber); the existence, location and type of equipment on the Loop, including but not limited to digital loop carrier or other remote concentration devices, feeder/distribution interfaces, bridged taps, load coils, pair-gain devices; the Loop length; the wire gauge and electrical parameters. 2.9.1.3 BellSouth’s LMU information is provided to <<customer_short_name>> as it exists either in BellSouth's databases or in its hard copy facility records. BellSouth does not guarantee accuracy or reliability of the LMU information provided. 2.9.1.4 BellSouth’s provisioning of LMU information to the requesting CLEC for facilities is contingent upon either BellSouth or the requesting CLEC controlling the Loop(s) that serve the service location for which LMU information has been requested by the CLEC. The requesting CLEC is not authorized to receive LMU information on a facility used or controlled by another CLEC unless BellSouth receives a LOA from the voice CLEC (owner) or its authorized agent on the LMUSI submitted by the requesting CLEC. 2.9.1.5 <<customer_short_name>> may choose to use equipment that it deems will enable it to provide a certain type and level of service over a particular BellSouth Loop as long as that equipment does not disrupt other services on the BellSouth network. The determination shall be made solely by <<customer_short_name>> and BellSouth shall not be liable in any way for the performance of the advanced data services provisioned over said Loop. The specific Loop type (e.g., ADSL, HDSL, or otherwise) ordered on the LSR must match the LMU of the Loop reserved taking into consideration any requisite line conditioning. The LMU data is provided for informational purposes only and does not guarantee <<customer_short_name>>’s ability to provide advanced data services over the ordered Loop type. Furthermore, the LMU information for Loops other than copper-only Loops (e.g., ADSL, UCL-ND, etc.) that support xDSL services, is subject to change at any time due to modifications and/or upgrades to BellSouth’s network. Except as set forth in Section 2.9.1.6, copper-only Loops will not be subject to change due to modification and/or upgrades to BellSouth’s network and will remain on copper facilities until the Loop is disconnected by <<customer_short_name>> or the End User, or until BellSouth retires the copper facilities via the FCC’s and any applicable Commission’s requirements. <<customer_short_name>> is fully responsible for any of its service configurations that may differ from BellSouth’s technical standard for the Loop type ordered. 2.9.1.6 If BellSouth retires its copper facilities using 47 C.F.R § 52.325(a) requirements; or is required by a governmental agency or regulatory body to move or replace copper facilities as a maintenance procedure, BellSouth will notify <<customer_short_name>>, according to the applicable network disclosure requirements. It will be <<customer_short_name>>’s responsibility to move any service it may provide over such facilities to alternative facilities. If <<customer_short_name>> fails to move the service to alternative facilities by the date in the network disclosure notice, BellSouth may terminate the service to complete the network change.

  • Description of the transfer(s) The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

  • Description of the Transfer The details of the transfer and of the personal data are specified in Annex B. The parties agree that Annex B may contain confidential business information which they will not disclose to third parties, except as required by law or in response to a competent regulatory or government agency, or as required under clause I(e). The parties may execute additional annexes to cover additional transfers, which will be submitted to the authority where required. Annex B may, in the alternative, be drafted to cover multiple transfers.

  • Description of the Project THIS SHOULD BE NO MORE THAN A TWO PARAGRAPH DESCRIPTION THAT PROVIDES A BACKGROUND OF THE PROBLEM, AS WELL AS HOW THE CONTRACTOR INTENDS TO SOLVE THE PROBLEM. KEEP IN MIND THAT THE CONTRACT SHOULD “STAND ON ITS OWN,” I.E. ANYONE SHOULD BE ABLE TO PICK IT UP AND FIGURE OUT WHAT IS GOING ON.)