Requirements Gathering Sample Clauses

Requirements Gathering. Parties Involved: EGI-InSPIRE NA3 (Xxxxx Xxxxxx, XXX.xx); MAPPER WP4 (UCL)
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Requirements Gathering. This phase of the project involves cooperation between Genuity/GNI and GTE and addresses the following questions: . What business problems the product in mind is supposed to solve? . Is a central global alarm repository a requirement? . Level of PM and FM data correlation? . How long does the data warehouse needs to keep information in history? . What are the requirements for data granularity? . Report types and categories. . OLAP capability requirements. . Data visualization capability requirements. . Data warehousing performance requirements. . Availability and scalability requirements . Etc. SOW - GNI Intelligent Reporting and Analysis --------------------------------------------------------------------------------
Sample 1
Requirements Gathering. OpenGov will ● Provide a three-day (3-day) onsite requirement gathering workshop to increase our understanding of your business and functional goals. Through workshops and interviews, OpenGov will identify best fit scenarios for OMS and provide a brief including any challenges as well as recommendations for OMS best practices relevant to your implementation. OpenGov will: ● Provide configuration services, including: o Up to ten (10) custom fields and up to two (2) custom layouts per asset type listed in the Assets section below o Up to thirty (30) custom fields and up to ten (10) custom layouts to be utilized in any of the shared areas of the system, such as Tasks o Up to twenty (20) automations o Up to twenty (20) preventative maintenance plans OpenGov will: ● Provide remote train-the-trainer training, up to two (2) hours, on overall system navigation and functionality to help familiarize your staff with the software environment and its common functions. Training topics include: o Dashboards o Standard KPI/ROI Xxxxxxx o Logins/Permission o Layers o Filters o Maps o Grids o System Navigation o Views (List & Detail) o Standard Reports o Attachments o Requests, Work, Assets, Resources, Reports, and Administrator Tabs ● Provide remote train-the-trainer training, up to one (1) hour, for an overview of Preventative Maintenance Plans. ● Provide remote train-the-trainer training, up to one (1) hour, for an overview of Asset Condition Manager and Advanced Inspections. ● Provide remote train-the-trainer training, up to two (2) hours, for an overview of Reporting. ● Provide remote train-the-trainer training, up to two (2) hours, on OMS Esri integration functionality. Training topics include: o OMS Esri integration configuration options o Integration functionality (basemap and feature) o Overall Esri integration requirements, considerations, and OpenGov recommended best practices ● Provide a three-day (3-day) onsite "train-the-trainer" training event. The training agenda will be defined and agreed upon by both OpenGov and your project manager. To avoid redundancy, and to utilize service time efficiently, training may cover a subset of the assets listed in the Asset section of the scope. Topics may include any of the following: o Request Management: ▪ Requests ▪ Requesters ▪ Task Creation from Requests ▪ Issue library (including settings such as Applies to Asset and Non-Location) ▪ OpenGov recommended best practices for Request and Requester Management o Work Manageme...
Sample 1
Requirements Gathering. Image Maintenance
Sample 1
Requirements Gathering. Conducting meetings with stakeholders to gather detailed requirements and specifications for the custom software solution.
Sample 1
Requirements Gathering. After completing the business process redesign, a collaborative requirement gathering workgroup session will be held to define functional system requirements for the development and implementation of a telemedicine system. The requirements gathered from the workgroup will be used as an input to the request for proposal in the identification of a telemedicine vendor.'
Sample 1
Requirements Gathering. A key element of user-centred approaches to system design is the gathering and analysis of user requirements, and incorporation of these as primary inputs into the functional specification of the system. Requirements gathering exercises are concerned with studying and engaging with potential users of the proposed system as a means of identifying:  Current activities and behaviours – what users do and how they do it  Perceived needs – what users know they want  New affordances – options suggested to users that they may not yet have thought of, due to lack of knowledge about what might be possible The first two areas provide information about the status quo and can be ascertained to some degree prior to the development of any prototypes of the new system. The requirements generated in this way are invaluable in understanding the context in which people will be using the system and some of the challenges faced by users that are not currently addressed by existing systems. These requirements will most likely address the core functionality, around which novel aspects of the system will be built. The third level of user requirements addresses new opportunities, and these requirements are often generated once a working prototype has been produced. Ideas for the prototype may therefore be somewhat exploratory, developed from knowledge of what is technically possible or from ideas around novel approaches to user problems. The prototype is then used as a means of testing whether these new developments are viable and/or desirable. Feedback from users who interact with the prototype is then used to validate, refine and prioritise the requirements for the novel elements of the system. For the PATHS project, we intend to gather requirements in all three of these areas, with the first two documented in this report, and the latter incorporated into later stages of the project and reported in due course, along with refinements of the system following testing and evaluation of each of our two prototypes. It is of course also imperative that these requirements are attributed to clearly defined user profiles, and these will also be developed as part of the overall requirements gathering activity. Engagement with users for requirements gathering can involve a number of different techniques, which are selected according to the nature of the system being developed, and within the limits of constraints such as access to users, the experience and skills of the project team, ava...
Sample 1
AutoNDA by SimpleDocs
Requirements Gathering a. Define total e-Commerce business model for the Hardware Industry b. Execute usability study with customers (50-100 retailers): likes, dislikes, concerns c. Execute usability study with manufacturers (10-20): likes, dislikes, concerns d. Target list of software vendor candidates
Sample 1

Related to Requirements Gathering

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Personnel Requirements a. The CONTRACTOR shall secure, at the CONTRACTOR'S own expense, all personnel required to perform this Contract. b. The CONTRACTOR shall ensure that the CONTRACTOR'S employees or agents are experienced and fully qualified to engage in the activities and perform the services required under this Contract, and that all applicable licensing and operating requirements imposed or required under federal, state, or county law, and all applicable accreditation and other standards of quality generally accepted in the field of the activities of such employees and agents are complied with and satisfied.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

  • COMPLIANCE WITH LICENSING REQUIREMENTS CONTRACTOR shall comply with all necessary licensing requirements and shall obtain appropriate licenses and display the same in a location that is reasonably conspicuous, as well as file copies of same with the County Executive Office.

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

  • 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.

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