October 20169 time, it also allows some form of customization that is essential for the process to be done. Meanwhile, it does take a longer implementation lead time and higher cost will be incurred.c) E-Documents Conversion ­ In this case if neither of the above solutions is applicable, then alternatively a company can deploy certain software to `automate the un-automatable' documents to an e-version, and then allow its data to be exchanged with internal/external selected parties to reduce lead time for data exchange. It is no longer a `full automation' but the implementation time and cost for these solutions are relatively less comparing with standard EDI connection. Many would now have the question whether with all these solutions available ­ is it the right time to deploy them for their business in APAC? There is no simple answer to that question but rather I would advise those who are interested, needs to take concern on the following:1) You need to take into concern on the number and financial impact of the e-business benefits, and compare it against the personalized and humanistic service requirements which your business need to provide, basing on how many current & future customer segments of your customer portfolio will need it. This will help you to define the scoping of your e-business clearly.2) The scoping of your business case will probably need to take into account on country adoption rate of certain e-business trend, depending on their speed & popularity of certain e-business process settling in. As an example, if you know your Thailand customer often requires physical delivery of invoice, then you need to consider the applicability of E-invoicing to them. Japan and Korea are generally more accepting to EDI supporting transactional service; on the contrary you will need to challenge the applicability of web shop there. India is currently very popular with webshop and e-procurement portals due to the initiative Digital India, but you may need to consider how long these trends will last.3) If there are low volume transactions then webshop/portal is recommended, else EDI is more preferable for high volume transactions.4) As you are possibly facing more than two audiences within one customer's legal entity (e.g. procurement and engineer), you need to be aware on the design of your company's homepage, the web shop, and you have to define clearly what kind of content and process will be included into which domain.5) If you are choosing to adopt EDI, then you need to consider whether you should adopt it on purely process level (e.g. for purchase or sales order transmission), or including people level (e.g. for mass communications, real time contact, profile, safety information exchange). Either way, the technical infrastructure readiness at your trading partner's company side, in terms of middleware setup and valid external EDI provider connection, will be something you need to be mainly concerned of, since APAC companies' readiness are typically lower comparing with EMEA and NAFTA companies. The scoping of your business case will probably need to take into account on country adoption rate of certain e-business trend, depending on their speed & popularity of certain e-business process settling inCharles Nie
< Page 8 | Page 10 >