Task Descriptions. Pre-show:
Task Descriptions. Principal Senior Program Manager Task Manager Senior Engineer Project Engineer Design Engineer Engineer‐In‐ Training Senior Engineer Tech Engineer Tech Admin / Clerical Senior Project Controls Total SA04 Hours Total Cost 160 FUNCTION CODE 160 ‐ ROADWAY DESIGN 160.C C. Roadway Design Controls 160.C.1 1. Geometric Design. 160.C.2 2. Roadway Design.
Task Descriptions. Principal Senior Program Manager Task Manager Senior Engineer Project Engineer Design Engineer Engineer‐In‐ Training Senior Engineer Tech Engineer Tech Admin / Clerical Senior Project Controls Total SA04 Hours Total Cost 160.C.10 10.
Task Descriptions. Principal Senior Program Manager Task Manager Senior Engineer Project Engineer Design Engineer Engineer‐In‐ Training Senior Engineer Tech Engineer Tech Admin / Clerical Senior Project Controls Total SA04 Hours Total Cost 160.E.4.a.v v. Plan sheets (1 sheet) 0 000.X.0.x.xx vi. Notes for plan layout 160.E.4.a.vii vii. Wiring Diagram sheet (1 sheet) 0 160.E.4.a.viii viii. Quantity and Phasing sheets 0 160.E.4.a.ix ix. Construction Detail sheets 0 160.E.4.a a. Remove Xxxxxxxx Xx Traffic Signal adjustment 0 160.F F. Miscellaneous (Roadway)
Task Descriptions. Task #1: Serve as a Member of the Board of Directors of eSoft. Task #2: Formulate, in conjunction with eSoft personnel, a Strategic Partner Offer Package and Prospect List . The Prospect List is to be comprised of applicable firms who are candidates to resell and/or license eSoft products, and the Offer Package is to contain:
Task Descriptions. The Contractor shall perform all the tasks necessary for the implementation of the Alphasat satellite and fulfilment of the proposed mission in a timely and cost-effective manner. Tasks identified below are neither exclusive nor exhaustive. The Contractor shall make maximum use of the activities performed in the frame of the Alphabus development, including adoption of supporting specifications, use of system and engineering analyses (and associated models) and exploitation of unit, subsystem and system test results and facilities (including ATB, ETB, STB, MMST, and PFM) as appropriate.
Task Descriptions. The Engineer shall categorize each task performed to correspond with the following Task Numbers and descriptions. Xxxxxxx, Xxxxxxxx, & Xxxxxxxx, Inc. has been requested and given notice to proceed on June 9, 2021 at scoping meeting to provide a detailed 45% Plans, Specification, and Estimate (PS&E) for Phase 2 of the Southeast Loop. Supplemental #1 was to continue the effort and scope needed to advance the 45% PS&E to final construction documents. Supplemental #2 adds Project Management effort past the original design effort to change project limits (tie into FM 3349 project north of Boggy Creek), incorporate QL X XUE not available prior to the 100% Submittal, missinx XOE to complete the PS&E, for environmental services and supporting ROW exhibit requests. The supplemental adds additional effort for Submittal of an Approved Jurisdictional Determination, Submittal of Nationwide Permit and Historic Resources Coordination. Finally, the supplemental is needed to allow for design coordination, alternatives analysis and design revisions based on QL X XUE and coordination with utility companies to address utility conflicts, to reduce Waters of the U.S. impacts, and to support ongoing ROW acquisition efforts.
Task Descriptions. The achievement of results gets confirmed through two steps according to verification protocols of the Program. Firstly, by checking their completeness/compliance of the gross data against the requirements given in Dossier/Report for particular DLI. Secondly, by conducting field verification of the results achieved through an agreed method of verification between LGED and Association. The first step is generally known as Desk Review, where sampling will be 100%. The second step is generally called as field verification, where sampling will be as per mandated in the verification protocols and adjust the reported results accordingly. The final step is preparing reports on actual results achieved and providing constructive feedbacks to the IMED. The scope of works under the terms of reference will be, but not limited to, the followings:
Task Descriptions. The delivery/performance of work under this agreement will be authorized by CPCCo through fully executed Contract Releases. Each release will have a Statement of Work, specific to that release, that may contain requirements beyond those specified herein and will be priced in accordance with Part II, Section 2.2 Basic Ordering Agreement. Funding commitments under this agreement are created solely through issuance and award of Contract Releases for the services specified. The types of work contemplated for award under this agreement include, but are not limited to: • Conduit Reroute • Water Truck Needs • Pump and Treat • Stabilization System Installation • Drilling Support • Elevator Modifications • Fire Line Relocation • Electrical Work • Teamster Support • Site Clearing & Grading • Repairs There is no minimum or maximum amount of funding or work awarded or guaranteed by issuance of this Basic Ordering Agreement.
Task Descriptions. The tasks in this workpackage map directly to the various health and environment applications, and as such do not strongly depend on each other, so there is no temporal sequencing of tasks. However, at the technology level, tasks will frequently interact and cross-fertilise. In order to drive and to utilise the technology workpackages in a consistent and coherent manner, co-ordination will be needed. All tasks run for the entire duration of the project. Four of the tasks aim at the CrossGrid-embedding of applications, the fifth one is responsible for the overall management of the workpackage and the coherence within and between the tasks. Task leader: Xxxxx X.X. Sloot, UvA (CR5) This task will be responsible for the co-ordination between the tasks and the coherence in their interaction with the other workpackages in the project. In order to monitor the progress of each task in this workpackage, and to mutually exchange results, the task leaders will be required to submit a formal report to the WP management twice a year. WP co-ordination meetings will be held with the same frequency. During various phases of the project and the development of the applications, activities will be undertaken to ensure coherency between the various tasks, genericity of the adopted solutions and a focussed collaboration on common issues such as the application deployment on the grid. In the first phase of the project, the definition of common and coherent detailed requirements to WP 2 and WP 3 is one of the prime objectives of this WP. As part of the kick-off meeting a one-day workshop on the applications will be organised, specifically aimed at identifying common interests. After that, beside the WP co-ordination meetings, technical meetings will be organised to further identify and discuss common requirements between tasks and to come to a coherent first deliverable for the tasks. Further workshops will be held at least semi-annually. Identified common interests and requirements will be followed up. If deemed effective, further collaborations between the tasks will be initiated. Working groups of experts from each task will be assembled to monitor and guide the parallel developments within the tasks. These issues will include, but will not be limited to, implementation of the testbeds, and application deployment on the grid, adoption of technology developed in the other CrossGrid workpackages and outside the project. In this way it will be ensured that to the maximum extent ...
