Servers 0 Hrs 1 Day example essay topic
This system needs to provide an easy method for the NCEs to access and leverage previously defined design solutions. This system will provide several key benefits to the NCE team: o NCE will be able to search for data related to the solution being considered NCE will save time in that we will not "reinvent the wheel" o NCE provided solutions will be more standardize do Using the same solution repeatedly simplifies supporting our solution so Allows our NCEs to be able to provide backup to one another o With standard solutions we increase the probability that we will continually improve the solution. User Requirements The IT team spent time interviewing and observing the NCE team using the current information systems. The team discovered that the current systems lacked the flexibility and access to meet the needs of the NCEs. In addition the processes to back up an effective workflow are absent.
Through this analysis the following key user requirements were identified. These requirements were considered in the selection of the proposed information system. The proposed information system provides for the following: o A flexible "form" for data entry o A sophisticated search methodology o Accessible via a web browser o Simple administrative capabilities o Capability to "revise" data base entries o Backup and archiving capability o Maintains statistics of hits to database records Business Requirements The IT team assembled and reviewed all data and documentation available on the current processes and tools in use by the NCE team today. In doing so we discovered some specific deficiencies that can be addressed in the proposed solution. At this time, we have neither formal procedures nor tools for cataloging and storing NCE design solutions for future reference. This means the NCEs are duplicating some of their efforts.
This duplication of effort is causing an increase in solution design time and support costs as well as losing best practices information among NCEs. To mitigate these issues the following business requirements have been designed into the proposed information system: o A data base to store design solutions as they are completed and implemented o The ability for the NCE to perform keyword solutions against he data base to identify previously developed and implemented solutions. o A web based application to access the database. o Functionality that includes adding new solutions, modifying existing solutions, collaboration on designs in progress, and the ability to delete obsolete design so The system will also provides statistics and reporting capabilities to monitor database usage and performance See Appendix A for a Return on Investment (ROI) analysis Information System Process Flow The proposed system will be accessed via a secure web site with a login and password. As the site is for corporate communication, the servers can reside within the network and with external access provided through VPN, also making the site more secure. Once the NCEs log on to the site, they will be able to enter or access design information entries and supporting documentation. Access to the system will also be given to project managers and higher management so they can keep abreast of the progress of various solutions based on the information the NCEs enter into the system.
Also, through the site the NCEs will have the ability to enter specific and detailed solution architectures including the specific hardware, connectivity, network topologies, and backbone appliances used in their solutions. This will further enhance the database by creating a knowledge base to be shared by other NCEs, TAC, and management. By using meta tags and keywords associated to the entry, the database can be queried for specific solutions to be brought up for reference. As NCEs continue to enter solutions into the system, the growth of the database will yield more information and will result in a very extensive library of solutions. Following is a slide that depicts the business functionality of the system.
Figure 1: NCE Groupware Information System Technical Design System Design The system will run in a Microsoft SQL Server 2000 data base environment. This environment will include two Dell Power Edge servers running Windows Server 2003 as the operating system. The two servers will be clustered to allow fault tolerant redundancy and will run in an active passive environment. The primary server will handle all database requests from the web servers. Should it fail, the second server will be configured to recognize the failure and switch to active mode, processing database requests until the primary server is restored to service. The data disk storage for these servers will be housed externally in a mirrored array that is raid configured with a hot spare drive to protect against failure.
The external storage array will be backed up incrementally nightly in the event a reload in required. Each server will have an internal drive to house the operating system and other system files. This drive will be mirrored by another drive to protect against failure of a system drive. The web servers will be configured in the same manner as the database servers. They will contain internal mirrored system drives to protect against drive failure. This type of configuration will provide redundancy against a server failure.
Our web servers will reside in a DMZ (demilitarized zone) and will be load balanced and scalable. The load balancing will occur in a round robin fashion. If a server fails, the load balancer will detect this loss of the server and drop it out of the round robin. This set up also provides easy scalability. Should the load on the server farm become intensive, we can simply add another server to take some of the load. See Appendix C for a hardware list for this information system.
Network Design The network portion of the proposed solution will consist of firewalls, routers, switches, load balancers, and content engines (used here as reverse-caching appliances). This combination of equipment will provide us with security, performance, and scalability. Our database server will sit inside our internal network to protect our data from unauthorized access. Our web servers will sit in our DMZ and will access the database server through an internal firewall. Access to the web servers from the internet will come through an outside or shield router and an external firewall, which is attached to a T 1 data line provided by out Internet Service Provider. Directly behind the external firewall in the DMZ, we will place a load balancer.
This device will do server load balancing (SLB) for the web servers. The content engines will be placed behind the load balancer as well. The load balancer will direct HTTP requests for static content to the content engines. The content engines will serve up content directly when a request is made for an object it has stored in cache memory. If the object requested is not in the cache engine, it will make an HTTP request to the web servers through the load balancer. The load balancer will receive HTTP requests for non-static content directly from the clients and will load balance the request to the best available server.
Following is a picture that depicts our network design. Figure 2: NCE Share Point Network System Software The web services are provided by the Microsoft Share Point Server Portal 2003 and will be deployed as a content managed extra net application. Administration of this product is minimal, once each database is created and the content management is handled by an overall coordinator with each NCE a contributor to the document and knowledge base content. The overall aesthetic of the website is highly and will accept Java and ASP. net programming to give full functionality to the site. The database connectivity is handled by ODBC to SQL and can be threaded to an active web application within the portal.
Individual or group portals can easily be created and are by the NCEs. The portal can serve as a web based file server for those who are on the road and need easy access to a highly functional file server without traversing the corporate network. Documents are version controlled and access is controlled via the coordinator using standard Windows security settings. Documents can be read, checked out, or published, depending on the access level of the individual logging in to the site.
Our clients who access the system from the internet will be required to use a VPN client for that access. Our users will be required to authenticate to our system with a user id and password. The VPN client will also encrypt the data sent and received from the user to protect it from unauthorized access. The other requirement on the client will be Internet Explorer browser 5.0 or above. We have included samples of our web pages that will be displayed for the user. Included is a technical diagram depicting the internet working that will also be used in our deployment.
Figure 3: NCE Home Page Figure 4: NCE Share Page " Proposal Conclusion The IT Team believes this design supports our business requirements as previously described. It also provides all the technical specifications stated at the beginning of this proposal. We have addressed security, availability, and performance. This design is only as complex as need be to meet the user and business requirements.
The design leverages some of the existing NCE and network capabilities and can be deployed in a planned and non-disruptive manner. Based on the evidence presented, we are asking the company's executive committee to approve funding for this information system project. The IT Team believes there are both short and long term advantages to implementing this information system for the NCE team. See Appendix B for implementation tasks Appendix ANCE Information System Project Plan (Task List prior to assignments and timelines) Project Start Date: Sun 1/25/04 Project Finish Date: Mon 1/26/04 Tasks with Assignments ID Task Name Work Duration Start Finish % Work Complete 1 Develop a Central Repository For Network Engineering Information 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%2 Form project team 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%3 Determine project team members 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%4 Identify project manager 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%5 Identify project scope 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%6 Identify timeline 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%7 Write requirements document 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%8 Evaluate required data sets 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%9 Evaluate database application 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%10 Evaluate hardware requirements 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%11 Evaluate Web-based applications 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%12 Begin technical interviews 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%13 Setup interviews with NCEs 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%14 Setup teleconferences 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%15 Form technical development team 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%16 Identify database developer 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%17 Determine database package 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%18 Identify web application designer 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%19 Determine web application package 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%20 Start database design 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%21 Database developers begin design 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%22 Identify hardware 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%23 Network engineers design servers 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%24 Purchase or procure servers 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%25 Deploy developmental server 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%26 Begin Web application Design 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%27 Work with database designer for entry fields 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%28 Plan on connectivity to database 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%29 Test initial database and application 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%30 Load test 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%31 Web accessibility test 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%32 Load initial database 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%33 Optimize Database 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%34 Load sharing 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%35 Hardware optimization 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%36 User testing 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%37 Provide access to NCEs. 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%38 Schedule time frame for testing 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%39 Review issues 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%40 Implement solutions to issues 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%41 Retest 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%42 User Acceptance 0 hrs 1 day? Mon 1/26/04 Mon 1/26/04 0%43 Deployment 0 hrs 1 day?
Mon 1/26/04 Mon 1/26/04 0%Figure 3: NCE Information System Project Plan Task List Appendix Return on Investment Analysis From a return on investment (ROI) perspective, based on the expected benefits previously stated, we expect to gain the following savings. This year, we will provide approximately two hundred solutions for our customers from eight design groups. Each solution costs the company $10,000 to develop, and the average price to the customer is $15,000. We estimate the current duplicate effort to be 10 percent or 20 design solutions. This amounts to a potential two hundred thousand dollar a year savings, or, the ability to deliver 20 additional customer solutions with a gain in revenue of $300,000, and additional profit of $100,000. This gain is realized without incurring additional development costs or an increase in support costs to support the extra sales.
We expect the cost to implement the system to be as follows. The hardware costs for the database and web servers are expected to be $35,000. The database software cost is $10,000. Estimated development and implementation costs are $20,000. Total cost to implement the system is $65,000. Based on the additional annual profit of $100,000 and a cost of $65,000 to implement the system, we estimate the return on investment (ROI) to be eight months.
We calculate this based on $100,000 divided by 12, which equals $8,333 additional profit per month. The $65,000 divided by $8,333 rounds out to eight months to the recoup our investment. The next slide depicts the return on investment time. Return on Investment Chart Appendix System Hardware requirements: Web Server Platform (2) CPU Speed: Dual 733 MHz (or higher) Itanium-based computer (64-Bit) Minimum RAM: 512 MBRecommended RAM 1 GBHard Disk Size 120 GB (2.0 GB for setup) CD ROM CD-RWNetwork Adaptor 10/100/1000 Monitor 15" Digital LCD Keyboard Standard USB Mouse Optical USB KVM Switch 8 Port Data Base Platform (2) CPU Speed: 733 MHz (or higher) Itanium-based computer (64-Bit) Minimum RAM: 512 MBRecommended RAM 1 GBHard Disk Size 40 GB (2.0 GB for setup) CD ROM CD-RWNetwork Adaptor 10/100/1000 External Storage Array (2) 6 Bay SCSI to IDE RAID tower with Intel i 80303 (R) RD 64 Bit RISC processor. Populated with 3 x 200 GB drives (expandable to 1,500 GB) Load Balancing Appliance (2) Cisco 11503 Content Service Switch (CSS) Web Caching Appliance (2) Cisco Content Engine 565 Client Platform: (NCEs already have suitable platforms) Type: Laptop with 15" display and built in mouse CPU Speed 1.5 GHz RAM: 512 Gbhard Disk Size 30 GBC D ROM CD-RW / DVD Microsoft IE Version 6.0, sp 2 Microsoft Office X PCD ROM DVD / CD ROM.