File Structure Sample Clauses

File Structure. The population of Data Flow files in different use cases is provided in the Online RGMA Data Flow Catalogue as different variations. • Files have been developed with consistent sets of data. This allows RGMA Data Flows to be made up of Data Groups so that changes can be limited to specific Data Groups, rather than being separately applied to each of the RGMA Data Flows. • The Data Groups are the records which are included in the RGMA Data Flow formats. The diagram below illustrates the file structure which consists of: o A header record o Transaction records (followed by a number of associated detail records) o A trailer record. Record Identifer Transaction type Record Identifer Header Transaction TRANSACTION Transaction Trailer Record RECORD Record Data Item Value Data Item Value Data Item Value Separator • Complete Data Groups are used in the definition of the records. The Data Groups include Data Items which, though not required as part of the minimum data, could be used to satisfy commercial arrangements, and to provide extra Data Items which can be populated for exception processing and updates. The use of standard Data Groups means any change can be applied once to the formats, and only the business rules need to be adjusted in the different uses thus minimising the impact of change. The overhead of RGMA Data Flows allowing for data which some organisations will not use, is minimised by having variable length fields and not using field separators which are in the standard set of characters. • Files have a core which can be used by all Market Participants. This allows Suppliers to change their MAM with minimal changes to their records and means of communication, while allowing for commercial additions to the core data resulting in Market Participants being able to provide tailored functionality. • The file will be as one stream of data with the defined codes providing delimiters between Data Items and Data Groups. Any spaces between data and delimiters will be significant. • There is no identified requirement for record sequence numbers, but record sequencing within a transaction is significant.
AutoNDA by SimpleDocs
File Structure. The Producing Party shall produce the following sets of files with 26 each production.

Related to File Structure

  • Governance Structure The Academy shall be organized and administered under the direction of the Academy Board and pursuant to the governance structure as set forth in its Bylaws. The Academy’s Board of Directors shall meet at least six times per fiscal year, unless another schedule is mutually agreed upon by the University President or Designee and the Academy.

  • Fee Structure In consideration of Consultant providing services, Municipality shall pay Consultant for Services performed in accordance with Exhibit A – List of Services and Fee Schedule.

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

  • Classification Structure All employees working under this Agreement shall be classified according to the skill based classification structure set out in Appendix A.

  • Corporate Structure The corporate structure, capital structure and other material debt instruments, material accounts and governing documents of the Borrowers and their Affiliates shall be acceptable to the Administrative Agent in its sole discretion.

  • Capital Structure (a) The entire authorized capital stock of Parent consists of 2,000,000,000 shares of common stock, par value $1.00 per share (the “Parent Common Stock”) and 1,500,000 shares of preferred stock, par value $1.00 per share (the “Parent Preferred Stock”). At the close of business on November 22, 2013, (i) 582,708,913 shares of Parent Common Stock were issued and outstanding, (ii) no shares of Parent Preferred Stock were issued and outstanding, (iii) 182,465,987 shares of Parent Common Stock were held by Parent in its treasury, (iv) 32,027,774 shares of Parent Common Stock were subject to options to purchase Parent Common Stock, (v) 23,955 shares of Parent Common Stock were subject to awards with respect to restricted Parent Common Stock, (vi) 2,911,298 shares of Parent Common Stock were subject to restricted stock unit awards with respect to Parent Common Stock) and (vii) 53,247,770 shares of Common Stock were reserved for issuance pursuant to future awards under benefit plans of Parent. No shares of Parent Common Stock are subject to or were issued in violation of the preemptive rights of any shareholder or any purchase option, call option, right of first refusal, subscription right or any similar right under any provision of the DGCL, the Organizational Documents of Parent or any agreement to which Parent is a party or otherwise bound. Except as set forth in this Section 4.2 and in Section 4.2 of the Parent Disclosure Letter, as of the date of this Agreement, there are no (i) issued and outstanding shares of capital stock of or other voting or equity interests in Parent, (ii) securities of Parent convertible into or exercisable or exchangeable for shares of capital stock of or other voting or equity interests in Parent, (iii) options, warrants or other rights or agreements to acquire from Parent, or other obligation of Parent to issue, deliver, transfer or sell, or cause to be issued, delivered, transferred or sold, any shares of capital stock of or other voting or equity interests in Parent or securities convertible into or exercisable or exchangeable for shares of capital stock of or other voting or equity interests in Parent, (iv) voting trusts, proxies or other similar agreements to which Parent or any of its Subsidiaries is a party or by which Parent or any of its Subsidiaries is bound with respect to the voting of any shares of capital stock of or other voting or equity interests in Parent or any of its Subsidiaries, (v) obligations restricting the transfer of, or requiring the registration for sale of, any shares of capital stock of or other voting or equity interests in Parent or any of its Subsidiaries, or (vi) outstanding or authorized appreciation rights, rights of first offer, performance shares, “phantom” stock rights or other agreements or obligations of any character (contingent or otherwise) pursuant to which any Person is or may be entitled to receive any payment or other value based on the revenues, earnings or financial performance, or stock price performance or other attribute of Parent or any of its Subsidiaries or any of their businesses or assets are calculated in accordance therewith (the items in clauses (i), (ii) and (iii) being referred to collectively as the “Parent Securities”). There are no outstanding obligations of Parent or any of its Subsidiaries to repurchase, redeem or otherwise acquire any Parent Securities. (b) All of the shares of Parent Common Stock are, and the shares of Parent Common Stock constituting the Per Share Common Stock Merger Consideration when issued will be, duly authorized, validly issued, fully paid and nonassessable and not subject to, or issued in violation of, any purchase option, call option, right of first refusal, preemptive right, subscription right or any similar right under any provision of the DGCL, the Organizational Documents of Parent, or any agreement to which Parent is a party or otherwise bound. Such shares have been issued in material compliance with all applicable state and federal Laws concerning the issuance of securities.

  • Structure a) The committee will meet as necessary at times determined by the Association and TEBA. b) The Association and TEBA shall each bear the cost of their participation in this committee. c) The Association and TEBA will each appoint three (3) representatives to the committee. d) The committee will be chaired jointly.

  • Group Structure 17.1 The Company does not have any Subsidiary nor has it at any time a member of or the beneficial owner of any shares, securities or other interest in any company or other person.

  • Organizational Structure The ISO will be governed by a ten (10) person unaffiliated Board of Directors, as per Article 5 herein. The day-to-day operation of the ISO will be managed by a President, who will serve as an ex-officio member of the ISO Board, in accordance with Article 5 herein. There shall be a Management Committee as per Article 7 herein, which shall report to the ISO Board, and shall be comprised of all Parties to the Agreement. There shall be at least two additional standing committees, the Operating Committee, as provided for in Article 8, and the Business Issues Committee, as provided for in Article 9, both of which shall report to the Management Committee. A Dispute Resolution Process will be established and administered by the ISO Board in accordance with Article 10.

  • Agreement Structure This Agreement includes Part 1 - General Terms, Part 2 - Country-unique Terms (if any), the LI, and the XxX and is the complete agreement between Licensee and Lenovo regarding the use of the Program. It replaces any prior oral or written communications between Licensee and Lenovo concerning Licensee’s use of the Program. The terms of Part 2 may replace or modify those of Part 1. To the extent of any conflict, the LI prevails over both Parts.

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