Issue link: https://read.dmtmag.com/i/117518
Infrastructure Management The team developed a CALM Geodatabase to house all construction projects with feature classes, including elevator/escalators, concessions, tenant and airline projects, roadway/traffic impacts, and airside/landside projects. Each project line-item captured all information regarding the project-management team, including the contractor, inspectors, operations manager, business-relationship manager and all associated contact information. This enabled LAWA to have a central repository for any information related to construction projects throughout LAX. Each contractor was required to submit a phasing and site-logistics plan that illustrated the "geography" of the construction work throughout the terminals and roadways. The site-logistics plan included access to the construction site, time/hours of planned work, and various related items such as dumpster, truck parking Figure 2. The CALMShare application shows the LAX Terminal 6 Ticketing Level with the tooltip functionality active and associated construction-related project information. Figure 3. ALMShare's filtering capabilities are viewed for concessions-construction projects in Terminal 6 at LAX. 24 G E O W O R L D / M A R C H 2 O 1 3 and crane locations. All such information is captured in the CALM Geodatabase and updated on a daily basis, enabling LAWA to have a "real-time" picture of construction-related activity in the field. The initial setup of the CALM SharePoint GIS involved a limited budget and few personnel. This type of project easily can be replicated in any type of airport or transportation infrastructure-development program. There were only two full-time staff members dedicated to the project for the data collection and development stages, and an additional IT member was later brought in for system development. The ongoing and future plans require four full-time employees to track and maintain all construction projects. The hardware/software specs included three dedicated servers: ArcGIS, SharePoint and SQL/Geodatabase. The initial costs were less than $100,000, excluding labor. It should be noted that the tool is an intranetbased application and open only to LAWA employees. This decision was made due to the sensitive nature of construction projects in an airport environment and related cost information. The tool uses ArcGIS Desktop and Server to manage spatial and scheduling data, and it expands on the "out-of-the-box" Esri-provided Silverlight API to develop mapping tools hosted in SharePoint. The CALM Team chose Silverlight 4.0 to fit with SharePoint 2010, and all development was done in Microsoft Visual Studio 2010. Microsoft's recent decision to drop Silverlight required the CALM development team to reconfigure the application using HTML5 and Esri's JavaScript API. Careful consideration of industry decisions is necessary when planning out development applications to alleviate backend programming issues later in the process. GIS Functionality Upon accessing the CALMShare Web site, employees can access construction projects by clicking on a specific terminal or project. LAWA employees then can drill down to a specific level of the terminal or project, where an interactive map application is displayed. The functionality mimics a Google Map application, where participants can pan and zoom as well as click on and off associated layers. As employees hover over construction-related projects, the tooltip functionality displays attributes from the CALM Geodatabase associated with the individual projects (see Figure 2). Another important feature is the filtering of projects by design, construction or completed phase as well as by start and end dates. As employees select start and end dates, they can filter out projects, enabling them to better plan construction work throughout the terminals or adjacent roadway. This functionality gets at the heart of the CALM Team: the ability to convey any "space/ time" conflicts with regard to construction projects throughout the Central Terminal Area (see Figure 3).