RFP Appendix 1 - Offeror Qualifications, Experience, and References.docx

DOCX document 114 KB Posted

Attached to
PennDOT Mainframe Services
Solicitation number
3525R03
Issued by
Pennsylvania

About this file

This file is an appendix to a Request for Proposal (RFP) issued by the Pennsylvania Department of Transportation (PennDOT) for mainframe services, specifically Solicitation No. 3525R03. The RFP seeks qualified vendors to provide IBM-compatible mainframe services including hosting, management, infrastructure support, disaster recovery, and security compliance for approximately 100 applications, with several classified as critical. Offerors must meet specific qualification requirements, including a three-year track record in public sector mainframe service delivery using an on-shore model without any terminated-for-cause engagements, and must have completed at least two major similar projects within the last six years as prime contractor, each valued at a minimum of $15 million annually.

The appendix establishes requirements for offerors to provide detailed business experience documentation, transition lessons learned from existing managed hosting environments, service delivery information demonstrating how the proposed solution addresses the Commonwealth's vision and outcomes, and pricing structures supporting consumption-based payment models that reduce costs proportionally as applications transition to alternative platforms. Offerors must submit a minimum of three references for comparable mainframe services previously delivered, with reference contacts including name, title, phone number, and service descriptions, clearly identifying whether the offeror served as prime or subcontractor. References cannot include prior contracts with Commonwealth of Pennsylvania entities, and all experience documentation must include specific client information, project scope, contract values, transition charges, and operational dates without external references or website links.

View the file

Other files

File Type Posted
1371302-event.pdf PDF
RFP Appendix 3 - Data Room Access NDA.pdf PDF
Technical Submittal Template.docx DOCX document
RFP Appendix 2 - Objections and Additions.xlsx XLSX spreadsheet
Data Room Instructions.pdf PDF
Master Services Terms (MST).pdf PDF
Exhibit 1.3 - Service Management Manual —
MST Attachment B - Insurance and Risk of Loss.pdf PDF
Offeror Response Formats and File Naming Instructions.docx DOCX document
Exhibit 2.0 - Service Model —
RFP Appendix 4 - RFP Tools Matrix.xlsx XLSX spreadsheet
MST Attachment E - Form of Work Order.pdf PDF
Exhibit 1.2 - Governance Model —
MST Attachment C - Commonwealth Software Products and Services.pdf PDF
Vendor Security Requirements.docx DOCX document
Exhibit 4.2 - Financial Responsibility Matrix —
Exhibit 3.1 - Service Level and Deliverable Matrix —
Diverse Business Good Faith Efforts Requirements.pptx PPTX presentation
RFP Appendix 6 - Software.xlsx XLSX spreadsheet
Exhibit 4.0 - Business Model —
Exhibit 2.2 - Mainframe Services Solution —
MST Attachment A - Non-Disclosure Agreement.pdf PDF
Exhibit 1.1 - Definitions —
Exhibit 3.3 - Reports —
BDISBO SDB VBE Goal Setting Information Session.pdf PDF
Exhibit 4.3 - Form of Invoice and Data Feed —
Q and A Board Instructions.pdf PDF
Exhibit 3.0 - Performance Model —
Policy Driven Adoption for Accessibility (PDAA) Assessment Template.docx DOCX document
RFP Appendix 5 - Personnel Projection Matrix.xlsx XLSX spreadsheet
Exhibit 1.0 - Operating Model —
MST Attachment D - Form of Parent Guaranty.pdf PDF
Exhibit 2.3 - Key Personnel —
MST Attachment F - Form of Final Contract.pdf PDF
Exhibit 2.1 - Mainframe Services SOW —
Show all 35

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Pennsylvania Department of Transportation (PennDOT)

Mainframe Services

RFP Appendix 1 Offeror Qualifications, Experience and References

RFP 3525R03

OFFEROR QUALIFICATIONS

Qualification/Requirement
Offeror Comments

Explain How Offeror Meets Requirements Be Specific – Identify Projects and Initiatives Role

Prime
Sub

