Data System management has long-term viability as a separate business function because ?->(Show Answer!)

1. Data System management has long-term viability as a separate business function because

Write Comment

Comments

Tags

Show Similar Question And Answers

QA->A subset of data in a warehouse in the form of summary data, related to a particular department of business function:....

QA->UnionMinister of State for Development of North Eastern Region Jitendra Singhinaugurated the ‘e-VMS’ (e-Visitor Management System) at which port as part ofthe Ease of Doing Business initiatives?....

QA->The process related to process control, file management, device management, information about system and communication that is requested by any higher level language can be performed by:....

QA->How manycities are termed as Smart Cities announced by the Urban Development Ministrywhere highly advanced in terms of overall infrastructure, sustainable realestate, communications and market viability?....

QA->Which government to business (G2B) portal under the Ministry of Commerce and Industry launched 11 government services for those who need to start business in India?....

MCQ-> on the basis of the information given in the following case. Teknik Group of industries had businesses in different sectors ranging from manufacturing, construction, fish farming and hotels. These different businesses operated as semi-independent units managed by the unit level managers. Teknik’s management had an internal consultancy group called as Business Advisory Group (known internally as BAG). The 15 experts in BAG were hired personally by Mr. Teknikwala, the owner of Teknik, who wanted this core group of experts to help his organization grow fast without facing the typical growth hurdles. Most of them were specialists in fields like law, information technology, human resource management, and operations management. Almost all of them had experience spanning decades in the industry. Whenever any of the units faced any significant all units and it represented an extra work for those who were involved. This coordination was required to understand the different work processes and the users’ requirements. This coordination activity was being extensively managed by the old timers as they were familiar with internal processes and people in the different units. An external consultant was also hired for customization and implementation After two months, BAG teams had to fortnightly present their progress to Ms. Teknikwali’s team. In the last meeting Ms. Teknikwali was dissatisfied. She explained her thinking that since ERP impacted every aspect of the business, the roll out had to be done faster. She wanted Mr. Shiv to get the implementation completed ahead of schedule. In the meeting she asked Mr. Shiv to get the people in IT team to be more productive. Not willing to disagree, Mr. Shiv committed to a roll-out schedule of complete ERP system in 6 months instead of earlier decided 14 months. Next day, Mr. Shiv presented the revised project milestone to BAG members. He told them that in order to meet the deadline, the members were expected to work on week-ends till the completion of the project. Along with that, they were also expected to maintain their earlier standards of delivery time and quality for the normal trouble-shooting and internal advisory work. Mr. Shiv also pointed out that anyone whose performance did not meet the expectations would be subjected to formal disciplinary action. The meeting ended without any member commenting on Shiv’s ideas, although Mr. Shiv heard a lot of mumbling in the corridor. Over the week, Shiv noticed that the members seemed to avoid him and he had to make extra effort to get ideas from them. After a fortnight Shiv reviewed the attendance register and found the Mr. Lal, an old time member, had not come during the week-ends and certain decisions were held up due to lack of inputs from Mr. Lal. Mr. Shiv issued a written reprimand to Mr. Lal. He was speechless on receiving the reprimand but kept silent. It has been three days since that incident. Some of the senior members had put in request for transfer to other business units. It was rumoured that four problems, the unit level managers would put up a request for help to BAG. The problems ranged from installation of internal MIS systems, to financial advice related to leasing of equipment, to handling of employee grievances. Over a period of 20 years, Teknik’s revenues grew from 100 crore 10,000 crore with guidance of BAG and due to Mr. Tekinwala’s vision. Given its reputation in the industry, many people wanted to start their careers in BAG. Often young MBAs fresh out of business schools would apply. However their applications used to be rejected by Mr. Teknikwala, who had a preference for people with extensive industry experience. Things changed after the unfortunate demise of Mr. Teknikwala. His daughter Miss. Teknikwali took up the family business. She was an MBA from one of the premier business schools, and was working in a different company when Mr. Tekinwala passed away. She preferred that BAG developed new ideas and therefore inducted freshly graduated MBAs from premier business schools. She personally supervised the recruitment and selection process. Now the entire group constituted of 50 specialists, out of which 35 were the old time members. She also changed the reporting relationships in the BAG group with some of the older members being made to report to the new members. In IT team, Mr. Shiv, a newly recruited MBA, was made in-charge. For the older members it was a shock. However, as most of them were on the verge of retirement, and it would be challenging to search for new jobs while competing with younger professionals, they decided to play along. After one month, all business units were caught up in the ERP fever. This was an idea pushed by Ms. Teknikwali who the need the need to replace the old legacy systems with latest ERP system integrating all the units of Teknik. This was heavily influenced by her experience in the previous where an ERP system was already up and running. Therefore she was not aware of the difference between installing an ERP system and working on an already installed one. The ERP mplementation in Teknik Group required extensive coordination with senior level managers of senior legal experts had agreed to an offer from a law firm. Other senior members would sporadically come in late to work, citing health reasons. Almost all senior members now wanted a weekly work-routine to be prepared and given to them in advance so that they could deliver as per the schedule. This insistence on written communication was a problem as urgent problems or ad-hoc requests could not be foreseen and included. Also normal services to other business units were being unattended to, and there were complaints coming from the unit heads.Which of the following could have been a better response of Mr. Shiv to Ms. Teknikwali’s request to re-schedule the ERP implementation?....

