Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR Final Year Project Report Format (Project Stage I)
1. Introduction
This document describes the standard format for projects reports to be submitted as part of the fulfillment of the B.Tech Degree at the Department of Computer Science and Department of Information Technology of PIET. Students have to ensure their reports conform to the required format before submission for examination.

2. Project Report
2.1 Typing Instructions and Length of the Report The total length of the main report shall not exceed 300 A4 pages. The text of the main report shall be spaced 1.5 lines, with a font VERDANA of size 10 and justify alignment for normal text with 1 inch top, left, right and bottom margins. All the titles must be of size 14 verdana font and bold. The subtitles must be of font verdana with bold effect and size 12. All the specific terms or definitions must be with italic effect. Appendices and other manuals can be in single space and a smaller font size. Appendices should be kept small and bounded together with the main report. However all the documents including Team Formation, Project Scenario, Survey Report, Project Charter, SRS, Use case reports and other documents should be contained in the CD. Student must write their Project Team No., Project Title, Team Members name, registration number, branch, section, academic year and college name on the CD. All the pages of main report will have header and footer. The header must include Final Year Project Report (Project Stage I), Academic Session 2011-12, PIET, Jaipur using font cambria, regular, size 8 and right aligned. The footer must include Page No. (font cambria, regular, size 8 and center aligned) and Team No. (font cambria, regular, size 8 and right aligned). Please consult your project guide if you are unsure which materials you should include in the main report and appendices and the length of appendices. The report should be clearly written, and should include only relevant information. Indeed the inclusion of too much detail may cause the evaluation committee to doubt whether the student has really learnt how to distinguish the important issues from the trivial ones. 2.2 Format All final year project reports must be prepared in the following sequence: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Front Hard Cover Page (CE Light Sky Blue, IT Yellow) Title Page Certificate Preface Acknowledgement Abstract Table of Contents List of Tables List of Figures List of Symbols, Abbreviations and Nomenclature Alumni Details Client Details (Project Charter)

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

MAIN 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26.

REPORT Introduction to the Project Client Survey / Result (Details) Requirements of Client (Project Objectives) Decomposition of functional requirements Modules, Division Work plan and work assignment (PERT, CPM, WBC) Software Requirement Specification Client comments Guide comments Expert comments FAQs About Projects References (Market, System, Website, Books) Appendices The back hard cover

Some of the important points on the report format are explained in the following sub-sections. 2.2.1 Front and Back Cover and Binding Hard binding should be used for all reports and appendices. As sketched in the sample pages, the words FINAL YEAR PROJECT REPORT (PROJECT STAGE I) (font size 11, bold, upper case, center aligned), the project title (font cambria, font size 14, bold, upper case, center aligned), the students name (font size 11, bold, center aligned), the words DEPARTMENT OF COMPUTER ENGINEERING OR DEPARTMENT OF INFORMATION TECHNOLOGY, POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR (font size 11, upper case, center aligned) and the academic year (font size 11, center aligned) should appear on the front cover. Front Cover of the Report Sample (Annexure 5.1) 2.2.2 Title Page The first page of the report should be a title page. It should consist of the words FINAL YEAR PROJECT REPORT (PROJECT STAGE I) (font size 11, bold, upper case, center aligned), the project title (font cambria, font size 14, bold, upper case, center aligned), the students name (font size 11, bold, center aligned), the words DEPARTMENT OF COMPUTER ENGINEERING OR DEPARTMENT OF INFORMATION TECHNOLOGY, POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR (font size 11, upper case, center aligned) and the academic year (font size 11, center aligned) and Project No, Guides name (font size 10, bold, left aligned), and deliverables (e.g., number of document volumes, software, hardware and etc.) (font size 10, left aligned) should also be included. The cover page should fit on one page. Title Page Sample (Annexure 5.2) 2.2.3 Certificate The Certificate shall be in 1.5 line spacing using font verdana and font size 11. The certificate shall carry the guides signature and shall be followed by the guides name, academic designation (not any other responsibilities of administrative nature), department and name of the institution. The term Project Guide must be typed in capital letters between the guides name and academic designation. The Certificate from the Client Carrying the necessary information as per the above that of guide. The Alumni Certificate from at-least one alumni, who act as a consultant and advisor for the project. (with details) Certificate Sample (Annexure 5.3)
2 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

