Online Forum

#

Question

EQL Response

1

Follow up to EQL 2019 235 Clarification 1, Question 1 (Published 3^rd Aug):
The Invitation to Tender Reference Schedule indicates a Commencement Date of the Proposed Agreement of September to October 2020, however the answer to this question shows the DEBBs end state architecture. Attachment B shows a Delivery Roadmap Timeline View indicating the delivery of this end state architecture into 2021. Is the expectation that Augmented Support commences in Sept '20 for the delivered solutions and that the systems and application delivering future functionality are taken into support during the course of '21 in line with the Delivery Roadmap?

Yes that is correct.  As there may be slight changes in timing, EQL will engage the successful Vendor Partner prior to implementation of products with a scope statement and request for quantification (if required).

2

Process Scope: 
Is there a full business process list available to understand the depth of SAP solution support needed?

Yes all implemented solutions are documented with business process designs.  These will be made available as part of the transition-in activities.

3

Support Scope:
Are there any support scope requirement for Geospatial Services through Esri and other third party products?

Not at this stage.

4

Service Level Agreements: 
- There is only mention of RPO and RTO , which is from a infrastructure point of view and primarily applicable for Disaster Recovery (DR) situation. Are there any other SLAs from a technical and application support point of view?
- Is there a definition of Category A, B+, B and D? 

Please see attached EQL 2019 235 Schedule 8 Service Levels.

5

Service Credits:
There is a requirement for Service Credit. However there are no fixed service credit amount mentioned for SLA breach. Is Vendor needed to propose ?

Please see attached EQL 2019 235 Schedule 8 Service Levels.

6

Landscape details:
Can you share the landscape details – Number of systems , DB size and number of tier for each system?

Refer to attachments included in response to question #1 for ‘DEBBs Target State Architecture Views (technology)’ as well as ‘EQL Application Catalogue extract’. These provide a high-level view of systems. Typically, our environment consists of 4 instances covering Development, System Integration Testing / Quality Assurance, User Acceptance Testing / Pre Production, and Production. This is the case for S/4HANA, SAP MDG, Ariba and SuccessFactors. Note multiple clients may exist within these instances. Question and response #11 Basis Scope provides more information relating to this question.

7

Integration:
Appendix C outlines the DEBBs High level architecture. Is there are full list of all integrations from S/4HANA to SAP (SF, Ariba, Fieldglass, Concur) and third-party systems (Energy Services, Retail, Distribution) indicating integration technology used – SCPI ?,  Frequency of execution,  Inbound/Outbound and Data Transferred?

Refer to attached document DEBBs Master Integration Catalogue Extract 2020-08-09 for a listing of current live interfaces. Note this has limited inclusion of integration technology as this needs to be handed over from design documentation from the project teams to our central register. Generally most interfaces are either native (out of the box vendor supplied) interfaces or connectors, or are otherwise implemented using SCPI for SAP and Cloud systems, and Oracle Service Bus for on premise systems. SAP Data Services is our ETL technology for relevant use cases. Note that a significant number of additional interfaces will be introduced as part of future projects however the proposed items are not included while this is being determined. The diagrams provided in Appendix C are proposed target state at the conclusion of our transformation program where ERP and EAM capabilities are transitioned from our current state systems to the SAP products. These are subject to change. The architecture views included in response to question #1 for ‘DEBBs Target State Architecture Views (technology)’ as well as ‘EQL Application Catalogue extract’ provide an updated view on the evolving system landscape.

8

To be Support Organisation:
What are the % of Functional, Technical, Architects, Developers, Basis, Process Owners expected for the support of the DEBBs Solution?

Currently EQL is undergoing a support transition phase.  Existing internal capability for technical support of the new solution roadmap is in it’s infancy. This is expected to support the upskilling that is underway and varies between support areas.  As an indication of internal support capability, the following High level % should be used:

• Functional Support capability across HSE, Finance and Enterprise Services, Governance Risk and Compliance, SuccessFactors and Procurement – Ariba: 80-90% (limited augmented support required)
• Technical Support capability including technical domain design across HSE, Finance and Enterprise Services & Governance Risk and Compliance as currently undertaken by vendor partners: 0%
• Development Support capability & development expertise e.g. ABAP & Fiori as currently undertaken by vendor partners: 0%
• Integration support capability including SCPI: 80% fulfilled (limited augmented support required)
• Architectural support capability is fulfilled internally although emergent requirements may arise to augment the existing team.
• Basis Support capability: 30% internally fulfilled with the balance of resources provided by external vendor partners.
• Process owners are internal to EQL: 100% (no augmented support required)

Please Note: Future planned release e.g. AWM and the remaining Digital core functions of the ERP/EAM solution are currently being quantified.  Augmented support will be expected across Technical and development streams.

It is expected that over time vendor support involvement will decrease as EQL internal capability increases.  Assistance with upskilling & mentoring of internal resources forms a core part of the Tender.

9

To be Support Organisation:
What is the approximate IT strength across the different solutions?

Please refer to: Supporting presentation for question 9 Support Organisation.

EQL uses a matrix model to delivery service capability.  All support resources will be sourced from within the Digital capabilities area and can be scaled up and down as required.

10

To be Support Organisation:
Where will the support organisation be physically located e.g. Brisbane, Townsville etc. approximate % by function, by site

The current EQL digital support capability is dispersed across Queensland with the majority of support personnel located in Brisbane (80%) with presence in other major locations including Townsville and Rockhampton.  Presence across other sites is limited more to desktop support officers.  The IT Service Desk operates out of Rockhampton.

Business functional support teams are represented across Queensland.

#

Question

EQL Response

