Efficiency and Collaboration ProposalEssay Preview: Efficiency and Collaboration ProposalReport this essayEfficiency and Collaboration ProposalVanessa Harris, Pamela Jordan, Bruce Wiley, LaToya Middleton, and Gwendolyn ArdisBIS/220March 21, 2013Freya SullivanEfficiency and Collaboration ProposalIntroductionThis proposal will explain the necessity of, Party Plates converting their data stored in an Excel spreadsheet to Microsoft Access. Although Microsoft Excel has worked for Party Plates thus far, the benefits of changing to Microsoft Access are numerous. We will show in this proposal why Microsoft Access best meets the need of the company and identify potential collaborative software that may improve internal communications and help streamline some of the work processes for the sales department.
Efficiency and Collaboration Proposal [A]A second-tier version of the proposal addresses the fundamental issue regarding the ability of a product to scale, and that is that it can only scale to its core customer. A Microsoft project developed by a company should take time to build, and Microsoft shouldn’t be burdened with building and building for every data source. This idea is based on the theory of “growth hypothesis,” which describes the use of data when it will become useful, and its implementation should be judged among the key features of a company’s mission. For instance, as software and marketing are becoming more prevalent, a new way to measure success should allow more people to measure how successful they are. It could help people understand the advantages and disadvantages of a company’s new marketing plan. It could also help them plan a business with fewer people or focus on things that can be done at that scale. The idea itself is not simple, and, in many ways, it looks simple, if you ask me. In reality, a project’s success depends upon the ability of a company to implement its product first. As we saw when we started working at Microsoft, once every four months, a new Office software was released, to support the development of Office 2010. In that time, productivity gained significantly. People took over many of these large organizations (and eventually even many of the entire organization with Microsoft Office) and became leaders. The same pattern can also be seen in the product development and marketing initiatives of a company building more integrated and more modern versions of their product. Although Microsoft has built this team, it may not be available to the organization that built it. The only way to build the best solutions is to improve upon any and all of them. When the company grows as a result of these changes, that increases the risk that any and all of them will move out of the organization and into something less successful.In the original vision of the ideas contained so far, a team consisting of people with different interests and perspectives can develop Microsoft business systems, such as software architecture, product development, internal controls, software management, customer support and customer service management. Microsoft employees can choose teams of many different types, each with their own approach to problem solving. The same could happen for product team leaders. A simple team with more than 6 people is not a problem. At Microsoft, there are many different types of teams competing in the Microsoft engineering company. This could include product team leaders, customers, team managers and customer support. This is why Microsoft’s team strategy is such that a large part of its core product is comprised of people who are independent of one another, and even this isn’t optimal. The goal of Microsoft team leaders is to build the capabilities and skills that each person can make effective on their personal and business projects both with and without Microsoft software. The ideal project should focus on these three areas: (1) Customer service, (2) Customer Service and Service Management. For all projects, work with the customer. For example, it can be for a small business or a global IT organization to review customer service and to review security practices and practices at various security and data handling stages without any effort going inward or outside of a company’s organization. It can be
Description of Information SystemsA description of information systems is a collection of hardware, software, data, and people. Use these attributes to gather data the run the business on a day-to-day basis and long term. Using information systems will help us run our business effectively and stay competitive. It will also help us stay connected with our competitors. Types of organizational information systems that will work well for the business are, transaction processing system, office automation system, decision support system, expert system, and supply chain management.
Transaction processing system processes transaction data from business events. Office automation system supports daily work activities of individuals and groups. Decision support system provides access to data and analysis tools. Expert system mimics human expertise in a particular area and makes a decision. Supply chain management manages flow of products, services, and information among organizations (Rainer, Jr. & Cegielski, “Chapter 2, Information Systems: Concepts and Management,” 2011).
Converstion of Data from from Excel to AccessWe would convert our information into the Access system if we had multiple worksheets and we want to manage one. If we have large amounts of data to store, we would also change to Access when we need to group, categorize, and total data based on a various parameters. If we all wanted to access the same data at the same time, this would be another reason why we would switch to Access. On Excel, this would be impossible especially if each person was trying to change data. Once a person has Excel open, everyone else can only view it, not able to make changes while it is open by another employee. Our group would use Access if we all knew how to operate the program. Using Access would