Rev. 7-25-18

1

AMENDMENT - REQUEST FOR PROPOSAL (RFP)

Amendment No.

002 RFP No.

4019000008 Project Name

SAP HANA IMPLEMENTATION SERVICES

COMPANY NAME AND ADDRESS (To be completed by Bidder)

Issued By METROPOLITAN TRANSIT AUTHORITY Procurement Division 1900 Main Street Houston, Texas 77002

Issue Date:

11/30/2018

The hour and date specified for receipt of Proposals is:

[ X ] Not extended

The RFP is amended as follows:

1. Page x, Paragraph S.4.i) is revised as follows:

i) Be a participant in SAP’s PartnerEdge Program.

2. Page 32, “SCOPE OF SERVICES”, section 2.1 “Methodology” is revised as follows:

2.1 Methodology

The Contractor shall have a methodology that either adopts, mimics, or supplements Industry Best Practices, developed by SAP, or a framework for Migration to HANA running on SUSE Linux.

3. Please see the attached Questions and Answers. Several answers refer to the “HANA Files” attachment posted to our SAP system and our external web site.

Except as provided herein, all instructions and provisions of the RFP, as heretofore changed, remain unchanged and in full force and effect.

Proposers must acknowledge receipt of the amendment prior to the hour and date specified for proposal delivery, by one of the following methods:

1. By acknowledging receipt of this amendment on the Proposal form; 2. By signing and returning one (1) copy of this amendment with your Proposal; 3. By separate letter acknowledging receipt.

FAILURE TO ACKNOWLEDGE RECEIPT MAY CAUSE FOR PROPOSAL REJECTION BY METRO.

PROPOSER (Authorized Representative)

BY NAME: _________________________________________________ SIGNATURE: _______________________________________________ TITLE: ____________________________________________________ SIGNATURE DATE: _________________________________________

METROPOLITAN TRANSIT AUTHORITY (Authorized Representative)

BY NAME: Alan Scanio SIGNATURE: //Signed// TITLE: Sup. Contract Spec.

Rev. 7-25-18

2

Project Name: SAP HANA Implementation

Solicitation #: 4019000008

Contract Administrator: Alan Scanio

Proposer Qualification Questions

Q1: Why Metro is looking for only SAP Certified Upgrade Partner when HANA Database migration, Technical Upgrade etc. are basic services which can be performed by any Authorized SAP Partner.

A1: Per METRO's SAP Account Executive, SAP has a program called PartnerEdge. METRO requires that the proposed vendor be a participant in this program. It is METRO's understanding that participants of this program receive top level support from SAP, and we believe this support will help ensure a successful project.

Q2: SAP Certified Upgrade Partner does not exist. Please provided the correct certification name.

A2: Per METRO's SAP Account Executive, SAP has a program called PartnerEdge. METRO requires that the proposed vendor be a participant in this program. It is METRO's understanding that participants of this program receive top level support from SAP, and we believe this support will help ensure a successful project.

Q3: Reg. SAP Certified Migration Partner: We checked with SAP and they stated that they are not aware of such partnership types. As discussed yesterday, we kindly request you to amend it probably like, “An Authorized SAP Partner” thereby giving confidence to Metro that it would get necessary support when needed. We would also like to bring it to your kind notice that SAP support to Metro is directly related to the level of Support it has signed for with SAP like – SAP Standard Support, SAP Product Support for Large Enterprise, MaxAttention & SAP ActiveEmbedded.

A3: Per METRO's SAP Account Executive, SAP has a program called PartnerEdge. METRO requires that the proposed vendor be a participant in this program. It is METRO's understanding that participants of this program receive top level support from SAP, and we believe this support will help ensure a successful project.

Q4: Does it satisfy Metro if actual SAP Consultants who would be performing the migration is Certified or has considerable experience performing such migrations ?

A4: The HANA database certification is certainly something METRO will be interested to see in the proposal, but the PartnerEdge program participation is required.

Q5: SAP does not require or has a HANA certification for HANA (DMO option). Do you just need a HANA Database certified Consultant for the installation of the Database? And Hana experienced developer. Certifications are normally reserved for S/4 Hana.

A5: The HANA database certification is certainly something METRO will be interested to see in the proposal, but the PartnerEdge program participation is required.

Q6: SAP HANA was introduced only in late 2011 and expecting a firm to have a minimum 5 years’ experience looks very unfair and unaccommodating to other eligible SAP Partners.

