1 Port of San Diego Journey to the Cloud AITP November 13, 2014 1.
-
Upload
hugh-oliver -
Category
Documents
-
view
212 -
download
0
Transcript of 1 Port of San Diego Journey to the Cloud AITP November 13, 2014 1.
- Slide 1
- 1 Port of San Diego Journey to the Cloud AITP November 13, 2014 1
- Slide 2
- Agenda About the Port Goals Driving factors Overall benefits/challenges Cloud solutions Subscriptions Infrastructure Applications Internet of Things 2
- Slide 3
- The Ports Jurisdiction The Port encompasses 2,403 acres of land and 3,535 acres of water. Five cities: Chula Vista, Coronado, Imperial Beach, National City and San Diego 3
- Slide 4
- Tidelands Trust Act 1962 Details Ports responsibilities Directs Port to manage San Diego Bay and the Tidelands Port must promote commerce, navigation, recreation and fisheries 4
- Slide 5
- Port by the Numbers About 527 employees 123 are sworn Harbor Police Officers 11 departments Fiscal Year 2014/2015 budget: Total Budgeted Operating Revenue: $141.8 million Real estate: $87.2 million Maritime: $36.2 million Harbor Police: $14.6 million Other: $3.8 million 5
- Slide 6
- Governance through a Seven-Member Board of Port Commissioners 6 Chair Ann Moore Secretary Marshall Merrifield Dukie Valderrama Chairman Bob Nelson Vice Chair Dan Malcolm Rafael Castellanos Robert Dukie Valderrama Garry Bonelli Ann Moore
- Slide 7
- 2011 Technology Environment 7
- Slide 8
- 8
- Slide 9
- Technology Strategic Plan Outsourcing Model 9
- Slide 10
- Goals Increase implementation response time Increase user acceptance Minimize complexity Minimize administration Decrease resources staff, hardware Decrease dependency on highly technical skill sets 10
- Slide 11
- Drivers Hiring freeze Limited budget Large number of new systems Complexity/Lack of standards 11
- Slide 12
- Overall Benefits Minimal additional infrastructure Minimal administration Standard processes Shortened implementation time Shorter learning curve Built in backup and disaster recovery 12
- Slide 13
- Overall Challenges Bandwidth Lack of integration Limited functionality Easy for end users to acquire 13
- Slide 14
- Other things SSAE16 Compliance Who owns the data Exit Strategy 14
- Slide 15
- Subscriptions 15
- Slide 16
- Infrastructure As A Service 16
- Slide 17
- Software As A Service 17
- Slide 18
- Software As A Service 18
- Slide 19
- 19 Internet of Things
- Slide 20
- 20 Energy Supply Roundtable 20
- Slide 21
- 2014 Technology Environment 21
- Slide 22
- 22 Deborah Finley [email protected]