USMS Web CMS.doc
DOC document 241 KB Posted
- Attached to
- Web Content Management System
- Solicitation number
- DJMS-11-Q-0010
About this file
Request for Information Overview.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DJMS-11-Q-0010 RFI QUESTIONS AND ANSWERS.doc | DOC document | |
| USMS Web CMS HLA - DRAFT.PDF | ||
| USMS Web CMS Requirements Worksheet.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
Sources Sought – USMS Web CMS
USMS Web Modernization
Overview The U.S. Marshals Service (USMS) is in the process of revamping and reorganizing its Web content to better serve its internal and external web audiences. To that end, the agency is planning a series of projects to address various aspects of that plan:
1. Develop the USMS Web Content Taxonomy and Information Architecture (IA)
2. Develop a new look and feel for the USMS intranet and internet websites
3. Implement a Web content management system (CMS) The purpose of this announcement is to develop a short list of the most suitable Web CMS products/implementers for a USMS Web CMS – item 3 in the list above.
THIS IS A SOURCES SOUGHT ANNOUNCEMENT ONLY. This notice does not constitute a commitment by the government.
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
· A cost estimate for any required customization
| 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 implementation |
| 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
· Software installation and configuration (fit-to-business) cost
· Software customization cost (see item 1); programming language(s) used for the customization
| 4. Schedule estimate for Web CMS solution implementation |
| The schedule estimate shall include the following line items (at a minimum): |
· High-Level tasks
· Estimated time to complete
| 5. Cost estimate for a proof-of-concept/ functional prototype development |
| The cost and schedule estimate shall include the following line items (at a minimum): |
· A cost estimate for the development of a proof-of-concept (a functional test environment - vendor hosted) that demonstrates the required features and functionality
· Whether or not an evaluation copy of their software is available for on-site (USMS) proof of concept development
| 6. Schedule estimate for a proof-of-concept/ functional prototype development |
| The schedule estimate shall include the following line items (at a minimum): |
· High-Level tasks
· Estimated time to complete
| 7. 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
· A brief description of the federal customer solution
| 8. 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 USMS |
Web CMS Requirements
| Configuration Requirement/Feature |
| Description |
| Priority Level |
| 1. Alternate language/content support |
| The Web CMS shall have the ability to: |
· Display alternate language content, when present
· Display alternate format content, when present
· Display a text-only version of any page
· Dynamically augment website navigation when alternate content is present (e.g. “En Español” link)
FORMCHECKBOX
High
FORMCHECKBOX
Med
FORMCHECKBOX
Low
| 2. Section 508 compliance |
| The Web CMS user interface and the content produced must meet the Section 508 standards outlined here: http://section508.gov/index.cfm?FuseAction=Content&ID=12 |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 3. 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. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 4. Multiple site support |
| The Web CMS must support the publication of Web content to multiple websites (internet, intranet, and extranet) |
· A draft high-level architecture (HLA) concept diagram is included in this RFI package
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 5. 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. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 6. Multiple levels of website permissions |
| The Web CMS must support of role-based access control to websites, areas within websites, and areas of pages |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 7. Secure website support |
| The Web CMS must support: |
· The creation of password protected websites/extranets
· Secure internet protocols
· Secure authentication
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 8. Auto-generated, human readable file names (URLs) |
| The Web CMS shall support auto-generated file names based on website structure, Web content taxonomy position, or other mechanism. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 9. Support for Active Directory and/or LDAP |
| The Web CMS shall support the following: |
· Users will be retrieved from Active Directory or LDAP
· Website groups and group permissions will be managed by the Web CMS and populated with users from Active Directory or LDAP
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 10. Browser-based publishing and administration |
| The Web CMS must support the use of a Web Browser as the system authoring and administration client. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 11. Content expiration and delayed publication |
| The Web CMS must support automatic: |
· Content expiration – sunset dates
· Delayed content publication – “go-live” dates
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 12. Integrated USMS Web templates (USMS will develop its templates) |
| The ability to integrate 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)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| b. CSS-based design |
| All generated Web content must: |
· Render the same in IE (6 and newer), Firefox (3 and newer), Opera [versions]
· Use CSS layout and positioning (no table-based layout)
· Be Section 508 compliant (see above)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 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 USMS organization. |
· Topical content will be retrieved using metadata/ the taxonomy
· Organizational content will be retrieved using metadata/ the taxonomy
· Administration of these pages will be assigned to the appropriate Office Content Coordinators (role based)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| d. Site/sub-site index page based on Web content taxonomy |
| Site/sub-site index pages are automatically generated pages that display a complete topical hierarchy of the site or sub-site directories |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
13. USMS taxonomy (controlled vocabulary) integration (under development) The Web CMS shall have the ability to integrate the forthcoming USMS taxonomy - allowing:
· Web authors to select keywords from the linked taxonomy to categorize content/ populate keyword metadata tags.
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 14. Integrated USMS metadata standard |
| The USMS metadata standard is derived from the Dublin Core (DC) standard: http://dublincore.org/2008/01/14/dcelements.rdf# |
Each page shall include metadata that:
· Includes a list of meta tags that is stored in a centralized source/component
· The list of meta tags in the centralized source may change over time and must be trigger an update in all pages
· Default metadata for all page assets (images, referenced files) inherited from the parent page
· Includes or requires values for all mandatory metadata tags including described below - at a minimum:
Figure 1 - Proposed, standard metadata fields
Required Meta Tag (Draft) Default Value Source keywords
Author selects from USMS controlled vocabulary (under development)
DC.title
None (author must enter)
DC.description
None (author must enter)
DC.subject
Web content taxonomy position
DC.type
Author selects from “content types” in the USMS controlled vocabulary (under development)
DC.date.reviewed
Approved date from Web CMS
DC.date.modified
Modified date from Web CMS
DC.date.created
Creation date from Web CMS
DC.creator
Author’s organization from Web CMS
DC.language
Author selects from a drop down list (English is the default)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 15. Image repository |
| The Web CMS shall include an image repository that allows Web authors to: |
· Reuse images across the website
· Associate user-defined metadata with images files stored in the repository
· Search for relevant images based on their metadata
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 16. Embedded page navigation based on the page’s position in the Web IA |
| The Web CMS shall include standardized navigational modules on all templates. These navigation modules cannot be directly edited by the Web author. They can only be altered by repositioning the content. The navigation modules are: |
| a. Parent links |
| This is a link to the immediate parent of the page in the USMS Web information architecture (IA) – content hierarchy |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| b. Sibling links |
| This is a link to all pages/directories at the same level as the current page in the USMS Web IA |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| c. Child links |
| These are links to all pages/directories that are one level below the current page in the USMS Web IA |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| d. Breadcrumbs |
| This is a “>” delimited list of hyperlinks reflecting the full path to the current page in the USMS Web IA |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| e. Other |
| The Web CMS shall allow for the addition of custom, standard page navigation components |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 17. Ad-hoc page navigation modules |
| Web CMS authors shall have the ability to add the following ad-hoc content navigation: |
| a. “See Also” links |
| This is a CSS-styled list of links related to content on the USMS website based on a term (and all subordinate terms) the Web author selects from the USMS taxonomy. The Web author shall have the ability to: |
· Select up to 7 links to add to the list
· Re-order their selected links to their liking
FORMCHECKBOX
High
FORMCHECKBOX
Med
| b. “Quick Finder” links |
| This is a tabular CSS-styled list of links to specific content on the USMS website based on locations/topics the Web author selects by browsing the Web IA. The Web author shall have the ability to: |
· Select up to 7 links to add to the list
· Re-order their selected links to their liking
FORMCHECKBOX
High
FORMCHECKBOX
Med
| c. Tabbed navigation |
| This is a CSS-styled list of links across the top of the page body, in “tab format,” related to content on the USMS website based on: |
· A term from the USMS taxonomy
· Other metadata
The Web author shall have the ability to:
· Select up to 7 links to add to the list
· Re-order their selected links to their liking
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 18. 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
· Identify incoming links to content that is being removed from the website
FORMCHECKBOX
High
FORMCHECKBOX
Med
| b. External links |
| The Web CMS shall allow for the management of external (e.g. outside the www.usmarshals.gov website or the USMS intranet) links by allowing Web authors to: |
· Validate external URLs at page authoring time
· Identify published pages with broken external links and alert the page author or site administrator
· Automatically place an “exit disclaimer” image (link to a standard exit disclaimer) after any external URL
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 19. Fully customizable work-flows |
| The Web CMS shall allow for: |
· Custom work-flow management by the USMS website administrator (all site areas)
· Custom work-flow management by sub-site administrators (for specific sub-sites/organizations)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 20. Web CMS user training |
| The Web CMS vendor shall provide a per class (vendor shall indicate maximum class size) cost to conduct on-site training for: |
· Web CMS system administrators
· Web CMS site administrators
· Web CMS site authors
· Website section administrators
· Website section authors
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 21. 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
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 22. Capable of Integrating with possible USMS Enterprise Content management System (ECMS) |
| Should the USMS implement an ECMS, the Web CMS must be capable of linking to that ECMS via Content Management Interoperability Services (CMIS). The link shall allow: |
· Discovery and linking to Web CMS content from the ECMS (this would include auto updating moved or deleted content)
· Enable ECMS records management (e.g. email notifications to owners) of Web CMS content
· Notify Web content owner via email of appropriate records-related action for Web copies of ECMS records
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 23. Web Content Migration Tool (CMT) |
| The Web CMS shall have a parsing tool that automates the migration of content into the USMS Web CMS implementation that: |
· Expedites the migration of legacy Web content
· Enables the migration of Web content developed outside of the Web CMS
The content migration tool (CMT) shall have the following features/functionality:
· Allows the end user to select a target Web content taxonomy position for the page or pages that are being migrated
· Applies a user-selected, agency standard template appropriate to the target Web taxonomy position
· Adds default or additional metadata to the page or pages as described by the metadata requirement
· Embeds page navigation as described in the page navigation requirement
· Replaces/removes any manually entered page navigation
· Enables the migration of pages with or without a database back-end
· Enables the migration of supporting files (images, PDFs, MS Word files, etc.)
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 24. Site map generation |
| The Web CMS tool shall support the generation of an XML site map for use by Google (Google Site Maps) or other search engines. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 25. Agency-Wide Internet/Intranet Calendar |
| The Web CMS shall include a calendar framework that can be used by all USMS business units. The following is a list of requirements for the application: |
· A single data store for all calendar entries
· Each business unit will have a calendar administrator(s) who has insert, update, and delete rights for their business unit’s entries.
· USMS Web Managers should have insert, update and delete rights on entries for ALL business units.
· The following web interfaces are needed:
· Event entry form:
· Login required.
· Allows insert, update, or delete of records based on authenticated user rights (see above).
· Allows calendar administrators to notify mailing list member(s) of an event entry
· Internet calendar page:
· Displays public events only
· Searchable by date, event name, or event description
· Filtered by business unit
· Intranet calendar page:
· Displays private events, and/or public events
· Searchable by date, event name, or event description
· Filtered by business unit
· Event Registration engine
FORMCHECKBOX
High
FORMCHECKBOX
Med
| 26. RSS Feeds |
| The Web CMS shall have an RSS feature that allows end users to subscribe to USMS website content at the page, subject, or site level. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 27. BLOGs |
| The Web CMS shall have a BLOG feature that allows Web authors to publish approved BLOGs with moderated content OR be capable of linking to an independent BLOG system |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 28. WIKI |
| The Web CMS shall have a WIKI feature that allows Web authors to publish approved WIKIs with moderated content OR be capable of linking to an independent WIKI system |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 29. 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. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 30. 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. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 31. 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. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 32. Content rating feature |
| The Web CMS shall have a content rating feature that allows websites users to evaluate content they have viewed. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
| 33. Support for PDAs |
| The Web CMS shall be capable of producing Web content that is client-aware and can refer to an alternate, PDA-specific CSS, or a text-only version of the content for PDA consumption. Other methods of PDA content delivery will be considered. |
| FORMCHECKBOX |
High
FORMCHECKBOX
Med
<Page 1 of 3>
Printed 12/8/2010 9:37 AM ckidd
File details come from the government source that posted it. Updated .