2.2.4 Abstract It consists of an abstract of the report of not more than 200 words outlining the project. The abstract should be comprehensible to readers of the report and enable them to judge the reports potential interest. The Keywords and Subject Descriptions should follow immediately after the abstract in the same page, each with not more than five careful selected items. Any suitable word that reflects the nature and content of the project may be chosen as a keyword. The student should consult the project guide when in doubt which keywords and descriptors be used. It should be kept in one double-spaced A4 page with verdana font size 10 and aligned as justify. Abstract Sample (Annexure 5.4) 2.2.5 Acknowledgement Following the abstract page, students may want to acknowledge the contributions or assistance of others to the project. It should be kept in one double-spaced A4 page. All the team members must sign on the acknowledgement. Acknowledgement Sample (Annexure 5.5) 2.2.6 Table of Contents In addition to the heading of each section, sub-heading can also be used but its depth should be kept to a minimum. Details of appendices should also be given here. Students may use more than one A4 page for the content page. Table of Contents Sample (Annexure 5.6) 2.2.7 List of Tables The list should use exactly the same captions as they appear above the tables in the text. One and a half spacing should be adopted for typing the matter under this head. 2.2.8 List of Figures The list should use exactly the same captions as they appear below the figures in the text. One and a half spacing should be adopted for typing the matter under this head. 2.2.9 List of Symbols, Abbreviations and Nomenclature One and a half spacing should be adopted or typing the matter under this head. Standard symbols, abbreviations etc. should be used. 2.2.10 Main report The structure of the main part of the report will vary according to the nature of the project. It is both convenient and conventional to organise the report in a hierarchical structure: Chapters, Sections, Sub-sections, and etc. In general, there should be an Introduction giving an overview and background of the project. Also, there is generally a section for Conclusions, and one for Recommendations where appropriate. Students should consult their project guides on how to structure 2.2.11 Appendices

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Information of secondary importance (and information whose inclusion would break the flow of the report) should be placed in Appendices. These include programme listing, electronic data sheets and data dictionary etc. Appendices should be numbered using Arabic numerals, e.g. Appendix 1, Appendix 2, etc. Appendices, Tables and References appearing in appendices should be numbered and referred to at appropriate places just as in the case of chapters. Appendices shall carry the title of the work reported and the same title shall be made in the contents page also. 2.2.12 References The references section includes the references of market where you studied about the project, systems which are not part of the project but it is used. A list of all books, report, papers, etc., referred to in the report or consult during the course of the project should be given under the References or Bibliography section. The reference material should be listed in the alphabetical order of the first author. The name of the author/authors should be immediately followed by the year and other details. A typical illustrative list given below relates to the citation example quoted above. REFERENCES 1. Ariponnammal, S. and Natarajan, S. (1994) Transport Phonomena of Sm Sel X Asx, Pramana Journal of Physics Vol.42, No.1, pp.421-425. 2. Barnard, R.W. and Kellogg, C. (1980) Applications of Convolution Operators to Problems in Univalent Function Theory, Michigan Mach, J., Vol.27, pp.8194. 3. Shin, K.G. and Mckay, N.D. (1984) Open Loop Minimum Time Control of Mechanical Manipulations and its Applications, Proc. Amer. Contr. Conf., San Diego, CA, pp. 1231-1236. 2.2.13 Table and figures By the word Table, is meant tabulated numerical data in the body of the project report as well as in the appendices. All other non-verbal materials used in the body of the project work and appendices such as charts, graphs, maps, photographs and diagrams may be designated as figures. 2.2.14 Page number and Section number The maximum number of pages for main report is 300. The page number here starts from the first page of Introduction to the last page of conclusion/summary. All other pages like abstract, contents, list of figures, list of tables, list of abbreviations, acknowledgements, list of references, bibliography, are not counted in these 100 pages. Please number 1, 2, 3, to 300 (the maximum) for your main report and number i, ii for all other pages in front of the main report. You are requested to continue your main report numbering for reference/bibliography pages that come at the end. A hierarchical numbering scheme for chapter numbering shall be used. For instances, use 1 for chapter one, 2 for chapter 2, 1.1 for the subsection of chapter 1, and etc (See the Table of Contents).

