Throughput Requirements Sample Clauses

Throughput Requirements. The first anticipated customer segment for the Blockchain is California solar installations, but it is anticipated that the Blockchain’s addressable market will expand to encompass all devices that draw a significant amount of power as these devices could all be potentially incorporated into demand/response systems. Such devices include electric vehicles, thermostats, HVAC systems, and large screen electronics. The size of this device category is expected to be in the billions per year. This growth in addressable market over time implies the blockchain need only process less than 1 transaction per second at first to address solar installations but be able to grow to hundreds of transactions per second when the market expands to other types of distributed energy resource devices. Latency measures how quickly a transaction can be finalized after the transaction is submitted to be processed by the system. Some separate the concept of latency into two measurements: latency, the time it takes to put a transaction on a blockchain, and finality, the time the transaction requester must wait to be sure the transaction has been accepted (e.g.- in Bitcoin, the chain that contains the transaction is the one that miners choose to use going forward). They will be treated the same because the present document’s main use case requires finality. The Blockchain’s use case with perhaps the highest sensitivity to latency is key provisioning. Often keys are provisioned on the manufacturing floor which does not lend much time to wait for a transaction to be processed. However, if transactions can be batched together and be decoupled from the manufacturing synchronization this could reduce latency requirements. Therefore, the present document does not mention a latency requirement The following sections will provide details of the different actors involved, as well as further breakdown into individual use cases and activities.
Sample 1Sample 2
AutoNDA by SimpleDocs
Throughput Requirements. 28 5.11.1. RETURN TO APPLICATION (RTA) FOR BASIC AND WORKGROUP ........... 28 5.11.2. CHECK TO START PRINT .......................................... 29 5.11.3. PRINTING TIME ................................................. 29
Sample 1
Throughput Requirements. The time to process a job is a function of a number of parameters including whether background of foreground printing is used, complexity of the print job (print quality, number of passes, color settings), load on the network, the CPU (internal HD, amount of RAM, processor), and I/O channel. Three fundamental time metrics are to be used in measuring performance: o Return to application (RTA) o Click to Start printing o Printing o Click to Clunk (just add click to start and printing times). Return to Application (RTA) for Basic and WorkGroup RTA is defined here as the time from starting the printing process (click) to when the host is ready to continue normal working with application (no noticeable performance degradation due to printing process). The generic goal for RTA time equals 10% of the total printing time (click to start plus printing time). This will apply to Eiffel plot suite provided by HP. HP understands that actual RTA time highly depends on specific plot and RIPping computer performance, so a plot suite with specific RTA times defined for each plot will be provided by HP. Reduced RTA is one of the main differentiators of the WG Solution versus the Basic one. This is achieved thanks to the server based architecture where the ripping of the print if performed OEM SOFTWARE DEVELOPMENT AND LICENSE AGREEMENT No 12/00 on the server and so the client workstation is not loaded. This is because in terms of RTA shall be defined two different goals, one for the typical configuration where the client is running on a different workstation than the server, and another where client is running on the same workstation as the server. RTA: client on different workstation than server Under this configuration the Ripping is not done on the client workstation. The WG solution shall provide a RTA for the client which is equivalent to the RTA there would be if instead of a SW RIP, an embedded PS printer was connected to the client. The goal for Eiffel is to obtain same RTA values as DesignJet 1055 when using the PostScript driver (running on same workstation). ICD will provide target numbers for the different plots included in the Eiffel plot suite. RTA: client on same workstation than server
Sample 1
Throughput Requirements. The time to process a job is a function of a number of parameters including whether background of foreground printing is used, complexity of the print job, load on the network, and I/O channel. Under similar conditions the DRIP is expected to process a job according to the following target times. Three fundamental time metrics are to be used in measuring performance: Return to application (RTA) Click to Start printing Printing Click to Clunk Some orientation of the goals for Printing Time for a D-size media is below, but real values are going to be defined according to a throughput test to run at the HP site: Image QA CAD Fast 150x150, coated media ? 1.47 minutes Best 600x600, coated media 21.57 minutes 9.30 minutes Best 600x600, glossy media 21.57 minutes Table 3: Throughput goals
Sample 1
Throughput Requirements. 40 13.3. COLOR PERFORMANCE GOALS .................................................. 41 13.3.1. Color Accuracy vs. Target ........................................ 42 13.3.2 Color Consistency ................................................ 42 14. Licensing restrictions ......................................................... 42 14.1. DEVICE MODEL CHECK LICENSING ............................................. 42 14.2. JAPANESE FONTS LICENSING ................................................. 43
Sample 1
Throughput Requirements. The time to process a job is a function of a number of parameters including whether background of foreground printing is used, complexity of the print job (print quality, number of passes, color settings), load on the network, the CPU (internal HD, amount of RAM, processor), and I/O channel. The following fundamental time metrics are to be used in measuring performance: o Return to application (RTA) o Click to Start printing o Mechanical printing time o Click to Clunk (just add click to start and printing times). Return to Application (RTA) RTA is defined here as the time from starting the printing process (click) to when the host is ready to continue normal working with application (no noticeable performance degradation due to printing process). The generic goal for RTA time equals 10% of the total printing time (click to start plus printing time). -------------------------------------------------------------------------------- HP InkJet Commercial Division Monday, December 10, 2001 HP SW RIP External Reference Specification [hp logo] -------------------------------------------------------------------------------- HP understands that actual RTA time highly depends on specific plot and RIPping computer performance, so a plot suite with specific RTA times defined for each plot will be provided by HP. Reduced RTA is one of the main differences of the HP SW RIP solution when the RIP is running in the same workstation than the graphics application, compared to the separated scenario (client/server): in the case of 2 different workstations (client and server) the ripping of the job if performed on the server and so the client workstation is not heavy loaded. So, RTA goals shall be defined for both: the typical configuration where the client is running on a different workstation than the server, and the standalone ones. Click to Start printing This is the time since the starting of the printing process (i.e., the users clicks on "print" in the application) to the moment the printer effectively starts to print. Same requirements than RTA. Mechanical printing time Once the RIP starts sending rendered data to the printer device engine, a minimum-rendering throughput shall be guaranteed in order to avoid printing stopping in between swaths (which can produce image quality problems). HP will provide additional information with the required rendering throughput (Kbytes/s) for each particular media/print quality combination. The compression algorithm to be applied to t...
Sample 1
Throughput Requirements. The OC ABI System throughput requirements cover all three classes of workflows. Contractor shall ensure the OC ABI System performs with the minimum requirements below: Type of Transaction Number of Transactions Criminal TP-TP 482 Other TP-TP 32 ID Slaps-TP 16 TP-LT 482 KP-PLT 385 LT-TP 97 PLT-KP 39 LT-LT 97 PLT-PLT 39 Tactical TP-TP (2+ Fingers) 680 Tactical DNS TP-TP (5+flat fingers) 482 The Throughput requirements are for concurrent ingest and processing of identification, forensic, and tactical Transactions. The average and peak rates are shown below. The Peak rates are expressed as a percentage of the number of transactions above. The Peak Hour will be made up of these peak periods and the rest of that Peak Hour will consist of average loads – for instance the Peak Hour will have a load of a peak 30 minutes worth of Criminal TP-TP and 30 minutes of the average Criminal TP-TP. Transaction Type Duration of Peak Period % of Average Daily Rate Criminal TP-TP 30 minutes 10% Other TP-TP 1 hour 20% ID Slaps-TP 30 minutes 10% Tactical TP-TP 5 minutes 2% TP-LT 30 minutes 20% KP-PLT 1 hour 20% LT-TP (100% penetration) 30 minutes 10% LT-LT (100% penetration) 30 minutes 10% PLT-KP (100% penetration) 30 minutes 10% PLT-PLT (100% penetration) 30 minutes 10%
Sample 1
AutoNDA by SimpleDocs
Throughput Requirements. The volume of data traffic consumed by the 5G and beyond 5G (B5G) use-cases, services and applications is expected to significantly grow in comparison to today’s 4G/LTE generation. A factor of approximately 5-10× is foreseen. The experienced 5G user data rate depends on the targeted application/use case, and ranges from few kbps in case of massive Internet of Things to hundreds of Mbps (up to a peak of several Gbps) in case of broadband access in dense urban areas and indoors [3]. These consumers’ performance requirements should be also reflected and supported in access and transport networks. Evolving from 4G/LTE to 5G network architecture, the main change is that the original single-node baseband functions in 4G/LTE are split between Central Unit (CU), Distributed Unit(s) (DU) and Radio Unit(s) (RU) resulting in a so-called centralized network architecture with functional split (Figure 1). This flexible and efficient architecture can deliver the different service requirements of a wide range of expected 5G use cases and applications [4].
Sample 1
Throughput Requirements. A. Image/Demographic Data Capture Time The uninterrupted start to finish time required for a trained live scan device operator to capture the rolled and plain impression fingerprint image data and to record demographic information must be, on average, no more than ten minutes per transaction. This time requirement excludes the printing process.
Sample 1

