System Capabilities Sample Clauses

System Capabilities. The system shall be capable of producing, scanning, printing, and tabulating ballots for elections with voter service centers and/or precinct polling locations for not less than 500,000 registered voters (active and inactive), not less than 500 precincts, 1-20 districts, 1-12 political parties, and 1-500 different ballot styles including as many as 100 ballot issues. In addition, the System must qualify for provisional certification by the Colorado Secretary of State.
View SourceView Similar (2)
System Capabilities. System Capabilities The E-Voting system will provide the capability for individuals to vote in local, state, and national elections securely from any pre-determined voting site. In addition, election administrators will be able to use the system to create election ballots, administer the election process and tally election results in a collaborative manner from any pre-determined election administration sites. The security level of the information contained within the E-Voting System application should be considered Top Secret, meaning access should be restricted to only those individuals who require it. The Principle of Least Privilege should be employed to determine all access levels for the system. In addition, the separation of the voter identification information from the ballot cast is essential to maintain any legally required anonymity of the voters.
View Source
System Capabilities i. The system should support RSA ID numbers or passport numbers as method of identification. ii. Interfaces to existing databases must be provided, which will allow for the routine update of the other systems, based on examinations passed e.g., PIT, Radworkers, etc. iii. Should a person fail his /her training, medical testing or security screening a predetermined number of time then they should be automatically barred on the system from further testing or applications for a period of 3 months or a duration set by Koeberg. iv. The required workflow processes as stipulated in the FFD procedure shall be integrated during the configuration and shall be implemented in the final version. v. Upon completion of training, a person may have actions taken against them, which must be reflected on the system. An interface to revoke training outside of the normal expiry date, and / or to blacklist a person, must be provided. When a person is blacklisted, they should not be allowed to re-apply for access to KNPS for a minimum period of one year. Certain categories of offences may result in a person being denied access permanently. The system shall make provision for both categories. Expiry dates should be able to be manually extended outside the calculated expiry dates. vi. Additional system requirements might be required once the configuration is been completed.
View Source
System Capabilities. Design and develop capabilities in the Medix System in accordance with Schedule I to enable the Medix System to send and receive data as described in Schedule I, and in addition:
View Source
System Capabilities. The Counties agree to maintain E9-1-1 systems with the following features and capabilities during the term of this Agreement:
View Source
System Capabilities. Ensure that LabCorp System will work properly with the functions as described in Schedule I and in addition: 5.6.1. Data Transmission. Utilize the appropriate technical standards for transmission of result data as defined in Schedule I.
View Source
System Capabilities. The BBU system shall be capable of providing 1400W peak load, with a minimum of 80% inverter efficiency, for at least 10 seconds. The BBU system shall be capable of providing 700W signal operation load for a minimum of 4 hours, and then switching to and providing 300W signal flash load for an additional 2 hours minimum, when batteries are fully charged. When the BBU system is running on battery power, the inverter/charger shall be capable of allowing the voltage at which the transition from normal operating load to flash mode occurs (usually 47.5V) to be selected by a user, via relay contacts and connection points on the front panel of the inverter/charger. The transfer time allowed, from disruption of normal utility line voltage to stabilized inverter line voltage from batteries, shall be less than 65 milliseconds. The same allowable transfer time shall also apply when switching from inverter line voltage to utility line voltage. The BBU system shall bypass utility line voltage whenever the utility line voltage is outside of the manufacturer’s default, or a user-programmed voltage range, ±2VAC. When the utility line power has been restored to a normal operating voltage for more than a user defined setting (default 30 seconds), the BBU system shall transfer from inverter line voltage to utility line voltage. The BBU system shall be equipped to prevent a malfunction feedback to the cabinet or from feeding back to the utility service. The BBU system shall be compatible with TS1, TS2 and Model 170/2070 controllers and cabinet components for full run-time operation. Unless the plans indicate otherwise, provide a BBU in an external battery cabinet. When indicated by the plans, provide a BBU system that can be shelf-mounted in NEMA TS-1 and TS-2 cabinets, or rack-mounted for Model 170/2070 332 cabinets. Provide a manual bypass that is capable of shelf mounting or that can be attached to the side of the signal cabinet. Provide interconnect cables that are no less than 10 ft. in length. Relay contact wiring for each set of NO/NC relay contact closure terminals shall be no less than 6 feet long and #18 AWG wire. Use manufacturer recommendations for size of wire for any cables lengths greater than 10 feet. The BBU system shall have lightning surge protection compliant with IEEE/ANSI C.62.41 latest edition and meeting all current UL1449 standards. Lightning surge protection shall be provided to the utility line voltage coming into the inverter/charger. The surge prot...
View Source
System Capabilities. Panasonic shall ensure that sufficient capacity is at all times maintained on its software, servers and/or network equipment and telecommunications facilities and services to enable any user to access the Hosted Services.
View Source
System Capabilities. Franchisee’s electronic data system shall be capable of capturing and reporting common data elements used within the IEMS.
View Source

Related to System Capabilities

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

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as all line-side and trunk-side facilities, plus the features, functions, and capabilities of the switch. The features, functions, and capabilities of the switch shall include the basic switching function of connecting lines to lines, lines to trunks, trunks to lines, and trunks to trunks. Local circuit switching includes all vertical features that the switch is capable of providing, including custom calling, custom local area signalling service features, and Centrex, as well as any technically feasible customized routing functions. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for ▇▇▇▇ when ▇▇▇▇: (1) serves an End User with four (4) or more voice-grade (DS0) equivalents or lines served by BellSouth in Zone 1 of one of the following MSAs: Atlanta, GA;

  • OPERATIONAL CAPABILITY Contractor represents and warrants, as previously certified in Contractor’s Bidder’s Certification, that Contractor has the operational and financial capability to perform the Contract.