The Offeror has not, within a three (3) year period preceding this RFP, had one or more public sector (federal, state, or local government) engagements for similar services stated in Exhibit 2.1 (Mainframe Services Statement of Work) terminated for cause.

Offeror must have three (3) or more years’ experience in the public sector (federal, state, or local government) providing similar services in an On-Shore delivery model as stated in Exhibit 2.1 (Mainframe Services Statement of Work).

3.Offeror must have entered into at least two (2) similar major projects within the last six years where the following was true: 1) The annual contract value was at least $15 million, and 2) The Offeror was the prime Contractor.

RFP Appendix 1 (Offeror Qualifications, Experience and References)

RFP Solicitation No. 3525R03 Page 11 of 12

OFFEROR EXPERIENCE

Offeror Guidelines

1. Offeror shall summarize its business experience providing the Services described in this RFP, including specific industry certifications or awards related to delivery of the Services described herein. If responding as a Prime and Subcontractor partnership, Offeror must specify the company for the specific business experience described below. Offeror shall fully respond to the elements as requested.

2. Offeror shall duplicate the table below as necessary to provide all relevant experience.

Offeror shall use projects reflecting the markets in which it typically works (e.g., state agency, federal government, education, local governments). Offeror shall describe and/or demonstrate how the experience supports Offeror qualifications described in this RFP.

Offeror shall not refer to information elsewhere in the RFP Response or reference website links. Attachments are acceptable and should be clearly marked and referenced.

Business Experience (Describe in detail for each element):

Description

1. Managed Service Project Information.

Offeror shall provide:

a. Client Name

b. Contact Name and Title

c. Contact Phone Number

d. Contact E-mail

e. Project Name and Scope

f. Project Schedule (start date and end date – mm/yyyy)

g. Transition Charges

h. Annual Contract Value

2. Transition Lessons Learned Offeror shall describe the lessons learned transitioning the services, including from an existing MFaaS environment, with examples of both positive and negative experiences and how those impacted the transition cost, timeline, and delivery of the services.

3. Service Delivery Lessons Learned Offeror shall describe how it designed and deployed a mainframe service (process and technology) that directly addresses the vision and desired outcomes articulated in section I-1 of the Technical Submittal document.

4. Pricing Offeror shall describe how it supported the client’s objective to pay for services on a consumption basis where costs are reduced proportionately as the Commonwealth transitions applications to other platforms (e.g., public or private cloud).

OFFEROR REFERENCES

Offeror Guidelines Offeror shall provide the name, title, contact number, and description of services provided for at least three (3) references for which the Offeror provided services of the nature described, noting if Offeror were the Prime or Subcontractor. If responding as a Prime Service Provider and Subcontractor partnership, Offeror must specify the company for the specific reference described below. Please note: References must have received the same type(s) of Mainframe Services from Offeror as what Offeror is proposing to provide in response to this RFP. Offeror is precluded from submitting references where the contract was with a Commonwealth of Pennsylvania entity.

OFFEROR PAST PERFORMANCE REFERENCE INFORMATION

Reference No. 1 Contractor Name on Proposal

Name of Client Organization:

Business Address

Business City

Business State

Zip
Contact Person Name
Contact Person Title
Phone Number
Contract Title

Prime or Subcontractor

Contract Description (including description of services, contract number, and award date)

Operations Start Date

Operations End Date

Reference No. 2 Contractor Name on Proposal

Name of Client Organization:

Business Address

Business City

Business State

Zip
Contact Person Name

Contact Person Title

Phone Number

Contract Title

Prime or Subcontractor

Contract Description (including description of services, contract number, and award date)

Operations Start Date

Operations End Date

Reference No. 3 Contractor Name on Proposal

Name of Client Organization:

Business Address

Business City

Business State

Zip
Contact Person Name
Contact Person Title

Phone Number

Contract Title

Prime or Subcontractor

Contract Description (including description of services, contract number, and award date)

Operations Start Date

Operations End Date

RFP Solicitation No. 3525R03 Page 11 of 12 image1.jpeg

File details come from the government source that posted it. Updated .