RFP 17-099Implementation Services for SAP Success Factors Module Integration
Attachment F, Technical Proposal Template
Instructions:Please include responses to the questions in the shaded fields of this attachment and reference any supplemental attachments provided.
Respondent’s Name:
2.4.1 EXECUTIVE SUMMARY:
Please provide a high level overview of the organization, value proposition, engagement approach, project methodology, and
solution architecture.
2.4.2 COMPANY OVERVIEW:
2.4.2.1Please describe the overall structure of your service organization, and your vision for this potential partnership with Indiana’s
State Personnel Department.
2.4.2.2How does your company keep current with products and technology?
2.4.2.3Describe the company’s level and type of certifications with each of the following: Oracle, PeopleSoft, the recommended middleware solution, and SAP SuccessFactors HCM.
2.4.3 RELEVANT EXPERIENCE:
2.4.3.1Describe no more than three (3) engagements where your company has successfully integrated PeopleSoft 9.1 with
SuccessFactors. In at least one of these engagements, your company must be the Lead or Prime vendor. Previous
governmental experience is important. May we contact these clients and talk with them about their experience?
2.4.3.2Describe your company’s experience working with enterprise-wide solutions for entities with more than 30,000 employees or that solicit over 100,000 job applicants each year.
2.4.3.3Describe your company’s recent experience with recruiting modules, and please highlight any experience you have with successfully configuring SAP SuccessFactors.
2.4.3.4Describe your company’s recent experience with performance management modules, and please highlight any experience you have with successfully configuring SAP SuccessFactors.
2.4.3.5Describe any reusable integrations, configuration templates or existing add-ons that your company can bring to this engagement to implement your proposed solution, and please include any time anticipated to be saved by the existence of these items.
2.4.3.6Describe the largest hurdles your company has had to overcome with this type of project and how your company has successfully addressed them in the past.
2.4.4SOLUTION – VISION AND STRATEGY:
The purpose of this section is to capture the high level solution envisioned when preparing the proposed team structure and budget.
2.4.4.1. SOLUTION – OVERALL APPLICATION ARCHITECTURE:
2.4.4.1.1APPLICATION ARCHITECTURE: Explain how you would arrive at your recommendation on which business
functions would remain in PeopleSoft HCM, and which should move to the new SAP SuccessFactors platform.
2.4.4.1.2MODULE INTER-DEPENDENCIES: Explain the inter-dependencies between the SAP SuccessFactors modules to be implemented, and associatedroadmap implications for the SAP SuccessFactors/PeopleSoft Rollout.
2.4.4.1.3EMPLOYEE CREATION: What options will SPD have for determining the points in the process when the Employee ID is created in PeopleSoft HCM?
2.4.4.1.4APPLICATION SECURITY: Describe the security framework of your proposed integration solution.
2.4.4.1.5STATE EMPLOYEE - ACTIVE DIRECTORY INTEGRATION: Describe how these software products can be implemented and integrated with the state’s Active Directory framework.
2.4.4.1.6APPLICANT – AZURE B2C INTEGRATION: Describe how these software products can leverage the existing Azure B2C Authentication to enable access for Applicants.
2.4.4.1.7SINGLE SIGN ON: What would be required to allow for a single sign-on for PeopleSoft, SuccessFactors, and the proposed integration solution?
2.4.4.1.8SOLUTION INFRASTRUCTURE: What infrastructure is required to run and maintain the proposed solution?
2.4.4.1.9RSS FEED SUPPORT: What is needed to accommodate the utilization of RSS feeds in the proposed integration solution?
2.4.4.1.10JOB BOARD INTEGRATIONS: How would the architecture handle integrations with the top job boards, in a way that can be modified to utilize different job boards and/or vendors in the future?
2.4.4.1.11GENERAL SOLUTION SECURITY CONSIDERATIONS: Describe the considerations for, and actions required to, ensure that the combined solution can work with network firewalls, internet filtering and antivirus software.
2.4.4.2. INITIAL SOLUTION – INTEGRATION STRATEGY:
2.4.4.2.1INTEGRATION ARCHITECTURE: Describe your company’s proposed solution for integrating PeopleSoft HCM 9.1 with SAP SuccessFactors to support data required for Jam, Recruiting, Onboarding, Goals and Performance and Succession Planning.
2.4.4.2.2TECHNOLOGY OPTIONS: What are the current industry “best practice” options for this integration?
2.4.4.2.3USER INTEGRATION: How will HR data transfer for user account sync between PeopleSoft and SuccessFactors be implemented, in order to automatically provision roles?
2.4.4.2.4SYSTEM OF RECORD DETERMINATION: Describe the process to determine which data moves into each system under your proposed solution. Please provide your best practice assumptions regarding the system of record for the key data entities managed by the recruiting and onboarding business processes. The state desires that PeopleSoft continue to be the State’s ultimate system of record for essential employee data.
2.4.4.2.5INTEGRATION POINTS:During what process steps would you expect to initiate the transfer of data from PeopleSoft to SuccessFactors, and vice-versa, under your proposed solution?
2.4.4.2.6INTEGRATION LIMITATIONS: Are there any limitations to what can be integrated with your proposed approach?
2.4.4.2.7DATA ENCRYPTION: Describe the encryption capabilities of your proposed integration solution, both at rest and in motion.
2.4.4.2.8TECHNOLOGY RECOMMENDATION: What middleware software will your proposed solution utilize to facilitate data transfer between PeopleSoft and SuccessFactors, and vice-versa?
2.4.4.2.9TECHNOLOGY RATIONALE: Present the pros and cons of using middleware software in this particular integration such as SAP’s Hana Cloud Integration (HCI), Dell’s Boomi, Microsoft’s Biz Talk, and your recommended solution.
2.4.4.2.10MIDDLEWARE MAINTENANCE: Describe how middleware software updates will need to be implemented and the amount/complexity of any development required to properly implement those updates.
2.4.4.2.11REAL TIME UPDATES: What level of support does your proposed solution offer for API’s and web services to be utilized in the data interchange?
2.4.4.2.12PEOPLESOFT UPGRADE COMPATIBILITY: Describe how the proposed integration solution would need to be changed to make it compatible with PeopleSoft 9.2 HCM.
2.4.4.2.13SECURITY – DATA TRANSFER: Describe the security around importing and exporting files using built-in tools in the proposed integration solution.
2.4.4.2.14SECURITY – MIDDLEWARE SOLUTION: Describe the types of security protocols supported by your proposed integration solution.
2.4.4.2.15INTEGRATION MONITORING: Describe the monitoring that the proposed solution will require. What reporting tools are there to assist with the diagnosis of any breakdown in the integration processes?
2.4.4.2.16SUPPORT FOR MULTIPLE ENVIRONMENTS: Describe how the proposed integration solution will need to be modified or replicated to enable integration between non-production environments. How many non-production environments can besupported?
2.4.4.2.17TECHNICAL ARCHITECTURE REQUIREMENTS: Describe any technical architecture requirements and/or operating systems limitations of the proposed integration solution.
2.4.5ENGAGEMENT MANAGEMENT AND TEAM STRUCTURE
2.4.5.1 IMPLEMENTATION PARTNER TEAM STRUCTURE: Describe the structure of the implementation team your company would
provide, and a brief biography including the background and experience of any key participants who will serve as a decision
facilitator, advisory consultant, lead functional, and lead technical consultants. Please include your current rate
card by role.
2.4.5.2STATE TEAM STRUCTURE: Describe the optimal configuration of the team the State should provide for your proposed team structure and solution to be successful.
2.4.5.3PROJECT MANAGEMENT COORDINATION: Describe how your company will interact with SPD’s project manager throughout the project.
2.4.5.4STATE RESOURCE INVOLVEMENT: Describe how you would include the SPD HRMS analysts during design and solution configuration, and the State project developers in the design and build of data interfaces and data migration.
2.4.5.5ITERATION / AGILITY: Describe any expectations your company would like to set around the potentially iterative nature of your proposed methodology.
2.4.5.6RELEASE MANAGEMENT: If agile development efforts are to be used, describe the release management strategy and supporting documentation. Please include estimated duration of sprints, requirements documentation, and communication of the scope and changes to be implemented with each release.
2.4.5.7SCOPE / CHANGE MANAGEMENT: Describe the change management approach that would be implemented in order to deliver the intended business value while also managing scope.
2.4.5.8ISSUE RESOLUTION: What is the company’s standard issue resolution process?
2.4.5.9STATUS REPORTING: Describe the standard status reports to be provided and typical frequency.
2.4.5.10DELIVERABLES: Provide a list of the deliverables that will be generated, reviewed and approved during the course of the project.
2.4.6 ENGAGEMENT METHODOLOGY:
2.4.6.1 METHODOLOGY - BEST PRACTICE PROCESSES
2.4.6.1.1 Describe how your consultants will leverage your company’s solution expertise to ensure that the initiative implements “best practice” processes and maximizes the value recognized by the implementation.
2.4.6.2 REQUIREMENTS & DESIGN:
2.4.6.2.1 Describe how your company will participate in and potentially lead requirements gathering and confirm that
all necessary requirements are understood by all parties involved. Please include the type of requirements
documentation that will be created, and how requirements traceability will be managed.
2.4.6.2.2 Describe how your company will participate in and potentially lead fit/gap discussions.
2.4.6.3METHODOLOGY - CONFIGURATION:
2.4.6.3.1 Describe how your consultants will complete the configuration of the SAP SuccessFactors Test and Production
environments.
2.4.6.3.2 Describe how your consultants will engage SPD analysts in the configuration effort throughout all phases of the
project.
2.4.6.4 METHODOLOGY - INTEGRATION & DATA MIGRATION:
2.4.6.4.1Based on your company’s previous experience, what data clean-up should be done in PeopleSoft to prepare for
this integration?
2.4.6.4.2 Describe the process to develop integrations with the top recruiting job boards.
2.4.6.4.3 Describe the process to develop integrations with the IN.GOV internet site, and agency specific sites.
2.4.6.4.4 What do you see as your typical role in the data conversion process? Describe your level of involvement in
planning and guiding the data conversion activities during the project (including planning, mapping, and executing
theconversion runs) and confirming that the data conversion is complete and accurate.
2.4.6.4.5Describe the documentation that will be provided or available to the State technology staff who will
support the integrations once the engagement is completed.
2.4.6.5 METHODOLOGY - SOLUTION TESTING:
2.4.6.5.1Describe how your company will support testing for the implemented modules and proposed integrations.
2.4.6.5.2How will data be staged to test the proposed solution?
2.4.6.5.3How will test plans and test scripts be produced?
2.4.6.5.4How will test results be monitored and evaluated?
2.4.6.5.5What type of teams should be involved with testing, and what is the suggested number on each team?
2.4.6.5.6Describe the process for defect management: including planning, communication, prioritization, and retest windows.
2.4.6.6 METHODOLOGY – PRODUCTION IMPLEMENTATION AND WARRANTY SUPPORT:
2.4.6.6.1 Do you recommend a “Big Bang” approach be applied when implementing each of the SuccessFactors modules, or
do you prefer an alternative approach, such as a phased-in approach by agency, etc?
2.4.6.6.2What level of expertise and guidance can the state expect for implementation planning as well as execution during implementation weekends?
2.4.6.6.3Describe how your company will provide “Go Live” support and through what time period?
2.4.6.7METHODOLOGY – TRAINING
2.4.6.7.1 What is your strategy for Training? Please include the timing and methods of training would be employed (CBT,
help guides, instructor-led, online help via the application, train-the-trainer, etc.), and why that methodology
would be used.
2.4.6.7.2Please define the technology that would be used to create the training materials so that the state knows if the CBT’s are easily supported.
2.4.6.7.3 What reusable training materials will the State receive at the end of the project, and will those materials be owned by the State?
2.4.6.8METHODOLOGY – KNOWLEDGE TRANSFER AND OPERATIONAL TRANSITION
2.4.6.8.1If your solution is chosen, what support will SPD require after the proposed solution is implemented?
2.4.6.8.2 What steps will the vendor take to orient and familiarize Stateproject staff with the SAP SuccessFactors modules
priorto implementation?
2.4.6.8.3 Once SuccessFactors is implemented, what contingency plans are there if there are any interface solution outages?
2.4.6.8.4 How will SPD and other state support agents be trained on supporting the proposed integration solution?
2.4.6.8.5What are the different levels and models of support and maintenance for any hardware and/or software
that are necessary in your proposed integration solution?
2.4.6.8.6 What emergency support is available for your proposed integration solution?
2.4.6.8.7Are daily and emergency support on-shore or off-shore?
2.4.6.8.8 If you were to be engaged to provide configuration and/or provisioning support after the warranty period, please describe the support model that would be employed including the process the State would follow to obtain resources.
2.4.7TIMELINE:
2.4.7.1 Describe at a high level how this engagement will unfold, including major milestones and an approximation of when
they would be completed assuming a June 1 start date. Please disclose any important assumptions that underlie the
timeline.
2.4.8OTHER RELEVANT INFORMATION:
2.4.8.1 What else would you like us to know about your proposed solution or this engagement that has not been specifically
addressed in the questions above?
RFP17-099 Technical Proposal, Page 1 of 7