Peace Corps VDS Redesign SECTION C:PERFORMANCE WORK STATEMENT (PWS) Section C - 3-8-10 PC 10 R CP 01 March 8, 2010

Solicitation PC-10-R-CP01 March 8, 2010
VDS Redesign
SECTI ON C: PERFORMANCE WORK STATEMENT (PWS)
TABLE OF CONTENTS- SECTION C
1.0 Volunteer Delivery and Support System Redesign: Overview
1.1 Existing VDS System
1.2 Goal of the Overall VDS Redesign Program
1.3 Goal of Volunteer Lifecycle Management Redesign
2.0 Peace Corps: Overview
2.1 Background
2.2 Metrics for scalability
3.0 Peace Corps: Current Environment
3.1 Current Physical Environment
3.1.1 Domestic Operations
3.1.2 International Operations
3.2 Current IT Infrastructure and Standards
3.3 Current Systems
3.4 Current Architecture
3.5 Current Volunteer Delivery and Support (VDS) System
4.0 Current VLMS Challenges
5.0 VLMS Objectives
5.1 Overarching Systems
5.2 Detailed VLMS Objectives
6.0 General Requirements
6.1 Business Requirements
6.2 Technical Requirements
6.2.1 Web Portal, Web Parts/Portlet Integration and Access Control
6.2.2 Service Oriented Architecture (SOA)
6.2.3 Peace Corps Specific SOA To-Be Environment
6.2.4 System Interfaces
6.2.5 Security Requirements
6.2.6 Hosting Support
6.2.7 Training


6.3 Implementation Plan
6.3.1 Planning
6.3.2 Configuration
6.3.3 Data Migration
6.3.4 Testing
6.3.5 Product Support
6.3.6 Software Upgrades
6.3.7 Help Desk Support


1.0 Volunteer Delivery and Support System Redesign Program Overview
The Volunteer Delivery and Support (VDS) System encompasses all the processes and
systems required to manage outreach, recruitment, evaluation (professional and medical),
placement, support (professional and medical), and return of Peace Corps Volunteers.
The VDS system will be branded by Peace Corps as the DOVE system (Database of
Volunteer Experience).
Peace Corps is currently fielding two separate, but complementary, RFPs to upgrade the
business systems and processes of two of the core elements of the VDS System, the
Volunteer Lifecycle Management System (VLMS) and the Volunteer Electronic Health
System (VEHS) components of the VDS System.
This RFP addresses solely the needs of the Volunteer Lifecycle Management System
(VLMS).Information on Volunteer Electronic Health System (VEHS) is provided as
reference material to aid in understanding the broader context of the Volunteer Delivery
and Support System.
1.1 Existing VDS System
The existing VDS System was developed to organize and administer the
Agencys central business processes required for recruitment, placement and
support of Volunteers for two years of overseas service and continuing interaction
after service.
The existing System is a patchwork of paper-based and electronic systems
developed over many years and requires a comprehensive revision in order to
meet current governmental requirements and to cope with anticipated expansion.
1.2 Goal of the Overall VDS Redesign Program
The goal of the overall VDS System Redesign is to develop and upgrade the core
VDS business systems and processes required to manage all stages of the
Volunteer lifecycle, encompassing both Volunteer support and medical
management.
1) Volunteer Lifecycle Management System includes the following
processes:
Marketing; recruiting; application; requests from Posts; evaluation and
selection; placement; training; service; close of service; and ongoing
interaction as alumni.
2) Volunteer Electronic Health System (which is not part of this RFP)
includes the following processes:
Medical support for Volunteers in the field during service, and any
service-related support required after service.