1

Volume data by SAP modules & by severity?

Please see the following graph that contains the last 90 days of incidents by severity:

2

Is this an on-prem SAP implementation?

We are running the on-premise version of S/4HANA however this is hosted with an Energy Queensland managed Virtual Private Cloud (VPC) on AWS. This was relocated from previously being hosted in HANA Enterprise Cloud. Components included in this VPC including S/4HANA, BW/4HANA, Solution Manager, Identity Management, Master Data Governance, and Open Text. Our Enterprise Intelligence Platform including HANA Database, Data Services and Information Stewart are in the same VPC. Other SAP Products and Services are hosted in the SAP Cloud Platform including SCPI, SuccessFactors and Ariba. Integration to existing systems include both cloud hosted and Energy Queensland data center hosted solutions.

3

Number of users? By System (ECC/Ariba/Success Factor / EHNS /Payroll etc.)

AWM 5,500

Enterprise Services AR/Banking 25

Finance S/4 HANA 169

SAP BPC 239

Governance, risk and Compliance (GRC) 332

HSE Emp: 7,614 Contractor: 1,668 Total: 9282

Master Data Governance (MDG) 24

People and Culture (Success Factors) Emp: 7,614 Contractor: 1,668 Total: 9282

Procurement (Ariba) Emp: 7,614 Contractor: 1,668 Total: 9282

Enterprise Intelligence Platform (EIP) 30

4

What Modules of GRC have been implemented?

*GRC-RM: SAP Risk Management 12.0

* GRC-SPC-AP which includes:

          * SAP Access Control 12.0;

          * SAP Process Control 12.0.

* GRC-AUD: SAP Audit Management

* SAP Business Integrity Screening

* SAP Regulation Management (RM) Cyber Governance by GreenLight

* (Regulatory Change Management (RCM) module only (i.e. not including Real time adaptor design studio (RTA DS) module))

5

Have they implemented “IS Utility”

Industry Solutions for Utilities is enabled in our S/4HANA instance and we have a base level of licensing however are not currently utilising any of the associated modules or functions. We have a roadmap to utilise this for our Customer and Australian Energy Market needs including metering however this is on hold while we review current systems and solution fit.

6

Is BASIS in scope? What activities of BASIS is in scope?

We have a current capability however are interested in exploring support augmentation in this space.

7

Is Job Monitoring in scope, what are number of jobs? & Schedules?

This is covered by internal EQL capability.

#

Section

Question

EQL Response

1

Transition

Is EQL open for rate card-based T&M engagement during Hypercare Augmentation phase in order to have staffing flexibility that aligns with later changes in implementation schedule?

The scope of this Tender does not include the requirement for Hypercare therefore there is no requirement to provide pricing for this.

2

General

Does EQL plan to have a parallel run of the source and target systems?

Can you please clarify the context of this question? Note: there is no expectation for involvement in implementation activities.  This is the responsibility of the DEBBs Portfolio.

3

General

We understand that vendor might not be expected to solution 100% managed services. In such a scenario, what functional/technical roles will be retained in-house?

As an indication of internal support capability the following High level % should be used:
• Functional Support capability across HSE, Finance and Enterprise Services, Governance Risk and Compliance, SuccessFactors and Procurement – Ariba: 80-90% (limited augmented support required)
• Technical Support capability including technical domain design across HSE, Finance and Enterprise Services & Governance Risk and Compliance as currently undertaken by vendor partners: 0%
• Development Support capability & development expertise e.g. ABAP & Fiori as currently undertaken by vendor partners: 0%
• Integration support capability including SCPI : 80% fulfilled (limited augmented support required)
• Architectural support capability is fulfilled  internally although  emergent requirements may arise to augment the existing team.
• Basis Support capability: 30% internally fulfilled with the balance of resources provided by external vendor partners.
• Process owners are internal to EQL: 100% (no augmented support required)
Please Note: Future planned release e.g. AWM and the remaining Digital core functions of the ERP/EAM solution are currently being quantified.  Augmented support will be expected across Technical and development streams.
It is expected that over time vendor support involvement will decrease as EQL internal capability increases.  Assistance with upskilling & mentoring of internal resources forms a core part of the Tender.

4

General

Is the S4/HANA hosting environment management in-scope for this RFP or will this be provided by SAP vendor?

No hosting is not in-scope for this RFT.

5

Transition

Is there an agreement on ‘# open defects’ for exiting ‘Hypercare’ phase and entering ‘Steady State Support’?

Each Project undertakes a support handover process which will assess the readiness for transition to support.  This includes an assessment of the number and severity of open defects and the overall stability of the solution.

6

Transition

Where will the implementation team be located at? Will this be the location for transition?

The current EQL digital support capability is dispersed across Queensland with the majority of support personnel located in Brisbane (80%) with presence in other major locations including Townsville and Rockhampton.  At this time, it is expected that the majority of resources will be located in Brisbane however this does not preclude future requirements for regionally based work where appropriate.

Note: There is no expectation for involvement in implementation activities.  This is the responsibility of the DEBBs Portfolio.

Tenders wishing to provide a response will be required to register with EQL’s realm of SAP Ariba by sending an email to  SPGDigital@energyq.com.au by no later than 30 July 4pm Qld time. 

Already have an account?  please email SPGDigital@energyq.com.au so we can confirm your account is active.  Do not assume if you have an exisitng Ariba account, that it will be available for EQL it may with another Customer.

Don't have an account - please contact SPGDigital@@energyq.com.au to have an account created and registered by no later than Monday 10th August 2020.

All reponses will need to be uploaded into Ariba.  Responses into QTenders will not be accepted.