SAP SAP ECC6 Enhancement pack 6 ANNEX C TECHNICAL RESPONSE GUIDELINES – Suppliers should provide a response to all points in their Technical Response with the following exceptions: Suppliers proposing an on-premise solution should not answer questions in orange text; and Suppliers proposing a SaaS solution should not answer questions in green text. TECHNICAL REQUIREMENTS 1.1 Integration Suppliers shall confirm that their products are compatible with the following technologies describing in each case the relevant methods of integration: 1.1.1 Java API integration capability to interface with other business enterprise applications. 1.1.2 Authentication and authorisation with Active Directory and single-sign-on capability. 1.1.3 Integrate with SAP (Module ECC6) and additional externally HR systems. 1.1.4 Integrate with identity management platforms. 1.1.5 Integrate with MS Exchange Server 2010. 1.1.6 Mobile device's browser and/or Mobile Apps capability, as described in section 1.2. 1.1.7 API compatibility or data source access to enable access to data. 1.1.8 Integrate with market leading code versioning e.g., Visual Source Safe, Subversions, Serena (Dimensions), MKS, IBM and CA. 1.1.9 Integrate with collaboration unified communication platforms, e.g. Cisco Jabber, Microsoft Lync or Microsoft Yammer. 1.1.10 Integrate with Workplace Management systems, e.g., Accruent, Planon, Tririga and FM Systems 1.2 Mobile devices 1.2.1 The Bank requires that the Tool has the functionality for to access the Tool by a mobile device to create, review, update and approved Service Requests, Incidents, Change Requests and Releases. 1.2.2 Suppliers are required to confirm the Tool is compatible with the mobile device platforms described within the table of section 2. and demonstrate how these requirements can be met. 1.2.3 The Bank requires this functionality to be available through both mobile device's browser and/or Mobile Applications. Suppliers provide details of how this functionality is delivered. 1.3 Security 1.3.1 The Tool will be utilised by separate business areas e.g. IT and HR. The Tool must therefore cater for security of sensitive data as well as have the ability to allocate role based security levels.
SAP SAP ECC6 Enhancement pack 6 ANNEX C – TECHNICAL RESPONSE GUIDELINES Suppliers should provide a response to all points in their Technical Response with the following exceptions: Suppliers proposing an on-premise solution should not answer questions in orange text; and Suppliers proposing a SaaS solution should not answer questions in green text. TECHNICAL REQUIREMENTS 1.1 Integration Suppliers shall confirm that their products are compatible with the following technologies describing in each case the relevant methods of integration: 1.1.1 Java API integration capability to interface with other business enterprise applications. 1.1.2 Authentication and authorisation with Active Directory and single-sign-on capability. 1.1.3 Integrate with SAP (Module ECC6) and additional externally HR systems. 1.1.4 Integrate with identity management platforms. 1.1.5 Integrate with MS Exchange Server 2010. 1.1.6 Mobile device's browser and/or Mobile Apps capability, as described in section 1.2. 1.1.7 API compatibility or data source access to enable access to data. 1.1.8 Integrate with market leading code versioning e.g., Visual Source Safe, Subversions, Serena (Dimensions), MKS, IBM and CA. 1.1.9 Integrate with collaboration unified communication platforms, e.g. Cisco Jabber, Microsoft Lync or Microsoft Yammer. 1.1.10 Integrate with Workplace Management systems, e.g., Accruent, Planon, Tririga and FM Systems 1.2 Mobile devices 1.2.1 The Bank requires that the Tool has the functionality for to access the Tool by a mobile device to create, review, update and approved Service Requests, Incidents, Change Requests and Releases. 1.2.2 Suppliers are required to confirm the Tool is compatible with the mobile device platforms described within the table of section 2. and demonstrate how these requirements can be met. 1.2.3 The Bank requires this functionality to be available through both mobile device's browser and/or Mobile Applications. Suppliers provide details of how this functionality is delivered. 1.3 Security 1.3.1 The Tool will be utilised by separate business areas e.g. IT and HR. The Tool must therefore cater for security of sensitive data as well as have the ability to allocate role based security levels.
smtrfp.docx