Modelling Scenarios Sample Clauses

Modelling Scenarios. Sediment sources modelled under this Project are summarized in Table 3.2. Two scenarios would be modelled for sediment dispersion modelling. Scenario C1 covers xxxxxx barge backfilling at the northernmost CMP, grab dredging (with 2 grab dredgers) at the middle CMP and xxxxxx barge capping at the southernmost CMP as well as other concurrent projects. Scenario C2 is similar except the dredging would be conducted with one TSHD. These two modelling scenarios are illustrated in Figure 3.4. Table 3.2 Summary of Sediment Sources Modelled under this Project CMP Items Marine Works Scenario C1 Scenario C2 Northernmost Plant Used Xxxxxx Barge or TSHD (Model xxxxxx barge for worst case) Production Rate (m3/day) 26,700 Working Hour (hr) 24 Sediment Loss Rate (kg/s) 60.0000 (modelled as 5 min release at 0.75 hr interval) Moving source? No Middle Plant Used Two Grab Dredgers One TSHD Production Rate (m3/wk) 100,000 256,200 Working Hour (hr) 24 24 CMP Items Marine Works Scenario C1 Scenario C2 Sediment Loss Rate (kg/s) 1.4054 (for each grab dredger modelled as continuous release) 17.7917 (modelled as 20 min release at 2 hr interval) Moving source? No Yes Southernmost Plant Used Xxxxxx Barge or TSHD (Model xxxxxx barge for worst case) Production Rate (m3/day) 26,700 Working Hour (hr) 24 Sediment Loss Rate (kg/s) 60.0000 (modelled as 5 min release at 0.75 hr interval) Moving source? No AGREEMENT NO. CE 72/2019 (EP) CONTAMINATED SEDIMENT DISPOSAL FACILITY AT WEST OF LAMMA ISLAND - INVESTIGATION Method Statement for Water Quality Modelling Assessment ASSESSMENT APPROACH AND MODELLING CONSIDERATIONS Figure 3.4 Sediment Sources to be Considered in Sediment Plume Modelling
Sample 1
AutoNDA by SimpleDocs
Modelling Scenarios. Sources of inert tracer for contaminant release modelling under this Project are summarized in Table
Sample 1
Modelling Scenarios. 3.1 The near field impact was modelled for different combinations of vertical density profile and ambient current velocity for 2009, 2013, 2020 and ultimate scenarios. For each assessment year, a set of three effluent flow rates, Q10, Q50 and Q90 were used, all based on the percentile of occurrence. The Q50 flow rate (the flow rate below which 50 percent of all effluent flow rates occur) was based on the average flow rate. The Q10 flow rate (the flow rate below which 10 percent of all flow rates occur) was calculated using a Q10 to Q50 ratio of 0.60. The Q90 flow rate was calculated using a Q90 to Q50 ratio of 1.28. These ratios are based on the findings from EEFS which are also in line with the actual measurement of effluent flow from SCISTW in 2004 and 2005. Based on the EEFS, the Q10 was representative of the flow rates that occurred between the 0 and 20 percentile (20 percent) and the Q90 was representative of the flow rates that occurred between the 80 and 100 percentile (20 percent) whereas the Q50 was representative of the remaining 60 percent. Table A5-1-4 below summarizes the adopted effluent flows. Table A5-1-4 Effluent Flow Adopted in Near-Field Model Scenarios ID % of occurrence Total Flow Flow per Riser Flow Per Port (m3/d) (m3/s) (m3/s) 2009 Q10 20 945,780 0.4561 0.0570 Q50 60 1,576,300 0.7602 0.0950 Q90 20 2,017,567 0.9730 0.1216 2013 Q10 20 996,660 0.4806 0.0601 Q50 60 1,661,100 0.8011 0.1001 Q90 20 2,126,105 1.0253 0.1282 2020 Q10 20 1,404,960 0.6775 0.0847 Q50 60 2,341,600 1.1292 0.1412 Q90 20 2,997,103 1.4454 0.1807 Ultimate Q10 20 1,680,000 0.8102 0.1013 Q50 60 2,800,000 1.3503 0.1688 Scenarios ID % of occurrence Total Flow Flow per Riser Flow Per Port (m3/d) (m3/s) (m3/s)
Sample 1

Related to Modelling Scenarios

  • Solution The Supplier’s contractually committed technical approach for solving an information technology business objective and associated Requirements as defined and authorized by the scope of the Contract or any order or Statement of Work issued under the Contract. Solution means all Supplier and Supplier’s third-party providers’ components making up the Solution, including but not limited to Software, Product, configuration design, implementation, Supplier-developed interfaces, Services and Work Product.

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

  • Screening 3.13.1 Refuse containers located outside the building shall be fully screened from adjacent properties and from streets by means of opaque fencing or masonry walls with suitable landscaping.

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

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

  • Signaling Parameters All SS7 signaling parameters will be provided in conjunction with traffic exchange trunk groups, where and as available. These parameters include Automatic Number Identification ("ANI"), Calling Party Number ("CPN"), Privacy Indicator, calling party category information, originating line information, charge number, etc. Also included are all parameters relating to network signaling information, such as Carrier Information Parameter ("CIP"), wherever such information is needed for call routing or billing. GTE will provide SS7 via GR-394-SS7 and/or GR-317-SS7 format(s).

  • Scoring The number of routes each company operates (Route # 0001-2999, 8000-8199) will be multiplied by 2 to determine the daily number of trips. (Only accidents, breakdowns and service reports related to routes falling in this range will be used for the evaluation). The daily number of trips will be multiplied by 175 to arrive at the annual number of trips. The number of accidents, breakdowns and service complaints will be divided by the total number of trips to calculate a percent figure. Each company’s percentage will be compared to the total average. See below for a sample. BUS COMPANY NUMBER OF TOTAL BKDN PERCENT ACCIDENTS PERCENT2 SERVICE PERCENT3 ROUTES TRIPS BKDN ACCIDENTS REPORTS COMPLAINTS TO TRIPS TO TRIPS TO TRIPS A 360 58680 3 0.01% 27 0.05% 46 0.08% B 48 7824 3 0.04% 4 0.05% 39 0.50% C 123 20049 11 0.05% 9 0.04% 27 0.13% D 91 14833 0.00% 10 0.07% 11 0.07% E 124 20212 20 0.10% 19 0.09% 18 0.09% TOTALS 746 121598 37 0.03% 69 0.06% 141 0.12% To score, if a company’s percentage is less than or equal to the total percentage for that category, the company will be awarded 6 points per category. Percentages greater than the total percentage for each distinct category (Accident, Breakdown, Service Complaints) will be scored according to the following scale: Vendor Category Percent Points Less than-Equal to Ave. 6 points 0-3% above average 5 points 4-7% above average 4 points 5-8% above average 3 points 9-12% above average 2 points 13-16% 1 points Greater than 17% 0 points Example: Company A had a lower percent of breakdowns than the average total, and would receive 6 points for breakdowns. If a company has a higher percentage than the average total, 0 point will be added to their score. Company B would not receive 6 points for breakdowns. The same calculation would be performed for accidents and service complaints. Any circumstance whereby a Breakdown or Accident is found by PTS to be ‘Non Reported’ by vendor within the required timeframe (see G-36) will count as (20) ‘Reported’ instances for the purpose of this Contractor Evaluation Scoring.

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

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

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