Statement of Work for
General Services Administration
Office of Electronic Government
Title Task:
Upgrade of XML.Gov Website
1.0 Background
The XML.gov
website was developed to serve the XML working group that is chartered by
the Chief Information Officers (CIO) Enterprise Interoperability and Emerging
Information Technology Committee (EIETC). Currently, the website is essentially
a collection of static XML-related documents. The site needs to be upgraded
to incorporate and demonstrate XML technology.
The ebXML family
of specifications that together enable a modular electronic business framework
were approved on May 11, 2001. The National Institute of Technology (NIST)
in partnership with the General Services Administration (GSA) is developing
the functional requirements and selection criteria for an ebXML compliant
registry/repository.
Initially, the
registry/repository will be compliant with the ebXML Registry Information
Model, and the ebXML Registry Services Specification. The registry/repository
implementation will be procured by GSA and operated by NIST as a pilot. The
registry/repository will be integrated into the XML.gov website after the
completion of the piloting phase. The XML.gov registry/repository
will be migrated to a COTS solution, as ebXML compliant registry/repository
products become available.
The XML.gov
website will undergo periodic, incremental upgrades throughout its life cycle.
Budgetary constraints and the XML working group priorities dictate the specific
tasks implemented during this upgrade.
2.0 General Website Upgrade Requirements
2.1 The contractor shall upgrade the XML.gov website using
the same general ‘look and feel’ at the present site. The contractor shall
upgrade the site using industry best practices.
2.2 The contractor shall ensure that the upgraded website
meets current federal accessibility requirements.
2.3 The contractor shall recommend a set of web tools necessary
to operate and maintain the site.
2.4 The contractor shall only use widely implemented languages,
standards, and tools in the upgrade and maintenance of the website. The
contractor shall avoid proprietary standards, and tools in the upgrade of
the website. In instances where an open standards-based solution is not available,
the contractor shall adopt the most widely adopted de facto standard consistent
with industry best practices.
2.5 All content delivered by the webserver to the client
must be capable of being rendered by the current versions of Internet Explorer,
version 5.0 and Netscape Browser, versions 4.1 - 4.7.
2.6 The contractor shall repair all broken links and check
links for accuracy.
2.7 The contractor shall check HTML coding for well-formed
HTML. The contractor shall also examine existing HTML coding and add structure
and documentation as required.
2.8 The upgraded website must satisfy all the requirements
of Federal Accessibility Guideline 1194.22 (Web-based Intranet and Internet
Information and Applications
3.0 Technical Upgrade Requirements
3.1 Support for WebDAV
The contractor
shall incorporate the defacto standard World Wide Web Distributed Authoring
Versioning (WebDAV) into the XML.gov site. WebDAV
extends the functionality of HTTP to provide a standard infrastructure for
asynchronous collaborative authoring across the Internet.
WebDAV provides a more user friendly, and efficient alternative to
the current FTP process currently being used to transfer files.
3.2 Upgrade of the Efforts Section
The contractor
shall coordinate with the XML working group to upgrade the ‘Efforts Section’
which is currently developed using Cold Fusion.
3.3 Membership List
The membership
list on the website needs to be accurate and kept current. Members are added
to list but are not linked to the database. The contractor shall employ
XML technology to facilitate better management of the membership list with
minimum administrative overhead.
3.4 Search Utility
The contractor
shall install a search utility to search the XML site, including the registry/repository
including the registry/repository that will be integrated into the XML.gov
site.
The contractor
shall review the existing XML.gov infrastructure to ensure that appropriate
changes are made to accommodate specified as well as anticipated growth
of the upgraded XML.gov technology portal.
4.0 Web Hosting Service
The contractor
shall propose and implement a level of web hosting service consistent with
the mission and functionality of the XML.gov website.
5.0 Hardware Environment
The contractor
shall recommend an appropriate hardware platform for Government approval.
6.0 Software Environment
6.1 The contractor shall recommend database software consistent
with required functionality and GSA environment.
6.2 The contractor shall recommend a suitable search engine
subject to GSA approval.
7.0 Deliverables
7.1 Plan of Actions and Milestones to be delivered within
10 days of kickoff meeting.
7.2 Detailed listing of all software used to upgrade the
website. This is required within four months of
contract award.
7.3 Fully operational website that satisfies all requirements
specified. This is required within four months of
contract award.
8.0 Acceptance of Deliverables
All deliverables
under this contract will be accepted or rejected in writing by the COTR.
The contractor warrants against latent defects for a period 13 months all
analysis, design, plans, and specifications produced under this contract.
Further constraints
shall apply to computer software deliverables. Such products will be accepted
on an interim basis for payment, but must perform satisfactorily from period
of acceptance date for 13 months. If deficiencies
are discovered within this period, the Government will list them and the contractor
shall correct them at no additional charge, within a period of 14 calendar
days.
All deliverables
must meet normal professional standards and the requirements set forth in
the contractual documentation and GSA capital zone's Task Order Procedures.
9.0 Deliverable Instructions
The deliverables
shall be delivered to the Client Representative
10.0 User Acceptance Period
The Government
will have ten (10) work days to complete the review of each deliverable and
accept or reject it in writing.
11.0 Reporting Requirements
The contractor
shall submit a monthly labor hours report, certified by the Client Representative,
with the invoice for labor and services each month to GSA.
12.0 Period of Performance
The period of
performance for the web hosting services is from October 1, 2001 through
the end of the fiscal year 2002.
The period of
performance of this contract (excluding the web hosting services) is four
months from the date of contract award.
13.0 Unauthorized Commitments (FAR 1.602.3)
The COR is designated
by the Contracting Officer to perform technical liaison between the Contractor’s
management and the Contracting Officer in routine technical matters constituting
general program direction within the scope of the contract. Under no circumstances is the COR authorized to effect
any changes in the work required under this contract whatsoever, or enter
into any agreement
Notwithstanding
this provision, to the extent the Contractor accepts any direction that
constitutes a change to this contract without prior written authorization
of the Contracting Officer, costs incurred in connection therewith are incurred
at the sole risk of the Contractor, and if invoiced under this contract will
be disallowed. On all matters that pertain to the
contract terms, the Contractor must communicate with the Contracting Officer.
Whenever, in
the opinion of the Contractor, the COR requests efforts beyond the terms
of the contract, the Contractor shall so advise the Contracting Officer. If the COR persists and there still exists a disagreement
as to proper contractual coverage, the Contracting Officer shall be notified
immediately, preferably in writing. Proceeding with
work without proper contractual coverage may result in nonpayment or necessitate
submittal of a contract claim.
14.0 508 Compliance
The Technical
Standard (Subpart B) for Web-based Intranet and Internet Information and
Applications (1194.22) of Section 508 are incorporated by reference. Vendors are required to state if the items proposed meet
the standard.
15.0
Award Criteria
Selection of
the successful Offeror will be on a "Best Value" basis.
Proposed technical capability/methodology is more important then
prior performance, which is more important then price. As
technical factors become more equal, price becomes more important.
Technical capability/methodology
and prior performance is more important Price. Prior Performance and capability/methodology
are of equal importance.