3. Deliverables
3 Copies of the Group Report.(Department /Guide/ Library). Each Group Report should Contain the CDs which include the Team Formation, Project Scenario, Survey Report, Project Charter, SRS, Use case reports and other documents. Project Team No., Project Title, Team Members
4 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

name, registration number, branch, section, academic year and college name must be clearly written on the CD. One copy of the Individual Report. The table and figures shall be introduced in the appropriate places.

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.1: Final Year Project Report Format (Front Cover of the Report Sample)

FINAL YEAR PROJECT REPORT (PROJECT STAGE I)

DEVELOPMENT OF A DATABASE LINK USING TYPE 4 DRIVER IN A 3-TIER ARCHITECTURE

Submitted in partial fulfillment of the degree of Bachelor of Technology Rajasthan Technical University

By Donald Singh Rathore (CE/07/444)

DEPARTMENT OF COMPUTER ENGINEERING POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR (Academic Year 2011-12)

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.2: Final Year Project Report Format (Title Page of the Report Sample)

FINAL YEAR PROJECT REPORT (PROJECT STAGE I)

DEVELOPMENT OF A DATABASE LINK USING TYPE 4 DRIVER IN A 3-TIER ARCHITECTURE

Submitted in partial fulfillment of the degree of Bachelor of Technology Rajasthan Technical University

By

Donald Singh Rathore (CE/07/444)

DEPARTMENT OF COMPUTER ENGINEERING POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR (Academic Year 2011-12)

Project No: <Team No.> Guide: Mr./Ms. <Guide Name>

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.3: Final Year Project Report Format (Certificate Sample) RAJASTHAN TECHNICAL UNIVERSITY POORNIMA INSTITUTE OF ENGINEERING & TECHNOLOGY, JAIPUR

CERTIFICATE

This is to certify that Final Year Project Report (Project Stage I) entitled DEVELOPMENT OF A DATABASE LINK USING TYPE 4 DRIVER IN A 3-TIER ARCHITECTURE has been submitted by Donald Singh Rathore (CE/07/444), XYZ (CE/07/445) for partial fulfillment of the Degree of Bachelor of Technology of Rajasthan Technical University. It is found satisfactory and approved for submission. Date: <Date>

Mr./Ms. <Guide Name> PROJECT GUIDE <Designation>, <Department> PIET, Jaipur

Mr./Ms. <HOD Name> Head, <Department> PIET, Jaipur

Mr. Manoj Gupta Director, PIET, Jaipur

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.4: Final Year Project Report Format (Abstract Sample)

ABSTRACT
A prototype system has been developed to connect an IBM PC or compatible to an IBM 3081 mainframe computer for making direct database accesses. The system includes programs which run on both the PC and the mainframe to allow communications and to forward database access queries and the results of the queries. The system was developed based on the ideas which have been used in different microcomputer packages. However, no existing system includes the widowing functionality, or the interactive capabilities have been developed here. The system was developed in Turbo Pascal for the IBM PC, and IBM Pascal on the main frame. The design criteria and the implementation details are presented in this report. Subject Descriptors: 8 CS 1 Distributed Systems 6 CS 4 Web Technology 5 CS 4 Database Management Systems 4 CS 3 Software Engineering Keywords: Distributed databases, micro-mainframe link Implementation Software and Hardware: IBM PC/XT, MS_DOS 3.1, MS-Windows, Turbo Pascal 3.0.1, IRMA Card, IBM 3081, VM/CMS, IBM Pascal

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.5: Final Year Project Report Format (Acknowledgement Sample)

ACKNOWLEDGEMENT

A project of such a vast coverage cannot be realized without help from numerous sources and people in the organization. We are thankful to Mr. Shashikant Singhi, Director General, PGC and Mr. Manoj Gupta, Director, PIET for providing us a platform to carry out such huge projects successfully. We are also very grateful to Mr. Mohit Garg (Dean, PIET) and Mr. Deepak Moud (HOD, CE)/Ms. Pooja Sharma (HOD, IT) for their kind support. We like to take this opportunity to show our gratitude towards Mr. Puneet Mathur (Coordinator, Training & Project, PIET) who helped me in successful completion of our Final Year Project Stage - I. He has been a guide, motivator & source of inspiration for us to carry out the necessary proceedings for the project to be completed successfully. We are also grateful to the <Project Guide> for their guidance and support. We are thankful to <Domain Expert> for their kind support and providing us expertise of the domain to develop the project. We are also privileged to have <Faculty Member(s)> who have flourished us with their valuable facilities without which this work cannot be completed. We would also like to express our hearts felt appreciation to all of our friends whom direct or indirect suggestions help us to develop this project and to entire team members for their valuable suggestions. Lastly, thanks to all faculty members of Computer Science department for their moral support and guidance. Submitted by:

