P12-6972 Energistics Proposal 18Jul2012 · 2020. 9. 19. · Proposal for EIP v1.0-compliant Prototype Implementation Esri Proposal No. P12-6972 3 July 18, 2012 2.2 The Technical Solution

PROPOSAL FOR EIP V1.0-COMPLIANT PROTOTYPE IMPLEMENTATION, REVISED 07/18/2012 Prepared for: Energistics Attn: Hari Koduru 1 Sugar Creek Center Blvd, Ste 1075 Sugar Land, Texas 77478 [email protected]

Date: July 17, 2012 Prepared by:

Environmental Systems Research Institute, Inc. (Esri) 380 New York Street Redlands, California 92373-8100 Phone: (909) 793-2853

This document contains commercial or financial information or trade secrets of Esri, which are confidential and exempt from disclosure to the public under the Freedom of Information Act 5 USC 522(b)(4), and unlawful disclosure thereof is a violation of the Trade Secret Act 18 USC 1905. This proposal includes data that shall not be disclosed outside of the Procuring Entity and shall not be duplicated, used, or disclosed in whole or in part for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this offeror as a result of or in connection with the submission of this data, the Procuring Entity shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Procuring Entity’s right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained on all sheets.

Revised

Copyright © 2012 Esri All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of Esri. This work is protected under United States copyright law and other international copyright treaties and conventions. Esri grants proposal recipient the right to internally redistribute this document to proposal recipient's management and staff on a need-to-know basis, so long as proposal recipient does not remove or obscure any Esri or its licensors' patent, copyright, trademark, or proprietary rights notices contained in or affixed to this document. No part of this work may be reproduced or transmitted to third parties (except for consultants under a confidentiality obligation who are involved in the proposal evaluation process) in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by Esri. All requests should be sent to Attention: Contracts and Legal Services Manager, Esri, 380 New York Street, Redlands, CA 92373-8100 USA.

US Government Restricted/Limited Rights

Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. The commercial license rights in the License Agreement strictly govern Licensee’s use, reproduction, or disclosure of the software, data, and documentation. In no event shall the US Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the US Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (DEC 2007); FAR §52.227-19(b) (DEC 2007) and/or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (DEC 2011) (Technical Data – Commercial Items) and/or DFARS §227.7202 (Commercial Computer Software and Commercial Computer Software Documentation), as applicable. Contractor/Manufacturer is Esri, 380 New York Street, Redlands, CA 92373-8100, USA.

Esri Trademarks and Service Marks

@esri.com, 3D Analyst, ACORN, Address Coder, ADF, AML, ArcAtlas, ArcCAD, ArcCatalog, ArcCOGO, ArcData, ArcDoc, ArcEdit, ArcEditor, ArcEurope, ArcExplorer, ArcExpress, ArcGIS, ArcGlobe, ArcGrid, ArcIMS, ARC/INFO, ArcInfo, ArcInfo Librarian, ArcLessons, ArcLocation, ArcLogistics, ArcMap, ArcNetwork, ArcNews, ArcObjects, ArcOpen, ArcPad, ArcPlot, ArcPress, ArcPy, ArcReader, ArcScan, ArcScene, ArcSchool, ArcScripts, ArcSDE, ArcSdl, ArcSketch, ArcStorm, ArcSurvey, ArcTIN, ArcToolbox, ArcTools, ArcUSA, ArcUser, ArcView, ArcVoyager, ArcWatch, ArcWeb, ArcWorld, ArcXML, Atlas GIS, AtlasWare, Avenue, BAO, Business Analyst, Business Analyst Online, BusinessMAP, CommunityInfo, Database Integrator, DBI Kit, EDN, Esri, Esri—Team GIS, Esri—The GIS Company, Esri—The GIS People, Esri—The GIS Software Leader, FormEdit, GeoCollector, Geographic Design System, Geography Matters, Geography Network, GIS by Esri, GIS Day, GIS for Everyone, GISData Server, JTX, MapIt, Maplex, MapObjects, MapStudio, ModelBuilder, MOLE, MPS—Atlas, PLTS, Rent-a-Tech, SDE, SML, Sourcebook·America, SpatiaLABS, Spatial Database Engine, StreetMap, Tapestry, the ARC/INFO logo, the ArcGIS logo, the ArcGIS Explorer logo, the ArcPad logo, the Esri globe logo, the Esri Press logo, the GIS Day logo, the MapIt logo, The Geographic Advantage, The Geographic Approach, The World's Leading Desktop GIS, Water Writes, www.arcgis.com, www.esri.com, www.geographynetwork.com, www.gis.com, www.gisday.com, and Your Personal Geographic Information System are trademarks, service marks, or registered trademarks or service marks of Esri in the United States, the European Community, or certain other jurisdictions. Other companies and products mentioned herein may be trademarks or registered trademarks of their respective trademark owners.

1/6/2012

Esri Proposal No. P12-6972 i July 18, 2012

Table of Contents Section Title Page Number

1.0 Executive Summary ............................................................................................................. 1

2.0 Solution Overview ................................................................................................................. 2

3.0 Scope of Work ...................................................................................................................... 6

4.0 Schedule ............................................................................................................................. 21

5.0 Project Team and Qualifications ..................................................................................... 23

Appendix A— Documentation of Deliverables ........................................................................... 24

Appendix B—Proposed Staff Resumes ....................................................................................... 25

Appendix C—Esri Master Services Agreement (E115M 6-09) .................................................. 32

Proposal for EIP v1.0-compliant Prototype Implementation

Esri Proposal No. P12-6972 1 July 18, 2012

1.0 Executive Summary Energistics has proposed a project to demonstrate the promise of the Energy Industry Profile (EIP) v1.0 using a network of three or more searchable metadata systems federated via the internet. The primary deliverable of the project is a new geoportal implementation customized for Energistics to support this EIP v1.0 profile. Environmental Systems Research Institute, Inc. (Esri) – a leader in supporting metadata standards and geospatial data sharing technologies – is pleased to present its proposal for professional services. The services include providing key supporting applications needed to enable creation, validation, publishing, search, and access of resources with EIP v1.0 metadata. The services also provide technology transfer to Energistics and workshops designed to encourage community adoption. Although additional deliverables were identified in the EIP Prototype Project Proposal subject to available funding, Esri chooses to focus on the first set of required deliverables, as documented in Appendix A of this proposal, in this response. The details regarding proposed Tasks can be found in Section 3.0 of this proposal. Esri’s proposed solution includes the following:

Project Initation Meeting onsite with Energistics Geoportal technology transfer to Energistics Geoportal configuration to identify, validate, and create EIP v1.0 metadata ISO 19115:2003 to EIP v1.0 Metadata Transform Capability FGDC to EIP v1.0 Metadata Transform Capability Metadata Publishing Workshop to Energistics CSW Clients for ArcMap customizations to support EIP v1.0 users Customizations to ArcCatalog 10 to support EIP v1.0 metadata Energy Community Workshop – Energistics-hosted in Houston Follow-on Training Webcast

