1 middle east technical university department of industrial engineering 06531 ankara / turkey ie 497...

1Middle East Technical University

Department of Industrial Engineering06531 Ankara / Turkey

IE 497 - 498Systems Design

2012 - 2013Lecture 4

IE 497 - 498 Systems Design



Agenda

Feedback on Fall semester project work, final presentations and reports:

IE 497 presentation evaluation resultsIE 497 gradesFeedback and suggestions from the faculty advisors

Spring schedule and final report writing




IE 497 Presentation Evaluation ResultsFall 2012 midsemester presentations:

Average scoreSistem tanımı ve bütününün incelenmesi 4.07Proje amacının kuruluşa uygunluğu

4.21Problem belirtilerinin incelenmesi

3.79Proje başarı ölçüsü önerileri

3.66Öngörülen proje çıktısı

3.75Veri kaynakları ve derleme öngörüsü

3.64Literatür tarama

2.72Karşılaşılabilecek güçlüklerin ve kısıtların

öngörülmesi3.54

Proje planının uygunluğu3.82




IE 497 Presentation Evaluation ResultsFall 2012 final presentations:

Average scoreProblem tanımı

4.16Mevcut sistemin analizi

4.05Projenin teknik içeriği

3.96Kaydedilen ilerleme 4.03Proje planı

4.17Sunumun etkililiği

3.96Soruların ele alınışı 4.13




AA BA BB CB CC DC DD0

5

10

15

20

25

30

35

16

22

29

11

5

0 0IE 497 Grades - Fall 2012


Number of students: 83



IE 497 Grades - Fall 2011


Number of students: 84

AA BA BB CB CC DC DD0

5

10

15

20

25

30

35

40

3

22

37

2

13

3 4



Faculty Feedback and SuggestionsWork harder

You should not hesitate to undertake hard workYou may have to learn new methods, tools and software packages to get what needs to be doneSD is a major link to industry, let us try not to lose face

TeamworkYou do not have to like each other, but you still have to work together as professionalsBe prepared for team meetingsDistribute load equally among team membersWork done and report sections written by individual members of the team need to be connected




Faculty Feedback and SuggestionsAnalysis of the problem situation

Using IE 398 tools (system elements, boundary and so on) is not sufficientConnect these to work that follows, use other toolsDraw useful conclusions from your analysis

"Haa, demek ki öyle!"

Statistical analysisDescribe data needed from the organization in a precise manner and submit written requests Question and interpret data analysis resultsConduct statistical estimation and hypothesis testing to draw useful conclusions

"Acaba öyle mi?”




Faculty Feedback and SuggestionsPresentations

Presentation skills are above the average, but...Technical content should be strengthened with better system and data analysis (more expected in Spring)More numerical results are needed to support symptoms and problemsGo over your slides with your faculty advisorsUse available time more effectivelyDo not talk fast, stick to the main points but support them betterDo not be defensive, make sure you understand the question before answering itAttend other teams’ presentations




Faculty Feedback and SuggestionsReport writing (more on this later)

Check lists in SD Handbook are not section headingsBegin by preparing an outline of sections and subsections, including figures, tables and appendicesBefore starting, discuss who is going to write what under which sectionMake sure that terminology is consistent throughout the reportAvoid redundant repetitionsEdit and correct on hardcopy before submissionIntroduction and problem situation sections are in particular problematicDo not put all figures and tables in appendices




Spring Schedule

See updated calendar

Poster: Friday, March 8thLecture 5: Friday, March 15thMidsemester report: Monday, March 25thMidsemester presentation: Friday, March 29thFinal report draft: Wednesday, May 8thFinal presentation: Friday, May 17thFinal report: Friday, May 24th




Project Poster

On standard size A1 paper (594mm x 841mm), portrait orientation, in TurkishIt will be a display (drawings, schemas, pictures, graphs, tables, demonstrations, short texts, etc.) of the progress you made in your projectIt should contain

Full project title, team members, sponsoring organization and advisors

Some text or graphics to highlight the essence of the problem

An indication of the goals and potential outcomes

Potential solution approach and its prospective impact




Midsemester Progress Report

This report should not exceed 15 of 1.5-spaced pages (excluding appendices)It should contain

Problem definition and formulationSolution (or design) approach and modelingInitial findings from solution trialsThe extent of meeting the goalsA vision of how the implementation of the solution will be initiated in the sponsoring organization

