Deployment Model
Traditionally, organisations have opted to deploy IBM's WebSphere Portal in-house; and while there has undoubtedly been a high degree of success within WebSphere's market, all too many deployments have suffered from:
- inadequate resources to provide the necessary skills required of an effective WebSphere Portal deployment
- major cost and time overruns as the complexity of deployment projects exceed initial expectations
- failure to realise the full potential of a portal due to overly bureaucratic management.
The BPS fully hosted model removes those problems while ensuring you maintain full ownership of your WebSphere Portal environment.

Below is a table highlighting deployment models
| | | Current |
|
| | Traditional Software | ASP/Hosted Model | SaaS BPS |
| Design Point | Built as a product for customer-premise deployment and management. Services are added on. | Reflects packaged software for Web hosting and remote management | Software and services integrated and delivered over the Internet. |
| Architecture | Install and manage each customer on an individual, dedicated instance | Typically installs and manages with customer on an individual instance | Multi-tenant model supports many customers on one license of code |
| Deployment | Moderate to lengthy (weeks to months to years)
| Moderate (weeks to months) | Short (hours, days to weeks) |
| Pricing Model | Customer buys: - Software license
- Hardware
- Middleware
- Implementation services
- Annual maintenance
| Customer buys: - Software licences
- ASP a subscription fee for hosting & management
| Customer buys: - Fixed cost implementation fee.
- Inclusive of subscription pricing for ongoing software, service, management etc.
|
| Upgrade Cycles | 12-36 months - Massive upgrades,
- Customer determines when to upgrade,
- Vendor maintains multiple versions
| 12-36 months - Controlled distribution through ASP
| 3-6 months - Smaller upgrades
- Automatically distributed to customer
|
| Customisation | Templates for tailoring, source code customisation | Templates for tailoring source code customisation | Policy-based, rules driven, self-service configuration wizards |
| Support and feedback cycle | - Often circuitous and piecemeal
- often through intermediaries (VARs SIs, etc)
| - Direct to ASP
- Indirect to ISV
| - Direct immediate support
- One-to-many Problem resolution
- High vendor accountability
|
To find out more about the benefits of SaaS, SOA and Web 2.0, contact us.