Esri is committed to producing excellent software and delivering exceptional services toward the implementation of high quality customer-focused systems. The company develops and supports GIS at all levels, from the desktop to the enterprise, and provides software, educational services, user support, and consulting services that range from needs assessments to system design and implementation. In this spirit, Esri is pleased to respond to the needs of the energy community through this proposal.



2.0 Solution Overview 2.1 Introduction The EIP v1.0-compliant Prototype Geoportal will be designed to participate in a network consisting of three or more searchable metadata systems federated via the internet. Each system will contain a catalog of metadata records and will expose those records for search or harvesting using a standard catalog service (Open Geospatial Consortium Catalog Service for the Web 2.0.2 (OGC CSW 2.0.2)) interface with results encoded in EIP v1.0-compliant, ISO XML format. Figure 1 below shows the federation of metadata systems; this proposal focuses on the EIP v1.0 implementation.

Figure 1, Federated EIP Catalog Network

The proposed solution has a technical component and a training and outreach component. The technical component will require close collaboration between the Energistics Metadata Work Group and Esri to customize the Esri Geoportal Server version 1.2 software and its components to support the emerging EIP v1.0 metadata profile. The training/community education component provides educational presentations and workshops to promote understanding of the system, the profile, and how to manage metadata resources.



2.2 The Technical Solution Esri Geoportal Server is an open source1 product that enables discovery and use of geospatial resources including datasets, rasters, Web services, and even non-geographic resources. It helps organizations manage and publish standards-based metadata for their assets so users can discover and connect to them. The Esri Geoportal Server is primarily composed of a Java web application that exposes an OGC CSW endpoint, a REST endpoint, and an OpenSearch endpoint for search. It supports a number of metadata profiles out of the box, and can be configured to support additional ones. It allows users to search other geoportals, CSW endpoints, and OpenSearch endpoints through a federated search capability. It provides tools that enable users to search geoportals from within ArcGIS Desktop, ArcGIS Explorer, a variety of web map viewers, HTML pages, and integration through the REST protocol with content management systems. In addition, Esri Geoportal Server can harvest other repositories and service endpoints into its catalog – OGC Services (e.g., WMS, WFS, WCS, and SOS), ArcGIS Server directories, ArcIMS Metadata Services, Open Archive Initiative repositories, Web Accessible Folders, CSW endpoints, and THREDDS Servers. Although out of the box the Esri Geoportal Server can harvest metadata that conforms to a variety of profiles and is provided through many different types of repositories, the scope of this project focuses on workflows for harvesting ISO 19115:2003 XML, EIP v1.0 XML, and FGDC XML, and providing transformation workflows for ISO 19115:2003 XML and FGDC XML to EIP v1.0 XML. ISO 19115-2 XML is also supported for harvesting out of the box, but this scope of work does not yet include workflows for transforming ISO 19115-2 XML to EIP v1.0 XML. Figure 2 below shows a geoportal implementation, connecting client applications with which it can be integrated, and protocols it can harvest. Note that at the heart of the geoportal is a database and an index. Microsoft SQL Server, Oracle, PostgreSQL, and MYSQL are all supported. The index is based on Apache Lucene indexing technology. The geoportal web application is a java .war file, which can be deployed from Tomcat, Glassfish, or WebLogic. Further information about the supported geoportal software environment is available online2; although the Esri Geoportal Server is easily integrated into an ArcGIS environment, no Esri software is required for its implementation.

1 Esri Geoportal Server was released under the Apache 2.0 license, which allows developers to freely customize and redistribute the software. See http://esriurl.com/geoportal for details. 2 See installation documentation at http://sourceforge.net/apps/mediawiki/geoportal/index.php?title=Preinstallation_1.2



Figure 2, Esri Geoportal Server Components



Powerful solutions are enabled when constellations of geoportals are federated together, allowing individual organizations to maintain their own user communities, metadata quality management, and customized interfaces while federating with other communities to broaden the discoverable resource base. Esri envisions the EIP v1.0-compliant Prototype Geoportal will be thus enabled. This proposal discusses technical solutions that will enable publishing, validation, creation, editing, and discovery of EIP v1.0 metadata. The solution will also transform harvested metadata from ISO 19115:2003 and FGDC XML to EIP v1.0 XML. It will also provide for a configuration profile for the ArcMap CSW Client so users can search the EIP CSW catalogs from within the ArcMap environment. Finally, Esri will provide consulting support to work toward customizations to ArcCatalog to support the EIP v1.0 metadata from the ArcGIS Desktop environment. 2.3 Training and Outreach The training and outreach solution discussed in this proposal will take place at three different sessions during the duration of the project. The first training will take place as a half-day session onsite with the Energistics Metadata Work Group on the same day as the onsite Project Kick-off meeting. The goal of this training will be to address technical questions surrounding how to manage and maintain a geoportal. This training is not specific to the EIP v1.0 metadata, but is for orienting the technical and workgroup staff to the general geoportal capabilities and technical maintenance. In the second training session, the Energistics Metadata Work Group and Esri staff will collaborate to prepare training that will educate a larger audience (e.g., may include delegates from the project’s sponsor organizations) on how to create EIP v1.0 metadata, publish it to the geoportal, and manage it once published. This training will be a remote webcast, and can represent a progress presentation for the development work done at that point in the project. The final training will take place onsite at a location hosted by Energistics in the early 2013 timeframe, after project-related development items discussed in the Technical Solution have been implemented. It will be a three-day session, with more in-depth training and discussions on EIP profile metadata, the EIP v1.0-compliant Prototype Geoportal and participating network, data sharing, how sponsors and their project particpants can participate, and additional ways to leverage the Esri Geoportal Server in a network environment. Following the three days onsite, there will be a remote summary webcast (to be recorded by Energistics) addressing similar topics in a condensed format for users who could not travel to the onsite training. These outreach activities have been perceived as valuable for creating understanding of the EIP and the network, and for encouraging participation and adoption. They also serve as important sessions where users and implementers can dialog for feedback and further ideas.