See Appendix B of SD Handbook for the report format




Final Report

This report should not exceed 50 of 1.5-spaced pages (excluding appendices)It is comprehensive (covers both semesters)It should be impeccably and professionally prepared It should contain clearly stated arguments, suggestions and comparisons“So what?” questions should have meaningful answersGo over the checklist in SD HandbookSee Appendix B for the report format and the title page




Final Report Organization

Typical sections: You can (and you should) change any part as you see fit for your project1. Introduction2. Overview of the Organization3. Analysis of the Problem

Situation4. Problem Definition5. Solution (or Design) Approach6. Results7. Implementation Plan8. Conclusion

Also, an Executive Summary in Turkish





1. IntroductionTo the report, not to the sponsoring organization

What work is the report about?

What is the scope of the work done?

Why is this work done (motivation)?

What is the main purpose of the work done?

How is the work done (brief decription)?

What are the main findings and conclusions?

How is the rest of the report organized?

About two pages





2. Overview of the OrganizationFacts that are relevant to the project, such as

Brief history

Ownership

Physical facilities

Organizational units

Products and/or services

Markets and customers

Business volume (number of workers, amount of sales, etc.)

Two to three pages





3. Analysis of the Problem SituationAnalysis results that are relevant to the project

Problematic “issues” encountered at the work place with their system-wide effects

History of these issues

Complexity of the issues

Internal and external relationships and interactions

Uncertainties and difficulties

Trade-offs and conflicts





3. Analysis of the Problem Situation (continued)Customer/stakeholder expectations, needs or requirements

Analysis of observed or potential effects (symptoms) of problems and their causes (sources)

Description of collected data to further understand the system and assess the current performance, and results of data analysis

Summary diagrams such as rich pictures and mind maps





4. Problem DefinitionHierarchy of systems and boundary judgments

Diagrams that describe the inputs, outputs, components of and relationships in the system of interest

As a result of the above analyses, definition of your problem as (these are only generic examples)

to develop a solution approach for the problem(s) of the organization

to improve existing product, process, service or system(s) of the organization

to design new product, process, service or system(s) for the organization





4. Problem Definition (continued)Problem structuring or formulation including components such as

goals/objectives

performance measures

restrictions

alternative courses of action





5. Solution (or Design) ApproachJustified choice of the solution approachProper representation of your model(s), e.g.

Pictorial or graphical representations of proposed product, process, service or system(s)Notation, formulation, explanation of objective function and constraints for a mathematical programming modelNotation and flowchart (or pseudo code) of a heuristic solution algorithmNotation, flowchart and description of modules for a simulation modelPostulated relationship equations to test hypotheses, to predict and/or optimize system responseDecision tree diagramsInputs, outputs and formulations for spreadsheet computation





5. Solution (or Design) Approach (continued)Estimation of input parameters (if any) for your model(s)Verification and validation of your model(s)





6. ResultsExpected results in terms of performance measures based on the following (when applicable)

Scenario analysis

Sensitivity analysisExperimental design and statistical analysisBefore/after comparison or comparison with benchmark data

Interpretation and discussion of results, proposed solution/design alternatives with cost-benefit analysisConfirmation of expected results based on pilot implementation (if possible)





7. Implementation PlanGuide to technical staff who is expected to implementyour suggestionsDiscussion of supporting and counteracting forces and factors for implementation of suggested solutions or designs Restructering and procedural changes required for implementationDesign of control mechanisms to monitor and improve the system performanceResource requirements for implementationTechnical, operational and financial feasibility





8. ConclusionSummary of work doneMain findings and conclusionsFuture work: what else needs to be done?About two pages





Executive SummaryIn Turkish, three to five 1.5-spaced pagesProvide the essence of the project, approach, suggestions and conclusionReader should grasp the problem and the proposed solution, and be able to judge it just by reading this





Do not take this report organization as a definite template, make changes as you see fitTry to write sections of the report throughout the semester, do not wait until the last week




Important!

The above report organization is given in a “linear” fashion, but remember that system design is “circular” or iterative by natureTherefore, as you do the actual analysis and design work, you will often have to return to the previous steps and revise the contents of Sections 3-7 accordingly


1 middle east technical university department of industrial engineering 06531 ankara / turkey ie 497...

Documents

systems design slide

ankara turkey faculty

ankara turkey agenda

ankara turkey project

ankara turkey spring

technical content

suggestions report

final presentations