1. Strategy Session(s) NY MTA Bus
1.1. Strategy Session Agenda
1.1.1. A. RFP Overview
1.1.1.1. Key Dates
1.1.1.1.1. RFP Issuance: December 16, 2024
1.1.1.1.2. Pre-Proposal Conference: January 8, 2025, at 1:00 PM Eastern Time
1.1.1.1.3. Deadline for Written Questions: January 10, 2025
1.1.1.1.4. Proposal Submission Deadline: January 24, 2025, at 3:00 PM Eastern Time
1.1.1.1.5. Potential Oral Presentations: Week of January 27, 2025
1.1.1.1.6. Anticipated Contract Start Date: On or about February 15, 2025
1.1.1.2. Submission Requirements
1.1.1.2.1. Proposals must be submitted electronically through the Conductiv portal by January 24, 2025, at 3:00 PM Eastern Time.
1.1.1.2.2. Prospective proposers must sign and return a Confidentiality and Non-Disclosure Agreement (NDA) before receiving access to the RFP documents.
1.1.1.2.3. The technical proposal should not exceed ten pages, excluding attachments and appendices.
1.1.1.2.4. Oral presentations may be required for some proposers.
1.1.1.2.5. Cost proposals must be submitted in a separate file from the technical proposal
1.1.1.2.6. 5 References
1.1.1.2.7. Resumes and references for individuals
1.1.1.3. Project Overview
1.1.1.3.1. Scope
1.1.1.3.2. Key Requirements and Challenges
1.1.1.4. Evaluation Criteria
1.1.1.4.1. Public Sector Experience and Knowledge -25 pointa
1.1.1.4.2. Technical Evaluation - 30 points
1.1.1.4.3. Enterprise Asset Management Integration - 30 points
1.1.1.4.4. Cost Evaluation - 5 points
1.1.1.4.5. Diversity Practice - 10
1.1.2. B. Win Theme Development
1.1.2.1. Bus knowledge & experience
1.1.2.1.1. Team Trained on PS bus implementations
1.1.2.1.2. lowest risk strategy
1.1.2.1.3. VMRS experience
1.1.2.1.4. Configuration Catalysts
1.1.2.1.5. Alignment with NTD and TAM Plans
1.1.2.1.6. Transit User Community / EAMinded Transit
1.1.2.2. Spear Experience
1.1.2.2.1. SFMTA
1.1.2.2.2. KCATA
1.1.2.2.3. LA Metro
1.1.2.3. Transit / Public Sector Focused
1.1.2.3.1. Hexagon Outstanding Public Sector Partner
1.1.2.3.2. Understand financials / integration/ workflow implication in public sector
1.1.2.3.3. Represented labor requirements
1.1.2.3.4. Public sector approach that considers public sector pace
1.1.2.3.5. Security & Privacy requirements
1.1.2.3.6. Standards Based
1.1.2.4. Integration Experience
1.1.2.4.1. GIS - for transit
1.1.2.4.2. Fleetwatch
1.1.2.4.3. OpenCAD IPC - transit agencies
1.1.2.4.4. ERP
1.1.3. C. Competitive Analysis
1.1.3.1. Accenture
1.1.3.1.1. Untitled
1.1.3.2. KPMG ?
1.1.3.2.1. Stratum
1.1.3.2.2. Strengths
1.1.3.2.3. Weaknesss
1.1.3.2.4. Themes
1.1.3.3. Guidehouse
1.1.3.3.1. EAM Solutions
1.1.3.3.2. Strengths
1.1.3.3.3. Weaknesses
1.1.3.3.4. Themes
1.1.3.4. EY
1.1.3.5. Stratum
1.1.3.5.1. No bench strength
1.1.3.6. EAM Solutions
1.1.3.6.1. No bench strength
1.1.4. F. Risk Assessment and Mitigation
1.1.4.1. - Identify potential project risks and mitigation strategies
1.1.4.2. Incorporate risk management into the proposal
1.1.5. G. Compliance Matrix
1.1.5.1. Sales team will create a compliance matrix to ensure all RFP requirements are addressed
1.1.6. H. Proposal Development Strategy
1.1.6.1. 1. . Strategy Session(s)
1.1.6.2. 2. High-level Story-boarding (main proposal flow and outline)
1.1.6.3. 3. Assign section owners and deadlines[
1.1.6.4. 4. Detailed Storyboarding Session
1.1.6.4.1. Each section lead will walk through a storyboard or outline of how they intend to produce their section
1.1.6.4.2. Identify where specific win themes will be emphasized
1.1.6.4.3. - Brainstorm potential graphics to support win themes and technical solution
1.1.6.4.4. Section leads collect feedback on storyboard. Group collecttively decides if we are ready to move forward to content development
1.1.6.4.5. Develop a comprehensive proposal outline/storyboard fof each section based upon RFP requirements
1.1.6.5. 5. Black review
1.1.6.5.1. Including Project Plan
1.1.6.6. 6.Red Review
1.1.6.6.1. Can be more than 1
1.1.6.7. 7. Green review (final green review here. Initial green reviews conducted previously)
1.1.6.8. 8. White Glove
1.1.6.9. 9 Submit
1.1.6.10. Untitled
2. Detailed Storyboards
2.1. Section 5, Proposer's Qualifications, Storyboard
2.1.1. I. Introduction
2.1.1.1. Briefly introduce 21Tech and its commitment to providing a robust and qualified team for the MTA's EAM project.
2.1.1.2. State that 21Tech's qualifications directly address the MTA's evaluation criteria and are based on the firm's "Win Themes".
2.1.1.3. Highlight that this response will focus on how 21Tech's qualifications align with the evaluation criteria specified by the MTA.
2.1.2. II. Public Sector Experience and Knowledge
2.1.2.1. Theme: Transit / Public Sector Focused: Emphasize 21Tech's dedication to the public sector and its understanding of the unique challenges of public transit agencies.
2.1.2.2. Theme: Bus knowledge & experience: Underscore 21Tech's expertise in bus operations and maintenance, directly addressing the need for experience in large public bus transit system
2.1.2.2.1. Mention RapidTAM in some form
2.1.2.2.2. Configuration Catalysts
2.1.2.2.3. Emphasize 10+ years working in large public sector transit systems
2.1.2.3. Theme: Team Trained on PS bus implementations: Highlight that 21Tech's team is specifically trained on public sector bus implementations, and that they have deep experience with the issues that the MTA faces
2.1.2.4. Theme: SFMTA, KCATA, LA Metro: Cite experience with specific large public transit systems like SFMTA, KCATA, and LA Metro, fulfilling the requirement for demonstrating successful Spear to Hexagon EAM implementations.
2.1.2.4.1. Mention that 21Tech has successfully implemented Spear to Hexagon EAM in two or more large public bus systems
2.1.2.4.2. Can we say more than anyone else ?
2.1.2.5. Theme: Transit User Community / EAMinded Transit: Showcase 21Tech's knowledge of the transit user community and its focus on EAM-minded transit.
2.1.3. III. Technical Evaluation
2.1.3.1. Theme: Understand setup of EAM processes and systems involves all transit asset classes
2.1.3.1.1. Rolling Stock, including Revene Vehicles and Service Vehicles
2.1.3.1.2. Equipment
2.1.3.1.3. Facilities
2.1.3.1.4. Infrastructure
2.1.3.1.5. Sample/Snapshop of hierarchies ?
2.1.3.2. Theme: Configuration Catalysts: Position 21Tech as experts in system configuration, setup of assets for non-revenue vehicles, facilities, bus equipment, and subcontractor equipmen
2.1.3.3. Theme: VMRS experience: Stress 21Tech's experience with Vehicle Maintenance Reporting Standards (VMRS), demonstrating the ability to configure assets properly
2.1.3.3.1. Mention OCM challenge of moving from pure VMRS code based to the depth of data available through hierarchy-based, and our experience balancing those
2.1.3.4. Theme: Represented labor requirements: Emphasize 21Tech's experience in understanding and addressing labor challenges and change management, which is important for implementing preventative maintenance programs and handling warranty issues.
2.1.3.4.1. Mention the knowledge of preventive maintenance programs, warranty conditions, claims generation, and processing of payments (not only for warranties, but for accident claims)
2.1.3.5. Theme: Spear Experience: Highlight 21Tech's familiarity with the existing Spear system, enabling smooth integration and migration to Hexagon EAM.
2.1.3.5.1. Mention experience integrating or migrating configurations of assets from Spear
2.1.3.5.2. Did we do temporary Spear integrations for MTA ?
2.1.3.6. Scope of Work Compliance
2.1.3.6.1. Cross reference project approach alignment with scope of work
2.1.3.7. PSA Compliance
2.1.3.7.1. Can we note no or limited exceptions ?
2.1.3.8. Theme: Security & Privacy requirements: Note the team's understanding of security and privacy requirements, and adherence to the MTA's Cybersecurity Requirements
2.1.3.8.1. Tell a liittle of of our experience
2.1.4. IV. EAM Integration
2.1.4.1. Theme: Integration Experience: Highlight 21Tech's ability to integrate systems and upload data from various systems used at NYCT, DOB, SFS, and Facilities while maintaining links to historical data
2.1.4.1.1. Demonstrate how through our many implementations we bring public sector bus transit industry best practices, workflow, techniques, methods, and processes for buses, facilities, and non-revenue assets
2.1.4.2. Transit Ecosystem knowledge
2.1.4.2.1. Ecosystem message from OCTA bid
2.1.4.2.2. Transit business architecture diagram ?
2.1.4.3. Theme: Fleetwatch: Emphasize 21Tech's experience with Fleetwatch, the MTA's fuel management system
2.1.4.3.1. VIA
2.1.4.3.2. SFMTA
2.1.4.3.3. KCATA
2.1.4.4. Mention experience in providing complete project plans, including system design, setup and configuration of Hexagon EAM for work scheduling, timekeeping, unscheduled work planning, scheduled work planning, workforce picks, material and inventory, fuel management, and tracking location of equipment in real tim
2.1.4.4.1. Examples of flows or diagrams for these
2.1.4.5. Theme: GIS - for transit: Highlight expertise in GIS for transit, demonstrating the capability to handle complex data management and visualization tasks
2.1.4.5.1. Can we mention some of the recent challenges in versions between ESRI and EAM (features not supported that helped overcome)
2.1.4.5.2. Route cleaning
2.1.4.6. Theme: OpenCAD IPC - transit agencies: Note experience with OpenCAD IPC for transit agencies, and the ability to integrate with other systems used at the MTA
2.1.4.6.1. VIA
2.1.4.6.2. BCRTC
2.1.4.6.3. Stress our understand of the workflow and also the tool's limitations (data, structured PDFs, etc)
2.1.5. V. Cost Evaluation
2.1.5.1. Theme: Understand financials budgeting and processing in public sector
2.1.5.2. State costs will be provided in a clear and itemized manner
2.1.5.3. Mention discounts and other savings benefits will be proposed where appicable as SOWs are developed
2.1.5.4. Theme: Minimize dependence on sub-contractors
2.1.5.4.1. We are the prime and the delivery arm
2.1.5.4.2. Controls costs and quality of work
2.1.6. VI. Diversity Practice
2.1.6.1. Briefly mention that 21Tech is committed to diversity practices and has completed the Diversity Practices Questionnaire
2.1.7. VII. Conclusion
2.1.7.1. Reiterate 21Tech's strong qualifications based on the win themes and their direct relevance to the MTA’s evaluation criteria.
2.1.7.2. Express confidence in 21Tech’s ability to successfully deliver the project based on its experience, expertise, and alignment with the MTA's goals and needs
2.1.7.3. Itemize win themes in a call-out box ?