3.0 Scope of Work 3.1 Introduction The overarching goal of the project specified in this scope of work is to deliver an Esri Geoportal Server implementation that supports the EIP v1.0 metadata specification through the deliverables described below, and provide training to support the EIP v1.0 Geoportal Server implementation. Deliverables are discussed in this section in order of when they would take place. The process for reviewing and accepting deliverables is also described in this section. 3.2 Deliverable Review and Acceptance Timely review and acceptance of deliverables by Energistics will be critical to maintaining the project schedule. The commencement of work on subsequent tasks with dependencies on preceding tasks will be contingent upon Esri receiving written acceptance for those preceding tasks. 3.2.1 Review for Customizations that Update the Esri Geoportal Server/ArcGIS This scope of work assumes the following testing and review cycle for customizations that update or support the Esri Geoportal Server and ArcGIS Desktop, as discussed in Tasks 3, 4, 5, 7, and 8 of this proposal. Esri uses a formal workflow for internal acceptance testing (IAT) and user acceptance testing (UAT). These testing workflows will be executed based on an Energistics-approved test plan for the tasks enumerated above. Internal acceptance testing and user acceptance testing are described in the following sections. 3.2.1.1 Internal Acceptance Testing In internal acceptance testing, Esri will establish a test installation of the custom application at Esri's offices in Redlands, California, for the purposes of formal testing. Using this test environment, Esri will perform an end-to-end test of the customization by stepping through the test cases and scenarios. The objective is to complete the same tests that will be used for user acceptance testing and verify each custom function based on test cases defined in the test plan. Following the IAT, Esri will review the test results and evaluate if the components of the release are ready to be installed at the Energistics site for UAT. 3.2.1.2 User Acceptance Testing The purpose of UAT is to verify that the application functions in accordance with the test plan in Energistics’ operational environment. Esri's approach to UAT is to have Energistics project participants conduct the structured testing, with Esri staff in a supporting role. Prior to UAT, Esri will provide details of the customizations and how to test to the Energistics testers. The testers



will be provided with the test cases and will conduct UAT in the test environment over a ten-day period. During UAT, defects and issues will be reported to Esri using a problem report template to be provided by Esri. Energistics will have ten business days to test the provided customizations. During this period, Energistics testers will report problems, issues, errors, or other feedback to the Energistics Project Manager. Reported issues will be assessed by the Esri Project Manager and the Energistics Project Manager using the guidelines described in the Corrective Actions section 3.2.1.3 below. Esri will fix defects identified in accordance with acceptance criteria and provide an update to the deliverable for Energistics to again review during another ten business day period. If no defects are identified on the basis of compliance with the test and acceptance criteria, the UAT will be considered complete and Energistics will be responsible for providing written acceptance of the release in the form of an electronic communication. To keep the project on schedule, if further issue reports or written acceptance are not provided within the ten day period, the latest version of the provided work will be considered as accepted by default. Customizations will be deemed acceptable by Energistics on completion of the following:

All tests identified in the Energistics-approved test plan have been executed to

completion by Energistics testers without encountering Severity 1 or 2 defects (defect levels are outlined in section 3.2.1.3). If actual results of the test scripts are materially different from expected results, the test scenarios will be rerun after logged defects related to them have been fixed.

There are no outstanding mutually agreed-on Severity 1 or 2 defects.

All Severity 3 defects have been reviewed by Energistics and Esri in a collaborative process to access the priority of these defects. Fixing of mutually agreed upon Severity 3 defects are not required to be resolved for the customized deliverable to go into production.

3.2.1.3 Corrective Actions The following section discusses procedures for corrective actions to address software issues reported by Energistics:

If Energistics testing project participants find a defect they believe is a software defect, they will first attempt to validate the defect by reproducing the defect before reporting it to Esri. Once submitted, Esri will work to validate the defect. If Esri can validate the defect, it will be recorded as a defect and Esri will classify it as one of four defect severity levels (see descriptions of severity levels below).



If Esri cannot validate the defect, Esri will ask the Energistics testing team to either provide

more information or demonstrate how and where the defect occurs. Based on this information, Esri will work further to identify the source of the defect. Esri may determine that the defect is not a custom component or application problem but instead a problem with data loading, nonapplication software, the network, an operator's use of the system, or a misunderstanding about how the system's business rules work.

If Esri cannot replicate a reported defect, if the Energistics testing team cannot demonstrate

it, or if it is determined by Esri that the defect has another cause not related to Esri-supplied application software, then Esri will notify the Energistics testing team that the problem is not a software defect and will reclassify the issue accordingly. If appropriate, Esri will recommend an action to take, for example, to reload certain data into the system.

Defect Descriptions

Severity Description

1 Critical

A severity 1 issue results in the application or process not working as defined in the approved design document and in the application or process being stopped with no workaround. The defect(s) may affect multiple users or frequently used functions.

2 High

A severity 2 issue severely impairs the process and reduces user productivity. No workaround has been identified by Esri. It could be a major problem that affects a limited number of users or affects functionality not needed on a daily basis.

3 Medium

A severity 3 issue impairs the process but has a workaround recommended by Esri. The user is able to function near the expected productivity level.

4 Low

A severity 4 issue does not have a significant impact on the process and reflects a minor problem(s).

3.2.2 Review for Documents This scope of work assumes the following review cycle for documents provided as deliverables in this project. All deliverable documents will be provided in softcopy electronically. Energistics will have five business days to provide reviewed, approved, and consolidated written feedback on draft documents. Upon receipt of Energistics' feedback on draft documents, Esri will incorporate mutually agreed upon changes into final versions of the documents within five business days. Energistics will then have five business days to provide written acceptance of final documents. The acceptance criterion for document deliverables is that the documents have incorporated the mutually agreed upon changes into the final document. If further changes or



written acceptance are not provided by Energistics to Esri within the five day period, the latest version of the document will be considered as accepted by default. 3.3 Work Plan Task 1 Project Initiation and Management Project management activities are described in this task, and include the Project Initiation Meeting, Project Plan, Monthly Status Reports, and communication calls. Task 1.1 Project Initiation Meeting Esri will schedule a half-day Project Initiation Meeting onsite at a Houston, Texas location hosted by Energistics upon receiving fully signed contract documents. The Esri project manager will coordinate with the Energistics project manager to schedule the meeting logistics, including agenda items and attendance of participants. Esri will prepare and submit a meeting agenda to Energistics three business days prior to the start of the Project Initiation Meeting. The meeting will cover the following topics:

Introduction of staff and identification of project roles Review project-related activities to date Review and discussion of the preliminary Project Plan Finalization of project planning items

Esri will capture results including meeting attendance, revisions to project planning elements (e.g. schedule), action items, issues, and decisions and will incorporate relevant details into the Project Plan (Task 1.2.1).

Esri Deliverables Meeting Agenda submitted to Energistics project manager three business days prior to

meeting.

Energistics Responsibilities Ensure appropriate Energistics project team members participate in the Project Initiation

Meeting. Provide adequate facilities onsite for hosting the Project Initation Meeting.

Assumption

Project Initiation Meeting will be conducted onsite at a Houston, Texas location hosted by Energistics.



Task 1.2 Project Management

