SOLICITATION NOTICE
D -- CATALOGER''S DESKTOP ON THE WEB
- Notice Date
- 8/15/2003
- Notice Type
- Solicitation Notice
- Contracting Office
- Library of Congress, Contracts Services, Contracts Section, 101 Independence Ave SE LA-325, Washington, DC, 20540-9411
- ZIP Code
- 20540-9411
- Solicitation Number
- RFQ3916
- Response Due
- 8/29/2003
- Archive Date
- 9/13/2003
- Point of Contact
- Valda Murfree-Fleming, Contract Specialist, Phone 202-707-0468, Fax 202-707-8611,
- E-Mail Address
-
vmur@loc.gov
- Description
- Cataloger's Desktop on the Web 1. Background The Library of Congress (LOC) Cataloging Distribution Service (CDS) is required to convert its quarterly CD-ROM-based cataloging documentation product, Cataloger's Desktop, to online access via the World Wide Web. Cataloger's Desktop provides access to a large number of electronic manuals and procedural documentation that describe standards for performing cataloging and classification tasks in a library. The product is used by staff at LOC as well as by many library professionals and para-professionals worldwide. LOC staff is located in three buildings on Capitol Hill. A very small number of LOC staff are located at remote sites: Taylor St. (Washington, D.C.) and six Overseas Field Offices. Additionally, this product has users in the library field nationally and internationally. 2. Scope The Contractor shall develop a web-based delivery system for Cataloger's Desktop using NextPageJ LivePublish. The system must be updatable on a quarterly basis. The web application must use the current Cataloger's Desktop CD-ROM product as a beginning point for interface and functionality design. The Contractor is encouraged to enhance Cataloger's Desktop for web delivery. The web-based application must be capable to accept updates by CDS staff. The accompanying customer management system must have the ability to be administered by the CDS staff. The deliverable shall become the property of LOC. It shall also be accessible to LOC staff, and national and international users. 3. General Requirements 3.1 Components of Cataloger's Desktop on the web The Contractor shall create Cataloger=s Desktop on the web as two components: an information delivery system based on the latest release of NextPageJ LivePublish; and a customer management system that enables CDS staff to manage subscription- and access-information for individual subscribers of Cataloger=s Desktop on the web. The latter will include a customer interface that enables subscribers to click through and accept a license, as well as update customer records for changes in email addresses, local system administrators, or customer-specific configuration issues. The final product must comply with Section 508 to assure web accessibility. 3.2. Design Prototypes The Contractor shall prepare in consultation with CDS a maximum of three design prototypes for the overall look and feel of Cataloger=s Desktop on the web. Each prototype will include at least one query template. CDS will evaluate and select the preferred design. 3.3 Target Audience The targeted audience is library staff working in cataloging areas. It is projected that Cataloger=s Desktop on the web will be used by approximately 5,000 librarians at roughly 1,000 institutions. 400 users will be LOC staff while approximately 4,600 users will be subscribers who have purchased Cataloger=s Desktop from CDS. The job position, educational level, and computer experience of prospective users can vary tremendously. Professional library staff may have a masters degree in library science while library technicians may have high school diplomas. Although the targeted user community is international, the Contractor will not be required to design Cataloger=s Desktop on the web for every type of end-user computer platform. The language of the product shall be English. 3.4 Estimated hours It is estimated that the Contractor shall be able to accomplish the tasks in approximately 400 work hours, by working approximately 6-8 hours per week, at the Library of Congress. It is anticipated that in addition to the hours spent by the Contractor, LOC staff will contribute approximately 600 hours of work to the project. Cataloger=s Desktop on the web must be ready for launched within 6 months of contract award. 4. Hardware/software Requirements 4.1 Software The Library of Congress has selected FolioViews 4.4 (AFolio@) as the standard tool for creating and maintaining the source files for Cataloger=s Desktop. The files shall be received by CDS as WordPerfect 8.0+ or MS Word files and converted and content-enriched by CDS staff to Folio Infobase format (NFO) using the current release of FolioViews. LOC's long-term goal is to migrate the content-enriched infobases to XML when suitable web delivery applications become available. In the meantime, LOC has selected the current release of LivePublish from NextPageJ to deliver Cataloger=s Desktop on the web. The Contractor-developed LivePublish application must have the ability to accept FolioViews 4.x infobase files in native format. If file processing is required to incorporate infobases in the LivePublish day one product or quarterly updating, the Contractor shall develop this processing software. Such processing software must be structured so that it can be run by LOC staff in a production environment and must not be more complex than the current release of FolioViews Workbench. 4.2 Platform The minimum platform for LOC staff and CDS customers of Cataloger=s Desktop is as follows: $ Netscape 4.78, 128 bit encryption; or $ Internet Explorer 5.5 (Javascript enabled) 4.3 Customer Management System The Contractor must provide a customer management system that will enable CDS staff to manage subscription- and access-information for individual customers of Cataloger=s Desktop on the web. Subscription duration and numbers of simultaneous users per subscription must be administered solely by CDS staff. This customer management system must also enable customers to click-through and accept a license, as well as update their customer record for changes in email addresses, local system administrators, or customer-specific configuration issues. 4.4 Server The Contractor shall recommend the location of Cataloger=s Desktop on the web and its customer management system. If Cataloger=s Desktop on the web is located on either the Contractor=s or a third party=s server, CDS will purchase a product-specific domain name. That name will be used for the product. If Cataloger=s Desktop on the web resides on an LOC server, the product will have a sub-domain of the LOC web domain (such as http://desktop.loc.gov). The ITS technical staff will be available to provide guidance to the Contractor on all server requirements. 5. Specific Requirements 5.1 Project Plan The project plan created by the Contractor shall lay out a well-defined project schedule steps, deliverables, intermediate tasks, that describes development milestones, and resources. It shall focus on the responsibilities assigned to the Contractor, which will incorporate advice on content, CDS=s responsibility, where necessary. It must be delivered to LOC within eight (8) workdays from the date of contract award. 5.2 CD-ROM Product Description Appendix A: Cataloger=s Desktop on CD-ROM Product Description focuses on the existing CD-ROM product available in FolioViews 4.4 infobase format. The Contractor will examine the content to determine the need to be re-purposed for presentation on the web. C Recommendations for the conversion of the existing content for web delivery. C Suggestions on methods and techniques for adding enhanced access and functionality to the web-based product. 5.3 Design Document The design document shall provide the overall design for Cataloger=s Desktop on the web developed from this statement of work. It shall include the following: C Three (3) design prototypes; these prototypes will include the user interface and representative functionality and must include at least 1 query template; these prototypes are the property of CDS C CDS evaluates the prototypes and selects one. The selected prototype will then be used as the basis for Cataloger=s Desktop on the web. 5.4 Cataloger=s Desktop on the web - Specific Requirements Cataloger=s Desktop on the web must be developed using the latest release of NextPageJ LivePublish. The product must be designed with end-user usability as central to its design approach. Cataloger=s Desktop on the web must be updatable by CDS staff on at least a quarterly basis. This updating must be accomplished by either the direct loading of Folio infobase files, or by washing Folio infobase files through a simple production software routine. The Cataloger=s Desktop on the web design must also be modular so that additional files can be added easily for new releases of Cataloger=s Desktop on the web when necessary. The LivePublish-based information system must not employ proprietary plug-ins or extensions that may not be supportable in subsequent releases of LivePublish unless waived by the Library. If waived by the Library, Contractor must explain steps taken to ensure no compatibility, security or upgrade issues will result. Cataloger=s Desktop on the web must be fully viewable by all major browsers, specifically Netscape 4.78 or higher, and Internet Explorer 5.5 or higher. The Cataloger=s Desktop product has quarterly updates to keep the standard documents and manuals it contains current. The structure of the product is stable and its appearance does not change dramatically very often. However, we must be able to update Cataloger=s Desktop on the web as needed (at least quarterly) to incorporate any changes to the product. The Cataloger=s Desktop on the web delivery package shall include: 3. User interface designed with optimal usability as its focal-point. 4. Software to convert Folio infobase files to be compatible with LivePublish without losing their native content enrichment. This conversion software must be structured so that it can be run by LOC staff in a production environment and must be no more complex to run than the current release of FolioViews Workbench. 5. The latest release of NextPageJ LivePublish development and server software. 6. Creation of a pilot version of Cataloger=s Desktop on the web for Ahands-on@ testing inside and outside of LOC. The Apilot version@ of Cataloger=s Desktop on the web is a segment of the product that contains all the technical capabilities used in the entire product. 7. Creation of a customer management system that enables CDS staff to manage subscription- and access-information for individual customers of Cataloger=s Desktop on the web. Subscription duration and numbers of simultaneous users must be administered solely by CDS staff. This customer management system must also enable customers to update their customer record for changes in email addresses, local system administrators, or customer-specific configuration issues. 8. Mentor and instruct the Project Team on site at Library of Congress in the installation, maintenance, and updating of LivePublish software and Cataloger=s Desktop on the web. 9. Mentor and instruct the CDS Project Team on site at Library of Congress in the installation, maintenance, and updating of the customer management system. 10. The product shall be revised by the Contractor and CDS based on the results of the pilot testing. CDS shall focus its revisions on the content. 11. Provide on-going technical and maintenance support of up to 100 hours per year for as long as Cataloger=s Desktop on the web is run on LivePublish software. 12. Provide on-going site hosting if the product is set up the Contractor=s server. 13. 6. Roles and Responsibilities The Contractor shall submit a Project Plan, a Design Document, and Specific Requirements for Cataloger=s Desktop on the web. The Contractor shall also create a Apilot version@ of Cataloger=s Desktop on the web for testing. The Contractor shall be responsible for the following: 14. Developing a data conversion production system; 15. User interface; 16. Design prototypes; 17. Query templates; 18. Customer management system; 19. Training of CDS Project Team; 20. Testing of pilot Cataloger=s Desktop on the web and making appropriate modifications based on the outcome of the test; 21. On-going support. Library of Congress: 21. If it is mutually agreed (by the Library of Congress and the Contractor) to mount Cataloger=s Desktop on the web at LOC, the Library shall mount the product on one of its servers and provide access to the product to subscribers. 22. The Library of Congress shall assign appropriate personnel to the following roles: Contracting Officer=s Technical Representative (COTR): C The Team Leader of the Cataloger=s Desktop Development Team in CDS will serve as the COTR for this project. Project Manager: 3. The Team Leader of the Cataloger=s Desktop Development Team in CDS will also serve as the Project Manager for this project. 4. Responsible for overall management of the project and formal acceptance of deliverables. 5. Will serve as the Contractor=s primary point of contact for design, development, and technical issues. 6. Will organize customer testing. Project Team: 7. Will assist the Project manager in performing the following duties: a. Oversee/monitor contract work; b. Provide technical expertise to Project manager and Contractor as requested; c. Conduct customer testing; d. Evaluate deliverables 8. Team shall consist of: a. COTR / Project manager b. CDS Chief c. A CDS technical support staff member d. A CDS customer support staff member e. A CDS marketing staff member f. One representative from the Information Technology Services Directorate (ITS) whose primary focus will be technical support for this project. Anticipated Government Contribution from CDS will be to: 9. Provide source files in FolioViews 4.4 infobase format 10. Supply graphics files as requested 11. Assist with testing of pilot Cataloger=s Desktop on the web product 12. Work space in CDS for Contractor which includes a personal computer with Cataloger=s Desktop and FolioViews software and a telephone 7. Anticipated Schedule for Completion during Fiscal Year 2004 Event Description Approx. Business Day(s) Approx. Total Hours 1 Contract awarded 1 4 2 Kick-off meeting 2 8 3 Project Plan 3.1 Detailed schedule of tasks and timeframes 3.2 List of deliverables 3-8 40 4 Design meeting 4.1 Present 3 design prototypes 4.2 Evaluate, select & approve prototype (CDS) 9-15 80 5 LivePublish template design, infobase conversion, & site setup 16-35 200 6 Customer management system development 36-50 320 7 Test web product 7.1 Test onsite at LOC 7.2 Test at remote locations 51-80 400 8 Final review and approval of contract deliverables (CDS) 81-90 32 (CDS hours) 9 Acceptance of final deliverables documented by Project Team (CDS) 91 8 (CDS hours) 8. Deliverables 8.0 The Contractor shall deliver to LOC the following: 1. Three design prototypes 2. Pilot test 3. A web delivery system for Cataloger=s Desktop based on the latest release of NextPageJ LivePublish. 4. Production software to enable CDS staff to update Cataloger=s Desktop on the web as needed, at least quarterly. 5. The latest release of NextPageJ LivePublish server and development software. 6. A customer management system to enable CDS staff to manage customer subscriptions to Cataloger=s Desktop on the web and control their access to the product. 7. Training and mentoring of CDS staff to develop the skills to support the LivePublish-based Cataloger=s Desktop on the web product, as well as its customer management system. 8. On-going site hosting for the LivePublish-based Cataloger=s Desktop on the web product, and/or its customer management system if either or both are set up the Contractor=s server. (This will be dependent on mutual agreement between LOC and the Contractor.) 9. One hundred (100) hours annually of on-going technical and maintenance support subsequent to the day-one launch of Cataloger=s Desktop on the web. 8.1 Required reports 1.1 Monthly report--- Due first of each month 1.2 Interim report-- Due when the project is one-half completed 1.3 Final report-- Due 30 days prior to the completion of the contract 8.2 Inspection and Acceptance The Contractor shall provide all reports in 82 H 11 paper and electronic format to submit them to the COTR for review. COTR shall review and return to Contractor with comments, suggestions, and recommendations within 5 days. Contractor shall incorporate comments, suggestions, or recommendations within 5 days and return to COTR for final approval. Failure to agree on final report shall be treated as a dispute and shall be resolved under the Library=s Disputes Clause. 9. Period of Performance The period of performance shall be six months from the date of award. 10. Applicable Documents The Contractor shall consider the following documents in the proposal. 1. Rehabilitation Act of 1993, Amendments of 1998, Section 508 2. Cataloger=s Desktop on CD-ROM Product Description 3. The current issue of Cataloger=s Desktop. 11. Definitions In this Statement of Work, the following terms shall have the following meanings: Cataloger=s Desktop on the web: Conversion of the existing CD-ROM-based Cataloger=s Desktop product to web delivery, whether mounted on a Library of Congress server or an external server, accessible via a browser by Library of Congress staff and national and international customers. Customer management system: A web-based application that allows CDS staff to administer customer information and subscription and access rights to Cataloger=s Desktop on the web. The customer management system will also allow Cataloger=s Desktop on the web subscribers to manage specific subsets of their institutional information within the system. Design prototypes: Each design prototype includes basic designs and color choices, a product title page, a customer management system interface page, two or three infobases, and at least one query template that demonstrate a look and feel for the web-based product that can be applied throughout the web-based product. Pilot test: A portion of the web-based product that contains the design and navigation of the final product and examples of most query templates. The pilot test must include at a minimum the following completed files: Anglo-American Cataloguing Rules, Library of Congress Rule Interpretations, MARC 21 Bibliographic Format, MARC 21 Language Code List, and the Subject Cataloging Manual: Subject Headings. This will be tested to determine its ease of use and freedom from bugs. Query templates: A template that enables Cataloger=s Desktop on the web subscribers to perform focused searching of one or more Cataloger=s Desktop on the web files. Query templates are intended to mimic the most frequently performed searching tasks so that Cataloger=s Desktop on the web subscribers intuitively discover information within the system. Training of CDS Project Team: The Contractor shall also provide on-site training for LOC staff in the following areas: infobase conversion and upload into the Cataloger=s Desktop on the web system, interface management, overall system management, and technical support. The Contractor must also provide on-site training for the customer management system. 12. Evaluation Factors Proposals will be evaluated as follows: 12.1 NextPage? Premier Partner: The vendor must be a NextPage? Premier Partner in current good standing. 12.2 Understanding of the Requirement. The offeror's proposal demonstrates an understanding of the requirements described in the Statement of Work. 12.3 Development Capability: The offeror must possess the knowledge, skills, and abilities needed to create a web version of Cataloger's Desktop that can be managed either thru CDS's customer information management system or thru a bridge customer information management system. This capability includes the perceived cultural fit between vendor and the Library and vendor's ability to work effectively with the Library's staff. 12.4 Professional and Management/Organization Capability: The offeror must demonstrate the ability to plan and manage the project so as to complete the project within a six-month period and the staff must possess the depth and breadth of experience, skills, and knowledge required by the Statement of Work, as solely determined by the Library. 12.5 Experience: The offeror is a NextPage? Premier Partner and demonstrates experience in migrating FolioViews-based systems to NextPage? LivePublish. offeror also has demonstrated experience integrating customer management features with LivePublish access. The qualifications of key personnel are reviewed. 12.6 Past Performance: Includes interviewing of professional references for evaluation of past performance. 12.7 Cost: The reasonableness of the vendor's proposed cost as well as the total cost to the library as it relates to the work performed. When technical factors are equal, cost will become a greater factor. Award will be made on the basis of best value. OFFERORS: An appendix will be emailed to offerors upon request. No phone calls please. Questions and requests may be emailed to the contracting officer.
- Record
- SN00403485-W 20030817/030815214655 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |