System Outcomes Sample Clauses

System Outcomes. System outcomes can differ in terms of types and visualization. Three primitive data types have been defined in 3.3.1.16 (showData): Text (T), Num- ber (N), List (L [Text+Number]). Others and more structured types can be added to fulfill all system requests. The visualization is another issue to face. The same number, for instance, can be rep- resented inside a textbox, a spinner or using a progress bar or a pie diagram. For the sake of generality and not knowing exactly the boundaries of the system, in this paragraph is proposed a solution that can deal with the most of situations. Case 1 – Text A text can be displayed in: 1) a label;
AutoNDA by SimpleDocs

Related to System Outcomes

  • Outcomes Secondary: Career pathway students will: have career goals designated on SEOP, earn concurrent college credit while in high school, achieve a state competency certificate and while completing high school graduation requirements.

  • 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 Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • SYSTEM OPERATION The Parties shall adhere to any applicable operational requirements of PJM necessary to protect the integrity of the transmission system within the PJM Control Area and the transmission systems of interconnected control areas, and shall satisfy any and all PJM, RFC and NERC criteria, when applicable. The DS Supplier shall also adhere to any applicable operational requirements of the Company necessary to protect the integrity of the Company’s local distribution system.

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

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”).

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Internet Connectivity School must provide sufficient hardline internet connectivity and the required network configurations (provided in Exhibit A) for each Pixellot System to allow live broadcasts. PlayOn will provide the point-to-point wireless internet base station (“Point to Point”) when needed to deliver hardline internet connectivity to Pixellot Systems installed in outdoor venues; provided that PlayOn is able to select the make and model of the Point to Point system. In the event that School requests, or requires, a specific Point to Point system that is different from what is provided by PlayOn, then School must provide and install the Point to Point system at its own expense.

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