Related to Throughput Requirements

  • Minimum Purchase Requirements Distributor shall make the minimum annual purchase of Products established in Exhibit B, unless the Agreement has become coexclusive. In the period within the fixed term and extension, if applicable, of the Agreement under Section 10(a) subsequent to [ * ], the parties shall meet in San Francisco at least [ * ] prior to the beginning of each of respective year to discuss market conditions and appropriate minimum purchases for such year. In the event that the parties fail to agree on an appropriate minimum any year subsequent to [ * ], the minimum annual purchase requirement for such year shall be calculated increasing or decreasing (as the case may be) the minimum purchase requirement for the preceding year in proportion to the increase or decrease in the [ * ] (based on data from mutually acceptable data provider) of the applicable product in the Territory. In the event Supplier is unable to deliver Products ordered by Distributor in an amount consistent with the most recent forecast, then the minimum annual purchase requirement shall be reduced by the quantity of Products that Supplier is unable to deliver when requested. In the event Distributor fails in any year (a “Shortfall Year”) to make the annual minimum purchase of Agreement Products required by Exhibit B, Supplier shall have the right to give Distributor written notice of default, and if such failure to make the minimum purchase is not cured (through the purchase of an amount of Agreement Product equal to the entire shortfall in the Shortfall Year, which amount shall not be counted towards any minimum purchase requirements for the year of purchase) within [ * ] of receipt of the notice, then Supplier shall have the right, in Supplier’s sole discretion and as Supplier’s sole remedy for Distributor’s failure to meet the minimum purchase requirements hereunder, either to convert the appointment of Distributor from exclusive to non-exclusive or to terminate this Agreement. In the event of either conversion to non-exclusive or termination of this Agreement pursuant to this Section 3(e), the Supplier shall pay Distributor a conversion fee equal to [ * ], and Distributor shall transfer all Regulatory Approvals relating to BMS or DES in the Territory to Supplier.

  • Payment Requirements ‌ If funding levels are significantly affected by state or federal budget and funds are not allocated and available for the continuance of the function performed by Subrecipient, the Contract may be terminated by the County at the end of the period for which funds are available. The County shall notify Subrecipient at the earliest possible time of any service, which will or may be affected by a shortage of funds. No penalty shall accrue to the County in the event this provision is exercised and the County shall not be obligated nor liable for any damages as a result of termination under this provision of this Contract, and nothing herein shall be construed as obligating the County to expend or as involving the County in any Contract or other obligation for future payment of money in excess of appropriations authorized by law.

  • Minimum Requirements Consultant shall, at its expense, procure and maintain for the duration of the Agreement insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the Agreement by the Consultant, its agents, representatives, employees or subconsultants. Consultant shall also require all of its subconsultants to procure and maintain the same insurance for the duration of the Agreement. Such insurance shall meet at least the following minimum levels of coverage:

  • LESSEE'S COMPLIANCE WITH REQUIREMENTS Lessee shall, at Lessee's sole cost and expense, fully, diligently and in a timely manner, comply with all "Applicable Requirements," which term is used in this Lease to mean all laws, rules, regulations, ordinances, directives, covenants, easements and restrictions of record, permits, the requirements of any applicable fire insurance underwriter or rating bureau, and the recommendations of Lessor's engineers and/or consultants, relating in any manner to the Premises (including but not limited to matters pertaining to (i) industrial hygiene, (ii) environmental conditions on, in, under or about the Premises, including soil and groundwater conditions, and (iii) the use, generation, manufacture, production, installation, maintenance, removal, transportation, storage, spill, or release of any Hazardous Substance), now in effect or which may hereafter come into effect. Lessee shall, within five (5) days after receipt of Lessor's written request, provide Lessor with copies of all documents and information, including but not limited to permits, registrations, manifests, applications, reports and certificates, evidencing Lessee's compliance with any Applicable Requirements specified by Lessor, and shall immediately upon receipt, notify Lessor in writing (with copies of any documents involved) of any threatened or actual claim, notice, citation, warning, complaint or report pertaining to or involving failure by Lessee or the Premises to comply with any Applicable Requirements.

  • Amendment Requirements (a) Notwithstanding the provisions of Sections 13.1 and 13.2, no provision of this Agreement that establishes a percentage of Outstanding Units (including Units deemed owned by the General Partner) required to take any action shall be amended, altered, changed, repealed or rescinded in any respect that would have the effect of reducing such voting percentage unless such amendment is approved by the written consent or the affirmative vote of holders of Outstanding Units whose aggregate Outstanding Units constitute not less than the voting requirement sought to be reduced.

  • SUBLEASE REQUIREMENTS The following terms and conditions shall apply to any subletting by Tenant of all or any part of the Premises and shall be deemed included in each sublease:

  • Service Requirement Except as otherwise provided in Section 6(e) of the Plan or Section 2 of this Agreement, this Option may be exercised only while you continue to provide Service to the Company or any Affiliate, and only if you have continuously provided such Service since the Grant Date of this Option.

  • Performance Requirements 1. Neither Party may impose or enforce any of the following requirements, or enforce any commitment or undertaking, in connection with the establishment, acquisition, expansion, management, conduct or operation of an investment of an investor of a Party or of a non-Party in its territory:

  • Service Requirements Grantee shall:

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

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