RATIONALE AND CODING OF THE REQUIREMENTS Sample Clauses

RATIONALE AND CODING OF THE REQUIREMENTS. ‌ The Safety user needs are here reported as specific and realistic User Requirements (UR), which can support the development phase of the project. In addition, SAFETY requirements are further subdivided in two sub-categories, including: - Capacity Requirement (CAP), defining what type of information the individual products shall deliver, including requests of performance; - Project Requirements (PRR), defining constraints imposed by the project or that the project has to follow considering the state of the art on the same topic. A specific coding scheme has been adopted to number uniquely the Safety user needs. This is a lesson learned from several other EU projects developed with similar purposes (e.g. Xxxxx, Lampre, etc.). Each single need is coded adopting the following labelling scheme: Where: - SAF identifies the SAFETY project (for compatibility with other similar projects); - UR identifies the SAFETY project the User Requirement (UR); - CAP defines the function of the requirement, including a Capacity Requirement (CAP) and a Project Requirement (PRR); - NUM is the progressive number of the requirement.
Sample 1
AutoNDA by SimpleDocs

Related to RATIONALE AND CODING OF THE REQUIREMENTS

  • Time Requirements The Independent Contractor will not be required to follow or establish a regular or daily work schedule, but shall devote during the term of this Agreement the time, energy and skill as necessary to perform the services of this engagement and shall, periodically or at any time upon the request of the Company, submit information as to the amount of time worked and scope of work performed.

  • Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Installation requirements We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • Credentialing Requirements Registry Operator, through the facilitation of the CZDA Provider, will request each user to provide it with information sufficient to correctly identify and locate the user. Such user information will include, without limitation, company name, contact name, address, telephone number, facsimile number, email address and IP address.

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Conference requirement and procedure (i) The Employer, or the Employer’s representative, shall, when requested by the Employees or their Employee Representative/ Union Delegate, confer (within a reasonable period of time which should not exceed 1/2 hour) for the purpose of determining whether or not conditions are inclement. (ii) Provided that if the Employer or the Employers’ representative refuses to confer within such reasonable period, Employees shall be entitled to cease work for the rest of the day and be paid inclement weather.

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