Spaces:
Sleeping
Sleeping
budhadityac24
commited on
Commit
•
048e38b
1
Parent(s):
4474bd3
Upload 6 files
Browse files- Biz_Obj.json +68 -0
- Customer_dependency.json +68 -0
- Material_handling.json +110 -0
- Prod_var_info.json +86 -0
- acceptance.json +62 -0
- software.json +62 -0
Biz_Obj.json
ADDED
@@ -0,0 +1,68 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "BIZ_OBJ",
|
4 |
+
"Field Name": "Problem Statement",
|
5 |
+
"Description": "A brief Problem Statement of the requirement",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "BIZ_OBJ",
|
10 |
+
"Field Name": "Current Inspection Methods",
|
11 |
+
"Description": "Description of the client's current methods for inspection.",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "BIZ_OBJ",
|
16 |
+
"Field Name": "Challenges with Current System",
|
17 |
+
"Description": "Specific issues or challenges faced with the current inspection methods.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "BIZ_OBJ",
|
22 |
+
"Field Name": "Desired Improvements",
|
23 |
+
"Description": "Improvements the client wishes to achieve with the new system.",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "BIZ_OBJ",
|
28 |
+
"Field Name": "Budget Constraints",
|
29 |
+
"Description": "The client's budget for the system to tailor a cost-effective solution.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "BIZ_OBJ",
|
34 |
+
"Field Name": "Key Performance Indicators (KPIs)",
|
35 |
+
"Description": "Metrics to measure the success of the vision system.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "BIZ_OBJ",
|
40 |
+
"Field Name": "Return on Investment (ROI) Criteria",
|
41 |
+
"Description": "Client's criteria for ROI on the vision system.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "BIZ_OBJ",
|
46 |
+
"Field Name": "Future Scalability Needs",
|
47 |
+
"Description": "Anticipated future requirements or expansions.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "BIZ_OBJ",
|
52 |
+
"Field Name": "Integration with Existing Systems",
|
53 |
+
"Description": "How the vision system needs to integrate with current business systems.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "BIZ_OBJ",
|
58 |
+
"Field Name": "Compliance Requirements",
|
59 |
+
"Description": "Any regulatory or industry compliance requirements.",
|
60 |
+
"User Answer": ""
|
61 |
+
},
|
62 |
+
{
|
63 |
+
"Category": "BIZ_OBJ",
|
64 |
+
"Field Name": "Environmental Impact Considerations",
|
65 |
+
"Description": "Any environmental goals or standards to adhere to.",
|
66 |
+
"User Answer": ""
|
67 |
+
}
|
68 |
+
]
|
Customer_dependency.json
ADDED
@@ -0,0 +1,68 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
4 |
+
"Field Name": "Space Requirements",
|
5 |
+
"Description": "Information on the physical space needed for the system.",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
10 |
+
"Field Name": "Internet Connectivity",
|
11 |
+
"Description": "What kind of internet connectivity can be provided for remote training and testing and later for troubleshooting",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
16 |
+
"Field Name": "Power",
|
17 |
+
"Description": "Details about power supply and network connectivity requirements.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
22 |
+
"Field Name": "Test and Train Samples",
|
23 |
+
"Description": "Whether the customer can provide sufficient sample products for training the system as well as for testing and system calibration.",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
28 |
+
"Field Name": "On-site Support",
|
29 |
+
"Description": "Information about the level of on-site support and training required for the client.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
34 |
+
"Field Name": "Environmental Conditions",
|
35 |
+
"Description": "Specific environmental factors where the system will be deployed, such as temperature, humidity, lighting, and contaminants.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
40 |
+
"Field Name": "User Profiles and Skill Levels",
|
41 |
+
"Description": "Technical expertise and training requirements of the end-users of the system.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
46 |
+
"Field Name": "Regulatory and Compliance Requirements",
|
47 |
+
"Description": "Industry-specific regulations or standards the system must comply with.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
52 |
+
"Field Name": "Maintenance and Support Requirements",
|
53 |
+
"Description": "Maintenance needs, expected system lifespan, and support requirements.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
58 |
+
"Field Name": "Performance Metrics and Success Criteria",
|
59 |
+
"Description": "Specific performance metrics expected from the system and how success is defined.",
|
60 |
+
"User Answer": ""
|
61 |
+
},
|
62 |
+
{
|
63 |
+
"Category": "CUSTOMER_DEPENDENCY",
|
64 |
+
"Field Name": "Risk Assessment",
|
65 |
+
"Description": "Potential risks or challenges in implementing the system for proactive planning.",
|
66 |
+
"User Answer": ""
|
67 |
+
}
|
68 |
+
]
|
Material_handling.json
ADDED
@@ -0,0 +1,110 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "MATERIAL_HANDLING",
|
4 |
+
"Field Name": "Material Handling Method",
|
5 |
+
"Description": "How products are transported to the inspection area.",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "MATERIAL_HANDLING",
|
10 |
+
"Field Name": "Loading",
|
11 |
+
"Description": "Description of how parts are loaded into the inspection system.",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "MATERIAL_HANDLING",
|
16 |
+
"Field Name": "Handling Speed",
|
17 |
+
"Description": "Speed at which products are handled or moved.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "MATERIAL_HANDLING",
|
22 |
+
"Field Name": "Part Movement During Inspection",
|
23 |
+
"Description": "Specifies whether the part is moving or stationary during the inspection process.",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "MATERIAL_HANDLING",
|
28 |
+
"Field Name": "FAIL/Rejection Action (NG components)",
|
29 |
+
"Description": "How rejected (Not Good) components are managed and what action should be taken.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "MATERIAL_HANDLING",
|
34 |
+
"Field Name": "PASS Action",
|
35 |
+
"Description": "What happens when a part is passed by the vision system.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "MATERIAL_HANDLING",
|
40 |
+
"Field Name": "Variant Change Over",
|
41 |
+
"Description": "How the system manages changes between different product variants.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "MATERIAL_HANDLING",
|
46 |
+
"Field Name": "Mechanical Drawings",
|
47 |
+
"Description": "Option to upload or describe mechanical drawings related to material handling.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "MATERIAL_HANDLING",
|
52 |
+
"Field Name": "Images/Video of the Existing Line",
|
53 |
+
"Description": "Visual reference of the current material handling setup.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "MATERIAL_HANDLING",
|
58 |
+
"Field Name": "Variants",
|
59 |
+
"Description": "List all different variants in the scope of this inspection and mention any out-of-scope variants.",
|
60 |
+
"User Answer": ""
|
61 |
+
},
|
62 |
+
{
|
63 |
+
"Category": "MATERIAL_HANDLING",
|
64 |
+
"Field Name": "Cycle Time",
|
65 |
+
"Description": "Describe cycle time and inspection speed.",
|
66 |
+
"User Answer": ""
|
67 |
+
},
|
68 |
+
{
|
69 |
+
"Category": "MATERIAL_HANDLING",
|
70 |
+
"Field Name": "Inputs to Vision System",
|
71 |
+
"Description": "Inputs from external systems interfaced with the vision system.",
|
72 |
+
"User Answer": ""
|
73 |
+
},
|
74 |
+
{
|
75 |
+
"Category": "MATERIAL_HANDLING",
|
76 |
+
"Field Name": "Outputs from Vision System",
|
77 |
+
"Description": "Outputs like PNP, TTL, EthernetIP, and interfacing details.",
|
78 |
+
"User Answer": ""
|
79 |
+
},
|
80 |
+
{
|
81 |
+
"Category": "MATERIAL_HANDLING",
|
82 |
+
"Field Name": "LOCATE FAILED/UNKNOWN/ERROR Action",
|
83 |
+
"Description": "What happens in scenarios of failed, unknown, or error detections.",
|
84 |
+
"User Answer": ""
|
85 |
+
},
|
86 |
+
{
|
87 |
+
"Category": "MATERIAL_HANDLING",
|
88 |
+
"Field Name": "Other Requirements",
|
89 |
+
"Description": "Open text for any other material handling requirements.",
|
90 |
+
"User Answer": ""
|
91 |
+
},
|
92 |
+
{
|
93 |
+
"Category": "MATERIAL_HANDLING",
|
94 |
+
"Field Name": "Special Handling Requirements",
|
95 |
+
"Description": "Specific conditions required for handling, like temperature control or fragility considerations.",
|
96 |
+
"User Answer": ""
|
97 |
+
},
|
98 |
+
{
|
99 |
+
"Category": "MATERIAL_HANDLING",
|
100 |
+
"Field Name": "Specifications/Standards Compliance",
|
101 |
+
"Description": "List of specific standards or specifications the system must comply with.",
|
102 |
+
"User Answer": ""
|
103 |
+
},
|
104 |
+
{
|
105 |
+
"Category": "MATERIAL_HANDLING",
|
106 |
+
"Field Name": "Material Standards",
|
107 |
+
"Description": "Specifies the material standards required for the components.",
|
108 |
+
"User Answer": ""
|
109 |
+
}
|
110 |
+
]
|
Prod_var_info.json
ADDED
@@ -0,0 +1,86 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "PROD_VARIANT_INFO",
|
4 |
+
"Field Name": "Product Name/ID",
|
5 |
+
"Description": "Unique Name or identifier for the product that needs to be inspected.",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "PROD_VARIANT_INFO",
|
10 |
+
"Field Name": "Product Description",
|
11 |
+
"Description": "Brief overview of the product, its use, and key features.",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "PROD_VARIANT_INFO",
|
16 |
+
"Field Name": "Product Image Upload",
|
17 |
+
"Description": "Option for users to upload images of the product for visual reference.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "PROD_VARIANT_INFO",
|
22 |
+
"Field Name": "Inspection Purpose",
|
23 |
+
"Description": "Brief description of why the product needs inspection (e.g., quality control, compliance, etc.).",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "PROD_VARIANT_INFO",
|
28 |
+
"Field Name": "Dimensions",
|
29 |
+
"Description": "Min and Max Dimensions of the product.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "PROD_VARIANT_INFO",
|
34 |
+
"Field Name": "Usage Context",
|
35 |
+
"Description": "Description of where and how the product is used.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "PROD_VARIANT_INFO",
|
40 |
+
"Field Name": "Criticality",
|
41 |
+
"Description": "Importance and Role of the inspection process in its usage context.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "PROD_VARIANT_INFO",
|
46 |
+
"Field Name": "Variant Names/IDs",
|
47 |
+
"Description": "Unique identifiers for each variant.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "PROD_VARIANT_INFO",
|
52 |
+
"Field Name": "Variant Descriptions",
|
53 |
+
"Description": "Descriptions highlighting differences between variants.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "PROD_VARIANT_INFO",
|
58 |
+
"Field Name": "Size Range",
|
59 |
+
"Description": "Minimum and maximum dimensions for all variants.",
|
60 |
+
"User Answer": ""
|
61 |
+
},
|
62 |
+
{
|
63 |
+
"Category": "PROD_VARIANT_INFO",
|
64 |
+
"Field Name": "Variant-Specific Features",
|
65 |
+
"Description": "Notable features unique to certain variants.",
|
66 |
+
"User Answer": ""
|
67 |
+
},
|
68 |
+
{
|
69 |
+
"Category": "PROD_VARIANT_INFO",
|
70 |
+
"Field Name": "Variant Images",
|
71 |
+
"Description": "Option to upload images for",
|
72 |
+
"User Answer": ""
|
73 |
+
},
|
74 |
+
{
|
75 |
+
"Category": "PROD_VARIANT_INFO",
|
76 |
+
"Field Name": "Production Volume",
|
77 |
+
"Description": "Annual/Monthly Production Voume (total as well as Variant wise breakup)",
|
78 |
+
"User Answer": ""
|
79 |
+
},
|
80 |
+
{
|
81 |
+
"Category": "PROD_VARIANT_INFO",
|
82 |
+
"Field Name": "Product 3D Model",
|
83 |
+
"Description": "Option to upload a 3D model of the product.",
|
84 |
+
"User Answer": ""
|
85 |
+
}
|
86 |
+
]
|
acceptance.json
ADDED
@@ -0,0 +1,62 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "ACCEPTANCE",
|
4 |
+
"Field Name": "Acceptance Test Criteria",
|
5 |
+
"Description": "Specific criteria that the vision system must meet for acceptance.",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "ACCEPTANCE",
|
10 |
+
"Field Name": "Trial Period",
|
11 |
+
"Description": "The duration of the testing phase before final acceptance.",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "ACCEPTANCE",
|
16 |
+
"Field Name": "Sample Size for Testing",
|
17 |
+
"Description": "Number of samples to be tested during the acceptance phase.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "ACCEPTANCE",
|
22 |
+
"Field Name": "Failure Thresholds",
|
23 |
+
"Description": "Defined limits for what constitutes a failure during testing.",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "ACCEPTANCE",
|
28 |
+
"Field Name": "Reporting Requirements",
|
29 |
+
"Description": "Details on reporting format and frequency during the trial period.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "ACCEPTANCE",
|
34 |
+
"Field Name": "On-Site Evaluation",
|
35 |
+
"Description": "Requirement for on-site testing as part of the acceptance process.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "ACCEPTANCE",
|
40 |
+
"Field Name": "Post-Implementation Review",
|
41 |
+
"Description": "Schedule and criteria for reviewing the system's performance post-implementation.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "ACCEPTANCE",
|
46 |
+
"Field Name": "User Training Completion",
|
47 |
+
"Description": "Confirmation that user training has been successfully completed.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "ACCEPTANCE",
|
52 |
+
"Field Name": "System Integration Test",
|
53 |
+
"Description": "Testing the system's integration with existing processes and equipment.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "ACCEPTANCE",
|
58 |
+
"Field Name": "Final Acceptance Sign-off",
|
59 |
+
"Description": "Process for formally accepting the system, including any necessary documentation or approvals.",
|
60 |
+
"User Answer": ""
|
61 |
+
}
|
62 |
+
]
|
software.json
ADDED
@@ -0,0 +1,62 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
[
|
2 |
+
{
|
3 |
+
"Category": "SOFTWARE",
|
4 |
+
"Field Name": "Operator Permitted Actions",
|
5 |
+
"Description": "List of actions the operator is allowed to perform.",
|
6 |
+
"User Answer": ""
|
7 |
+
},
|
8 |
+
{
|
9 |
+
"Category": "SOFTWARE",
|
10 |
+
"Field Name": "Operator Restricted Actions",
|
11 |
+
"Description": "Actions the operator is not allowed to perform.",
|
12 |
+
"User Answer": ""
|
13 |
+
},
|
14 |
+
{
|
15 |
+
"Category": "SOFTWARE",
|
16 |
+
"Field Name": "Variant Selection Mechanism",
|
17 |
+
"Description": "How variant information is communicated to the vision system.",
|
18 |
+
"User Answer": ""
|
19 |
+
},
|
20 |
+
{
|
21 |
+
"Category": "SOFTWARE",
|
22 |
+
"Field Name": "Feedback Mechanisms",
|
23 |
+
"Description": "Any operator alerts or notifications.",
|
24 |
+
"User Answer": ""
|
25 |
+
},
|
26 |
+
{
|
27 |
+
"Category": "SOFTWARE",
|
28 |
+
"Field Name": "Language Preferences",
|
29 |
+
"Description": "Preferred languages for the interface.",
|
30 |
+
"User Answer": ""
|
31 |
+
},
|
32 |
+
{
|
33 |
+
"Category": "SOFTWARE",
|
34 |
+
"Field Name": "Database Integration",
|
35 |
+
"Description": "Details on the integration with external databases for data management.",
|
36 |
+
"User Answer": ""
|
37 |
+
},
|
38 |
+
{
|
39 |
+
"Category": "SOFTWARE",
|
40 |
+
"Field Name": "ERP Integration",
|
41 |
+
"Description": "Information on integration with Enterprise Resource Planning systems.",
|
42 |
+
"User Answer": ""
|
43 |
+
},
|
44 |
+
{
|
45 |
+
"Category": "SOFTWARE",
|
46 |
+
"Field Name": "Image Backup Requirements",
|
47 |
+
"Description": "Parameters for image data backup.",
|
48 |
+
"User Answer": ""
|
49 |
+
},
|
50 |
+
{
|
51 |
+
"Category": "SOFTWARE",
|
52 |
+
"Field Name": "Backup Storage",
|
53 |
+
"Description": "Preferred backup storage solution.",
|
54 |
+
"User Answer": ""
|
55 |
+
},
|
56 |
+
{
|
57 |
+
"Category": "SOFTWARE",
|
58 |
+
"Field Name": "Production Line Feedback",
|
59 |
+
"Description": "Result feedback to be communicated to the production line .",
|
60 |
+
"User Answer": ""
|
61 |
+
}
|
62 |
+
]
|