Erp Unit I-Iii
Erp Unit I-Iii
Erp Unit I-Iii
Introduction to ERP – Conceptual model of ERP – Evolution of ERP – Structure of ERP – Reasons for Growth –
Advantages of ERP – Enterprise: An overview. ERP and Related Technologies: Business Process Re-engineering –
Management Information System – Decision Support System – Executive Information system – Data warehousing –
Data Mining – OLAP – Supply Chain Management.
UNIT III - Hardware and Software’s of ERP and SAP Teaching hours - 13
A Gateway to SAP – SAP Easy Access – The Architecture of SAP R/3 – Presentation Interface – Application inte
rface – Database interface. SAP User Interface Starting and Shutting the SAP System – Handling Tasks in SAP Reports
– Background Processing: SAP System Administration Utilities – SAP R/3 Basis System.
Modules of SAP components – Roles in SAP application – Basic introduction to ABAP – Data Type and Tables i
n ABAP – The ABAP Programming Language – ABAP User Dialogs – Running ABAP Programs.
UNIT I:
Objectives
INTRODUCTION TO ERP :
A business process is a collection of linked tasks that find their end in the delivery of a service or
product to a client.
A business process has also been defined as a set of activities and tasks that, once completed, will
accomplish an organizational goal.
That means
accounting,
quality,
finance,
Different departments like receiving, inventory management, customer order management, production
planning, shipping, accounting, human resource management, and other business functions.
Basically, it is the practice of consolidating an enterprise’s planning, its manufacturing, its sales and
marketing efforts into one management system.
It combines all databases across different departments into a single database which can be easily accessible
to all employees of that enterprise.
Before ERP:
Before an ERP system, there are different databases of different departments which they managed by their
own. The employees of one department does not know about anything about other department.
After ERP :
After ERP system, databases of different departments are managed by one system called ERP
system. It keep tracks of all the database within system. In this scenario, employee of one department have
information regarding the other departments.
Vendors of ERP:
Baan
JD Edwards
Oracle
PeopleSoft
SAP
Benefits of ERP:
1. This system helps in improving integration.
2. It is the flexible system.
3. There are fewer errors in this system.
4. This system improved speed and efficiency.
5. There is a complete access to information.
6. Lower total costs in complete supply chain.
7. This system helps in Shortening the throughput times.
8. There is sustained involvement and commitment of the top management.
9. Enhanced Decision-Making: ERP provides real-time access to critical business data, enabling decision-
makers to quickly identify and respond to issues, make informed decisions, and improve business
outcomes.
10. Improved Collaboration: ERP facilitates collaboration and communication between different
departments and stakeholders, enabling them to work together effectively towards common business
goals.
11. Standardization of Processes: ERP ensures that business processes are standardized across the
organization, reducing the risk of errors and inconsistencies and improving efficiency.
12. Effective Resource Management: ERP enables efficient management of resources such as personnel,
equipment, and inventory, ensuring optimal utilization and reducing wastage.
13. Scalability: ERP is highly scalable and can be customized to meet the evolving needs of the business,
ensuring that the system remains relevant and effective over the long term.
14. Regulatory Compliance: ERP systems can help businesses comply with regulatory requirements by
providing accurate and timely reporting, ensuring data privacy and security, and facilitating audits.
Limitations of ERP:
ERP system has 3 significant limitations:
1. Managers generate custom reports or queries only with the help from a programmer and this will create
a problem that they did not receive information quickly, which is essential for making a competitive
advantage.
2. There is no proper decision-making scenario i.e. this systems provide only the current status, such as
open orders. Whenever there is need to look for past status to find trends and patterns it become
difficult.that aid better decision-making.
3. No doubt that data is integrated within the system, but there is no integration of data with other
enterprise or division systems and it does not include external intelligence.
4. High implementation costs: Implementing an ERP system can be expensive and time-consuming. It
requires significant investment in hardware, software, and personnel, as well as training and consulting
costs.
5. Complex customization: Customizing an ERP system to meet the specific needs of an organization can
be complex and require specialized knowledge. This can lead to delays and additional costs.
6. Resistance to change: ERP systems often require significant changes to an organization’s processes
and workflows, which can be met with resistance from employees who are comfortable with existing
practices.
7. Data security risks: Centralizing sensitive business data in an ERP system creates potential security
risks, especially if the system is not properly secured or if there are vulnerabilities in the software.
8. Limited flexibility: ERP systems are designed to provide standardization and control, which can limit
the flexibility of an organization to respond to changing business needs and market conditions.
9. Dependence on vendor support: Organizations that use ERP systems are often heavily dependent on
the vendor for support, maintenance, and upgrades. This can create a risk of vendor lock-in and limit
an organization’s ability to switch to other systems or providers.
These business policies lead to critical elements for the ERP system. The success of ERP depends
on the level of its adoption in the organization.
ERP can be defined in the following ways by keeping the above-mentioned concept in mind :
1. It is a planning methodology or philosophy that is based on the smooth integration of all the
business processes of an enterprise.
2. It is a set of software casing major business areas e.g. economics, plans, sales, materials,
manufacturing, distribution, all so tightly integrated with one another that any business activity
recorded at one place is immediately reflected in all other places.
3. It is the finest expression of the consistency of Info-tech and business. An enterprise-wide
system with enabling technology and effective managerial tool for integrating all the levels and
improving report ability.
The above definitions explain the fundamental design feature of ERP as a system-based business
solution. ERP integrates the various departments and functions throughout the organization. It
attempts to comprehend everything into a single system that can serve every department and
functional needs. While doing so, it focuses on the business plan areas and addresses those problems
with an integrated planning approach.
To understand how ERP is a system based business solution, we have to first critically examine
the two key words ‘System’ and ‘solution’.
System :
In the present context, we can say that ERP is a system for a specific set or arrangement of elements
that are organized to accomplish a pre-defined goal through the processing of information. This goal
invariably could be to support an existing business function, improve the transparency of data,
improve efficiency in business, improve decision-making, and provide improved customer
satisfaction. The key resource elements of such a system are hardware, software, users, databases,
etc.
Solution :
A business solution can be explained as a framework encompassing strategy, organization
structures, key performance indicators, measurements, and IT, which must be aligned to the business
processes. Conventionally, there are three kinds of business processes- acquiring and paying for
input resources, converting inputs into finished goods and services provided.
Thus ERP as a combination of system and business solution provides the user with a productive
planning tool.
STRUCTURE OF ERP :
The essence of ERP is the fundamental approach that takes an integrated view of the subject. The
established application systems, which the organization generally employs, treat each deal separately.
They are built around the strong boundaries of specific functions that a specific application is meant to
carter.
Features of the Structure of ERP :
Here, we will discuss the basic features of the Structure of ERP as following.
ERP considers them to be part of the interlinked processes that make up total business and
financial impact. Almost all the typical application systems are nothing but data manipulation
tools.
They store data, process them, and present them inappropriately whenever requested by the user.
In this process, the only problem is that there is no link between the application system being used
by different departments.
An ERP system also does the same thing but in a different manner. There are a hundred such data
tables that store data generated as a result of the diverse deal, but they are not confined to any
departmental or functional boundaries.
These are rather integrated for speedy and precise results required by multiple users, for multiple
purposes, for multiple sites, and at multiple times.
ERP Advantages :
Here, we will discuss the advantages of ERP. Let’s have a look.
Flexible –
In response to changing needs of an enterprise, it should be flexible. The client-server technology
authorizes ERP to run across various database backend via open database connectivity.
Modular –
The ERP system has to have modular implementation architecture. This means that many
performances are logically clubbed into the different business procedure and structured into a
module which can be interfaced or detached whenever need without influence the other modules. It
should support multiple hardware platforms for the companies having a heterogeneous collection
of systems. It must support some third-party add-ons also.
Comprehensive –
It should be able to support a diversity of organizational functions and must be suitable for a wide
range of business organizations.
BPR projects have failed sometimes to meet high expectations. Many unsuccessful BPR attempts are
due to the confusion surrounding BPR and how it should be performed. It becomes the process of trial
and error. Phases of BPR : According to Peter F. Drucker, ” Re-engineering is new, and it has to be
done.” There are 7 different phases for BPR. All the projects for BPR begin with the most critical
requirement i.e. communication throughout the organization.
1. Begin organizational change.
2. Build the re-engineering organization.
3. Identify BPR opportunities.
4. Understand the existing process.
5. Reengineer the process
6. Blueprint the new business system.
7. Perform the transformation.
Objectives of BPR : Following are the objectives of the BPR :
1. To dramatically reduce cost.
2. To reduce time requirements.
3. To improve customer services dramatically.
4. To reinvent the basic rules of the business e.g. The airline industry.
5. Customer satisfaction.
6. Organizational learning.
Challenges faced by BPR process : All the BPR processes are not as successful as described. The
companies that have start the use of BPR projects face many of the following challenges :
1. Resistance
2. Tradition
3. Time requirements
4. Cost
5. Job losses
A management information system (MIS) is an information system used for decision-making, and for the
coordination, control, analysis, and visualization of information in an organization. The study of the
management information systems involves people, processes and technology in an organizational context.
MIS IMPORTANCE.
1. Management Information System is always management oriented and keeps in view every level of
management and gets the desired information.
2. Integrated – refers to how different components (sub systems) are actually tied up together. eg: different
departments of organization linked together.
3. Useful for planning – as every organization makes log-term and short-term plans with the help of
information like sales & production, capital investments, stocks etc management can easily plan..
4. Effective Management Information System helps the management to know deviations of actual
performance from pre-set targets and control things.
Structure of MIS:
Structure of MIS may be understood by looking at the physical components of the information system in an
organization.
The physical components of an organizational information system may be hardware, software, database,
manual procedures and operating persons.
A brief description of these components has been outlined in the following paragraphs:
Hardware Hardware refers to the physical data processing equipment and peripheral devices, For example,
CPU, monitor, keyboard, printer, drives, tapes, communication devices, etc.
Software Software is a broad term given to the instructions or programs that direct the operating of the
hardware. Software could be of two types, i.e. system software and application software.
Procedures Formal operating procedures, which are required to operate a system, such as manuals, are also
regarded as physical elements.
Operating Personnel Personnel like Computer Operators, Computer Programmers, System Analysts,
System Managers, etc., are the operating people of the information systems.
Input and Output Various physical inputs and outputs from the information system, existing in forms like
printout, reports etc.
1. TPS are used primarily for structured operational, and to a lesser degree, management
control applications.
2. MIS are used for semi--structured, management control applications. It also overlaps into
the operational and strategic planning realms as well.
3. DSS are used primarily for unstructured decision-making whether that occurs at
the operational, management and strategic planning levels.
4. ESS is used primarily for structured management and strategic planning applications.
5. OAS are used as a facilitator of office correspondence and communication, underlies all
of this activity.
A typical organization is divided into operational, middle, and upper level. The information
requirements for users at each level differ. Towards that end, there are number of information
systems that support each level in an organization.
Examples of users at this level of management include cashiers at a point of sale, bank
tellers, nurses in a hospital, customer care staff, etc.
Users at this level use make structured decisions. This means that they have defined rules
that guides them while making decisions.
For example, if a store sells items on credit and they have a credit policy that has some
set limit on the borrowing. All the sales person needs to decide whether to give credit to a
customer or not is based on the current credit information from the system.
Tactical users make semi-structured decisions. The decisions are partly based on set
guidelines and judgmental calls. As an example, a tactical manager can check the credit
limit and payments history of a customer and decide to make an exception to raise the
credit limit for a particular customer. The decision is partly structured in the sense that
the tactical manager has to use existing information to identify a payments history that
benefits the organization and an allowed increase percentage.
This is the most senior level in an organization. The users at this level make unstructured
decisions. Senior level managers are concerned with the long-term planning of the
organization. They use information from tactical managers and external data to guide
them when making unstructured decisions.
Transaction Processing System (TPS)
Transaction processing systems are used to record day to day business transactions of the
organization. They are used by users at the operational management level. The main objective of
a transaction processing system is to answer routine questions such as;
The decisions made by operational managers are routine and highly structured.
The information produced from the transaction processing system is very detailed.
For example, banks that give out loans require that the company that a person works for should
have a memorandum of understanding (MoU) with the bank. If a person whose employer has a
MoU with the bank applies for a loan, all that the operational staff has to do is verify the
submitted documents. If they meet the requirements, then the loan application documents are
processed. If they do not meet the requirements, then the client is advised to see tactical
management staff to see the possibility of signing a MoU.
Management Information Systems (MIS) are used by tactical managers to monitor the
organization's current performance status. The output from a transaction processing system is
used as input to a management information system.
The MIS system analyzes the input with routine algorithms i.e. aggregate, compare and
summarizes the results to produced reports that tactical managers use to monitor, control and
predict future performance.
For example, input from a point of sale system can be used to analyze trends of products that are
performing well and those that are not performing well. This information can be used to make
future inventory orders i.e. increasing orders for well-performing products and reduce the orders
of products that are not performing well.
Sales management systems – they get input from the point of sale system
Budgeting systems – gives an overview of how much money is spent within the
organization for the short and long terms.
Human resource management system – overall welfare of the employees, staff
turnover, etc.
Tactical managers are responsible for the semi-structured decision. MIS systems provide the
information needed to make the structured decision and based on the experience of the tactical
managers, they make judgement calls i.e. predict how much of goods or inventory should be
ordered for the second quarter based on the sales of the first quarter.
Decision Support System (DSS)
Decision support systems are used by senior management to make non-routine decisions.
Decision support systems use input from internal systems (transaction processing systems and
management information systems) and external systems.
The main objective of decision support systems is to provide solutions to problems that are
unique and change frequently. Decision support systems answer questions such as;
What would be the impact of employees' performance if we double the production lot
at the factory?
What would happen to our sales if a new competitor entered the market?
Decision support systems use sophisticated mathematical models, and statistical techniques
(probability, predictive modeling, etc.) to provide solutions, and they are very interactive.
Online analytical processing (OLAP) is used to query and analyze multi-dimensional data and
produce information that can be viewed in different ways using multiple dimensions.
Let's say a company sells laptops, desktops, and Mobile device. They have four (4)
branches A, B, C and D. OLAP can be used to view the total sales of each product in
all regions and compare the actual sales with the projected sales.
Each piece of information such as product, number of sales, sales value represents a
different dimension
The main objective of OLAP systems is to provide answers to ad hoc queries within
the shortest possible time regardless of the size of the datasets being used.
DATA WAREHOUSING
The term "Data Warehouse" was first coined by Bill Inmon in 1990. According to Inmon, a data
warehouse is a subject oriented, integrated, time-variant, and non-volatile collection of data. This
data helps analysts to take informed decisions in an organization.
A data warehouses provides us generalized and consolidated data in multidimensional view.
Along with generalized and consolidated view of data, a data warehouses also provides us
Online Analytical Processing (OLAP) tools. These tools help us in interactive and effective
analysis of data in a multidimensional space. This analysis results in data generalization and data
mining.
Data mining functions such as association, clustering, classification, prediction can be integrated
with OLAP operations to enhance the interactive mining of knowledge at multiple level of
abstraction. That's why data warehouse has now become an important platform for data analysis
and online analytical processing.
Data Warehouse Features
The key features of a data warehouse are discussed below −
Subject Oriented − A data warehouse is subject oriented because it provides information
around a subject rather than the organization's ongoing operations. These subjects can be
product, customers, suppliers, sales, revenue, etc. A data warehouse does not focus on the
ongoing operations, rather it focuses on modelling and analysis of data for decision
making.
Integrated − A data warehouse is constructed by integrating data from heterogeneous
sources such as relational databases, flat files, etc. This integration enhances the effective
analysis of data.
Time Variant − The data collected in a data warehouse is identified with a particular
time period. The data in a data warehouse provides information from the historical point
of view.
Non-volatile − Non-volatile means the previous data is not erased when new data is
added to it. A data warehouse is kept separate from the operational database and therefore
frequent changes in operational database is not reflected in the data warehouse.
Note − A data warehouse does not require transaction processing, recovery, and concurrency
controls, because it is physically stored and separate from the operational database.
Data Warehouse Applications
As discussed before, a data warehouse helps business executives to organize, analyze, and use
their data for decision making. A data warehouse serves as a sole part of a plan-execute-assess
"closed-loop" feedback system for the enterprise management. Data warehouses are widely used
in the following fields −
Financial services
Banking services
Consumer goods
Retail sectors
Controlled manufacturing
Types of Data Warehouse
Information processing, analytical processing, and data mining are the three types of data
warehouse applications that are discussed below −
Information Processing − A data warehouse allows to process the data stored in it. The
data can be processed by means of querying, basic statistical analysis, reporting using
crosstabs, tables, charts, or graphs.
Analytical Processing − A data warehouse supports analytical processing of the
information stored in it. The data can be analyzed by means of basic OLAP operations,
including slice-and-dice, drill down, drill up, and pivoting.
Data Mining − Data mining supports knowledge discovery by finding hidden patterns
and associations, constructing analytical models, performing classification and prediction.
These mining results can be presented using the visualization tools.
Data mining
Data mining (sometimes called data or knowledge discovery) is the process of analyzing
data from different perspectives and summarizing it into useful information - information
that can be used to increase revenue, cuts costs, or both.
Data mining software is one of a number of analytical tools for analyzing data. It allows
users to analyze data from many different dimensions or angles, categorize it, and
summarize the relationships identified.
Technically, data mining is the process of finding correlations or patterns among dozens
of fields in large relational databases.
Data Mining is defined as extracting information from huge sets of data. In other words,
we can say that data mining is the procedure of mining knowledge from data.
The key properties of data mining are
Automatic discovery of patterns
Prediction of likely outcomes
Creation of actionable information
Focus on large datasets and databases
The information or knowledge extracted so can be used for any of the following
applications –
• Market Analysis
• Fraud Detection
• Customer Retention
• Production Control
• Science Exploration
Roll-up
Drill-down
Slice and dice
Pivot (rotate)
Supply chain involved all the stages directly or indirectly in fulfilling a customer request which
includes manufacturers, suppliers, transporters, warehouses, retailers and customers. It is the
integration of demand and supply. Examples of supply chain activities include farming,
refining, design, manufacturing, packaging, and transportation.
Suppliers
Manufacturers / Producer
Deal
REailers, Customer
etc., Work together
in an effort to
Acquire raw materials
Convert these raw materials into specified final products, and
Deliver these final products to retailers.
Supply chain management basically merges the supply and demand management.
It uses different strategies and approaches to view the entire chain and work
efficiently at each and
every step involved in the chain. Every unit that participates in the
process must aim to minimize the costs and help the companies to
improve their long term performance, while also creating value for
its stakeholders and customers. This process can also minimize the
rates by eradicating the unnecessary expenses, movements and
handling.
Creation era
The term "supply chain management" was first coined by Keith Oliver in 1982.
However, the concept of a supply chain in management was of great importance long before, in the
early 20th century, especially with the creation of the assembly line. The characteristics of this era of
supply-chain management include the need for large-scale changes, re-engineering, downsizing driven
by cost reduction programs, and widespread attention to Japanese management practices. However,
the term became widely adopted after the publication of the seminal book Introduction to Supply
Chain Management in 1999 by Robert B. Hand field and Ernest L. Nichols, Jr., which published over
25,000 copies and was translated into Japanese, Korean, Chinese, and Russian.
UNIT II
ERP-MANUFACTURING PERSPECTIVE
Material Requirement Planning
Material requirement planning is a system based approach, which organizes all
necessary production material. Material Requirements Planning, abbreviated as
MRP is a straightforward system to calculate arithmetically the requirements of
the input materials at different points of time based on actual production plan.
Theorists described MRP as a planning and scheduling system to meet time-
phased materials requirements for production operations. It is a set of techniques
that calculate the requirement of all items structured in bill of material. The
calculated requirements are based on the quantity and timing requirement of end
items listed in master production schedule. The item calculation requirement is
based on the master production schedule, the bill of material file and the item
master file (Toomey, 1996). The main intent of is to meet the delivery schedule of
finished products as specified in the master production schedule. MRP is a
material planning method that developed in the decade of1970 that utilized
computer technology.
1. Material planning provides information that all the required raw material and
products are available for production.
2. Material planning guarantees that inventory level is maintained at its minimum
levels. But also ensures that material and product are available whenever
production is scheduled, therefore, helping in matching demand and supply.
3. Material planning provides information of production planning and scheduling
but also provides information around dispatch and stocking.
The major objectives of MRP: The goal of the Material Requirements Planning
document is to supply information that will facilitate the company to have enough
inventory on hand to fulfil demand, available only when needed at a quality level
that meets specification, (and at the lowest price. A good Material Requirements
Planning program can offer the fundamental needs of keeping inventory levels
low and fulfilling customer expectations for on time delivery.
Architecture
Master Production Schedule: MPS is designed to fulfil the market demand that
include company orders and forecasted demand in future in the taken planning
horizon. MPS mainly represents the complete delivery schedule of the end
products. However, orders for replacement components can also be included in it
to make it more comprehensive.
Bill of Materials File: This symbolizes the product structure. It includes
information about all sub components needed, their quantity, and their sequence
of develop in the end product. Information about the work centres performing
build-up operations is also included in it (Toomey, 1996).
Inventory Status File: Inventory status file maintains recent record of each item
in the inventory. Information such as, item identification number, quantity on
hand, safety stock level, quantity already allocated and the procurement lead
time of each item is recorded in this file.
After getting input from these sources, MRP logic processes the available
information and gives information about the following:
Planned Orders Receipts: This is the order quantity of an item that is planned
to be ordered so that it is received at the beginning of the period under
consideration to meet the net requirements of that period. This order has not yet
been placed and will be placed in future.
Planned Order Release: This is the order quantity of an item that is planned to
be ordered in the planned time period for this order that will ensure that the item
is received when needed. Planned order release is determined by offsetting the
planned order receipt by procurement lead time of that item.
1. Identifying requirement.
2. Running MRP- creating the suggestion.
3. Firming the suggestion.
Major issues of using procedure of Material requirements planning are that they
are not fully perfect. If there is some error in the system, then it is going to throw
off all the other numbers thus making the outputted data inaccurate. The issue
with MRP systems is the integrity of the data. If there are any errors in the
inventory data, the bill of materials, that are called 'BOM data, or the master
production schedule, then the outputted data will also be incorrect. Data integrity
is impacted by imprecise cycle count adjustments, mistakes in receiving input
and shipping output, scrap not reported, waste, damage, box count errors,
supplier container count errors, production reporting errors, and system issues.
Many of these types of errors can be minimized by implementing pull systems
and using bar code scanning. Most sellers of this type of system recommend at
least 99% data integrity for the system to give valuable results. Another problem
is that Material requirements planning systems do not necessarily factor in other
warehouses in other cities or states. Therefore, the system will explain that
company do not need to order anymore parts when in fact those parts are in
other factories. Other major factor is that the MRP system can not consider
manpower.
Ordering too much inventory, which increases carrying costs and ties up more
cash in inventory overhead that could be used elsewhere.
Inability to meet demand because of insufficient raw materials, resulting in lost
sales, canceled contracts and out-of-stocks.
Disruptions in the production cycle, delaying sub-assembly builds that result in
increased production costs and decreased output.
Manufacturing companies rely heavily on MRP as the supply planning system
to plan and control inventory, scheduling and production, but MRP is also
relevant in many other industries, from retail to restaurants, to create balance
between supply and demand.
3. Scheduling production.
Using the master production schedule, the system determines how
much time and labor are required to complete each step of each build
and when they need to happen so that the production can occur without
delay.
The production schedule also identifies what machinery and
workstations are needed for each step and generates the appropriate
work orders, purchase orders and transfer orders. If the build requires
subassemblies, the system takes into account how much time each
subassembly takes and schedules them accordingly.
MRP steps include identifying requirements, checking inventory, scheduling production, and identifying
issues.
MRP Inputs
How well your MRP system works depends on the quality of the data you
provide it. For an MRP system to work efficiently, each input must be accurate
and updated. Here are some of the inputs an MRP depends on:
Demand
Including sales forecasts and customer orders. When working with predicted
demand, a system that is integrated with an enterprise-wide ERP system
allows forecasting using historical sales vs. just sales forecasts.
Inventory
It’s essential to have a real-time view of inventory across the organization to
understand what items you have on hand and which are en route or have
purchase orders issued, where that inventory is and what the inventory’s
status is.
MRP Outputs
Using the provided inputs, the MRP calculates what materials are needed,
how much is needed to complete the build and when in the build process they
are needed.
Benefits of MRP
MRP systems allow you to plan and schedule production efficiently, making
sure materials move through the work order quickly and helping businesses
fulfill customer orders on time.
When builds are complex and require multiple sub-assemblies within the work
order, it’s easy to miscalculate timing. An MRP helps you understand all of the
components that go into each sub-assembly and how long it takes to
complete each step, preventing delays in the production cycle and increasing
production yield.
MRP Challenges
Although using an MRP solution is a far better than using spreadsheets for
supply planning, it’s only as good as the data you put into it. The better a
business understands and documents its processes, the better an MRP
system can serve them.
You need to make sure you input correct inventory availability, time to
complete a subassembly, waste calculations and lead-times from vendors.
Otherwise, your production schedule will be inaccurate—an MRP can’t define
the production build timeline and materials required if the data isn’t accounted
for in the inventory record, bill of materials and master production schedule
Advantages of Distribution
Requirements Planning (DRP)
The advantages of distribution requirements planning (DRP) pertain to the following:
DRP always connects to the current inventory and forecasts of field demand to manufacturing’s MPS and
MRP. DRP allows for a fully integrated system and a continuous flow of information throughout the network.
This pushes for a much more efficient and adequate production process/flow that ultimately cut costs and
waste within a manufacturing operation.
DRP is also accurately able to anticipate future requirements in the field. This enables for decreased inventory
and costs within an operation and ultimately increases the organization’s profit. Anticipation of future
requirements is by far one of the most beneficial aspects pertaining to distribution requirements planning
(DRP).
DRP matches material supply to demand, once again ultimately matching inventory to the customer service
requirements and cutting costs within an operation. DRP also pushes for faster decision making, utilization of
demand forecasting, planning initiation accuracy, and enhances overall customer service.
JUST IN TIME
The Just-In-Time technique based manufacturing system, developed and implemented in the Toyota
Motor Company may be defined as manufacturing only the necessary items in exact quantities and at
the required time
The purpose of JIT is to produce a unit, such a way that there is only one unit of work in process and
minimum stock of finished goods in inventories. Excess inventories invite troubles and bad causes. Those
goods, which are to be consumed only, are to be produced and replaced. Based on the above idea,
system has to be developed to produce one unit just in time to go into the next process in an ideal
situation. An ideal situation is near about impossible, and even Japanese firm has not attained such a
situation. They work aggressively to get as close as possible to stockless production.
JIT deliveries involve getting exactly the right amount ofitems at exactly the right place at just the right
time. The JIT philosophy basically aims to achieve Five zeros. db Zero inventory efo Zero defect cfc Zero
Material handling &b Zero Lead time 4b Zero Setup time The primary goal of JIT is to promote better
better, faster customer service while reducing inventory and labour costs. This is accomplished by
reducing the amount of Work-In-Process (WIP) on the shopfloor and shortening cycle times. There are
several policies and methods, companies use to achieve a successful JIT program. Some simplify bills
ofmaterials and part routing. Some have eliminated work orders. Setup times between jobs have been
minimized to further reduce cycle times. JIT also helps produce goods economically, quickly and safely.
The structure ofJIT is designed based on the factor that significant cost saving can be achieved by
producing the necessary quantities. This can emerge into a pull system wherein the subsequent station
waits for the preceding station to perform the operation to cater to the demand. This can be done
effectively by proper line balancing the operations in the manufacturing line.
Just in time (JIT) “Just-in-Time” means making “only what is needed, when it is needed, and in the
amount needed”. Supplying “what is needed, when it is needed, and in the amount needed” according
to this production plan can eliminate waste, inconsistencies, and unreasonable requirements, resulting
in improved productivity. A production strategy that strives to improve return on investment by
reducing inventory and associated costs To meet JIT objectives, the process relies on signals or (Kanban)
between different points, which are involved in the process, which tell production when to make the
next part. Kanban are usually “tickets” but can be simple visual signals, such as the presence or absence
of a part on a shelf. Implemented correctly, JIT focuses on continuous improvement and can improve a
manufacturing organization's return on investment, quality, and efficiency. To achieve continuous
improvement key areas of focus could be flow, employee involvement and quality. JIT relies on other
elements in the inventory chain as well. For instance, its effective application cannot be independent of
other key components of a lean manufacturing system or it can. “end up with the opposite of the
desired result.” In recent years manufacturers have continued to try to hone forecasting methods such
as applying a trailing 13-week average as a better predictor for JIT planning; however, some research
demonstrates that basing JIT on the presumption of stability is inherently flawed. Philosophy. The
philosophy of JIT is simple: the storage of unused inventory is a waste of resources. JIT inventory
systems expose hidden cost of keeping inventory, and are therefore not a simple solution for a company
to adopt it. The company must follow an array of new methods to manage the consequences of the
change. The ideas in this way of working come from many different disciplines including statistics,
industrial engineering, production management, and behavioral science. The JIT inventory philosophy
defines how inventory is viewed and how it relates to management. Inventory is seen as incurring costs,
or waste, instead of adding and storing value, contrary to traditional accounting. This does not mean to
say JIT is implemented without awareness that removing inventory exposes pre-existing manufacturing
issues. This way of working encourages businesses to eliminate inventory that does not compensate for
manufacturing process issues, and to constantly improve those Downloaded by Thamaraiselvi.M grdcs
SCIB (thamaraiselvi.m@grd.edu.in) lOMoARcPSD|5329935 processes to require less inventory.
Secondly, allowing any stock habituates management to stock keeping. Management may be tempted
to keep stock to hide production problems. These problems include backups at work centers, machine
reliability, process variability, and lack of flexibility of employees and equipment, and inadequate
capacity. In short, the Just-in-Time inventory system focus is having “the right material, at the right time,
at the right place, and in the exact amount”, without the safety net of inventory. The JIT system has
broad implications for implementers. Effects/Considerations 1. Transaction cost JIT helps in keeping
inventory to minimum in a firm. However, a firm may simply be outsourcing their input inventory to
suppliers, even if those suppliers don’t use JIT investigated this effect and found that suppliers in Japan
charged JIT customers, on average, a 5% price premium. 2. Environment JIT, multiple daily deliveries.
Increased scale has required a move to vans and lorries. Potential and actual problems with regard to
gridlock and burning of fossil fuels. This violates three JIT waste guidelines: Time—wasted in traffic
jams Inventory—specifically pipeline being transported Waste—fuel burned in deliveries 3. Price
More orders equals more deliveries more handling equals increased cost, which translates into price
increase. 4. Quality JIT implicitly assumes that input parts quality remains constant over time. If not,
firms may hoard high-quality inputs. As with price volatility, a solution is to work with selected suppliers
to help them improve their processes to reduce variation and costs. Longer-term price agreements can
then be negotiated and agreed-on quality standards made the responsibility of the supplier. Fixing up of
standards for volatility of quality according to the quality circle 5. Demand Highlights the importance of
relatively stable demand, which helps Downloaded by Thamaraiselvi.M grdcs SCIB
(thamaraiselvi.m@grd.edu.in) lOMoARcPSD|5329935 ensure efficient capital utilization rates. 6. Supply
stability Strikes and natural disasters can affect supply. Implementation Benefits 1. Reduced setup time.
Cutting setup time allows the company to reduce or eliminate inventory for “changeover” time. 2. The
flow of goods from warehouse to shelves improves. Small or individual piece lot sizes reduce lot delay
inventories, which simplifies inventory flow and its management. 3. Employees with multiple skills New
skills are acquired and are used more efficiently. Having employees trained to work on different parts of
the process allows companies to move workers where they are needed. 4. Production scheduling Work
synchronized with demand. If there is no demand for a product at the time, it is not made. This saves
the company money, either by not having to pay workers overtime or by having them focus on other
work or participate in training. 5. Increased emphasis on supplier relationships. A company without
inventory does not want a supply system problem that creates a part shortage. This makes supplier
relationships extremely important. 6. Supplies Supplies come in at regular intervals throughout the
production day and are synchronized with production demand and the optimal amount of inventory is
on hand at any time. When parts move directly from the truck to the point of assembly, the need for
storage facilities is reduced. 7. Minimizes storage Less stock needs less space. Downloaded by
Thamaraiselvi.M grdcs SCIB (thamaraiselvi.m@grd.edu.in) lOMoARcPSD|5329935 8. Stock age Reduced
chance of inventory being out of date (life or fashion), damaged, stolen Problems 1. Supply shocks The
JIT operation leaves suppliers and downstream consumers open to supply shocks and large supply or
demand changes. 2. Multiple deliveries Very low stock levels means shipments of the same part can
come in several times per day. Alternate suppliers. Suppliers will improve capability and documentation.
The Toyota effect Additional benefits 1. Improved customer satisfaction By providing deliveries within a
day or two of the minimum economic shipping delay. 2. Building to order Vehicles built to order,
eliminating the risk they would not be sold. This improved the company's return on equity. 3. Quality
improvement Since assemblers no longer had a choice of which part to use, every part had to fit
perfectly. This caused a quality assurance crisis, which led to a dramatic improvement in product quality.
Eventually, Toyota redesigned every part of its vehicles to widen tolerances, while simultaneously
implementing careful statistical controls for quality control. Toyota had to test and train parts suppliers
to assure quality and delivery. In some cases, the company eliminated multiple suppliers. When a
process or parts quality problem surfaced on the production line, the entire production line had to be
slowed or even stopped. No inventory meant a line could not operate from in-process inventory while a
production problem was fixed. Many people in Toyota predicted that the initiative would be abandoned
for this reason. In the first week, line stops occurred almost hourly. But by the end of the first month,
the rate had fallen to a few line stops per day. After six months, line stops had so little economic effect
that Toyota
INTRODUCTION – PRODUCT DATA MANAGEMENT
PDM is defined as “is the discipline of controlling the evolution of a product and
providing other procedures and tools with the accurate product information at the
right time in the right format during the entire PLC”.
However, normally PLM focuses on the whole lifecycle of a product and PDM is a
storage location for all the information that is related to the product.
Because of this confusion of the terms the actual information concerning only the
PDM seems to be hard to find, or in fact hard to differentiate from PLM
information. [1] The history of PDM started in the early 1980s.
Because of the lack of computers, PDM was operated manually and designers
managed the drawings and data sheets by hand. After the escalating access to
computers and designing programs, PDM was linked to these designing systems
(CAx). The linked tools were user unfriendly, so their development continued and
in the middle of the 1990s PDM had a strong foothold in the field of engineering.
Everyone involved has to have access to the information and in this case the PDM
system can help: the system itself converts the files, for example, to pdf-format, so
that everybody can open them no matter what the native file format was.
One of the most important principles of the PDM system is that the information is
easy and swift to find. As mentioned earlier, all the created data should be put in to
the system, nothing should be based on a single engineer's knowledge. [3] As Stark
[4] wrote: “Users need support from data management systems so that they will not
discard potentially useful data”.
Product data management (PDM) or product lifecycle management (PLM) systems
provide the tools to control access to and manage all product definition data. It
does this by maintaining information (meta-data) about product information. PDM
or PLM systems, when tightly integrated with other product development tools, do
this transparently and with minimal additional effort on the part of the user. In
addition, PDM tools provide valuable functionality with process management
particularly as it relates to configuration management or engineering change
control. This environment is depicted below.
Product lifecycle management systems vary in their functionality, but some of their
common capabilities are described below.
Access Control
Access control to each element in the product definition data base can be specified.
Read only access can be given to personnel not directly involved with the design,
development and planning process. Creation and maintenance access can be given
to the individuals responsible for product and process design. As product data
management systems evolve towards collaborative product commerce (CPC)
systems which are used across multiple enterprises in a supply chain, access
control becomes more critical and requires control to limit access to specific
projects, products or parts for a specific supplier or customer.
Component / Material Classification
Components and materials can be classified and organized and attributes assigned.
This supports standardization by identifying similar components/materials,
eliminating redundancy, and establishing a preferred parts list. Establishing classes
and subclasses with attributes allows a designer to search and select a needed
material, component or assembly with minimal effort thereby avoiding having to
re-specifying an existing or similar component or material.
Product Structure
Since the relationship of a product’s parts is a logical one maintained by the
information system rather than a fixed physical relationship as represented on a
drawing, it is possible to readily maintain more than one relationship. This will
allow different views of part relationships in assemblies to correspond to the
various departmental needs (e.g., engineering and manufacturing product
structures), while maintaining rigor and consistency of the product’s definition
through this single data base. Thus, this one logical data base can support product
and process design requirements as well as maintain part relationships to serve as a
manufacturing bill of materials for MRP II/ERP. In other words, PDM provides the
ability to hold not just the physical relationships between parts in an assembly but
also other kinds of structures; for instance, manufacturing, financial, maintenance
or document relationships. So, it is possible for specialist team members to see the
product structured from their point of view. Product data can be accessed via this
complete Bill of Materials. This access includes assemblies, parts and related
documents.
An integrated approach to developing, organizing and maintaining part and product
definition data facilitates the design process, makes design data more readily
usable and enhances integration with process requirements.
Engineering Changes
Engineering changes can be facilitated with this configuration management and
administrative control embedded within the system. CAE/ CAD tools will enable
engineering changes to be more thoroughly developed and analyzed to better
define change impact. Once a design has been created, it can be checked-out
electronically to a workstation for engineering changes. When the changes have
been made, it can be returned to the central database and placed in a queue or an
email notification sent for approval by designated parties. In this manner, a Change
Control Board (CCB) can even “convene” and provide individual member’s input
electronically. In addition to supporting engineering analysis, information related
to procurement, inventory, manufacturing and cost is available for members of the
CCB to evaluate, designate the effectivity of the change and determine the
disposition of existing items.
Process Management and Workflow
PDM or PLM systems support process management by defining process steps
related to the development, distribution and use of product data. The process is
defined in the form of specified process steps and release or promotion levels that
the data must achieve. The manner in which the process is defined varies with
Enterprise resource planning (ERP) systems have become a critical tool for
businesses over the past several decades. An ERP solution automates
critical business processes and serves as a shared database for all
financial and operational information from across the company. It pulls this
data from a number of modules built to help various departments, from
accounting to supply chain to human resources, perform their individual
functions.
An ERP solution gives all employees access to the information they need
to answer important questions about their department’s current
performance and future planning, as well as target areas for improvement.
This single source of information minimizes data accuracy and consistency
issues and ensures everyone is looking at the same numbers, no matter
their role. It also drives better decision-making that leads to more efficient
processes and cost savings. Additionally, ERP can automate many tasks,
reducing errors and freeing up employees to focus on more strategic work.
Common ERP modules support back- and front-office functions like finance
and accounting, procurement, manufacturing, inventory management,
order management, warehouse management, supply chain
management, customer relationship management (CRM) procurement and
workforce management. More functionally rich solutions may also include
professional services automation (service resource management), human
resources management, ecommerce and marketing automation.
Each ERP module is designed for specific business functions, providing the
data and supporting the processes that will help those employees do their
jobs. Every module plugs into the ERP system, so the system provides a
single source of accurate data, even as the business adds new modules. If
the ERP system is the toolbox, the modules are the screwdriver, wrench,
hammer and other tools in the box that each have specific uses.
2. Procurement
The procurement module, also known as the purchasing module, helps an
organization secure the materials or products it needs to manufacture
and/or sell goods. Companies can keep a list of approved vendors in this
module and tie those suppliers to certain items, helping with supplier
relationship management. The module can automate requests for a quote,
then track and analyze the quotes that come in.
3. Manufacturing
The earliest version of ERP, material requirements planning (MRP)
systems, were designed for manufacturers, and manufacturing remains a
key piece of ERP. Today, ERP systems typically have a production
management or manufacturing execution system (MES). The
manufacturing module helps manufacturers plan production and make sure
they have everything they need for planned production runs, like raw
materials and machinery capacity. During the manufacturing process, it can
update the status of goods-in-progress and help companies track actual
output against forecasted production. It also provides a real-time picture of
the shop floor, capturing information on items in progress and finished
goods. It can calculate the average time to produce an item and then
compare supply with forecasted demand to plan adequate production.
4. Inventory Management
The inventory management module enables inventory control by tracking
item quantities and location down to individual SKUs. This module offers a
complete picture of not only current but also incoming inventory, through an
integration with the procurement tool. This piece of software helps
businesses manage inventory costs, making sure they have sufficient stock
without tying up too much cash in inventory. An inventory management
application can weigh sales trends against available product to helps
companies make informed decisions that boost margins and increase
inventory turn (a measure of how often inventory is sold over a certain
period). It can help prevent stockouts and delays, which enhances
customer service.
Businesses that lack other supply chain management modules may also
use the inventory management application to handle purchase orders,
sales orders and shipping. Larger organizations will need a version of this
solution that can track inventory across multiple locations.
5. Order Management
An order management module tracks orders from receipt to delivery. This
piece of the ERP feeds all orders to the warehouse, distribution center or
retail store after customers place them and tracks their status as they’re
prepared, fulfilled and shipped to the customer. The order management
module prevents orders from being lost and boosts on-time delivery rates
to keep customers happy and cut unnecessary expenses for expedited
shipping.
6. Warehouse Management
A warehouse management module can deliver a rapid return on investment
for businesses that operate their own warehouses. This application can
efficiently guide warehouse employees through all warehouse processes
based on the layout of the facility, from putaway when shipments arrive to
picking to packing and shipping. It can also help companies plan labor
based on expected order volume. The warehouse management module
can support different picking strategies like batch picking, wave picking and
zone picking depending on which is most efficient for a given business, and
some modules can show employees the most efficient pick path.
Many businesses also use CRM to manage sales leads and opportunities.
It can track communication with prospects and suggest which customers
should be targeted for certain promotions or cross-sell opportunities. More
robust CRM modules may support customer segmentation (enabling more
targeted marketing) and advanced contact managers and reporting tools.
9. Professional Services Automation (Service Resource Management)
A professional services automation (PSA) module, also called a service
resource management module, allows an organization to plan and manage
projects. Services-based businesses often use this module. The application
tracks the status of projects, managing human and capital resources
throughout, and allows managers to approve expenses and timesheets. It
facilitates collaboration between teams by keeping all related documents in
a shared place. Additionally, the PSA module can automatically prepare
and send bills to clients based on rules around the billing cycle.
Payroll could also fall under the workforce management module. A payroll
sub-module automatically distributes paychecks to employees on a set
schedule with the appropriate taxes deducted and handles expense
reimbursement. It can also provide reports on payroll expenses, total
overtime hours and similar KPIs.
1.
Preventive Maintenance
2. Predictive Maintenance
For this purpose, asset monitoring, asset analytics & performance are
analyzed regularly so that anticipation can be made. This is one of the most
used plant maintenance types as no plant manager wants unexpected
asset failure.
In this way, asset uptime increases and downtime decreases. For this
purpose, sensors and artificial intelligence are used so that predictions can
be made without compromising accuracy.
4. Corrective Maintenance
In this technique, the machine is brought back into running condition, but
the root cause is not identified. Mostly corrective maintenance is used on
those assets which are run to failure.
5. Emergency Maintenance
QUALITY MANAGEMENT
The quality management module is one of the important modules in the ERP system. Quality
management helps the industry to inspect and maintain the quality of manufactured items that
match the standards for certification. Every market has specific expectations from the product
that hit the shelves.
The quality management module is one of the important modules in the ERP system.
Quality management helps the industry to inspect and maintain the quality of
manufactured items that match the standards for certification. Every market has specific
expectations from the product that hit the shelves. Quality management or quality
control module keeps those expectations in check. Quality control management
performs checks at various checkpoints to track the quality of the manufactured item.
ERP quality management module prevents defects in the manufactured items.
The ERP for quality management is also used to set up, manage, and track quality
control plan. To track the quality control plan, the plan has to be set up in the ERP
software using a quality management module. This module interacts with various
modules for assessing the quality of manufactured products. Material management and
production planning are two modules from which the quality control management
module exchanges information and data. This data is stored centrally so that the
modules can easily access the data.
ERP for quality management deals constantly with the task or operation of checking and
keeping the produced products keep up with the company standards. Lighthouse ERP
for quality management or quality control meticulously checks and maintains the high
standards and quality of the products to ensure that customers always gets the top-
notched product. Unable to keep up with standards and guidelines of quality can lead to
disaster in the industry. Some of the industries where Lighthouse ERP for quality
management is implemented and doing exemplary job are steel industries, plastic
industries, coal industries, FMCG industries, and aluminium industry.
Users can define various aspects and test criteria in the module for testing. The quality
control management module can be used to define these criteria.
Testing criteria include tolerance percentages, parameter testing, & mapping of test
products. These tests are done automatically and results are generated.
The products while failing these tests are put in rejected or failed list and space in the
warehouse is automatically allocated. Multiple tests are assigned and done on various
products.
Quality Inspection
Basic testing is performed on every product on a production line. The quality control
management module also enables the industry to set due dates for the tests.
Test results are also linked to the vouchers such as purchase orders or production
orders. This makes the system accessible testing results for everyone.
The status of the test results can be easily obtained with one click. The test reports are
also readily available and stored centrally on the server.
Module Integration
The ERP Software for quality management has to collect a plethora of information
and data from other modules to help it assess the quality of a product.
Module integration makes it possible to integrate quality control management module
into other modules and sub-modules. This helps tremendously for analysis.
Module integration also helps in eliminating data duplication that enriches processes &
data flow with accurate and real information. This also helps in approaching with right
strategies.
Quality Certification
Quality standards and criteria define the quality of a product. Various standards of
quality are applied to a variety of products. These standards have to be matched.
Quality certification helps the customers to know about the quality standards of the
product. Customers can also view defined standards passed by the product.
These standards are listed in the certificate. International organization for
Standardization develops various standards for different products that it must pass to
obtain an ISO certificate.
Quality management module reduces the inspection cost as the industry itself is
competent in assessing the quality of the items.
Quality control management effectively increases the efficiency of resource usage
so that nothing is wasted.
Production methods can have a huge impact on them by collecting the right data
from the production process.
Products manufactured in the industry maintain the same quality as all so that
uniformity of products is formed.
Customers seeking good quality products can receive them without any defect, so
customer satisfaction is guaranteed.
Customer satisfaction ensures that more orders for the products are placed, thus
increasing the profitability of the business.
Quality management and control can help is a reduction of operational cost due to
the elimination of defective products on a production line.
Quality control & management plays a significant role in improving the overall quality of
the products thus improving the working of ERP module. Quality management is ERP
software that ensures that the products are safe to use and are exactly as they should
be. This module also ensures that the products match the guidelines and specifications
to pass the quality certification process. Lighthouse Info provides industry-specific ERP
software to all the industries. Lighthouse ERP is one of the best ERP software and can
improve the workflow of the industries tremendously. This makes the software an
absolute digital solution in all industries. 35+ years of experiences and constant
upgrades make the software cater to all the needs of modern industries.
I
7. Collaboration
8. Operational Efficiency
9. Organized Workflows
It’s essential that your report reflects the latest data, and that’s why
real time is so important. If it takes two weeks to receive revenue
numbers from the last quarter, that’s not very useful because the
information is already outdated and may not be relevant. But if
revenue totals update in real time, as each sale happens, you can
immediately use it to inform decision-making. This has become
critical in today’s fast-paced, hyper-competitive environment.
11. Mobility
Since
Fourth Large Scale Integration PC
1980
Data: Facts, figures, statistics etc. having no particular meaning (e.g. 1, ABC, 19 etc).
Record: Collection of related data items, e.g.
in the above example the three data items had no meaning. But if we organize them in the following
way, then they collectively represent meaningful information. Roll Name Age 1 ABC 19
The facts that can be recorded and which have implicit meaning known as 'data'. Example: Customer
----- 1.cname. 2.cno. 3.ccity.
Database: It is a collection of interrelated data . These can be stored in the form of tables.
A database can be of any size and varying complexity. A database may be generated and manipulated
manually or it may be computerized. Example: Customer database consists the fields as cname, cno, and
ccity Cname Cno Ccity
Database System: It is computerized system, whose overall purpose is to maintain the information and
to make that the information is available on demand.
Advantages:
It is a collection of programs that enables user to create and maintain a database. In other words it is
general-purpose software that provides the users with the processes of defining, constructing and
manipulating the database for various applications.
Security Problems.
. Advantages of DBMS:
1.Data Independence.
4.Data administration.
Applications
Database Applications:
Manufacturing: production, inventory, orders, supply chain Human resources: employee records,
salaries, tax deductions .
Many persons are involved in the design, use and maintenance of any database.
Actors on the scene: The people, whose jobs involve the day-to-day use of a database are called as
'Actors on the scene', listed as below.
1.Database Administrators (DBA): The DBA is responsible for authorizing access to the database, for
Coordinating and monitoring its use and for acquiring software and hardware resources as needed.
These are the people, who maintain and design the database daily. DBA is responsible for the following
issues. 3 a. Design of the conceptual and physical schemas: The DBA is responsible for interacting with
the users of the system to understand what data is to be stored in the DBMS and how it is likely to be
used. The DBA creates the original schema by writing a set of definitions and is Permanently stored in
the 'Data Dictionary'. b. Security and Authorization: The DBA is responsible for ensuring the
unauthorized data access is not permitted. The granting of different types of authorization allows the
DBA to regulate which parts of the database various users can access. c. Storage structure and Access
method definition: The DBA creates appropriate storage structures and access methods by writing a set
of definitions, which are translated by the DDL compiler. d. Data Availability and Recovery from Failures:
The DBA must take steps to ensure that if the system fails, users can continue to access as much of the
uncorrupted data as possible. The DBA also work to restore the data to consistent state. e. Database
Tuning: The DBA is responsible for modifying the database to ensure adequate Performance as
requirements change. f. Integrity Constraint Specification: The integrity constraints are kept in a special
system structure that is consulted by the DBA whenever an update takes place in the system.
2.Database Designers: Database designers are responsible for identifying the data to be stored in the
database and for choosing appropriate structures to represent and store this data. 3. End Users: People
who wish to store and use data in a database. End users are the people whose jobs require access to the
database for querying, updating and generating reports, listed as below. a. Casual End users: These
people occasionally access the database, but they may need different information each time. b. Naive or
Parametric End Users: Their job function revolves around constantly querying and updating the
database using standard types of queries and updates. c. Sophisticated End Users: These include
Engineers, Scientists, Business analyst and others familiarize to implement their applications to meet
their complex requirements. d. Stand alone End users: These people maintain personal databases by
using ready-made program packages that provide easy to use menu based interfaces. 4.System Analyst:
These people determine the requirements of end users and develop specifications for transactions.
5.Application Programmers (Software Engineers): These people can test, debug, document and maintain
the specified transactions. Department of CSE,JBIET 4 b. Workers behind the scene: Database Designers
and Implementers: These people who design and implement the DBMS modules and interfaces as a
software package. 2.Tool Developers: Include persons who design and implement tools consisting the
packages for design, performance monitoring, and prototyping and test data generation. 3.Operators
and maintenance personnel: These re the system administration personnel who are responsible for the
actual running and maintenance of the hardware and software environment for the database system.
DATABASE SYSTEMS
What is a Database?
Another example is the library. The library contains a huge collection of books of
different genres, here the library is database and books are the data.
DBMS is a collection of inter-related data and set of programs to store & access
those data in an easy and effective manner.
According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been
removed before storage.
Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that
case if the customer information such as customer name, address etc. are stored
at both places then this is just a wastage of storage (redundancy/ duplication of
data), to organize the data in a better way the information should be stored at
one place and both the accounts should be linked to that information somehow.
The same thing we achieve in DBMS. Fast Retrieval of data: Along with storing the
data in an optimized and systematic manner, it is also important that we retrieve
the data quickly when needed. Database systems ensure that the data is retrieved
as quickly as possible.
Consider a university that keeps the data of students, teachers, courses, books
etc. To manage this data we need to store this data somewhere where we can
add new data, delete unused data, update outdated data, retrieve data, to
perform these operations on data we need a Database management system that
allows us to store the data in such a way so that all these operations can be
performed on the data efficiently.
3. Banking System: For storing customer info, tracking day to day credit and debit
transactions, generating bank statements etc. All this work has been done with
the help of Database management systems.
6. Education sector: Database systems are frequently used in schools and colleges
to store and retrieve the data regarding student details, staff details, course
details, exam details, payroll data, attendance details, fees details etc. There is a
hell lot amount of inter-related data that needs to be stored and retrieved in an
efficient manner.
7. Online shopping: You must be aware of the online shopping websites such as
Amazon, Flipkart etc. These sites store the product information, your addresses
and preferences, credit details and provide you the relevant list of products based
on your query. All this involves a Database management system.