I need to have an idea on the effort estimation to integrate SAP and Non-SAP system. Ball park estimate could be enough for me.
I do understand that this can't be answered without having proper information. So, let me please ask the following questions.
i) What are the parameters should be considered to measure the complexity of one interface?
ii) If we categorize the complexity into simple, average and complex then what should be the ball park effort-estimation on each category?
iii) Assumption1 can be made that developers are well trained.
iv) Assumption2: Interfaces are identified.
Any kind of experience sharing is most welcome.
To be honest, the amount of workload including the design, development, testing everything is no different from other projects in R/3.
To be more specific to your kind of scenario in XI, we have done the following to arrive at an intial estimate with few considerations and assumptions:
1. Usage of Standard Adapters
2. Inbound/Outbound R/3 transactions shall either be IDOC, RFC and custom developments which are pre-existing.
3. Data transaction validations would be done as the part of R/3 as the part of interface development and NO or minimal cross company code conversions will be assumed in XI while mapping.
4. SLD has been predefined with all the Business Systems withing the organization.
5. NON R/3 receivers/senders will have prebuilt scripts to receive/send the files to a common location and XI has already established mapping/connectivity to that location.
6. The integration development will have Dev,Quality and Production environments. (COMM CHANNEL development time shall be considered).
7. Sizing and Hardware pulsibility is already done for scalling the performance of the system. (This is actually needed during initial phase of XI establishment)
...... number of other factors involving data management etc.,etc.,
The estimates shall be
1. The Number of Messges, Mapping volume, transaction volume, receiver and destination locations, Adapter Framework shall be few primary factors from the Development standpoint of view within XI.
2. Business Process development and Mapping template, interface identification from R/3 for Inbound and Outbound will be primary factors for Business Application Needs. This will be needed for Requirement gathering and Consultation.
3. Added to the above, If process involves complex mapping related to Content based Routing, BPM and multiple recivers, Cross Company business applications then the development, testing and realization would take more time for taking sign-off.
4. Scoping and design template, documentation and UTD.
5. Initial testing, realization. SAT and UAT, Integration testing invarious platforms, realization and Final move to Production.
Here are the estimates in terms of hours/days.
1. Requirement Gathering and Blueprint phase and sign-off - 5 to 10 Days (Assume Political situations as well)
2. Specs and realization on Mapping Document QR approval for development- 2 Days (not sure if is applicable everywhere)
3. Design,Development and intial development documentation
Subjected to scope of work involving Repository and Directory- 4 Days (One to One Mapping, Complex Message types like MATMAS, GLMAST, Invoice and Billing, SDPICK, PICKSD, ORDERS etc.,). Subjected to Standard Message Mapping or non-complex XSLT mapping (Java/Abap)
- x 2 to 3 times incase of complex requirements.
4. Initial Testing and Realization - 1/2 Day to 1 Day
5. Integration testing for the given scenarios, Realization and Documentation - 1 day - 2 Days.
6. Integration testing in Quality Environment, Realization and Documentation changes (if any) - 1 day to 2 Days.
7. Final Production Migration and Sign-Off - 1 Day
So, it will be a 3 Weeks to 6 Weeks Assignment. Please understand that this is only an estimate and time has been calculated based on my experience in carrying up Hyperion and other main frame integrations which mostly deal with FI module of SAP R/3 for SEM project.
For bigger integration projects like ICH, SCM it will be purely based on Business requirements.
Hope this will be of use and let's know if you want to know anything more.
>>i) What are the parameters should be considered to measure the complexity of one interface?
a) The amount of consultations with business - if you have to interface something
that will be working slightly different than it used to in the past then
you have to go ask many people how they see it - and frankly speaking you'll have to talk about
every additional field - this is the most time consuming part I believe
b) the use of standard adapters - it can really speed up you project
if you're using standard adapters on the other hand there are many,
many situations when you'll have to build you're own of use simpler method - java proxies
(if you got very good java XI people this won't be difficul but still time consuming)
c) the complexity of mappings - if you got one to one (or almost one to one)
mappings can be done really fast but if the target document is completely different
then you may have to create many RFC FMs (that you'll be calling from
your integration processes) or use many user exits to fill your
messages with the right and complete data
c) testing the more complex the data is the more XI developers testing (in the first testing faze) has to be involved