A Statement of Work (SOW) is typically used when the task is well-known and can be described

in specific terms. Statement of Objective (SOO) and Performance Work Statement (PWS)
emphasize performance-based concepts such as desired service outcomes and performance
standards. Whereas PWS/SOO's establish high-level outcomes and objectives for performance
and PWS's emphasize outcomes, desired results and objectives at a more detailed and
measurable level, SOW's provide explicit statements of work direction for the contractor to
follow. However, SOW's can also be found to contain references to desired performance
outcomes, performance standards, and metrics, which is a preferred approach.

The Table of Content below is informational only and is provided to you for purposes of
outlining the PWS/SOO/SOW. This sample is not all inclusive, therefore the reader is cautioned
to use professional judgment and include agency specific references to their own
PWS/SOO/SOW.

1. INTRODUCTION ................................................................................................................................................ 3
2. OBJECTIVE ......................................................................................................................................................... 3
3. SCOPE .................................................................................................................................................................. 3
4. REQUIREMENTS AND TASKS ........................................................................................................................ 4
4.1 REQUIREMENTS ........................................................................................................................................... 4
4.2 SPECIFIC TASKS ........................................................................................................................................... 5
5. OPTIONAL TASK ............................................................................................................................................... 8
6. DELIVERABLES AND DELIVERY SCHEDULE............................................................................................. 9
6.1 DELIVERY SCHEDULE .............................................................................................................................. 10
6.2 NOTICE REGARDING LATE DELIVERY ................................................................................................. 11
7. PERSONNEL ..................................................................................................................................................... 11
7.1 KEY PERSONNEL ........................................................................................................................................ 11
7.2 RESUMES...................................................................................................................................................... 11
8. QUALITY ASSURANCE AND MONITORING OF WORK DELIVERABLES ............................................ 11
8.1 GENERAL ACCEPTANCE CRITERIA ....................................................................................................... 12
8.2 QUALITY ASSURANCE.............................................................................................................................. 12
9. GOVERNMENT FURNISHED EQUIPMENT, GOVERNMENTFURNISHED INFORMATION AND
APPLICABLE DOCUMENTS ................................................................................................................................... 12
9.1 GOVERNMENT FURNISHED EQUIPMENT (GFE) .................................................................................. 12
9.2 GOVERNMENT FURNISHED INFORMATION ........................................................................................ 13
9.3 APPLICABLE DOCUMENTS ...................................................................................................................... 13
10. PLACE OF PERFORMANCE ....................................................................................................................... 13
11. PERIOD OF PERFORMANCE ..................................................................................................................... 13
12. ESTIMATED LEVEL OF EFFORT .............................................................................................................. 13
12. ADMINISTRATIVE CONSIDERATIONS................................................................................................... 13
12.1 HOURS OF WORK ....................................................................................................................................... 13

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 1 of 21

