Technical/ Functional Requirements Sample Clauses

Technical/ Functional Requirements. The Enterprise Management System must include the following key features and capabilities:  Data Capture: o Dynamic data capturing and management which does not have any data schema and design requirements “any data sets” o Manipulate all sources of data into standard normalised form on database o User definable nodes and periods for data capture at each target node or all 24x7 o Should have very lightweight collection agent not requiring any special privileges o Data agents for databases such as Oracle, Informix, SQL Server etc. o Data agents for services such as IIS, Exchange etc. o Data to be imported directly and automatically with dynamic changes to parameters o Add/change schemas to metrics database, change machine names & levels of data o Collect and report metrics from non-standard sources; generalised import o Easy installation and roll-out of new agents and control of licence mechanism o Multi-protocol support including SFTP for data collection  Monitoring: o Automatically collects any metric (technical data coming from the IT Infrastructure and Business data (i.e. forecast, budget etc.) o Collection and storing of monitored metrics, ability to set threshold values. o OS process data collection and workload characterizations (logical classification of work on a computer system). o Monitor System and Process-level performance as well as utilisations, space etc. o Measurement of the load of virtual machines o Monitoring of storage systems o Support of heterogeneous storage systems o At its lowest granularity a workload is based on a group of processes. Once created, workloads can be used for:  Report on application availability  Define alarms to monitor a specific process or application  Report usage by application, by user, or by any other characteristic  Model systems based on defined workloads o Ability to measure the load on physical host (hypervisor level) as well as for each virtual machine. o Administer capacity, throughput, space utilization, cache efficiency, power consumption, directory size, disk usage, file count, raid array status and temperature o Tool must be able to monitor multi-vendor storage infrastructure from a unified view  Root Cause Analysis: o Drill down (from alarms/events) to identify process/application that cause the resources spike(s) or contention o Root-cause identification & resolution that seamlessly takes you from symptoms to the details you need for diagnosis.
Sample 1
AutoNDA by SimpleDocs

Related to Technical/ Functional Requirements

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

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

  • Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.

  • Drug and Alcohol Testing – Safety-Sensitive Functions A. Employees required to have a Commercial Driver’s License (CDL) are subject to pre-employment, post-accident, random and reasonable suspicion testing in accordance with the U.S. Department of Transportation rules, Coast Guard Regulations (46 CFR Part 16) or the Federal Omnibus Transportation Employee Testing Act of 1991. The testing will be conducted in accordance with current Employer policy.

  • Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Contractor Work Hours and Safety Standards Contractor shall ensure compliance with all safety and hourly requirements for employees, in accordance with federal, state, and County safety and health regulations and laws.

Time is Money Join Law Insider Premium to draft better contracts faster.