INDEX

Contents Title of the Project Introduction and Objectives of the Project Project Category Tools/Platform, Hardware & Software requirement specification Complete Structure of the Program a. b. c. d. e. f. g. 6. Analysis (DFDs) ER Diagram Modules and their brief description Data Structure (Tables) Process Logic of each Module Types of Report generation Validation Checks 02

Page No.

03-04 05 06 07-09 10 11-14 15-23 24-25 26 27 28

Scope of future application

TITLE OF THE PROJECT

PRODUCTION MANAGEMET SYSTEM

INTRODUCTION
Enterprises resource Planning ( E.R.P ) is an integrated monitoring system. It can be used as resource planning system. In this system customer interact with system and get desire output. In this system various modules are interacted these are Inventory, Sales, Purchase, Product Planning & control. Each module may have various sub-modules. Although Internet started as an experimental project of U.S government in 1960 and it gone through many changes, development and became commercial success in 1990.Now a days Internet plays a vital role in many organization, such as BUSSINESS ORGANIZATION. It is concerned with customer and company. A company may have so many branches, in order to centralize the control over the organization; a system is developed so that each department uses the system with authority. In the modern world of really tough competition and rivalry among industries for supremacy, time becomes the reckoning factor for the success of any company. Time management and optimized use of resources play the most important part in development of any company. It is extremely important for any company to manage the resources tactfully so that it can exist in the market and grow.

OBJECTIVE
Production records the actual production against the planned production schedule in the job card. Downtimes details are captured and analysis is done on the same. All produced items go through quality control before being passed to main stores. The shop floor inventory is maintained separately. An important report to analyze the variance between actual planned productions, consumption analysis is available. Production software keeps a track of the machine planning specifications that are used in the production process like machine capacity, machine efficiency, listing, etc. Shift master records the working schedule of machines, machine down time reason can also be recorded. Production allows us to issue job card for the production of an item. The Job Card stores the actual quantity produced against the planned quantity. After and before the production a quality check is done. If the raw material is not suitable for the production, then it is rejected and it is not sent to the production floor. Production allows us to issue job card for the production of an item. The Job Card stores the actual quantity produced against the planned quantity. After and before the production a quality check is done. If the raw material is not suitable for the production, then it is rejected and it is not sent to the production floor.

PROJECT CATEGORY
CLIENT/SERVER This project is based on RDBMS (Relational Data Base Management System). There is interaction between customer and company. So all the information stored on DATABASE. In a client/server application, software is divided between client (normally PCs) and server ( a more powerful computer ) that typically maintains a centralized database. This concurrent process model is often used as the paradigm for the development of client/server application. A client/server system is composed of a set of functional components. When applied to client/server, the concurrent process model defines activities in two dimensions: a system dimension and a component dimension. System level issues are addressed using three activities: design, assembly, and use. The component dimension is addressed with two activities: design and realization. Concurrently is achieved in two ways (1) system and component activities occur simultaneously and can be modeled using the state-oriented approach ; (2) a typical client/server application is implemented with many components, each of which can be designed and realized concurrently. In reality, the concurrent process model is applicable to all types of software development and provides an accurate picture of the current state of project. Rather 3

than confirming s/w engineering activities to a sequence of events, it defines a network of activities. Each activity on the network exists simultaneously with other activities. Events generated within a given activity or at some other place in the activity network trigger transmission among the states of an activity. Client/Server describes the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfills the request. Here client will be the application or front-end, which will generate request, and the server will be relational data base management system, which fulfills the request of a client.

HARDWARE & SOFTWARE SPECIFICATIONS

Data Entry Screens : Developer 2000. Database Operating System Reporting Tools : Oracle 9i. : Windows NT Server. : Developer 2000.

Hardware Specification

Pentium III 1.5 GHz and Above 256 MB SDRAM or More 40 GB HDD

Software Specification

Windows NT Oracle 9i Developer 2000

ANALYSIS OF THE PROJECT

DFDs

PPC Sales Inventory

Planning report Order produduct

Production

Finish goods

Raw material

Fig: Context Diagram

Process_tab Manager_info_tab
Product Detail

Machine Code

Process Type

Manager

Order

1.0 Daily Planning

Job_card Plan detail Job_card_tab

2.0 Listing

Machine Detail

List detail

