Questions-and-Answers.pdf
PDF 154 KB Posted
- Solicitation number
- Not on record
- Issued by
- Philadelphia County, Philadelphia City, Pennsylvania
About this file
This is a Questions and Answers document for SEPTA's (Southeastern Pennsylvania Transportation Authority) Expression of Interest for an Integrated Platform-as-a-Service (iPaaS) solution in Pennsylvania. The EOI seeks to establish a shortlist of qualified vendors for an iPaaS platform to modernize SEPTA's technology infrastructure, which is currently segmented and lacks scalability to integrate multiple data sources. SEPTA is undertaking a major Enterprise Resource Planning (ERP) platform implementation with a projected completion timeframe of 36 months. The agency strongly prefers a cloud-first deployment model with the eventual goal of realizing a fully cloud-based application environment. Following review of EOI responses, SEPTA plans to release a formal RFP for potential vendors to respond to, though specific go-live timelines and deadlines are not yet disclosed in this document.
Detailed information regarding SEPTA's current technology infrastructure, transaction volumes, data payload sizes, specific systems in use (ERP, HRIS, CRM), cloud platforms (Azure, AWS, GCP), API gateway configurations, budget ranges, pricing model preferences, and MBE/WBE or local subcontracting requirements will be provided in the upcoming RFP. The document indicates that SEPTA is in the process of modernizing its technology infrastructure to meet current IT standards, moving away from legacy systems. Security requirements, including any federal cybersecurity mandates such as TSA directives for public transit or FTA requirements, will also be detailed in the subsequent RFP. The Q&A addresses inquiries about integration protocols, event streaming platforms, data residency requirements, identity providers, and potential transit-specific standards like GTFS, though most responses defer comprehensive answers to the forthcoming RFP documentation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Expression-of-Interest-for-Integrated-Platform-as-a-Service.pdf | ||
| EOI-Letter-.pdf |
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
EOI – INTEGRATED PLATFORM-AS-A-SERVICE (iPaaS)
QUESTIONS AND ANSWERS
1. Could SEPTA share details of its current integration landscape, including the primary technologies, platforms, and middleware in use today?
Information regarding SEPTA's technology infrastructure and landscape will be provided in the upcoming RFP.
2. Has SEPTA already identified or shortlisted any preferred iPaaS platforms under consideration, or is the evaluation fully open?
The purpose of this EOI is to establish a shortlist of qualified vendors based on the responses received.
3. Are there existing vendor partnerships or technology standards that influence platform selection?
SEPTA is currently in the process of modernizing its technology infrastructure to meet current information technology standards.
4. What are the current pain points SEPTA faces with integration (e.g., data silos, latency, lack of API governance, manual workflows)?
The current technology infrastructure is segmented and lacks scalability and expandability that a modern technology infrastructure has to integrate multiple data sources.
5. Is there a strong preference for cloud-first deployment, or will hybrid/on-premise models be equally considered?
SEPTA strongly prefers a cloud environment model.
6. What is SEPTA’s expected transaction volume and scalability requirements for the iPaaS solution?
More information regarding current transaction volume will be provided in the upcoming RFP.
7. Could SEPTA outline its integration roadmap for the next 12–24 months, including major modernization or cloud migration initiatives?
SEPTA will complete an initiative to obtain and implement an Enterprise Resource Planning platform for the organization. The projected timeframe for completion is within 36 months.
8. Are there specific business transformation projects that the iPaaS solution should support in the next 12-24 months?
Information regarding SEPTA's business transformation projects will be provided in the upcoming RFP.
9. Could SEPTA provide insight into the complexity of its current ETL/ELT processes, and the data volumes and throughput requirements?
Information regarding SEPTA's ETL/ELT processes, and the data volumes and throughput requirements will be provided in more detail in the upcoming RFP.
10. What ERP, HRIS, CRM, and financial systems are currently in use? (Infor, SuccessFactors, etc.)?
The purpose of this EOI.
11. How many distinct applications and systems need to be integrated, both now and in the next 2–3 years?
SEPTA is currently in the process of modernizing its technology infrastructure to meet current information technology standards. More information will be provided with the release of the upcoming RFP.
12. Are there any legacy on-premise systems that must remain on-prem long-term, or is full cloud migration the eventual goal?
SEPTA's goal is to realize a fully cload based application
13. What are the approximate transaction volumes per day/month across integrations?
14. What is the largest payload size anticipated? Are there bulk file transfers (e.g., SFTP batch files from payroll or finance)?
15. Are there any real-time, sub-second latency requirements, and for which specific use cases?
More information will be provided in the upcoming RFP.
16. What cloud platforms does SEPTA currently use or plan to adopt (Azure, AWS, GCP)?
Information regarding SEPTA's technology infrastructure and landscape will be provided in the upcoming RFP.
17. Does SEPTA have an existing API gateway in place (Apigee, AWS API Gateway, Azure APIM), or is API management a greenfield need?
18. Beyond the protocols listed, are there any transit-specific standards required — e.g., GTFS, GTFS-RT, or NTD reporting integrations?
19. Are there any EDI requirements (X12, EDIFACT) for vendor or partner integrations?
More information will be provided in the upcoming RFP.
20. Is there a need to integrate with SCADA or OT systems for rail/infrastructure operations?
21. Is Apache Kafka or any event streaming platform already in use?
22. Which operational systems generate events that need to be streamed (e.g., vehicle telemetry, fare collection, incident management)?
23. Does SEPTA fall under any federal cybersecurity mandates (e.g., TSA cybersecurity directives for public transit, FTA requirements)?
Security requirements will be provided in the upcoming EOI.
24. Is FedRAMP authorization a hard requirement, or a preference?
25. What identity provider does SEPTA use (Azure AD, Okta, on-prem Active Directory)?
26. Are there data residency requirements — must data remain within the US or within Pennsylvania specifically?
27. Is there a specific SIEM platform in use today (Splunk, Microsoft Sentinel) that log integration must support?
28. How many integration developers and architects are on staff today?
29. Is there an existing API catalog or policy framework, or is this being built from scratch?
30. What is the anticipated go-live timeline, and are there any hard deadlines tied to system retirements or go-lives of other platforms?
31. What is SEPTA's rough budget range or expected pricing model preference (subscription, consumption-based)?
32. Are there MBE/WBE or local subcontracting requirements that a prime vendor would need to satisfy?
33. Beyond this EOI, what does SEPTA's evaluation process look like — will there be a formal RFP, oral presentations, or a proof-of-concept/demo requirement?
Atter review of the resposes from this EOI, SEPTA plans to release a formal RFP for potential vendors to respond.
File details come from the government source that posted it. Updated .