Proposed New Routine Uses Sample Clauses

Proposed New Routine Uses. The Privacy Act requires that agencies publish a notice in the Federal Register of ‘‘each routine use of the records contained in the system, including the categories of users and the purpose of such use.’’ 5 U.S.C. 552a(e)(4)(D). We have developed the following new routine uses that will allow us to disclose information to additional entities in support of our representative payee program: • To agencies or entities who have a written agreement with SSA, to perform representative payee reviews for SSA and to provide training, administrative oversight, technical assistance, and other support for those reviews; and • To state protection and advocacy systems, that have a written agreement with SSA to conduct reviews of representative payees, for the purpose of conducting additional reviews that the protection and advocacy systems have reason to believe are warranted. We will include the new routine uses in the following systems of records: System No. and name New routine use Federal Register citation No./publication date 60–0058—Master Files of Social Security Number Holders and SSN Applications ........................... No. 47 & 48 ... 75 FR 82121, 12/29/10. 78 FR 40542, 07/05/13. 79 FR 78780, 02/13/14. 60–0089—Claims Folders System ....................................................................................................... No. 37 & 38 ... 68 FR 15784, 04/01/03. 72 FR 69723, 12/10/07. 60–0090—Master Beneficiary Record ................................................................................................. No. 40 & 41 ... 71 FR 1829, 01/11/06. 72 FR 69723, 12/10/07. 78 FR 40542, 07/05/13. 60–0094—Recovery of Overpayments, Accounting and Reporting .................................................... No. 10 & 11 ... 70 FR 49354, 08/23/05. 72 FR 69723, 12/10/07. 60–0103—Supplemental Security Income Record and Special Veterans Benefits ............................ No. 38 & 39 ... 71 FR 1830, 01/11/06. 72 FR 69723, 12/10/07. 60–0222—Master Representative Payee File ..................................................................................... No. 21 & 22 ... 78 FR 23811, 04/22/13. 60–0318—Representative Payee/Misuse Restitution Control System (RP/MRCS) ............................ No. 9 & 10 ..... 70 FR 29547, 05/23/05. 72 FR 69723, 12/10/07. We are not republishing in their entirety the SORNs to which we are adding the proposed new routine uses. Instead, we are republishing only the identification number, name of the SORN, the numbers...
AutoNDA by SimpleDocs

Related to Proposed New Routine Uses

  • Proposed Goods and Services Proposed Goods and Services docx Please upload one or more documents or sheets describing your offerings, line cards, catalogs, links to offerings OR li st links to your offerings that illustrate the catalog of proposed lines of goods and or services you carry and offer unde r this proposal. I does not have to be exhaustive but should, at a minimum tell us what you are offering. It could be as simple as a sheet with your link to your online catalog of goods and services. Resellers/Dealers - COMPLETE AND UPLOAD ONLY IF YOU HAVE RESELLER OF YOUR GOODS OR SERVICES PROPOSED No response If the PROPOSING vendor has resellers that will be selling for the vendor UNDER this contract, the vendor must downl oad the Resellers/Dealers spreadsheet from the attachment tab, fill in the requested information and upload the compl eted spreadsheet. DO NOT UPLOAD encrypted or password protected files. HUB Subcontracting Plan Form OPTIONAL No response Completion of the HUB Subcontracting Plan Form is OPTIONAL. THE FORM INFORMATION HAS NO EFFECT ON YO UR EVALUATION SCORE. IT IS INFORMATIONAL ONLY. Some Texas State agencies and Universities require it be a p art of the file when determining if they can use a TIPS contract. If you choose to complete one, it is not project specific but the general plan the vendor would use. Complete it as best you can. Vendor can download the HUB Subcontracting Plan Form from the "Attachments" tab and upload their HUB Subcontra cting Plan Form. D/M/WBE Certification OPTIONAL No response D/M/WBE Certification documentation may be scanned and uploaded if you desire to claim your status as one of the i dentified enterprises. (Disadvantaged Business Enterprise, Minority Business Enterprise and/or Woman Business Ent erprise) If vendor has more than one certification scan into one document. (PDF Format ONLY) DO NOT UPLOAD encrypted or password protected files. HUB Certification OPTIONAL No response HUB Certification documentation may be scanned and uploaded if you desire to document you status as a HUB compa ny. (Historically Underutilized Business) (PDF Format ONLY) DO NOT UPLOAD encrypted or password protected files. Warranty No response Warranty information (if applicable) must be scanned and uploaded. (PDF Format ONLY) DO NOT UPLOAD encrypted or password protected files. Supplementary No response Supplementary information may be scanned and uploaded. (Company information, brochures, catalogs, etc.) (PDF Fo rmat ONLY) DO NOT UPLOAD encrypted or password protected files. All Other Certificates No response All Other Certificates (if applicable) must be scanned and uploaded. If vendor has more than one other certification sc an into one document. (PDF Format ONLY) DO NOT UPLOAD encrypted or password protected files.

  • PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. CHANGES TO THE ORIGINAL LEARNING AGREEMENT The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • REQUIRED CONTENT FOR ARTICULATION 1. Career Assessments

  • Proposed Services A description of the Contractor’s proposed services to accomplish the specified work requirements, including dates of completion.

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

  • Technical Objections to Grievance No grievance will be defeated or denied by any minor technical objection.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process.

  • Technical Objections No grievance shall be defeated merely because of a technical error, other than time limitations in the processing of the grievance through the grievance procedure. To this end, an arbitrator shall have the power to waive formal procedural irregularities in the processing of the grievance in order to determine the real matter in dispute.

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