CERTIFICATE

This is to certify that the project “Factory Information System” submitted by the teamwork
of Deuti Gurung (362475), Nabin Shuyel (362478) and Sujin Taujae (362486) has
completed successfully under the supervision and guidance in practical fulfillment of the

requirement for the project of BCA 6th Semester of Purbanchal University for the year
2022.

......................................

Head of Department,

BCA
 ACKNOWLEDGEMENT

We would like to express our gratitude to all those who gave us the possibility to
complete this project. Several people are involved to achieve such a fruitful result of
application development. It is our pleasure to acknowledgement our debt to the many people
involved indirectly in the development of this application.

Our Primary thanks goes to Mrs, Kapila Shrestha concern project in-charge and
H.O.D whose timely and valuable suggestions, assistance and guidance’s supported a lot to us
to come up with this result within a short span of time. The credit of these outcomes goes to
the management, staffs and executives of CITE, Kathmandu without whom our work has been
remained incomplete. Hence, we are heartily grateful to all the concerned people from CITE
college for the required information.

We can’t stay without thanking all the members of computer department and lab that
always nepotism us by assisting in computer works and corresponding supports. Our beloved
friends are also equally credited of our achievement. Also, we anticipated deep corporation
and support from all of you in coming days as we need to go far ahead in the highway of life.

Thank you!

I
 ABSTRACT

The sole intention behind the consideration of this Project is to develop and manage a simple
and user interface for Factory Information System. This project is developed considering light
memorymanagement and simple UI.

This report is prepared by the students of BCA 2018 batch based on the syllabus of
Purbanchal University for the 3rd year 6th semester minor project. The major purpose of this
project is to make a Factory Information System using Laravel, PHP framework. This report
has been prepared analyzing the various possible difficulties and possible implementation of
this project. The concept of Factory Information System has been on the internet or market
for a long time.

II
 TABLE OF CONTENTS

ACKNOWLEDGEMENT....................................................................................... I

ABSTRACT.............................................................................................................. II

1. CHAPTER 1: INTRODUCTION
1.1. Background and significance.................................................................. 1
1.2. Problem Statement................................................................................... 2
1.3. Objectives.................................................................................................. 3
1.4. Project Features........................................................................................ 3
1.5. Documentation Overview......................................................................... 4
2. CHAPTER 2: EXITSING SYSTEM
2.1. Introduction.............................................................................................. 5
2.2. Research Background.............................................................................. 6
2.2.1. Problems in Existing System
2.2.2. Solution to existing Problems
2.3. Proposed System...................................................................................... 8
2.3.1. Salient Features of Proposed System
2.3.2. Functions to be Provided
2.4. Drawbacks................................................................................................ 9
3. CHAPTER 3: SYSTEM ANALYSIS
3.1. System development model..................................................................... 10
3.1.1. Major advantages of Waterfall model
3.1.2. Conclusion
3.2. Requirement specification....................................................................... 12
3.2.1. Functional Requirement
3.2.2. Non Functional Requirement
3.3. Feasibility Study....................................................................................... 13
3.3.1. Technical Feasibility
3.3.2. Economic Feasibility
3.3.3. Operational Feasibility
3.3.4. Gantt Chart
4. CHAPTER 4: SYSTEM DESIGN
4.1. System Architecture............................................................................... 16
4.1.1. Primary Design Phase
4.1.2. Secondary Design Phase
4.2. Use case Diagram................................................................................... 17
4.3. Activity Diagram.................................................................................... 18
4.4. ER Diagram............................................................................................ 20
5. CHAPTER 5: SYSTEM DEVELOPMENT AND IMPLEMENTATION
5.1. Tools and technology used.................................................................... 21
5.2. Operating environment......................................................................... 21
5.3. Minimum Software Requirement........................................................ 21
6. CHAPTER 6: CONCLUSION AND FUTURE ENHANCEMENT
6.1. Conclusion.............................................................................................. 22
6.2. Limitations............................................................................................. 22
6.3. Future Enhancement............................................................................ 23

REFERENCE........................................................................................................ 24

APPENDIX............................................................................................................. 25
 CHAPTER 1: INTRODUCTION

1.1. Background and significance

Factory Information System (FIS), originally developed as factory statistics system or factory
statistics information system, is a web-based tool for effective management and handling of
various operations in a factory or industry. Also Factory Information Systems are interrelated
components working together to collect, process, store, and disseminate information to
support coordination, control, analysis, and visualization in an organization.