MCQ-> Read the following passage carefully and answer the questions given below. Certain words/phrases have been printed in bold to help you locate them.Management is a set of processes that can keep a complicated system of people and technology running smoothly. The most important aspects of management include planning, budgeting, organising, staffing, controlling, and problem-solving. Leadership is a set of processes that creates organizations in the first place or adapts them to significantly changing circumstances. Leadership defines what the future should look like, aligns people with that vision, and inspires them to make it happen despite the obstacles. This distinction is absolutely crucial for our purposes here: Successful transformation is 70 to 90 per cent leadership and only 10 to 30 per cent management. Yet for historical reasons, many organizations today don't have much leadership. And almost everyone thinks about the problems here as one of managing For most of this century, as we created thousands and thousands of large organizations for the first time in human history, we didn't have enough good managers to keep all those bureaucracies functioning. So many companies and universities developed management programmes, and hundreds and thousands of people were encouraged to learn management on the job. And they did. But, people were taught little about leadership. To some degree, management was emphasized because it's easier to teach than leadership. But even more so, management was the main item on the twentieth-century agenda because that's what was needed. For every entrepreneur or business builder who was a leader, we needed hundreds of managers to run their ever growing enterprises.Unfortunately for us today, this emphasis on management has often been institutionalized in corporate cultures that discourage employees from learning how to lead. Ironically, past success is usually the key ingredient in producing this outcome. The syndrome, as I have observed it on many occasions, goes like this: success creates some degree of market dominance, which in turn produces much growth. After a while keeping the ever larger organization under control becomes the primary challenge. So attention turns inward, and managerial competencies are nurtured. With a strong emphasis on management but not on leadership, bureaucracy and an inward focus take over. But with continued success, the result mostly of market dominance, the problem often goes unaddressed and an unhealthy arrogance begins to evolve. All of these characteristics then make any transformation effort much more difficult.Arrogant managers can over-evaluate their current performance and competitive position, listen poorly, and learn slowly. Inwardly focused employees can have difficulty seeing the very forces that present threats and opportunities. Bureaucratic cultures can smother those who want to respond to shifting conditions. And the lack of leadership leaves no force inside these organisations to break out of the morass.Why, according to the author, is a distinction between management and leadership crucial?
....

MCQ->Data System management has long-term viability as a separate business function because....

MCQ-> Read the passage carefully and answer the questions given at the end of each passage:Turning the business involved more than segmenting and pulling out of retail. It also meant maximizing every strength we had in order to boost our profit margins. In re-examining the direct model, we realized that inventory management was not just core strength; it could be an incredible opportunity for us, and one that had not yet been discovered by any of our competitors. In Version 1.0 the direct model, we eliminated the reseller, thereby eliminating the mark-up and the cost of maintaining a store. In Version 1.1, we went one step further to reduce inventory inefficiencies. Traditionally, a long chain of partners was involved in getting a product to the customer. Let’s say you have a factory building a PC we’ll call model #4000. The system is then sent to the distributor, which sends it to the warehouse, which sends it to the dealer, who eventually pushes it on to the consumer by advertising, “I’ve got model #4000. Come and buy it.” If the consumer says, “But I want model #8000,” the dealer replies, “Sorry, I only have model #4000.” Meanwhile, the factory keeps building model #4000s and pushing the inventory into the channel. The result is a glut of model #4000s that nobody wants. Inevitably, someone ends up with too much inventory, and you see big price corrections. The retailer can’t sell it at the suggested retail price, so the manufacturer loses money on price protection (a practice common in our industry of compensating dealers for reductions in suggested selling price). Companies with long, multi-step distribution systems will often fill their distribution channels with products in an attempt to clear out older targets. This dangerous and inefficient practice is called “channel stuffing”. Worst of all, the customer ends up paying for it by purchasing systems that are already out of date Because we were building directly to fill our customers’ orders, we didn’t have finished goods inventory devaluing on a daily basis. Because we aligned our suppliers to deliver components as we used them, we were able to minimize raw material inventory. Reductions in component costs could be passed on to our customers quickly, which made them happier and improved our competitive advantage. It also allowed us to deliver the latest technology to our customers faster than our competitors. The direct model turns conventional manufacturing inside out. Conventional manufacturing, because your plant can’t keep going. But if you don’t know what you need to build because of dramatic changes in demand, you run the risk of ending up with terrific amounts of excess and obsolete inventory. That is not the goal. The concept behind the direct model has nothing to do with stockpiling and everything to do with information. The quality of your information is inversely proportional to the amount of assets required, in this case excess inventory. With less information about customer needs, you need massive amounts of inventory. So, if you have great information – that is, you know exactly what people want and how much - you need that much less inventory. Less inventory, of course, corresponds to less inventory depreciation. In the computer industry, component prices are always falling as suppliers introduce faster chips, bigger disk drives and modems with ever-greater bandwidth. Let’s say that Dell has six days of inventory. Compare that to an indirect competitor who has twenty-five days of inventory with another thirty in their distribution channel. That’s a difference of forty-nine days, and in forty-nine days, the cost of materials will decline about 6 percent. Then there’s the threat of getting stuck with obsolete inventory if you’re caught in a transition to a next- generation product, as we were with those memory chip in 1989. As the product approaches the end of its life, the manufacturer has to worry about whether it has too much in the channel and whether a competitor will dump products, destroying profit margins for everyone. This is a perpetual problem in the computer industry, but with the direct model, we have virtually eliminated it. We know when our customers are ready to move on technologically, and we can get out of the market before its most precarious time. We don’t have to subsidize our losses by charging higher prices for other products. And ultimately, our customer wins. Optimal inventory management really starts with the design process. You want to design the product so that the entire product supply chain, as well as the manufacturing process, is oriented not just for speed but for what we call velocity. Speed means being fast in the first place. Velocity means squeezing time out of every step in the process. Inventory velocity has become a passion for us. To achieve maximum velocity, you have to design your products in a way that covers the largest part of the market with the fewest number of parts. For example, you don’t need nine different disk drives when you can serve 98 percent of the market with only four. We also learned to take into account the variability of the lost cost and high cost components. Systems were reconfigured to allow for a greater variety of low-cost parts and a limited variety of expensive parts. The goal was to decrease the number of components to manage, which increased the velocity, which decreased the risk of inventory depreciation, which increased the overall health of our business system. We were also able to reduce inventory well below the levels anyone thought possible by constantly challenging and surprising ourselves with the result. We had our internal skeptics when we first started pushing for ever-lower levels of inventory. I remember the head of our procurement group telling me that this was like “flying low to the ground 300 knots.” He was worried that we wouldn’t see the trees.In 1993, we had $2.9 billion in sales and $220 million in inventory. Four years later, we posted $12.3 billion in sales and had inventory of $33 million. We’re now down to six days of inventory and we’re starting to measure it in hours instead of days. Once you reduce your inventory while maintaining your growth rate, a significant amount of risk comes from the transition from one generation of product to the next. Without traditional stockpiles of inventory, it is critical to precisely time the discontinuance of the older product line with the ramp-up in customer demand for the newer one. Since we were introducing new products all the time, it became imperative to avoid the huge drag effect from mistakes made during transitions. E&O; – short for “excess and obsolete” - became taboo at Dell. We would debate about whether our E&O; was 30 or 50 cent per PC. Since anything less than $20 per PC is not bad, when you’re down in the cents range, you’re approaching stellar performance.Find out the TRUE statement:
....