1.3 Goal of Volunteer Lifecycle Management Redesign
The goal of this specific COTS redesign is to review, develop and upgrade the
business systems, and the associated business practices required for the
management of the Peace Corps Volunteer lifecycle.
The new system must meet mandated government standards and be designed to
efficiently and comprehensively cope with changing Agency requirements,
particularly those dealing with growth, changes in countries of service, and
varying Volunteer requirements.
2.0 Peace Corps: Overview
2.1 Background
President Kennedy formed the Peace Corps with an executive order on March 1,
1961 and in 1979, it was made a fully independent agency. Since its founding,
Peace Corps has served in 138 developing countries, and nearly 200,000
American citizens have served as Peace Corps Volunteers (PCVs). The
PeaceCorps has approximately 2000+ employees, 800 of whom work in the
United States at headquarters in Washington DC and in 9 regional recruiting
offices, and 1200 who work in our Posts throughout the world. Some Posts are in
resource-challenged environments where electricity and connectivity are
unreliable. Post headquarters offices are located in major cities, but Volunteers
are placed in both urban and rural environments. Communication between and
among headquarters, regional recruitment staff (including field-based and contract
recruiters), Posts, Volunteers, and alumni must function within this context.
For more information on the Peace Corps mandate and mission, see Attachment
#1. See also the Peace Corps website:
http://www.peacecorps.gov/index.cfm?shell=learn.whatispc.
2.2 Metrics for scalability
Over 180,000 individuals contact the Peace Corps each year expressing an interest
in Volunteer Service. In fiscal year 2009, 15,386 individuals completed an
application to serve in the Peace Corps. Recruitment (Office of Volunteer
Recruitment and Selection VRS) interviewed and assessed about 63% (9,706)
of these applicants. From this group, approximately 52% (7,900) of the total
number of applicants were recommended for Peace Corps Volunteer service.
Approximately28% (4300) of the total number of applicantswere evaluated and
medically cleared for Peace Corps Service and were invited to a specific job and
country. Roughly 3,700 of this group entered a Training Program in their country
of service. Close to 3,000 per year successfully complete a two year tour of duty.
(For a more detailed breakdown, please see Attachment 2: VDS Funnel)
Because of the two-year service term, approximately half of the Volunteers cycle
in or out each year. In 2009, the Peace Corps deployed approximately
4,000Volunteers out of approximately 15,000 applications and

supportedapproximately 8,000 Volunteers in 70+developing countries. The Peace
Corps anticipates significant growth in the next five years. As many as 8,000
Volunteers may be placed each year, with up to 15,000 serving abroad at any
given time.
3.0 Peace Corps: Current Environment
3.1 Current Physical Environment
3.1.1 Domestic Operations
Peace Corps headquarters is located in Washington, DC. There are nine
Regional Recruiting Offices located in the following cities:
Atlanta, GA
Boston, MA
Chicago, IL
Dallas, TX
Los Angeles, CA
New York, NY
San Francisco,
CA
Seattle, WA
Arlington, VA
While most Recruiters currently operate out of the Regional Recruiting
Offices, Peace Corps has been moving towards the placement of more
field-based Recruiters.
3.1.2 International Operations
Peace Corps international offices and their operations are called Posts.
They are spread out world-wide amongst three administrative regions:
Africa; EMA (Europe, Mediterranean and Asia) and IAP (Inter America
and Pacific.) Typically the Post headquarters office is in the capital city of
each host country. Each Post uses remote sites for training and other
administrative and medical functions. Volunteers are placed at work sites
in rural and urban communities throughout the host country.
Please note that due to programming needs, emergency situations, and
other reasons, a number of Posts can be opened or closed in any given
year. In emergency situations, Volunteers may need to be pulled out on
short notice. Below is the current listing of Posts by Regions.
Africa
Benin
Botswana
Burkina Faso
Cameroon
Cape Verde
Ethiopia
Ghana
Guinea
Kenya
Lesotho
Liberia
Madagascar
Malawi
Mali
Mauritania
Mozambique
Namibia
Niger
Rwanda
Senegal

Sierra Leone
South Africa
Swaziland
Tanzania
The Gambia
Togo
Uganda
Zambia
EMA
Albania
Armenia
Bulgaria
Cambodia
Georgia
Indonesia
Jordan
Kazakhstan
Kyrgyz Republic
Macedonia
Moldova
Mongolia
Morocco
Philippines
Republic of
Azerbaijan
Romania
Thailand
The Peoples
Republic of China
Turkmenistan
Ukraine

