Response-Form-4-Non-Functional-Requirements.xlsx
XLSX spreadsheet 115 KB Posted
- Solicitation number
- RFP 26-00268-AHAC
- Issued by
- Philadelphia County, Philadelphia City, Pennsylvania
About this file
Summary
This document is Response Form 4: Non-Functional Requirements for the Southeastern Pennsylvania Transportation Authority (SEPTA) Enterprise Resource Planning (ERP) Software and Implementation Services procurement. The file provides detailed instructions and requirements for proposers to evaluate and respond to 92 technical requirements (Tech.001-Tech.092) and 106 cybersecurity requirements (Sec.001-Sec.106) across domains including general architecture, PaaS/hosting, support and operations, disaster recovery, integration, configuration management, storage, network, testing, usability, and data conversion. Proposers must evaluate each requirement using standardized compliance codes (Y for out-of-the-box, C for configurable, F for future release, 3 for third-party solution, or N for not supported), specify customization complexity (High/Medium/Low), identify the module or solution component, and provide mandatory narrative comments for non-standard responses. Requirements are classified as either Required (Req) or Preferred (Pref), with many mapped to NIST SP 800-53 security controls for cybersecurity items.
Key technical requirements include cloud-based SaaS architecture with multi-tenant isolation, U.S.-based data centers within the contiguous United States, browser compatibility with Microsoft Edge and Google Chrome, integration with Azure AD/SAML for identity federation, support for REST APIs and modern integration patterns, mobile access for Android and iOS devices, WCAG 2.1 Level AA accessibility compliance, and comprehensive data migration capabilities with validation and reconciliation controls. Cybersecurity requirements emphasize encryption using FIPS 140-2 validated modules for data at rest and in transit (TLS 1.2+), role-based access controls with separation of duties, multi-factor authentication aligned with NIST SP 800-63B-4 AAL2, integration with SEPTA's SIEM for security event logging, vulnerability management with defined remediation timelines (Critical within 30 days, High within 60 days, Medium within 90 days using CVSS v3.1), annual SOC 2 Type II audit reports, incident notification within 24 hours for breaches, compliance with Pennsylvania's Breach of Personal Information Notification Act, and comprehensive audit logging with protected retention. Proposers are prohibited from modifying requirement IDs, adding or deleting rows, or altering SEPTA's pre-populated content, and must maintain strict response discipline to enable consistent evaluation and scoring.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Response-Form-1-QA-Submission.xlsx | XLSX spreadsheet | |
| Attachment-03B-Software-Price-Proposal.xlsx | XLSX spreadsheet | |
| RFP-26-00268-AHAC-for-ERP-Software-and-Implementation-Services.pdf | ||
| Exhibit-C-Reports-Inventory.xlsx | XLSX spreadsheet | |
| Appendix-2B-Exit-Services.pdf | ||
| Response-Form-3-Functional-Requirements.xlsx | XLSX spreadsheet | |
| Attachment-03A-Price-Proposal-for-SI-Services.xlsx | XLSX spreadsheet | |
| Invitation-to-Propose-ERP-SI.pdf | ||
| Response-Form-2-Proposer-Information.xlsx | XLSX spreadsheet | |
| Appendix-2C-Performance-Management.pdf | ||
| Exhibit-B-Key-Personnel.pdf | ||
| Exhibit-A-Applications-Interfaces-Inventory-1.xlsx | XLSX spreadsheet |
Show all 12
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
Instructions
| SEPTA ERP Software and Implementation Services |
| Response Form 4: Non-Functional Requirements — Instructions & Proposer Guidance |
Proposers responding to SEPTA's RFP must use the guidance provided in this sheet to review and respond to the detailed requirements in the subsequent tabs. Proposers are required to evaluate each non-functional requirement across all technical and cybersecurity domains, designate their solution compliance rating (Y/C/F/3/N), specify customization complexity (H/M/L), and provide required narrative comments.
| 1. REQUIREMENT COLUMNS & VENDOR RESPONSE DEFINITIONS | ||
| Column Header | Description & Functional Meaning | Valid Values & Guidance |
| ReqID | Unique identifier assigned to each non-functional or cybersecurity requirement. Used for cross-referencing during proposal evaluation, technical scoring, and contract framing. | Pre-populated by SEPTA. Proposers must NOT modify, renumber, or delete any ReqID. |
| Main Process / Topic | High-level non-functional domain classification representing core architecture, security, infrastructure, or operational service categories. | Pre-populated by SEPTA. Proposers must NOT modify. Standard Categories: |
• Cybersecurity
• General Architecture
• PaaS / Hosting
• Support & Ops
• Disaster Recovery
• Integration
• Configuration
• Storage
• Network
• Testing
• Usability
• Data Conversion
| Sub-Process / Topic | Specific technical capability or operational focus area within the main process category. | Descriptive topic title detailing the technical focus area of the requirement. Pre-populated by SEPTA. Proposers must NOT modify. |
| NIST 800-53 Mapping | Applicable NIST SP 800-53 Special Publication security control family and control identifiers mapped specifically to Cybersecurity requirements. | NIST Control References. Applicable to Cybersecurity ('Sec') rows. Pre-populated by SEPTA. Proposers must NOT modify. |
| Requirements | Detailed non-functional requirement statement defining technical capabilities, architectural compliance, security controls, SLAs, or vendor service expectations. | Explicit requirement specifying technical baselines and performance criteria. Pre-populated by SEPTA. Proposers must NOT modify. |
| Would like to see in a demo | Indicates SEPTA's preference to see a demonstration of this capability during vendor oral presentations and software demonstration sessions. Additional details on a potential demostration agenda will be provided at a later date. SEPTA reserves the right to add additional capabilities / use cases to the demo agenda. | Pre-populated by SEPTA. Proposers must NOT modify. |
• X — Indicates SEPTA's preference to see capability demonstrated in oral presentation / demonstration Priority (Pref or Req) SEPTA's baseline priority level for the requirement:
• Req (Required): Mandatory capability required for core operational go-live.
| • Pref (Preferred): Highly desirable capability; evaluated for value-add and operational optimization. | Pre-populated by SEPTA. Proposers must address both Required and Preferred items. | |
| Solution Response Code | ||
| (Y / C / F / 3 / N) | Mandatory single compliance rating code reflecting how the proposed software solution meets the specified non-functional requirement. | Proposers MUST enter exactly ONE of the following codes for every row: |
• Y — Standard Out-of-the-Box (Supported natively in SaaS platform)
• C — Configurable (Supported via standard configuration/admin setups)
• F — Future Release (Planned roadmap feature; state committed date)
• 3 — Third-Party / Independent Software Vendor (Delivered via integrated partner tool)
• N — Not Supported / Custom (Requires custom code or unavailable)
| Module/ Solution | Identifies the specific software module, application suite component within the proposer's proposed architecture that satisfies and delivers the requirement. | Proposers must specify the exact software product, suite component, or module name providing the requested capability for each requirement line item. | |
| Customization Complexity | |||
| (H / M / L) | Estimated implementation level of effort required for requirements rated as Configurable (C), Future (F), Third-Party (3), or Custom/Not Supported (N). | Proposers must enter: |
• L — Low Complexity (Minor administrative setup)
• M — Medium Complexity (Moderate workflow/interface setup)
• H — High Complexity (Significant technical effort / custom work)
• [Blank] — Acceptable for standard Out-of-the-Box (Y) items Comments Mandatory narrative response section providing technical clarification, configuration approach, partner software name, or release timeline. Mandatory for any requirement coded C, F, 3, or N. P
• For 'C': Explain configuration effort.
• For 'F': State committed release date.
• For '3': Name 3rd-party product & integration method.
• For 'N': Describe proposed workaround, if any.
| 2. GENERAL PROPOSER INSTRUCTIONS & COMPLIANCE RULES |
| 1. Single Compliance Rating: Proposers must provide exactly ONE Solution Response Code (Y, C, F, 3, or N) per requirement row. Multiple codes or ambiguous entries will be flagged during evaluation. |
| 2. Mandatory Comments: Narrative comments are mandatory for any requirement coded as Configurable (C), Future Release (F), Third-Party (3), or Not Supported (N). Proposers must describe the configuration method, partner tool, or roadmap release. |
| 3. Sheet Integrity: Proposers must not insert, delete, or reorder rows or columns, nor modify pre-populated ReqIDs or requirement statements. |
Tech. Reqs
| SEPTA ERP Software and Implementation Services | ||||||||||
| One Response Per Requirement | Module/ Solution | Customization Complexity | Comments | |||||||
| ReqID | Main Process/Topic | Sub-Process/Topic | Requirements | Would like to see in a demo | Priority | |||||
| Pref or Req | Y | C | F | 3 | N | H / M / L | ||||
| Tech.001 | General Architecture | Total solution architectural diagrams and supportive text | The Supplier and ERP Platform Vendor shall provide complete documentation for the proposed cloud-based ERP solution, including architecture documentation, including tenancy model, cloud infrastructure, identity integration with Azure AD via SAML, environment structure (DEV, TEST, UAT, PROD), integration architecture, data storage, archival, and backup and recovery processes. Documentation must also identify network connectivity options (internet access and optional private connectivity) and alignment with SEPTA enterprise architecture standards. | Req | ||||||
| Tech.002 | General Architecture | Avoid supplier specific extensions, stored procedure triggers | SEPTA requires the solution to leverage out-of-the-box functionality and configuration capabilities of the proposed cloud-based ERP solution. Custom database procedures, triggers, or proprietary extensions are not permitted within the SaaS environment. Business logic must be implemented through the ERP solution's configuration, workflow, and standard APIs. Any extension must follow the ERP solution's approved extensibility framework (PaaS extensions, APIs, or integration services) and require SEPTA IT leadership approval. | Req | ||||||
| Tech.003 | General Architecture | Web apps complaint with W3C browser neutrality | All web-based components must comply with W3C standards and modern browser compatibility. SEPTA standard browsers are Microsoft Edge and Google Chrome. The solution must be fully compatible with the ERP solution's browser support requirements and should not require browser plugins or legacy technologies. | Req | ||||||
| Tech.004 | General Architecture | Capacity and performance | The Supplier must describe the proposed ERP solution's capacity and performance model, including transaction throughput expectations, monitoring capabilities, and performance management approach. The design should leverage the ERP solution's native monitoring, scaling, and performance management capabilities while ensuring integration with SEPTA operational monitoring processes where applicable. | Req | ||||||
| Tech.005 | General Architecture | Technologies for compatibility | The solution must align with the proposed ERP solution's technology standards, including REST/SOAP APIs, and standards-based data exchange mechanisms. Compatibility must support integration with SEPTA enterprise systems through modern API-based and middleware integration patterns. | Req | ||||||
| Tech.006 | General Architecture | Concurrently operate with other software | The proposed ERP solution must operate concurrently within SEPTA’s enterprise ecosystem and integrate with other enterprise applications such as identity management, analytics platforms, workforce systems, and operational systems. Integration must use the proposed enterprise integration platform, REST APIs, or other supported integration mechanisms, ensuring coexistence with existing enterprise platforms. | Req | ||||||
| Tech.007 | General Architecture | Dynamic mashup of data | The platform must support integration and data access between the proposed ERP solution data and SEPTA enterprise data sources. Integration should leverage APIs, the proposed enterprise integration platform, and enterprise analytics tools to support reporting and workforce management analytics without requiring direct database access to the SaaS environment. | Req | ||||||
| Tech.008 | General Architecture | Minimize network bandwidth latency | The proposed ERP solution is delivered as a SaaS platform accessed via HTTPS over the public internet. The solution must be optimized for standard enterprise connectivity and designed to minimize bandwidth and latency impacts for geographically distributed users. The Supplier should document expected network bandwidth requirements, latency tolerances, and recommended connectivity practices for SEPTA locations and remote users. | Req | ||||||
| Tech.009 | General Architecture | SEPTA Energy email addresses | The solution must support SEPTA-owned email addresses for all system-generated notifications. The platform must allow configuration of both “From” and “Reply-To” addresses and support integration with SEPTA enterprise email systems where applicable. ERP notifications must be configurable to align with SEPTA communication and identity standards. | Req | ||||||
| Tech.010 | General Architecture | Monitoring of email exchange blacklist/whitelist | The ERP platform vendor must ensure that system-generated emails originate from trusted domains and maintain appropriate reputation management to prevent blacklisting. The vendor must provide monitoring and remediation processes for email deliverability issues and support SPF, DKIM, and DMARC standards for email security and authentication. | Req | ||||||
| Tech.011 | General Architecture | Metadata and use of XML | The platform must support metadata capture, management, and export capabilities for technical, operational, and business metadata. While XML-based interchange may be supported, the solution should also support modern metadata exchange and integration standards (REST/JSON, APIs). | Req | ||||||
| Tech.012 | General Architecture | Compatibility assurance - mobile | The platform must support mobile access for Android and Apple iOS devices via native application or extensible web interface. The solution should also support browser-based access for Windows-based devices and field tablets used by SEPTA operations staff without requiring device-specific customization. | Req | ||||||
| Tech.013 | General Architecture | Same functionality across devices | Core ERP functionality should be accessible across desktop and mobile devices, recognizing that some advanced administrative functions may remain optimized for desktop access. Mobile capabilities should support common operational tasks such as approvals, notifications, and data review. | Req | ||||||
| Tech.014 | General Architecture | Conformance to Well Known and Registered port numbers | The proposed ERP solution is delivered as a SaaS platform accessed over HTTPS using standard TCP/IP ports. SEPTA will not manage application port configurations within the SaaS environment. Any required network communications must conform to standard IANA port assignments and enterprise network security policies. | Req | ||||||
| Tech.015 | General Architecture | Printer plotter compatibility | The platform should support standard enterprise printing capabilities through browser-based printing and document generation (e.g., PDF output). | Pref | ||||||
| Tech.016 | General Architecture | Standards for writing software/business components | Proposed ERP components are delivered as managed SaaS services. SEPTA expects all extensions or integrations to utilize vendor-approved extensibility frameworks, REST APIs, proposed enterprise integration platform, or PaaS extensions rather than custom platform code modifications. | Req | ||||||
| Tech.017 | General Architecture | User role reports | The platform must support role-based ad hoc reporting. Users should be able to generate reports and analytics based on their assigned roles and permissions, including user-defined fields and configured data objects. | Req | ||||||
| Tech.018 | General Architecture | Report distribution | The platform must support secure scheduling and distribution of reports, including daily, weekly, and monthly delivery. Report distribution should support secure access controls, role-based permissions, and integration with enterprise communication channels such as email or secure portal access. | Req | ||||||
| Tech.019 | General Architecture | Customer collaboration on solution roadmap and strategy | The vendor should provide a structured product roadmap engagement process, including periodic roadmap reviews, release briefings, and customer advisory programs that allow SEPTA to understand upcoming platform changes and influence long-term product direction. | Req | ||||||
| Tech.020 | General Architecture | Unlimited SEPTA specific URLs | The proposed ERP solution is accessed through standard SaaS tenant URLs. Additional application access paths should be managed through secure application routing and identity federation rather than creating multiple custom URLs. | Pref | ||||||
| Tech.021 | General Architecture | User interface code independence | The platform must follow modern SaaS application architecture principles, ensuring that the user interface layer is logically separated from core business logic and services. Extensions and integrations must use platform-supported APIs and extensibility frameworks rather than modifying core application logic. | Req | ||||||
| Tech.022 | Support | Issue/incident severity levels | Supplier incident severity definitions must align with SEPTA severity levels. Severity 1 incidents must receive immediate response and executive escalation, particularly where production service interruption or data loss occurs. | Req | ||||||
| Tech.023 | Support | SEPTA access to appropriate Supplier personnel | SEPTA must have access to designated supplier support contacts, technical specialists, and account leadership, including 24x7 escalation contacts for critical incidents. | Req | ||||||
| Tech.024 | Support | Escalation path based upon severity to Supplier Senior Management. | Supplier must provide a formal escalation process to senior management for unresolved issues or disputes impacting production operations. | Req | ||||||
| Tech.025 | Support | Escalation path based upon severity to vendor experts | Supplier must provide direct access to subject matter experts responsible for the impacted application or module during incident resolution. | Req | ||||||
| Tech.026 | Support | Change request management. | Change requests must include ROM estimates, impact assessment, implementation plan, and formal change order approval prior to execution. Supplier must provide monthly reporting of change requests and status. | Req | ||||||
| Tech.027 | Support | Known issues documentation | Supplier must maintain up-to-date documentation of known issues, including workaround, severity classification, and expected remediation timeline. | Req | ||||||
| Tech.028 | Support | Services, via an automated web interface, to triage and remedy reported issues, outages, and security vulnerabilities | Supplier must provide a web-based support portal for incident management, ticket tracking, vulnerability reporting, and status monitoring. | Req | ||||||
| Tech.029 | Disaster Recovery | Standard datacenter resiliency | Data centers hosting the ERP solution must meet industry resiliency standards equivalent to Uptime Insitute Tier III or higher, with redundancy for compute, storage, and network infrastructure. | Req | ||||||
| Tech.030 | Disaster Recovery | Geographically separated failover datacenter | The ERP solution must support geographically separated failover environments within the contiguous United States capable of sustaining production operations during a disaster scenario. | Req | ||||||
| Tech.031 | Disaster Recovery | Recovery Plans | Disaster recovery plans must be documented, reviewed annually, and tested at least annually, with remediation of identified issues. | Req | ||||||
| Tech.032 | Disaster Recovery | Support functional testing of SEPTA's Recovery Plans | The Supplier must support SEPTA disaster recovery testing activities where ERP services are involved. | Req | ||||||
| Tech.033 | Disaster Recovery | Cloud Service SaaS Solution safeguards | All SEPTA data must be protected through encryption, security controls, and access governance, and must reside within U.S.-based datacenters located in the contiguous United States. | Req | ||||||
| Tech.034 | Integration | Integration-client integration-email | Supplier must identify supported integration platforms and partner ecosystems, including the proposed enterprise integration platform and other enterprise integration technologies. | Req | ||||||
| Tech.035 | Integration | Documentation for APIs | Complete documentation must be provided for all APIs and integration services, including authentication methods and usage guidelines. | Req | ||||||
| Tech.036 | Integration | Data extraction, encryption and transmission | Data extraction and transmission must support secure APIs, encryption in transit, and controlled batch interfaces where required. | Req | ||||||
| Tech.037 | Integration | Standard data formats | The platform must support standard data exchange formats including, but not limited to, JSON, XML, and CSV. | Req | ||||||
| Tech.038 | Integration | Developer tools for integration code and configurations | Supplier must provide developer tools, integration frameworks, and knowledge transfer to enable SEPTA staff to support integrations. | Req | ||||||
| Tech.039 | Integration | Employee Interface | The platform must support event-driven data updates and near real-time integration for key workforce and organizational data objects. | Req | ||||||
| Tech.040 | Integration | Flexible integrations | The platform must support flexible integration approaches, including synchronous APIs, batch processing, and integration platform services. | Req | ||||||
| Tech.041 | Integration | Client integration - email | The solution must support integration with Microsoft Outlook / Exchange Online, which is SEPTA’s enterprise email platform. | Req | ||||||
| Tech.042 | Integration | Integration - Microsoft Word | The solution must support integration with Microsoft Office applications, including Word and Excel for document generation and reporting. | Req | ||||||
| Tech.043 | Integration | RESTful HTTP SOAP Services | The platform must support REST-based APIs as the primary integration method, with legacy SOAP services where required. | Req | ||||||
| Tech.044 | Integration | Integration with Master Data Management solutions | The platform must support integration with enterprise Master Data Management (MDM) platforms through standard APIs and data exchange mechanisms. | Req | ||||||
| Tech.045 | Configuration | Preservation of migration pathways/configurations while accommodating "emergency fix" | The Supplier must provide a controlled configuration migration and release management process that supports emergency fixes while preserving existing development work across environments. | Req | ||||||
| Tech.046 | Configuration | Environment configuration visibility | The ERP Platform Vendor must provide visibility into configuration differences across DEV, TEST, and PROD environments using ERP vendor provided configuration comparison and migration tools. | Req | ||||||
| Tech.047 | Configuration | Automated configuration object access security | Configuration access must follow role-based security controls aligned with identity federation through Azure AD / SSO. | Req | ||||||
| Tech.048 | Configuration | Automated tool for customer execution of compare reports of each object | The ERP Platform Vendor must provide tools to compare configuration objects across environments, including configuration changes, timestamps, and user modification history. | Req | ||||||
| Tech.049 | Configuration | Control/definition of release configuration by customer | SEPTA must be able to define configuration release packages including configuration objects, integrations, reports, and data definitions for controlled deployments. | Req | ||||||
| Tech.050 | Configuration | Version control/schema for SEPTA configured release | Configuration management must support version tracking of configuration releases, allowing clear identification of configuration packages deployed across environments. | Req | ||||||
| Tech.051 | Configuration | Config viewer - self-executable visibility into release and refresh info | The platform must provide self-service dashboards displaying environment versions, configuration levels, and refresh status. | Req | ||||||
| Tech.052 | Configuration | Automated configuration replace process | Configuration deployment must support automated configuration promotion and rollback capabilities aligned with ERP platform release management practices. | Req | ||||||
| Tech.053 | Configuration | Separate update environment | The ERP Platform Vendor must maintain a vendor update environment to validate quarterly SaaS updates without disrupting SEPTA development and testing activities. | Req | ||||||
| Tech.054 | Configuration | Tool that can perform "where used"� analysis - objects - config or not and all data attributes | The platform should provide tools to perform “where-used” analysis for configuration objects and data attributes across the solution. | Req | ||||||
| Tech.055 | Storage | Documentation of Infrastructure | Supplier must provide documentation describing the cloud storage infrastructure supporting the solution, including data flows, redundancy, and HA/DR capabilities. | Req | ||||||
| Tech.056 | Storage | Archive support and access | The platform must support data archiving capabilities with access controls and audit logging to ensure data integrity and immutability. | Req | ||||||
| Tech.057 | Storage | Archive/e-discovery | The ERP vendor's product must support configurable records and information management controls that enure reliable, automated, and defensible disposition according to SEPTA's practices | Req | ||||||
| Tech.058 | Storage | Optimum storage limits definitions | Supplier must publish storage limits and performance thresholds applicable to the SaaS platform. | Req | ||||||
| Tech.059 | Storage | Surpass service storage limits | Supplier must describe the process for expanding storage capacity beyond standard limits without service disruption. | Req | ||||||
| Tech.060 | Network | Network and Internet topology | Supplier must provide documentation describing network architecture and connectivity topology supporting the SaaS platform. | Req | ||||||
| Tech.061 | Network | Capacity-planning | Supplier must provide capacity planning guidance for expected transaction volumes, user populations, and future growth. | Req | ||||||
| Tech.062 | Network | Network connectivity to data centers | Supplier must describe secure connectivity between data centers supporting HA and disaster recovery. | Req | ||||||
| Tech.063 | Network | SEPTA Corporate intranet connection directly to SaaS Provider | Supplier must describe available secure connectivity options between SEPTA networks and the SaaS platform, including private connectivity options where supported. | Req | ||||||
| Tech.064 | Network | Firewall considerations and required configurations | Supplier must provide documented firewall and network configuration requirements for client connectivity. | Req | ||||||
| Tech.065 | Network | Outside of Network operational requirements | Supplier must document external connectivity requirements for integrations with third-party applications and partners. | Req | ||||||
| Tech.066 | Network | Network performance and latency tests | Supplier must conduct periodic network performance and latency testing and provide results upon request. | Req | ||||||
| Tech.067 | Network | Real-time performance-monitoring service | The platform must provide real-time performance monitoring dashboards accessible to authorized SEPTA personnel. | Req | ||||||
| Tech.068 | Testing | Testing environment and methodologies for traditional testing phases | Supplier must describe testing methodologies supporting functional, integration, regression, performance, and acceptance testing. | Req | ||||||
| Tech.069 | Testing | Acceptance testing environment | The solution must provide a production-like environment for user acceptance testing (UAT). | Req | ||||||
| Tech.070 | Testing | Testing environment clone | The platform should support environment refresh or cloning capabilities to facilitate testing activities. | Req | ||||||
| Tech.071 | Testing | Test cases for latency | Supplier's testing scenarios must include latency and performance testing across desktop and mobile access scenarios. | Req | ||||||
| Tech.072 | Testing | Testing model (as part of SaaS service) | Supplier must describe the testing responsibilities for SaaS platform updates vs. customer configuration testing. | Req | ||||||
| Tech.073 | Testing | Test tools for SEPTA regression testing | Supplier must provide tools or frameworks to support regression testing of configuration changes. | Req | ||||||
| Tech.074 | Testing | Testing tools (available to SEPTA in offering) | Supplier must identify testing tools available to SEPTA as part of the solution offering. | Req | ||||||
| Tech.075 | Usability | Configurability | The platform must support configuration of terminology, workflows, and user profiles without requiring custom code and must preserve configurations through platform upgrades. | Req | ||||||
| Tech.076 | Usability | Time-related factors | The solution must support time zones, enterprise calendars, and holiday schedules applicable to SEPTA operations. | Req | ||||||
| Tech.077 | Usability | SEPTA branding | The platform must support configuration-based branding (logos, email templates, notification headers, and report templates) consistent with SEPTA branding standards without requiring custom code changes. | Req | ||||||
| Tech.078 | Usability | SEPTA branding | The solution must provide deep links into the application compatible with SEPTA’s enterprise SSO authentication (Azure AD / Entra ID). | Req | ||||||
| Tech.079 | Usability | Context mechanism | The platform should provide clear contextual navigation (e.g., breadcrumb navigation and contextual menus) consistent with modern enterprise user interface design standards. | Pref | ||||||
| Tech.080 | Usability | Customizable end-user dashboards | The platform must support configurable dashboards and role-based home pages, allowing users to personalize views and retain preferences. | Req | ||||||
| Tech.081 | Usability | User differentiation by knowledge/skill | The platform should support role-based and skill-based user experiences, including guided workflows for new users and productivity shortcuts for experienced users. | Pref | ||||||
| Tech.082 | Usability | ADA & 508 compliance | The solution must comply with WCAG 2.1 Level AA accessibility standards and ADA Title II requirements, consistent with DOJ regulations effective April 2026. | Req | ||||||
| Tech.083 | Data Conversion | Load times report | The Supplier must provide data migration load performance reporting, including estimated load times for each data object and migration batch. | Req | ||||||
| Tech.084 | Data Conversion | Data conversion methodology for no data left behind | The Supplier must provide a data conversion validation methodology, including reconciliation controls, exception handling procedures, and audit checks to ensure data completeness. | Req | ||||||
| Tech.085 | Data Conversion | Data conversion strategy, methodology, and best practice model | The Supplier must provide a comprehensive data migration strategy, including data cleansing, mapping, transformation, validation, and cutover approach. | Req | ||||||
| Tech.086 | Data Conversion | Data conversion tools and processes description | The Supplier must describe data conversion tools, scripts, templates, reconciliation reports, and error handling procedures used for migration activities. | Req | ||||||
| Tech.087 | Data Conversion | Data conversion process approval by SEPTA | The Supplier must define the data conversion governance process, including SEPTA review checkpoints and approval prior to migration execution. | Req | ||||||
| Tech.088 | Data Conversion | Data conversion environment for SEPTA business approval of conversion | The implementation must include a dedicated data validation environment allowing SEPTA business stakeholders to review converted data prior to production deployment. | Req | ||||||
| Tech.089 | Data Conversion | Source data and target environment difference report | The Supplier must provide data comparison reports identifying differences between source data and migrated target data, including exception reporting and resolution procedures. | Req | ||||||
| Tech.090 | Data Conversion | Data transfer/convert from SEPTA to Supplier - taxonomies | The Supplier must support migration of SEPTA organizational and workforce taxonomies, including organizational structures, job classifications, and related reference data, into the target ERP data model. | Req | ||||||
| Tech.091 | Data Conversion | Support for SEPTA rule based data extraction for validating data conversion | The solution must support data extraction capabilities enabling SEPTA technical teams to perform rule-based validation and reconciliation during migration activities. | Req | ||||||
| Tech.092 | Integration | Integration with security stack | The platform must support integration with SEPTA enterprise security services, including Azure AD identity federation, SIEM integration (for security event logging), and Data Loss Prevention (DLP) controls, consistent with SEPTA cybersecurity policies. | Req |
Cybersecurity SEPTA ERP Software and Implementation Services
| One Response Per Requirement | Module/ Solution | Customization Complexity | Comments | ||||||||
| ReqID | Main Process/Topic | Sub-Process/Topic | NIST 800-53 Mapping | Requirement | Would like to see in a demo | Priority | |||||
| Pref or Req | Y | C | F | 3 | N | H / M / L | |||||
| Sec.001 | Cybersecurity | System and Communications Protection | SC-8, SC-13 | ERP Platform Vendor must document API security architecture, including encryption protocols (TLS 1.2+ or higher), authentication methods (OAuth, API tokens, SAML/OIDC), and protection against unauthorized API access. API documentation and security controls should be provided during evaluation. | Req | ||||||
| Sec.002 | Cybersecurity | System and Services Acquisition | SA-9(8) | All production environments, data storage, and backup/DR services must reside within the contiguous United States. ERP Platform Vendor must disclose hosting locations and confirm that data processing or replication outside the U.S. does not occur without SEPTA approval. | Req | ||||||
| Sec.003 | Cybersecurity | System and Communications Protection | SC-8, SC-28, AC-3 | ERP Platform Vendor must demonstrate encryption of data in transit and at rest, along with key management practices and access controls that prevent unauthorized disclosure. Security architecture and monitoring controls should be described. | Req | ||||||
| Sec.004 | Cybersecurity | Personnel Security | PS-3, SA-21 | ERP Platform Vendor and Supplier must attest that their respective employees and subcontractors with access to SEPTA systems or data undergo formal background checks consistent with national standards and appropriate training. SEPTA may require written attestation rather than full policy documentation. | Req | ||||||
| Sec.005 | Cybersecurity | System and Communications Protection | SC-4, SC-7 | ERP Platform Vendor must demonstrate logical tenant isolation ensuring separation of SEPTA data from other customers. Architecture description should address controls at application, storage, and administrative layers. | Req | ||||||
| Sec.006 | Cybersecurity | Access Control | AC-2, AC-3 | ERP Platform must support role-based access controls (RBAC) with approval workflows, notifications, and audit logging for access requests. Configuration should must support SEPTA's roles, support separation of duties, and least-privilege access. | Req | ||||||
| Sec.007 | Cybersecurity | Access Control | AC-2, AC-6(7) | ERP Platform must support periodic access reviews and automated entitlement recertification at configurable intervals (e.g., quarterly or semiannual). ERP Platform must support workflow approval and audit tracking. Supplier must configure and implement the integration that forwards the required events to SEPTA's SIEM. Specific SEPTA SIEM details will be provided under NDA. | Req | ||||||
| Sec.008 | Cybersecurity | Access Control | AC-24 | ERP Platform must support integration with enterprise identity providers and external authorization systems. Integration with SEPTA identity management architecture will be required: SAML based Single sign-on, federated with SEPTA's identify management solution. | Req | ||||||
| Sec.009 | Cybersecurity | Access Control | AC-3(7) | ERP Platform must support multi-tier RBAC including segmentation by role, function, and organizational structure. Administrative and IT support access must be separately controlled and auditable. | Req | ||||||
| Sec.010 | Cybersecurity | PII Processing and Transparency | PT-1, PT-5 | ERP Platform Vendor must provide a published privacy policy describing handling of personally identifiable information (PII). | Req | ||||||
| Sec.011 | Cybersecurity | System and Communications Protection | SC-4, AC-3 | ERP Platform Vendor must demonstrate the ability to logically partition and segregate SEPTA employee, customer, and partner data within the SaaS tenant. Controls should prevent cross-access between organizational groups and support data segmentation policies. | Req | ||||||
| Sec.012 | Cybersecurity | Access Control | AC-3(7), IA-2 | ERP Platform must support role-based and process-based identification and authorization controls, enabling enforcement of least privilege and separation of duties across application functions. | Req | ||||||
| Sec.013 | Cybersecurity | Access Control | AC-2(1) | ERP Platform must provide API-based user lifecycle management capabilities, including provisioning, modification, and deprovisioning of user accounts. Integration with enterprise identity systems is expected. | Req | ||||||
| Sec.014 | Cybersecurity | Configuration Management | CM-2(6), CM-4(1), SI-2 | Supplier must maintain a non-production environment (e.g., staging or QA) for testing application updates and patches prior to production deployment. ERP Platform Vendor should document change validation procedures and expected testing duration before promotion to production. | Req | ||||||
| Sec.015 | Cybersecurity | System and Services Acquisition | SA-3, SA-15 | ERP Platform Vendor must maintain a documented Secure Software Development Lifecycle aligned with recognized standards (e.g., NIST SP 800-218 SSDF, ISO 27034, or equivalent). Documentation may be referenced in ERP Platform Vendor's SOC 2 or security program documentation. | Req | ||||||
| Sec.016 | Cybersecurity | System and Services Acquisition | SA-11(1), SA-11(8), RA-5 | ERP Platform Vendor must perform static and dynamic application security testing as part of vulnerability management practices. ERP Platform Vendor should describe, and provide evidence of, testing frequency, remediation timelines, and whether results are validated through SOC 2 or equivalent security assessments. | Req | ||||||
| Sec.017 | Cybersecurity | System and Services Acquisition | SA-11, CA-2 | Supplier should describe security-focused quality assurance testing processes used to validate authentication, authorization, logging, and overall security architecture prior to release. | Req | ||||||
| Sec.018 | Cybersecurity | Configuration Management | CM-2(6), SA-3(1) | Supplier should maintain a staging or pre-production environment used for development and testing prior to deployment into production. | Req | ||||||
| Sec.019 | Cybersecurity | Configuration Management | CM-5(5), CM-2(6), AC-5 | Supplier must demonstrate separation of duties across development, testing, and production environments. Administrative and developer access must be restricted and auditable. | Req | ||||||
| Sec.020 | Cybersecurity | System and Communications Protection | SC-28, SC-13, CP-9(8) | ERP Platform must encrypt all data at rest, including application data, PII/PHI, metadata, backups, and logs using FIPS 140-2 or higher validated cryptographic modules or equivalent industry-standard encryption controls. | Req | ||||||
| Sec.021 | Cybersecurity | System and Communications Protection | SC-12 | ERP Platform Vendor should describe session key management practices, including key renegotiation intervals and controls used to maintain secure communication sessions. | Req | ||||||
| Sec.022 | Cybersecurity | System and Communications Protection | SC-12, IA-5(2) | ERP Platform Vendor should describe certificate lifecycle management processes, including issuance, renewal, and revocation mechanisms consistent with enterprise security practices. | Req | ||||||
| Sec.023 | Cybersecurity | System and Communications Protection | SC-8, SC-13 | ERP Platform must encrypt all data in transit using TLS 1.2 or higher (or current industry standard) with FIPS 140-2 validated cryptographic modules or equivalent security controls. | Req | ||||||
| Sec.024 | Cybersecurity | Identification and Authentication | IA-2, IA-8 | ERP Platform must support integration with enterprise Identity and Access Management solutions through standard protocols (e.g., SAML, OIDC, OAuth). Specific SEPTA IAM details will be provided under NDA for integration validation. | Req | ||||||
| Sec.025 | Cybersecurity | Audit and Accountability | AU-3 | ERP Platform must support detailed security logging including username, timestamp, transaction success/failure, source IP address, and event description. Logs must support audit, monitoring, and security incident investigation. Supplier must configure and implement the necessary integrations to deliver security and audit events to SEPTA's SIEM. | Req | ||||||
| Sec.026 | Cybersecurity | Identification and Authentication | IA-2, IA-9 | ERP Platform web services must support authentication at the user level against the system identity store or integrated enterprise identity provider. ERP Platform Vendor should document supported authentication protocols and identity federation options. | Req | ||||||
| Sec.027 | Cybersecurity | Identification and Authentication | IA-9, AC-3 | ERP Platform must support both service identity and system identity controls to enable authorization decisions at both the application and service level. ERP Platform Vendor should describe how service-to-service authentication is implemented. | Req | ||||||
| Sec.028 | Cybersecurity | Identification and Authentication | IA-5(1) | ERP Platform must support configurable password policies consistent with industry standards, including minimum length, complexity, expiration, reuse prevention, and account lockout policies. ERP Platform Vendor should describe default configurations and available administrative controls. | Req | ||||||
| Sec.029 | Cybersecurity | Access Control | AC-12 | ERP Platform must support configurable session timeout and logout capabilities to terminate inactive user sessions. Session termination should prevent reuse of session identifiers. | Req | ||||||
| Sec.030 | Cybersecurity | Identification and Authentication | IA-2, AU-3 | Authentication and authorization must occur at the individual user level. User identity must be propagated through system transactions and captured in audit logs to support traceability and accountability. | Req | ||||||
| Sec.031 | Cybersecurity | Access Control | AC-6 | ERP Platform should function across supported client systems without requiring privileged access on user devices. ERP Platform Vendor should describe supported client environments and security restrictions. | Req | ||||||
| Sec.032 | Cybersecurity | System and Communications Protection | SC-28, SI-7, AC-3 | ERP Platform must maintain the integrity and confidentiality of stored information. ERP Platform Vendor should describe mechanisms protecting data from unauthorized modification, deletion, or query manipulation, including integrity validation and access controls. | Req | ||||||
| Sec.033 | Cybersecurity | Access Control | AC-7, AU-2 | ERP Platform must log unsuccessful authentication attempts and enforce configurable account lockout thresholds. Logs must support security monitoring and incident investigation. | Req | ||||||
| Sec.034 | Cybersecurity | System and Communications Protection | SC-5, SC-7 | ERP Platform must provide protections against the Open Worldwide Application Security Project (OWASP) Top 10, including but not limited to distributed denial of service (DDoS) attacks. ERP Platform Vendor must describe protection approaches and controls, including the use of any third party services. | Req | ||||||
| Sec.035 | Cybersecurity | Identification and Authentication | IA-2, IA-8 | ERP Platform must support enterprise authentication services (e.g., Active Directory, Azure AD, SAML, OIDC). ERP Platform Vendor should describe supported identity federation protocols and authentication architecture. | Req | ||||||
| Sec.036 | Cybersecurity | Identification and Authentication | IA-5, SC-28 | Passwords and service credentials must never be displayed during authentication and must be stored using secure cryptographic hashing or encryption methods consistent with industry best practices. | Req | ||||||
| Sec.037 | Cybersecurity | System and Information Integrity | SI-12, AU-11 | ERP Platform should support electronic discovery and legal hold capabilities allowing administrators to preserve records, perform advanced searches, and export data for regulatory or legal review. | Req | ||||||
| Sec.038 | Cybersecurity | System and Information Integrity | SI-12 | Supplier must configure the ERP Platform's record retention capabilities to support SEPTA's record retention policies. | Req | ||||||
| Sec.039 | Cybersecurity | Planning | PL-2 | ERP Platform Vendor should provide documentation defining system boundaries, including architecture diagrams and security boundaries for infrastructure, application layers, and data services. | Req | ||||||
| Sec.040 | Cybersecurity | System and Information Integrity | SI-2 | ERP Platform Vendor must maintain a vulnerability management program. Critical vulnerabilities should be remediated within thirty (30) days, High within sixty (60) days, and Medium vulnerabilities within ninety (90) days. Severity must be determined using CVSS v3.1 or higher. | Req | ||||||
| Sec.041 | Cybersecurity | Access Control | AC-2 | ERP Platform must support administrative capabilities allowing authorized SEPTA personnel to manage user provisioning activities (create, modify, disable accounts and roles) through secure administrative controls or APIs. | Req | ||||||
| Sec.042 | Cybersecurity | System and Communications Protection | SC-13 | ERP Platform must use FIPS 140-2 (or higher) validated cryptographic modules for encryption of data at rest and in transit, consistent with NIST SP 800-131A cryptographic standards. | Req | ||||||
| Sec.043 | Cybersecurity | System and Communications Protection | SC-12 | Cryptographic key management must include defined key lifecycles, rotation policies, and expiration controls consistent with enterprise security practices and NIST guidance. | Req | ||||||
| Sec.044 | Cybersecurity | System and Communications Protection | SC-12 | ERP Platform must maintain the security of any encryption key until all of the information being protected is considered benign and disclosure will no longer have a potential negative impact to SEPTA. | Req | ||||||
| Sec.045 | Cybersecurity | System and Communications Protection | SC-12 | Encryption keys must be stored separately from the encrypted data and protected using secure key management mechanisms (e.g., dedicated key management services or hardware security modules). ERP Platform Vendor should describe key storage architecture. | Req | ||||||
| Sec.046 | Cybersecurity | Identification and Authentication | IA-5(1), IA-5(5), CM-6 | Default passwords must be changed prior to system deployment or initial access. Supplier should confirm that no default credentials remain active in production environments. | Req | ||||||
| Sec.047 | Cybersecurity | System and Information Integrity | SI-11, IA-6 | Authentication error responses must not reveal whether a username or password was incorrect. System responses must be generic to prevent account enumeration. | Req | ||||||
| Sec.048 | Cybersecurity | Access Control | AC-6 | ERP Platform must support granular access control mechanisms that allow administrators to grant permissions based on the principle of least privilege and configurable default access policies. | Req | ||||||
| Sec.049 | Cybersecurity | Access Control | AC-6 | ERP Platform must enforce least privilege access controls ensuring users are granted only the minimum permissions required to perform assigned responsibilities. | Req | ||||||
| Sec.050 | Cybersecurity | Access Control | AC-5, AC-6(2) | Administrative privileges must be segregated from standard user roles to support separation of duties and reduce risk of unauthorized administrative actions. | Req | ||||||
| Sec.051 | Cybersecurity | Access Control | AC-3(7), AC-5 | ERP Platform must support role definitions that enforce separation of duties, including configurable roles and permission boundaries. | Req | ||||||
| Sec.052 | Cybersecurity | Access Control | AC-6, AC-2 | Service and process accounts must not have administrative privileges unless explicitly required and approved. These accounts must not be used for interactive user access. | Req | ||||||
| Sec.053 | Cybersecurity | Access Control | AC-3, SI-7 | ERP Platform must support fine-grained data access controls to ensure users can only modify authorized data elements within the system. | Req | ||||||
| Sec.054 | Cybersecurity | Access Control | AC-3(7) | When multiple roles are assigned to a user, the effective permissions must not exceed the intended cumulative access defined by those roles. | Req | ||||||
| Sec.055 | Cybersecurity | Access Control | AC-8 | ERP Platform should have the capability to display custom login text (e.g., an acceptable use or legal warning banner) during the authentication process. | Req | ||||||
| Sec.056 | Cybersecurity | System and Services Acquisition | SA-8, CM-2 | Supplier must implement the ERP Platform without weakening existing enterprise security controls or reducing the security posture of integrated applications or systems. | Req | ||||||
| Sec.057 | Cybersecurity | Audit and Accountability | AU-2, AU-12 | ERP Platform must provide comprehensive logging of user, administrative, and system events to support operational monitoring, security investigations, and compliance reporting. Supplier must configure and implement the integration with SEPTA's SIEM as part of the implementation. | Req | ||||||
| Sec.058 | Cybersecurity | Audit and Accountability | AU-9 | ERP Platform must restrict access to audit logs to authorized personnel and protect the logs from unauthorized viewing, modification, or deletion. Supplier must configure and implement the integration that forwards designated audit events to SEPTA's SIEM. | Req | ||||||
| Sec.059 | Cybersecurity | Audit and Accountability | AU-11 | ERP Platform must support configurable audit log retention periods to meet SEPTA records retention policies and applicable regulatory requirements. | Req | ||||||
| Sec.060 | Cybersecurity | Audit and Accountability | AU-9 | Audit logs must be protected from tampering, modification, or deletion by unauthorized users. ERP Platform Vendor should describe log integrity protections. | Req | ||||||
| Sec.061 | Cybersecurity | Media Protection | MP-6, SC-4 | Temporary data storage locations (e.g., caches, file shares, transfer locations) must be automatically purged when data is no longer required. | Req | ||||||
| Sec.062 | Cybersecurity | Access Control | AC-3, SC-4 | Temporary data storage locations must enforce appropriate access controls (e.g., file system permissions, role-based access) to prevent unauthorized data access. | Req | ||||||
| Sec.063 | Cybersecurity | Access Control | AC-2(9) | Temporary data storage locations must not use shared user accounts for interactive access. All access must be attributable to individual authenticated users. | Req | ||||||
| Sec.064 | Cybersecurity | System and Information Integrity | SI-7, AU-2 | ERP Platform must provide mechanisms to detect or prevent unauthorized modification of data, including integrity validation or monitoring capabilities. | Req | ||||||
| Sec.065 | Cybersecurity | System and Communications Protection | SC-8, SI-7 | ERP Platform must support mechanisms to verify the integrity of data transferred into or out of the system, such as cryptographic checksums, signatures, or equivalent integrity validation controls. | Req | ||||||
| Sec.066 | Cybersecurity | System and Information Integrity | SI-2, SI-5 | ERP Platform Vendor must provide timely notifications regarding newly identified vulnerabilities, security advisories, and the release of security patches impacting the ERP Platform or underlying infrastructure. | Req | ||||||
| Sec.067 | Cybersecurity | Risk Assessment | RA-5, SI-5, IR-6 | ERP Platform Vendor must notify SEPTA within twenty-four (24) hours of discovery of any Critical or High severity vulnerability affecting the ERP Platform. Notification must include impact assessment and remediation timeline. | Req | ||||||
| Sec.068 | Cybersecurity | System and Services Acquisition | SA-3(2), CM-2(6) | Production data must not be replicated or used in non-production environments unless properly sanitized or anonymized. Supplier must document controls preventing exposure of production data during testing or development. | Req | ||||||
| Sec.069 | Cybersecurity | System and Services Acquisition | SA-9(5), CP-2 | ERP Platform Vendor must document scenarios where data may be relocated between physical environments (e.g., failover, disaster recovery, or replication). SEPTA must be informed of such processes. | Req | ||||||
| Sec.070 | Cybersecurity | Identification and Authentication | IA-5(1), SC-28 | Passwords must be protected using secure cryptographic hashing and never stored in plaintext. ERP Platform Vendor must document hashing algorithms and password protection methods. For users authenticated through SEPTA's federated identity solution, ERP Platform must not require the user's password. | Req | ||||||
| Sec.071 | Cybersecurity | Access Control | AC-2 | ERP Platform must allow authorized SEPTA personnel to perform security administration functions, including account management, access controls, and privilege assignments. | Req |
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 .