Team Members: <Team Leader> <Team Member> <Team Member> <Team Member>

10

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Annexure 5.6: Final Year Project Report Format (Table of Contents Sample)
Table of Contents Description Title Abstract Acknowledgement List of Figures Chapter 1: Introduction 1.1 The use of Database Links 1.2 Mainframe and PC Intercommunications 1.3 Other Distributed Database Procedures Chapter 2: Study 2.1 2.2 2.3 2.4 | | | Chapter 20: Chapter 21: Testing Methodology Conclusions 21.1 Summary 21.2 Limitations 21.3 Recommendations for Further Work 80 89 89 92 95 v vi vii of Existing Packages Framework Machintosh Smalltalk General Windowing Features Page No. i ii iii iv 1 1 3 4 5 5 7 8 9

References Appendix A Appendix B

11

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Introduction:
RFID is a technology that is sparking interest in the library community because of its applications that promise to increase efficiency, productivity and enhance user satisfaction. Globally emerging knowledge-based societies of the twenty first century will need information to sustain their growth and prosperity. With intellectual capital as investments, knowledge and information have become wealth generators. In this scenario, who can deny the importance of libraries, which are repositories of reference resources? A library stacked with books and other information dissemination processes, has a physical presence. A library is an institution of knowledge acquisition and learning; it provides invaluable service to its members, patrons and to a wider local community. Current library management systems use barcode technology and security strips. Using barcodes, a library management system can keep records of lending, borrowing and shelving status of items such as books, audio or video tapes, CDs, DVDs, etc. Security strips on library items tag their movements. But barcodes and security strips (electronic article surveillance or EAS) have their limitations. They are slow to read and are prone to sabotaging by thieves. All these lead to irreparable loss to a library and its valuable inventory stock. This is where RFID technology can come to the aid of library managers and users. Many libraries are switching over to RFID applications, for example, the Vatican Library. With its priceless, ancient collections of 2 million books and manuscripts, the Vatican Library is now using RFID to track, manage and secure its assets. The main problem these ancient libraries face are thefts, non-returns and misfiled items. It is expected that by adopting an RFID solution the Vatican Library will be able to control misuse of its library and at the same time provide its users the best possible facilities and access to rare manuscripts. In the ensuing discussions we will see how RFID technology is recommended for library automation. RFID technology is not just there to tags books and other library assets; it will provide a comprehensive route for enhancing all library services and upgrade operations for everyone concerned with the library.

Issues:
During a day, library managers have to supervise many activities within their libraries. These activities have to be performed smoothly and simultaneously for the benefit of all persons concerned. Some of the important functions in a library are: check-in/check-out of items Shelve items Prevent thefts Check inventory

If each of these functions is done by conventional methods, they will take time and lead to inefficiencies and unsatisfactory services to the library patrons.
12 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Let us see how check-out of items is done with barcodes and EAS. Scan Patron Card --> Receive Materials --> Locate/Scan Barcode --> Deactivate Security --> Return Materials --> Date Due Receipt It is a six step process. This is tedious and slow. If by using RFID technology this process is made for time-efficient, then it could be recommended. As far as shelving is concerned, in a conventional library, it is done manually. In most busy libraries, many books, DVDs, audio cassettes and videos must be shelved everyday. This is a time consuming task. Misplacement of items, misshelving of books, is quite common. Not only this, repetitive re-shelving task can be health risk to library staff. If automated, all these problems can be avoided. In each and every activity within a library, RFID technology will provide a greater amount of efficiency and error free functioning. It will ensure that there is: Quick check-in/check-out of items for convenience of members Quick and correct shelving of items Complete prevention of thefts Quick inventory check RFID tags contain a memory chip and RF antenna that can send and receive several bits of data. Such RFID tags are known as smart labels or digital identification tags. These tags provide benefits of electronic article surveillance (EAS) as well as barcodes.