1.2.1 Project Plan Esri will develop a Project Plan based on the scope of the contracted services. Esri will present the Project Plan to the Energistics project team for their approval during the Project Initiation Meeting. The Project Plan will address the project schedule and the communication plan. Esri will update the presented Project Plan based on Energistics input from the Project Initiation Meeting, and will provide the updated Project Plan document to Energistics for review. Energistics will review the Project Plan and provide feedback to Esri. Esri will incorporate mutually agreed upon changes, and will deliver a baseline version of the Project Plan to Energistics for written acceptance. The Project Plan may be updated as needed. Updated items will be reflected in the Monthly Status Reports. 1.2.2 Monthly Status Reports Monthly Status Reports will be provided to the Energistics Project Manager in electronic form. The monthly status report shall include:

Current Status Activities completed during that month Activities planned for the next month Issues and Resolutions Milestones and deliverables

1.2.3 Communication Calls Throughout the duration of the project, Esri will participate in biweekly calls with Energistics to report on status, discuss upcoming tasks, receive clarification where needed, and discuss other project-related issues. Additional calls will be scheduled in advance as necessary during periods of intense task work. An agenda for the call will be provided to the Energistics Project Manager at least two days in advance of the call, and minutes that result from the call will be provided to the Energistics Project Manager within two days after the call. Although the agenda and minutes are part of this Task’s Deliverables, they are not subject to the review and acceptance protocol described in Section 3.2.

Esri Deliverables Project Plan Monthly Status Reports Agenda and minutes for biweekly calls

Energistics Responsibilities Identify a project team made up of Energistics project participants with defined roles and

key project stakeholders.



Provide written acceptance of the Project Plan per guidelines in Section 3.2. Ensure participation of necessary Energistics project team in meetings and calls.

Assumptions The accepted baseline Project Plan is the baseline for all work activities that will be

executed during the project. Energistics will have a project team with defined team roles and key project stakeholders

and will share that project organization with Esri. The Energistics project manager will be the main point of contact for the Esri project

manager. Task 2 Geoportal Technology Transfer to Energistics While onsite for the Project Initiation Meeting (Task 1.1), Esri will provide a technical training and FAQ session for general Geoportal Server maintenance. Because an Energistics project participant is already familiar with how to install and configure a Geoportal Server instance, the focus of this training will be for participants to get specific technical answers. To assist Esri in preparing for the technical training session, Energistics will participate in a one-hour webcast to show Esri the system environment upon which the Energistics initial Esri Geoportal Server implementation is installed. During that webcast, Esri will guide the Energistics project participants in talking about their implementation, with the goal of identifying the status of the Energistics geoportal installation and what issues are of interest that should be addressed in the technical training. After this initial webcast, Esri will compose an Agenda based on the topics noted during the initial webcast, and provide the Agenda to the Energistics Project Manager in advance. The training will be a half-day session preceding or following the half-day Project Initiation Meeting, and will first address issues of interest identified during the initial webcast. After those issues are addressed, the remaining time will be used to answer additional questions and topics of interest.

Esri Deliverables One hour long webcast to investigate the Energistics geoportal installation system

environment and note technical issues of interest. Training Agenda submitted to Energistics project manager three days prior to meeting. One half-day training session onsite preceding or following the Project Initation Meeting

to answer technical questions related to Geoportal Server topics.

Energistics Responsibilities Ensure that appropriate technical staff are available and participate in the pre-training

webcast and subsequent training session. Advertise the training to staff



Provide adequate facilities onsite for hosting the training session.

Assumptions The training will address general Esri Geoportal Server technical topics and will not

include training on the EIP v1.0 metadata profile-specific customizations. The training activity is not dependent on other deliverables pursuant to this project. The training will be conducted onsite at a Houston, Texas location hosted by Energistics,

on the same day as the Project Initation Meeting. Task 3 Geoportal Configuration to Identify, Validate, and Create EIP v1.0

Metadata In the context of this project, the term ‘validation’ refers to the set of rules that an organization decides a metadata XML record must abide by for that XML to be considered compliant. The Esri Geoportal Server version 1.2 will be customized to support the validation of metadata against the EIP v1.0 profile, display of validation issues for not-valid records, an interface for creating EIP v1.0 metadata, and publishing of valid records to its catalog. The Esri Geoportal Server will implement CSW 2.0.2 with the EIP/ISO 19115-1 outputFormat as well as the standard csw:record outputFormat. Esri will deliver a Geoportal Server Deployment File that supports the customizations discussed in the following paragraphs. Validation will be determined by a schema and schematron provided by Energistics but called by the Geoportal Server validation mechanisms; validation will be triggered upon metadata harvest and when a record created or updated through the Geoportal edit interface is committed. Schematron rules can implement validatation of codelist values against EIP v1.0 code lists that are hosted at a public web accessible location by Energistics in a form and format that follows the TC 211 code list structure, as shown in the example at http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml. The metadata creation and editing interface will be modeled after the Esri Geoportal Server’s XML Editor (GXE), which provides for dynamic repeating sections in the metadata, the ability to save an in-progress record as a draft, and upon completing a metadata record the ability to validate it. Here again, the EIP v1.0 code lists will be referenced to populate respective dropdowns in the metadata editor form. The metadata editor would also provide the ability to display the description of the code list value - as defined in the code list file – when the user hovers over the code list value in the metadata editor form.



Esri Deliverables Esri Geoportal Server Deployment File containing the customizations supporting the

following: • Validation of XML-encoded metadata records using XML schema and schemtron

rule sets for the EIP v1.0 metadata profile. • Access to metadata for search, with response in CSW GetRecordsResponse

documents containing EIP v1.0 XML-encoded metadata records. • Metadata editor for creating,editing, and viewing EIP v1.0 XML. • Metadata editor ability to call code list values and their description in the metadata

editor form. • EIP v1.0 XML to html transformation for displaying EIP (ISO 19115-1) metadata in

the geoportal Details view.

Energistics Responsibilities Provide the schema and schematron to be used for EIP v1.0 validation to Esri staff at

least five days prior to the start of this task. Develop and host code lists as defined in the TC211 specification at a location accessible

to their geoportal implementation. Code list XML files will be modeled after the ISO TC 211 specification for code lists. An example that can be used as a template is available at http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml.

Install the delivered Deployment File in the Energistics environment according to the Esri Geoportal Server installation documentation1.

Provide written acceptance of the Deployment File per guidelines in Section 3.2. Assumptions

The Energistics environment for hosting the customized Esri Geoportal Server will conform to the system environment requirements as described in Geoportal Server documentation2.

Energistics will define the metadata validation criteria to be used for these customizations at the outset of the project. Although the EIP v1.0 specification may evolve during the course of the project – especially as the DIS 19115-1 evolves - Esri’s customizations will be determined by this designated first specification. Updates to accommodate limited changes in the specification can be addressed by Additional Consulting Hours (Task 11).

Code list values and descriptions that appear in the metadata editor will be provided in English, and may not be localizable.