IAP
Belize
Costa Rica
Dominican
Republic
Eastern Caribbean
Ecuador
El Salvador
Federated States
of Micronesia
Fiji
Guatemala
Guyana
Honduras
Jamaica
Mexico
Nicaragua
Panama
Paraguay
Peru
Samoa
Suriname
Tonga
Vanuatu

3.2 Current IT Infrastructure and Standards
Current IT infrastructure is defined in Current Architecture, section 3.4 below.
For Peace Corps system development standards please refer to the Peace Corps
Systems Development Lifecycle (SDLC) Handbook Version 4.2 (Attachment
3: SDLC Handbook) The SDLC outlines the policies, standards and lifecycle
that govern information technology systems at Peace Corps.
3.3 Current Systems
Over the past 20-plus years, Peace Corps information systems and technology
have incorporated a variety of platforms, system owners and functions to support
various activities. Recent initiatives have included examples such as the
following: a financial system (Odyssey), an overseas infrastructure system (GSS

3.0), databases for in-service volunteers (VIDA and VRT) and a medical system
(Expert). (Attachment 4: Enterprise Architecture Systems Map. This map
provides a depiction of the multiplicity of systems and platforms required to
support the current VDS system. See also Attachment 5, Volunteer Delivery
System Model, for a full listing of Peace Corps Systems and data flows.)
Some of these systems have been built in a piecemeal fashion that reflected
shifting priorities, available funding and current technology. (See Table 1 below)
Roughly four eras of technology can be identified. While the earliest period,
Mainframe, had been successfully migrated to other systems, Peace Corps
maintains three separate periods of software and systems development.
Even with the latest iterations of Peace Corps IT systems to support Volunteer
Delivery, the current system remains primarily a paper and process-based system.
Assistive/automated workflows are not well implemented, if at all, and much
information resides outside of any IT system in file folders and cabinets and in
locally developed spreadsheets created by individual offices or Posts.
Table 1
Era Mainframe PCApps BizApps .NET/Aquifer
Data Tier
Mainframe
Oracle
UNIX/Windows
Oracle
UNIX/Windows
Oracle
Windows
SQL Server
Oracle
Application
Tier
ColdFusion .NET/Aquifer
Presentation
Tier
Dumb Terminal
Thick Client
Oracle Forms
Web Forms
Smart Client
ASP .NET
Time

3.4 Current Architecture
The Peace Corps Segment Architecture consists of eight systems spread amongst
three segment areas. The segments are illustrated below in Table 2.
Core Mission Area Segments consist of the Volunteer Delivery and
Support System (VDS), Medical Services, and Post Services.
The Business Services Segments consist of Human Resources, Financial
Systems and Inspector General Systems.
Enterprise Services consist of the Global Network and Global
Infrastructure which includes Domestic, IAP, EMA and Africa.

The Peace Corps Technical Architecture is predominantly made up of Wintel
systems. Windows XP is the desktop operating system and Windows 2000, 2005
and 2008 physical and virtual servers reside in the on-site data center.
Additionally, there are several HP-UX and Linux systems in the on-site data
center. Peace Corps maintains a disaster recovery site outside of Washington DC.
Databases include Oracle 10i and Microsoft SQL Server 2000, 2005 and 2008.
Many, if not all, business units and overseas Posts maintain their own Access and
Excel-based data. File and print services are managed via Windows 2005 and
2008 servers. Active Directory (AD) is in place and a single AD structure is
being implemented at all overseas Posts connected to the Peace Corps global
network. Microsoft SharePoint is currently in the Peace Corps environment.
Approximately a third of all Posts (all of IAP and a few Posts in EMA and Africa)
are integrated into the Peace Corps global network via VPN using Ciscos Wide
Area Application Services (WAAS). The WAAS provides both security and
WAN acceleration. The remaining Posts are disconnected from the Peace Corps
global network on their own un-trusted domains. However, they are connected to
the Internet via either local ISP and/or VSAT. VSAT is predominantly used in
Posts in Africa. Overall, the architecture allows business-related communication
by all Posts to HQ via custom-built applications.
Peace Corps Systems have been developed using Oracle Forms, ColdFusion,
Java, J2EE & .NET. Users in the US and at Posts typically have multiple logins
to access different systems. Single sign-on has yet to be implemented.