A FIS may also provide tools for personalization, or one-to-one marketing. One-to- one
marketing is the ability of a website to tailor its content and advertising to a user's specific
characteristics using information a user provides or a website gathers. Using FIS is today's
need, because:
• The big advantage is that, we, a non-programming civilian, can update own
information/data.

• Updating information is fairly straightforward. After the initial learning curve of the FIS,
we will find it fairly easy to update data.

• If our website has regularly changing content such as weekly specials, an updating
content, pages, or a blog, posting own content could save you a lot of money in the long
run. The alternative to making own updates is to pay developer a monthly maintenance
or hourly rate for changes which can get quite costly.

• Real-time data, particularly useful where fast action is needed (ex: mechanical fault).

1
1.2. Problem Statement

An increasing number of organizations have websites. The trend is to disseminate

responsibility of managing web content for the web site to the people who generate it rather
than webmaster. In the situation the web master can focus on large system issues and avoid
dealing with small updates or additions. At the same time, this scenario creates a situation in
which people who are uncomfortable with working on web design are forced to complete
tasks for a web site. In addition, many organizations support multiple sites such as Web
Application Protocol, Flash, and HTML sites that have the same content. Thus, there is a
need for a system that will manage and organize web site content.

In order to address these issues, it's important to have a clear agreement about what is being
purchased, and what is being delivered. The problem is, there are a ton of variables, and
many of them are not discovered until the project is well underway. Doing the groundwork to
identify all the possible pitfalls of a project is probably about half the actual work of a
project—and in most cases, that's far more of an investment than the client wants to make
without an actual result. We've done a number of “discovery projects,” of this nature, and
almost always put far more into the discovery than we planned—if we don't win the rest of
the project, we lose money. Which means we need to charge our paying clients enough to
cover that, making it more expensive all around.

We propose a solution with the following properties: allow users to interact with text for a
web site, group text into different categories to deal with the quantity to text, allow style sheet
and graphics file to be combined with the text files, allow for a verification section in which a
VP or other managers in the company to check additions and changes before they go live, and
finally update content on all sites at once. The presentation of the files associated within our
system is handled by modules outside of the system.

2
1.3. Objectives
Most organizations recognize that Factory Information System (FIS) is a necessity when
maintaining a large corporate website or intranet. It is important to ensure however, that
beyond a general ‘need’, FIS solutions should be made to meet specific business goals.
Without a clear vision of the business goals of the system, it is impossible to track the success
of the project, or ensure that the benefits are maximized.

• Increase flexibility of the site

• Support marketing
• Improve customer experience
• Support sales
• Support website growth

1.4. Project Features

There are different features in this project. They are as follows:
• Create and edit content
• Workflows, reporting, and content organization
• User and role-based administration
• Security
• Flexibility, and performance
• Personalization and analytics
• Dynamic webpage

3
1.5. Documentation Overview
This document plays a vital role in the development of life cycle (SDLC) as it describes the
complete requirement of the system. This report is organized in six chapters. The chapters of
this report are:

CHAPTER I: Introduction
The project background, significance, introduction, problem statement, objectives, project
features are well stated.

CHAPTER II: Existing System Overview

The research problem and research method. Apart from that, the reviews of the existing
system also are being discussed in this chapter.

CHAPTER III: System Analysis

The system development model that we’ve used in the project is described. Requirement
specification with both functional and non-functional requirement are listed in this chapter
.
CHAPTER IV: System Design
The system architecture, ER diagram, UML diagram and activity diagram are shown and
explained in this chapter.

CHAPTER V: System Development and Implementation

The tools and technology used and operating environment for the project has been described
in this chapter.

CHAPTER VI: Conclusion and Future Enhancement

The conclusion, limitation, and Future enhancement of the project is written in this chapter.

4
 CHAPTER 2: EXITSING SYSTEM

2.1. Introduction
In the globalization era, rapid data communication and sufficient information is important to
make the right decision at the right time. At present, various organizations/ industries in
Nepal are using paper based methods, which are time consuming. Recently, few
organizations have installed computerized systems instead of traditional systems. The use of
internet-based technologies to communicate information is one of the best approaches to
support the informational needs of various departments of an organization. In this research
work a case study was performed on a specific Garments Industry. The existing information
model of that factory is studied and then a conceptual information model named Factory
Information System (FIS) was suggested. Then software was developed for a smooth flow of
information. The developed software is composed by two sections that are design database
and functions of programs or user interfaces design.

