Management system analysis

Paper for Analysis
Purpose: Show that we can develop a small system that is logically complete and consistent and is documented for an appropriate management presentation or funding presentation.
*Do not read The Goal until systems model is approved for our new idea
Format and Content are important
• Format: Business – Not English or History Paper
• In this order and she wants a hardcopy
4 Pieces to Paper:
1. Cover Letter – Letter of Transmittal (First Page)
a. A short business letter or memo that moves the study from you to the person who asked for it or the piece of the organization who asked for it. Address it to Professor Sampson or someone who is the head of the expedition company you are doing it for. Do not send to Fisher or Hall because they are dead. Haha
b. Your role is the outside advisor consultant.
c. *Will bring scoring sheet next Tuesday
d. Graded on: Format (Beginning of course email is proper format)
i. Takes up a page
ii. Signature
e. All you have to say: I got this assignment on February 16, 2016 and it is completed and attached.
i. Might want to point out something significant in your recommendation briefly but don’t oversell it.
2. Executive Summary / Summary of the Recommendation
a. 1 Paragraph or 2
b. Single spaced
c. Not an abstract
d. Stand alone page but probably wont be a full page of writing
e. Can have title of “Executive Summary”
3. Text (Name to fit your recommendation subsystem)
4. Model
a. Closed-looped model
5. Optional Other Attachments
a. Organizational Chart
b. Timeline
6. Bibliography
Order to do it:
• Model
• Text
• Executive Summary
• Cover Letter
Model:
• Start with idea of a sub system that you can build based on what you learned from Everest (Your Book, Other Book, Videos, Presentations)
• Doesn’t have to be big – but has to involve other people. A job description doesn’t work.
• Start with core system and then spin off to the sub systems
Order for Model:
1. Overall Objective, Name of System, Boundaries
2. Objectives
3. Standards (a,b,c)
a. 2 Measurable
b. 1 Fuzzy Yes/No
i. Make them as real as you can but might need to invent them
4. Results (x,y,z)
a. Won’t know results because you’re implementing something. You need a generic measure to compare to the standards
5. Feedback (Basis for corrective action)
a. A vs. X
i. <
ii. =
iii. >
6. Corrective Action
a. Most likely, = (Equal) is no corrective action necessary
b. < (Greater), what are you going to do about it?
c. > (Less), what are you going to do about it?
i. 1 can be Yes/No
ii. Probably will have 9 each
iii. X vs. A
iv. X vs. B
v. X vs. C
vi. Y vs. A
vii. Y vs. B
viii. Y vs. C
ix. Z vs. A
x. Z vs. B
xi. Z vs. C
7. Inputs
a. What are the things that are necessary and sufficient to achieve the results
b. People are not inputs (Lena, Beck) – Not good enough and not right
i. Those people are not going to exist again
c. Going to do it for an expedition that will run in the future
i. This May is too soon too
8. Process
a. Sub-activities
b. Components
c. Transformation
i. Some may be to correct
ii. Some may be to let those results go on to the next phase of the system
iii. Some may to get more out of the environment
Meet with Sampson WITH your Model. “Close” does not mean A. “Close” means that the system is almost logical and complete.