If Esri finds issues with the EIP v1.0 profile itself or can identify best practices to which the profile is not conforming, Esri will report them to Energistics Metadata Work Group for consideration in next EIP version revision.

1Installation documentation at http://sourceforge.net/apps/mediawiki/geoportal/index.php?title=Installation 2System environment requirements at http://sourceforge.net/apps/mediawiki/geoportal/index.php?title=Preinstallation_1.2



Task 4 ISO 19115:2003 to EIP v1.0 Metadata Transform Capability The Geoportal Server will be customized via a Deployment File to transform metadata records from ISO 19115:2003 to the EIP v1.0 profile upon upload/harvest, and then publish them to the geoportal. Items that do not pass EIP v1.0 validation after transformation will be published to the geoportal in draft form, meaning that they will not be discoverable through search but can be edited through the Geoportal metadata editor (see Task 3) to be made valid. This task includes internal testing of the Energistics-provided transformation and its integration with the customizations to support EIP v1.0 XML validation as described in Task 3. It also includes code changes in an integral part of the Geoportal publishing component to facilitate the statusing of harvested documents as ‘Draft’ if they fail validation.

Esri Deliverables Esri Geoportal Server Deployment File that includes customizations for transforming ISO

19115:2003 metadata to EIP v1.0 metadata, and documents that fail validation after transformation will be published as draft.

Energistics Responsibilities Provide the transformation xslt from ISO 19115:2003 to EIP v1.0 – or alternatively, two

xslts where the first is ISO 19115:2003 to ISO 19115-1, and the second is ISO 19115-1 to EIP v1.0, at least five business days prior to the start of this task.

Provide written acceptance of the customized Deployment File per guidelines in Section 3.2.

Assumptions Metadata documents that are not ISO 19115:2003 will not be transformed nor published

as draft by this customization. When a document is published as draft, only metadata elements that are supported for

editing via the metadata editor (Task 3) will be persisted.

Task 5 FGDC to EIP v1.0 Metadata Transform Capability The Geoportal Server will be customized via a Deployment File to transform metadata records from FGDC to the EIP v1.0 profile upon upload/harvest, and then publish them to the geoportal. Items that do not pass EIP v1.0 validation after transformation will be published to the geoportal in draft form, meaning that they will not be discoverable through search but can be edited through the Geoportal metadata editor (see Task 3) to be made valid. This task includes internal testing of the Energistics-provided transformations and their integration with the customizations to support EIP v1.0 XML validation as described in Task 3. This task also includes an assessment of the feasibility of chaining together transformations (e.g., FGDC to ISO 19115:2003, then ISO 19115:2003 to EIP v1.0 XML). This task will leverage the work described in Task 4 as a base for developing the same behavior for the ‘Draft’ statusing of documents that fail validation after transformation from FGDC to EIP v1.0 XML.



Esri Deliverables Esri Geoportal Server Deployment File that includes customizations for transforming

FGDC metadata to EIP v1.0 metadata, and documents that fail validation after transformation will be published as draft.

Energistics Responsibilities Provide the transformation xslt from FGDC to EIP v1.0 – or alternatively, an xslt that

transforms FGDC to ISO 19115:2003, and the xslt work from Task 4 can be leveraged to transform the ISO 19115:2003 to EIP v1.0, at least five business days prior to the start of the task.

Provide written acceptance of the customized deployment file per guidelines in Section 3.2.

Assumptions Metadata documents that are not FGDC will not be transformed nor published as draft by

this customization When a document is published as draft, only metadata elements that are supported for

editing via the metadata editor (Task 3) will be persisted Task 6 Metadata Publishing Training for Geoportal Implementation This task consists of a two-hour training webcast, to be recorded by Energistics, where the first hour is instruction on publishing and managing metadata in the Esri Geoportal Server, and the second hour encourages users to publish records and ask questions as they work through the publishing process. In this training session, the Energistics Metadata Work Group and Esri staff will collaborate to prepare training that will educate a larger audience (e.g., may include delegates from the project’s sponsor organizations) on how to create EIP v1.0 metadata, publish it to the geoportal, and manage it once published. This training will be a remote webcast, which will be recorded by Energistics, and can represent a progress presentation for the development work done at that point in the project. The Esri project manager will work with the Energistics Metadata Work Group to finalize an Agenda and submit it to the Energistics project manager three business days prior to the meeting.

Esri Deliverables Training Agenda submitted to Energistics project manager three business days prior to

meeting. One two-hour training webcast on Geoportal Server metadata publishing/management

topics.



Energistics Responsibilities Ensure that a Geoportal Server implementation with project-related customizations that

have been implemented at that point is running and available to Energistics participants. Ensure that appropriate Energistics project team members and possibly sponsor-delegated

staff are available and participate in the training. Record training webcast. Advertise the training to staff.

Assumptions The training will be conducted remotely via conference line and webcast, and may be

recorded by Energistics if desired. Task 7 CSW Clients for ArcMap Customizations to Support EIP v1.0 Users

(Optional) The CSW Clients for ArcMap will be customized to include preset configurations to a specific set of CSW endpoints, including the EIP v1.0-compliant Prototype Geoportal. The list of endpoints will be provided to Esri by Energistics at the start of work on this Task, and will include network nodes the Energistics geoportal plans to search. The CSW Client will allow for query on EIP v1.0 metadata elements as defined in the Task 3, and through the CSW Client users will be able to retrieve EIP v1.0 metadata documents from the EIP v1.0-compliant Prototype Geoportal. It is important to note that other CSW endpoints to which the CSW Client is configured to connect may support additional metadata profiles; the CSW Client will retrieve metadata from those endpoints regardless of the profile as long as they match the searchText criteria. The CSW Client does not do the transformations described in Task 4 and 5; e.g., if a network catalog only contains ISO 19115:2003 metadata, and the metadata matches the searchText query from the CSW Client, the user will retrieve ISO 19115:2003 metadata. The CSW Clients installer will be customized such that the designated network endpoints will be included by default upon installation by the user. The installation workflow will be the same as described in the CSW Clients installation documentation1, and is distributable to any EIP user.

Esri Deliverables A custom CSW Client for ArcMap add-in that includes configurations for the specified

CSW endpoints.

1 See documentation at http://sourceforge.net/apps/mediawiki/geoportal/index.php?title=Geoportal_CSW_Clients



Energistics Responsibilities Provide list of CSW endpoints to which the CSW Clients should be configured to

support, at least five business days prior to the start of the task. Provide written acceptance of the customized CSW Clients per guidelines in Section 3.2.

Assumptions Users will need to have ArcGIS Desktop 10.0 licensed and installed before applying the

CSW Clients. CSW endpoints provided by Energistics for configuration support the OGC CSW 2.0.2

specification. Endpoints that are down or not responsive cannot be searched by the CSW Clients. Changes to the user interface of the CSW Clients will not be included in this