Table 2

3.5 Current Volunteer Delivery and Support (VDS) System
The VDS is a complex mix of formal and informal processes that span systems,
databases, organizational divisions, culture, time and space. Many parts are
automated, others are not. In many regards, the process is very well documented.
Differing historical initiatives created a rich and detailed description of processes,
data, challenges and opportunities.
The Volunteer Lifecycle is illustrated below (see Table 3), with a brief
explanation. (Please see the scenario in Section M for a description of the eight
stages of Volunteer Lifecycle.)


Table 3

1. RECRUIT: Prospective Volunteers are recruited by staff located
throughout the United States. Peace Corps conducts outreach via
multiple media and means. The effectiveness of outreach ismonitored
and tracked. Interested individuals indicate interest through the Peace
Corps website where key data is captured. (Prospect)
2. APPLY: Applicants for Volunteer service (98+%) apply through a
web-based form. Applications are evaluated and suitable applicants
are interviewed. (Attachment 6: Application; Attachment 7: Peace
Corps Response Application) (Applicant)
Peace Corps
Volunteer
Delivery
Lifecycle
2. Apply
1. Recruit
5. Place
4. Evaluate
3. Nominate
8. Return
7. Serve
6. Train

3. NOMINATE: After applicants are interviewed by Recruiters, they
are evaluated and those found suitable are nominated for further
evaluation possibly leading to Peace Corps service. (Nominee)
4. EVALUATE: Background and medical evaluations are
conducted.All Peace Corps and Peace Corps Response Applicants
must go through both a background check and a
medical/dental/counseling review process before being qualified for
service. (Nominee)
5. PLACE: Based on skills, availability and the health evaluation,
qualified nominees are invited to be Volunteers in a specific country to
support a specific project or country program. Projects include, but
are not limited to, the following areas: health; environment, business,
community development, agriculture, and education. (Invitee)
6. TRAIN: By accepting invitations to serve, invitees become trainees
when they are brought together in the United States as a group to
complete their registration. Afterwards, they are sent abroad to their
country of service for an 8-12 week Pre-Service Training (PST).
Based on host country needs and pre-arrival information on trainee
skills, training is developed to prepare Volunteers to acquire language
ability and deal appropriately with project-specific technical
requirements, as well as cross-cultural, health and safety issues.(Peace
Corps Trainee/PCT)
7. SERVE: Based on host country needs and on-site research, Peace
Corps staff at country Posts assign Volunteers to a variety ofhost
country communities and agencies where they will live and work for
two years. Volunteers are placed in communities and agencies to work
within the context of their specific project areas, and are given further
training and support as possible over their two years of service.(Peace
Corps Volunteer/ PCV)
8. RETURN: Returning volunteers are contacted to fulfill ongoing
Agency needs that address recruiting, funding, Agency support, and
program participation, in addition to invitations to receive repatriation
assistance. Peace Corps Response (PCR) recruits and places Returned
Peace Corps Volunteers (RPCV) in short-term, 6 to 12 month
assignments, usually in countries where Peace Corps currently serves,
has served, or is planning to open new programs. RPCVs must apply,
and if selected, must then be medically and legally cleared. The new
Lifecycle Management System must incorporate the PCR application,
evaluation and placement processes and be integrated fully into the
business process flow. (Alumni/RPCVs)


