Model Documentation Sample Clauses

Model Documentation. The Facility dynamic model shall be fully documented. The documentation shall describe in detail the model structure, inputs, outputs and how to set up and use the model in the simulation software environment that can be used by CEB to simulate the dynamic performance of the Facility, specifically voltage control, load ramping and frequency support within the design operating range of the Facility. The document shall at least contain the following:
AutoNDA by SimpleDocs
Model Documentation. 3.1. Simulation model of case Östersundom The Östersundom model represents a large district containing 14 areas, each with different square meter amounts of multi-storey buildings, town houses, smaller residential buildings, public buildings (schools, kindergarten etc.), commercial buildings and shops. When it comes to energy solution, the whole Östersundom area contains one combined heat and power (CHP) plant. This plant is controlled according to the heat demand while producing electricity simultaneously as one- third respect to the heat production. There is a centralized thermal storage for the whole district while thermal storage capacity can be added to each area separately. The sizes of the storages are modified through their volumes between zero to 20 000 m3 per urban area. The Östersundom district model contains also a district heating component from which one could change the supply and return temperatures of the district heating network and lower the heating value of the fuel used in the CHP. It can be regarded that this district heating component is forming a unity with the CHP component. See Figure 6 for overview of the Östersundom model. The separate components are described in the following. A closer description about the Östersundom model, its components and the calibration done can be found in deliverable document 3.4.
Model Documentation. Activities The Engineer will prepare written documentation of the modeling methodology and results for inclusion in TM#3: Modeling Methods, Assumptions and Results. Modeling results (basin boundaries, peak flows, and surcharge areas) will be documented in GIS shapefiles and spreadsheets, so that the City has access to modeling data and results. At the end of the project, model files will be provided to the City in XPSWMM or other SWMM format. Phase 5 Deliverables The following deliverables will be provided under Task 5: • Draft TM#3: Modeling Methods, Assumptions and Results • Electronic modeling files in XPSWMM or other SWMM format at project completion • GIS shapefiles documenting subbasin delineation • Tabular documentation of existing and future flow rates at key locations • Inclusion of capacity problem areas in the potential project matrix under Task 6-1 Phase 5 Assumptions The following assumptions are made for Phase 5: • No additional field investigation or survey work is included in this task. • No more than 260 subbasins will be evaluated as part of the hydrologic modeling effort, consistent with the number of subbasins evaluated in 2006. • Current land use and existing vacant lands will be used to calculate current (i.e., existing) condition stormwater flows for each design storm; future land use reflecting full-build out conditions based on current zoning will be used to calculate the future- conditions stormwater flows. • City staff will provide anecdotal reports of flooding problems for use in model validation. Validation efforts under Task 5-3 will be limited to comparing existing- conditions model results for a select storm event to available information from City flooding reports and photographs. • Pipes and culverts less than 12 inches in diameter will not be included in the modeling effort. • The hydraulic modeling effort may include piped and open channel conveyances where stormwater is the primary source of discharge. Outfalls to creeks will be the end points of the hydraulic model. This scope of services does not include modeling of natural systems with baseflow or stormwater flow generated outside the city limits. • Where survey data are not available from Tasks 2 and 3, the Engineer will incorporate assumed data from LIDAR, field measurements, or other sources and document the modeling assumptions. • Due to the unknown scope and scale of modeling work, the total hydraulic modeling scope reflected under Tasks 5-3 reflects 140 hours o...
Model Documentation. 1) Prepare and submit draft technical memorandum describing hydraulic model development and calibration for City review and comment.
Model Documentation. Xxxxxx-Xxxx will provide updated model documentation at the completion of the project detailing the model file structure, model inputs and model outputs. Details of model validation will be included as part of the documentation. Anticipated Meetings: • Up to one (1) additional in person status meeting • Up to five (5) status conference calls

Related to Model Documentation

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Tax Documentation Xxxxxx agrees to provide a completed IRS 1099 for its payments to, and Xxxxxxx agrees to provide IRS W-9 forms for, each of the following payees under this Settlement Agreement:

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • ENVIRONMENTAL DOCUMENTATION Each environmental service provided by the Engineer shall have a deliverable. Deliverables shall summarize the methods used for the environmental services, and shall summarize the results achieved. The summary of results shall be sufficiently detailed to provide satisfactory basis for thorough review by the State, The Federal Highway Administration (FHWA), and (where applicable) agencies with regulatory oversight. All deliverables shall meet regulatory requirements for legal sufficiency, and shall adhere to the requirements for reports enumerated in the State’s NEPA MOU.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

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