A6: Our market research with our SAP representative indicated that multiple firms exist with this many years of experience. We believe this amount of experience is important to ensure a successful project.

SOLICITATION QUESTIONS & ANSWERS

Rev. 7-25-18

3

Schedule Questions

Q7: We would like to request an extension for the RFP Response Due Date. Would it be possible to extend the due date by 30 days, i.e. to the end of December?

A7: An extension of one week until December 7, 2018 was issued.

Q8: In order to submit a credible and competitive proposal we hereby request an extension, to the submission date, of at least a week to 10 days.

A8: An extension of one week until December 7, 2018 was issued.

Q9: In previous/similar projects, how much UAT testing time did you provide?

A9: Approximately 3 weeks

Q10: What is the eta for the new hardware to be operational? Could you share the hardware specifications?

A10: The hardware should be operational in either February or March 2019

Q11: When is the estimated start date?

A11: We are targeting May, 2019

Q12: What is the target start date for the Migration project?

A12: We are targeting May, 2019

Q13: Are there any dates that we should plan around, for example busy periods or conflicting projects?

A13: The core of the project is expected to run through the summer of 2019. There may be some vacations, but should not be an impact. METRO's fiscal year end close is on September 30, 2019. The go-live will need to take place just after this date, possibly during October or November 2019.

Labor Rate Questions

Q14: p. 26: Pls. advise how Metro had come up with such a project team composition and team effort hours.

A14: The labor categories descriptions are identical to those found in SAP's publicly available GSA schedule. The hours are estimates based upon METRO's available budget, and what we think the most likely labor mix would be.

Q15: p. 26: Pls. identify if Metro’s technical team has already discussed with any potential vendor who has proposed such a team and effort estimates ? Has any such discussions / assessment study made already ? 3. If Yes, Is the company which did assessment/ discussions with Metro team participating in this opportunity ?

A15: The Contractor's implementation team is not required to have each of these labor categories represented, the implementation work is reimbursed on a fixed price basis. However, we require the Contractor to provide these labor categories if needed for unforeseen work related to the HANA implementation.

Q16: p. 26: What is the purpose of section 3 – Page 26. We feel for a SAP HANA Database migration, there is absolutely no need for a 14 member team, even a 10 member team is too high.

A16: The Contractor's implementation team is not required to have each of these labor categories represented, the implementation work is reimbursed on a fixed price basis. However, we require the Contractor to provide these labor categories if needed for unforeseen work related to the HANA implementation.

Q17: p. 26: Assuming that Metro operates only in US Central Time zone - would appreciate if Metro can explain the need for an offshore consultant when an exact role is present Onsite ?

A17: We require the Contractor to provide these labor categories if needed for unforeseen work related to the HANA implementation. Since the work is unforeseen, we are allowing an offshore resource to be billed under the contract if the need arises.

Rev. 7-25-18

4

Q18: p. 26: On one hand Metro expects a company to have at a minimum of 5 years’ experience but per Position Description it is satisfied with consultants who have much lesser experience. For example: a. Jr. Technical Support Engineer who has a minimum of just two weeks of SAP Training or three months in the role. b. Technical Support Engineer I: Two years of general experience with two to four weeks of applicable SAP training or three to six months experience in the role with an SAP proficiency of Low to Medium c. Technical Support Engineer II: Three years of general experience with four or more weeks of applicable SAP training (possible training in different modules or toolsets) and twelve months experience in the role (may have experience in more than one SAP implementation) with an SAP proficiency of Medium. d. Lead Technical Support Engineer, Project Implementation Manager, Implementation Specialist Three to six years of general experience (could have extensive industry experience) with significant SAP training (training in different modules or toolsets). Three to five years’ experience in the role (may have experience in more than one SAP implementation, possible project management experience, platinum SAP experience possible, and possible mastery of SAP architecture/functional core competencies and a recognized expert in more than one area while being a resource to other consultants in all defined areas of expertise) with an SAP proficiency of High.

A18: This experience requirement applies to the proposer, not to its personnel.

Q19: p. 27: Though it is stated that the quantities appearing are estimated quantities, we are trying to understand the reasoning behind putting exact role & their estimated effort in hours ? If Metro’s intention was only to provide a sample, it could have chosen round off numbers like 30, 50 or 100 hours Why and how did Metro choose estimate like 92, 83, 48, 142 ?

A19: The roles are listed so that proposers can provide an offer for these labor categories in the event they are needed during the Period of Performance. The quantities are METRO's estimate.