Job_card Machine_master_tab
3.0 Production

WIP Progess_tab WIP Job_card Product detail

4.0 Material Billing

Acknowledgement

Manager

Product detail BOM_tab

Fig: First Level DFD

Inventory tab Raw item detail

3.1 Quality Checking

MRN

3.2

Acceptation detail

Surplus Material Checking

Manager_info_tab Product detail

3.3 Machine Scheduling

Rejection detail Supplier

Surplus material Shop floor Process Description

Stock detail Job card

3.4 Process Scheduling

Machine Information

Job_card_tab

Process detail Process_inform_tab Process detail

3.5 Production Process

WIP

Progess_tab

Product detail
3.6

LRN

Final Quality

Product

Checking

Accepted Product detail Product_tab Fig: Second level DFD of Production (3.0)

E.R. DIAGRAM
Process_Master

Use_In

Prepares

Job_Card Che ck

Machine_Master

Pos t

Progress Information Master Process Redeployme nt

Devel op

Progress_Part Proces s Mak e Stor e Raw_Material

BOM

Product Send

Inventory

NUMBER OF MODULES AND THEIR DESCRIPTION

1. Calendar:
Calendar gives the plan for the production of whole month. This gives the Chart that in how many days, how much work will be done. Progress of work is also mentioned in this, if delay occurs, calendar is rescheduled to get the output unaffected.

2. Daily Planning:
Daily Planning allow us to plan the production for a particular day. When a daily plan is prepared, Job Card for the plan is generated in production.

3. Listing:
Listing generates the details of all the machines, shifts, production details of selected machines for those specified years, down time reason for a machine. The machine detail includes its name, process assign to it, efficiency, etc. The shift detail includes shift name, machine code, and timing. Machine Scheduling: Machine Schedule is done for the proper utilization of resources of the organization. A business rule for machine scheduling is given below.

Business Rules for Machine Scheduling

1. Suppose we have a product A, & we have to deliver 1000 pieces of A on 15th, May 2004. 2. We run the scheduling & we want to know that from which date we should start production, so that we can deliver it on delivery date. 3. Following Steps have to be taken for calculating the start date. 4. First of all check for available stock of product A. While checking for the stock we have to take only that stock which is not booked for any other product. 5. If we find any stock, which is not booked, then we book it & subtract it from the quantity to be delivered. 6. Then we have balanced quantity of the product A, for which scheduling is required. 7. Find out all Child, Sub Child etc. items of A & their respective quantities in which they required to produce one quantity of Product A. 8. Find the child wise total quantity to produce balance quantity of A. 9. Start a loop 9

Pick 1st child item, check for the available stock of that child item. While checking for the

stock we have to take only that stock which is not booked for any other product. If we find any stock, which is not booked, then we have book it & subtract it from the total quantity of that child item. Find out the processes, time to be required for that process & the work centre in which that Start a loop Pick 1st process of the child item, check for the available WIP (Work In Progress) for that child item on that particular process. Again we have to take only that stock which is not booked, if we find any stock which is not booked, book it & subtract it from the balanced quantity. Find the number of machines available in that work centre. Take alternate machines only if alternate flag is up. Divide the total balanced quantity by number of machines available. We will get the number of items to be worked on one machine. Start a loop Pick 1st machine & find out its set-up time. Multiply number of items to be worked on that machine by time required for that process. Then add set-up time in that time, we will find total time for which that machine is to be booked. This loop will continue, till the last machine & then it will exit from loop. End loop. By this we will find the start date & end date for that particular process. Check whether any holiday comes between the start date and end date, If yes then add one day in the end date of that process. Now check if that process is done 40% of the quantity, If yes then transfer it on the next process. That transfer date will be start date for the next process. This loop will continue, till the last process & then it will exit from loop. End loop. 10. End loop. 11. This loop will continue till last child item & then it will exit from loop. 12. By this you will get maximum date of completion of all child items. process are to done, for that particular child.

10

Now check it whether maximum date is after the delivery date. If yes then alternate flag will be up & whole process will run again. If maximum date is below the delivery Date then it will show you that from which date we should start which process.

4. Production Process
Process Scheduling: Process Scheduling is the processes in which we select and schedule the various processes that will need to form finish goods. Production Process: In Production Process various processes carried out to produce the finished item.

