Monday 12 November 2012

What's in a support proposal

Slim line look at what’s should be in a support proposal. Not always necessary in the below order, but in general. << Just meant to serve as guidance, not a template >> Overview Scope of Work Requirements Coverage Your value proposition Getting down to the bottom of it Server Builds LAN and WAN Configuration and Access Control Application Deployment Monitoring and Alerting Backup and Recovery IT Health Checks Delivery Approach UAT Basic OAT Post Delivery Project Team Support Post Delivery Hardware & O/S Maintenance and Support Governance and Technical Direction Exclusions Risks, Assumptions, Issues & Dependencies Outline Transition Phase Change Control Process Change Impact – Impact Overview, (Impact score (1 = low, 5 = high, tick one box in each row) Impacted Area 1 2 3 4 5 Business Criticality Business Operation Architecture Technical Performance Design & Build Complexity Operational Complexity People Process Documentation ) Impact on Service, Impact on Products, Parties impacted, Impact Level, Timescales Impact Cost Impact Your Case Studies Focus on Business Sector, The project/program/application in question Consider Locations – Onsite, Offshore Study the client’s past awarded contracts – pitfalls and successes << Just meant to serve as guidance, not a template >> ..........................................................................Goodluck!!!