Component Systems Sample Clauses

Component Systems. Now that we have defined Basic Components and Blackbox Components, we can finally define components that have other components inside: a Compo- nent System can be viewed as one component but with an internal structure consisting of Blackbox Components. This recursive definition gives us the hierarchical structure we need for modeling component based applications. We use diagrams for Component Systems to show how components are used together, and to show what components need services from which other components. In Component System diagrams only components, their Ports, and their Component Interfaces and their connections are shown, using the makeProxy() startServ() receivePercept(percept) conferenceStart() sendMessage(line) ... conferenceGUI() addLine(line) ...
Sample 1
AutoNDA by SimpleDocs
Component Systems. PROD: Pensacola Part # (if applicable) Component Systems User Restriction* Quantity Type Support Level** 1 PSINT31 Station Alerting Interface 1 CDB XTP Total License Fee: $15,000.00 * If specified in the User/License Restriction field:
Sample 1
Component Systems. Additional Quantities of
Sample 1
Component Systems. Newly Licensed Component Systems Part # (if applicable) Component System User Restriction* Quantity Type Support level** 1 COG-DS7I-REPCS Infor EAM Enterprise Edition Advanced Reporting Consumer 55 CU XT Total License Fee: $25,780.00 *If specified in the User Restriction field: • CU = “Concurrent Users” allows access to the Component System up to the stated maximum number of individual concurrent users who are simultaneously logged on to the Component System at any given point in time, irrespective as to whether or not any such user is actually using resources related to the Component System. The Licensee agrees to assign to each Concurrent User a unique identification profile, it being agreed that to the extent Licensee uses generic user profiles as a means to access the Component System, each separate log-on accessing the Component System will be counted as a separate user. • NU = “Named Users” Allows access to the Component System up to the stated maximum number of individual named users, irrespective as to whether any such user is actively logged on to the Component Systems at a given point in time; The Licensee agrees to assign to each Named User a unique identification profile, it being agreed that to the extent Licensee uses generic user profiles as a means to access the Component System, each separate log-on accessing the Component System will be counted as a separate user. **Support Level: Infor Xtreme (“XT”) Support unless otherwise indicated. Descriptions of the Support levels can be found at xxxx://xxx.xxxxx.xxx/content/brochures/inforxtremesupportplanfeatures.pdf/. If Applicable, “XTP” = Infor Xtreme Premium (24x7) and “XTE”= Infor Xtreme Elite (24x7) Plus
Sample 1

Related to Component Systems

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • Implementation Services The Company and the Client have developed a plan for implementing the services to be provided hereunder, including with respect to the transition of responsibility for such services from the Client and its current administrator to the Company, which plan attached hereto as Schedule I (the “Implementation Plan”). The Company shall perform the services required to complete the Implementation Plan, as set forth therein (the “Implementation Services”). The Company and the Client shall comply with any applicable requirements agreed in the Implementation Plan.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

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

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