MGMD 233 –MIS Topic 3: Enterprise Infrastructure & Integration

1. MGMD 233 –MISTopic 3: Enterprise Infrastructure & Integration AMN 2012/2013

2. INTRODUCTION • A service-oriented architecture (SoA) is a software architecture perspective that focuses on the development, use, and reuse of small sell-contained blocks of code (services) to meet all the application software needs of an organization. • It also can be used as a philosophical approach to help the organization of the future meet all its IT-related needs and help organization respond to:- • **refer text figure 7.1 – SoAPhilosopy

4. HARDWARE & SOFTWARE INFRASTRUCTURE • Infrastructure – “the structure beneath a structure” – implies different layers of structure, which provide support / services. • IT infrastructure is the implementation of architecture (SoA) for an organization’s structure. • In corporation, IT infrastructure includes the hardware, software (e.g ERP) & information that to ensure the components work together & enable people, business processes, customer interact & perform their tasks.

5. HARDWARE & SOFTWARE INFRASTRUCTURE

6. ERP (revisited) • Enterprise resource planning (ERP) system – collection of integrated software for business management, accounting, finance, supply chain management, inventory management, customer relationship management, e-collaboration, etc • For ERP to integrate everything, everything must be plug-and-play components or services • All modules of an ERP vendor must be interoperable • Software from multiple ERP vendors must be interoperable • The infrastructure beneath must be hidden from users and customers • **refer figure 7.5 – an ERP infrastructure

7. ERP (revisited)

8. SUPPORTING NETWORK INFRASTRUCTURE • Network is two / more computers sharing information, software, peripheral devices, processing power. • It’s a fundamental underlying infrastructure for any IT environment. • There are 5 major types of network infrastructures

9. SUPPORTING NETWORK INFRASTRUCTURE

10. SUPPORTING NETWORK INFRASTRUCTURE

11. SUPPORTING NETWORK INFRASTRUCTURE – Tiered (Layer)

12. CLOUD COMPUTING • Cloud computing – model in which any and all IT resources are delivered as a set of services via the Internet such as:- • Application software • Processing power • Data storage • Backup facilities • Development tools • Literally everything

13. CLOUD COMPUTING

14. CLOUD COMPUTING - Goals • Pay for only what you need and use • Real-time scalability (up or down) • Align computing costs with level of business activity • Reduce fixed costs in IT infrastructure

15. CLOUD COMPUTING - Implementation

16. PUBLIC & PRIVATE CLOUD • Public cloud – comprises cloud services that exist on the Internet offered to anyone and any business. • Amazon Web Services (AWS) • Windows Azure • Rackspace Cloud • Google Cloud Connect • ElasticHosts

17. PUBLIC & PRIVATE CLOUD • Private cloud – cloud computing services established and hosted by an organization on its internal network and available only to employees and departments within that organization. • All benefits of cloud computing, except held private within an organization

18. ADVANTAGES OF CLOUD • Lower capital expenditures • Lower barriers to entry • Immediate access to a broad range of application software • Real-time scalability

19. BUSINESS CONTINUITY PLANNING (BCP) • Business continuity planning (BCP) – rigorous and well-informed organizational methodology for developing a business continuity plan, a step-by-step guideline defining how the organization will recover from a disaster or extended disruption • BCP is very necessary today given terror threats, increased climate volatility, etc

20. BCP Methodology

21. BCP Phases – OSP Organizational Strategic Plan - it all starts here with understanding the relative importance of resources, systems, processes, & other organizational assets.

22. BCP Phases - Analysis • Analysis phase the organization performs on the:- • Impact analysis – risk assessment, evaluating IT assets, their importance, and susceptibility to threat • Threat analysis – document all possible major threats to organizational assets • Impact scenario analysis – build worst-case scenario for each threat • Requirement recovery document – identifies critical assets, threats to them, and worst-case scenarios

23. BCP Phases - Design • Design phase the organization deign a formal, technical and detailed plan for recovering from a disaster. • Build disaster recovery plan, may include • Collocation facility – rented space and telecommunications equipment • Hot site – fully equipped facility where your company can move to • Cold site – facility where your company can move to but has no computer equipment

24. BCP Phases - Implementation • Implementation phase is engaging any businesses that will provide collocation facilities, hot sites, and cold sites. • Implement procedures for recovering from a disaster • Train employees • Evaluate each IT system to ensure that it is configured optimally for recovering from a disaster

25. BCP Phases - Testing • As opposed to traditional SDLC, testing in BCP methodology occurs after implementation • Testing involves executing simulated scenarios of disasters and having employees execute on the disaster recovery plan to ensure that solution satisfies for organization’s recovery requirements.

26. BCP Phases – Maintenance • Perform testing annually, at a minimum • Change business continuity plan as organizational strategic plan changes • Evaluate and react to new threats • No “system” is ever complete