Section_L_-_Instructions_to_Offerors_tracked_changes_amendment_0002.pdf

L.1.1 RESPONSIBILITY

This contract shall be awarded only to a responsible prospective Contractor. To be determined responsible, a prospective Contractor must:

Have adequate financial resources to perform the contract, or have the ability to obtain them;

(a) Be able to comply with the required or proposed delivery or performance schedule, taking into consideration all existing commercial and governmental business commitments;

(b) Have a satisfactory performance record;

(c) Have a satisfactory record of integrity and business ethics;

(d) Have the necessary organization, experience, accounting and operational controls, and technical skills, or the ability to obtain them (including, as appropriate, such elements as production control procedures, property control systems, and quality control measures applicable to materials to be produced or services to be performed by the prospective Contractor and Subcontractors;

(e) Have the necessary production, construction, and technical equipment and facilities, or the ability to obtain them; and

(f) Be otherwise qualified and eligible to receive an award under applicable laws and regulations.

Offerors are not required to submit information to comply with these requirements. PBGC will make this determination on its own.

L. 1.2 ADDENDUM to 52.212-1 Instructions to Offerors – Commercial Items (April 2014)

A. Addendum to Paragraph (e) “Multiple offers.” Paragraph (e) “Multiple offers” is deleted in its entirety. Multiple offers will not be accepted.

L.1.3 PROPOSAL SUBMISSION INSTRUCTIONS

Proposals shall be submitted electronically.

L.1.4 ELECTRONIC SUBMISSION

Proposals must also be submitted electronically via the PBGC Secure Proposal site. To submit your proposal, follow the steps below:

1. Encrypt your file(s) (password protect).

2. Go to https://pbgc.leapfile.com.

3. Select "Secure Upload."

4. Enter the email address of the Contract Specialist Dan Swart at swart.dan@pbgc.gov and copy to mcfarlane.patrick@pbgc.gov and click "Start."

5. Enter your contact information.

6. Enter your message and a description of the submission (this information will be included in the notification to the Procurement Officer.) Click the notification checkbox

Formatted: Indent: Left: 0"

Commented [SD1]: Q&A #144

Commented [SD2]: Q&A #143 to ensure you receive notification when the file is downloaded by the Procurement Officer.

7. Select the upload method, Regular or Enhanced. Regular upload works with all browsers and enhanced upload works with Java enabled browsers.

8. Select the file(s) to send (use the Browse buttons).

9. Press the Upload & Send button.

10. Send a separate email to the Procurement Officer with your encryption password.

You will receive an automated system confirmation of a successful upload, and an automated system email when the Procurement Officer downloads your submission.

L.1.5 FACSIMILE SUBMISSION

Proposals submitted via facsimile will not be considered.

L.1.6 LATE PROPOSALS

Complete electronic versions must be received before the time and date specified for receipt. If the proposal is received at the destination after the time and date specified for receipt, the proposal will be considered late and will be dealt with in accordance with the late proposal provision of FAR 52.212-1.

L.1.7 PROPOSAL FORMAT AND COMPOSITION

General Instructions:

The Written Proposal shall use the specific format below. These directions assist in providing a fair and equitable evaluation of all proposals. The Government may determine those proposals not following the directions as unacceptable and may reject such offers from further consideration. The Written Proposals shall use:

• 8.5 by 11-inch paper.

• 12 pitch print or larger, Times New Roman style font.

•o 10 pitch print or larger for graphics, figures and tables.

• 1.25 inch left hand margin, .75 inch right hand margin and 1 inch margins at both the top and bottom for each page.

• All pages single spaced.

• Every page sequentially numbered; and

• Page numbers shall be centered in the bottom margin.

The written proposal shall be accompanied by a cover letter (letter of transmittal) prepared on the company’s letterhead stationery. The cover letter (letter of transmittal) shall acknowledge receipt of all amendments, state validity of offer IAW L.6, and identify all enclosures being transmitted.

and The cover letter shall be used only to transmit the proposal and shall include no other information.

Formatted

Commented [SD3]: Q&A #57

Commented [SD4]: Q&A #39

The Offeror shall submit a Written Proposal addressing the evaluation factors listed in Section M. All offers shall be evaluated preliminarily to ensure compliance with the requirements set forth in this solicitation, which include the following:

• Timely receipt of the offer.

• Determination of contractor and subcontractor responsibility in accordance with FAR 9.104.

• Information presented in the manner required by Section L

The written proposal shall be submitted in three (3) separate volumes:

Each of the volumes must be prepared and submitted in separate electronic files, so the evaluation of each part may be conducted independently.

Volume I – Technical Volume Part A – IDIQ Response Part B – Task Order One Response Part C – Task Order Two Response Part D – Sample Development Task Scenario Response Volume II – Price/Business Volume Part A – IDIQ Business/Price Proposal Part B – Task Order One Price Proposal Part C – Task Order Two Price Proposal Volume III – Small Business Participation

L.1.8 PAGE COUNT LIMITATION:

Below are the page limits associated with each section of the contractor proposal. PBGC will not evaluate or consider any pages that exceed the page limits listed for each item in the table below.

Resumes are limited to 2 pages each are not included in the page limits listed in the below table.

Cover pages, table of contents, list of acronyms, list of figures, glossary of terms, cross reference/compliance matrix, executive summaries, resumes, letters of commitment, Table of Labor Categories, PWSs with QASPs, Quality Control Plans and tabs are not included in the count.

Section Page Limit Cover Letter N/A Volume I – Technical Volume 65 Pages Table of Contents N/A Part A – IDIQ Response 20 Pages LCAT Table N/A Past Performance Rating Articles N/A Part B – Task Order One Response 15 Pages

PWS N/A

Transition Plan N/A

QASP N/A

Commented [SD5]: Q&A #113

Commented [SD6]: Q&A #109, 110, 111, and 112

Commented [SD7]: Q&A #114

Commented [SD8]: Q&A #116

Commented [SD9]: Q&A #107

Commented [SD10]: Q&A #108

Commented [SD11]: Q&A #52

Commented [SD12]: Q&A #113

Commented [SD13]: Q&A #114

Commented [SD14]: Q&A #90

Commented [SD15]: Q&A # 136 Included with the removal of PBGC 52.215-7000

Commented [SD16]: Q&A #117

Commented [SD17]: Q&A #142

Commented [SD18]: Q&A #189

Quality Control Plan N/A Part C – Task Order Two Response 15 Pages

PWS N/A

QASP N/A

Quality Control Plan N/A Part D – Sample Development Task Scenario Response 15 Pages

PWS N/A

QASP N/A

Quality Control Plan N/A Volume II – Business Price Volume N/A Part A – IDIQ Business/Price Proposal N/A Part B – Task Order One Price Proposal N/A Part C – Task Order Two Price Proposal N/A Volume III – Small Business Participation N/A Volume IV – Small Business Subcontracting Plan (other than small businesses only N/A

L.2 - EVALUATION OF TECHNICAL VOLUME

The Offeror shall respond to the IDIQ and each Sample Task Order independently as outlined in the L.1.7 above. For each Technical Volume Part, the Offeror shall fully address the following evaluation factors and subfactors. The offeror shall provide responses which address the evaluation factors and subfactors for the IDIQ, Task Orders and Sample Development Task Scenario Response as listed Below. In order that the technical proposal may be evaluated strictly on the merit of the material submitted, no pricing information is to be included in the technical proposal. No materials shall be incorporated by reference that are not included in the technical proposal. Each proposal section should stand alone.

Commented [SD19]: Q&A #142

Commented [SD20]: Q&A #142

Commented [SD21]: Q&A #142

Commented [SD22]: Q&A #152

Commented [SD23]: Q&A # 136 Included with the removal of PBGC 52.215-7000

L.2.1 - PART A – IDIQ RESPONSE

Factor 1 – Approach and Understanding of Requirements

Offerors must describe their approach to addressing each area as outlined in the IDIQ for FMS Information Technology Systems Support (FMS-ITSS) for PBGC. Offerors must also describe their approach to responding to and managing future Task Orders. An Offeror who simply states they will perform the work and complete the requirement will be considered non-responsive and subsequently will be determined technically non-compliant and be eliminated from further consideration for award. Additionally, simply repeating the language set out in the solicitation will be considered insufficient.

For program and task order management under the IDIQ, the offeror must clearly describe its approach to those program management activities listed in the SOO Section 2.1

Factor 2 – Key Personnel

Provide personnel with expertise in developing, administering, and analyzing proposed IDIQ tasks. Provide a description of the experience, skills, and capabilities of each of the key personnel. Descriptions shall include the quality and depth of experience of proposed personnel in working on similar projects in terms of background, education, work experience, and accomplishments. Descriptions shall demonstrate the knowledge that key personnel have gained through completed and ongoing efforts on similar programs. "Similar programs" is meant to convey similarity in subject matter, dollar value, and complexity as related to work described in the IDIQ task areas.

In order to meet the requirements of the IDIQ, the contractor should assess and propose the Key Personnel deemed appropriate. The contractor is not limited in the number of Key Personnel they can offer, but shall propose at least one IDIQ Program Manager as key personnel.

Factor 3 – Staffing and Management Approach

The offeror will describe its approach to staffing the overall IDIQ and task orders as they are issued. The offeror should not assume that the CLIN structure or task structure is an indication that separate teams should be established. It is anticipated that resources will be shared across areas and tasks. The offeror shall identify the minimum labor categories and associated experience/education levels. Additional labor categories can be included beyond the minimum listed. The staffing plan should include its management approach and, at a minimum, address the following:

1. Overall approach strategy to be used for staffing and task order management across tasks

2. Approach to staffing task orders as they are issued or completed. For example, as new tasks are awarded, how will the offeror quickly bring on new, experienced staff to ensure consistency of delivery. As projects are completed, how will the offeror ensure transition to operations and maintenance activities

3. Describe the offeror’s reach back capability

4. While Task Order #1 and Task Order #2 include the initial transition, operations and release development for three FMS systems, it is anticipated that additional task orders will be issued to provide for operations and maintenance of all systems, multiple releases and potentially concurrent large IT development efforts. The Offeror must describe what a full staffing model would look like should task orders be issued covering operations for all systems with multiple concurrent release and development efforts.

4.5.Communications Plan

The contractor shall also propose labor categories, labor category descriptions and associated credentials required for each labor category and level. At a minimum the offeror shall include the labor categories included with the labor category template included with the solicitation.

Factor 4 – Past Performance

Describe the experience and capability of your organization in conducting relevant work.

“Relevant" is meant to convey similarity in subject matter, dollar value, duration, and complexity. This includes specific experience supporting financial services or financial regulatory clients. Additionally, experience should demonstrate efforts utilizing similar technologies supporting FMS systems.

Provide a summary of at most three (3) similar contracts performed by your organization during the last three years consistent with all task areas detailed in the IDIQ. Past Performance may be provided for significant subcontractors but at least one must be from the prime contractor.

Include a brief description of the project, project title, contract number, period of performance, performance ratings, contract amount, and client identification including Agency or company name, and point-of-contact with e-mail and telephone number. Contact information must be current. For similar IDIQs, the past performance shall include performance ratings across all tasks under the IDIQ as support for the IDIQ performance. This shall be no longer than one page for each reference.

Commented [SD24]: Q&A #5

Commented [SD25]: Q&A #120

L.2.2 PART B – TASK ORDER ONE RESPONSE

Offerors must describe their approach to addressing each objective as outlined in Task Order #1 and address the associated constraints in meeting those objectives.

Offerors must include in their technical approach a staffing plan and performance work statement (PWS) that includes, as defined in Task Order #1, Section 3, the following:

• Tasks required to meet task order objectives and associated performance standards

• Deliverable and performance standards that incorporate minimum deliverable and performance standards as set out in the task order.

• Quality Assurance Surveillance Plan (QASP)

• Quality Control Plan

These must detail and address how they will successfully complete all requirements identified in TO #1 (i.e., who is doing what when and how, and what are the expected results). In addition, offerors shall propose the methodology and the framework for the IT services and associated performance metrics they will be utilizing and measured on under this task order. A successful approach must include how quality deliverables will be produced through effective technical writing.

The approach shall be simple, easy to read, and shall clearly and concisely describe task responsibilities and personnel, relevant communication and coordination, scheduling of all tasks and subtasks, meetings, and deliverables. All staff needed to conduct the work and produce all required products and deliverables must be identified in a project organizational chart. In meeting deliverables, Offerors shall elaborate on how they plan to measure their efforts to ensure the highest quality of performance.

An offeror who simply states they will perform the work and complete the requirement will be considered non-responsive and subsequently will be determined technically non-compliant and be eliminated from further consideration for award. Offerors technical approach must demonstrate a thorough understanding of the context of the work to be performed and must possess the ability to perform all task requirements and have a clear value proposition that attempts to differentiate itself from other potential offerors.

The Contractor shall provide a detailed plan and schedule describing how they will transition all services to be provided from the implementation contractor under this contract. The transition plan shall detail all specific actions that need to be taken and their expected completion dates.

First, the transition plan shall identify all critical steps needed to be completed to transition all the services, second the plan shall identify all the steps for knowledge transfer and staffing approach. The transition plan shall be detail on how the contractor shall perform implementation and elaborate on how they will address transition issues and risks. The plan shall be comprehensive and assure the Government that the work can be transitioned to the new Contractor by the end of the Transition POP.

Commented [SD26]: Q&A #158

Provide personnel with expertise in developing, administering, and analyzing proposed Task Order #1 objectives. Provide a description of the experience, skills, and capabilities of each of the key personnel. Descriptions shall include the quality and depth of experience of proposed personnel in working on similar projects in terms of background, education, work experience, and accomplishments. Descriptions shall demonstrate the knowledge that key personnel have gained through completed and ongoing efforts on similar efforts. "Similar efforts" is meant to convey similarity in subject matter, dollar value, and complexity as related to work described in the task objectives.

In order to meet the requirements of the task order, the contractor should assess and propose the Key Personnel deemed appropriate. The contractor is not limited in the number of Key Personnel they can bid, but shall propose at least the following:

Project Manager/Project Managers: The contractor will identify one or more project managers with overall responsibility for delivery of tasks and deliverables identified in the PWS. The project manager will be the responsible for meeting and exceeding deliverable quality, timeliness and cost measures. He/she will have strong organizational skills, project management skills, and the ability to lead teams to deliver and implement robust IT solutions. It is highly desirable that the identified project managers have the following experience/qualifications:

5+ years demonstrated experience managing highly complex and high-visible IT projects relating to financial support systems across the entire software development lifecycle.

5+ years demonstrated experience supporting financial IT system operations and managing IT software development projects using multiple methodologies

Technical understanding and experience with the technologies identified supporting the FMS systems

Project Management Institute Project Management Professional (PMP) Certification

Demonstrated written and verbal communication skills, including experience in presenting material to senior Government officials.

Technical Lead/Leads: The contractor will identify one or more technical leads who will be responsible for architecting, deploying, and supporting all the FMS footprint. The technical lead(s) will have strong conceptual design skills, knowledge of scripting, and the ability to lead teams to envision, design, and implement robust IT solutions.

Technical lead(s) should have extensive technical leadership and IT systems development experience directly supporting financial systems. It is highly desirable that the technical lead(s) has the following experience 10+ years experience overseeing the design, development, and implementation of software and hardware solutions, systems and products Experience interfacing IT systems with Department of Treasury shared services

Extensive hands on experience with technology supporting the FMS systems with specific emphasis on Oracle/Java technologies including Oracle E-Business Suite.

Experience with the following technologies highly desired:

Oracle E-Business-Suite (EBS) Release 12 (GL Module, Fed Admin, TCA, CRM, AP, PO)

Oracle SOA Suite Oracle BI Publisher and Oracle Forms and Reports Oracle RDBMS and Weblogic server Oracle Rules Engine Java Web services Oracle 11g/12C database administration UNIX shell scripting and cron jobs Java/J2EE JavaScript

PL/SQL

Spring Framework iBatis Oracle ADF

JAX-WS JAXB

.NET

Asynchronous Javascript and XML (AJAX), XHTML, and VB coding principle Bootstrap

Factor 3 – Management Approach

Offeror’s proposal must demonstrate the following:

An effective, efficient, feasible and practical level of understanding of the operating environment in accomplishing the tasks of TO #1, with minimal risk to the Government and an effective concept of operations with their team and the Government.

An effective, organizational structure, which explains handling lines of authority and communication both within the contractor’s team and with stakeholders at PBGC.

An effective, approach to risk management providing a realistic process for managing risk as well as an understanding of the risk areas encountered and approach to quality assurance.

L.2.3 PART C – TASK ORDER TWO RESPONSE

Offerors must describe their approach to addressing each objective as outlined in Task Order #2 and address the associated constraints in meeting those objectives.

Offerors must include in their technical approach a staffing plan and performance work statement (PWS) that includes, as defined in Task Order #2, Section 3, the following:

• Tasks required to meet task order objectives and associated performance standards

• Deliverable and performance standards that incorporate minimum deliverable and performance standards as set out in the task order.

TO #2 (i.e., who is doing what when and how, and what are the expected results). In addition, offerors shall propose the methodology and the framework for the IT services and associated performance metrics they will be utilizing and measured on under this task order. A successful approach must include how quality deliverables will be produced through effective technical writing.

The approach shall be simple, easy to read, and shall clearly and concisely describe task responsibilities and personnel, relevant communication and coordination, scheduling of all tasks and subtasks, meetings, and deliverables. All staff needed to conduct the work and produce all required products and deliverables must be identified in a project organizational chart. In meeting deliverables, Offerors shall elaborate on how they plan to measure their efforts to ensure the highest quality of performance.

An offeror who simply states they will perform the work and complete the requirement will be considered non-responsive and subsequently will be determined technically non-compliant and be eliminated from further consideration for award. Offerors technical approach must demonstrate a thorough understanding of the context of the work to be performed and must possess the ability to perform all task requirements and have a clear value proposition that attempts to differentiate itself from other potential offerors.

Provide personnel with expertise in developing, administering, and analyzing proposed Task Order #2 objectives. Provide a description of the experience, skills, and capabilities of each of the key personnel. Descriptions shall include the quality and depth of experience of proposed personnel in working on similar projects in terms of background, education, work experience, and accomplishments. Descriptions shall demonstrate the knowledge that key personnel have gained through completed and ongoing efforts on similar efforts. "Similar efforts" is meant to convey similarity in subject matter, dollar value, and complexity as related to work described in the task objectives.

Commented [SD27]: Q&A #158

In order to meet the requirements of the task order, the contractor should assess and propose the

Project Manager/Project Managers: The contractor will identify one or more project managers with overall responsibility for delivery of tasks and deliverables identified in the PWS. The project manager will be the responsible for meeting and exceeding deliverable quality, timeliness and cost measures. He/she will have strong organizational skills, project management skills, and the ability to lead teams to deliver and implement robust IT solutions. It is highly desirable that the identified project managers have the following experience/qualifications:

• 5+ years demonstrated experience managing highly complex and high-visible IT projects relating to financial support systems across the entire software development lifecycle.

• 5+ years demonstrated experience supporting financial IT system operations and managing IT software development projects using multiple methodologies

• Technical understanding and experience with the technologies identified supporting the FMS systems

• Project Management Institute Project Management Professional (PMP) Certification

• Demonstrated written and verbal communication skills, including experience in

Technical Lead/Leads: The contractor will identify one or more technical leads who will be responsible for architecting, deploying, and supporting all the FMS footprint. The technical lead(s) will have strong conceptual design skills, knowledge of scripting, and the ability to lead teams to envision, design, and implement robust IT solutions.

Technical lead(s) should have extensive technical leadership and IT systems development experience directly supporting financial systems. It is highly desirable that the technical lead(s) has the following experience

• 10+ years experience overseeing the design, development, and implementation of software and hardware solutions, systems and products

• Experience interfacing IT systems with Department of Treasury shared services

• Extensive hands on experience with technology supporting the FMS systems with specific emphasis on Oracle/Java technologies including Oracle E-Business Suite.

• Experience with the following technologies highly desired:

• Oracle E-Business-Suite (EBS) Release 12 (GL Module, Fed Admin, TCA, CRM, AP, PO)

• Oracle SOA Suite

• Oracle BI Publisher and Oracle Forms and Reports

• Oracle RDBMS and Weblogic server

• Oracle Rules Engine

• Java Web services

• Oracle 11g/12C database administration

• UNIX shell scripting and cron jobs

• Java/J2EE

• JavaScript

• PL/SQL

• Spring Framework

• iBatis

• Oracle ADF

• JAX-WS JAXB

• .NET

• Asynchronous Javascript and XML (AJAX), XHTML, and VB coding principle

Bootstrap

Factor 3 – TO Management Approach

Offeror’s proposal must demonstrate the following:

• An effective, efficient, feasible and practical level of understanding of the operating environment in accomplishing the tasks of TO #2, with minimal risk to the Government and an effective concept of operations with their team and the Government.

• An effective, organizational structure, which explains handling lines of authority and communication both within the contractor’s team and with stakeholders at PBGC.

• An effective, approach to risk management providing a realistic process for managing

L.2.4 PART D – SAMPLE DEVELOPMENT TASK SCENARIO RESPONSE

The Offeror’s response to the Sample Development Task Scenario SOO (attached) is for technical evaluation purposes only. Pricing is not requested for the response to the sample development task scenario.

Factor 1 - Approach and Understanding of Requirements

Offerors must describe their approach to addressing each objective as outlined in the Sample Development Task Scenario and address the associated constraints in meeting those objectives.

Offerors must include in their technical approach a staffing plan and performance work statement (PWS) that includes, as defined in Sample Task Order, Section 3, the following:

• Tasks required to meet task order objectives and associated performance standards

• Deliverable and performance standards that incorporate minimum deliverable and performance standards as set out in the task order.

Sample Task Order (i.e., who is doing what when and how, and what are the expected results).

In addition, offerors shall propose the methodology and the framework for the IT services and associated performance metrics they will be utilizing and measured on under this task order. A successful approach must include how quality deliverables will be produced through effective technical writing.

The approach shall be simple, easy to read, and shall clearly and concisely describe task responsibilities and personnel, relevant communication and coordination, scheduling of all tasks and subtasks, meetings, and deliverables. All staff needed to conduct the work and produce all required products and deliverables must be identified in a project organizational chart. In meeting deliverables, Offerors shall elaborate on how they plan to measure their efforts to ensure the highest quality of performance.

An offeror who simply states they will perform the work and complete the requirement will be considered non-responsive and subsequently will be determined technically non-compliant and be eliminated from further consideration for award. Offerors technical approach must demonstrate a thorough understanding of the context of the work to be performed and must possess the ability to perform all task requirements and have a clear value proposition that attempts to differentiate itself from other potential offerors.

Factor 2 - Key Personnel

Provide personnel with expertise in developing, administering, and analyzing proposed Sample Development Task objectives. Provide a description of the experience, skills, and capabilities of each of the key personnel. Descriptions shall include the quality and depth of experience of proposed personnel in working on similar projects in terms of background, education, work experience, and accomplishments. Descriptions shall demonstrate the knowledge that key

Commented [SD28]: Q&A #158 personnel have gained through completed and ongoing efforts on similar efforts. "Similar efforts" is meant to convey similarity in subject matter, dollar value, and complexity as related to work described in the task objectives.

In order to meet the requirements of the task order, the contractor should assess and propose the

Project Manager: The contractor will identify a project manager with overall responsibility for delivery of tasks and deliverables identified in the PWS. The project manager will be the responsible for meeting and exceeding deliverable quality, timeliness and cost measures. He/she will have strong organizational skills, project management skills, and the ability to lead teams to deliver and implement robust IT solutions. It is highly desirable that the identified project managers have the following experience/qualifications:

• 5+ years demonstrated experience managing highly complex and high-visible IT projects relating to financial support systems across the entire software development lifecycle.

• 5+ years demonstrated experience supporting financial IT system operations and managing IT software development projects using multiple methodologies

• Technical understanding and experience with the technologies identified supporting the FMS systems

• Project Management Institute Project Management Professional (PMP) Certification

• Demonstrated written and verbal communication skills, including experience in

Technical Lead: The contractor will identify a technical lead who will be responsible for architecting, deploying, and supporting all the FMS footprint. The technical lead will have strong conceptual design skills, knowledge of scripting, and the ability to lead teams to envision, design, and implement robust IT solutions. The technical lead should have extensive technical leadership and IT systems development experience directly supporting financial systems. It is highly desirable that the technical lead(s) has the following experience

• 10+ years experience overseeing the design, development, and implementation of software and hardware solutions, systems and products

• 5+ years hands-on experience with the technologies identified in the Sample Task Order future state objectives.

• Demonstrated experience managing large web modernization projects for the Federal Government.

• Demonstrated written and verbal communication skills, including experience in presenting material to mid-level and senior Government officials.

• Demonstrated experience with Federal Regulations related to publicly accessible federal web sites and applications

• Demonstrated experience maintaining project schedules and ensuring deliverables completed according to Government requirements.

User Experience Specialist: The contractor shall identify a User Experience (UX) Specialist to serve as the web modernization’s project UX subject matter expert. It is highly desirable that the UX specialist has the following experience on federal e-Gov modernization projects with requirements like those contained in the task order:

• Demonstrated experience with customer satisfaction surveys and improving scores of federal e-Gov web applications

• Demonstrated experience in user interface design and improvement

• Demonstrated experience with Section 508 federal regulations and requirements related to UX

• Demonstrated experience with system performance and its relation to user experience

• Demonstrated experience with federal government plain language initiatives and its relation to user interface instructions, context sensitive help, and user manuals

Factor 3 - Task Order Management Approach

Offeror’s response must demonstrate the following:

• An effective, efficient, feasible and practical level of understanding of the operating environment in accomplishing the tasks of Sample Order, with minimal risk to the Government and an effective concept of operations with their team and the Government.

• An effective, organizational structure, which explains handling lines of authority and communication both within the contractor’s team and with stakeholders at PBGC.

• An effective, approach to risk management providing a realistic process for managing

L.3 BUSINESS / PRICE PROPOSAL (VOLUME II):

BUSINESS / PRICE PROPOSAL (VOLUME II) The Offeror shall provide a complete Price Proposal and a complete Section K (Certifications and Representations) in accordance with the solicitation. The Offeror's Business/Price Proposal, must include the following items/documents:

(a) The Proposal Form, SF 1449, "Solicitation, Offer and Award." The Proposal Form is to be executed fully and used as the cover sheet (or first page) of this volume. The acceptance period entered on the Proposal Form by the Offeror shall not be less than 120 calendar days from the date specified for the receipt of offers. The person signing the Proposal Form must have the authority to commit the Offeror to all of the provisions of the proposal, fully recognizing that the Government has the right, by terms of the solicitation, to make an award without further discussions.

(b) The Offeror's Representations, Certifications, and Other Statements of Offerors (Section K) are to be completed and included in this volume.

(c) Existence or appearance of potential conflicts of interest. Offerors must disclose to the Contracting Officer any personal or business relationships with Government personnel, or financial interests, which could present the appearance of an existing or potential conflict of interest. Failure to do so, if such become known by other means could result in a determination of nonresponsibility prior to award, or termination of the contract after award.

(d) The Pricing section of the proposal shall consist of a completed Section B, “IDIQ Pricing Schedule” for the Base Year plus all four Option Periods in accordance with the template provided in Section B and the rates in Section B. Failure to complete the entire Section B, inconsistency between Section B rates and the pricing rates will render the pricing proposal unacceptable.

Pricing information shall include:

Part A: IDIQ Pricing Response

The FMS-ITSS IDIQ itself will not carry any costs but will dictate the overall pricing for TOs issued against it. For all periods of performance of the IDIQ, please provide proposed prices. These prices will form the basis of all pricing for task orders issues against the IDIQ for the life of the contract. A pricing template is provided in Section B representing minimum information required by offerors.

Pricing information must include:

• Labor category title

• Fully burdened hourly rate (for both Govt.-site and Contractor-site)

Commented [SD29]: Q&A #138 and 139

Part B: Task Order One Pricing Response

The offeror shall propose pricing for conducting work under the task order and reflect the current pricing reflected in the overall IDIQ pricing response from Section B Pricing Schedule. A pricing template is provided, representing minimum information required by offerors.

Pricing information must include:

• Labor category title

• Fully burdened hourly rate (for both Govt.-site and Contractor-site)

• Estimated hours for each proposed labor category

• Any discount being provided for this TO.

As a firm fixed price task order, detailed information is provided for evaluation purposes only.

Part C: Task Order Two Pricing Response

For Task Order #2, cost and pricing information should be provided for the proposed price of conducting work under the task order and reflect the current pricing reflected in the overall IDIQ pricing response from Part A.

Pricing information must include:

• Labor category title

• Fully burdened hourly rate (for both Govt.-site and Contractor-site)

• Estimated hours for each proposed labor category

• Any discount being provided for this TO.

L.4 SMALL BUSINESS PARTICIPATION (VOLUME III)

L.4.1 The small business participation factor, as used in this solicitation, assesses the offerors plan to maximize opportunities for small business in the performance of the solicitation requirements.

L.4.1.1 STRICT COMPLIANCE REQUIREMENT: THE OFFEROR SHALL SUBMIT

THE FOLLOWING DOCUMENTATION OR ITS PROPOSAL WILL BE REMOVED

FROM FURTHER CONSIDERATION AND WILL NO LONGER BE ELIGIBLE FOR

AWARD:

• A completed Contract Participation Matrix (Attachment 0007).

• The proposed subcontractor’s written certification of size and socio-economic status for each proposed subcontractor. However, for HUBZone certified subcontractors, the offeror shall provide evidence of HUBZone certification using one of the methods in FAR clause 52.219-8(d)(2).

• Documentation demonstrating the offerors commitment to small business. This documentation shall also address historical small business performance.

Commented [SD30]: Q&A #150

L.4.1.2 Definitions:

• Participant, as used in this factor, includes the offeror as well as any subcontractor.

• Participation, as used in this factor, includes the work (dollars) performed by the offeror, as well as the work (dollars) of any subcontractor.

• Recent, as used in this factor, is defined as any contract action where services or deliverables were performed or still being performed anytime within three (3) years of issuance of this RFP.

L.4.2 The offeror’s proposal shall include a completed Contract Participation Matrix (Attachment 0007). Attachment 0006 contains instructions to complete the Contract Participation Matrix. The Contract Participation Matrix shall identify:

• Each proposed participant, including:

• Full Company Name

• CAGE Code

• Each Socio-Economic Category for which the participant qualifies, i.e., Small

Disadvantaged Businesses (SDB), Women Owned Small Businesses (WOSB), HUBZone certified Small Businesses (HUBZone), Veteran Owned Small Businesses (VOSB), or Service-Disabled Veteran-Owned Small Businesses (SDVOSB).

• Total Dollars allocated to the participant.

• The total dollars proposed to each category (Small Businesses (SB), SDB, WOSB, HUBZone, VOSB, SDVOSB, and Other than Small

• The total participation dollars (total dollars proposed to Small Businesses + total dollars proposed to Other than Small Businesses). The total participation dollars shall equal $100,000,000.00.

• The percentage of participation (goal) for each socio-economic category.

Note: Small Business participation shall include total dollars allocated for the business in each category for which the business qualifies. For example, if the offeror allocates $100 to a HUBZone-certified SDVOSB, the offeror would include $100 in the SB category, $100 in the HUBZone category, $100 in the SDVOSB category, and $100 in the VOSB category.

L.4.3 The offeror shall provide the written certification of size and socio-economic status for each small business subcontractor proposed for this procurement. The offeror may, but is not required to, provide a copy of the System for Award Management (SAM) certifications for clause 52.219-1, Small Business Program Representations in lieu of written certifications.

However, for HUBZonecertified subcontractors, the offeror shall provide evidence of HUBZone certification using one of the methods in FAR clause 52.219- 8(d)(2). The written certifications shall match the size and socio-economic status identified in the Contract Participation Matrix for each subcontractor.

L.4.4 The offeror’s proposal shall also provide evidence supporting the offeror’s commitment to small business and information on its historical small business participation. This information shall address:

• Compliance with all terms and conditions of FAR 52.219-8, Utilization of Small Business Concerns (when required on recent contracts). This shall include procedures established to ensure timely payments to small business subcontractors. This clause is

Commented [SD31]: Q&A #150

Commented [SD32]: Q&A #150 normally in most Federal contracts, and is also applicable to small businesses. If not required in any recent contracts, the offeror shall so state.

• Compliance with terms and conditions of FAR 52.219-9, Small Business Subcontracting plan (when required on recent contracts). If not required in any recent contracts, the offeror shall so state.

• Actual small business utilization compared to small business participation goals identified in the approved subcontracting plan for each recent contract that included a subcontracting plan. Offerors shall identify the date of the last Individual Subcontracting Report (ISR)/Summary Subcontracting Report (SSR). Offerors shall address achievement on each individual goal stated within the subcontracting plan including good faith effort if the goal was not achieved. If not required in any recent contracts, the offeror shall so state.

The offeror also may submit bilateral teaming arrangements, an explanation of internal controls/documentation/systems, or any other documentation the offeror feels demonstrates a commitment to small business. The offeror’s submission should also explain how the documentation demonstrates a commitment to small business.

L.4.5 Note for other than small businesses ONLY. Separate from Small Business Participation, other than small business offerors shall also submit a Small Business Subcontracting Plan as required by FAR 19.7 (FAR clause 52.219-9, Small Business Subcontracting Plan). The Small Business Subcontracting Plan shall be consistent with proposed small business participation. The subcontracting plan shall be submitted in Volume IV, not in this Volume.

L.5 QUESTIONS CONCERNING THE SOLICITATION:

(a) All questions concerning this solicitation must be submitted in writing to the Contract Specialist, Dan Swart and the Contracting Officer, Patrick McFarlane.

(b) Questions will be submitted in writing by email to swart.dan@pbgc.gov and copy to mcfarlane.patrick@pbgc.gov. Answers to inquiries/questions will be provided to offerors being solicited, giving due regard to the proper protection of proprietary information.

(c) No information concerning this solicitation will be provided in response to telephone calls.

All such requests must be submitted by email to swart.dan@pbgc.gov and copy to mcfarlane.patrick@pbgc.gov. Inquiries will be answered by amendment to the solicitation.

(d) Prospective offerors are asked to submit their questions grouped by solicitation section and making reference to the particular paragraph. Questions must be submitted in writing by May 24, 2018 at 4:30 PM to allow the PBGC an opportunity to respond. Any questions received after that may not be answered before the solicitation closing date.

L.6 OFFER VALIDITY STATEMENT

Offeror(s) shall make a clear statement in their proposal cover letter that the proposal is valid for no less than 120 calendar days from the closing date of the solicitation.

Commented [SD33]: Q&A #39