Section E Final.docx
DOCX document 115 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 E - Solicitation Provisions
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
| Section E – Solicitation Provisions |
| August 23, 2010 |
SECTION E – SOLICITATION PROVISIONS
E.1. 52.212-1 Instructions to Offerors—Commercial Items (June 2008)
(a) North American Industry Classification System (NAICS) code and small business size standard. The NAICS code and small business size standard for this acquisition appear in Block 10 of the solicitation cover sheet (SF 1449). However, the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees.
(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation. Offers may be submitted on the SF 1449, letterhead stationery, or as otherwise specified in the solicitation. As a minimum, offers must show—
| (1) | The solicitation number; |
| (2) | The time specified in the solicitation for receipt of offers; |
| (3) | The name, address, and telephone number of the offeror; |
| (4) | A technical description of the items being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary; |
| (5) | Terms of any express warranty; |
| (6) | Price and any discount terms; |
| (7) | “Remit to” address, if different than mailing address; |
| (8) | A completed copy of the representations and certifications at FAR 52.212-3 (see FAR 52.212-3(b) for those representations and certifications that the offeror shall complete electronically); |
| (9) | Acknowledgment of Solicitation Amendments; |
| (10) | Past performance information, when included as an evaluation factor, to include recent and relevant contracts for the same or similar items and other references (including contract numbers, points of contact with telephone numbers and other relevant information); and |
| (11) | If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration. |
(c) Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm for 360 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.
(d) Product samples. When required by the solicitation, product samples shall be submitted at or prior to the time specified for receipt of offers. Unless otherwise specified in this solicitation, these samples shall be submitted at no expense to the Government, and returned at the sender’s request and expense, unless they are destroyed during preaward testing.
(e) Multiple offers. Offerors are encouraged to submit multiple offers presenting alternative terms and conditions or commercial items for satisfying the requirements of this solicitation. Each offer submitted will be evaluated separately.
(f) Late submissions, modifications, revisions, and withdrawals of offers.
(1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. If no time is specified in the solicitation, the time for receipt is 2:00 p.m., local time, for the designated Government office on the date that offers or revisions are due.
(2)(i) Any offer, modification, revision, or withdrawal of an offer received at the Government office designated in the solicitation after the exact time specified for receipt of offers is “late” and will not be considered unless it is received before award is made, the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and—
(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or
(B) There is acceptable evidence to establish that it was received at the Government installation designated for receipt of offers and was under the Government’s control prior to the time set for receipt of offers; or
(C) If this solicitation is a request for proposals, it was the only proposal received.
(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.
(3) Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the offer wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.
(4) If an emergency or unanticipated event interrupts normal Government processes so that offers cannot be received at the Government office designated for receipt of offers by the exact time specified in the solicitation, and urgent Government requirements preclude amendment of the solicitation or other notice of an extension of the closing date, the time specified for receipt of offers will be deemed to be extended to the same time of day specified in the solicitation on the first work day on which normal Government processes resume.
(5) Offers may be withdrawn by written notice received at any time before the exact time set for receipt of offers. Oral offers in response to oral solicitations may be withdrawn orally. If the solicitation authorizes facsimile offers, offers may be withdrawn via facsimile received at any time before the exact time set for receipt of offers, subject to the conditions specified in the solicitation concerning facsimile offers. An offer may be withdrawn in person by an offeror or its authorized representative if, before the exact time set for receipt of offers, the identity of the person requesting withdrawal is established and the person signs a receipt for the offer.
(g) Contract award (not applicable to Invitation for Bids). The Government intends to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror’s initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received.
(h) Multiple awards. The Government may accept any item or group of items of an offer, unless the offeror qualifies the offer by specific limitations. Unless otherwise provided in the Schedule, offers may not be submitted for quantities less than those specified. The Government reserves the right to make an award on any item for a quantity less than the quantity offered, at the unit prices offered, unless the offeror specifies otherwise in the offer.
(i) Availability of requirements documents cited in the solicitation.
(1)(i) The GSA Index of Federal Specifications, Standards and Commercial Item Descriptions, FPMR Part 101-29, and copies of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained for a fee by submitting a request to— GSA Federal Supply Service Specifications Section Suite 8100 470 East L’Enfant Plaza, SW Washington, DC 20407 Telephone (202) 619-8925 Facsimile (202) 619-8978.
(ii) If the General Services Administration, Department of Agriculture, or Department of Veterans Affairs issued this solicitation, a single copy of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained free of charge by submitting a request to the addressee in paragraph (i)(1)(i) of this provision. Additional copies will be issued for a fee.
(2) Most unclassified Defense specifications and standards may be downloaded from the following ASSIST websites:
(i) ASSIST (http://assist.daps.dla.mil).
(ii) Quick Search (http://assist.daps.dla.mil/quicksearch).
(iii) ASSISTdocs.com (http://assistdocs.com).
(3) Documents not available from ASSIST may be ordered from the Department of Defense Single Stock Point (DoDSSP) by—
(i) Using the ASSIST Shopping Wizard (http://assist.daps.dla.mil/wizard);
(ii) Phoning the DoDSSP Customer Service Desk (215) 697-2179, Mon-Fri, 0730 to 1600 EST; or
(iii) Ordering from DoDSSP, Building 4, Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5094, Telephone (215) 697-2667/2179, Facsimile (215) 697-1462.
(4) Nongovernment (voluntary) standards must be obtained from the organization responsible for their preparation, publication, or maintenance.
(j) Data Universal Numbering System (DUNS) Number. (Applies to all offers exceeding $3,000, and offers of $3,000 or less if the solicitation requires the Contractor to be registered in the Central Contractor Registration (CCR) database.) The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation “DUNS” or “DUNS+4” followed by the DUNS or DUNS+4 number that identifies the offeror’s name and address. The DUNS+4 is the DUNS number plus a 4-character suffix that may be assigned at the discretion of the offeror to establish additional CCR records for identifying alternative Electronic Funds Transfer (EFT) accounts (see FAR Subpart 32.11) for the same concern. If the offeror does not have a DUNS number, it should contact Dun and Bradstreet directly to obtain one. An offeror within the United States may contact Dun and Bradstreet by calling 1-866-705-5711 or via the internet at http://fedgov.dnb.com/webform. An offeror located outside the United States must contact the local Dun and Bradstreet office for a DUNS number. The offeror should indicate that it is an offeror for a Government contract when contacting the local Dun and Bradstreet office.
(k) Central Contractor Registration. Unless exempted by an addendum to this solicitation, by submission of an offer, the offeror acknowledges the requirement that a prospective awardee shall be registered in the CCR database prior to award, during performance and through final payment of any contract resulting from this solicitation. If the Offeror does not become registered in the CCR database in the time prescribed by the Contracting Officer, the Contracting Officer will proceed to award to the next otherwise successful registered Offeror. Offerors may obtain information on registration and annual confirmation requirements via the internet at http://www.ccr.gov or by calling 1-888-227-2423 or 269-961-5757.
(l) Debriefing. If a post-award debriefing is given to requesting offerors, the Government shall disclose the following information, if applicable:
(1) The agency’s evaluation of the significant weak or deficient factors in the debriefed offeror’s offer.
(2) The overall evaluated cost or price and technical rating of the successful and the debriefed offeror and past performance information on the debriefed offeror.
(3) The overall ranking of all offerors, when any ranking was developed by the agency during source selection.
(4) A summary of the rationale for award;
(5) For acquisitions of commercial items, the make and model of the item to be delivered by the successful offeror.
(6) Reasonable responses to relevant questions posed by the debriefed offeror as to whether source-selection procedures set forth in the solicitation, applicable regulations, and other applicable authorities were followed by the agency.
E.2 PRE-PROPOSAL CONFERENCE
After formal release of the RFP, the Government intends to hold a Pre-Proposal Conference with the date (approximately 14 work days after RFP issuance). This Conference will allow actual or prospective Offerors to gain a better understanding of the objectives of the acquisition. The Contracting Officer (CO) will make the necessary arrangements and conduct the Pre-Proposal Conference. The agenda will include a general presentation of ETS2 requirements and timetable for award. Written questions must be received 5 work days before the Pre-Proposal Conference using the template provided. However, additional questions may be asked during the conference and Government personnel will be available to answer them. Questions answered orally during the conference are also distributed in writing to all prospective Offerors. Additional questions after the Pre-Proposal Conference shall be submitted no later than 5 days after the Pre-Proposal Conference using the template provided, or they may not be addressed by the Government.
E.3 POINT OF CONTACT
The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent via email to the CO as follows: ets2@gsa.gov, subject “RFP QMAD-JM-100001-N.” The Contracting Officer’s address is as follows:
| General Services Administration |
| Travel Division (QMAD) |
| Attention: Contracting Officer |
| 2200 Crystal Drive, Room 300 |
| Arlington, Virginia 22202 |
E.4 NONGOVERNMENT CONSULTANTS/ADVISORS
The Government may employ individual technical consultants/advisors from the below listed firms under contract with GSA to read and advise on portions of the written proposals (technical or price), as well as any Demonstration, and/or IV&V testing.
CACI International, Inc.
Dell Perot Systems, Inc.
Deloitte, LLC SiloSmashers, Inc.
Global Cynex Government Contract Solutions, Inc.
John Caldwell and Associates Kapsales Consulting Group mLinqs Suntiva Executive Consulting Travel Technologists Travel Technology Consulting
These technical consultants/advisors and their firms will sign or have already signed non-disclosure agreements (NDAs) for the protection of source selection information and proprietary data. In addition, they are subject to Organizational Conflict of Interest (OCI) concerns and are restricted from being a Contractor, subcontractor, or teaming partner in this solicitation.
These representatives shall not, under any circumstances, be used as voting evaluators. However, the Government may consider the advice provided in its evaluation process.
Any member of the GSA Office of Travel and Transportation Services and its customer agencies may serve as an advisor to the source selection process with respect to the program strategy, vision, requirements and pricing.
E.5 PROCUREMENT STRATEGY
This is a Full and Open competitive procurement in which the Government intends to award one or two firm fixed price, indefinite delivery, indefinite quantity (IDIQ) contracts. The methodology for awards is discussed in Section F.
Certain contract line items (CLINs) as set forth in Section B – Supplies or Services and Prices/Costs will have prices that are firm at the master contract level and may not be negotiated lower at the task order level. Other CLINs will have prices at the master contract that are negotiable by customer agencies through their task orders, but may not exceed the ‘Not to Exceed (NTE)’ rate at the master contract.
E.5.1 Final Proposal Revisions If discussions are held, the CO will request that the Offeror submit its Final Proposal Revision (FPR). The Offeror is advised that any changes to the proposal in the FPR must be fully addressed and/or explained and reflected in the final proposed price. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The CO will establish a common format, due date, and time for submission of the FPR.
E.6 INSTRUCTIONS TO OFFERORS
The Offeror is advised that all submissions and related materials become the property of the Government and will not be returned.
E.6.1 General:
| (a) | The Offeror is advised that its offer, if accepted by the Government, will form a binding contract. Therefore, care must be taken to properly address the requirements set forth in the RFP. These instructions set forth requirements for preparation and submission of proposals and to establish format and specific content of each offer. This is to assure completeness and suitability for both evaluation purposes and the cohesiveness of the resulting contract. Be sure that the proposal explains how your firm will fully satisfy all of the performance requirements of the intended contract. Submit a complete proposal. Proposals that are not complete may be determined unresponsive and rejected. |
| (b) | To aid in evaluation of proposals, each proposal shall be clearly and concisely presented as instructed (telephonic and telegraphic offers will not be accepted). Include all information required by this RFP, with pages numbered and logically assembled. Each proposal shall have a cover sheet that identifies the volume number, copy number, name of the contractor, date of submission, RFP number, and solicitation title. |
· The original must be submitted unbound, 3 hole punched, and rubber banded.
· Two additional hardcopy proposals shall be separately bound in a three-ring loose-leaf binder which permits the volume to lie flat when opened. Do not use staples.
· Complete electronic volumes shall be submitted in Microsoft Office format, readable by 2003 Microsoft (MS) Word, MS Excel, MS PowerPoint, and/or Adobe Acrobat (.pdf) unless otherwise specified. Electronic copies will not be password protected. Regarding the use of MS Excel, all formulas and hidden columns shall be viewable by evaluators. All electronic copies shall be on non-re-writable digital versatile disks (DVD-R) in a protective sleeve. Each volume shall be submitted on two separate DVD-Rs. The DVD-Rs and protective sleeves shall be clearly marked as to volume number, Offeror’s name, solicitation title, and solicitation number. Offerors shall ensure electronic copies on DVD-R are virus free. Electronic versions of the proposal shall be an exact duplicate of the original hardcopy proposal. Page format restrictions and limitations apply. Sound or video (e.g., MPEG) files shall not be embedded into the proposal files. If discrepancies are identified between the electronic proposal and the original signed unbound proposal, the original signed unbound proposal shall prevail.
E.6.2 Proposal Format:
| (a) | Proprietary Data: Each and every page of both the technical and price proposals must be reviewed for and marked as to proprietary data content, by the Offeror. A single blanket statement at the front of the proposal is not adequate. Failure to mark every page that contains proprietary information may subject your technical proposal to public release through Freedom of Information Act (FOIA) requests. Offerors are hereby placed on notice that their assertion that information is proprietary does not conclusively make it so, and that the 'default' in FOIA reviews is to release information, rather than withhold it. In any case, Offerors are hereby notified that the release or withholding of any information is governed by the FOIA and implementing regulations. |
| (b) | Proposal Arrangement: Each proposal shall consist of six physically separate files individually titled and numbered as stated below. The required number of each proposal volume is also shown below: |
| Volume Title | |
| Maximum Page Limit | |
| Original Signed Unbound | |
| # of HARDCOPY Volumes | |
| DVD-R |
| VOLUME 1 - ADMINISTRATIVE |
| See Below |
| 1 |
| 2 |
| 2 |
| Tab 1: Cover Letter, SF1449 |
| 2 |
| Tab 2: Complete solicitation and amendments |
| As issued |
| Tab 3: Financial Data |
| None |
| Tab 4: ORCA and CCR |
| None |
| Tab 5: Point of Contact List |
| 3 |
| Tab 6: Master Table of Contents |
| None |
| Tab 7: Exceptions (any exceptions taken to the objectives must be clearly identified and explained in this tab) |
| None |
| VOLUME 2 - TECHNICAL |
| See Below |
| 1 |
| 2 |
| 2 |
| Tab 1: Table of Contents and Glossary |
| None |
| Tab 2: Key Personnel |
| 5 pages for Key Personnel Plan and |
2 pages per resume as needed
Tab 3: Performance Work Statement (PWS) Mandatory Requirements Matrix Objectives Matrix None None
| Tab 4: Project Management Plan |
| 125 |
| Tab 5: Demonstration |
| 10 as instructed in E.6.3.2 |
| VOLUME 3 – SOCIO-ECONOMIC PLAN |
| See below |
| 1 |
| 2 |
| 2 |
| Tab 1: Essential Role of Small Business |
| 10 |
| Tab 2: Small Business Subcontracting Plan |
| None |
| VOLUME 4 - PAST PERFORMANCE |
| See Below |
| 1 |
| 2 |
| 2 |
| Tab 1: Past Performance Summary |
| 7 |
| Tab 2: Past Performance Information (PPIs) |
| None (see instructions in Section E.6.3.4, Tab 2) |
| Tab 3: Client Authorization Letter |
| 1 page each |
| VOLUME 5 - PRICE |
| See Below |
| 1 |
| 2 |
| 2 |
| Tab 1: Price Breakdown Structure (PBS) |
| None |
| Tab 2: Price Proposal for Single Award |
| None |
| Tab 3: Price Proposal for Multiple Award |
| None |
| VOLUME 6 – INDEPENDENT VERIFICATION AND VALIDATION (IV&V) |
| - |
| - |
| - |
| - |
| Tab 1: Test Scenarios |
| None |
| Tab 2: Test Results |
| None |
| (c) | Cross-referencing volumes is not allowed unless otherwise stated herein. Each volume shall be written on a stand-alone basis without cross-referencing to other volumes of the proposal. Price information shall only be included in the price volume. |
| (d) | The proposal shall be submitted on standard 8-1/2” x 11” paper, double-sided, single-spaced with fold outs as required, with each fold of the fold out page counted as a single page and no single fold out is to exceed 11” x 17”. The type shall not exceed 6 lines/spaces to the vertical inch with a minimum font size 11 or larger. |
| (e) | The proposal shall contain all pertinent information in sufficient detail to permit evaluation. Statements paraphrasing the Statement of Objectives are considered inadequate, as are phrases such as “standard procedures will be employed,” “well known techniques will be used,” or “the Offeror concurs.” The Technical volume is intended to present with clarity and completeness the discussion of how the SOW will be accomplished. Through the Performance Work Statement, the Offeror must detail what will be done. Through the Project Management Plan, the Offeror must detail how it will be done and managed. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address the extent to which the Offeror is capable of performing. The matrices will be used to comprehensively trace mandatory requirements and objectives to the technical volume, and is critical to the overall evaluation. Offerors shall assume that the Government has no prior knowledge of their experience and will base its evaluation on the information presented in the Offeror’s proposal. |
No appendices, attachments, etc., will be permitted to the proposal unless otherwise directed. The Offeror shall follow the general rule that quality of information is significantly more important than quantity. In this respect, the maximum number of pages allowed for each volume of the proposal is to be strictly observed: pages exceeding the page limitation will be removed from the proposal prior to evaluation. Furthermore, the Offeror is encouraged to use the least expensive form of reproduction that will provide legible copies. Unnecessarily elaborate brochures or other presentations beyond that sufficient to present a complete and effective proposal are not desired. Elaborate art work, expensive paper and bindings, or expensive visual and other presentation aids are neither necessary nor wanted.
E.6.3 Content:
E.6.3.1 Volume 1, Administrative:
Tab 1, Cover Letter and SF 1449, Volume 1 shall contain the following:
· Cover letter providing an executive summary of the offer and a statement that the Contractor assents to the terms and conditions of the solicitation or takes exception to certain terms and conditions. Any exceptions to the solicitation terms and conditions must be placed in Tab 7.
· Completed and signed Standard Form (SF) 1449 by the company’s signatory authority.
Tab 2, Complete Solicitation and Amendments, Volume 1 shall contain the following:
· Solicitation in its entirety (with fill-ins and check boxes completed).
· Completed and signed amendments to the solicitation in their entirety (with fill-ins and check boxes completed if provided in the Amendments).
Tab 3, Financial Data, Volume 1 shall contain the following:
· Financial data consisting of audited annual reports or audited consolidated financial statements for the past 3 years.
Tab 4, ORCA and CCR, Volume 1 shall contain the following:
· Copy of current Online Representations and Certifications Application (ORCA) (https://orca.bpn.gov/).
· Copy of Central Contractor Registration (www.bpn.gov/ccr).
Tab 5, Point of Contact List, Volume 1 shall contain the following for each Contractor, teaming partner, and subcontractor:
· Company name and division (if applicable)
· Company URL
· Role in ETS2
· Mailing address
· DUNS number
· TIN number
· Congressional district
· Primary and alternate points of contact to include name, position title, address, phone, email address, and signatory authority levels Tab 6, Master Table of Contents, Volume 1 shall contain the following:
· Table of contents for the entire proposal (with hyperlinks in the electronic version if possible).
Tab 7, Exceptions, Volume 1 shall contain the following:
Exceptions taken to the objectives. Any exceptions taken to the mandatory requirements will not be accepted (Section C); however, the Government may consider exceptions taken to Section C objectives. If exceptions are taken, they must be cross-walked back to the proposal. Exceptions shall be provided in the format provided in Attachment E-4, Exceptions Taken to the Objectives – Technical Format.
E.6.3.2 Volume 2, Technical:
Tab 1, Table of Contents and Glossary, Volume 2 shall contain the following:
· Table of Contents (with hyperlinks in the electronic version) for Volume 2 and glossary defining terms of Volume 2.
Tab 2, Key Personnel/Resumes, Volume 2 shall contain a Key Personnel Plan (not to exceed 5 pages in length excluding resumes) that addresses:
· Key Personnel positions, roles, responsibilities, authorities, and percentage of time allocated to the contract;
· Organizational structure and relationship between Contractor, team members, and subcontractors; and
· Recruitment and retention.
Key personnel positions to be proposed shall include, but are not limited to:
· Program Manager
· Service Technical Lead
· Information System Security Officer (ISSO)
· Commercial Travel Expert
· Federal Travel Policy Expert
· Training Manager
· Usability Assurance Manager
· Agency Account Manager(s)
· Contract Administrator The Offeror shall submit resumes (not to exceed two (2) pages in length per person) for all key personnel using the template provided in Attachment E-3 - Resume Format. If an Offeror proposes an individual as key personnel who is not actually employed by the Offeror, team members, or subcontractors, the Offeror shall include a signed contingent employment agreement executed by that individual stating their intent to accept employment upon contract award. Failure to include a contingent employment agreement will result in the individual's resume not being included as part of the Offeror's team for proposal evaluation purposes.
Key personnel are considered critical to program success or failure. They are to be subject matter experts in the appropriate areas and contain all necessary education, experience and skill sets needed to ensure success of ETS2.
· PAGE LIMIT – Resumes not-to-exceed 2 PAGES in length per person; Key Personnel Plan not-to-exceed 5 PAGES.
Tab 3, Performance Work Statement (PWS), Volume 2 shall: Provide the full and complete performance work statement (PWS) for ETS2. The PWS shall address the “Whats” of contract performance. It shall be fully integrated to the Project Management Plan (Tab 4) which will address the “Hows” of contract performance. The PWS shall form the basis for the ultimate contract award.
· The PWS must give the Government a high degree of confidence that the Offeror has a robust understanding of ETS2 goals and requirements. It must demonstrate a comprehensive work statement, with clear identification and demonstrated understanding to accomplish the requirements and objectives, key milestone dates to meet, etc. In preparing the PWS, each of the following broad goals of ETS2 shall be addressed including but not limited to:
· usability;
· data and interoperability;
· security management; and
· quality control.
· The Offeror shall also prepare two matrix documents demonstrating alignment between the RFP and the PWS. The matrices are not included in the page limitation. Paragraph numbering in the Offeror’s PWS shall correlate with the paragraph numbering of the SOW.
· Offerors shall provide a complete Mandatory Requirements Matrix. Offerors are cautioned that not referencing and cross referencing ALL Mandatory Requirements may result in a determination the Offeror is non-responsive or technically unacceptable.
· Offerors shall provide a complete Objectives Matrix if any objectives are offered, including the projected delivery date. Offerors are not required to offer objectives, however, not referencing and cross referencing ALL Objectives that have been offered may result in an inability to give full consideration of the objectives offered.
· Key requirements which must be reflected in the PWS include but are not limited to:
· Adherence to the FTR;
· Inclusion of agency policy filters;
· Architecture approach and refreshment/modernization;
· Comprehensive Software Development Life Cycle Methodology, Release Management, Software Quality Management, and Configuration Management;
· Clear service boundaries and interoperability points;
· Completion of the End-to-End travel process and creation of travel and routing documents;
· Accounting functionality within travel documents;
· Document amendment requirements;
· Creating, routing, and amending travel payment documents;
· Training approach;
· Usability Assurance approach;
· Section 508 accessibility compliance approach:
· Agency configurability requirements;
· Technology refresh and service release management requirements;
· Security management;
· Quality control;
· Performance metrics; and
· Performance measurement
· PAGE LIMIT – 75 PAGES
Tab 4, Project Management Plan, Volume 2:
· The Offeror shall propose a comprehensive Project Management Plan in Tab 4. The Project Management Plan must give the Government a high degree of confidence that the Offeror has a robust plan of accomplishment. It must demonstrate a comprehensive plan of accomplishment, with clear actionable strategies and timeframes for accomplishing the requirements and objectives. For example, if the PWS establishes a milestone date, the Project Management will address how the date will be met. In preparing the Project Management Plan, each of the broad goals of ETS2 shall be addressed including but not limited to those indicated below. The Project Management Plan must be fully integrated with the PWS. The Project Management Plan will address the “Hows” of contract performance. The Offeror is to demonstrate how it will perform all of the Government’s requirements, offered objectives, overcome or mitigate constraints, and meet or exceed contract performance requirements.
· Key areas to include in the Project Management Plan include but are not limited to all of the following:
· All key requirements included in the PWS.
· Management of the ETS2 Service -- addressing overall management roles and responsibilities, Contractor organization, subcontractors and teaming arrangements, task order management, Contractor/government communication (including a partnership with the GSA ETS2 PMO) at all phases of implementation and on-going account management, rules of operation, and streamlined billing practices.
· Government-wide Travel Management – ETS2 performance elements that achieve the vision for and further propagates adoption of government-wide travel management objectives. The Offeror must demonstrate how it will technically refresh and maintain the service with commercially available travel service and architecture advancements as well as Government policy updates over the life of the contract as part of routine operations and maintenance.
· Usability - The Offeror must demonstrate how it will achieve the usability requirements outlined in Section C, including usability assurance for the initially deployed ETS2 as well as usability assurance and continuous improvement going forward. The Offeror shall describe how it will ensure the usability of ETS2, respond to customer issues identified, and strive for usability improvements over the life of the contract, making use of its User-Centered Design/Usability Assurance Plan (see D-40) and its Semi Annual Usability Action Report (see D-40). The Offeror shall describe how they will measure customer satisfaction for usability and how usability improvements will be managed over the life of the contract.
· Implementation / Transition - Provide an implementation and transition plan, which addresses both a single award scenario and a dual award scenario, detailing differences, if any.
· Demonstrate how the Offeror intends to implement and transition ETS2 considering various agency “roll-out” alternatives using agency profile data provided with Attachment 1- Agency Profiles of the Statement of Objectives.
· Describe and detail risk mitigation measures that specifically addresses performance issues, performance failures, change of ownership, and bankruptcy.
· Describe the Offeror’s ability to increase resources and support the capacity necessary to deploy all Federal Agencies prior to the expiration of the current ETS1 contracts and deliver expected end-to-end travel services.
· Describe processes, capabilities, and timeframes necessary for development and testing of financial business interface(s).
· Demonstrate the capability to field trainers, obtain and transfer complex traveler profiles, and develop/arrange customer routing and workflow and accounting requirements necessary for implementation.
· Address corporate reserves for implementation and transition.
· Describe the transition of ETS2 to a new contractor at the end of the period of performance, both at a task order level and at the master contract, with a Transition-Out Plan. Roles and responsibilities must be clearly defined. Fully address exactly what each party must do to ensure a successful transition. At a minimum, the Transition-Out Plan shall address:
1. Project management processes;
2. Points of contact;
3. Status of ongoing technical initiatives;
4. Transition of key personnel while retaining program knowledge;
5. Transition-out schedules and milestones;
6. Actions required of the Government;
7. Method of establishing and maintaining effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings;
8. Transition and delivery of Government Furnished Equipment (GFE)/Government Furnished Information (GFI);
9. Transition and delivery of Government Owned Data and Information as described in the Master Contract. This includes, but is not limited to:
· Traveler and user profiles;
· Centrally billed accounts;
· Organizational structure, approval routing, business rules and other agency configurable functionality;
· Accounting codes;
· Interfaces and documentation;
· Travel transaction data archives and plans for archiving through the end of the period of performance; and
· Embedded TMC service information and points of contact.
10. Transition consultation services; and
11. Risk mitigation measures; and
12. Closeout.
· Standard Data and Interoperability - The Offeror must demonstrate how it will achieve the data and interoperability requirements outlined in C.8, including the extent to which standard data elements will be incorporated into the proposed architecture, with respect to ETS2 integration, data transmission, and customer reporting and specify any modifications to the Standard Data Elements (SDE) provided in Attachment 14 - E-Gov Travel Systems Standard Data Elements of the SOW and associated rationale for the deviation. The Offeror shall explain their approach to: 1) work cooperatively with third-party vendors (at the agency’s request) for integration and data exchange, and meet timeframes for interface development, and changes (including those caused by fiscal year, policy, reporting, security, regulatory changes and other customer agency changing mission related travel needs).
· Security Management Plan - The Offeror shall submit an initial security management plan following the Attachment E-2 – ETS2 Security Management Plan. Key goals of security management are outlined in C.6 Security Capabilities and Characteristics including both the general and specific requirements for the Contractor, team-members and all subcontractors.
· Quality Control Plan - The Offeror shall describe their specific approach for meeting or exceeding the solicitation requirements and objectives. Specifically, the quality control portion of the Project Management Plan shall address management of on-going quality activities for the Contractor, all team members, and all subcontractors. It must comprehensively address all portions of the quality control process and illustrate how superior customer satisfaction shall be achieved. The Offeror shall address how the Quality Control Plan will be combined with the Service Level Agreements and Quality Assurance Surveillance Plan. Special attention should be paid to mature and pervasive processes for ETRS, ATRS, Ticketing and Fulfillment and TMC Integration.
· PAGE LIMIT – 125 PAGES
Tab 5, Demonstration, Volume 2:
After review of the offer, the Government may invite the offeror(s) to present a demonstration of their proposed ETS2 solution. The following procedures shall apply to the demonstration:
· The demonstration must be conducted by proposed key personnel. All key personnel from the prime, team members, and subcontractors must be present.
· The demonstration must be of the offered ETS2 intended web-based production capabilities. Screen shots are not acceptable.
· Offeror will identify whether the demonstration will be based upon an existing service/system in production or prototype.
· The demonstration will be based on Government-developed scenarios provided on the day of demonstration that address, but will not be limited to, the following ETS2 functional capabilities:
| 1) | Travel Planning: | |
| a. | Ability to identify Government contract and preferred suppliers (Air, Lodging, Car) and enforce policy compliance for self-service reservations; and | |
| b. | Ability to create, modify, and cancel reservations. | |
| 2) | Travel Authorization to include at a minimum: | |
| a. | Ability to select specific trip types and purposes; | |
| b. | Ability to add, modify and delete expense types linked to expense categories; | |
| c. | Ability to select at least two lines of accounting and to allocate expenses across those lines. | |
| d. | Ability to accurately compute per diem allowances and trip cost estimates; and | |
| e. | Ability to properly route/approve travel authorization documents. | |
| 3) | Travel Advance: | |
| a. Ability to track and accurately report travel advances; and | ||
| b. Ability to restrict unauthorized users from requesting an Advance when policy disallows. | ||
| 4) | Travel Voucher: | |
| a. | Ability to create a voucher from a previously approved authorization and evaluate the accuracy of pre-populated information in the previously approved authorization, including travel reservation information; | |
| b. | Ability to manually update the voucher information with actual expenses (such as actual lodging and rental car rates, taxes, user-fees and out-of-pocket expenses) and ensure that the ETS2 complies with the FTR and other applicable travel regulations, including appropriate exception handling; | |
| c. | Ability to add and delete expense types linked to expense categories; | |
| d. | Ability to accurately pre-populate travel voucher data, calculate per diem and expense calculations, and the ability to configure split disbursements; | |
| e. | Ability to accurately compute entitlements for trips of 12 hours but less than 24 hours in duration, trips longer than 24 hours in duration, and trips that cross the International Date Line; | |
| f. | Ability to review that the travel Advance is appropriately liquidated against the total trip cost for reimbursable expenses; and | |
| g. | Ability to attach electronic receipts to the travel voucher for approval and auditing purposes. | |
| 5) | Local Travel Voucher: Ability to add and delete expense types to include POV and link to expense categories. | |
| 6) | Blanket Travel: | |
| a. | Ability to create limited and unlimited Blanket Travel Authorizations; | |
| b. | Ability to properly route Blanket Travel Authorizations for approval; and | |
| c. | Ability to create two (2) or more vouchers per Blanket Authorization. | |
| 7) | System Administration: | |
| a. | Ability to manage User and User role changes on an individual, agency/organization, and enterprise-wide basis; | |
| b. | Ability to modify organizational sub-unit characteristics without impacting other units in hierarchy; | |
| c. | Ability to handle changes for business rules, approval routing, and permission levels on an agency/organization and enterprise-wide basis; and | |
| d. | Ability to add data elements (e.g. travelers, lines of accounting) to the system. |
· The table below identifies the mandatory requirements from Section C that may be evaluated as part of the Demonstration in conjunction with the functional capabilities listed above. Offerors should note that this list is provided for guidance only and other functionality may be requested in the demonstration:
| Section Reference |
| Requirement Numbers |
| C.3.2.1 – Types of Travel |
| 1, 2, 4 |
| C.3.3.1 – Usability |
| 1, 3, 4, 5, 9, 10, 11, 15, 16 |
| C.4.1.1 – Federal Travel Policy Compliance |
| 1, 2 |
| C.4.2.1.1 - User Roles, Use Cases and Account Access |
| 1, 2, 3, 5, 6, 7 |
| C.4.2.2.1 – Travel Process Workflow |
| 1, 2, 3, 4, 6 |
| C.4.2.3.1 – ETS2 Travel Portal |
| 1, 3 |
| C.4.2.4.1 – Traveler Profiles |
| 1, 2, 9 |
| C.4.2.5.1 – Travel Planning and Reservation Services |
| 1, 2, 5 |
| C.4.2.6.1 – Online Travel Planning and Reservation Service |
| 2, 3, 5, 6, 7, 19, 23, 24, 28, 31, 32, 33, 34, 38, 40, 41 |
| C.4.2.13.1 – Travel Authorizations and Vouchers |
| 1, 2, 3, 4, 5, 6, 7, 10, 11, 12, 17, 18 |
| C.4.2.14.1 – Travel Authorizations |
| 1, 2, 3, 4, 5, 6, 7, 8, 12, 13 |
| C.4.2.15.1 – Travel Advances |
| 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 |
| C.4.2.16.1 – Travel Vouchers |
| 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 |
| C.4.2.17.1 – Travel Documentation |
| 1 |
| C.4.2.18.1 – Accounting Capabilities |
| 1, 2, 3, 9 |
| C.4.2.19.1 – Travel Document Routing and Approval |
| 1, 4 |
| C.4.2.21.1 – Local Vouchers |
| 1, 2, 6 |
| C.4.2.25.1 – ETS2 Customer Configuration and Administration |
| 1 |
| C.9.1 – Queries and Reports |
| 1, 2 |
· Following the demonstration, a short break will be taken. When the demonstration resumes, the Contracting Officer will open a question and answer session, where the Government may ask a full range of questions to understand the Contractor’s ETS2 and approach.
· The demonstration will take place at a Government designated facility with standard AC power outlets and T1 line or equivalent (1.544 Mbps) connectivity. The Government will provide a computer for the Demonstration with Internet access, which will be projected for evaluation purposes. The Contracting Officer is at liberty to consult with the Offeror, any Government evaluator, and any technical consultants/advisors. The Government may record the Demonstration via both video/digital and audio means and/or have transcription services provided.
· If a technical problem encountered is Government related, Offerors will be provided adequate make-up time (within stated limitations) to complete the testing. Technical problems encountered that are beyond the control and without fault or negligence of the Offeror may be, but are not required to be, considered by the Government in providing make-up time. Determination of responsibility for problems and their resolution is solely at the Contracting Officer’s discretion and all decisions will be final.
· Screen shots, power point presentations, etc., are not permitted as a substitute for the Demonstration. The Offeror shall be provided a 2-day period to complete the Demonstration. The approximate time (all times Eastern Time) for each day will be allotted as shown below. Question and answer periods have been included and will be moderated by the Contracting Officer, but if Q&As take longer, it will not count towards the allotted Demonstration time as noted in the notional schedule, and accordingly, there may be some slippage in the noted start and end times.
| Task |
| Time Limitation |
| Notional Agenda |
| Offeror Set up |
| 1 Hour |
| 7:00 AM – 8:00 AM |
| Introductions |
| 30 Minutes |
| 8:00 AM – 8:30 AM |
| Demonstration |
| 1 Hour |
| 8:30 AM – 9:00 AM |
| Q&A |
| 15 Minutes |
| 9:00 AM – 9:15 AM |
| Morning Break / Evaluator Documentation |
| 30 Minutes |
| 9:15 – 9:45 AM |
| Demonstration |
| 1.25 Hours |
| 9:45 AM – 11:00 AM |
| Q&A |
| 15 Minutes |
| 11:00 AM – 11:15 AM |
| Evaluator Documentation |
| 15 Minutes |
| 11:15 AM – 11:30 AM |
| Lunch |
| 1.25 Hours |
| 11:30 AM – 12:45 PM |
| Demonstration |
| 1 Hour |
| 12:45 PM – 1:45 PM |
| Q&A |
| 15 Minutes |
| 1:45 PM – 2:00 PM |
| Afternoon Break / Evaluator Documentation Period |
| 30 Minutes |
| 2:00 PM – 2:30 PM |
| Demonstration |
| 1.5 Hours |
| 2:30 PM – 4:00 PM |
| Q&A |
| 15 Minutes |
| 4:00 PM – 4:15 PM |
| Wrap Up |
| 15 Minutes |
| 4:15 PM – 4:30 PM |
| Evaluator Documentation |
| 30 Minutes |
| 4:30 PM – 5:00 PM |
· The Offeror may take up to ten (10) pages to address the key points which will be conveyed in the Demonstration. The supplemental demonstration handout that addresses key points shall be delivered via email 2 full work days prior to the offeror’s scheduled demonstration to the Contracting Officer at ETS2@gsa.gov. Changes to the handout are not permitted.
· PAGE LIMIT – SUPPLEMENTAL DEMONSTRATION HANDOUT - 10 PAGES TO COVER BOTH DAYS OF DEMONSTRATION.
E.6.3.3 Volume 3, Socio-Economic Plan:
Tab 1, Essential Role of Small Business, Volume 3 shall contain the following:
· Address how the resulting contract will recognize the essential role that small businesses play in the economy, and how the Offeror will ensure continuous opportunity for small businesses. This requirement should not be a restatement of the small business subcontracting plan. Rather, it should focus on recognition, delivery, and integration of small business into the solution the Offeror is proposing.
· PAGE LIMIT – 10 PAGES
Tab 2, Small Business Subcontracting Plan, Volume 3 shall contain the following:
The Offeror shall submit a Subcontracting Plan in accordance with FAR 52.219-9 (Attachment D-2). The minimum subcontracting goal for small business shall be 23% of total subcontracted dollars. In addition to the requirements outlined in FAR 52.219-9, the Subcontracting Plan shall address:
· The Offeror’s process for reporting subcontracted dollars and percentages at all tiers of subcontracting in order to identify the dollar and percentages of effort contracted with small businesses.
· The Offeror’s process for ensuring the appropriate North American Industrial Classification System (NAICS) codes and size standards shall be applied at all tiers of subcontracting.
· Methodology used to ensure that the flow-down requirements of the Electronic Subcontracting Reporting System (eSRS) are met.
· PAGE LIMIT – None.
E.6.3.4 Volume 4, Past Performance:
Past performance provides the Government with the information necessary to make an affirmative determination of responsibility. This volume will also give the Government significant insight into the Contractor’s past performance and will aid in assessing performance risk. It includes three tabs.
Tab 1, Past Performance Summary, Volume 4 shall contain the following:
· The Offeror, for itself and each of its subcontractor(s) and teaming partners, shall provide a summary of their past performance including: travel management experience, technical experience, program and schedule management, financial system integration, web-based reservation systems, fulfillment, and responsiveness to customers. The summaries of three relevant projects performed in the last 3 years shall include detailed descriptions of work performed, by whom, their roles and responsibilities, and results achieved.
· Narrative that addresses how the work performed is similar in size, scope, and complexity to that described herein. Identify client spend, number of online versus offline transactions, adoption rate, etc.
· PAGE LIMIT – 7 Pages.
Tab 2, Past Performance Information (PPIs), Volume 4 shall contain the following:
· A list of the references that the Offeror sent the PPI to. Include the point of contacts (POCs), telephone and email address. Ensure identified POCs for each referenced contract include two (2) of the following:
· Contracting Officer/Contract Administrator with direct oversight of contractor performance
· Contracting Officer’s Representative/Contracting Officer’s Technical Representative/Quality Assurance Evaluator
· Program/Project Manger or equivalent The Contractor shall provide the past performance information found in Attachment E1 - Past Performance Questionnaire directly to at least 10 customers for whom it has done work of a similar size, scope, and complexity as that contemplated by ETS2. Each subcontractor or teaming partner should separately send the PPI directly to at least 5 customers for whom it has done work of a similar size, scope, and complexity as that of ETS2. A large Federal department will be considered of similar size, scope, or complexity. A Fortune 100 commercial entity may also be considered of a similar size, scope, or complexity.
The PPI is to be submitted directly from the reference to the GSA Contracting Officer prior to the time and date specified for closing. Signed references in a .pdf format shall be e-mailed to:
ETS2@GSA.gov, subject line: “Solicitation Number QMAD-JM-100001-N -- ETS2 PPI.”
The Government reserves the right to include its own past experience with the Offeror, first tier subcontractor, or teaming partner in addition to provided references as well as other sources of past performance information available to the Government.
After the Contracting Officer receives the PPI directly from the reference, and after closing, he/she will insert this data into Volume 4 Tab 2.
· PAGE LIMIT – None.
Tab 3, Client…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .