Creating a process map | Management homework help

Before Scenario: Information Flow Challenges

In our organization, we’ve been grappling with significant issues related to information flow. These challenges are particularly pronounced due to missed emails, repetitive back-and-forth communication on the same issues, and a reluctance to fully embrace the capabilities of the Microsoft Suite tools available to us. As a result, the transfer of critical information between departments within our Maintenance, Repair, and Operations (MRO) framework has been less efficient than desired.

One specific area where this problem manifests is in the E10 Logistics department. Requisitions are primarily sent via email( by the floor management), but this approach has its drawbacks. The sheer volume of emails makes it easy for requisitions to be overlooked, leading to missed orders or delays. The logistics team relies heavily on this information to process orders and coordinate with Planning, the Customer Maintenance Support Representative (CMSR), and Production Leads. Unfortunately, the reliance on email communication often results in inefficiencies. For instance, printed communication is sometimes hand-delivered to Production Leads, necessitating additional time spent locating leads and verifying information.

Root Causes:

1.
Walking Distance for Information Retrieval: The physical distance between the materials team and email senders (such as Planning, Production Leads, and CMSR) contributes to delays. This unnecessary motion impacts efficiency and productivity.

2.
Lack of Visibility on Orders: There is no clear visibility into orders sent from management, planning, or CMSR. This lack of transparency creates defects and hinders timely decision-making.

3.
Missing Attachments and Information: Requisitions often lack necessary attachments or critical details, leading to further defects in the process.

4.
Order Verification Gap: Without proper verification, we risk ordering incorrect items or encountering warranty-related issues. This can result in financial losses or wasted time.

5.
Service Level Agreement (SLA) Gaps: There are no defined SLAs between different Service Center Departments, affecting inventory management and overall efficiency.

6.
Lack of Centralized Order Database: The absence of a centralized “data base” for order requisitions compounds waiting times, defects, and unnecessary motion.

Note:

Requisitions are first sent from Floor management (Leads or planning), it is sent to the Parts team. Once it is sent to the parts team, the CMSR’s then have the choose if it is covered under warranty, free of charge, buy, epep or pending customer approval. Once this is done Parts team places the order. (Pending no issues of course)

Continue to order Get a quote

July 1, 2023

The Role of Systems Assignment 1

Purpose

The purpose of this assignment is to assess your ability to explain the role of information systems to support business collaboration.

Action Items

1. Conduct research for the following topical areas. Focus your research by locating current articles (i.e., within the last 12 months) in information technology and/or MIS journals. Concentrate on articles that discuss specific implementations of collaboration systems for:

· Knowledge management;

· Content management;

· Workflow management; and

· Groupware.

2. Conduct additional research regarding future trends in collaboration systems. Examples might include:

· Instant messaging; or

· Blogs; or

· Streaming content; or

· Online meeting/collaboration spaces; or

· Other trends of your choice.

3. Choose a specific future trend related to collaboration systems and discuss its potential benefits to organizations.

Assignment 2 PowerPoint Presentation

Please choose one option and three roles associated with that option

Project Research and Strategy Proposal – As a C Level

Proposal Strategy Analysis and Solution Proposal – As an Executive

Solution Proposal Analysis and Recommendation Proposal – As a Manager

Option 6 - CCO- Chief compliance officer = CCO> Senior Vice President, Human Resources> Manager, HR

· ERP Risk Factor: The implementation (Big Bang Approach) integrated everything at once.

· ERP Risk Factor: The implementation did not consider how requirements might frequently change.

· You will each research those 2 ERP risk factors, discuss how collaboration might mitigate them, and propose a strategy to implement them, from the perspective of your job title.

· Your research and discussion should focus on actual implementation.

· You will prepare a PowerPoint presentation, including notes for each slide contained in the presentation.

· In your discussion/presentation, you will focus on:

· Introduction, this should frame what you will be presenting.

· What are the factors which you are responsible for?

· Who (by job title) would be involved with each factor?

· Quantify and discuss the risk factor in terms of potentially negative impact (1/least-10/most) and include at least two examples of issues from each risk factor in real-life ERP implementations? You will focus your research by locating current articles (i.e., within the last 12 months) in information technology and/or MIS journals. Concentrate on articles that discuss specific ERP implementations.

· When should collaboration be part of the implementation?

· Why will collaboration be a positive remedy?

· How will collaboration address the risk(s)?

· Conclusion/Summary/Recommendation, this should be a strong restatement of your findings.