customization work. Task 8 ArcCatalog 10 Customizations for EIP v1.0 Metadata (Optional) Esri will provide up to 34 labor hours for an Esri Consultant and eight labor hours for a GIS Technical Specialist/Engineer to work towards the following customizations to ArcCatalog 10:

• An ‘EIP v1.0’ metadata style1 for viewing and editing metadata • Inclusion of EIP metadata elements and codelist values in the ArcCatalog ArcGIS

Metadata editing environment so users can author EIP metadata • Export metadata created/edited in ArcCatalog to an EIP v1.0-compliant XML

document • Installer that installs EIP v1.0 ArcCatalog configuration in an ArcGIS 10 SP4

environment This task will be executed on a time and materials basis to allow flexibility to pursue these customizations, test, and adjust the implementation in accordance with feedback from Energistics. If these customizations are completed with time remaining, additional customizations may be pursued or the hours can be moved to Task 11 activities.

Esri Responsibilities Provide up to 42 hours of remote support for the activities described above.

Energistics Responsibilities Ensure that appropriate staff are available for contact by Esri staff.

1 http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Choosing_a_metadata_style/003t00000009000000/



Assumptions Codelists in the ArcCatalog Metadata Editor will not be dynamically generated from the

codelists online (referenced in Task 3) but from a list of domains defined in the ArcCatalog configuration files.

Customizations will be compatible with ArcGIS Desktop 10 SP4. Initial work will not include customizations to the look and feel of the ArcCatalog

Metadata Editor interface but will use the out-of-the-box look and feel; if the identified tasks are completed with hours remaining, Energistics can decide to leverage the remaining time to pursue look and feel customizations.

Customization activities will be conducted remotely by Esri staff. Task 9 Energistics Community Workshop – Energistics-hosted in Houston

(Optional) This workshop uses the Esri Geoportal Server 3 Day Jumpstart Service to provide up to three business days of onsite Esri Geoportal Server support by one Esri consultant. This package offers the flexibility to provide not only a training workshop on the implemented EIP v1.0-compliant Prototype Geoportal, but also the ability to investigate further enhancements, configurations, and/or workflow discussions. Onsite time may be shifted between activities if more support is needed during any one activity, but the maximum number of three days onsite is fixed. It is envisioned that the workshop will be conducted in two parts, each spanning one day. The first part will be a technical training workshop focusing on installation, configuration, and customization topics. Customizations that support the EIP v1.0 as a result of this project will also be presented and discussed. The second part will be an end-user training that focuses on discovering resources through the EIP v1.0-compliant Prototype Geoportal, and how to create, edit, and publish EIP v1.0 metadata through the geoportal. The remaining day will be used for discussions relating to further enhancements, configurations, workflows, or other geoportal and EIP-related topics of interest. Energistics participants may attend either or both training workshops. They may also attend meetings and discussions that take place on the third day.

Esri Deliverables One Esri staff person onsite for three days for a workshop and other user-directed project

related activities.

Energistics Responsibilities Work with Esri staff to develop and approve an agenda for the three days onsite

workshop.



Ensure that appropriate staff participates in the workshop during relevant times per the agenda.

Provide appropriate meeting facilities for the workshop.

Assumptions Training will take place in Houston, TX at facilities provided by Energistics. Users will interact with the implemented EIP v1.0-compliant Prototype Geoportal. Esri will prepare presentation materials, which will be provided to Energistics during the

workshop. Remote participation may not be facilitated at all parts of the workshop; therefore, remote

participants will be encouraged to participate the Follow-on Training Webcast (Task 9) instead.

Task 10 Follow-on Training Webcast (Optional) Because it is expected that not all users will be able to participate in the onsite training described in Task 9, a follow-on webcast will take place after the onsite training. This webcast will be four hours in length, can be recorded by Energistics if desired, and will cover more briefly the content covered in the onsite workshop.

Esri Deliverables A four-hour webcast conducted remotely by Esri staff to Energistics project participants,

with international dial-in provided.

Energistics Responsibilities Ensure that appropriate staff is able to participate the workshop. Advertise the workshop.

Assumptions

Webcast will be remote, hosted by Esri, and be a duration of four hours. Energistics may record the webcast if desired.

Task 11 Additional Consulting Hours (Optional) It is expected that both the ISO 19115-1 standard and the EIP v1.0 profile will mature and change during the course of this project. For this reason, Esri recommends that Energistics purchase additional consulting hours to be used at the end of the project to address potential updates to the customizations.



These hours can be purchased on a time and materials basis as the nature of the activities needed to update customizations can be varied. If updates are not necessary, Energistics could use the hours for additional support, customizations, or training as desired. Esri will provide up to ten labor hours for an Esri Consultant and twenty labor hours for a Senior Application Developer to work toward the following activities:

Identify requirements for change items Modifications of customized deliverables per this scope of work to address updates to the

ISO 19115-1 and/or EIP v1.0 profile Other customizations that would support the EIP v1.0-compliant Prototype Geoportal Tech transfer or additional training

Esri Responsibilities Provide up to 30 hours of remote support for the activities described above.

Energistics Responsibilities Ensure that appropriate staff are available for contact by Esri staff.

Assumptions

These activities will be conducted remotely by Esri staff.



4.0 Schedule Execution of the project will commence after funding has been obtained and the service contract between Energistics and Esri has been signed by both parties. As requested in the EIP Prototype Project Proposal, the project is envisioned to proceed in the following phases:

1. Project Kick Off and Onsite Technology Transfer a. This corresponds to Task 1 – ‘Project Initiation and Management’ and to Task 2 –

‘Geoportal Technology Transfer to Energistics’. b. Begin: At project start c. Duration: 1-2 weeks

2. Development/configuration of at least one EIP-compliant metadata editor and one

transform utility. a. This corresponds to proposed Tasks 3, and 4/5 – ‘Geoportal configuration to

identify, validate, and create EIP v1.0 metadata’, ‘ISO 19115 to EIP v1.0 Metadata Transform Capability’, and ‘FGDC to EIP v1.0 Metadata Transform Capability’, respectively

b. Begin: 3 weeks after project start c. Duration: 5 weeks

3. Delivery of the Metadata Publishing Training Webcast, with the Energistics Metadata

Work Group and sponsor organization staff. a. This corresponds with Task 6 – ‘Metadata Publishing Training for Geoportal

Implementation’ b. Begin: Planning should commence as development reaches its midpoint. c. Completion: As the training webcast may possibly include sponsor organizations

and their staff, the exact date would be determined by Energistics. Target for the webcast is shortly after Phase 2 development and testing is complete.

4. Development of remaining supporting applications and utilities. a. Esri envisions this will be the remaining metadata transformation, Task 7 – ‘CSW