Q20: Are all vendors expected to quote for all the team members proposed with the hours per section 3 – Solicitation / Contract amount, items & prices? For example: what if we feel there is no need for an Global Support Manager and Sr. Director and perhaps need a SAP QA tester or a SAP Trainer / OCM Consultant.

A20: The Contractor will be expected to provide these services if necessary, and METRO will reimburse them at the hourly rate listed in the resultant Contract.

Q21: In-case Metro has allocated a budget based on previous estimated hours, what would happen if the number of proposed labor hours varied by more than 100 percent ?

A21: The Contractor shall not incur charges against the Contract in excess of the total Contract amount.

Technical Questions

Q22: Are you Unicode converted in all current SAP ECC, BW and SRM systems?

A22: Yes

Q23: Can you provide output of SCI (Code inspector) to assess level of customizations?

A23: Please refer to the provided files from Procurement

Q24: Can you provide the current sizes of the SAP systems, and output of the sizing reports provided to the hardware partner?

A24: Please refer to the provided files from Procurement

Q25: What is the existing operating system, and database versions?

A25: Windows Server 2012 and SQL Server 2012

Q26: Please provide the current SAP components list for all systems.

A26: Please refer to the provided files from Procurement, and review the Early Watch reports

Q27: Do you have any HA or DR setup requirements?

A27: High level DR guidance is in scope

Rev. 7-25-18

5

Q28: Who is responsible for the HANA installations - will you be buying appliances or will the consulting partner be responsible?

A28: These are on-prem servers, and the installations will be performed as a collaborative effort between METRO Basis and vendor team

Q29: Do they have need to go to the latest support pack stack on target using SAP DMO, or do you just want a DB migration to HANA for all these systems?

A29: Latest support pack stack will be required.

Q30: Do you have preference for a Big Bang migration (e.g. ECC, BW, SRM in parallel) or would you be willing to do it in a phase wide manner?

A30: This will be an N+1 phased approach for Dev and QA. We will have a cutover weekend for go-live.

Q31: Do you use automated testing tools, or do you have current test scripts to perform regression testing?

A31: METRO has test scripts, no automation at this time.

Q32: Do you use TDMS for client data refreshes?

A32: No. These have been manual process by the Basis team. METRO does have EpiUse Data Sync Manager, but that's only used for targeted HR data.

Q33: Do you use Charm in Solution Manager, or is it just used for monitoring?

A33: Yes

Q34: p. 26: If possible, pls. share any such minutes of the meeting, memorandums of documents other than information that are published in the RFP document (page 52 onwards) including and not limited to Technical landscape of the Environment, Staffing Plans, Budgets, Project initiation dates etc.

A34: METRO will provide a group of files that include items like inventory lists, early watch reports, code analysis, sizing, and Visio diagram of the various landscapes.

Q35: p. 26: Has Metro defined and agreed project plan - the sequence of events ? For example, identified which systems would get upgraded first or migrated first ? Is the deployment in sequence or happening in Parallel mode ? If happening in Parallel- has Metro identified the risks associated with such big bang approach instead of phased approach ?

A35: The Contractor's implementation team is not required to have each of these labor categories represented, the implementation work is reimbursed on a fixed price basis. However, we require the Contractor to provide these labor categories if needed for unforeseen work related to the HANA implementation.

Q36: Pls. advise us on the Protest mechanism that exists which proposers can exercise. We are hopeful that procurement department would conduct a fair and impartial procurement process. It is essential that a level playing field be maintained for a win-win situation.

A36: See page x, paragraph T, "PROTESTS"

Q37: Is it possible for you to provide me with a list of SAP Services Partners that METRO works with?

A37: Peloton Alliance, that includes Peloton, Atos, EpiUse, Summit, and Vesta Partners. METRO also works with SAP Professional Services.

Q38: Page 55 of 70: Also request to rephrase the words, “Rapid Deployment Solutions” as “Industry Best Practices”

A38: Agreed - this can rephrased. SAP did have a period of time where they were offering so-called "Rapid Deployment Solutions". Not sure if this is relevant any longer, but is terminology we have continued to use internally.

Q39: Page 26 of 70, Section 1: Table needs clarification - if the scope is only for SAP ERP HANA migration or includes other SAP systems + Sandbox as well. If Yes, then pls. include additional line items matching the Scope of services as defined in page 55 of 70.

A39: METRO will provide a series of files that include a Visio diagram of the environment to be migrated, and an inventory spreadsheet that was produced at the same time of the Visio. These may not be 100% up to date, but very closely represent the current environment.

