eBusiness IT Strategy

Assuming that Internet based business transactions are to be introduced into an existing IT environment then the technical strategy will be influenced by the existing infrastructure. Charteris approach development of e-business IT strategies by starting with a review of the existing infrastructure with a view to determining what you will need for your Internet based business transactions. This includes determining:

1. Existing Web servers in use;
2. Existing transaction engines in use;
3. Existing database applications in use;
4. Current architectural approach;
5. Electronic sales and marketing in use;
6. Electronic payment switches/gateways in use;
7. Current approach to integration – is it best of breed or pacakged integrated business solutions;

Having understood the existing infrastructure Charteris can resolve the following issues that must be addressed before proceeding:

  • The Internet redefines the term “Legacy” – applications built as recently as 1995 or 1996 may become redundant but old databases may still have value;
  • Adopting a consistent architectural approach- do you go with web to legacy, front end web-enabled applications or end-to-end Internet business applications;
  • The Internet is a strategic IT platform – do not necessarily assume that Internet technology will sit isolated from the business simply as a means for reaching customers. An end to end business process might be completely supported by Internet technologies;
  • Outsourcing versus Build, Operate and Transfer – in a rapid application environment the business must expect to be integrally involved in desinging and building new Internet based systems;
  • Adopting the right standards – standards are emerging for EDI-INT for EDI on the Internet, Open Financial Exchange (OFX), Open Trading Protocol (OTP) etc which customers will expect you to comply with. How do you monitor and adapt to these standards as they emerge;
  • Security – how do you want secure vital assets whilst providing external entities access to the information they contain;

Having determined the above Charteris can then assist you to determine the framework architecture you should adopt. This will involve modifying the following generic framework as appropriate:

  • Content and services in the digital domain – creating your online inventory eg information about hard-goods or soft-goods for download;
  • Merchant services – creating the services analogous to those required for a physical outlet eg catalogue, product display, shopping cart;
  • Transaction management – enabling processing of digital offers and receipts with authentication, order management and record keeping;
  • Payment mechanism – incorporating universal payments methods and interfacing to the required financial institutions;
  • Order fulfilment – this will cover fulfilment of one or more of the following four types of product and will need to interface to logistics systems if appropriate:

    • a) Soft (software, digital music, information);

    b) Hard (books, CDs);

    c) Interactive services (access to processes infromation);

    d) Digital tokens (ticketless tickets);

  • Customer service and support – customer expect immediate online support including statements of account and transaction histories;
  • Data reporting and analysis – this includes internal controls and data reporting on customer an Website activity ie from hit activity to customer behaviour analysis.