you will find 2 documents the 1st one is a memo. technically the memo is the instructions for the project and then after you red the memo you need to build the project based of the memo needs and the other document is the rubric.
INFO 300 LAN Project Grading Rubric Minimum Specs The drawings, budget, and summaries are of no value in a portfolio if they are sloppy or inaccurately drawn and won't earn points for the project. Hand-drawn diagrams, or hand-drawn marks on the printed copy, are not acceptable. Projects will be rejected if the pdf copies are not properly formatted, for example with font too large or a column too narrow to fit a column of extended costs without wrapping on a line, or without the customary columns. Where connectors are used to represent network drops on the floorplan or jumpers on the rack they must be drawn with straight connectors with curved bends. Do not use curved or freely drawn connectors. Place network drops close to walls where they'll be supported on hooks. Do not use red or yellow for drops or jumpers. Green, blue, or orange are better colors. Black & White drawings are fine if the drops and jumpers are shown clearly. Projects that don't meet these minimum specs will not be accepted and will be docked daily for late submit until they do. Required Parts: 1) Cover page describing the project. 2) Detailed Total Cost of Ownership for project. 3) Warehouse Floorplan. 4) Network Rack Diagram · Summarize up-front and recurring costs separately. Projects that do not provide these summaries in the customary format will be rejected at first submission. The Boss wants to be able to compare your up-front and on-going costs with others without getting out a calculator! · Make sure the printed diagrams fill the pages and are easily usable as printed. The printed dimensions of the warehouse walls must be 8 3/4 X 6 inches. Make 'skeletons' of your floorplan and rack diagram and try printing them _before_ putting much effort into the details and try printing them. Projects that can't be read as printed without a magnifier or do not fit on the printed page will be rejected · On the floor plan, after drawing the walls place telecom outlet symbols on the walls where each ethernet jack will be placed. Place them to avoid pulling jumpers along the wall, around a corner, or over the floor to connect equipment. After the telecom outlets have been placed, put a wall segment in the network room to represent the rack, place a connection point on it and move it to the layer with the Telecomm outlets (data and flow terminals), then lock the walls and turn off their snap and glue. Use straight connectors between the connection point in the network closet and the telecom outlets, and format them with curved bends. Represent the bundles and drop wires separately by bundling together the drops or by using a thicker connector to represent the bundle and peel each drop off it. Do not draw bundles or drops on top of the walls, keep them inside the premises and clearly visible. · After placing equipment on the rack diagram, place connection points where each jumper connects to equipment or patch panel. Use callouts or other neat technique to label each ethernet port with its IP assignment. Do not label the jumpers. Format straight connectors with curved bends for jumpers, not thin or with right-angled bends. Avoid crossed connectors, kinks, and extra bends to make a neat drawing. An 'electronic' copy as a single pdf that contains all requested parts: Floor plan with furnishings, premises wiring, and wall jacks; Rack diagram clearly indicating the DMZ and IP addresses; and an accurate Summary of Upfront and Ongoing Costs. Submit electronic copy to the instructor by midnight on April 1, 2021. Designing a Network A Project to design and implement a network Poor 10 pts Fair 15 pts Good 20 pts Great 25 pts Design This portion reflects the design portion of the project including rack design, computer layout, warehouse layout, and wiring diagrams. Poor Little or no design present one requirement present. Fair Basic design, at least two requirements are present. Not updated. Good Design is mostly complete, at least 3 requirements are present some updates, but not current. Great Design is complex, includes neat and clear documentation for jacks, network rack, and overall equipment layout. Easily readable with legend to represent symbols that are not clearly defined. Hardware The hardware part of the project includes building the Network and specifying the hardware . this portion of the rubric reflects whether only the hardware works correctly. Poor Only one or two hardware components have been implemented, network logical design will not communicate. Fair All network hardware has been implemented; however logical IP addressing will not work as designed. Good Project is built, all hardware components are implemented network logical design will communicate but numerous problems are present does not match design. Great Network hardware in correctly implemented all components communicate network logical design will communicate and is overall consistent with the design. Budget This is the software component of this project. Students will install server and client software and make appropriate network connections Poor Budget is missing several components and is not clearly represented to understand the TCO or overall financial cost of the project. Fair All budget items are present but not clearly represented or laid out to understand TCO or capital vs recurring costs are not clearly identified. Good All budget items are present and TCO is identified but overall layout is no easy to read or follow. Great Budget contains all up front and recurring costs clearly laid out in an easy to read and understand format. Total cost of ownership is easily identified, and no financial questions are left unanswered. Overall Proposal Proposal should be presented in business like format and should flow. It should identify the scope of the project and the overall “solution” you are proposing. Poor Project submitted is not cohesive and does not present a solution to the problem. Fair Short paragraph only addressed one or two required components. Completed some but not all of the components and did not present a cohesive project that addressed the problem. Good Project Proposal was well but missed one or more key components or did not completely solve the problem. Solution was missing components or did not transition well when reading. Great Personal reflection was well written with all required components. Project proposal solved the problem and presented a concise easy to read plan and cost of implementation Honor This is 100% an Individual Project. It is not a group or team project . Learning to use Visio or other CAD tool, an ability to read and follow instructions, and getting questions answered are part of this exercise. Technical skills are not developed by watching others do them and this is an opportunity to practice and develop technical skills and learn about costs and capabilities of LAN components. Every key stroke and mouse click should be from the student submitting the project. Do not submit any portion of any files from another student, in any degree of completion, as your own, with or without changes. Never give another student your files in any degree of completion! A lamer/cheat who can't do this work is likely to submit your work as his or her own and you'll be dragged into an honor proceeding for 'facilitating academic dishonesty'. If another students wants to see your project, show it only if you'd like, and help by answering questions. Helping others learn the tools or about the products involved in the project is a very Ram thing to do, will make more winners on our team, and is one of the best ways of learning more! Students are welcome to discuss the project and work with others, but each of them should be working at their own PC or notebook and never share the files involved, in any degree of completion, or touch another student's keys or mouse. TIPs · Be careful when choosing the starting project from the options Visio presents. If you choose something like 'floor plan' the scale will be set wrong for a rack diagram. If you choose 'rack diagram' the scale will be wrong for a floor plan. Make sure _as you __start__ your drawing_ that the scale is appropriate and that your drawing will be usable on the printed page or pdf. · For Engineering Quality drawings: Learn to 'scale the drawing' so that graphics are the appropriate size and the dimensions printed are accurate. The drawing from The Boss, scanned from an 8 1/2 X 11 sheet of paper, pretty much fills the page and doesn't usually require changing from Visio's default scaling factor to make a good-looking diagram. Marks on the drawing show the scale. If you want to make measurements exact use Visio's Design -> Page Setup flyout -> Drawing Scale tool to set the scale exactly. It's about .1 inch, 10 pixels, to a foot. Use Custom Scale to adapt to a hand-drawn diagram. Another approach is to add a line to the drawing, size it to the longest measurement on the drawing on the background, then scale the drawing to fit it exactly... · Use 'rulers' to help align your walls and objects. Drag them into the diagram from the rulers at the edges. Shapes will snap to rulers unless 'snap to' has been turned off. · Shapes important for the assignment as demo'd in class are: Maps & Fooorplans -> Building & Walls, and Electrical and Telecom; Network -> Rack Mounted Equipment. Callouts for labelling ip addresses annd other details, are in the default set of shapes on earlier versions of Visio, have been moved to 'Extras' for the latest version. · Getting shapes for equipment from VisioCafe.com is a really good idea! You can get all your points for this project with generic shapes from Visio, but rack diagrams where all components are from VisioCafe are the best looking if they're accurately drawn and will really pop for the instructor or technical interviewer who's grading your documents relative to all they've seen. · Use Layers to your advantage: Start from the background and work up, locking each layer as it's completed. Almost 100% of problems with placing connection points and connectors are because too many layers are left unlocked without snap-to disabled. Complex diagrams without layers are unmanageable. Visio automagically creates a layer for each of the shape templates used... · Make sure your floor plan is a faithful representation of the floor plan sketched by The Boss, all proportions exactly resembling the sketch. Don't submit a diagram where the walls appear to be several feet thick, join at odd angles, make 'blind hallways', or otherwise don't match the Boss' sketch. 'Tracing' is the pro's technique to ensure accurate dimensions: Most drawing application allow an image to be loaded onto a background layer so that the app's drawing tools can be used to create objects that exactly resemble a photo or sketch. Use Visio's Insert dialog to put the boss' sketched floorplan