Clients for ArcMap customizations to support EIP v1.0 users’ and Task 8 ‘ArcCatalog 10 Customizations for EIP v1.0 Metadata’

b. Begin: after completion of tasks in Phase 2 c. Duration: 4 weeks



5. Delivery of the Energistics Community Workshop with the Energistics Metadata Work Group.

a. This corresponds to Tasks 9 and 10 – ‘Energistics Community Workshop – Energistics-hosted in Houston’ and ‘Follow-on Training Webcast’

b. Begin: 8 weeks before Energy Community Workshop c. Completion: It is envisioned that this workshop will take place in early 2013.

There is an optional final phase which consists of work to upgrade the customized deliverables to the latest version of the EIP metadata profile, as discussed in Task 11, to be completed within the 2013 calendar year.



5.0 Project Team and Qualifications 5.1 Introduction The Professional Services organization at Esri includes over 600 technical, management, and administrative staff qualified to provide GIS support services to a broad range of user organizations throughout the world. This technical staff is composed of consulting, program/project management, data conversion/migration, and programming experts with extensive experience in using GIS as the core technology platform for business application integration. The Professional Services staff for this project work in the Spatial Data Infrastructure specialty, and - in addition to being well-acquainted with Esri’s Desktop, Server, and Web solutions and GIS technology - are also subject matter experts in implementing and maintaining systems for geospatial information sharing, standards-based service protocols, standards-based metadata, and inter-agency/international information collaboration. This team also manages the open source Esri Geoportal Server product and its contributing community. 5.2 Identification of Project Team This project consists of management, development, documentation, and knowledge transfer/training tasks. The formal assignment of staff will be made during the Project Planning process (Task 1), but it is expected that staff from the following roles will be participating throughout the project’s duration.

Project Manager Technical Lead Software Developer Instructor

Appendix B includes resumes for staff that are likely to be working on the project.



Appendix A— Documentation of Deliverables Shown below are the deliverables that Esri is addressing in this proposal. 1. An EIP v1.0-enabled instance of the Esri Geoportal open source software that will be

Energistics-owned. 2. Geoportal technology transfer to Energistics needed to support and maintain their system. 3. One or more client applications that allow users to search one or more of the catalogs via the

OGC CSW service, and present results in a user friendly way. (In addition to the web client included in the Esri Geoportal software, one that would see wide use is an Esri ArcMap client that enables users to search for web map services, inspect the metadata, and add the web service as a layer in ArcMap.)

4. A software application that enables creation of EIP v1.0 XML metadata records by transforming existing ISO 19139:2006 or FGDC XML records.

5. A software utility that validates XML records as compliant with EIP v1.0. 6. A web page (on energistics.org) that publishes EIP-specific code lists, and associated web

service that validates terms as EIP v1.0-compliant code list values. 7. A software application or configuration file for an existing application, that enables creation

of new EIP v1.0 XML metadata records. 8. Documented changes identified as improvements/fixes needed for EIP v1.1. 9. A public workshop to enable and encourage community adoption.



Appendix B—Proposed Staff Resumes Remainder of page left intentionally blank.



Highlights • Supported the NOAA NCDC, NODC, NGDC,

and CSC offices in implementing the Esri Geoportal Server

• Regular participation and presentation in open source software and data communities (e.g., FOSS4G and OpenStreetMap)

• Identified key next steps for USGS in their development of an Integrated Requirements Information System.

GIS Experience 5 years with Esri; over 8 years total with expertise in GIS and Spatial Data Infrastructure. Education • M.S. (Geography) University of South

Carolina, Columbia, 2007.

• B.S. (Geography) University of South Carolina, Columbia, 2002.

Christine White Project Manager/Consultant

Ms. White joined Esri as a consultant for the SDI Solutions Team in 2007. Ms. White has more than eight years of experience working with GIS, including experience in the analysis of geospatial data and how it is communicated within and between organizations. She supports project teams throughout the requirements, analysis, design, build, and rollout stages. She is also proficient with the PMI-based project management, and has requisite project management experience and skills. Accomplishments Ms. White has contributed to the development, testing, documentation, and marketing of the Esri Geoportal Server (formerly GIS Portal Toolkit and ArcGIS Server Geoportal extension) product. She has helped hundreds of users understand, implement, and customize the software. Ms. White has played a key role in helping customers at NOAA, USDA, Arizona Geological Survey, University of Alaska, and others get their geoportal implementations running successfully. In 2011, Ms. White spoke at two open source software conferences to share the story of how the Esri Geoportal Server transitioned from a project, to a product, to fully open source. Timeframe: 2007 - Current In 2011, Ms. White joined the ArcGIS Editor for OpenStreetMap project. She coordinates the development team and manages enhancements that enable Esri users to contribute to the OpenStreetMap database. She participated in the State of the Map Denver meeting, and is an active member of the OpenStreetMap community. Ms. White has worked closely with the USGS in the planning and prototype of their Integrated Requirements Information System (IRIS). The system will enable the USGS to manage data acquisition opportunities in light of current holdings, in-work projects, and program requirements. Timeframe: 2008 - Current Technical Capabilities Ms. White is familiar with metadata standards, open source solutions, data sharing technologies and protocols, GIS modeling, and cartographic visualization techniques. Ms. White is proficient with Esri Geoportal Server, ArcGIS for Server, Portal for ArcGIS, ArcGIS for Desktop and its extensions, ArcGIS Workflow Manager, metadata and data standards (such as OGC services, FGDC, ISO, Dublin Core, REST, and OpenSearch), and database management systems.

Work History



From 2006 to 2007, Ms. White was a GIS specialist and research assistant for the Institute for Public Service and Policy Research at the University of South Carolina, Columbia. She implemented a Web site using ArcIMS and scalable vector graphics to display South Carolina county economic indicators for public use. She also trained the staff in the use of geospatial technology to enhance their research and reports.

During 2006, Ms. White worked as a research assistant at the University of South Carolina for the National Academies of the Sciences on a project called Land Parcel Databases: A National Vision. She interpreted the results of an online survey conducted by the National Research Council investigating the further development of a nationwide cadastre. She also designed promotional materials for one of the Land Parcel Panel's summit meetings.

From 2005 to 2006, Ms. White was a research assistant for the Learning Center for Sustainable Living at the University of South Carolina. She promoted ecologically sustainable practices to students living in the Leadership in Energy and Environmental Design (LEED)-certified residence hall. She designed maps and promotional materials for use by the students.

During 2005, Ms. White worked as a GIS data analyst for the South Carolina State Climatology Office in Columbia. She selected the weather stations and assessed their data quality for a project that developed an interactive online mapping tool to weight drought indices.