5. Quality Checking:
It is a process in which we get the information about the quality of the raw material that comes from the inventory. If the quality is accepted then it will be passed to the shop floor. If rejected then that will send back to the supplier. Raw Material. Final Product Checking:
After the finished item is made quality of the item is checked. If it is not suitable for the desired quality then it will again send back to the inventory. Details of the quality check include the rejected, reworkable and accepted quantities. After the quality checking, rejected and reworkable material can be returned to the inventory. The accepted quantity can be directly issued from the shop floor/store.

6. Material Billing:
Material Billing specifies the process involve in production cycle of the product along with input, output, by products and overhead. In Material Billing production cost of the production is also calculated. This cost is the cost of the last process and includes the inputs, outputs, and overhead cost involve in all previous processes. It is also possible to do Material Billing for a product from a similar predefined Material Billing of any other product.

7. Surplus Material Checking:

This process checks the quantity of the stock available at the shop floor or the store. If there is excess stock in the store for the necessary product then it will take up all the necessary steps and sent MRN to the inventory.

11

 Line Rejection Note (LRN) : If the input items are rejected or reworkable then we issue the LRN. After inventory receives the LRN from shop floor, rejected material is returned back to the inventory. Business logic followed here is given below. 1. The rejected quantity should not be less than or equal to on-hand-quantity. 2. The reworkable quantity should be less than or equal to rejected quantity. Reworkable quantity can be zero but rejected quantity cannot be zero. Material Return Note (MRN) : When there is excess material in the shop floor then after inventory receives the MRN the excess material is return back to the inventory from the shop floor. The Surplus material Checking checks this condition.

DATA STRUCTURES (TABLES)

1) MST_MACHINE Field-Table VC_COMP_CODE VC_MACHINE_CODE VC_MACHINE_DESC VC_PROCESS_CODE NU_CAPACITY NU_HOURS VC_UOM NU_EFFICIENCY CH_YR_OPERATE_FLAG DT_LAST_MAINTENANC E DT_AMC_DATE NU_MON_MAIN_SHIFTS NU_YR_MAIN_SHIFTS CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Field-Type Description VARCHAR2(2) VARCHAR2(4) VARCHAR2(40) VARCHAR2(4) NUMBER(10,3) NUMBER(2) VARCHAR2(12) NUMBER(3) CHAR(1) DATE DATE NUMBER(2) NUMBER(2) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) 12

VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 2) MST_SHIFT Field-Table VC_COMP_CODE VC_SHIFT_CODE VC_SHIFT_DESC TM_SHIFT_FROM TM_SHIFT_TO NU_HOURS CH_STAT_FLAG H_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COM P VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 Validation NOT NULL NOT NULL NOT NULL

VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

Field-Type VARCHAR2(2) VARCHAR2(4) VARCHAR2(40) DATE DATE NUMBER(5,2) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

Description

3) MST_PROD_CALENDAR Field-Table VC_COMP_CODE VC_MACHINE_CODE DT_CALENDAR VC_SHIFT_CODE H_WORKING_FLAG CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE C_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Field-Type VARCHAR2(2) VARCHAR2(4) DATE VARCHAR2(4) CHAR(1) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) Description

13

VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2

VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

4) HD_JOB_CARD Field-Table VC_COMP_CODE VC_JOB_CARD_NO VC_MPS_NO DT_PRODUCTION VC_SHIFT_CODE VC_MACHINE_CODE VC_PRODUCT_CODE VC_OUTPUT_CODE NU_QTY_PLANNED NU_QTY_PRODUCED VC_OPERATOR_NAME VC_DOWNTIME_CODE H_JOB_CARD_STATUS CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 5) DT_JOB_CARD Field-Table VC_COMP_CODE VC_JOB_CARD_NO VC_MPS_NO VC_ITEM_CODE NU_QTY_REQUIRED NU_QTY_ISSUED NU_QTY_USED Validation NOT NULL NOT NULL NOT NULL NOT NULL Field-Type VARCHAR2(2) VARCHAR2(10) VARCHAR2(8) VARCHAR2(30) NUMBER(10,3) NUMBER(10,3) NUMBER(10,3) Description Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Field-Type VARCHAR2(2) VARCHAR2(10) VARCHAR2(8) DATE VARCHAR2(4) VARCHAR2(4) VARCHAR2(30) VARCHAR2(30) NUMBER(10,3) NUMBER(10,3) VARCHAR2(40) VARCHAR2(4) CHAR(1) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3) Description

