Topic: Management system analysisOrder DescriptionPaper for AnalysisFebruary 27 (Saturday) by 4PM – Hard Copy ONLYPurpose: Show that we can develop a small system that is logically complete and consistent and is documented for an appropriate management presentation or fundingpresentation.*Do not read The Goal until systems model is approved for our new ideaFormat and Content are important• Format: Business – Not English or History Paper• In this order and she wants a hardcopy4 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 toProfessor 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. Hahab. Your role is the outside advisor consultant.c. *Will bring scoring sheet next Tuesdayd. Graded on: Format (Beginning of course email is proper format)i. Takes up a pageii. Signaturee. 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 Recommendationa. 1 Paragraph or 2b. Single spacedc. Not an abstractd. Stand alone page but probably wont be a full page of writinge. Can have title of “Executive Summary”3. Text (Name to fit your recommendation subsystem)4. Modela. Closed-looped model5. Optional Other Attachmentsa. Organizational Chartb. Timeline6. BibliographyOrder to do it:• Model• Text• Executive Summary• Cover LetterModel:• 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 systemsOrder for Model:1. Overall Objective, Name of System, Boundaries2. Objectives3. Standards (a,b,c)a. 2 Measurableb. 1 Fuzzy Yes/Noi. Make them as real as you can but might need to invent them4. Results (x,y,z)a. Won’t know results because you’re implementing something. You need a generic measure to compare to the standards5. Feedback (Basis for corrective action)a. A vs. Xi. 6. Corrective Actiona. Most likely, = (Equal) is no corrective action necessaryb. < (Greater), what are you going to do about it?c. > (Less), what are you going to do about it?i. 1 can be Yes/Noii. Probably will have 9 eachiii. X vs. Aiv. X vs. Bv. X vs. Cvi. Y vs. Avii. Y vs. Bviii. Y vs. Cix. Z vs. Ax. Z vs. Bxi. Z vs. C7. Inputsa. What are the things that are necessary and sufficient to achieve the resultsb. People are not inputs (Lena, Beck) – Not good enough and not righti. Those people are not going to exist againc. Going to do it for an expedition that will run in the futurei. This May is too soon too8. Processa. Sub-activitiesb. Componentsc. Transformationi. Some may be to correctii. Some may be to let those results go on to the next phase of the systemiii. Some may to get more out of the environmentMeet with Sampson WITH your Model. “Close” does not mean A. “Close” means that the system is almost logical and complete.