Describe a PLC system with diagram

profilejacobeast916
ENS5253CaseStudyReportandInfo1.pdf

Control Systems Case Study Report and Information

Semester 1, 2020 1 Copyright © Edith Cowan University

CASE STUDY REPORT CONTROL SYSTEMS

Ref: Kirkup (1994). Experimental Methods: An Introduction to the Analysis and Presentation of Data. Brisbane: John Wiley & Sons.

A case study report is required to be submitted by each student as one of the assessment items for this unit. The report will be assessed and marked out of 10%.

The format of the report is that of an engineering/scientific report. All aspects of your report must be your own original work. You must acknowledge any assistance that you received, and must provide appropriate referencing for any copyright information that you include in your report.

One of the primary goals of the project is to get you to perform “inquiry or problem- based learning” through this project. You investigate the problem, and when you reach the limit of your knowledge, you will need to backtrack and re-examine the problem. You should determine explicitly what you need to know at each stage, and then search for information from the sources at your disposal – the lecture notes, textbook, other references, the library, the internet, etc. We understand that you may not know everything you need to know at this stage, but your learning should accelerate as you progress through the project.

What Your Report Should Contain You are required to include the following information, and structure your report as described:

Assignment Cover Sheet – download from the Unit page on Blackboard. Case Study Report Template – download from the Unit page on Blackboard then:

• Edit the Word file and adjust it to your project realisation.

• Keep the number of words within the limits indicated next to each paragraph title.

• Follow the guidelines below and keep the report as professional as possible.

Introduction

• Short summary of the purpose or function of your proposed system – what goals are you trying to achieve.

• Include background information on previous work, including references.

Case Description

• Description of the procedures and apparatus to be used. Include a diagram of your proposed case study.

• Based on the case study goals, define what you intend to control. Include a description of the operating range (and any other properties) of your defined control processes.

• If you use software, describe the software and what you need to include in the software to achieve your stated goals. You should map out a plan of the functions you want the software to perform. This can be a flow diagram.

Control Systems Case Study Report and Information

Semester 1, 2020 2 Copyright © Edith Cowan University

References Reference all material that you use from other sources. Use the correct referencing method defined by the University (or Kirkup)*.

Appendix • Include any information that you feel is important for interpreting the report that does

not actually belong in the body of the report; i.e. important datasheets and other equipment information.

Overall Organization and Presentation

• Use a word processor – this makes editing and rewriting easy and efficient – it also allows you to submit the report electronically. This also allows you to pass copies of the report between group members so that everyone can contribute to the editing. Your report must be submitted individually as a Microsoft Word formatted file or a PDF file (preferred).

• Length: The length of your report should have a maximum of twenty A4 pages, single spaced, including figures (diagrams and graphs). Do not make it too long – use appendices if needed.

• Page Size and Margins: Page size should be A4, with margins of 1 inch (2.5 cm) all round.

• Font: Font size should be 12 font either Times Roman, Arial, Courier or similar – that is, readable.

• Page Numbers: Already at the bottom of the page of the template file. • Section Headings: Be consistent in the labelling of sections, whether you use

section numbers and a heading or just a section heading. • Where appropriate, use footnoting within the text. • Spell correctly, and use correct grammatical structure. • Neutral (third) or second person (“we”) – neutral is preferred. • Do not use dot points – write proper sentences (dot points are OK in laboratory

notebook, but not in reports). • Paragraphs: There are two conventions for defining a paragraph: (1) Begin

paragraphs on the left margin and have a blank line between paragraphs, or (2) indent the first line of a paragraph (0.25 to 0.5 cm) with no blank lines between paragraphs (or a half line between paragraphs). Be consistent in the method you choose.

Equations • Create equations using an equation editor. • Equations should be on a new line, numbered sequentially on right, with the

line right justified. The number should be in brackets, e.g. (1). • Identify symbols when they first appear.

• Express numbers clearly – e.g. 6  1023, not 6e23 or 6*10^23. • Use appropriate units on all numerical values. • Express numerical values to the appropriate number of significant figures. • Equations form part of the text; that is, the presence of an equation should

appear as if it is part of a sentence, even though it is on a separate line and is numbered. If the equation is at the end of a sentence, it should be followed by a full stop; if it is in the middle of a sentence, then a comma may be required.

Control Systems Case Study Report and Information

Semester 1, 2020 3 Copyright © Edith Cowan University

• In the text, refer to the equation by its number. “As discussed earlier, Equation (1) indicates that …”

Tables • Numbered (using roman numerals) in sequence – e.g. “Table II”. • Title at top of table – to right of or under table number. Again, the title is actually

a caption that describes what the table is displaying. • Results presented with errors (uncertainties) and units. • Literature values (footnoted) may be included for comparison. • Make sure that all captions stay with the appropriate table on the same page. • Refer to all tables appropriately with their numbers in the text; i.e. “Table II

shows data on …” not “in the table below”. • Tables are separate from the text.

Figures • Create graphs with a graphing program (e.g. Excel, MATLAB). • Numbered (using Arabic numerals) – e.g. Fig. 1. • Include figure caption – a description of what the figure shows. • Figure number and caption centred at the bottom of the figure. • Provide a “key” or “legend” for each graph, including curve fits (this can be

included in the figure caption). • Axes clearly labelled, including units – use appropriate ranges, scales and

number formats for axes data labels. • The data should fill the graph. • Data appears as symbols, trend lines appear as lines. • You only need a legend if you plot more than one set of data. • Refer to all figures appropriately with their numbers in the text; i.e. “as shown in

Figure 1” not “in the diagram below”. • Make sure that all captions stay with the appropriate figure on the same page. • Figures are separate from the text; embedded into the text.

*Referencing Techniques:

The University has a referencing method based on the Harvard system. You can use the Harvard system if you prefer. The Harvard system works like this: (Smith, 2014). Then in the reference section you have the list in alphabetical order of the first author. The advantage of this is that you don’t need to keep track of numbers.

However, the Vancouver referencing system is the preference in scientific and engineering publications. A reference number is used in text with square brackets [1]. The reference section is then a list of the references in numerical order. You can number them in the order they appear in your report (the easiest) or you can have them numbered in alphabetical order in the reference list, then use the appropriate number where the reference occurs in text (much more complicated).

If you take a diagram or image from another copyright source, you must include a reference to the source of this material. Failure to do so is plagiarism and copyright violation.