4.0 CURRENT VLMS CHALLENGES
Historically limited budgets have resulted in piecemeal and stove-piped
development of independent databases which hampered effective
communications with applicants and resulted in ineffective integration of data
between users. Current systems span multiple technological platforms.
Under the Peace Corps Act, federal employees of the Agency are term-limited
to five years. The five-year rule results in increased staff turnover and
reduces institutional knowledge and memory.
Diverse existing systems require integration with each other. The new
VLMSProgram will need to phase out many of these legacy systems in
multiple cycles in order to reduce the overall risk to the agency.
Peace Corps employs a subjective, individualized screening process to
determine suitability for service and to assess the skills and experience to
match the expressed needs of post requests.
Integration between recruiting/placement and medical management, especially
concerning the function of pre-service medical screening, has been limited.
Managing issues out of normal processing procedures, such as the placement
of married couples with diverse skill-sets and older applicants with broader
professional experiences.
Peace Corps has over 70 overseas Posts interconnected by a distributed world-
wide network; many suffer from low-bandwidth, high-latency connections
and inconsistent electrical supply requiring smart client applications.
5.0 VLMS OBJECTIVES
5.1 The overarching systems supporting the VLMSProgram shall:
1. Provide a coherent, integrated system using industry standard best practices
that ensures seamless integration with current applications, including but not
limited to the new proposed VEHS.
2. Provide for system implementation/set-up 60 days after award, with pilot
phase testing to start 1 October, 2010, and full deployment completed 18
months after the award.
3. Provide a state of the art system architecture that is stable, with cost effective
upgrades, short learning curves, and is easy to use and manage.
4. Meet the overall goals and requirements of Peace Corps proposed business
processes (as stated in Appendices A and B).
5. Enable better communication via information sharing and workflow by
creating synergy between and among integrated systems (see Paragraph
6.2.4and Table 4.)

6. Include mechanisms to provide and support reusable service development and
service governance policy, and incorporate version management to support
future versions as the systems continue to mature.
7. Ensure that appropriate information is available to domestic staffand
Postsabroad based upon the defined roles and responsibilities ofusers.
8. Provide tools to enable flexible reporting to support informed business and
policy decisions.
9. Provide scalability to permit effective increases in number of prospects,
Volunteer applicants and their placement. Support the rapid scaling up of
applicant processing while reducing associated Agency costs of hardware,
staff, processing and overhead.
10. Provide metrics throughout the Volunteer lifecycle to identify opportunities
for process oversight and improvement.
11. Provide necessary security and privacy provisions, policies, procedures and
oversight to meet federally mandated security regulations for
applicants/Volunteers and the Agency.
12. Insure the system has a common look and feel, set of data values, branding,
and access and processing methods.
13. Implement a system which is sustainable, independent of specific staff it
must not be affected by the ramifications of frequent staff turnover due to the
Agencys 5-year rule.
5.2 Detailed VLMS Objectives
In addition to the Overarching Objectives in Section 5.0, the solution shall:
1. Manage and maintain information of individuals from first inquiry through the
rest of their association with Peace Corps.
2. Enable outreach to all American citizens, particularly those interested in Peace
Corps service including individuals with skill sets needed to fill specific
position descriptions at Overseas Post.
3. Provide an easy-to-use portal for online Applicants that they will continue to
use throughout the Volunteer lifecycle.
4. Enable matching of applicants with country program placements who are
otherwise out of standard processing procedures, such as couples and
applicants with strategic skills.
5. Assist in matching applicants to positions based on demand from Post and
improve Volunteer recruitment and placement in context of skills matching
and personal readiness.
6. Provide tools to assess the suitability of applicants based on their
qualifications, soft and hard skills as defined by Post.

