Section C Final - Attachment 13.docx
DOCX document 19 KB Posted
- Attached to
- E-Gov Travel Services 2. 0 (ETS2) Federal contract opportunity
- Solicitation number
- SOL__QMAD-JM-100001-N
- Issued by
- GSA Federal Acquisition Service
About this file
Section C - Statement of Work Attachment 13
View the file
Other files for this federal contract opportunity
Show all 50
E-Gov Travel Services 2. 0 (ETS2) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
GSA SOLICITATION QMAD-JM-100001-N
August 23, 2010
GSA SOLICITATION QMAD-JM-100001-N
Attachment 13 – FEMA Surge Blanket Travel August 23, 2010
Attachment 13 Federal Emergency Management Administration (FEMA) Surge Blanket Travel (Separately Priced Mandatory Requirement) The Federal Emergency Management Administration (FEMA) has a unique requirement for “Surge Travel.” Surge Blanket Travel (SBT) requires an extremely large number of employees to be granted authority to travel under one Travel Authorization. SBT is Domestic, requires interaction of five user roles and utilizes a unique routing and approval workflow which cannot interfere with or degrade organizational routing and approval workflow already established for an employee involved in SBT. Requirements, all of which must be offered, are provided below.
SURGE BLANKET TRAVEL REQUIREMENTS
The ETS2 shall:
1) Have the ability to create SBT functionality that:
a. Creates a SBT authorization that:
i. Maintains deployment dates, locations and funding;
ii. Allows unlimited travelers under the same authorization;
iii. Allows unlimited number of trips;
iv. Allows unlimited number of changes, amendments, additions and deletions until the SBT authorization is closed;
v. Allows travel to take place over fiscal years with no degradation of information or status;
vi. Supports unlimited vouchers integrated to the financial business system; and
vii. Supports a robust audit capability, further described below.
b. Supports the following Roles:
i. SBT Manager(s) who is (are) able to:
1. Create SBT authorizations which include:
a. Allowable travel dates
b. Total funding listed by cost center
c. Allowable travel States and cities
d. Allowable travel purpose
e. Allowable “per-trip” authorization
f. Allowable “per-trip” number of days, and
g. Event number, description and area(s).
2. Designate Alternate Preparers, additional Managers and Supervisor(s). Note: This function is not auditable.
3. Add or remove Travelers;
4. Modify SBT authorizations;
5. Indicate when SBT authorization is complete;
6. Close SBT authorization; and
7. Audit SBT(s).
ii. SBT Alternate Preparer(s) who is (are) able to:
1. concurrently add and remove travelers to the SBT authorization;
2. Create and modify a travel plan for each traveler associated with the SBT authorization; and
3. Create and modify unlimited vouchers.
iii. Travelers who are able to:
1. Create and modify a travel plan associated with SBT authorization
2. Create and modify unlimited vouchers
3. Utilize a unique routing and approval workflow separate from their organizational routing and approval workflow
iv. SBT Supervisors who are able to:
1. Utilize a unique routing and approval workflow for SBT
2. Be the only static approver needed to approve the voucher (s) of any associated traveler;
v. System Administrator(s) who are able to:
1. Enable business rule to disable the SBT functionality and
2. Audit SBT(s)
c. Contains the following travel functionality to:
i. Associate Supervisors (static voucher approvers) to the SBT approval and routing chain;
ii. Maintain without degradation or corruption of existing Traveler routing and approvals, a separate routing and approval chain;
iii. Transmit approved voucher information to the agency financial system;
iv. Transmit funding information to the agency financial system;
v. “Auto-approve” the Travel Plan created by the traveler / alternate preparer;
vi. Prevent authorization “closing” if there are approved travel plans without an approved voucher; and
vii. On the first day of a new fiscal year, complete the previous FY authorization and create a new SBT authorization pre-populated with the previous year’s data except funding.
d. Contain the following audit functionality to:
i. Manage the following changes to the SBT authorization
1. Date
2. Time
3. Type
4. Description
5. Change originator, and
6. Change approver
ii. Provide a record/display/of changes to Managers and System Administrators
File details come from the government source that posted it. Updated .