In most organizations, information flow plays a vital role for proper workplace
activities. The usage of computer makes it possible to do efficient and quick work and get
accurate results in every field of life e.g. industry, agricultural research, engineering and
medical. It is extremely difficult to organize and to maintain the current and old official
records manually. Most of the organizations are storing their data manually, putting their
precious records at risk without any security. The search for a specific file is cumbersome
process and some time they fail in their search, this leads to realization to ease their work,
which is possible with computers having sophisticated and user-friendly software. The
effective management of information requires information technology and that technology is
therefore crucial to organizational success. Using IT systems to capture and analyze
information can have a significant impact on a firm’s performance. Information technology
comes in many forms-networked personal computers, software applications, the Internet and
more-but one thing all types of information technology have in common is that their effective
use depends upon users. People put the technology to work in managing information and
people are ultimately responsible for whether information technology succeeds or fails. Over
the last 15-20 years the apparel sector has been in a state of continuous restructuring. A
combination of technological and socio-economic changes, production cost, liberalization

5
and the emergence of important international competitor from Asia and the Mediterranean
region are influencing the apparel manufacturing sector of Nepal.
Seeing that we now know what a FIS is, we desire to take a moment to see why anybody
would want to use one. Though there are many reasons we will only look at a few quickly.

2.2. Research Background

