The Web ProblemThe Web Problem
The website as it stands now does not makeuse of the current available technology,support or security that allows two-waycommunication or online transactions.
GoalGoal
Modern website supporting onlinetransactions and two-way communicationwith customers.
StakeholdersStakeholders
Board Members, Staff and Management
Licensees
Public
Industry Professionals (Credentialing, etc.)
State Oversight (GITA, SPO, GAO, etc.)
ObjectivesObjectives
Define architecture
Obtain new website hosting solution
Prepare business process documentationand in-house design
Partner with outside vendor for onlineimplementation (application development,interfacing with internal systems, etc.)
Define Architecture:Define Architecture:
Options:
–Self-hosting
–Co-location
–Managed Hosting
–Shared Hosting
Architecture OptionsArchitecture Options
Self-hosting: Establish web server in ourown office, on our own network.
–Pros: Complete control – immediate responseto agency needs and changes, managedalongside our internal systems.
–Cons: Complete responsibility – hardwareprocurement and maintenance, environmentalcontrol, physical and network security, drain onbandwidth and other resources, etc.
Architecture OptionsArchitecture Options
Co-location: Provide agency-owned server in anoutside vendor’s datacenter.
–Pros: Nearly complete control – agency owns andoperates hardware and software; vendor provides space,environmental control, physical security, networkbandwidth.
–Cons: Nearly complete responsibility – little or novendor monitoring or support; response time increaseddue to physical distance from server; same procurementand maintenance requirements as self-hosting.
Architecture OptionsArchitecture Options
Managed Hosting: Vendor supplies and maintainshardware and basic software at the vendor’sdatacenter.
–Pros: Flexibility of control – vendor monitorshardware, software and security 24/7; providesbandwidth, environmental controls, backup units;outsourcing expertise available on demand.
–Cons: Greater monthly cost, reliance on vendor’s SLA(service level agreement).
Architecture OptionsArchitecture Options
Shared Hosting: Vendor provides space on server,shared among several different “tenants.”
–Pros: Lower cost, vendor provides all basic serverrequirements.
–Cons: Little control of anything, limited technicalcapabilities; competition for hardware, software,bandwidth and other resources; 3rd party applicationsfor other customers may reduce our uptime; our growthmust also accommodate others on same web server.
RecommendationRecommendation
Managed Hosting provides the best balancebetween cost, flexibility and maintenanceresponsibilities.
Objective 2Objective 2
To bring the BOMEX website to a newserver that offers us the ability to growtechnologically while offering us the service,security and backup that we need.
Vendors ConsideredVendors Considered
IBM
ADOA
STG
Vendors ConsideredVendors Considered
IBM
–Pros: Name recognition, reputation for quality,24/7/365 monitoring and support, highestuptime, capacity for growth, outsourcingexpertise, Tier 1 datacenter.
–Cons: Price, flexibility.
Vendors ConsideredVendors Considered
ADOA
–Pros: Price.
–Cons: Incorrect software, can’t use their SQLserver, questionable uptime and availableresources, have to purchase hardware (would bethe same as co-location without the benefits ofa real co-location vendor); poor reputation.
Vendors ConsideredVendors Considered
STG
–Pros: Price, security, 24/7/365 monitoring andsupport, high uptime, growth potential,personal service and consulting, small butprofessionally designed and equippeddatacenter (former US West facility).
–Cons: Little name recognition, smaller lower-tier vendor.
RecommendationRecommendation
STG currently provides the best balance ofcost, quality, and personalized service. A12-month contract meets immediate needswhile providing future flexibility.
Design and ImplementationDesign and Implementation
Two “tracks” run in parallel: Design andImplementation.
–First phase’s design leads to second phase’simplementation, etc.
Process has been designed in twelve-week(quarterly) increments, to balance workloadwhile closely monitoring progress andadjusting course as necessary.
Tracking ProgressTracking Progress
Bi-weekly meeting to be held one daybefore the Executive Staff meeting.
Monthly meeting with the ED to ensure theplan is on the envisioned path.
Coordination with Web Team.
Other meetings to be held as needed.