14

U_QTY_RETURNED CH_MRN CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE C_DEFAULT_COMP VC_AUTH_CODE DT_PRODUCTION VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 6) HD_EXECUTION Field-Table VC_COMP_CODE VC_EXECUTION_NO VC_MPS_NO DT_PRODUCTION VC_SHIFT_CODE VC_MACHINE_CODE C_OPERATOR_NAME CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2

NOT NULL

NUMBER(10,3) CHAR(1) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) DATE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL

Field-Type VARCHAR2(2) VARCHAR2(8) VARCHAR2(8) DATE VARCHAR2(4) VARCHAR2(4) VARCHAR2(40) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VRCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

Description

7) DT_EXECUTION_ITEM Field-Table VC_COMP_CODE C_EXECUTION_NO VC_ITEM_CODE CH_ITEM_FLAG Validation NOT NULL NOT NULL NOT NULL NOT NULL Field-Type VARCHAR2(2) VARCHAR2(8) VARCHAR2(30) CHAR(1) Description

15

NU_QTY CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE C_DEFAULT_COMP VC_AUTH_CODE DT_PRODUCTION VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1

NOT NULL

NUMBER(10,3) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) DATE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE

8) DT_EXECUTION_PRODUCTION Field-Table VC_COMP_CODE VC_EXECUTION_NO VC_OUTPUT_CODE NU_QTY_PRODUCED NU_QTY_REJECTED U_QTY_REWORKABLE CH_QC_FLAG CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE DT_PRODUCTION VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 9) HD_MACHINE_PROG Field-Table VC_COMP_CODE VC_MPS_NO C_PRODUCTION_REQ_NO DT_PRODUCTION VC_SHIFT_CODE VC_MACHINE_CODE CH_MPS_MODE_FLAG CH_STAT_FLAG Validation NOT NULL NOT NULL NOT NULL Field-Type VARCHAR2(2) VARCHAR2(8) VARCHAR2(30) NUMBER(10,3) NUMBER(10,3) NUMBER(10,3) CHAR(1) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) DATE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3) Description

NOT NULL

NOT NULL

Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL

Field-Type VARCHAR2(2) VARCHAR2(8) VARCHAR2(6) DATE VARCHAR2(4) VARCHAR2(4) CHAR(1) CHAR(2)

Description

16

CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 10) DT_MACHINE_PROG Field-Table VC_COMP_CODE VC_MPS_NO C_PRODUCT_CODE VC_OUTPUT_CODE NU_QTY_PLANNED CH_ITEM_FLAG TM_FROM TM_TO CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE C_DEFAULT_COMP VC_AUTH_CODE DT_PRODUCTION VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 11) MC_WISE_SHIFT Field-Table VC_COMP_CODE C_MACHINE_CODE VC_SHIFT_CODE CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE C_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 Validation NOT NULL NOT NULL NOT NULL Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL

CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

NOT NULL

Field-Type VARCHAR2(2) VARCHAR2(8) VARCHAR2(30) VARCHAR2(30) NUMBER(10,3) CHAR(1) DATE DATE CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) DATE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE

Description

Field-Type VARCHAR2(2) VARCHAR2(4) VARCHAR2(4) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

Description

17

DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 12) PROD_LOT_SUMMARY Field-Table VC_COMP_CODE VC_ITEM_CODE NU_BALANCE_QTY NU_QTY_REJECTED U_QTY_REWORKABLE NU_QTY_DEFECTIVE VC_LOT_NO VC_BIN_NO NU_COST CH_STAT_FLAG CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2 13) PROD_STOCK Field-Table VC_COMP_CODE VC_ITEM_CODE NU_AREA_CODE NU_BALANCE_QTY NU_QTY_REJECTED U_QTY_REWORKABLE NU_QTY_DEFECTIVE NU_QTY_ORDERED NU_QTY_REQUESTED NU_QTY_TO_ORD NU_QTY_AVAILABLE NU_QTY_REQUIRED CH_STAT_FLAG Validation NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Validation NOTNULL NOT NULL

