The following document is an actual Statement Of Work received from a government agency by a small software company. The government agency name has been "X'ed" out for security reasons.
1.0 BACKGROUND.
This initiative will provide the automated management support tools
required by policy makers to: integrate forms management and policy
review processes and schedules; streamline the forms update process; and
allow for the consolidation and elimination of some forms. Internet-
based forms access without the requirement for users to pay license fees
will also be demonstrated.
2.0 APPLICABLE DOCUMENTS:
2.1 Database Design Description for DOCUMENT Publications Management
System (DPMS), Version 4, 7 June 1999
2.2 DPMS User's Manual, Version 2.1, August 1998
2.3 US Government Multiple Parallel Processing Server (MPPS)
2.4 Department of the Government Pamphlet
2.5 Government Regulation (AR) 710-1 Centralized Inventory Management of the
Government Supply System
2.6 AR 710-2 Supply Policy Below the Wholesale Level
2.7 PAM 710-2-2 Supply Support Activity Supply System: Manual
Procedures
2.8 PAM 710-2-1 Using Unit Supply System (Manual Procedures)
2.9 AR 735-5 Policies and Procedures for Property Accountability
3.0 SCOPE. The contractor shall provide all labor, materials,
equipment, and supplies, except those specified herein as Government-
furnished, to define, develop, document, prototype, test, and modify
DPMS by adding an Interactive Forms Management Capability NLT 30 June
2000. The Interactive Forms Management Capability will integrate
management processes for prescribing regulations and pamphlets and their
associated blank forms, allowing authors and approvers to change, add,
or delete forms information in concert with changes in their prescribing
regulations and pamphlets.
3.0.a Provide a DOCUMENT forms database. The database shall provide Open
Database Connectivity and include the ability to query the displayable
contents and database fields of existing and newly revised electronic
forms.
3.0.b Provide an integrated forms cross-reference within DPMS that
allows for synchronized update of electronic forms and their prescribing
regulations and pamphlets.
3.0.c Provide software that integrates the forms update and management
processes within DPMS, to include integrating forms utilization analysis
tools within the forms management process.
3.0.d Provide electronic Form 2028 (Recommended Changes to
Publications and Blank Forms) submission software and user input screens
for DOCUMENT proponent blank forms. The capability shall be integrated
with existing DPMS change submission procedures, allowing electronic
Form 2028s to be submitted for Blank Forms as well as Government Regulations
and Pamphlets.
3.0.e Demonstrate automatic DD Form 67 (Form Processing Action Request)
transmission procedures. These procedures will allow for paperless
approval of forms changes, additions, and deletions.
3.0.f. Demonstrate HTML hosting of DOCUMENT proponent forms and hyper-
linked forms access via prescribing policy regulations and pamphlets.
The goal here is to demonstrate the ability to host Internet-based
DOCUMENT proponent forms without the requirement for user license fees.
3.0.g The Interactive Forms Management Capability shall be
operationally compatible with DPMS. Operational compatibility in this
context is defined as "the ability for DPMS users to update and staff
blank forms using DPMS."
3.0.h The contractor shall develop the new Interactive Forms Management
Capability anticipating future interface with the XXXX XXXX XXXX XXXX
Administrative Publication program with minimal or no redesign. The
Interactive Forms Management Capability must be capable of sharing
information with XXXXX and utilizing XXXX data if needed. The Interactive
Forms Management Capability must also comply with XXX Common Operating Environment
standards.
3.0.i The contractor shall provide all functional and technical
supporting documentation to include source code, all libraries
associated with the application, compiler(s), program structure
diagrams and data dictionaries for the Interactive Forms
Management Capability NLT 30 June 2000 or earlier if specified
herein.
3.1 Task 1. The contractor shall develop a work management plan
describing the approach, organizational resources, and management
controls to be employed to meet the cost, performance, and schedule
requirements of this statement of work. The plan shall address
dependencies between activities, major milestones and resources to be
applied, estimated costs, follow-up actions, and critical path events
for each major milestone.
3.2 Task 2. The contractor shall prepare and deliver a monthly status
report describing state of deliverables, work accomplished during the
reporting period, status of funds, and any issues or concerns requiring
resolution, to include recommended solutions to all issues and
concerns. The contractor shall conduct at least four in progress
reviews (IPRs) during the performance period to provide comprehensive
status on project deliverables. The contractor shall develop and
publish minutes for IPRs, other meetings and briefings conducted during
the contract performance period.
3.3 Task 3. The contractor shall construct a software development
plan outlining design strategies and implementation plans for
incorporating automated forms update capabilities within DPMS.
3.4 Task 4. The contractor shall modify the DPMS Database Design
Description to incorporate Interactive Forms Management Capability
modifications and enhancements.
3.5 Task 5. The contractor shall provide an operational and
technical test and evaluation plan to support XXXXX's assessment of
software deliverables. The contractor shall participate in the
operational and technical test and shall fix all problems
identified during test and evaluation. The contractor shall
provide orientation training necessary to support operational and
technical testing. XXXX will conduct operational and technical
testing over a 30-Day period, commencing after the delivery of all
capabilities identified in paragraphs 4.6, 4.7, 4.8, 4.9 (below).
Operational and technical testing will be conducted IAW with the
XXXXX approved test and evaluation plan. Testing will include
prescribing directives and forms described per 2.5 through 2.9
(above).
3.6 Task 6. The contractor shall construct a DOCUMENT forms database.
The database shall provide Open Database Connectivity.
3.6.a Establish automated methods and provide software as
necessary for converting digitized logistics forms published by
the US Government Publishing Agency to a DPMS compatible format. DPMS
compatibility is described per paragraph 3.0.g (above).
3.6.b Populate the DOCUMENT forms database. The DPMS database will
be composed of all digitized DOCUMENT proponent forms (approximately
200) now available for download at the US Government Publishing Agency
web site.
3.6.c Provide cross-form search and retrieval capabilities. The
capability must allow the displayable contents of forms and form
fields to be queried across the forms database using single words,
phrases, or combination word/phrase searches. The capability to
perform literal and wildcard textual and numerical searches must
also be demonstrated. Search result statistics must be provided.
The contractor shall consider a future requirement to accommodate
Natural Language searches across prescribing policy directives and
form elements during database development.
3.7 Task 7. The contractor shall synchronize the update process for
forms with their prescribing policy sources (regulations and pamphlets).
3.7.a Establish user screens and software necessary to provide an
integrated cross-reference between all active (approximately 400)
DOCUMENT proponent forms and their prescribing documents.
Document A will be used as a source for populating the cross-
reference.
3.7.b Establish DPMS menu access to the cross-reference.
3.8 Task 8. Integrate forms update and management processes into DPMS.
3.8.a Modify DPMS Publication and User and Workflow Management
tables, user screens, and software to incorporate the forms update
and management processes.
3.8.b Modify Management, Coordinator Management, and Custom
Reports to provide forms management information.
3.9 Task 9. Modify DPMS Form 2028 submission software, user
screens, and transmission and collection software to process recommended
changes for all active (approximately 400) DOCUMENT proponent blank forms.
3.10 Task 10. Demonstrate and provide automatic Form 67
transmission procedures using at least one DOCUMENT proponent blank form.
3.11 Task 11. Demonstrate and provide HTML hosting of DOCUMENT proponent
forms and hyper-linked forms access from a prescribing policy regulation
or pamphlet using at least one DOCUMENT proponent form.
3.12 Task 12. Provide program software documentation as follows:
1) Program Flow Diagram. This should chart the execution of the
management program for handling forms.
2) XXXXX Interactive Forms Management Capability User's Manual. The
User's Manual shall include an Interactive Forms Management Capability
overview and process summary. The Manual shall address: the
application environment, organizational interfaces, security and privacy
requirements, and problem reporting procedures. The Manual shall
provide: equipment familiarization; instructions for software access;
system operating procedures, to include instructions for initiating a
session, stopping and suspending work.
3) XXXXX Interactive Forms Management Capability System
Administrator/Maintenance Manual. The Systems Manual shall include:
an Interactive Forms Management Capability overview; executable software
and source file identification; an "as built" capability design
description; compilation, build, modification procedures; communication
requirements; security and privacy protection procedures; and
requirements trace-ability procedures.
3.13 Task 13. All software applications will be documented as Y2K
compliant. This shall include:
a) Documentation showing Y2K compliance for all COTS products
used by the program (excluding system applications).
b) Include and document descriptions of tests performed and
all test results (including location and testing authority).
3.14 Task 14. A transition plan will be written to outline the steps
necessary for transitioning the Interactive Forms Management Capability
to USAPA or the XXXXX MPPS. The contractor shall include a certification
that XXXXX's hardware configuration satisfies all Interactive Forms
Management Capability system requirements. A contractor site visit will
be performed to gather background information on the current MPPS
configuration.
4.0 DELIVERABLES. These products shall be delivered electronically to
the XXXXX Agency, hereinafter
referred to as the Government. The contractor shall install program
deliverables on MPPS IAW paragraph 3.14 and provide minutes, plans, and
documentation in Microsoft Word 97 or earlier compatible version,
Microsoft Excel 97 or earlier compatible version, or Microsoft Access
97 format. Internet address for delivery is
xxxxx@xxx.xxx.xxx. The mailing address, if needed, is:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
Unless otherwise specified, deliverables may be provided in a contractor-
specified format. Unless otherwise specified, the Government shall have
10 working days to review and comment on deliverables. The contractor
shall have 10 working days to incorporate comments and return a final deliverable.
4.1 Work Management Plan. The contractor shall provide a Task Order
Management Plan for this statement of work. This action plan is to be
delivered within 10 days after contract award. The contractor shall
present the proposed work management plan during a Start of Work
meeting held by XXXXX within 10 days after contract award.
4.2 Monthly Status Reports and IPR. The contractor shall provide
monthly status reports, conduct IPRs, and publish minutes of meetings
as described in paragraph 3.2 (above). The first IPR will be conducted
within 45 days after contract award.
4.3 Software Development Plan. The contractor shall provide a
software development plan for XXXXX approval within 45 days after
contract award.
4.4 Updated DPMS Database Design Description. The revised DPMS
Database Design Description shall at a minimum describe the following
forms database information: data elements, data relationships and
tables, screen formats, frequency and mode of database update. The
contractor shall provide a revised DPMS Database Design Description for
XXXXX approval within 60 days after contract award.
4.5 Test and Evaluation plan. The contractor shall provide
operational and technical Test and Evaluation plans for the Interactive
Forms Management Capability. Both plans shall include specific test
criteria and metrics for determining success, contain software
configuration management procedures to be used during testing, and
address contractor participation in and orientation training for
testing IAW paragraph 3.5 (above). Both plans shall be provided for
XXXXX approval within 75 days after contract award.
4.6 Compatible Form Database. The contractor shall deliver and install
an operational forms database NLT 240 Days after contract award. XXXXX
will complete operational testing of the forms database NLT 30 days
after receipt. The forms database must be adequate to effectively
support its operational purpose and intent, to include: a repository
of blank forms; a tool that allows for forms consolidation, elimination
of obsolete forms; a support tool for improving forms management
practices, to include integrating forms management with policy review
processes and schedules.
4.7 Synchronized Update Capability. The contractor shall provide
integrated forms cross-reference software and DPMS menu access to cross
reference NLT 240 Days after contract award. XXXXX will complete
operational testing of synchronized update software NLT 30 days after
receipt. The cross-reference software must provide DPMS users an
automated method for identifying and maintaining prescribing
relationships between DOCUMENT proponent forms and regulations/pamphlets.
4.8 Integrate Forms Update and Management Capabilities within DPMS.
The contractor shall provide integrated forms update, management, and
report software within DPMS NLT 240 Days after contract award. XXXXX
will complete operational testing of integrated forms update,
management, and report software NLT 30 days after receipt. The
integrated capabilities must be adequate for DPMS users to update and
staff forms in the same fashion and using the same software formats as
policy and procedures are now updated. The integrated forms software
must be adequate for DPMS users to access and maintain Publication and
User and Workflow Management tables for blank forms using DPMS
software, user screens, and procedures.
4.9 Modify Form 2028 Software to include Blank Forms. The
contractor shall modify DPMS change submission, collection, access
screens and software to accommodate blank forms processing NLT 240 Days
after contract award. The modified software shall be adequate to allow
electronic Form 2028s to be submitted and processed for blank forms
in the same manner as now processed by DPMS for regulations and
pamphlets. XXXXX will complete operational testing of modified
Form 2028 submission capabilities NLT 30 days after receipt.
4.10 Demonstrate automatic Form 67 transmission procedures NLT 240
Days after contract award. Contractor will provide a demonstration of
software and associated procedures necessary for electronically
transmitting a completed DD Form 67 between XXXXX and the US Government
Publishing Agency. Contractor will provide demonstration at XXXXX, XXXX,
XXXXX. XXXXX will complete demonstration testing of Form
67 transmission procedures NLT 30 days after receipt.
4.11 Demonstrate HTML Hosting and Hyper-Linking Forms to their
Prescribing Policy Source NLT 240 Days after contract award. Contractor
will provide a demonstration of an HTML hosted blank form, to include
demonstrating hyper-linked access to a prescribing policy source from
the same HTML hosted form. Contractor will provide demonstration at
XXXXX, XXXXX,XXXXX. XXXXX will complete demonstration testing of
HTML Hosting and Hyper-Linking Forms to their Prescribing Policy Source
NLT 30 days after receipt.
4.12 Program software documentation. The contractor shall provide the
following NLT 240 Days after contract award:
1) A Program Flow Diagram as described per paragraph 3.12(1).
2) An XXXXX Interactive Forms Management Capability User's Manual as
described per paragraph 3.12(2).
3) An XXXXX Interactive Forms Management Capability System
Administrator/Maintenance Manual as described per paragraph 3.12(3).
4.13 Y2K certification documentation. The contractor shall provide Y2K
certification documentation, per paragraph 3.13, NLT 240 days after
contract award.
4.14 Transition Plan. The contractor shall provide a transition plan,
per paragraph 3.14, NLT 240 days after contract award.
5.0 PERIOD OF PERFORMANCE.
The period of performance for this contract is 360 days from date of
award.
6.0 PLACE OF PERFORMANCE/TRAVEL. The place of performance for this
effort will be primarily at the contractor's location. The
programs/applications will be developed on the MPPS environment in
XXXXX,XXXXX, if accessible. IPRs and testing will be performed at
XXXXX, XXXXX, XXXXX. Prototype demonstrations will be performed at
XXXXX, XXXXX, XXXXX or XXXXX, XXXXX.
7.0 GOVERNMENT FURNISHED EQUIPMENT/INFORMATION (GFE/GFI). For work
performed at the contractor site, the Government will provide
publications as described per paragraph 2.0. The contractor will be
provided access to technical documentation and DPMS coding as necessary
to support development.
8.0 CONTRACTOR FURNISHED MATERIALS. The contractor will provide all
material as required to complete the statement of work.