Program Operation. The City normally conducts two blood donation drives per year, one in January and one in July. Donations are credited to the City of Oakland Club and are good for one year. Withdrawals are made from the account by submitting requests to the City Manager’s Office. City credits remaining at the end of one year are switched into the general Blood Bank Fund. However, by participation in the program, all blood needs of the City are covered, even if there are insufficient credits in the City Club account, without monetary charge or replacement requirement to the unit members during the term of this Agreement. The City and the Union agree to actively encourage unit members and dependents to participate in the blood donation drives.
Program Operation. Provide the necessary administrative, professional, and technical staff for operation of the program.
Program Operation. EDD shall administer this Agreement in accordance with the Federal Workforce Investment Act, Unemployment Insurance Code, and applicable federal and State regulations and directives.
Program Operation. The City normally conducts two blood donation drives per year, one in January and one in July. Donations are credited to the City of Oakland Club and are good for one year. Withdrawals are made from the account by submitting requests to the City Administrator’s Office. City credits remaining at the end of one year are switched into the general Blood Bank Fund. However, by participation in the program, all blood needs of the City are covered, even if there are insufficient credits in the City Club account, without monetary charge or replacement requirement to the represented employee during the term of this Agreement. The City and the CMEA agree to actively encourage represented employees and dependents to participate in the blood donation drives.
Program Operation. Programs must meet or exceed licensing standards. You agree to operate during hours reported in Exhibit 5 to the maximum extent possible.
Program Operation. As necessary, offer technical training to all program subcontractors covering the scope of work, including proper procedures and contract requirements. GRANTEE will also ascertain that all subcontractors comply with all program requirements, including but not limited to performing the required eligibility verifications and vehicle dismantling. GRANTEE will be responsible for payment to the vehicle dismantlers, buy- back facilities and the scrapped vehicle owners.
Program Operation. Federos warrants that the Programs, when used in accordance with the terms of this Agreement, will operate substantially as set forth in the accompanying Documentation for a period of ninety (90) days following Delivery.
Program Operation. SSC is responsible for the cost and operation of its programs. SSC is not eligible for City grant funds or subsidies for program operating expenses or tournaments held as part of a regular season. Notwithstanding, SSC may request special event funds for regional, state, or national tournaments held outside of SSC’s regular season. Requests for special event funding must follow the City’s application process.
Program Operation. A. Federally Approved Revisions or Changes to the Mitigation Rule. Federally approved changes and revisions to the Mitigation Rule shall not automatically require a modification of this Instrument. In the event that such changes/revisions are approved, the Sponsor shall submit, in writing, proposed procedures for implementing the approved revisions/changes, if necessary. The DE shall determine whether implementation of the revisions will require consultation with the IRT or notification of the public, in accordance with the requirement set forth in the revised Mitigation Rule, guidance provided by Corps Headquarters/U.S. Environmental Protection Agency (USEPA) and/or information contained in the approved, revised Mitigation Rule.
B. Interagency Review Team The Interagency Review Team (IRT) shall be governed by the Mitigation Rule [33 CFR 332.8(b)]. The IRT currently consists of representatives from the Corps, U.S. Fish and Wildlife Service (USFWS), USEPA, and Kentucky Division of Water (KDOW). The role of the IRT is to facilitate the establishment of third party mitigation through the development of mitigation banking or in-lieu fee instruments. The IRT serves in a consulting role to the Corps; however, the Corps retains full authority for approval of third party instruments used to satisfy compensatory mitigation requirements for DA permits.
Program Operation. The Executive Block assigns logical units and files, and controls the computational block(s) to be executed. These functions depend on reading in a at least four data lines which must be supplied according to the needs of a given computer run. These data lines are: (1) the interface file numbers, (2) the scratch file numbers, (3) the names of the various blocks called in the simulation run, and (4) $ENDPROGAM. The Executive Block assigns logical unit numbers to the interface and scratch files by reading the SW and MM data groups, respectively. The first line (denoted by SW in the first two columns) may contain up to 50 integer numbers, corresponding to 25 input and 25 output units. The maximum number of files open at any one time is eight (two interface files and six scratch files). These file limits should not exceed the realistic capability of most computer systems. Usually only two to six units will be needed for any single simulation. The output file is saved (during the run) for use by a subsequent computational block and is subsequently deleted, unless the file is saved permanently by using the ‘@’ function. The output files can be examined directly during the run by using the graphing and statistical capability of the Executive Block. The file assignments in the second data group (denoted as MM) are for scratch files, i.e., files that are generated and used during execution of the program, and erased at the end of the run. Again, there is provision for up to six such files, but only one or two are typically needed. The unit numbers of the interface and scratch files are stored in the labeled common COMMON/TAPES/ for use by all blocks. Scratch files are opened when a block is called and closed when control returns to the executive block. This was done to ensure that the Runoff Block does not erase valuable user data. The Runoff Block uses NSCRAT files for precipitation, evaporation, temperature, and wind speed input. Thus, the @ lines should be clustered within the data of a block. Multiple @ functions should be used when a scratch file has a different meaning from block to block. For example, NSCRAT(1) may be the rainfall input file in Runoff and be a true scratch file in Transport. An @ line should be used anywhere before the $TRANSPORT to open the file for Runoff. The file will be closed when Runoff finishes execution. A new file called FORT#, where # is the unit number assigned to NSCRAT(1) will then be opened when the Transport Block is called.