From 2002 to 2005, Ms. White worked as an associate minister and administrative manager for the Shack Campus Ministry, University of South Carolina, Columbia. She initiated and coordinated programs for personal growth among young adults. She personally raised more than $40,000 for the organization through networking with individuals and churches. She presented material to students in large and small groups, individually, and in written correspondence. She administered the operation's budget and devised systems for managing data pertaining to those associated with the organization.

From 2000 to 2001, Ms. White worked as an assisting climatologist and data manager for the Southeast Regional Climate Center in Columbia, South Carolina. She managed certifiable climate data for more than 1,000 weather stations across 13 southeastern states, composed creative resources for a K–12 education Web site, and collaborated with senior climatologists analyzing long-term phenomena like the effects of drought and El Niño.

Employer Position title Position Dates Esri Project Manager/Consultant May 2007 - present

Institute for Public Service and Policy Research at the University of South Carolina

GIS specialist August 2006 – May 2007

University of South Carolina and National Academies of the Sciences

Land Parcel Databases: A National Vision project

March – July 2006

Learning Center for Sustainable Living at the Research Assistant August 2005 – May 2006



University of South Carolina

South Carolina State Climatology Office GIS Data Analyst May- August 2005

Shack Campus Ministry, University of South Carolina

Associate Minister and Administrative Manager

May 2002-October 2005

Southeast Regional Climate Center, Columbia, South Carolina

Assisting Climatologist and Data Manager

January 2000 – January 2001

Continued Professional Development Professional Activities

• InterNational Committee for Information Technology Standards, 2011-present • Participation through Esri membership in Earth Science Information Partners, 2010- present • Member, American Geophysical Union, 2010-2011 • Member, Association of American Geographers, 2005–07.

Presentations

• White, C., and Yuanjie Li, 2011 (January), “Geoportal Server: Open Source Software for Data Discovery and More,” ESIP Winter Meeting, Washington DC.

• White, C., 2011 (September), “From Project, to Product, to Open Source. Now What?” FOSS4G, Denver.

• White, C., 2011 (July), “Discover and Share Spatial Resources on the Web,” OSCON Data, Portland.

• Dollison, R., L. Batten, T. Clark, and C. White, 2011 (August) “Base Data for Earth Science: The National Map and ArcGIS.com Future Directions,” USGS CDI Conference, Denver.

• White, C., 2011 (June), “Esri Geoportal Server,” NOAA 2011 Environmental Data Management Conference, Silver Spring.

• White, C., 2010 (December), “Geo-enabling Science through Web Services,” American Geophysical Union Fall Meeting 2010, San Francisco.

• White, C., 2010 (July), “Exposing Data with Web Services,” ESIP Summer Meeting, Knoxville. Academic and Professional Achievements

• Recipient, Cynthia MacCharles Memorial Award for Global Spatial Data Infrastructure (GSDI)-9, Santiago, Chile, 2006.

• Recipient, Julian J. Petty Award for Excellency in Scholarship, University of South Carolina,

Columbia, 2002.

• Graduation Magna Cum Laude, University of South Carolina, Columbia, 2002.

• Recipient, Donald O. Bushman Award for Cartography, University of South Carolina, Columbia, 2001.

Publications

• White, Christine, 2007 (May), "The Transfer of Spatial Data in South Carolina through the Lens of Annexation," Master's Thesis, University of South Carolina, Columbia.



Training • “Essentials of Project Management,” Knowledge Structures, Inc. 2011 • “Professional Selling Skills,” Achieve Global, 2011. • “Developing Applications w/ ArcGIS Server Using the Java Platform” Esri Learning Center, 2009.



Highlights Mr. MacGillivray has been extensively involved in the development of a public Internet portal (http://gos2.geodata.gov/wps/portal/gos) for maintaining and searching GIS metadata records at the U.S. national, state, and local levels. GIS Experience 23 years with Esri; over 25 years total with expertise in GIS. Education • Diploma (Geographic Information Systems)

College of Geographic Sciences, Lawrencetown, Nova Scotia, 1988.

• B.Sc. (Physics), Dalhousie University, Halifax, Nova Scotia, 1983.

Urban MacGillivrayApplications Software Engineer

Mr. MacGillivray joined Esri's Professional Services Division as an applications programmer in 1989. He earned his diploma in geographic information systems from the College of Geographic Sciences, Nova Scotia, Canada, in 1988 and his B.Sc. in physics from Dalhousie University, Nova Scotia, Canada, in 1983. He has more than 19 years of experience in GIS programming. Accomplishments As an applications software engineer, Mr. MacGillivray is responsible for the design, coding, and implementation of ArcGIS systems. He is directly involved in reviewing clients' GIS functional requirements, database design, consulting, software and user interface design, software coding and quality assurance, end user document development, and software installation and training. Mr. MacGillivray is presently involved in the development of the ArcGIS Server Geoportal extension. The application will serve as a basis for the collection and discovery of GIS related data and services for national governments, state governments, and multinational corporations. Mr. MacGillivray has been extensively involved in the development of a geospatial clearinghouse for the State of Mississippi. The application centers on the distribution of spatial datasets through the Internet. Mr. MacGillivray has been extensively involved in the development of a geodata gateway for the U.S. Environmental Protection Agency. The application centers on the cataloging of GIS related metadata across the multiple regional offices of the EPA. Mr. MacGillivray has been extensively involved in the development of an enterprise land use planning system for the U.S. Bureau of Land Management. The application centers on the development of planning documents and scenarios and the Internet presentation of these plans for public comment. Mr. MacGillivray has been extensively involved in the development of an Esri Business Information Solutions Web site. The Web site is an e-commerce site focused on the generation of maps and reports associated with the demographic profile of customers surrounding a business location. Mr. MacGillivray was responsible for the development of an Internet-based demographic analysis application for ADVO, Inc. This application supports demographically targeted direct mailing. Technical Capabilities Mr. MacGillivray is experienced with Java, .NET, C++, XML, HTML, Javascript, AJAX and related technologies. He has extensive experience with both Internet and desktop software applications. He has experience with relational databases, such as Oracle, SQL Server, and Informix, and in a variety of UNIX and Windows operating systems. He has in-depth knowledge of the Esri software product line.



Work History In 1988, while at the College of Geographic Sciences, Mr. MacGillivray was involved in a cooperative program with the Surveys and Mapping Branch of Energy, Mines, and Resources in Canada. He wrote a translator between the Canadian Council of Surveying and Mapping digital file format and ARC/INFO. Program modules were written in FORTRAN 77 on a Prime 750 computer. All ARC/INFO file input/output was performed using existing system routines established by Esri. While attending Dalhousie University, Mr. MacGillivray performed summer fieldwork for the Geodetic Survey of Canada.

Employer Position title Position Dates Esri Applications Software Engineer 1988 - Present

College of Geographic Sciences GIS specialist 1988



Appendix C—Esri Master Services Agreement (E115M 6-09)

Remainder of page left intentionally blank.