Rev. 7-25-18

6

Q40: Page 26 of 70: b. Section 2: Thanks for the clarification that table 2 Rate Card is only for any Ad-hoc work that may or may not arise in future. You have also clarified this rate card consultants are not directly related to the upgrade project activity under consideration and Metro cannot assure if they would really need such resources. Our request here is: 1. If that is the case, can we request to have Estimated Quantity as 1 Hour for all line items ? 2. If Metro can share the need for such team members ?

A40: 1. No, we believe it is important for Proposers to know how these rates will be evaluated, so we have provided our best estimate of the labor mix. 2. The requirements are not known at this time, so the need is undefined.

Q41: Considering a SME / DBE in Houston is not a must & does not account in any additional scoring during evaluations however Metro would appreciate including one.

A41: This is true.

Q42: To arrive at the sizing for SAP landscape upgrade and Migration to SAP HANA / Sybase ASE DB; we will require Early Watch Reports and Sizing of Current running landscape.

A42: METRO will provide an Early Watch report as part of series of files.

Q43: Section 1.2.1 Review existing SAP systems hardware, database and SAP software configuration – Question: Are we also migrating SAP Primary Application server & SAP Application Server from Windows platform to Linux Platform?

A43: This is really a question for the project blueprinting sessions. However, internally we are leaning towards leaving the various components on Windows Servers wherever possible. If something in our environment can be converted to HANA, then it goes on Suse Linux - otherwise we leave it on Windows Sever.

Q44: Question: What are the Business Module are currently implemented in ERP 6.0 EHP 7 systems and SRM systems?

A44: This can be deduced from our Visio diagram and inventory spreadsheet.

Q45: Question: Do we have to upgrade and Migrate SAP ECC, BW, SRM Gateway, Portal, Solman, SUS ABAP and SUS Java systems to SAP HANA 2.0 and Latest Support pack release?

A45: Yes.

Q46: Section 1.1.5 - Implementation of new functionalities and demonstration of way forward - Question: Do we have to develop or implement any new business process for example FICO / SD/PP /MM?

A46: METRO's goal in this project is to only modify those items which break due to HANA. There is no plan to implement new functionalities or business processes.

Q47: Section 2.2.1 – Project Scope – Question: Are we considering MDM as part of Migration and upgrade to SAP Sybase ASE database?

A47: Yes, and it's planned to be migrated to ASE. Please refer to the provided inventory spreadsheet.

Q48: Section 1.2.14 – Question: Should bidders consider onsite training or will Remote training be acceptable to keep the costs low?

A48: Yes, this is acceptable.

Q49: Section 1.3.1 – SAP Upgrade partner certification – Question: What kind of SAP Upgrade partner certification vendor must provide? For example – SAP Hosting certification, SAP Gold Partner, SAP Implementation partner.

A49: Per METRO's SAP Account Executive, SAP has a program called PartnerEdge. METRO requires that the proposed vendor be a participant in this program. It is METRO's understanding that participants of this program receive top level support from SAP, and we believe this support will help ensure a successful project.

Q50: Section 1.5.1. – Development Tools – Question: Please share list of all current development tools used by Metro? for example SAP web IDE for Fiori, SAP Eclipse etc.

A50: The following are METRO's SAP tools: Web IDE, Eclipse, Process Orchestration, and EpiUse DataSync Manager

Rev. 7-25-18

7

Q51: Section 1.5.1 – Development Tools - Question: Should the bidder assume any scope for development tool migration and or its testing?

A51: No

Q52: Section 1.5.2. – Landscape – Question: What is the Scope of SAP Success factor as part of HANA Migration?

A52: Success Factors is not in scope, including the interfaces.

Q53: Section 1.5.2. – Landscape – Question: What is scope of third party applications as part of migration? for example – Upgrade of BSI Tax factory is it in scope? Integration of third party application in scope? If yes, please list them down?

A53: METRO has two 3rd party timesheet applications, interfaced with Process Orchestration that will need to be tested. BSI Tax Factory will also need to be tested. EpiUse DSM will need testing to ensure it still works.

Q54: Section 1.5.2. – Landscape – Question: What is scope of third party applications as part of migration? for example – please provide details of third party application setup and configuration. For example, It is installed on Add on SAP Systems or standalone on dedicated system.

A54: There are no other 3rd party applications on SAP.

Q55: Section 2.1 – Methodology – Question: Do you want bidder to use SAP standard migration methodology?

