Functional Appropriateness Sample Clauses

Functional Appropriateness. The functional appropriateness has been tested through iterative test cases performed in 20 cycles and for a period of time of one week. Table 8 shows the results of this test process for selected functionalities offered so far from the NOMAD platform. For each test case, the relevant NOMAD platform use case is indicated, so that a connection of the test cases with the defined tasks and objectives (as per Table 1) and the current status of the platform (as per Table 3, Table 4 and Table 5) is realised. Load public domain models and navigate through their entities UC6 Success Create a new domain model in three languages UC7 Success Open an existing domain model in a specific language and browse through it UC7 Success Create a new domain entity and update the term in three languages UC8 Success Drag and drop an entity from a public domain model to the model under development UC8 Success Delete the structure of a domain entity and rebuild from scratch UC8 Success Load public domain and policy models and navigate through their contents UC12 Success Create a new policy model in three languages UC13 Success Open an existing policy model in a specific language and browse through it UC13 Success Create a new policy component and update the definition in three languages UC14 Success Drag and drop an entity from a public domain model to the model under development UC14 Success Delete the structure of a policy component and rebuild from scratch UC14 Success Drag and drop a policy component from a public policy model to the model under development UC14 Success Create a new argument, update the definition in three languages and specify polarity UC15 Success Drag and drop an argument from a policy component to another policy component of the same policy model UC15 Success Invoke word cloud for a domain model UC18 Success Invoke time analysis for a domain model UC19 Success Invoke word cloud for a policy model UC21 Success Invoke time analysis for a policy model UC22 Success

Related to Functional Appropriateness

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Technical and professional ability Selection criteria as stated in the procurement documents

  • Capabilities A. The Parties agree that the DRE must possess the legal, technical, and financial capacity to: (1) Accept and expend non-federal funds consistent with Section 4.2.4; (2) Accept transfer of the FERC license and title for the Facilities from PacifiCorp; (3) Seek and obtain necessary permits and other authorizations to implement Facilities Removal; (4) Enter into appropriate contracts and grant agreements for effectuating Facilities Removal; (5) Perform, directly or by oversight, Facilities Removal; (6) Prevent, mitigate, and respond to damages the DRE or any of its contractors, subcontractors, or assigns cause during the course of Facilities Removal, and, consistent with Applicable Law, respond to and defend associated liability claims against the DRE or any of its contractors, subcontractors, or assigns, including costs thereof and any judgments or awards resulting therefrom; (7) Carry the required insurance and bonding set forth in Appendix L to respond to liability and damages claims associated with Facilities Removal against the DRE or any of its contractors, subcontractors, or assigns; (8) Meet the deadlines set forth in Exhibit 4; and (9) Perform such other tasks as are reasonable and necessary for Facilities Removal. B. Before the DRE and PacifiCorp file the joint application to transfer the license for the Facilities, the DRE will Timely demonstrate to the reasonable satisfaction of the States and PacifiCorp that it possesses the legal, technical, and financial capacity to accomplish the tasks in Sections 7.1.2.A(1) through (5), (8), and (9). PacifiCorp and the States will consult if the DRE fails to make the demonstration required in this subsection. C. Within six months of the DRE’s execution of the Settlement, the DRE will include in an informational filing in the FERC license transfer proceeding proof that it possesses the legal, technical, and financial capacity to accomplish the tasks in Sections 7.1.2.A(6) and (7). This filing will include documentation that the DRE meets the requirements of Parts II, III, and IV of Appendix L and is capable of fulfilling its obligations under Section 7.1.3. The DRE will not provide the filing if either of the States or PacifiCorp objects to the filing after a reasonable opportunity to review before submission to FERC. The six-month deadline may be changed by agreement of the DRE, the States, and PacifiCorp. The Parties will Meet and Confer if the DRE fails to provide the informational filing to FERC.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union ▇▇▇▇▇▇▇, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.