Solution:
For a library, smart labels have several added advantages over EAS and barcodes. One of the major benefits of an RFID system in a library is the ease of check-in and check-out of library items. Patrons can self check-in and check-out library items, saving themselves valuable time. To understand this in details, let us see how a smart label on an item communicates. In a library, an RFID system consists of: A smart label A reader or a hardware for interrogating the smart label A software for controlling the hardware and decoding the responses from smart labels Since RFID tags do not have line of sight requirements: Many items can be read simultaneously even whilst stacked Items do not have to be opened and scanned one at a time Items in multiple formats like books, CDs, etc. can be read at the same time

13

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Automated counters, which read RFID signals, can help patrons: To self check-in/out of items from a height adjustable counter (may be placed anywhere suitable within the library) To quickly renew their issued out items To obtain a receipt of the transaction

These automated self check-in/out counters are suitable for children and persons with physical disabilities. After a check-out operation, the same RFID system disables the security requirements so that patrons can take the books, CDs, videos, etc. outside the library. Many libraries, where RFID technology is operational, have an external chute, mounted on the exterior walls of the library, for returns of books and other borrowed materials. This is operational 24 x 7. (In principle, the return drop boxes may be placed anywhere at airports, at town centers, at railway stations, etc.) These return chutes have RFID readers installed in them. The external return chutes can be opened by members card (secured access). On-board receipt printer can print out the details of the items returned and automatically check items back to the library management system. Sorting and shelving becomes quick, easy and accurate with RFID technology. Once items are returned, a digital sort conveyor belt can place them in appropriate bins from where staff can place them in their correct shelves. With hand held mobile digital library assistant and inventory wand, the library staff can obtain data about shelving the item and other information immediately (catalogue number, shelf number, etc.). Many libraries have found that with RFID technology inventory and scanning of items: Take only 10% or less time as compared to conventional systems Misplaced books and other materials can be found easily the reader can hone-in of misplaced or wrongly shelved items quickly Find cataloguing errors and replace incorrect spine labels

Besides these incredible technological advantages, an RFID system in a library can offer the following as well: RFID tags are safe for magnetic media such as CDs, DVDs, etc. Some RFID tags are rewritable. If, for example, a cataloguing error occurs, it can be rectified quickly Less manual handling of items hence better preservation RFID smart membership cards can give members: access control in certain areas, make payment (fines or fees) easy, lets them use fee-based library facilities such as the photocopier, internet, etc.
14 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Staff has more time from routine chores and can therefore provide better service to patrons Staff schedules can be made flexible Tags last longer than barcodes as reading is contact-less

Solution details:
With RFID applications in libraries, all the library assets, namely books, manuscripts, CDS, DVDs, videos, audio cassettes, etc. have to be embedded with RFID tags. The RFID readers and antennas are placed conveniently where library users will have maximum access. In addition there has to be computers that are managing and controlling all the library activities. Thus, in a library, an RFID system consists of: A smart label which can be attached to or concealed within a library item it contains a memory chip and RF antenna to send and receive data and can be programmed Hardware for interrogating the smart label Software for controlling the hardware, programming the tags and decoding the responses from smart labels in the interrogation zone The three main system components can be further separated into six more subcomponents: A smart label or a tag A reader An encoder or a printer A middleware An application software A host system or a server

Middleware: RFID middleware is a software layer that connects data coming in from tags (on library items such as books, etc.) and readers, to the library management system. Middleware provides a coherent and stable interface between RFID hardware operations and flow of data elements such as membership number, catalogue number, etc. into the library database. RFID middleware solutions provide messaging, routing, and connectivity features required to integrate RFID data into existing library management system. Server: A server is the heart of an RFID application system. It is the communications gateway among the various components of the system. It receives the information from one or more of the readers and exchanges information with the library databases. Application software: The applications software would have the APIs (API: Applications Programming Interface) necessary to interface the RFID system with the server, etc. so as to achieve automated library system. RFID application software is generally a browser-based management interface for centralized monitoring. The software enables safe, secure and highly efficient movement of library items by asset tracking and prevents loss or tampering.
15 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Tags and readers: The microchips on the RFID tags can be programmed electronically. Similarly a reader (technically known as an interrogator) has to be programmed to send and receive correct information from a tag. There are three types of tags: Read only Write once (WORM: Write Once Read Many) Full read/write All of the RFID tags used in libraries are passive types of tags. Generally data stored on the tags have the following options: Item id theft bit shelving information date of circulation

