Functional Sample Clauses
Functional. ATOSS is prohibited from processing contract data beyond the scope of this Agreement. All processing for other purposes, in particular the unauthorized transfer of contract data to third parties, is not permitted. ATOSS is obligated to process the contract data of different customers separately.
Functional these include the specific core requirements for the design and performance of the Works.
Functional. 30.1 The Supplier guarantees that, once the Operational Guarantees Acceptance Certificate(s) has been issued, the System represents a complete, integrated solution to the Purchaser’s requirements set forth in the Technical Requirements and it conforms to all other aspects of the Contract. The Supplier acknowledges that GCC Clause 27 regarding Commissioning and Operational Acceptance governs how technical conformance of the System to the Contract requirements will be determined.
Functional. Functional support is defined as providing expertise to Buyer system users in answering questions related to how application software works. Functional support will be provided by Tyson to Buyer employees during the transition, conversion and post conversion support periods in a manner consistent with standard Tyson procedures. This will include help desk and phone support and research requests made by Buyer employees.
Functional. 1. Application must connect to and query the NWI Web Feature Service (WFS) to identify wetland features
2. Application must display wetland query results on a map
3. Application must connect to and query the NHD Web Feature Service (WFS) to identify stream features
4. Application must connect to and invoke a Web Processing Service (WPS) to perform intersection-based and proximity-based analysis of wetlands and streams
5. Application must display analysis results in tabular form and on a map
6. Application should provide the user the ability to select wetlands and streams from the map and display information about them
7. Application should allow the user to browse the wetland and stream features used in the analysis within a report detailing the results of the analysis
8. Application should allow the user to specify annotations on the map which are persisted with the report
Functional. IELPC will meet at mutually agreed upon intervals. Leadership of the LPAs will be determined by the local core partners. Updating the LPA will be completed in collaboration with all IELPC core partners as needed.
Functional. These changes are created as a result of the RIFTSOFT software user requests, including nonEND USER users. END USER may choose to implement these changes on a quarterly basis. END USER recognizes that failure to implement these types of changes over an extended period could increase the difficulty of code upgrade at a future date. All upgrades will be coordinated between the END USER POC and the SUPPLIER POC.
Functional. Project/Programme Management Client Orientation, Professionalism, and Communications
Functional. Leadership of the LPAs will be determined by the local core partners. The process for updating the LPA will be done based upon semiannual reviews.
Functional. Core partner contact information (Refer to Exhibit E for the SDLPA Core Partners) SDLPA will meet once per month for 1-2 hours. The core partners use emails in between meetings to work on document and process development. When the Community Partners become involved in the LPA, communication will be done by face-to-face meetings, emails, and phone calls. Leadership of the LPAs will be determined by the local core partners. Leadership efforts include: Presentations Discussions Q & A Sessions Email contacts Phone calls Efforts are made to ensure administrators from the various organizations are kept up to date and LPA efforts to ensure buy-in and organizational support.