D -- IMPLEMENTATION OF AN INTEGRATED, SCALABLE CONTENT MANAGEMENT SYSTEM (CMS) THAT ENCOMPASSES WEB AND E-MAIL APPLICATIONS, AND PROVIDES THE CAPABILITY TO ADOPT PRINT PUBLISHING FUNCTIONS IN THE FUTURE.

Notice Date

June 20, 2001

Contracting Office

Department of the Interior, Minerals Management Service, Procurement Operations Branch, MS2500, 381 Elden Street, Herndon, Virginia 20170-4817

ZIP Code

20170-4817

Solicitation Number

31168

Response Due

June 30, 2001

Point of Contact

Robin Kisner (703) 787-1343 Robin.Kisner@mms.gov

Description

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 97-20. The following provisions and clauses apply to this acquisition: 1) 52.212-1, Instructions to Offerors-Commercial (OCT 2000); 2) 52.212-3, Offeror, Representations and Certifications-Commercial Items; 3) 52.212-4, Contract Terms and Conditions-Commercial items (APR 1998), with an addendum; and 4) 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders Commercial Items (AUG 2000). Solicitation Number 31168, the solicitation is issued as a request for proposals (RFP). Proposal are due NLT 30 June 2001, 1:00PM eastern time.. This requirement is being issued by Gov.Works under the franchise authority of the Department of State. GovWorks/DOS intends to issue a contract. 2. SUMMARY The Liquid State content management system (CMS) encompasses two broad functions: one for IIP editors, or producers; the other for its worldwide audience of public users. The CMS will be implemented in four phases and deployed on servers at IIP offices in Washington and at UUNet in Atlanta, Georgia. Each of the CMS functions, phases, and deployments are summarized here and described in greater detail elsewhere in the Statement of Work. This document also describes IIP's LAN and WAN environment, chief information products, and Internet operations. 2.1. Producers. For IIP staff editors and administrators, the content management system facilitates the production, editing, and distribution of policy materials for its daily information service known as the Washington File, and for its International Web site. IIP editors and staff reside at State Annex 44 in Washington, D.C. 2.2 Users. For overseas posts, foreign audiences and other users, the content management system provides a mechanism for "dynamic" database delivery of texts, policy documents, and Web-based materials via the Internet. These public users will access the output of the content management system via Web and database servers residing at UUNet. 2.3 Phases. Implementation of the Liquid State content management system will take place in four phases. Phases 1 and 2 can be categorized as a pilot program. In phase 3, the Liquid State content management system becomes the primary production and delivery system for the Web version of IIP's Washington File. In phase 4, the CMS becomes the primary editorial and production mode for the entire IIP international Web site. 2.3.1. Phase 1 covers initial installation and testing of the content management system.2.3.2. Phase 2 constitutes a demonstration project for the daily Washington File on IIP's international Web site. 2.3.3. Phase 3 is full implementation of the content management system as the primary editorial and production system for the Washington File on the IIP International Web site. 2.3.4. In phase 4, the content management system becomes the primary editorial and production system for the entire IIP International Web site (http://usinfo.state.gov). 2.3.5. In phase 5, IIP will define additional requirements for possible expansion of the content management system to overseas posts. Precise definition of these requirements are beyond the scope of this Statement of Work. 2.4. Deployment. The content management system will be deployed in two locations. IIP offices in Washington, D.C., for testing, training, and evaluation; full server and software installation at IIP's Internet Service Provider, UUNet facilities in Atlanta, Georgia. 3. GENERAL REQUIREMENTS This section outlines the basic requirements of the Liquid State content management system. The primary focus is upon document production and delivery of policy materials for three Internet-based products: Washington File, IIP international Web site, and e-mail Listserv applications. 3.1. Overview. The contractor shall implement an integrated, scalable content management system (CMS) that encompasses Web and e-mail applications, and provides the capability to adopt print publishing functions in the future. It must be cross platform, functioning on any widely used commercial operating system. 3.2. Internet Focus. As outlined below, the chief focus will be on Web and other Internet-based functions, building on the foundation of IIP's daily Washington File and its international Web site -- <http://usinfo.state.gov/>. 3.3. Dynamic Delivery. The content management system will receive, process, and store information in a database server, then deliver it dynamically to users via Web, e-mail (Listserv), or print. The bulk of the information consists of written texts policy statements, press releases, speeches, transcripts, staff-written articles, and government reports -- from U.S. officials and experts. Selected materials are also translated and presented in language versions, including French, Spanish, Arabic, Russian, and Chinese. 3.4. Formats and APIs. The content management system must have the ability to store, index, and deliver these materials in a variety of formats, including but not limited to: ASCII text, standard word-processing formats (including MS Word), HTML, PDF, and XML. The system must possess the open application programming interfaces (APIs), scalability, and flexibility to accommodate standard, commercial applications and modes of storing and delivering information, including such fast-evolving technologies as wireless (WAP, I-Mode) and audio/video streaming (RealMedia, Quicktime, Windows Media Player). 3.5. Print/E-Mail. Web pages will offer users the options of clicking on links or buttons that optimize texts and documents for either print and e-mail delivery. 3.6. PDQ Database. Using a Web interface, the content management system will access and retrieve documents from the remotely hosted PDQ (Public Diplomacy Query) database, which serves as a primary source of official, foreign-policy documents, texts, statements, and other text materials. 3.6.1. Typically, editors using the CMS will access the PDQ database via the Web to search and locate listings of policy documents related to a current text undergoing editorial review. Editors will incorporate selected items from PDQ into the current text as "related links" or "background information," reformatting or saving the document as a static HTML page. 3.6.2. The PDQ server, located in the Washington, D.C. area, operates under Windows NT 4.0 using a Microsoft SQL relational database. Excalibur Retrievalware software is loaded on a Pentium-based Dell Server running NT 4.0. The system allows for open access and password protection and involves transmitting data over publicly accessible phone lines or Internet connections. 3.6.3. The PDQ database is accessed by Washington-based research specialists and editors, as well as by information specialists and other staff professionals in more than 120 U.S. embassies and missions around the world. As a link on the IIP Web site, it can also be searched by general foreign audiences. (Click "archive" on usinfo.state.gov.) Although it contains a relatively small "staff use" section requiring name and password, all PDQ data is unclassified. 3.6.4. The PDQ database has French- and Spanish-language sections, and IIP will be adding language modules in Russian, Chinese, and Arabic by 2002 to permit archiving and searching in those languages as well. 3.7. Graphics. The content management system must also be able to accept, store, access, and deliver visual materials, including photographs and graphic art in standard electronic formats (JPG, GIF, TIF, EPS), streaming audio and video files, and other Internet-based applications such as Flash. 3.8. Dynamic Web Pages. The CMS must accept and organize information into relational databases, and then have the capability of delivering the material via dynamic Web-page building. 3.9. Versions and Templates. The CMS must offer version control, and employ both standard and specialized Web-page templates, images, and graphic elements. 3.10. Bandwidth. The CMS will deliver Web-based content that is accessible by U.S. embassies and missions around the world with both high- and low-bandwidth capacity. 4. EDITORIAL WORKFLOW 4.1. The Liquid State content management system will provide permissions and levels of access to facilitate three basic editorial/administrative roles. In the initial phases, this description of functions pertains to the daily Washington File of texts, transcripts, and other policy documents. In later phases, this same general, three-level breakdown of editorial/administrative roles will apply to operation of the entire IIP Web site. 4.2. This description does not identify number of staff, which will range from 20 to 100 writers, editors, and administrators. In some instances, a single individual may retain all three roles; in others, the three roles maybe be divided among a larger number of IIP staffers. 4.3. The contractor(s) must deliver a system with the ability to distinguish among the following editorial and administrative roles, and to define the appropriate levels of rights, permissions, and system access. 4.3.1. Writer/Editor: 4.3.1.1. Input and editing of text files (texts) from Microsoft Word, comparable world-processing systems, and/or directly via a browser Web-form. 4.3.1.2. Input of metadata, including key words, slugs, summaries, index terms and other descriptors. 4.3.1.3. Access to Web-based databases, such as PDQ, and Web-search functions permitting selection of related articles, texts, Web sites, and other materials. (Function may be shared with content editor and/or administrator.) 4.3.2. Content Editor: 4.3.2.1. Review of texts submitted by writer/editors. Approve or reject texts submitted by writer-editor(s). Return text with redlining and/or editorial comments for revision. 4.3.2.2. Offer content editors the option of issuing e-mail notification to writer-editors regarding status of texts. 4.3.2.3. Search existing materials to provide "related materials" links to texts, including online databases and Web sites. (Function may be shared with role of writer-editor.) 4.3.2.4. Link to digital images and graphics, such as photos, streaming audio or video, graphics, texts. Provides captions and credits. These photos and images are stored in LAN directories photo CD collections, and delivered as e-mail attachments. 4.3.2.5. Access IIP photo database, which IIP anticipates acquiring in the near future. This digital image database will eventually integrate all IIP photo and graphic materials. Database will be managed directly by IIP in its LAN environment. 4.3.2.5. Identify and tag each story for use with multiple Web templates for publishing in multiple categories on Web site. 4.3.2.6. Create a composite top "front page" from current texts, and present them in rank or priority order. (Function may be shared with role of administrator.) 4.3.2.7. Publish or "push" texts and related materials to IIP Web site once content is approved. 4.3.3. Administrator: 4.3.3.1. Set editorial/access rights and permissions to different levels of the content management system. 4.3.3.2. Review and approve front-page headlines and selection of priority texts and other documents. 4.3.3.3. Determine values and handling of texts and other Internet-based materials, including but not limited to the length of time texts remain live, when texts are archived, and which templates are assigned to different sections or pages. 5. EDITORIAL AND SYSTEM REQUIREMENTS 5..1. Database Server. The content management system will index new content into an Oracle database server. However the CMS must be cross-platform and offer the capacity of accessing and indexing content in SQL or another enterprise-level database server. 5.2. Caching. The content management system will store current texts in a static cache, allow them to be keep active for a specific length of time (set by the Administrator). At the end of the time period, archive the texts to the database along with all related materials on the texts page. 5.3. Data Formats. The content management system must be able to store, index, and deliver the following data formats: XML, HTML, PDF, GIF, JPEG, MP3, MPEG, Real, Windows Media, QuickTime (and other streaming content). It must also accommodate such wireless applications as WAP and I-mode. 5.4. Accessibility. All Web content and formats must be compliant with Section 508 of the Rehabilitation Act, which provides for access to information by vision-impaired and disabled users. IIP will provide specifications and standards necessary for Section 508 compliance largely through its own Web templates and operating procedures. 5.5. User Interface. The content management system will allow for standard Web viewing and/or personalized content viewing based on user-input criteria. 5.6. Integration. The content management system will be built on software that provides open APIs for integration with other Web and print publishing software.5.7. Server-Side Deployment. On the server side, the content management system can be deployed on one or all of the following systems: Windows NT 4.0, Windows 2000, or Solaris/UNIX. 5.8. Client-Side Deployment. On the client side, the content management system will be deployed on Windows NT 4.0 workstations, but must also supports users with Windows 95 and higher. 5.9. Business Logic. The software used for developing the content management system must separate the "business logic" from both the database input and presentation output. 5.10. IIP Templates. Contractor must be able to implement Web template designs created by IIP personnel that are then incorporated into the CMS output engine. 5.11. "Dynamic" Content. The content management system should allow for easy updating of "look and feel" via Web page templates. The system must accommodate, for example, use of Cascading Style Sheets (CSS). 6.12. Demographics. The system must be able track site usage based on specific demographic information. 6.12.1. User demographics would be collected via electronic Web forms and stored in the database hosted by the Internet Service Provider, UUNet. Demographics would be used to identify categories of users to analyze Web site functionality. 6.12.2. In future applications, demographic data would be used to provide customized Web pages serving up topical information specified by the user (the "My State Department" page model). 6.12.3. In any demographic application, the content management system will not employ persistent cookies or other code that identifies and/or tracks individual users. 6.13. Security and Privacy. The system must fully safeguard all software and data, and meet all privacy safeguards for individual users of federal government Web sites. 7.13.1. Editors and administrators will access the system remotely via a Virtual Private Network using firewall and encryption applications specified and approved by UUNet and the State Department's Bureaus of Information Resource Management (IRM), Diplomatic Security (DS). 6.13.2. Contractor will provide a single point of contact to coordinate security and operational requirements of UUNet and State Department's Bureau of Resource Management, Diplomatic Security, and the Office of International Information Programs. 6.13.3. The CMS will not employ "persistent cookies" that identify and track individual users in any of its applications or configurations. So-called "session cookies," which terminate after the user leaves a Web site or logs off, are permissible. 7. DEPLOYMENT AND INSTALLATION This section summarizes deployment and configuration of the content management system at IIP in Washington, D.C., and at UUNet facilities in Atlanta, Georgia. It also specifies servers, LAN connections, and technical support that IIP will provide as part of the CMS deployment. 7.1. One copy of the content management software, for testing, training, and evaluation, will be installed on the IIP LAN at 301 4th Street SW, Washington, DC (State Annex 44). 7.2. The CMS will support 20 users in phases 1 and 2, 60 users in phase 3, and 100 users in phase 4. These users are the editors, administrators, and Web developers who acquire and produce the policy materials that are the "content" in the content management system. (See Section 9 for details on each project phase.) 7.3. For the Washington deployment, IIP will furnish all hardware and LAN connections, including servers and client-side workstations. IIP will furnish cubicles, desks, and telephone service to the Contractor personnel. IIP will also furnish all required Web templates and graphics. 7.4. Parallel with the IIP deployment, the vendor will work with the Department of State and UUNet to install the full production version of the content management system at UUNet, which is where public users will access the Web pages and other materials produced by the Liquid State CMS. 7.5. Installation of the CMS test version in Washington and production version at UUNet will be configured to meet operational and security requirements of all stakeholders, including UUNet, IIP, and the Department's Bureaus of Information Resource Management (IRM), and Diplomatic Security (DS). 7.6. IIP will provide LAN-based Internet connections to permit Washington editors and administrators to access the CMS at UUNet and publish to the Web site. 7.7. The full production deployment of the CMS at UUNet will incorporate an Oracle database server that will index and store content, as well as development and Web application servers. 7.8. IIP will provide assist the vendor in establishing processes and procedures for how data moves from IIP to UUNet. IIP will be responsible for the Internet connectivity to meet these data transfer requirements. 8. TRAINING AND SUPPORT 8.1. Vendor will provide technical training for IIP personnel in the installation and support of the content management system. Vendor will provide similar orientation and technical training necessary for UUNet personnel to maintain the systems Web applications and database servers, and software. 8.2. Vendor will provide user training and support for IIP's editors and administrators who will manage the content management system in Washington (State Annex 44). 8.3. Vendor will provide a manual with instructions for editorial users of the system as well as for technical staff responsible for supporting the system. 8.4. Vendor will provide project management reports on a biweekly basis throughout all four phases of the project. 8.5. Vendor will provide monthly financial status reports that document expenditures through all four phases of the project. 8.6. Primary work location will be at 301 4th Street S.W., Washington, D.C. 20547. 9. CONTRACT PERIOD AND RENEWAL 9.1. [Proposal Due Date] 9.2. The contract shall run from [one-year time period] with four (4) one-year renewal options. 10. BID SUBMISSION 10.1. Each offeror must submit the following information: (1) an offer; (2) specified written information about the offeror's ability to perform the prospective contract; (3) specified written information about the offeror's proposed prices. 10.2. Offer. A price sheet stating the price per month and the total price for 12 months. Additionally, the price sheet will include a price breakdown of the monthly and hourly rates. 10.3. Written Information. The offeror should prepare and submit the following: 10.3.1. Resume of proposed workers. The resume should i

Record

Loren Data Corp. 20010622/DSOL012.HTM (W-171 SN50P515)