7. Process the Entry on Duty of new Trainees/Volunteers while reducing the
number of forms andamount of paper used in the process.
8. Track Peace Corps Volunteer progress and accomplishments.
9. Provide tools to maintain the relationship with returned Peace Corps
Volunteers and enable appropriate information sharing with external systems.
6.0 General Requirements
The Contractor shall provide a web-based Volunteer Lifecycle Management System. The
Contractorshall provide a system and services that address the business and technical
requirements specified in Appendices A and B. In summary:
The VLMS, services, and interfaces acquired under this contract shall be
deployed in phases throughout the period of performance in order to reduce
Agency and VDS Program risks.
The system shall be externally hosted with all services provided by the
Contractor. The hosting facility must meet all Peace Corps physical and cyber
security requirements for hosting Sensitive but Unclassified (SBU) data
(Attachment 8: FIPS-199; Section 6.2.4: Security Requirements).
Additionally, the Contractor shall be required to produce status reports, training,
assessments of pilot system implementations, and Help Desk services in an
ongoing and as-required basis.
The Contractor shall submit an implementation plan describing how it will meet
the requirements specified in this solicitation.
Once the VLMSis implemented and enters production mode, the Contractormust ensure
that the VLMS is continuously available on a 24/7 basis as defined and agreed to in the
Service Level Agreements. (Appendix B)
6.1 Business Requirements
The system shall meet the requirements found in Appendix A,Business
Requirements.
6.2 Technical Requirements
The system shall conform to the technical environment as described within this
section and the detailed requirements as specified within Appendix B.
6.2.1 Web Portal, Web Parts/Portlet Integration and Access Control
Due to the need to integrate with the Volunteer Electronic Health System
(VEHS), the VLMS requires a Web Portal as part of the Contractors
proposal. The Web Portal must include support for Web Parts and Portlet
integration. Furthermore, the Contractor mustprovide a single sign-on
solution to enable seamless access to related systems outside of the
VLMS, most importantly the VEHS. The goal is to provide a unified user

