PROJECT DIALOG Sample Clauses

PROJECT DIALOG. In the project dialog (CW_PROJECT_DIALOG) the user can either select an existing project or create a new one. The dialog basically consists of two components, namely new_project_component and exist_project_component. The component for an existing project (CW_EXIST_PROJECT) asks the user for a path on a project file. The new project component (CW_NEW_PROJECT) needs a path pointing to a .NET assembly, a working directory, and a project name. Both components use text fields (CW_TEXT_FIELD) for entering text, and path fields (CW_PATH_FIELD) for entering text associated with a browse button. A click on this button opens a dialog for selecting a file respectively a directory, depending on the set state. The path field has a feature set_filter. It is only possible to browse for files that are specified in the filter, e.g. the filter "*.dll;*.exe" only allows to select files with a valid assembly extension. The query is_complete originally inherited from CW_DIALOG is true when the text fields belonging to a project component are filled out; which component depends on the user’s selection to create a new project or to open an existing one.
AutoNDA by SimpleDocs
PROJECT DIALOG. The following dialog asks you to open an existing project or to create a new project (see Figure 17). By default the section where you can open an existing project is enabled. You need to provide the path to a project file with the extension .cpr (contract project). You can either type it in the text field or use the “Browse” button, which opens an “open file” dialog. It is only possible to select a project file with the correct project extension.
PROJECT DIALOG. If you whish to create a new project, select the radio button with the label “Create a new project”. This section gets activated and you can choose the parameters of the new project. In the first text field you have to enter the full path to a .NET assembly. A click on the “Browse” button launches a file dialog where you can specify an assembly file in a more comfortable way. An assembly file has the extension .dll (dynamic link library) or .exe (executable). The filter in the dialog is set so that you can only select an assembly file with a valid extension. By default the working directory is “$CONTRACT\project”. The wizard stores the generated files in this directory. You can change it either by typing in the path to the desired directory or by choosing the directory from a dialog launched by pressing the “Browse” button. When you select an assembly and the field for the project name is empty, the wizard creates a project name for you. It has the same name as the assembly. Of course you can change this name just by replacing it with another one. The check box named “Overwrite a project with the same name” is by default selected. When you deselect it and it has already a project file with the same name in the specified directory the wizard brings up a dialog as shown in Figure 18.

Related to PROJECT DIALOG

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Project Team To accomplish Owner’s objectives, Owner intends to employ a team concept in connection with the construction of the Project. The basic roles and general responsibilities of team members are set forth in general terms below but are more fully set forth in the Design Professional Contract with respect to the Design Professional, in the Program Management Agreement with any Program Manager, and in this Contract with respect to the Contractor.

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Contractor’s Project Manager 7.2.1 The Contractor’s Project Manager is designated in Exhibit F (Contractor’s Administration). The Contractor shall notify the County in writing of any change in the name or address of the Contractor’s Project Manager. 7.2.2 The Contractor’s Project Manager shall be responsible for the Contractor’s day-to-day activities as related to this Contract and shall meet and coordinate with County’s Project Manager and County’s Contract Project Monitor on a regular basis.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • Project Personnel It is understood and agreed that the Project Director identified at Item 3, Page One of this Agreement shall be responsible for the overall supervision and conduct of the Work on behalf of the Contractor and that the persons described in the Statement of Work shall serve in the capacities described therein. Any change of Project Director by the Contractor shall be subject to the prior written approval of NYSERDA. Such approval shall not be unreasonably withheld, and, in the event that notice of approval or disapproval is not received by the Contractor within thirty (30) days after receipt of request for approval by NYSERDA, the requested change in Project Director shall be considered approved. In the event that NYSERDA requires additional time for considering approval, NYSERDA shall notify the Contractor within thirty (30) days of receipt of the request for approval that additional time is required and shall specify the additional amount of time necessary up to thirty (30) days.

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