BACKGROUND TO AND REASONS FOR THE PROPOSAL (a)Background to the Proposal Sample Clauses

BACKGROUND TO AND REASONS FOR THE PROPOSAL (a)Background to the Proposal. The Company was established in 1991 as a wholly owned subsidiary of Old WMI to assume substantially all of the waste management operations of Old WMI located outside North America. In April 1992, 20 per cent. of the issued share capital of the Company was offered for sale to the public in the form of Ordinary Shares and ADSs. The Ordinary Shares were admitted to the Official List of the London Stock Exchange and the ADSs were quoted on the NYSE. The purpose of the offering was to increase access to equity markets, raise the profile and status of the Company and enhance the potential to expand the business by utilising Ordinary Shares as consideration for the acquisition of additional businesses. Notwithstanding this offering, the Company remained under the control of Old WMI which, through its subsidiaries, continued to own approximately 80 per cent. of the issued Ordinary Shares and continued to influence the Company's strategic direction. Since the offering in 1992, the Company has not used Ordinary Shares to acquire additional businesses. Following the offering in 1992, the closing middle market price of the Ordinary Shares on the London Stock Exchange reached a peak of 790p on 16 November 1992. This compares to the average closing middle market price of the Ordinary Shares on the London Stock Exchange over the twelve months preceding the date of the announcement of the Proposal of 227p per share. The last date on which the price of the Ordinary Shares on the London Stock Exchange was equal to or greater than the amount available to Scheme Shareholders under the Scheme of 345p per Scheme Share was 19 July 1996.
AutoNDA by SimpleDocs

Related to BACKGROUND TO AND REASONS FOR THE PROPOSAL (a)Background to the Proposal

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Hiring Decisions Contractor shall make the final determination of whether an Economically Disadvantaged Individual referred by the System is "qualified" for the position.

  • Announcement Explanation School District Board Member Vacancy The School District is accepting applications to fill the vacancy resulting from [reason for vacancy] of [former Board member's name]. The contents of a vacancy announcement, how it is announced, and where it is posted are at the Board's sole discretion. The Board may want to announce the vacancy and its intent to fill it by appointment during an open meeting. The announcement may be posted on the District's website and in the local newspaper(s). The individual selected will serve on the School Board from the date of appointment to [date]. The length of the appointment depends upon when during the term of office the vacancy occurred. See 105 ILCS 5/10-10 and Board policy 2:70, Vacancies on the School Board - Filling Vacancies, to determine the length of the appointment. The School District [School District's philosophy or mission statement]. See Board policy 1:30, School District Philosophy, for the District's mission statement that is specific to the community's goals. Applicants for the Board vacancy must be: [Board's list of qualifications]. See checklist item titled Develop a list of qualifications for appointment of a person to fill the vacancy above. Applicants should show familiarity with the Board's policies regarding general duties and responsibilities of a Board and a Board member, including fiduciary responsibilities, conflict of interest, ethics and gift ban. The Board's policies are available at [locations]. Listing this along with the Board's list of qualifications assists candidates in understanding a Board member's duties and responsibilities and may facilitate a better conversation during the interview process. See Board policies: 2:20, Powers and Duties of the School Board; Indemnification; 2:80, Board Member Oath and Conduct; 2:100, Board Member Conflict of Interest; 2:105 Ethics and Gift Ban; and 2:120, Board Member Development. Applications may be obtained at [location and address and/or website] beginning on [date and time]. Completed applications may be turned in by [time and date] to [name and title of person receiving applications]. See action item titled Decide who will receive completed vacancy applications above. Publicize the vacancy announcement by placing it on the District's website, announcing it at a meeting, and/or advertising it in the local newspaper(s). Accept and review applications from prospective candidates (see Decide who will receive completed vacancy applications above). Contact appropriate applicants for interviews (see Decide who will receive completed vacancy applications above). Develop interview questions.

  • Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • ROAD WORK PHASE APPROVAL Purchaser shall obtain written approval from the Contract Administrator upon completion of each of the following phases of road work:  Drainage installation  Subgrade compaction  Rock compaction SUBSECTION RESTRICTIONS

  • Technical Advisory Committee (TAC The goal of this subtask is to create an advisory committee for this Agreement. The TAC should be composed of diverse professionals. The composition will vary depending on interest, availability, and need. TAC members will serve at the CAM’s discretion. The purpose of the TAC is to: • Provide guidance in project direction. The guidance may include scope and methodologies, timing, and coordination with other projects. The guidance may be based on: o Technical area expertise; o Knowledge of market applications; or o Linkages between the agreement work and other past, present, or future projects (both public and private sectors) that TAC members are aware of in a particular area. • Review products and provide recommendations for needed product adjustments, refinements, or enhancements. • Evaluate the tangible benefits of the project to the state of California, and provide recommendations as needed to enhance the benefits. • Provide recommendations regarding information dissemination, market pathways, or commercialization strategies relevant to the project products. The TAC may be composed of qualified professionals spanning the following types of disciplines: • Researchers knowledgeable about the project subject matter; • Members of trades that will apply the results of the project (e.g., designers, engineers, architects, contractors, and trade representatives); • Public interest market transformation implementers; • Product developers relevant to the project; • U.S. Department of Energy research managers, or experts from other federal or state agencies relevant to the project; • Public interest environmental groups; • Utility representatives; • Air district staff; and • Members of relevant technical society committees. The Recipient shall: • Prepare a List of Potential TAC Members that includes the names, companies, physical and electronic addresses, and phone numbers of potential members. The list will be discussed at the Kick-off meeting, and a schedule for recruiting members and holding the first TAC meeting will be developed. • Recruit TAC members. Ensure that each individual understands member obligations and the TAC meeting schedule developed in subtask 1.11. • Prepare a List of TAC Members once all TAC members have committed to serving on the TAC. • Submit Documentation of TAC Member Commitment (such as Letters of Acceptance) from each TAC member. Products: • List of Potential TAC Members • List of TAC Members • Documentation of TAC Member Commitment

  • SCOPE OF SERVICES/CASE HANDLING A. Upon execution by Xxxxxx, Attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client agrees that Xxxxxx may choose to associate additional law firm(s) and/or lawyer(s) to represent Client in connection with the investigation and prosecution of the rights Client has as a purchaser of publically traded securities of Xxxxxx, and Client understands that such representation shall be on the same terms as those described in this agreement.

  • HHS Single Audit Unit will notify Grantee to complete the Single Audit Determination Form If Grantee fails to complete the form within thirty (30) calendar days after receipt of notice, Grantee maybe subject to sanctions and remedies for non-compliance.

  • Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.

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