View
46
Download
6
Category
Preview:
DESCRIPTION
Interlab 2003 November 6, 2003. DOE’s Implementation of a CMS for Energy.gov. www.energy.gov. Getting from here…. …to there. The Task. Redesign Energy.gov Reorganize Site Content Improve Search Engine Implement a Content Management System Implement a Taxonomy - PowerPoint PPT Presentation
Citation preview
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Interlab 2003 November 6, 2003
DOE’s Implementation of a CMS for Energy.gov
Interlab 2003 November 6, 2003
A CMS for Energy.gov
www.energy.gov
Getting from here……tothere.
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Task
• Redesign Energy.gov
• Reorganize Site Content
• Improve Search Engine
• Implement a Content Management System
• Implement a Taxonomy
• Plan for a roll-out to other DOE entities
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
1. Get DOE Buy-in
2. Define Roles and Responsibilities
3. Establish Technical Infrastructure
4. Create templates / pages
5. Develop / Convert Content
6. Develop a Taxonomy
7. Implement / Test / Deploy
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
1. Get DOE Buy-in
• The Committee– 34 DOE staff members representing a cross-
section of the organization– Questionnaires– Initial planning sessions– Responses:
• Support• Indifference• Skepticism• Enthusiasm• Hostility
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
2. Define Roles and Responsibilities
• Create a Content Team
• Working Relationships: IT / Multiple vendors
• Management v. Web Staff
• CMS is a New Animal: Who’s Who?
• Decision-makers
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
3. Establish Technical Infrastructure
• Requirements– Web Server– Application Server– Database– CMS Software– Search Engine
• Test / Staging / Production
• Roles and Responsibilities
• Acquisition of HW / SW
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
4. Develop Templates / Pages
• Magic!• Magic…?
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
4. Develop Templates / Pages
• Magic…?• Programming
• HTML Templates
• JSPs
• Wiring to Admin / Authoring Engine
• Wiring to Display Engine
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
4. Develop Templates / Pages
• Content Management Wiring– Templates
• Content “Chunks”
– Users• Authors, Editors, Approvers, Admins
– Workflows• Steps in the Publishing Process
Interlab 2003 November 6, 2003
A CMS for Energy.gov
TILES
- “Content Containers”
- Reside within Layouts
- Page or section-specific
- Reusable
LAYOUTS
- Some have editable “behaviors.”
Interlab 2003 November 6, 2003
A CMS for Energy.gov
TILES
LAYOUTS
Group tiles to use with Workflows
Workflows relate to groupings of content
Workflow 1
Workflow 3
Workflow 2
Author 3
Author 2
Author 1
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
5. Develop / Convert Content
• “Moveable” Content
• New Content
• Disposable Content
• Formats and Formatting
• Automating Conversion
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Content Plan
6. Develop a Taxonomy
• What is a Taxonomy?
• Office of the CIO Taxonomy
• “A to Z list”
• Topics
• Offices and Facilities
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Plan
7. Implement / Test / Deploy
• Roles and Responsibilities
• Testing– Functional– System– Regression– Stress– Acceptance
• Deployment: An Environmental Concern– Testing / Staging / Production
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
…? Develop / Convert Content
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
IT Words to Live By:
• Expect the Unexpected
• Plan for Failure
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
…? Develop / Convert Content
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
…? Develop / Convert Content- No Web team established (Cost not built into
project)- Dependence on others caused delays- No plan for automating conversion
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
…? Develop / Convert Content
…? Define Roles and Responsibilities
…? Establish Technical Infrastructure…
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Remember…:
• Expect the Unexpected
• Plan for Failure
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
3/1/20032/17/2003 3/31/2003
Establish Technical Infrastructure• Acquisition of HW / SW
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
3/1/20032/17/2003 3/31/2003
Establish Technical Infrastructure• Acquisition of HW / SW
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
3/1/20032/17/2003 6/1/2003
4/1/2003 5/1/2003
Establish Technical Infrastructure• Acquisition of HW / SW
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the PlanEstablish Technical Infrastructure• Acquisition of HW / SW
6/2/2003 6/20/2003
3/1/20032/17/2003 6/1/2003
4/1/2003 5/1/2003
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
Develop / Convert Content
…? Define Roles and Responsibilities
Establishing Technical Infrastructure delay =
- System Configuration delay- CMS Software Deployment delay- Training delay- Content Entry delay
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
…? Develop / Convert Content
…? Define Roles and Responsibilities
Establish Technical Infrastructure
• Implement / Test / Deploy
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Murphy’s Law:
• Program Manager Change Shortened Deadline
• Timeline Crunched
• Content Creation Fell Behind, Delaying Testing
• Other IT Projects Demanded Resources
• The Site Launched …
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Murphy’s Law
A driver incompatibility between application server and search software…
…the site was slow due to connection pooling issues…
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Murphy’s Law
A high-visibility public site with multiple players and something goes wrong…
…? Define Roles and Responsibilities• Fingers Pointing• Hands Wringing• Too Many Fingers In the Pie• Multiple Solutions Tried• Testing Needed• IBM, Oracle Contacted…
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
A driver incompatibility between application server and search software…
…was resolved.
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Redesigned the Site
Got DOE Buy-in
Wired the Templates
Developed a Taxonomy
Developed / Converted Content
Defined Roles and Responsibilities
Established Technical Infrastructure
Implemented / Tested / Deployed
Launched and Relaunched
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Executing the Plan
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
• Manage Your Project
• Be a Team
• Give Too Much Time to Content Conversion
• Know Your Software
• Clarify Roles and Responsibilities
• Document Everything
• Expect the Unexpected
• Plan for Failure
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
Manage Your Project
• Set Reasonable Goals
• Use a Phased Approach
• Regard Each Project Element As a Project
• Can My CMS Make My Coffee?
• Be a Team
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
Give Too Much Time to Content Conversion
• Analyze Your Content Carefully
• Be Ready To Jettison Outdated Content/Methods
• Look for Automated Conversion (*but be careful)
• Clarify Roles And Responsibilities
• Staff Up To Handle The Job
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
Know Your Software
• What’s New?
• How Will This Change Our Processes?
• Be Sure Your Vendor Can Tell You What Is Really There
• Exception Handling
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
Clarify Roles and Responsibilities
• Decision Makers
• Publishing Staff, Authors, Admins
• System: Staff, IT, Vendors
• Figure It Out Up Front
• Communicate Weekly (at least!)
• Document Everything
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Lessons Learned
Document Everything
• Statements of Work (SOW)
• Change Control
• Roles and Responsibilities
• Technical Documentation
• Training
• Updates and Upgrades
Interlab 2003 November 6, 2003
A CMS for Energy.gov
The Good News
It Works…
…If You
• Manage Your Project
• Expect the Unexpected
• Plan for Success
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Interlab 2003 November 6, 2003
A CMS for Energy.gov
Recommended