The barcode of an item and its item id are kept identical. Readers are RF detectors that can read tags to obtain the information stored within them. It has an antenna that sends and receives signals. A reader generates an RF field. When a tag passes through the field, the information stored on the chip in the tag is decoded by the reader and sent to the server. There is software in each reader to facilitate communication with the server and therefore automate the whole library system. Today's library RFIDs mainly operate in the high-frequency (HF) 13.56 MHz band, the most widely used of the RFID HF bands because it's the global standard frequency for contact-less smart labels. These tags have a read range of about 3 feet.

Business benefits:
A library RFID system consists of several components: tags, tag readers, tag programming stations, sorting equipment, tag inventory wands, etc. A tag microchip is programmed with distinctive information about the item (for example, barcodes) which can be directly imported from an integrated library system (ILS) at the tag programming station. Thus the new technology can be easily merged with the existing ILS. RFID application in libraries will benefit all persons involved in managing, running and using their facilities. Let us look at the business benefits that are anticipated with RFID technology. Benefits to library management: Uncompromised security within the library Efficient collection management system (can be located suitably and made 24x7) Uncompromised collection security Flexible staff schedules Labor saving methods free the staff to help customers Higher customer/patron satisfaction levels
16 Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Improved inter-library cooperation Better preservation of inventory because of less handling by staff Same security and labeling formats for all items such as books, CDs and DVDs, hence better management of databases

Benefits for library staff: Time saving devices free them to help customer better Labor saving devices free them from doing repetitive, physically stressful tasks Can have flexible working schedules

Benefits for library patrons: Self check-in and self check-out facilities Check-in and check-out of all types of items (books, audio tapes, video tapes, CDs, DVDs, etc.) at the same locations More staff available for assistance Quicker service such as payment of fees, fines, etc. Better inter-library facilities, more efficient reservation facilities, etc. Faster and accurate re-shelving means patrons can find items where they should be, hence quicker and more satisfying service Height adjustable self check-in/out tables are liked by children and physically disabled persons who use the library

Possible problems:
RFID technology will continuously communicate with the library database, the real danger of merging this technology is in letting secure ILS database be contacted/updated/opened several times and thereby make them prone to hackers. Some of the technological problems that may occur with RFID applications in libraries are: RFID tags are not hidden since these tags are typically affixed to the inside back cover and are exposed to vandalism Some interference from metallic material in book covers, CDs and DVDs does occur and tag reading may not be correct RFID tags are easy to shield from readers by ordinary aluminum foils and may not serve the purpose of being anti-theft tools RFID reading accuracy declines if many items are read simultaneously (although collision avoidance air interface protocol may be used to minimize this effect) RFID reader range depends on its power and antenna size

In addition to these technical problems, there may be other difficulties in implementing RFID systems in libraries. Some of these are: Privacy issues Forward (future) compatibility and inter-library operations due to differences in tags or software Limitations in reorganization of library spaces Metal shelves may hinder operations of readers and sensors Operational difficulties such as installation of return chutes, provision of power supply near the self check-in/check-out desks or chutes Budget restrictions for technology upgradation as RFID tags are more expensive than barcodes and security strips

17

Designed By: Puneet Mathur

Final Year Project Report Format(Project Stage-I), Academic Year 2011-2012, PIET, Jaipur

Summary:
Today's library RFIDs mainly operate in the high-frequency (HF) 13.56 MHz band and are very suitable for library application since they have longer read ranges, about 3 to 5 feet. Although RFID technology has matured and offers an ideal solution for libraries to replace their EAS and barcode systems for security and theft prevention, the picture is not all that smooth. There are several concerns and some are about patron privacy violations. Large numbers of libraries have gone into RFID tagging for their inventory and have put in place best practices to inform their patrons about the use of technology and protection of their privacy.

18

Designed By: Puneet Mathur