Ready Made Garments (RMG) sector of Nepal today are operating in a highly competitive
global environment. The phasing out of quota privileges and facilities from developed
countries offers new challenges as well as opportunities. The challenges include becoming
more competitive in terms of quality, price and on time delivery. In the new economy, the
focus has been on; building on core strength; provision of real-time information; visibility of
key performance indicator; collaboration in supply-chain operation and e-commerce
development. The web based information system has several advantages and overcome some
traditional problems. These includes:
• Single data entry to minimize human error
• Online query function
• Multi-level password controls (so that different` functions have different access levels
controlled by their respective authorized people).
At present there are many systems to provide smooth information flow through the
organization but this is too expensive to implement in the composite apparel industries. These
difficulties provide the opportunities to build an effective and efficient system for the
composite apparel industry from where all the information can be accessed and updated by
individual department and can be retrieved when necessary. Some software companies now-
a-days are making software on the basis of production information system and Human
resource information system etc. They develop the software according to companies demand.
Although that software is very much strong in structure but it’s expensive and difficult to
maintain. So, most of the apparel industries are incapable to use those software.
Basically the development of the website is reflection of current information sharing process
of the apparel industry. PHP language and MYSQL database (XAMPP) is used to develop
the software.

6
2.2.1. Problems in Existing System
• It was less user-friendly.
• It have a lots of manual work (Manual system does not mean that we are working with
pen and paper, it also include working on spread sheets and other simple software's)
• It requires more no of employees need to work.
• It was time consuming process.
• The present system was very less secure.

2.2.2. Solution to existing Problems

The development of the new system contains the following activities, which try to automate
the entire process keeping in view of the database integration approach.
• User friendliness is provided in the application with various controls.
• The system makes the overall project management much easier and flexible.
• It can be accessed over the Internet..
• There is no risk of data mismanagement at any level while the project development is
under process.
• It provides high level of security using different protocols like https etc
All of these reasons are valid but they often come with hidden or overlooked challenges

7
2.3. Proposed System
Administrators or manager etc are able to access the database according to their privilege
after Authentication using passwords.
Factory Information System an attempt to take a step towards "paperless work". Factory
Information system a multi-user, user friendly and GUI based application software. In this
system every user will need to have only a single computer terminal. which is attached to the
server of the Institute. Any query related to the product will be served from the centralized
database server at the Institute .This Login and Password should be kept Confidential as this
can provide access to each and every module of the Database. Thus, system ensures the
security from the unauthorized access other than the user of the institute. The system offers
the functionality at client/server.

2.3.1. Salient Features of Proposed System

• Create and edit content
• Workflows, reporting, and content organization
• User and role-based administration
• Security
• Flexibility, and performance
• Personalization and analytics
• Dynamic webpage

2.3.2. Functions to be Provided

The proposed system is based on information made available by the administration section.
The data pertaining to various transactions of the students will be fed to system through the
data entry screens to generate database in the required form. The new system will provide
data in processed and consolidated form taking care of the purpose being served by the
specific tables being already maintained. The access to this package will be provided only
through a password. The data entry will be possible through the respective forms. Each and
every type of queries is proposed to deal with specific areas of customers, products, and other
related modules.

8
2.4. Drawbacks
• Security Risks: FIS poses a larger Security Risk unless maintained and regularly
updated.
• Hosting company may shut website down: This happens only if website is not
maintained, as security hole on particular website can lead to other sites on the server
being compromised.
• Learning FIS like with any new tool or resource: Time must be given to learning how
to get the most out of the tool. This will vary, based on comfort level with computers.
• Manpower for updating website: Many business owners have set up a FIS with the
intent of updating their own content but time and other work take priority leaving the
website out of date.
• Consideration for search engine optimization: If this concept is new to you then
perhaps you would need to look more into what SEO is and consider how it impacts site
when adding content.
• Images must be resized for use on the web: Though there are other reasons to resize
images for the web the biggest is it reduces the file size.

9
 CHAPTER 3: SYSTEM ANALYSIS

3.1.1. System Development Model

For this system development, we have used waterfall model. It is also referred as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each
phase must be completed before the next phase can begin and there is no overlapping in the
phases.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.

Fig 1: Waterfall Model of SDLC

10
3.1.2. Major advantages of Waterfall model
The advantages of waterfall development are that it allows for departmentalization and
control. A schedule can be set with deadlines for each stage of development and a product
can proceed through the development process model phases one by one.

Some of the major advantages of the Waterfall Model are as follows –

• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.

3.1.3. Conclusion
All these phases are cascaded to each other in which progress is seen as clearly. The next
phase is started only after the defined set of goals are achieved for previous phase and it is
signed off, so the phases will not overlap and easy to maintain and built the system.
Therefore, we implement waterfall model in this project.

11
3.2. Requirement specification

3.2.1. Functional Requirement

• The system provides all the information about the organization in detail.
• The system gives in detail description of organization infrastructure.
• All the information about services and projects are provided category wise.
• All the information is rendered with proper images and flash slides for better navigation.
• Proper information regarding the events and available means is also included.

3.2.2. Non Functional Requirement

• The system should be available at all times, meaning the user can access it using
application
• Runs on low performance systems and on any environment
• Cost effective deployment (When buying out of storage space).

12
3.3. Feasibility Study
Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibilitystudy of a system
proposal is according to its workability, which is the impact on the organization, ability to
meet their user needs and effective use of resources. Thus, when a new application is proposed
it normally goes through a feasibility study. The document provides the feasibility of the
project that is being designed and lists various areas that were considered very carefully
during the feasibility study of this project such as Technical, Economic and Operational
feasibilities. The following are itsfeatures:

3.3.1. Technical Feasibility

Technical feasibility centers on the existing computer system i.e. Hardware, Software etc.
Bank requires SQL database management that are all easily available with extensive
development support through manuals and blogs. The system must be evaluated from the
technical point of view first. The assessment of this feasibility must be based on an outline
design of the system requirement in the terms of input, output, programs and procedures.
Having identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once it has been
designed.
Technical issues raised during the investigation are:
• Does the existing technology sufficient for the suggested one?
• Can the system expand if developed?
• What are the cost and the savings of the alternative(s)?
• Is there a new and better way to do the job that will benefit the user?

The project should be developed such that the necessary functions and performance is
achieved within the constraints. The project is developed within latest technology.

Through the technology may become obsolete after some period of time, due to the fact that
never version of same software supports older versions, the system may still be used. So,
there are minimal constraints involved with this project.

13
3.3.2. Economic Feasibility
Economical Feasibility is the most frequently used method for evaluating the effectiveness of
a candidate system. More commonly known as Cost/ Benefit analysis, the procedure is to
determine the benefits and savings that are expected from the candidate system and compare
them with costs.
If the benefits outweigh costs, then the decision is made to design and implement the
system. The developing system must be justified by cost and benefit. Criteria to ensure that
effort is concentrated on project, which will give best, return at the earliest. One of the
factors, which affect the development of a new system, is the cost it would require.
The following are some of the important things to consider:
• The costs conduct a full system investigation.
• The cost of the hardware and software.
• The benefits in the form of reduced financial questions asked during preliminary
investigation: costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also, all the resources are already available, it gives an indication of the
system is economically possible for development.

3.3.3. Operational Feasibility

The proposed system is operationally feasible because of the following reasons:
• The cost of the proposed system is almost negligible when compared to the benefits
gained. Unplanned downtime and follow-up costs can be avoided and delivery
performance can be further increased.
• Factory planning becomes step-by-step digital. Lean, waste-free processes are a key
success factor for efficient production

14
3.3.4. Gantt Chart

Online Clothing May May June 1 June June July July July
Store 10 12 Onwards 10 20 02 08 12

Planning

Research

Designing

Implementation

Follow-up

15
 CHAPTER 4: SYSTEM DESIGN

4.1. System Architecture

In this phase the software’s overall structure and its nuances are defined. In terms of client
server technology the no of tiers needed for the package architecture, database design, data
structure design etc are defined in this phase. Analysis and Design are very crucial in entire
development cycle. Any glitch in this phase could be expensive to solve in the later stage of
software development. Normally, design is performed in the following in the following two
steps:

4.1.1. Primary Design Phase

In this phase, the system is designed at block level. The blocks are created on the basis of
analysis done in the problem identification phase. Different blocks are created for different
functions emphasis is put on minimizing the information flow between blocks. Thus, all
activities which require more interaction are kept in one block.

4.1.2. Secondary Design Phase

In the secondary phase, the detailed design of every block is performed.

16
4.2. Use case Diagram
Cases included in following use-case diagram:
• User
• Admin
• Manage page
• Manage blog
• Manage contacts
• Manage events
• View page
• View blogs
• View events

Fig 3: Use Case Diagram

17
4.3. Activity Diagram

Fig 4: Activity diagram

18
Fig 5: Activity Diagram

19
4.4. ER Diagram

Fig 6: ER Diagram

20
 CHAPTER 5: SYSTEM DEVELOPMENT AND
IMPLEMENTATION

5.1. Tools and technology used

• Windows 7,10 as an operating system
• Phpstorm IDE
• Framework: Laravel
• Languages: HTML/CSS, PHP
• Database: MySQL

5.2. Operating environment

The system is light weight program and can run in any modern PC. Minimum hardware
requirement
• RAM : 512 MB or higher
• Processor : Pentium processor or higher
• Hard Disk : 4.0 BGB or more

5.3. Minimum Software Requirement

• Operating system: Any Windows version/MAC

• Browser (ex: Google chrome or Mozilla Firefox or Opera or Brave)

• Database (MYSQL 7.0)

21
CHAPTER 6: CONCLUSION AND FUTURE ENHANCEMENT

6.1. Conclusion
Factory Information systems have a number of vital components, some tangible, others
intangible, and still others of a personnel nature. These components collect, store, organize,
and distribute data throughout the organization. You may have even realized that one of the
roles of information systems is to take data and turn it into information, and then transform
that information into organizational knowledge A windows-based application software tool
related to the Factory Information System has been developed, this role has evolved into the
backbone of the organization, making information systems integral to virtually every
business. The integration of information systems into organizations has progressed over the
decades.
Using this tool management of an industry, an entity can recognize the different activities and
information of its various production department. Considering all the observations it is
significant that this tool can play a vital role in any industry. It is an easy to use content
system where you don’t have to be technical savvy.
Its structure is organized. Changing pages in this system can affect other pages. Always
contact developer for making a change.

6.2. Limitations
• Dependency on plug-in and widgets
• Hidden cost of plug-in and widgets
• Slow site loading speed
• Needs to be maintained on a regular basic
• Not highly scalable
• Back end functions are limited
• Required proper knowledge for basic operations
• Poses a security risk if not updated regularly

22
6.3. Future Enhancement
• A mobile application of the system can be made
• A smart chat bot can be added to the site for quick guidance
• Improvised Customer Service
• More retina friendly designs and graphics
• Motion UI trends

23
 REFERENCES

[1] https://neonex.de/en/iiot-hub/smart-factory-basics/smart-factory-advantages-disadvantages

[2] https://www.nibusinessinfo.co.uk/content/benefits-information-systems-business

[3] https://opentextbook.site/informationsystems2019/chapter/chapter-1-what-is-an-information-
system-information-systems-introduction/

[4] https://docs.google.com/document/d/1IlMciJEkPzsFYHtGNedPVclcBFV3a-IL/edit#

[5] https://www.researchgate.net/publication/227439074_A_MODEL_ON_FACTORY_INFOR
MATION_SYSTEM_FIS

24
 APPENDIX

Appendix 1: Screenshots

25
26
27
28