SRFD STD PMS

1

Version 1

Client Name: Compucare India Project Manager: Manish Shah

www.compucareindia.com

2

Abstract

This document will be useful for developer and tester to understand client’s requirement.

This project will be developed as per this document.

1. Introduction and Purpose This is the System Functional Requirement Document (SFRD), which contains the functional description of project regarding PMS-Andon System as per discussion with Client (all client). This document will be useful for developer & tester to understand client requirements. The software will be customized as per this document.

2. Definitions, Acronyms and Abbreviations Acronym

Meaning

SFRD

System Functional Requirement Document

CIPL

Compucare India Pvt. Ltd.

Client

All Client

3. Business Processes Objective PMS-Andon Application – Web based Application module to support production monitoring and Andon alerts.

4. Functional Process and Requirement •Process Overview

1. Dashboard

All Machines are grouped into types [Group Line], dashboard need to split based on types [ Injection (23), Welding (14), Balancer (12)] We need to support machine wise statistics as shown in below image. All machine should have below parameters; IMM, Mold No, Part Cord, Part Name, CT, ACT, Plan Qty [ target in order], Act Qty which will have average part Actual cycle time, NG Qty, Next Plan [ Part Name, Date, Time] where IMM, Mold No, Part Cord, Part Name, CT are part parameters; image background color depends on Running, Change Over, Quality Issues, Under Maintenance, and Under Tool Room [ i.e. as many problem created in master]

System Functional Requirement Document

3

2. Company Company master will have flags to indicate reports and dashboard should have Plan and/or Target.

System Functional Requirement Document

4

3. Shift Master Company shift master should have all the shift for the production line, shift time should not be over written i.e. all shift should have distinct timing. Shift breaks option is available so user can ignore those schedule time from production time.

4. Group Line Company does group of certain lines, so user can define all groups which they want and then when creating line user has to link lines with the group by selecting respective group dropdown, group wise filter will happen on dashboard to monitor how entire group lines are doing.

System Functional Requirement Document

5

5. Assets Company will have one or more machines / stations on the line, where user provide information whether production exists and maintenance exists. When production exists then user has to select whether they have production, rejection, machine status inputs.

When maintenance exists then user can provide as many Andon sensor needed.

6. Global settings Company has to provide email and SMS credential. Where email server URL, port, sender email id, password is required for auto email. Make sure your email works properly, we can provide public email id like gmail etc. for testing if email does not work then client IT Team need to resolve issues. For SMS we can provide assistance on how to get SMS pack and create template, however ownership will be with client.

System Functional Requirement Document

6

7. Machine Setup Machine wise production, rejection, machine status sensors will be linked via this screen and assign machine wise shift wise operator.

8. Product setup Product wise setup of data like name, cycle time, critical cycle time, multiplication factor, barcode etc. data and extra parameters values will be supported in product master.

System Functional Requirement Document

7

9. Schedule Order User will create line wise date wise target for the product, it has type which indicates order will be manually managed or at shift end it will close and restart or once target is achieved then it will start next order.

10. Order Setup User can see all scheduled order for the day, once user closed any order it will get closed and removed from the list. User can start next order then currently running order will get closed and it will start product which user started.

11. Breakdown Reason User can provide list of reasons which they want to pick for breakdown cases, i.e., transaction which are greater than critical cycle time.

System Functional Requirement Document

8

12. Breakdown User can see breakdown transactions between 2 dates, user can select from and to date then click generate, this will collect all the data which are having cycle time greater than critical cycle time. User can provide reason and action taken, same will be visible in report.

13. Rejection Reason User can provide list of rejection reasons which they want to pick for rejection cases, i.e., transaction which are rejected will have reason of rejection.

14. Rejection User can select machine, product and order for the day when there is rejection of particular product, user will select reason and quantity. This count will get counted in rejection for selected machine and product, same will be visible in report.

System Functional Requirement Document

9

15. Order Page User can select location and lower block will have calendar view for all the orders for that month, user can select weekly or daily view to verify all the orders on same line.

16. Report Setup There are 4 reports which can be configured to be sent via email to selected list of users, their email id must exist in user account.

System Functional Requirement Document

10

17. Problem Category There is option to classify problems into multiple category, if user is not defining category then it will have sub problem directly into problem.

18. Problem User can define problem names as listed on Andon Device, this problem will have its escalation matrix duration defined, and link them to sub problem and category if needed. User can link resources for escalation matrix via machine setup.

19. Machine Setup User will see all the machine setup for Maintenance, i.e list of Andon problems defined.

User has to set sensors for all problems, all problems will also have acknowledge sensors.

User can also define shift wise escalation members i.e. minor escalation, critical escalation.

System Functional Requirement Document

11

17. Problem Category There is option to classify problems into multiple category, if user is not defining category then it will have sub problem directly into problem.

18. Problem User can define problem names as listed on Andon Device, this problem will have its escalation matrix duration defined, and link them to sub problem and category if needed. User can link resources for escalation matrix via machine setup.

19. Machine Setup User will see all the machine setup for Maintenance, i.e list of Andon problems defined.

User has to set sensors for all problems, all problems will also have acknowledge sensors.

User can also define shift wise escalation members i.e. minor escalation, critical escalation.

System Functional Requirement Document

12

20. Andon List User can see all the alerts raised on Andon station, Machine wise problem wise list.

21. TV Views

View-1

View-2

System Functional Requirement Document

13

22. Reports •Common Reports.

1. Shift Overall Summary – user can see shift wise order wise production, efficiency, rejection reason wise count, and downtime based on Andon alert.

2. DownTime – user can see date wise order wise downtime based on andon problems defined

•PMS Reports.

1. Production Summary

2. Date wise Production

System Functional Requirement Document

14

3. Shift wise Production

4. Location wise Production

System Functional Requirement Document

15

5. Hour wise production

6. Production overall summary

System Functional Requirement Document

16

7. Rejection summary

8. Breakdown summary - Breakdown Report for Machine wise, Product wise between two dates

9. Machine Status

System Functional Requirement Document

17

10. Operator wise shift wise production

11. OEE Report

System Functional Requirement Document

18

• Andon Reports 1. Andon Summary

2. Hourly Summary

System Functional Requirement Document

19

3. Line wise Report

5. Pre-Requisites • Windows 11 • IIS • .Net framework 4.7.2

Note: If any additional modification/customization/changes required which is not mentioned in this document will be charged extra.

Note: - Please study this document and email your query regarding the same and if all the points are covered as per your requirement, then send the confirmation mail, based on the mail we will start the development.

Authorized Person

Authorized Person

Mr. Sachin Goswami

CIPL

Mr. Manish Shah

CIPL

System Functional Requirement Document

Date

Sign

Email: inquiry@compucareindia.com Mobile: +91-9558812824 | +91-9898090830

OUR BUSINESS ADDRESS 203-210, Bombay Shopping Centre, Opp. GEB, Race Course, Vadodara – Gujarat – INDIA.