interface with a similar look and feel and reduce the amount of password
fatigue required to navigate multiple connected systems.
6.2.2 Service Oriented Architecture (SOA) Definition
Peace Corps future Information Technologies architectural direction will
embrace the use of SOA. Refer to A Practical Guide to Federal Service
Oriented Architectureversion 1.1 June 30, 2008
(http://www.whitehouse.gov/omb/e-gov/pgfsoa.aspx) for more details on
the definition and recommended approach in implementing a Service
Oriented Architecture within the federal government.
6.2.3 Peace Corps Specific SOA To-Be Environment
The future SOA architectural direction for Peace Corps will make use of
an Enterprise Service Bus (ESB), as depicted in Table 4. An ESB will
enable communications and information sharing between major
applications.
6.2.4 System Interfaces
The Contractors proposal must providesystem interfaces that will
automate data exchanges between the VLMS of this solicitation, and other
Peace Corps systems connected to an Enterprise Service Bus (ESB). An
ESB to support SOA-based systems is currently under development.
Microsoft BizTalk was chosen as the ESB platform. Table 4 illustrates the
major systems that will be integrated into the ESB. Those systems and
additional systems are listed below:
Volunteer Electronic Health System
Existing Software related to Volunteer Lifecycle Management
and Support (PCVDBMS and MEDDBMS)
Odyssey (E-Business Financials and HRMS/Payroll)
ForPost/ForHQ (Post/HQ portions of Odyssey)
Microsoft Office SharePoint Server (MOSS)
CIRS (Crime Incident Reporting System, used to report crimes
against Volunteers to HQ)
VIDA (Volunteer Information Database Application, used to
manage Volunteer and basic program information at Post)
PCVRT (Peace Corps Volunteer Reporting Tool, used to
manage Volunteer activities and their impact)
Legacy Peace Corps applications (Includes many of the
applications built using Oracle Forms and ColdFusion to
support the current VDS system)
Additionally, the Contractor shall define requirements for implementing
appropriate interfaces to allow data exchanges for purposes of eliminating

manual procedures and for tracking the status of new applicants, current
volunteers and RPCVs.

Table 4

Table 4 depicts only four of the eight stages of the VLMS.
All eight stages of the lifecycle are depicted in Table 3
6.2.5 Security Requirements
The Volunteer Lifecycle System is a Major Application (MA) in the Peace
Corps System Inventory as based upon the Office of Management and
Budget (OMB) Circular A- 130 Appendix III
http://www.whitehouse.gov/omb/circulars_a130_a130appendix_iii.
Furthermore, based on the information to be processed, transmitted and
stored by the Volunteer Lifecycle System and the impact to the Agencys
mission of a loss in the availability, integrity or confidentiality of the
information, this MA has been categorized as a moderate impact system
per the criteria provided in the Federal Information Processing Standards
(FIPS) 199- Standards for Security Categorization of Federal Information
and Information
Systemshttp://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-
final.pdf and NIST 800-60, Revision 1, Guide for Mapping Types of

Information and Information Systems to Security
Categorieshttp://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-
60_Vol1-Rev1.pdf and http://csrc.nist.gov/publications/nistpubs/800-60-
rev1/SP800-60_Vol2-Rev1.pdf. The analysis and evaluation is included
in Attachment 8, FIPS-199.
The Volunteer Lifecycle Management systemmust meet current and future
requirements of all relevant Office of Management and Budget (OMB)
Memorandum, Federal Information Processing Standards (FIPS),
andNational Institute of Standards and Technology Special Publications
(NIST) http://csrc.nist.gov/publications/PubsSPs.html, including the
requirements of OMB Memoranda, FIPS, other NIST SPs and other noted
references, Recommended Security Controls for Federal Information
Systems under all security controls indicated as part of the moderate-
impact system baseline. This list includes but is not limited to:
OMB Memorandum M-06-16, Protection of Sensitive Information,
June 2006.
OMB Memorandum M-07-16, Safeguarding Against and
Responding to the Breach of Personally Identifiable Information,
May 2007.
FIPS-140-2 Security Requirements for Cryptographic Modules
FIPS-197 Advanced Encryption Standard
FIPS-199 Standards for Security Categorization of Federal
Information and Information Systems
FIPS-200 Minimum Security Requirements for Federal
Information and Information Systems.
NIST SP 800-18, Guide for Developing Security Plans forFederal
Information Systems;
NIST SP 800-30, Risk Management Guide for Information
Technology Systems;
NIST SP 800-34, Contingency Planning Guide for Information
Technology Systems;
NIST 800-37, rev 1, Guide for Applying the Risk Management
Framework to Federal Information System;
NIST SP 800-53, Recommended Security Controls for Federal
Information Systems.
The Contractor shall comply with the delivery dates for system
applications to be submitted for independent validation & verification to
complete both preliminary and final authorizations to operate
Peace Corps will work in conjunction with the Contractor to meet the
requirements of preliminary and final Authorizations to Operate. Peace
Corps will provide resources for final approval authority in accordance
with NIST 800-37.


6.2.6 Hosting Support
The Contractoris required to provide an external hosting solution that
provides full service support, including the development, testing, training,
pilots, phased implementation and production operation of the Volunteer
Lifecycle Management System.The Contractor must provide at least one
physical environment separate from production. The externally hosted
solution is required to meet the technical requirements as specified in
Appendix B-14 and meet Service Level Agreements as specified therein.
6.2.7 Training
The Contractor is required to propose best practices, timing, and
documentation for the Volunteer Lifecycle Management System.
Training shall be provided at the Peace Corps Washington DC
Headquarters site.
Training and documentation shall be generated, as applicable, for testing,
acceptance and for each production phase.
The following types of training are required:
Training-of-Trainers (TOT)
The TOT is to enable designated Peace Corps staff to subsequently
train other staff as needed. The TOT shall be focused on overall
system use and navigation as well as specific sub-functions. The
TOT shall cover all levels of end users from High-End Users with
special permissions through to Managers with special approvals
and overviews.
Peace Corps System Administrators
Training and documentation shall be provided directly to Peace
Corps designated System Administrators.
Peace Corps Technical Development Staff
Training and documentation shall be provided directly to Peace
Corps technical development and support staff for the purpose of
data reporting and interface processing across the Enterprise
Service Bus.
6.3 Implementation Plan
The Contractor shall develop an implementation plan addressing, at a minimum,
the areas below. The following activities occur within the context of the Peace
CorpsSDLC (Attachment 3: SDLC Handbook)
6.3.1 Planning
The Contractor shall support planning efforts that include, but are not
limited to, analyzing organizational needs; defining goals, objectives and
metrics; planning implementation to include which components will be

rolled out; identifying and mapping requirements to system components;
scheduling and assigning resources for a successful implementation based
on organizational requirements; and backup and disaster recovery
planning.

6.3.2 Configuration
It is anticipated that the Lifecycle Management System will consist of one
or more best-of-breed commercially available COTSproducts with limited
custom development. Therefore, the Contractor shall be required to
provide a fully configured system that will be available, via Web access,
to all users within the Peace Corps environment. The Contractor shall
propose only fully commercialized software.
6.3.3 Data Migration
The Contractor shall work in conjunction with Peace Corps in the
migration of data from existing legacy systems to the Volunteer Lifecycle
Management System. The Contractor shall be responsible for the
generation of specifications and development of required load routines.
Peace Corps will provide data for migration from legacy systems in the
load format.
6.3.4 Testing
Contractor shall conduct testing at various stages throughout the
development and production stage of the Volunteer Lifecycle
Management System and for the duration of the contract. The
Contractorshall provide technical support to assist with error detection
prior to rollout and to ready the system for the production environment.
The Contractor shall also provide a separate physicalenvironment for
Peace Corps staff or their designees to conduct testing.
6.3.5 Product Support
Technical Support shall consist of Product Support and Software updates
as specified in Appendix B, Technical Requirements. Such technical
support services shall be provided in accordance with the Contractors
software technical support policies in effect at the time the services are
provided. During the period of performance of this contract, the
Contractor shall not materially reduce the level of service provided in its
technical support policies in effect as of the effective date of the contract.
The Contractors Product Support shall include, but not be limited to, the
following:
24/7 problem diagnosis and resolution through access to a
Lifecycle Management System Help Desk that will provide system
users with technical information and assistance
Near-time solutions through 24/7 web and telephone access to
technical expertise

Rich, web-based technical resources, including technical
repositories; rapid information access; and the ability to log and
track service
Contractor Support Services for Lifecycle Management System
development for all system releases and patches
Solutions based on universal standards and best practices to ensure
consistent, accurate support
High-quality problem analysis and responsiveness on submitted
service requests depicting methodology and SLA parameters
Prioritization of service requests based on problem severity
6.3.6 Software Upgrades
Contractor software assistance and problem resolution shall include, but
not be limited to, the following:
Program updates/upgrades, including general maintenance releases
and selected functionality releases. Upgrade means a subsequent
release of the program that the Contractor generally makes
available for program licenses to its supported customers, provided
Peace Corps has ordered software upgrades for such program
licenses for the relevant time period. Upgrade does not include
any release, option, or future program that the Contractor licenses
separately.
Documentation updates
Bug information and patches as made available
The Contractor shall notify the COTR of any new upgrades to enhance the
system. The Peace Corps reserves the right to accept or decline proposed
software upgrades. There shall be no additional cost for upgrades and
enhancements that are part of the core product.
6.3.7 Help Desk Support
Contractor shall provide Help Desk technical support will be provided as
tier-2 through the Peace Corps Help Desk. The Peace Corps Help Desk
will provide all direct user support (including, but not limited to,
hardware, software, and network) to the users as the tier-1 Help Desk.
The Contractor will only be contacted by the Peace Corps Help Desk to
resolve issues relating to the Volunteer Lifecycle Management System
application itself. No users will directly contact the Contractor and the
Contractor will not have to address any issues relating to user access to
Peace Corps systems. The cost for this service shall be included in the
proposal.
The Contractor shall provide support on a 24/7 basis as mutually agreed in
Service Level Agreement. For description of the requirement, please see
Appendix B, section 8, the Maintenance / Support portion of the
technical requirement. The Contractor shall provide status reports based
upon the agreed upon Service Level Agreements.

Peace Corps VDS Redesign SECTION C:PERFORMANCE WORK STATEMENT (PWS) Section C - 3-8-10 PC 10 R CP 01 March 8, 2010

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Peace Corps VDS Redesign SECTION C:PERFORMANCE WORK STATEMENT (PWS) Section C - 3-8-10 PC 10 R CP 01 March 8, 2010

Caricato da

Copyright:

Solicitation PC-10-R-CP01 March 8, 2010

Potrebbero piacerti anche