A55: Yes

Q56: Section - 2.2.1 – SAP Fiori – Question: Custom App Migration 1.0 to 2.0 – Please provide high level application details of Custom Apps?

A56: Custom apps are used to create notifications in SAP PM work orders - such as time entry, and assignment.

Q57: Section 2.2.1 – SSO Configuration – Question: Do the bidders have to consider single sign on configuration as part of migration activity if yes please share list of systems?

A57: Yes

Q58: Section 2.2.4 – Testing plan – Question: How many iteration cycle vendors must perform as part of Testing? for example 1 UAT or 2 UAT cycle?

A58: Two integration/testing cycles, and one UAT.

Q59: Section 2.2.4 – Testing plan – Question: Will vendor get test script from Metro to execute UAT cycle? if not; does Vendor have to consider creation of test scripts as well in our efforts?

A59: METRO will provide test scripts for UAT. However, in some cases there may be a need for minor updates depending on changes HANA creates.

Q60: Section 2.2.4 – Testing plan – Question: Does bidder have to consider performance and load testing? if Yes Will can Metro provide third party tool to perform this testing?

A60: Load testing is not in scope. Performance tuning will however be expected during the project, and also after go-live during stabilization.

Q61: Section 2.2.5 – Security Plan – Question: Please provide details about HANA has altered underlying system components.

A61: This is a blueprinting topic during the project.

Q62: Section 2.2.6 - Question: Do we have to build and configure the Disaster Recovery (DR) systems for each landscape or should we provide only high-level detail about DR?

A62: Vendor should provide high-level detail as outlined in the RFP.

Q63: Section 2.2.8 – Question: Please share any existing and upcoming inflight projects?

A63: SAP Success Factors - recruiting management and onboarding. This is an independent project that will be performed in parallel.

Q64: Section 2.2.9 – Question: What kind of performance comparative benchmark will be considered as part of existing to the new upgrade system?

Rev. 7-25-18

8

A64: METRO expects that various processes will run faster, and at least equal in time to the non-HANA environment. An example of this is payroll, which is probably the longest running process at METRO. Outside of that, most everything is transactional in nature. METRO primarily does not want to experience slow downs from the current environment. We don't expect this, as HANA is faster, and will be implemented on new servers.

Q65: Section 2.2.10 –Post Go live – Question: Please provide classification of High, Medium and Low priority issues?

A65: Please refer to the RFP- Scope section 2.2.10. These were specified in hours.

Q66: Section 2.2.10 – Post go live – Question: Should the Post go live support be provided from purely from onsite or can also be remotely provided?

A66: If something can be performed remotely, then this is acceptable for METRO. However, during the immediate post go-live period, it's expected that vendor staff will be onsite.

Q67: Section 2.3 – Downtime – Question: What is the minimum downtime for production system during migration?

A67: Our target window is from a Friday at noon until the following Monday morning at 6:00am. This is a 66 hour window, which represents the absolute maximum time. METRO will be looking to shorten this to it's absolute minimum - which should be determined during the phases up to go-live.

Q68: Section 2.6.3 – Onsite Basis Consultant / SAP Project Manager – Question: What is the frequency of SAP BASIS consultant / SAP Project Manager to be onsite at Houston - In order to keep costs low we recommend every other week? Please confirm.

A68: This is something METRO would consider, however it's always better to have some resource onsite for the duration of the project.

Q69: Commercial: What is your process for contacting references? Call? Visits? etc..

A69: A call is acceptable.

Q70: Commercial: Confirmation SOH technical upgrade versus S4H implementation?

A70: This is Suite on HANA only - not S4/HANA.

Q71: BASIS: for the on-premise HANA solution, how is Metro going to achieve TDS certification

A71: METRO is a government agency, and as such does not have a TDS certification.

Q72: BASIS: who will be responsible for the sizing

A72: Sizing has already been performed in order to procure the new HANA servers. The sizing documents will be provided as a reference.

Q73: BASIS: Are all systems currently Unicode

A73: Yes

Q74: BASIS: Which version of SQL Server is currently in use

A74: SQL Server 2012

Q75: BASIS: Which version of Windows Server is currently in use

A75: Primarily Windows Server 2012, with possibly a few in 2016.

Q76: BASIS: Which version of Solution Manager is currently in use

A76: Version 7.2

Q77: BASIS: Which modules/features of Solman have been implemented

A77: CHaRM only.

Q78: BASIS: No mention of Front End Server (FES) for Fiori in the landscape. It is also not showing on the software screen shots. Where is it installed

