Laserfiche WebLink
<br />..,\\\141 <br />\), <br /> <br />2.0 Overview of 24 MSM <br /> <br />The 24 Month Study Model (24MSM) is a monthly water accounting model used in the <br />management and operation of the Colorado River Basin. It is used in conjunction with a <br />variety of other models, mostly the Colorado River Simulation System model (CRSS), <br />and the Binary Hoover Operational Model (BHOPS). Generally, the 24MSM is a tool used <br />to develop the Annual Operating Plan (AOP) for each year, the AOP being a document <br />detailing the "Philosophy of Operations" of the Colorado River. The 24MSM is subse- <br />quently used to track and adjust operations throughout the water year to reflect the AOP. <br /> <br />>>>>>>>>>>>>>>>>> <br /> <br />The 24MSM is actually a derivative model of the CRSS model. In 19877, the 24MSM was <br />converted from Fortan IV to Fortran V, running on the VAX system. <br /> <br />***a brief description of how the model is used: Bruce and Brad*** <br /> <br />Porting: The first step of the project was dependent upon getting the 24MSM running on <br />the VAX ported over to a SUN workstation, running Fortran77. This was accomplished in <br />roughly one week, with substantial help of Rich Hedrich also of LC Region. <br /> <br />description of 24MSM data files <br /> <br />sources of data <br /> <br />>>>>>>>>>>>>>>>>>>>>>>>> <br /> <br />3.0 Project History <br /> <br />The 24MSI was developed jointly by CADSWES and the Lower Colorado Region, <br />Bureau of Reclamation. Personnel who were involved in the project included: Henry <br />Horsey, CADSWES; David Theobald, CADSWES; Terry Fulp, USBR, LC Region; Bruce <br />Williams, USBR, LC Region; and Brad Vickers, USBR, UC Region. <br /> <br />The 24MSI project was formally initiated on May 23, 1990. Activities prior to this date <br />had outlined the project goals, introduced the existing 24MSM methodology, and <br />discussed functionality required by LC Region. Design activities from April until June 4 <br />concentrated on a user needs assessment, which resulted in the first rendition of the <br />. Version/Implementation Plan (VIP). This was a working document, which provides a <br />listing of the requirements of the system, loosely organized by main functional compo- <br />nents, and prioritized into version categories. It provided a metric to mark the project's <br /> <br />24 Monlh Study Project Doalmentation Volume I <br /> <br />618191 <br /> <br />4 <br />