Offeror Response Formats and File Naming Instructions.docx

14 KB Posted

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

About this file

Written by GovTribe AI ·

This document provides offeror response format and file naming instructions for RFP 3525R03, a Pennsylvania Department of Transportation (PennDOT) solicitation for mainframe services. The RFP seeks IBM-compatible mainframe services including hosting, management, infrastructure support, disaster recovery, and security compliance for approximately 100 applications, including critical systems. Offerors must submit technical submittals using either the provided template or their own format, with responses formatted on standard 8.5 x 11 inch pages, minimum 0.5 inch margins, and fonts no smaller than 11-point. All electronic files must be created or fully compatible with current Microsoft 365 or Microsoft Project software suites and be searchable with selectable text. Multiple files should be combined into a single document or a .zip file. Technical submittals and supporting attachments should be uploaded to JAGGAER Question 1.1.1 and 1.1.2 respectively, while the cost submittal must be submitted exclusively in Excel format using the provided template to JAGGAER Question 1.5.1.

All submissions must ensure compatibility with Microsoft Office 2010 or above, and responses to specific questions may be submitted in PDF format where indicated, particularly for trade secret redacted versions and documents requiring signatures. Offerors must save each file using the original filename prefixed with their service provider name identifier and the word "Response" (for example, "ABC Response"), maintaining consistent use of the same identifier across all submitted files. The cost information submission requires offerors to complete the Summary Charges tab with their company name, date, and "completed by" information, with cost data restricted to the designated cost question response only.

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
RFP Appendix 1 - Offeror Qualifications, Experience, and References.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
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

RFP 3525R03 PennDOT Mainframe Services Offeror Response Formats and File Naming Please download, complete and upload your Technical Submittal as instructed to JAGGAER Question 1.1.1 using the Technical Submittal located in Buyer Attachments, or you may use your own format. Either will be accepted. Technical Submittals should not be excessively lengthy, and pictures should be limited. Responses should be formatted on a standard 8 ½ x 11 in. page size, with no less than ½ in. margins and a font no smaller than 11-point. All electronic files submitted should be created (or fully compatible) with the current versions of Microsoft 365 or Microsoft Project Software suites or packages. Documents should be searchable, and with selectable text.

Any additional attachments in support of the technical submittal can be uploaded to JAGGAER Question 1.1.2. as instructed. If multiple files are needed combine into a single document or create a .zip file combining the files into a single .zip file. All responses must ensure compatibility with Microsoft Office 2010 or above. Offerors need to respond using the provided Microsoft Word and Excel templates.

Responses to JAGGAER Question 2.1.4 (Trade Secret redacted version) may be submitted in pdf for redaction purposes.

Documents and question responses with signature requested may be submitted in pdf.

The response to JAGGAER Question 1.5.1 Cost should be submitted only in Excel format on the provided template. Type in the Offeror’s name, date, and “completed by” blanks as requested on the Summary Charges tab. Cost information should be submitted only in response to JAGGAER Question 1.5.1., as requested.

For each file submitted, the Offeror shall save the file as the original filename prefixed with the Service Provider name identifier and the word “Response” (e.g., “ABC Response”) where “ABC” is an acronym identifying the Offeror. All files submitted by the Offeror must use the same identifier (e.g., only use ABC, not variations such as AB, AB&C, Abc, and ABnC).

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