A78: This is NetWeaver Gateway Server, and is outlined in the Visio and inventory files that have been provided.

Q79: BASIS: What other projects are currently underway and do those projects impact any of the SAP systems being upgraded

A79: SAP Success Factors - recruiting management and onboarding. This is an independent project that will be performed in parallel, but should have minimal impact on the Basis team.

Rev. 7-25-18

9

Q80: BASIS: Are there plans to switch from Sybase (With large volume Interfaces (lot of messages large size messages) Hana DB is recommended)

A80: METRO does not have large volume interfaces.

Q81: BASIS: How many resources are being committed by Metro? Is all hands-on work being performed by the contractor?

A81: This will be a collaborative effort. METRO has two Basis Administrators, and 12 SAP Analysts.

Q82: BW: What is the size of the database (BW)

A82: This is outlined in the provided METRO inventory spreadsheet.

Q83: BW: How many InfoCubes

A83: 100 Infocubes

Q84: BW: How many DSOs

A84: 74 DSO objects

Q85: BW: How many MultiProviders

A85: 23 MultiProviders

Q86: BW: How many InfoSets

A86: 1 InfoSet

Q87: BW: How many Queries

A87: Approximately 630

Q88: BW: How many DataSources

A88: Two

Q89: BW: How many time dependent attributes are defined across all master data bearing characteristics

A89: 304 time dependent info objects

Q90: BW: Are there any 3.X data flows

A90: No

Q91: BW: Are there any InfoSpokes

A91: No

Q92: BW: How many process chains

A92: Approximately 14

Q93: BW: How frequently is data loaded into BW? Nightly? Any near-real-time data loads

A93: Nightly for majority, and twice per day for three specific reports.

Q94: BW: How long is the data load Window

A94: Approximately 2 hours.

Q95: BW: How complex is the transformation logic in BW? Low/Medium/High

A95: Medium

Q96: BW: Which of the interfaces are used to load into BW? Service API, Flat File, DB Connect, UD Connect, Web Services…

A96: Service API only

Q97: BW: From how many systems is the data loaded into BW? ECC, CRM, SRM, …

A97: ECC and SRM

Q98: BW: What are the downstream applications that receive data from BW?

A98: None

Q99: BW: What interfaces are used to extract data from BW

A99: None

Q100: BW: What are the front-end application technologies? BOBJ, BEx, etc.

A100: BOBj, WEBI, and Bex

Q101: BW: Any dashboarding product is in use

Rev. 7-25-18

10

A101: No

Q102: BW: How many business-critical applications and processes are dependent on BW

A102: Three

Q103: BW: Any plans to use HANA with native modeling techniques (without BW modeling artifacts like Transformations & InfoCubes)

A103: This is not in scope

Q104: BW: Any mobile applications are dependent on BW

A104: No

Q105: BW: Any scheduling product in use

A105: No

Q106: BW: How many named users use the BW reports? How many concurrent users use the BW system at one time

A106: 105 Named, and 10 concurrent

Q107: BW: Any external facing applications depend on BW

A107: No

Q108: BW: Are there any, and if so which Fiori transactions used in BOBJ

A108: None

Q109: BW: Is any BW data sent to other systems

A109: No

Q110: BW: What are the DR requirements for BW

A110: This is part of the overall DR plan as noted previously and in the RFP

Q111: Front End: Fiori UI5 O-data - what is already there /in use?

A111: There are 8 projects each having one class, and each have approximately 12 methods. There are approximately 9 tiles.

Q112: PI/PO Interfaces: How many interfaces have been in use

A112: There are approximately 15 PO interfaces in production.

Q113: PI/PO Interfaces: How many Lines of code

A113: This can be discussed during the blueprinting phase of the project.

Q114: PI/PO Interfaces: Are these interfaces legacy receiver determination or Integrated Configurations

A114: They are a mix of both.

Q115: PI/PO Interfaces: How many IDoc interfaces are being used

A115: Two

Q116: PI/PO Interfaces: Are there any BPMs (Business process management) dependent interface management

A116: No

Q117: PI/PO Interfaces: Multi step business process Order, example: material reservation confirmation of ship date

A117: No

Q118: PI/PO Interfaces: Quantified mapping tables, …

A118: No

Q119: PI/PO Interfaces: Interface scan is available if desired

A119: We are not sure what information you are asking for.

Q120: PI/PO Interfaces: Has anything already been re-coded in Java, or is everything still in ABAP