13. NON-PERSONAL SERVICES:..................................................................................................................... 14
14. POST AWARD ADMINISTRATION ........................................................................................................... 14
14.1 PRESERVATION, PACKAGING, PACKING, AND MARKING............................................................... 14
14.2 PLACE OF INSPECTION AND ACCEPTANCE ........................................................................................ 14
14.3 SCOPE OF INSPECTION ............................................................................................................................. 15
14.4 INITIAL DELIVERABLES ........................................................................................................................... 15
14.5 NON-CONFORMING PRODUCTS OR SERVICES ................................................................................... 15
15. ACCESS TO GOVERNMENT ELECTRONIC MAIL ................................................................................. 15
16. INVOICE SUBMISSION............................................................................................................................... 16
17. INVOICING INSTRUCTIONS ..................................................................................................................... 16
18. TRAVEL ........................................................................................................................................................ 17
18.1 TRAVEL REGULATIONS ........................................................................................................................... 17
19. CONTRACTING OFFICER’S TECHNICAL REPRESENTATIVE (COTR) .............................................. 18
20.1 ORGANIZATIONAL CONFLICT OF INTEREST ...................................................................................... 19
20.2 NON DISCLOSURE REQUIREMENTS ...................................................................................................... 19
21. SECURITY CONSIDERATIONS ................................................................................................................. 19
22 TRANSFER OF HARDWARE/SOFTWARE MAINTENANCE AGREEMENTS TO FOLLOW-ON
CONTRACTORS ........................................................................................................................................................ 19
23. PRIVACY ACT ............................................................................................................................................. 19
24. TASK ORDER CLOSEOUT ......................................................................................................................... 19
25. PAST PERFORMANCE INFORMATION ................................................................................................... 20
26. CONTRACTOR’S PURCHASING SYSTEMS ............................................................................................ 20
27. DATA RIGHTS ............................................................................................................................................. 20
28. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION CLAUSES
(http://www.arnet.gov/far/) .......................................................................................................................................... 20

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 2 of 21

 STATEMENT OF WORK

Project Name & ID: ______________

May 1, 2011

1. INTRODUCTION

The Office of the Chief Information Officer (OCIO) provides institute wide computer support to support this
mission. This includes helpdesk support, infrastructure operation and management, and the development and
operations of the computer applications needed to manage scientific and administrative resources and support
extramural business activities in the management of the agency grants portfolio.

2. OBJECTIVE

A key mission for the organization is the development and maintenance of data intensive research and
administrative applications in support of the agency mission. To accomplish these tasks necessitates in-depth
knowledge and expertise in all areas of requirements elicitation, application design, documentation, implementation,
maintenance, management to ensure that requirements are met and deliverable products comply with the IT
enterprise architecture and business needs.

To ensure that all agency application development, documentation and maintenance efforts deliver products that
effectively meet approved requirements and established architectures, the services of an expert contractor are
required.

The objective of this statement of work is to obtain a contract to provide support for on-going development efforts
and new efforts described within this Statement of Work (SOW).

Expected benefits of these application design, development, implementation and maintenance support services to the
Government include:

• Increased consistency and value of applications;

• Increased confidence in the products delivered;
• Increased quality of individual deliverables, products, and services provided;
• Reduced project risks;
• Reduced implementation costs;
• Improved user acceptance;
• Improved benefits realization, and
• Reduced operation and maintenance costs.

3. SCOPE

The scope of this effort includes services necessary to provide a full range of application design, development, and
maintenance support. Primarily, but not exclusively, services provided will focus on applications supporting the
agency extramural business process but may include other administrative or scientific applications as well.

All services provided and products delivered must comply with the Government security, Section 508 and
architecture requirements.

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 3 of 21

Specifically, the scope of services required includes:

• Project Management;
• Complete project documentation
• Business application analysis;
• Application requirements definition;
• Application development;
• Application design
• Graphic design
• Application integration
• Application documentation
• Application user support
• Application testing
• Quality assurance

Any contract resulting from this Statement of Work (SOW) may be modified at any time to accommodate increases
or decreases in the number of end users supported, the number of systems requiring support, and legislative changes
that affect agency system and/or data requirements.

4. REQUIREMENTS AND TASKS

In order to support the agency mission, projects and system requirements, the Government requires sophisticated
information technology systems support services. The following section of the SOW describes the requirements and
tasks that shall be accomplished to meet these requirements.

4.1 REQUIREMENTS

The contractor must have demonstrated corporate experience and provide support staff meeting the following
requirements:

• Functional knowledge of the corporate IMPAC II system, general functional knowledge in business
processes including Extramural Grants Management, Budgeting process, Intramural business process, and
the Personnel Management process.

• Proven experience developing software systems utilizing Unified Process (UP), Rapid Application
Development (RAD) and Agile methodologies

• Demonstrated experience in designing, architecting, developing and delivering Java Two Enterprise Edition
(J2EE) applications;

• Demonstrated experience in the development of 3 and 4-tier web applications.

• Demonstrated experience in conducting requirements gathering sessions and workshops

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 4 of 21

 • Demonstrated experience in web application technologies such as HTML,XML/XSL JDBC, JNDI, LDAP,
JavaScript, Java EJBsIappletslservlets

• Demonstrated experience in the use of CSS (Cascading Style Sheets)

• Demonstrated experience in usability assessment

• Experience in understanding of Section 508 regulations and compliance of these regulations in support of
the design of and development of web based applications.

• Knowledge of SAEAF ( Service Aware Enterprise Architecture Framework

• Knowledge of SOA ( Service Oriented Architecture)

4.2 SPECIFIC TASKS

The contractor shall provide several general classes of services including (but not limited to) process management
and reporting and technical planning, assessment, evaluation, design, development, monitoring, requirements
analysis, architecture, graphic design, design, coding, quality assurance testing and deployment. These services
require careful interaction with the government project officer, enterprise system project management staff, other
contractors, product vendors, and management. The contractor shall not play any role in directing or managing
work of any other project or support contractor staff.

The contractor shall provide management and technical services within the scope of this contract to support the
following tasks.

4.2.1 PROGRAM AND PROJECT MANAGEMENT

Work efforts performed in support of this Statement of Work require management expertise, oversight, control, and
direction in team building, communications, time management, quality assurance and quality control and
management, procedure development, risk management, configuration management, cost management, and software
integration. Using state-of-the-art knowledge, skills, tools, and techniques, the contractor shall:

• Review existing change management and track policy and procedures and update them as needed to
address change requests and application defects from receipt through review, analysis, development, and
installation;

• Develop and implement Program and Project Management Plans that identify the management strategies to
be followed and goals to be achieved. These plans shall be revised and updated as necessary to remain
current and effective;

• Provide an effective labor and skill mix to accomplish all tasks;

• Effectively address changes in work priorities and staffing;

• Ensure proper staffing and skill set coverage at all times;

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 5 of 21

 • Ensure deliverable quality and timeliness;

• Provide data for Earned Value Management (EVM) reporting upon request;;

• Develop Work Breakdown Structures (WBS) for each project and task as warranted;

• Develop, coordinate, update and maintain, in IT Systems provided tools, all applicable Standard Operating
Procedures;

• Ensure adequate documentation meeting standards throughout the full software development life cycle
(SDLC);

• Follow an approved iterative development methodology;

• Enforce proper configuration management;

• Ensure compliance with all agency 508 compliance regulations;

• Ensure compliance with all agency security regulations;

• Provide assistance to the staff with regard to security information updates for the applications developed;

• Evaluate current languages and tools and recommend to the Contacting Officer’s Technical Representative
(COTR) new languages and tools as appropriate;

• Provide information, technical, and management briefings and presentations to the COTR and to other staff
as requested by the COTR on all aspects of the work being performed.

4.2.2 DEVELOPMENT AND SUPPORT FOR EXTENSION APPLICATIONS AND ADMINISTRATIVE

APPLICATIONS

The Government has developed multiple applications as extensions to IMPAC II that support extramural business
processes and applications that support the internal business process. The contractor shall enhance and support these
production applications and create new applications as the need arises. Work to be accomplished will focus
primarily on the following systems and their components. However additional systems support and development
may be required.

The contractor shall:

• Monitor, maintain, enhance and manage all existing business applications and correct defects as they
become known. The same software engineering best practices and techniques will be used for application
modifications as are to be used for new system development. All data and programming standards shall be
used and consistently applied.
• Utilize an iterative development methodology for all work done under this contract. The methodology shall
allow users to examine the validity and accuracy of the business requirements and to respond to the
usability and performance of new developments. User testing and acceptance throughout the development
cycle will detect usability issues, missing requirements, and any necessary design changes early in the
process, allowing them to be put in place immediately.

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 6 of 21

 • Identify risks associated with the development of new software efforts, including extension systems, the
analysis and classification of those risks as to severity and likelihood, and the identification of techniques to
mitigate the risks.
• Conduct feasibility/cost-benefit studies, requirements analyses, and all other life cycle activities included in
the design phase, including the use of an object-oriented technology such as the Unified Modeling
Language (UML), development, implementation, and documentation, for the development and
maintenance of systems for long-term use.
• Collect, develop, and analyze software requirements through the use of facilitated user sessions.
• Formulate a business model identifying the proposed (to-be) business processes necessary to improve the
efficiency and effectiveness for each application, as necessary.
• Develop “use cases” and determine the prescribed set of “artifacts” for each phase of each development
cycle.
• Develop java applications using a service-oriented architecture and web services were applicable
• Develop applications in a multi-platform environment, using object oriented programming, with an
understanding of Internet/Intranet architecture.
• Develop software applications prototypes for COTR evaluation.
• Provide Graphic design for application user interface
• Conduct usability analysis and assessments
• Adhere to 508 compliance regulations for all development efforts
• Utilize the Government provided 508 reporting tool to identify and mitigate 508 issues
• Develop, document, and adhere to effective and appropriate configuration management practices.
• Design systems using the Rational Unified Process, or a framework similar to it.
• Assist with the development of business case documents by providing feasibility and high level business
requirements analyses for existing systems or new requests and development cost estimates.

4.2.3 DOCUMENTATION

The contractor shall develop system and user documentation for both existing and newly deployed application
software.

The contractor shall provide the following documentation for each application:

• System Documentation
• Training Documentation
• User Documentation

The contractor shall provide necessary documents upon each completed phase of
Project:

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 7 of 21

 • Inception phase documents shall include Vision, Use Cases, Data Modeling, Risks, Architecture,
Infrastructure, Schedule, Cost Breakdown
• Elaboration phase documents shall include Use Cases, Data Models/Procedures, Test Cases, Models
• Construction phase documents shall include Source Code Baselines, Compile Time-Files, and Component
executables.
• Transition phase document shall include User Guide, Analysis and Design Package, and Maintenance and
Deployment Package.
• Other documents deemed necessary.

All documentation shall be in a format editable by the Government and maintained in the appropriate provided tool.

4.2.4 HELP DESK AND USER SUPPORT

The contractor shall assist in resolving technical issues presented to the help desk.

The contractor shall provide support staff with the technical experience and expertise to diagnose and resolve issues
in a complex, multi-application environment based on
a three-tiered architecture.

The contractor shall provide staff with sufficient business knowledge in support of the applications to understand
and provide assistance with any user issues of a non-technical nature.

5. OPTIONAL TASK

The Office of Communication and Education (OCE) is the public interface. OCE is responsible for the content and
hosting of the agency public web presence and the intranet presence. Additionally, OCE publishes educational
materials relating to all aspects dealing with the mission of the agency.

Due to ongoing efforts to consolidate services for the economy of scale and its administration is planned that xxx
will be absorbing the OCE infrastructure. The first steps will include transitioning to xx the hosting, maintenance
and management of web sites and applications not directly related to the public mission of OCE. The agency
anticipates that this transition will begin during the timeframe of the award of this SOW and will require the addition
of tasks and personnel with specific expertise to accomplish.
The additional tasks would include:

• Site graphic design

• Site statistics reporting , if appropriate, utilizing agency provided tools
• Site content management, either by HTML based tools or an agency provided Content Management System
• Site usability testing
• Site and document 508 testing and reporting

The four additional positions required by this effort are:

• Senior graphic designer/usability expert

• Senior 508 person
• Two Content managers

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 8 of 21

6. DELIVERABLES AND DELIVERY SCHEDULE

All written deliverable products shall be submitted in electronic draft format for the COTR’s review and comment.
Final copies shall be delivered to the COTR five (5) working days after receipt of the Government’s comments.
Deliverables shall be submitted with an accompanying letter describing the deliverable product and delivered to,
Office of the Chief Information Officer.

All written draft deliverable products shall be submitted in electronic format for review and comment. Final
deliverable products shall be submitted in three (3) final bound copies, one (1) unbound flat final copy suitable for
reproduction, and an electronic copy. Other quantities and formats may be submitted after prior approval or request
from the COTR. Electronic copies will be submitted in Microsoft Office 2003 format unless prior approval for
another format has been obtained from the COTR.

The delivery schedule of products is outlined in a delivery schedule table below. Other written and technical
deliverables shall be submitted according to the schedules identified in the approved Contract Management Plan
developed under this SOW. The Contractor shall deliver the following:

Contract Management Plan – The Contractor shall prepare draft and final Contract Management Plan specifying the
tasks, sub tasks, and approaches to be used to provide the services and products specified including the deliverable
documents, analyses, and reports necessary to fulfill the requirements of this SOW. This Plan shall be delivered in
draft not later than one week following the award of the Contract.

Quality Control Plan – The Contractor shall prepare draft and final versions of a Quality Control Plan specifying the
tasks, sub tasks, and approaches to be used to ensure adequate quality and integrity of work developed. This Plan
shall be delivered in draft not later than one week following the approval of the Contract Management Plan.

Program and Project Plans – The Contractor shall prepare draft and final versions of specific Program and Project
Plans when necessary or as directed that are appropriate for the size and scale of technical efforts being undertaken.
These plans shall specify the tasks, sub tasks, dependencies, resource requirements, schedules, and milestone dates
required to complete specific technical programs or projects. When approved by the COTR, these plans shall be
used to monitor, control, and report progress, issues, and resource expenditures. These plans shall be updated as
required and approved by the COTR as required to maintain currency with project objectives, activities, and
direction.

Weekly Contract Status and Progress Review – The Contractor shall participate in weekly management review
meetings and be prepared to present and discuss the following:

• Activities planned for the week;

• Work and deliverables completed during the period;

• Status of ongoing activities;

• Activities planned for the following period;

• Problems or issues projected or identified;

• Alternatives and/or recommended solution(s) for identified or projected problems or issues; and

• Known or projected resource (staff and funding) and schedule impacts.

Monthly Status and Progress Summary Report – The Contractor shall prepare and submit draft and final Monthly
Status and Progress Summary Reports. Draft reports shall be forwarded to the COTR by the 10th calendar day of
the month following the reporting period. In addition, this Report shall be presented to the enterprise system project

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 9 of 21

managers for discussion, if requested by the COTR. A final report shall be submitted five days after receipt of
government comments.

This Report and presentation may be delivered in conjunction with the presentation of the Contractor’s Weekly
Contract Status and Progress Review. This Report shall be a compilation of weekly management issues and
meetings during the month reported and in sufficient detail to ensure understanding of performance progress and
issues.

The delivered Reports must be suitable for forwarding to executive management. The format and content of the
Report shall include the following:

• Activities planned for the reporting period;

• Work and deliverables completed during reporting period;

• Status of ongoing activities including percentage of completion;

• Activities planned for the following reporting period;

• Planned travel during the following reporting period;

• Problems or issues projected or identified;

• Alternatives and/or recommended solution(s) for identified or projected problems or issues;

• Known or projected resources (staff and funding) and schedule impacts; and

• Status of project funds including monthly and total expenditures and funds remaining;

• Summary of tasks performed under section 4.2 of the Statement of Work.

Other Deliverables – The Contractor shall prepare and submit draft and final copies of other deliverable analysis,
evaluation, review, and report products necessary to meet the requirements of technical tasks and activities
performed in the provision of this Statement of Work. All written deliverable products shall be delivered in
electronic draft format for Government review and comment. Final copies shall be delivered in five (5) working
days after receipt of government comments.

Final Contract Report - The contractor shall provide a final report to the COTR at the conclusion of the period of
performance. This report shall summarize objectives achieved, significant issues, problems, and recommendations
to improve the process in the future.

The delivery schedule of key written management products is specified in the delivery schedule table contained in
this section. The contractor shall deliver the following:

6.1 DELIVERY SCHEDULE

Deliverable Deliverable Due Date

Draft Contract Management Plan One week after Contract Award
Final Contract Management Plan Five working days after receipt of Government
comments.
Draft Quality Control Plan One week after receipt of the Final Contract
Management Plan
Final Quality Control Plan Five working days after receipt of Government

APPLICATION SERVICES AND COMPONENT FRAMEWORK Page 10 of 21