Statement of Work for Web Content Management System.doc
DOC document 84 KB Posted
- Attached to
- Web Content Management System
- Solicitation number
- EOKWK1RH111
- Issued by
-
Defense Finance and Accounting Service
About this file
Statement Of Work for Web Content Management System
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Web Content Management System Q A.doc | DOC document | |
| Content Management System RFQ.doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Statement of Work
Content Management System for use by public website, www.dfas.mil
1.0 Introduction
The Defense Finance and Accounting Service (DFAS) is in the process of rewriting and reorganizing its web content to increase value to the customer. The agency will acquire a web content management system (CMS). The CMS will provide an interface for a content management team with various technical ability to load text, images, documents, etc to a public facing website. Software support will be included.
2.0 Objective
The purpose of this announcement is to develop a short list of the most suitable web CMS products for DFAS Technical Service Organization (TSO) to deploy on the host servers. The CMS will allow users to load web content and submit finished pages for approval through a workflow process before pushing to the live website.
3.0 Required information
All submissions must include the following, required items:
| Submission Requirement |
| Description |
| 1. The completed system requirements worksheet |
| Based on the description of the requirement, the vendor must use the requirements worksheet to indicate whether the requirement is satisfied by a standard feature of their Web CMS product |
· If so, indicate the feature that satisfies the requirement
· If not, whether or not the product can be customized to meet the requirement
· A description of the feature or customization that will meet the requirement
| 2. List of technical system requirements |
| Identify which technologies are supported by the Web CMS (Web server platform(s), database platform(s), etc.) |
3. Cost estimates for Web CMS solution licensing / support
The cost estimate shall include the following line items (at a minimum):
· Software licensing cost (include cost for tiered licensing options if applicable)
· Software support/maintenance subscription cost
| 4. List of federal customers |
| If applicable, the vendor shall furnish a list of federal clients that includes: |
· The name of the federal agency
· An agency contact
| 5. Additional Web CMS features/benefits |
| If applicable, the vendor shall provide descriptions of additional features their Web CMS tool has that may be useful to DFAS. |
4.0 Web CMS requirements
| Configuration Requirement/Feature |
| Description |
| 1. Section 508 compliance |
| The Web CMS user interface and the content produced can be easily made 508 compliant, Section 508 standards outlined here: http://section508.gov/index.cfm |
| 2. Role based access to Web CMS authoring features |
| The Web CMS shall support role-based access control to features in the Web authoring interface, by the site administrators. |
| 3. De-coupled content production and delivery |
| The Web CMS must support the separation of Web content production and maintenance from the delivery of that content via the production Web servers. |
| 4. Multiple levels of website permissions |
| The Web CMS must support of role-based access control to websites, areas within websites, and areas of pages |
| 5. Secure website support |
| The Web CMS must support: |
· The creation of password protected websites/extranets
· Secure internet protocols
· Secure authentication, including certificate based authentication.
| 6. Support for Active Directory and/or LDAP |
| The Web CMS shall support the following: |
· Website groups and group permissions will be managed by the Web CMS and allowed access to authorized users
| 7. Browser-based publishing and administration |
| The Web CMS must support the use of IE 6 and above, and Firefox 3.6 and above as the system authoring and administration client. |
| 8. Customizable DFAS Web templates (DFAS will develop its templates) |
| The ability to customize multiple, customizable templates for the generation of Web content for each Web environment (internet, intranet and extranet), and at the various sub-levels of those environments |
| a. Centralized template management |
| Once implemented the templates shall have the following features: |
· The ability to change any of the templates and have those changes reflected in all pages that are using it
· Includes Agency standard metadata (see metadata requirement below)
| b. CSS-based design |
| All generated Web content must: |
· Render the same in IE (6 and newer), Firefox (3 and newer),
· Use CSS layout and positioning (no table-based layout)
· Be Section 508 compliant (see above)
| c. Landing/Organizational pages |
| Landing/Organizational pages are pages that serve as a single point of departure page for all content related to a certain topic or DFAS organization. |
· Administration of these pages will be assigned to the appropriate content manager (role based)
| 9. Integrated DFAS metadata standard |
| Each page shall include metadata tags and metadata descriptions |
| 10. Asset repository |
| The Web CMS shall include an asset repository that allows Web authors to: |
· Reuse assets across the website
· Associate user-defined metadata with asset files stored in the repository
· Search for relevant assets based on their metadata
| 11. Embedded page navigation based on the page’s position in the Web IA |
| The Web CMS shall include standardized navigational modules on all page templates. These navigation modules cannot be directly edited by the Website administrator and developer. They can only be altered by repositioning the content. The navigation modules include: header, footer, top level, left hand, breadcrumbs and ad-hoc links from within the page content. Creation of new pages automatically populates the top level and left hand navigation. |
| 12. Comprehensive link management |
| The Web CMS shall allow for the management of internal and external links. |
| a. Internal links |
| The Web CMS shall allow for the management of links internal to a Web CMS managed website by allowing Web authors to: |
· Relocated target content and have the updated URL reflected in all links to the target content
· Update a URL and have the update reflected in all references to the URL
| 13. Fully customizable work-flows |
| The Web CMS shall allow for: |
· Custom work-flow management by the DFAS website administrator (all site areas)
· An auto-generated email notification for page review/approval
· Tracking of comments in review/approval process
| 14. Product Documentation |
| The Web CMS vendor shall provide: |
· Full product documentation including:
· System set-up, configuration and maintenance
· API reference
· A list of 3rd party documentation or text are available for their Web CMS tool, if available
| 15. Site map generation |
| The Web CMS tool shall support the generation of an site map |
| 16. Import/Export Feature |
| · The Web CMS shall have an import/export feature that allows migration of website from one host to another. |
| 17. RSS Feeds |
| The Web CMS shall have an RSS feature that allows end users to subscribe to DFAS website content at the page, subject, or site level. |
| 18. WYSIWYG Content Editor |
| The Web CMS shall have a What you see is What you get (WYSIWYG) editor that provides inline content editing. The editor shall include the following content types: paragraph content, frequently asked questions, and images. The editor shall the option to toggle back and forth to source code. |
| 19. Multimedia content support |
| The Web CMS shall allow Web authors (or administrators) to add multimedia (YouTube video, QuickTime, Flash, etc.) on Web pages in a consistent, standardized manner. |
| 20. Custom application development framework |
| The Web CMS must have a framework/API that allows for the development of custom modules. The vendor shall indicate which language(s) are supported and commonly used with the API. |
21. Data display pages
The Web CMS shall allow non-technical users (using a wizard or similarly intuitive feature) to create pages that display data from a back-end data store.
22. User technical ability
The web CMS shall provide an interface that is easy to use for non-technical (non developer) types.
| 23. Cross-platform compatible |
| The web CMS shall be certified with multiple operating systems, including Solaris 10 operating system and Windows 2003 and above. |
| 24. Built-in search engine |
| The Web CMS shall contain an integrated search engine function. |
| 25. Add-on modules |
| The Web CMS shall allow for vendor supplied or 3rd party add-on modules. |
5.0 Security requirements
Vendor will ensure CMS meets required IT clearance for use on government hardware.
6.0 Standards
The CMS must be fully compatible with JAVA 1.6.x, Apache Tomcat 6.x and above, Oracle 11g Database, and the Solaris 10 Operating System.
7.0 Support
Vendor will provide support to ensure software install is successful with DFAS TSO – Corporate Services (TSO-CS) organization. Customer Service support available during normal business hours with a 48-hour reaction time.
File details come from the government source that posted it. Updated .