A120: For SAP PO - everything is in ABAP and graphical mapping.

Q121: PI/PO Interfaces: Is EDI used

A121: No

Q122: PI/PO Interfaces: What adapters are used

A122: None

Rev. 7-25-18

11

Q123: PI/PO Interfaces: Are there any ccBPMs developed in dual-stack system? If yes, then how many mapping programs have been used

A123: No

Q124: PI/PO Interfaces: Are there any ABAP mappings used? If yes How many ABAP mappings are developed

A124: METRO uses APAB proxies as part of the PO interfaces.

Q125: Solution Manager: What is currently functionality running on the existing Solution Manager

A125: CHaRM only.

Q126: Solution Manager: What is their current version

A126: Version 7.2

Q127: Solution Manager: Planning an upgrade or brand-new install

A127: Not applicable - this was recently upgraded and should be HANA ready.

Q128: Solution Manager: What are the top 5 Solution Manager functionality that need to be implemented

A128: CHaRM only.

Q129: Solution Manager: What are the Solution Manager functionality that you would like to see be implemented

A129: CHaRM only.

Q130: Solution Manager: Do they have 2 (D/Q – P) or 3 (D-Q-P) Solution Manager systems

A130: Only Sandbox and Production - no D or Q.

Q131: Solution Manager: Has the SLD been setup

A131: Yes

Q132: Solution Manager: Has the hardware been sized for Solution Manager

A132: Yes

Q133: Solution Manager: What OS will Solution Manager be running on

A133: This should be migrated to Suse LINUX as part of the project

Q134: Solution Manager: What Database will Solution Manager be running on

A134: HANA

Q135: Solution Manager: What training has the team had on Solution Manager? Please list the courses and version if possible

A135: Not applicable. Staff are already trained on ChaRm.

Q136: Solution Manager: Is a 3rd party tool being used to monitor the SAP systems? If so what is the tool

A136: No

Q137: Solution Manager: Is a 3rd party tool being used for Job Scheduling? If so what is the tool

A137: No

Q138: Solution Manager: Is a 3rd party being used for documentation of your SAP business process.

A138: No

Q139: Solution Manager: Is there a centralize location for your SAP documentation

A139: Yes

Q140: Solution Manager: Do you have connectivity to SAP via the current SAP System

A140: Yes

Q141: Solution Manager: What tool is being for Change Management

A141: CHaRM only.

Q142: Solution Manager: What tool is being used for reporting incidents

A142: Service Desk Plus

Q143: Solution Manager: Do you currently archive

A143: No

Q144: Solution Manager: How many team members do expect to use Solution Manager

A144: 15 staff

Rev. 7-25-18

12

Q145: Solution Manager: What has been or is the biggest concern with Solution Manager

A145: None

Q146: ABAP Code optimization: 20 Abaps How many lines of cod

A146: Each ABAP program should have between 300-700 lines of code

Q147: ABAP Code optimization: How many custom ABAP programs (Reports/Programs/Includes)

A147: Approximately 700

Q148: ABAP Code optimization: How many custom Function Modules

A148: Approximately 500

Q149: ABAP Code optimization: How many custom Classes

A149: Approximately 30

Q150: ABAP Code optimization: How many custom transaction codes

A150: Approximately 200

Q151: ABAP Code optimization: How many Dynpros/Web Dynpros

A151: We are unsure of the exact numbers. Dynpros may be about 5. WebDynpros may be about 20-25.

Q152: ABAP Code optimization: How many User-exists / BADIs

A152: Approximately 100

Q153: ABAP Code optimization: How many custom tables

A153: Approximately 300, but will be better determined during the blueprint phase of the project

Q154: ABAP Code optimization: How many SAP Scripts / Smart Forms

A154: About 10

Q155: 2.2.9 Performance Tuning before and after upgrade: Are the Expectations for PI/PO maybe 4-6 weeks

A155: The expectation should be less than 4 weeks, as we only have 15 interfaces.

Q156: 2.2.9 Performance Tuning before and after upgrade: Basis maybe 3-5 weeks

A156: This sounds reasonable, but should be better defined during the blueprinting phase of the project.

Q157: 2.2.10 Resolution of issues: Can we assume that the resolution within 4 hours will depend on the Services Agreement

A157: Please refer to the RFP- Scope section 2.2.10. These were specified in hours.

Q158: We would like to request an extension on the 11/30 deadline. If possible, moving the deadline to mid or late December would be greatly appreciated. Its a difficult time of year to turn this type of proposal around so quickly.