DATE DATE NUMBER(20,3) NUMBER(20,3)

NOT NULL

Field-Type VARCHAR2(2) VARCHAR2(30) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) VARCHAR2(6) VARCHAR2(6) NUMBER(13,2) CHAR(2) CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

Description

Field-Type VARCHAR2(2) VARCHAR2(30) NUMBER(6) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) NUMBER(12,3) CHAR(2)

Description

18

CH_STAT_UP_FLAG DT_MOD_DATE VC_DEFAULT_COMP VC_AUTH_CODE VC_FIELD1 VC_FIELD2 VC_FIELD3 VC_FIELD4 DT_FIELD1 DT_FIELD2 NU_FIELD1 NU_FIELD2

CHAR(2) DATE VARCHAR2(2) VARCHAR2(2) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) DATE DATE NUMBER(20,3) NUMBER(20,3)

PROCESS LOGIC
Problem: Managing of the production process. Requirement: A system, which will take care of the production Management. Company wants to meet the client deadlines and therefore they needs a system which should keep them updating about the latest. System will tell the client that whether with the current speed target can be achieved, if not then what is the alternative path to be followed? The way we have to proceed. First we require qty to be produced. 1. Quantity to be produced 2. Check for the latest delivery date of the product 3. Choose the product for processing which is required at the earliest 4. Check for the processes required for the product 5. Now we have to start the processing from the last process 6. Go to the last process, which to be scheduled 7. See the cycle time of the last process and calculate like

8. Subtract the time from the target date time

19

9. Now complete all the processes required for the part, repeat the steps 6 to 8. Qty to be produced 1. Qty (Qty which is to be produced) 2. Part (The product to be produced) 3. Client (For whom it is to be produced) 4. Delivery Date (Date on which it is to be delivered) Latest delivery date of the part 1. Part 2. Delivery date 3. Client

TYPES OF REPORT GENERATION

1. Calendar_Report. 2. Machine_Management_Report. 3. Job_Card 4. Machine_Master. 5. Shift_Master. 6. Holiday_Master. 7. Break_down Information. 8. Raw_Material Master. 9. Bill_of_Material. 10. Quality_Checking. 11. LRN_Master. 13. MRN_Master.

VALIDATION & CHECKS

Validation refers to the process of using software in a live environment using real data. The process of validation refers to a set of activities that ensure that the software that has been built is matching to customer requirement. Validation is successful when software functions in a manner that can be reasonably expected by the customer.

20

Suitable validation checks have been put wherever need was felt so as to avoid wrong data input. Coding has been done so as to avoid wrong entries in the tables. For example Numeric character are not allowed in the Subscribers name. Various modules have different process logic, which involves sorting of data on different attributes and selection of required attribute depending upon conditions have been decided. Most of these are SQL queries.

Validation: This determines if we are building the right product? (i.e. does the requirement specification describe what the customer wants?) The various kinds of validations performed in our system are as follows: 1) Date Validation: The validation on date data type has been specified to be of the format DD/MM/YY. Any other format is unacceptable. 2) Amount Validation: There is a validation on amount that is entered in rupees in the following format. 00,000,000.00 e.g. 15,65,789.00 3) From Date to Date: The From Date always has to be less than the To Date, e.g. From 1 Nov, 2003 to 4 Nov, 2003 is correct and it cannot be other way round. 4) Number Field Validation: The field specified with Number as then their data-type will not accept Character or any other data type. 5) User Authentication: When a user logs on to the system to access data from the database, the password needs to be checked for user authentication. 6) Password change Validation: Only authorized users are allowed to change the password and the process requires to ask the old password before changing it to the new one. 7) Mailing Labels Validation: Only those subscribers whose subscription is active in our Database will have labels generated for them

FUTURE SCOPE AND ENHANCEMENT OF THE PROJECT

1) Enhancement of our proposed system would be in terms of connectivity with the rest of the departments so that information is made available throughout the organization which leads to efficiency and speeding up of a number of processor. E.g. Finance dept. connected directly with subscriber DB could get information regarding expenditure and gains. 21

2) Centralized Database in the main server could establish connections with each and every zonal head office via satellite communication. This would involve the concept of VSAT installed at each and every station communicating through WAN. 3) Online subscriber register facility could be brought on Web that would automatically send subscriber details into the master Database.

22