A158: An extension of one week until December 7, 2018 was issued.

Q159: Has METRO run any of the SAP reports to support the Migration, if so, could you share the reports? Examples are; a. EWA; b. QuickSizer; c. Code Checker /Code Inspector

A159: Yes, please refer to the additional provided files.

Q160: How many custom objects are there in the Production system?

A160: Approximately 1500

Q161: Is there a architecture diagram that you could share?

A161: Yes, please refer to the additional provided files.

Q162: Can you share a list and description of all integrations?

A162: Yes, please refer to you additional provided files.

Q163: Resumes – are representative resumes sufficient? We normally do not commit specific staff until the project is awarded. We can provide representative resumes and commit to have people at or above the skill/experience levels in the representative resumes.

A163: Representative resumes will be sufficient. However, Key Personnel may only be replaced with METRO’s approval

Q164: Are all your systems Unicode?

Rev. 7-25-18

13

A164: Yes

Q165: Please clarify your DR request? what is a on-prem DR. Did you mean: Local HA with Global DR secondary site?

A165: DR site is Transtar Houston, with rack space owned by METRO. Primary servers are installed in METRO's data center. The production landscape will be replicated from the data center to Transtar.

Q166: Please provide a list of your personal who would work with us on this project and their availability % for this project. Example: Entire Functional test team 80% available. Basis 2 member 50% each, etc.

A166: This will be a collaborative effort. METRO has two Basis Administrators, and 12 SAP Analysts. Basis should be 50% available, and Analysts, at least 50% during course of the project.

Q167: What is your maximum downtime requirement for Production in hours? do we need a Near zero downtime cost as well?

A167: Our target window is from a Friday at noon until the following Monday morning at 6:00am. This is a 66 hour window, which represents the absolute maximum time. METRO will be looking to shorten this to it's absolute minimum - which should be determined during the phases up to go-live.

Q168: Do you need us to provide functional public sector testers. If so are your business process documented in Solution Manager?

A168: No, METRO does not need public sector testers. Business processes (per se) are not documented in Solution Manager. That said, every transport and change is clearly documented.

Q169: Can you supply recent SAP Early Watch reports for all productions systems that will be migrated to SAP HANA 2.0?

A169: Yes, that was included in the files provided (and zipped)

Q170: Has a hardware vendor for the new infrastructure been selected? If so, has the hardware been ordered?

A170: Yes, Dell Poweredge Servers

Q171: Does Metro have an archiving strategy? If so, has data been archived?

A171: No archiving strategy. This is not in scope, however is something METRO will be looking at in the next couple years.

Q172: Is there a High Availability requirement?

A172: No. However the Dell Poweredge have a number of fault tolerant features.

Q173: On the SAP HANA Implementation Services RFP; may we ask for extension for the submission to Friday Dec 14th. Please confirm if this is acceptable to Metro?

A173: An extension of one week until December 7, 2018 was issued.

Q174: Sandbox environment- is it part of the landscape for all products which are given in scope?

A174: Yes

Q175: ERP, SRM and BW needs an upgrade and there is NO MIGRATION to SAP HANA is in scope.

A175: We are not sure what information you are asking for.

Q176: What is the target version of Business Objects

A176: Business Objects are not targeted for an upgrade at this time.

Q177: What is the source and target versions of Solution Manager ?

A177: 7.2 is the current version, and no further upgrade is being considered at this time.

Q178: Should we consider FUNCTIONAL TESTING in scope or it would be executed by Metro Houston team ?

A178: METRO will conduct function testing. However, support and oversight will be required from the vendor on this project.

Q179: Code optimization is specified as 20 objects for ECC, BW and SRM. Is it only 20 objects? If so 20 objects for each product or cumulative 20 objects or is it complete code optimization .

A179: Cumulative 20 objects, and will be determined during blueprinting.

Q180: Pls. fill in the missing data in the below table.

Rev. 7-25-18

14

A180: Please refer to provided Visio diagram as a further reference SAP ERP 6.0 - migration-yes, target-HANA SAP SRM 7.0 - migration-yes, target-HANA SAP Netweaver BW - migration-yes, target-HANA SAP PO - Landscape-SDQP SAP Netweaver Gateway - Landscape-SDQP SAP Enterprise Portal - Landscape-SDQP SAP Business Objects - source 4.1-target 4.1, Landscape-SDQP SAP Solution Manager source 7.2-target7.2, Landscape-SP