Component testing

Abstract

A system 100 for physical testing of one or more components 104 in a test apparatus 102. The test apparatus comprises one or more devices 108 for applying one or more tests to the component during the

Description

Field The present disclosure relates to a system for physical testing of one or more physical components. Background Testing of components is a common, and often essential, part of component design and manufacturing. For example, it must be ensured that any component or product that is to be sold or otherwise used is fit for purpose and safe for the end consumer. Testing is typically carried out by one or more approved testing bodies. Once testing has been completed, test results are sent to a certification agency or an approved notified body, so that the component or product can be certified. For example, International Fire Consultant Certification (IFCC) provides fire safety certification. UL International is an example of an accredited certification body. The United Kingdom Accreditation Service, or UKAS (https: / / www.ukas.com / ) offers accreditation to certification. Component or product testing can be slow, laborious and inefficient. First, once a component or product is ready for testing, it can take a long time (up to 6 months is not unusual) for test equipment at a testing house to become available. Moreover, the testing process can be opaque to the manufacturer whose component or product is being tested. They must travel to the test house to witness the start of the test just to ensure the test has started on time, then throughout the testing process (usually around 3 months), the manufacturer isn’t offered any access to the test unless they request another visit to the site. When tests are completed or failed, the manufacturer often must chase vigorously for an update. Moreover, when a test fails, the full test process needs to restart. This can cause long delays, especially since a previously failed product or component is usually sent to the back of the testing queue for the re-test. This problem can be compounded by a lack of available technical data as to how, why and when the product failed, meaning it can be difficult to isolate the product feature that needs to be improved for the re-test. The process from booking a test, up to the receipt of the report can be anything between 12 to 24 months. This timescale can be problematic for product development, and may introduce an unacceptable delay in bringing a product to market. The timescale can be particularly problematic if the component or product fails or only narrowly passes the test, as it significantly delays the time taken to make necessary or desired improvements to the component or product. Moreover, current test reports can lack detailed test data, making it difficult for a manufacturer to understand the performance of the product under test in detail. The present inventors have attempted to address or at least mitigate the above-mentioned problems. With this in-mind, the present inventors have aimed to provide a system for physical testing of one or more physical components, which can vastly speed up the overall testing process. The provided system also aims to provide an end-user with detailed technical test data that can help the end-user understand performance of a product under test. The provided system also aims to lead to the manufacture of improved components and products. Summary Accordingly, there is provided a system for physical testing of one or more physical products, according to claim 1. Some further features of the invention are provided, according to the dependent claims. Brief description of drawings Figure 1 schematically shows a system for physical testing of one or more physical products, according to an example embodiment of the invention. Figure 2 schematically shows an output display of test data, according to an example embodiment of the invention; Figure 3 schematically shows a display screen, according to an example embodiment of the invention; Figures 4A and 4B schematically show displayed test results, according to an example embodiment of the invention; Figure 5 schematically shows an output graph of test data, according to an example embodiment of the invention. Detailed description Figure 1 schematically shows a system 100. The system 100 is for physical testing of one or more physical components. In other words, the system 100 is for testing of real-life components in the physical world. It will also be understood that the system 100 is suitable for testing of one or more physical products, where such products may comprise a plurality of components. For conciseness, and unless stated otherwise, the term component or components may be used interchangeably with the terms product or products. The system comprises a test apparatus, shown schematically at 102. The test apparatus 102 is configured for receiving a component 104 to be subject to a physical testing procedure. The test apparatus 102 may include a mounting or test bed 106 for receiving the component 104 to be tested. The test apparatus 102 comprises one or more devices, shown schematically at 108, for applying one or more respective physical tests to the component 104 during the physical testing procedure. By way of non-limiting example, the one or more devices 108 may comprise one or more or any combination of: one or more actuators; one or more clamps; one or more impact tools; one or more liquid or fluid outlets or baths; one or more heaters; one or more fire or flame sources, etc. The test apparatus 102 also comprises one or more sensors, shown schematically at 110. The one or more sensors 110 are configured for obtaining test data relating to the component 104 and / or the one or more devices 108 and / or environmental conditions of the test apparatus 102, during the physical testing procedure. The test data may be considered technical test data. Test data relating to the component may comprise, by way of non-limiting example, performance data such as sensed speed or velocity of movement data, sensed positional data, sensed force data, sensed stress data such as a bending stress, sensed strain data such as a bending strain, etc. Test data relating to the one or more devices 108 may comprise, by way of non-limiting example, data of applied force (e.g. by an actuator), data of applied speed (e.g. by an actuator), data of applied heat (e.g. by a heater), data of applied corrosive substances (e.g. by a fluid outlet), etc. Environmental conditions may include, by way of non-limiting example, any one or more of: temperature; moisture; humidity; light level; time of day, etc. By way of non-limiting example, the one or more sensors 110 may comprise one or more or any combination of: one or more optical sensors; one or more cameras for obtaining still or motion images; one or more light sensors; one or more force sensors; one or more torque sensors; one or more temperature sensors; one or more corrosion sensors; one or more moisture sensors; one or more humidity sensors; one or more clocks or timers, for example an atomic clock; etc. In some examples the physical testing of the component 104 may comprise mechanical testing. Mechanical testing may comprise any one or more or any combination of: a durability test; a tensile strength test; a compression strength test; a hardness test; an impact test; a repeated cycle test. In some examples the physical testing of the component 104 may comprise tribology testing. For example, tribology testing may comprise a friction or wear test. In some examples the physical testing of the component 104 may comprise corrosion testing. For example, corrosion testing may comprise a corrosion resistance test. In some examples the physical testing of the component 104 may comprise fire testing. For example, the fire testing may comprise a fire retardance test. The system 100 comprises a computer-implemented test report generator 112. The test report generator is in communication with the test apparatus 102. Accordingly, the test report generator 112 is configured to receive information or data from the test apparatus 102. For example, the test report generator may receive information from or pertaining to the one or more sensors 110 and / or the one or more devices 108. The test report generator 112 is configured to generate and continuously or continually populate a test report with test data for the component 104, as the component 104 is being subject to the physical testing procedure. The system 100 comprises a communication interface 116. The communication interface 116 is configured to enable an authorised user 118 to perform remote monitoring of the physical testing procedure. For example, the communication interface 116 is configured to enable the remote user 118 to request and obtain from the test report generator 112, (i) a completed test report 120 comprising completed test data once the physical testing of the component has been completed. The completed test report 120 may provide an indication of whether the component has passed or failed the physical testing procedure. The completed test report may also include a clear statement of whether the component 104 has passed or failed the physical testing procedure (e.g. PASS / FAIL). The communication interface 116 is also configured to enable the remote user 118 to additionally or alternatively request and obtain from the test report generator 112, (ii) a partial test report 122 comprising partial test data for a period of the test up to when the partial test report was requested. For example, if a physical testing procedure was initiated or started at time To, and the partial test report was requested at time Ti, then the partial test report will comprise test data for a time period between To and Ti. In some examples, obtaining a partial and / or completed test report from the test report generator 112 comprises downloading the partial and / or completed test report. As well as the completed and / or partial test reports, in some examples the remote monitoring may also enable the remote user 118 to obtain processed and / or raw data from the test apparatus 102, such as processed and / or raw data from the one or more sensors 110. In some examples, the processed data is based on the raw data but has been processed in some manner to enable the data to be more easily understood by the remote user 118. For example, raw sensor data may be processed into easier to understand data such as colour coding or simple classification categories such as poor, satisfactory, good. In some examples, the communication interface 116 may be configured to communicate with a computing device 126 of the remote user 118. The remote computing device 126 may comprise a PC, a tablet, a smart phone etc. In some examples, a “dashboard” 128 is provided on the computing device 126 for the remote monitoring and / or viewing of the partial or completed test reports. In some examples, the communication interface 116 is configured to receive one or more authorisation credentials, such as a password, from the remote user 118. Then, the remote user 118 can be authorised or verified before any test data is supplied to the remote user. In some examples, the system 100 comprises at least one camera 124. The camera 124 is configured to obtain video or photographic data of the physical testing procedure. The remote monitoring by the remote user 118 may be considered to comprise remotely viewing the video or photographic data of the physical testing procedure. In some examples the at least one camera 124 comprises a closed-circuit television (CCTV) camera. In some examples the at least one camera 124 comprises multiple cameras, enabling the remote user 118 to view the test apparatus 102 and / or the component 104 from multiple angles or positions. As discussed above, in some examples the at least one sensor 110 comprises a camera. In such instances that at least one sensor 110 may be considered a first camera, and the at least one camera 124 may be considered a second camera. For example, where the at least one sensor 110 comprises a first camera, the first camera may be able to take highly detailed photographs of the component 104 (such as a micrograph), and the at least one camera 124 or second camera may take less detailed (but still high quality) images enabling the remote user 118 to more generally monitor the test remotely. For example, the purpose of the at least one camera 124 may be to enable the remote user to get high level information of the testing procedure, such as whether the test procedure has started, stopped, or is in progress. In some examples, when the component 104 has failed the physical testing procedure, the test report generator 112 is configured to provide a timestamp of when the failure has occurred. The timestamp may be included in the full or partial test report, or in a dedicated failure notification sent to the remote user 118. In some examples, the remote user 118 can use the timestamp information to determine where in footage obtained from at least one camera 124 to view the point of failure. In some examples, sensor data collected from at least one sensor 110 is provided with corresponding time information. The remote user may also use the timestamp information of the failure to quickly ascertain which sensor data from at least one sensor 110 to view, to obtain data relevant to the failure. According to some examples, the communication interface 116 is configured to make the test data obtained from the one or more sensors 110 available in real time to the remote user, for the remote monitoring. The test data that is sent to the remote user 118 may be processed data. For example, processed data may comprise test data that has been processed in a way to make it more easily readable for the remote user 118. For example, colour coding may be used to indicate whether a component 104 is operating within acceptable parameters or outside of acceptable parameters. For example, a green indicator could indicate that a component 104 is operating within acceptable parameters, and a red indicator could indicate that a component 104 is operating outside of acceptable parameters. Additionally or alternatively, the remote user 118 may be provided with raw data from at least one sensor 110 in real-time. In some examples, the real time test data is displayed on dashboard 128 of computing device 126. In some examples the test report generator 112 is configured to indicate that the component has passed the physical testing procedure when the physical testing procedure has reached a threshold duration without failure. For example, the test report generator 112 is configured to indicate that the component 104 has passed the physical testing procedure when the physical testing procedure has been ongoing for a defined or pre-determined period of time. The defined or predetermined period of time may be in seconds, minutes, hours, days, weeks, months etc. The defined or pre-determined period of time may be varied dependent on the component that is being tested. In some examples the test report generator 112 is configured to indicate that the component 104 has passed the physical testing procedure when a threshold number of test cycles has been reached without failure of the component 104. The threshold number may be varied dependent on the component that is being tested. The test report generator 112 is configured to extrapolate test data of a partially completed physical testing procedure to determine a likelihood of the component 104 subsequently failing the physical testing procedure. For example, say a component is to be tested over 500,000 cycles, and is expected to remain within certain operational parameters over that number of cycles. Now, say that after 1,000 cycles the component has degraded or performance has degraded to a point that the test report generator extrapolates or predicts that the component is unlikely to last for 500, 000 cycles. Then, the test report generator can predict or extrapolate a high likelihood of the component failing the testing procedure. In response to determining a likely failure of the physical testing procedure by the component 104, the test report generator 112 is configured to send a notification to the remote user 118 indicating the likely failure. This gives the remote user 118 an instantaneous or near-instantaneous update of the likely failure, and allows the remote user 118 to begin taking remedial action without unnecessary delay. For example, remedial action may comprise requesting that the test procedure be stopped. Additionally or alternatively, the remedial action may comprise beginning a re-design of the failed component. This contrasts with current testing regimes where it may take months for a customer to learn that a component has failed its test. Alternatively, in some examples the test report generator doesn’t predict the likelihood of a subsequent pass or fail. In such examples, the test report generator provides test data, and it is up to the manufacturer or customer to make a prediction of likelihood of failure themselves based on their expertise. According to some examples, the test report generator 112 is configured to include a reason for the likely failure with the notification. For example, a reason may be “parameter x close to boundary of acceptable operational parameters after y cycles”. For example, in a tensile test a component may be stretched close to an acceptable limit after relatively few cycles. In some examples the component 104 may comprise a door closer component 130, and the one or more devices 108 for applying one or more respective physical tests to the component comprises an actuator 132 for causing an opening and / or closing force to be repeatedly applied to the door closer component 130. For example, the door closer component 130 may be a component that is configured to provide assistive opening and / or closing forces to a door. According to some examples the door closer component 130 comprises a powered door closer component. For example, the door closer component 130 may comprise an electric motor or an electromagnet. Additionally or alternatively the door closer component 130 may be a mechanical door closer component, comprising one or more biasing means such as a spring. For example, the actuator 132 may be configured to mimic an action of a person manually opening or closing a door. In some examples the physical test procedure comprises a predetermined number of opening and closing cycles of the door closer component 130, as part of a durability test of the door closer component. For example, the predetermined number of opening and closing cycles comprises 500,000 or approximately 500,000 cycles. It will be appreciated that there may be one or more other tests and pass / fail criteria that the component needs to meet in addition to the durability test, so that the component can be classified as a pass or fail overall. In some examples, the one or more sensors 110 is configured to sense, over a predetermined distance or angle of movement of the door closer component, one or more of: an opening speed of the door closer component 130; a closing speed of the door closer component 130. For example, a required standard may be that a door closer component 104 must be able to effect the last 10° of closure within a certain timeframe (e.g. 10 seconds). According to some examples, the one or more sensors 110 is configured to sense, over a predetermined distance or angle of movement of the door closer component 130, one or more of: a force required to open the door closer component 130; a force required to close the door closer component 130. In some examples, the one or more sensors 110 is configured to sense the opening speed of the door closer component as part of a back check test. A back check valve in a door component controls the opening speed of a door as it reaches its near fully open position, for example the final 15° of opening. This prevents a door from being slammed open, for example in heavy winds. For example, a back check test may comprise the door closer component having to complete 100,000 cycles with the back check setting on, followed by removal of the back check and test being set to 500,000 cycles. Of course, the door closer component may be subjected to further tests, and the tests described above are provided as illustrative examples. For example, a door closer component may be subjected to any one or more tests that are required to meet the criteria set out in the BS EN1154 standard, “Building hardware - Controlled door closing devices - Requirements and test methods”. According to some examples the system 100 comprises a user interface 134 that is in communication with the test apparatus 102. The user interface 134 may comprise a display 136 and a user input device 138. For example, the user input device 138 may comprise a touchscreen and / or one or more physical knobs or buttons. In some examples, the user interface 134 is configured to enable a user (such as a test laboratory worker) to input one or more commands to the test apparatus 102. For example, the one or more commands may comprise one or more of: a start command for starting the testing procedure; a stop command for stopping the testing procedure; a pause command for pausing the testing procedure. The user interface 134 may also be referred to as a human machine interface (HMI). In some examples, via the user interface 134 a user can input instructions or test parameters to the test apparatus 102. For example, via the user interface 134 a user may operate the one or more devices 108 and / or the one or more sensors 110. Additionally or alternatively, via the user interface 134 a user can adjust one or more operational parameters of the one or more devices 108 and / or the one or more sensors 110. According to some examples the user interface 134 is configured to enable a unique identifier to be input and associated with the testing procedure for the component 104. This unique identifier can be used to associate a component under test with an authorised remote user. For example, once the unique identifier is assigned to a component 104, then the unique identifier is provided to the remote user 118. When the remote user 118 wants to view a specific component under test, then the remote user 118 can provide the unique identifier (as well as authentication credentials), for example via communication interface 116. In some examples the unique identifier may be in the form of a job number. Via the user interface 134 an operative may also add one or more job requirements pertaining to a test. According to some examples, the test report generator 112 is configured to produce test reports in conformance with one or more requirements of a certification or industrial standards agency. For example, the certification or industrial standards agency may be ASTM International, or the United Kingdom Accreditation Service (UKAS). In some examples the system 100 is configured to send a completed test report to a certification or industrial standards agency once a test has completed, for example via the communication interface 116 of the system 100. According to some examples the system 100 comprises multiple test apparatus 102. For example, the system 100 may be comprised in a test laboratory with multiple components being tested on multiple respective test apparatus 102. In some examples, the system comprises ten to twenty test apparatus 102. In some examples, the system 100 comprises sixteen test apparatus 102. In some examples where there are multiple test apparatus 102, each test apparatus 102 has a dedicated user interface 134. In some examples where there are multiple test apparatus 102, each test apparatus 102 has a dedicated test report generator 112. In some examples where there are multiple test apparatus 102, the multiple test apparatus 102 has a dedicated communication interface 116. Alternatively, where there are multiple test apparatus 102, two or more of the test apparatus 102 may share a user interface 134 and / or test report generator 112 and / or communication interface 116. According to some examples the system 100 comprises a computer-implemented Client Relationship Management (CRM) system or tool. The CRM tool is schematically shown at 140. In some examples the remote user 118 (and one or more other clients or customers of the system) may communicate with the system 100 via the CRM 140. Additionally or alternatively, the proprietor of the system 100 may communicate with the system 100 via CRM 140. In some examples testing equipment, such as test apparatus 102, can be monitored or controlled via CRM 140. The CRM 140 may also be used to manage client information, plus other internal organisational information such as staff roles and responsibilities. In some examples the CRM 140 hosts a client “Customer Portal”, shown schematically at 142. The client portal 142 acts as a window to the system 100 for the remote user 118. In some examples the CRM is housed on an Application Programming Interface (API). In some examples the API is hosted using an external cloud infrastructure, shown schematically at 146. In some examples, the CRM 140 is also regularly backed up on an external server 148 to minimise any risk of data loss. For example, the CRM 140 may be backed up to the external server 148 twice a day. To further aid understanding of the invention, a typical “job” will now be described by way of a worked example. According to some examples, from an initial conversation or enquiry with a customer, customer information is populated into the CRM tool 140 and allocated to a relevant organisation, contact or staff member. The CRM 140 may prepare a contract I job review and agree or decline the enquiry based on current capabilities of the system 100. Once agreed, the CRM 140 may generate a proposed start date, approximate end date, and a quote for a testing procedure and the job is added to the CRM 140 with its status set to “Enquiry status”. Each job may also be assigned a unique Job ID. The customer can review details of the job (e.g. start date, end date, quote) and accept or decline the job through the portal 140. Once accepted the job becomes live, and the job is allocated to a relevant test apparatus, such as test apparatus 102. In examples, each test apparatus has its own unique ID to ensure jobs cannot be double booked, and so that each test can be easily tracked and monitored from start to finish. Once the component(s) or product(s) to be tested are received, they are booked into the CRM 140 and installed on to the test apparatus 102. Upon the start of each test the unique Job ID is entered on to the screen of the user interface 134. The customer may also be provided with a link to the camera 124 that is facing the test apparatus, and the link takes them through to a password protected URL. The password will be unique for each job to offer security and protection online. Once the test is started, test data is collected by the one or more sensors 110. Using the unique Job ID, the data is transferred through an API connector that translates the data in to an API readable format that picks up the Job ID and populates the data to the CRM 140 and the client portal 142. The test data is also sent to test report generator 112, as previously explained. In some examples, the test report generator is comprised in CRM 140. This continues until the test comes to an end. If required, the customer can download the data to analyse and make an estimate of whether they feel the test is going well based on the test data and / or any laboratory observations. The term “laboratory observations” may be considered to comprise observations that are physically observed in the testing laboratory, for example by one or more laboratory technicians. For example, if a laboratory technician notices that one of the components under test is showing physical damage or wear but it is still currently operating correctly or within acceptable parameters, the technician may make an observation and add that observation to the client portal 142, along with a brief description of the observation and optionally with one or more images. In some examples the technician has the option on the client portal to add the observation to the test report. If the technician selects “yes”, then the observation feeds in to the report. On the other hand, test data may be considered physical data being transferred from the test rigs, for example from the one or more sensors 110, to the software and / or client portal 142. In some examples the laboratory observations give the customer a good indication of whether the product will pass or fail. If potential issues with the products are flagged by the laboratory observations and the manufacturer thinks the product could fail, the manufacturer can start preparing another product for testing. In some examples, the laboratory observations may flag a potential failure before the test data does (and vice versa in other scenarios). The laboratory observations may, in some examples, be considered qualitative observations. The test will come to an end when the test reaches the required cycles to complete the test or whether the product fails the test. Then, the status on the client portal 142 and CRM 140 may update automatically depending on the outcome of the cycles. For example: • Completed = reached the number set • Paused = The test apparatus has stopped (for maintenance or power cut etc.) • Failed = The product failed to reach the set cycles required In some examples the customer will receive a notification to say the status of the test has changed. The customer can then view what is happening live via camera 124, and / or or go back to the time and date that the test stopped to view why or how it stopped. Whilst the test is ongoing, the test data and laboratory observations are also populating the test report in real-time. When the test comes to an end the final test report is written and ready immediately or near immediately, for approval. In some examples the approval is entered via CRM 140. Once approval is given this can be uploaded to the documentation section of the relevant organisation and the authorised personnel is notified that final test report document has been uploaded, giving the customer the report they need for certification. Figure 2 schematically shows a portion of a display screen or user interface 250. For example the display screen 250 may be viewable via one or both of user interface 134 or client portal 142. The display screen 250 shown in Figure 2 may be considered to comprise live data, and / or form part of a partial test report. In the example of Figure 2, the display screen 250 displays information pertaining to a door closer component. More particularly, the display screen 250 displays: a job ID column 252, which identifies a specific job or component being tested and / or identifies a test apparatus; a cycles column 254, which displays how many test cycles have been undertaken (for example as part of a durability test); a date column 256 displaying a date of the relevant test results; a file column 258 which provides a link enabling a customer to download the test data and / or a partial test report if available; a description column 260 comprising information that has been entered by a technician at the test laboratory (e.g. confirming that a pin of the door closer component has been greased); a closing speed column 262 that displays technical data pertaining to a closing speed of the door closer component; and an ambient temperature column 264 showing an ambient temperature of the test apparatus. Figure 3 shows another example of a display screen 350. For example, the display screen 350 may be for display on CRM 140 and / or client portal 142 and / or user interface 134. Various test data may be displayed, such as job ID 352; job creation date 354; job number 356; number of cycles 358; description 360; closing speed 362; ambient temperature 364. These aspects are the same or similar to those described in Figure 2, and for conciseness are not explained in further detail. The display 350 of Figure 3 further comprises a “show on forms” icon 366 and a “show on portal” icon 368, enabling an operative or laboratory technician to decide whether the information on that row should be included in the full and / or partial test report and whether the information should be displayed on the client portal 142, respectively. A “create new observation” icon is also provided at 370, enabling an operative such as a laboratory technician to input a new observation pertaining to one or more of the jobs. Sample technical data of a test report are shown in Figure 4A and Figure 4B. This data may be included and displayed in a partial test report or a full test report, or indeed be downloadable by a customer via the client portal 142 as required. The example test report data shown in Figure 4A and Figure 4B relates to a torque requirement of a door closer component at various opening and closing angles, as required by the specification or standard. Figure 4A shows data after 5,000 cycles (for example part way through a test), and Figure 4B shows data after 500,000 cycles (for example at the end of the test). In the example of Figures 4A and 4B, each test result 472, and the average 474, is within the test requirement 476, so that a “pass” result is shown in the column 478. In some examples, test data may also be made available to a customer, for example via client portal 142, in a processed manner. For example, test data may be converted into one or more graphs to be displayed in the client portal 142, for ease of understanding by the customer. By way of a non-limiting and illustrative example, Figure 5 shows an example graph or chart which plots Torque (Nm) on the y-axis against door angle (degrees) on the x-axis for a door closer component. The upper plot is for an opening cycle and the lower plot is for a closing cycle. This data may be made available as live data, and / or in a partial or full test report. It will be appreciated that the disclosed invention enables a customer, such as remote user 118, to witness the start of a test remotely. The customer may also be given access to viewing the test from anywhere in the world, at any time of day. The customer also has access to the customer portal 142 to view current and previous test information, as well as some future test information (such as future tests that have been booked in). The customer can also be kept up to date with test status notifications. In examples, live test data is fed into the client portal 142. The test data can then be downloaded for analysis and evaluation. At the end of the test, an automated report can be sent to the customer to give a rapid pass / fail decision rule. Not only is the customer provided with a rapid pass or fail decision, but the customer can also access the sensor data itself, as well as remotely view footage at the point of failure. This enables the customer, who may for example be a manufacturer of safety critical components, to quickly understand reasons for failure and begin resolving any problems. Ultimately, this can lead to better quality products being developed in a more efficient timescale. 16 The examples described herein are to be understood as illustrative example embodiments of the invention. Further embodiments and examples are envisaged. Any feature described in relation to any one example or embodiment may be used alone or in combination with other features. In addition, any feature described in 5 relation to any example or embodiment may also be used in combination with one or more features of other of the examples or embodiments, or any combination of any other of the example embodiments. Various modifications to the preferred embodiments of the present invention, as defined by the appended claims, will be apparent to those skilled in the art. 10

Claims

1. A system for physical testing of one or more physical components, the system comprising:a test apparatus for receiving a component to be subject to a physical testing procedure, the test apparatus comprising one or more devices for applying one or more respective physical tests to the component during the physical testing procedure, and the test apparatus comprising one or more sensors for obtaining test data relating to the component and / or the one or more devices and / or environmental conditions during the physical testing procedure;a computer-implemented test report generator in communication with the test apparatus, the test report generator configured to generate and continuously or continually populate a test report with test data for the component, as the component is being subject to the physical testing procedure;a communication interface, the communication interface configured to enable an authorised user to perform remote monitoring of the physical testing procedure, and the communication interface configured to enable the remote user to request and obtain from the test report generator one or more of: (i) a completed test report comprising completed test data once the physical testing of the component has been completed, the completed test report providing an indication of whether the component has passed or failed the physical testing procedure, (ii) a partial test report comprising partial test data for a period of the test up to when the partial test report was requested;wherein the test report generator is configured to extrapolate test data of a partially completed physical testing procedure to determine a likelihood of the component subsequently failing the physical testing procedure;wherein in response to determining a likely failure of the physical testing procedure by the component, the test report generator is configured to send a notification to the remote user indicating the likely failure and a reason for the likely failure; andwherein the system is configured to enable a human technician to input qualitative observations that can feed in to the full test report and / or the partial test report..

2. A system according to claim 1, comprising a camera that is configured to obtain video or photographic data of the physical testing procedure, and the remote monitoring comprises remotely viewing the video or photographic data of the physical testing procedure.

3. A system according to claim 1 or claim 2, wherein when the component has failed the physical testing procedure, the test report generator is configured to provide a timestamp of when the failure has occurred.

4. A system according to any of claims 1 to 3, wherein the communication interface is configured to make the test data obtained from the one or more sensors available in real time to the remote user, for the remote monitoring.

5. A system according to any of claims 1 to 4, wherein the test report generator is configured to indicate that the component has passed the physical testing procedure when the physical testing procedure has reached a threshold duration or a threshold number of test cycles without failure of the component..

6. A system according to any of claims 1 to 5, wherein the physical testing of the component comprises one or more of: mechanical testing; tribology testing; corrosion testing; fire testing.

7. A system according to any of claims 1 to 6, wherein the component comprises a door closer component, and the one or more devices for applying one or morerespective physical tests to the component comprises an actuator for causing an opening and / or closing force to be repeatedly applied to the door closer component.

8. A system according to claim 7, wherein the one or more sensors is configured to sense, over a predetermined distance or angle of movement of the door closer component, one or more of: an opening speed of the door closer component; a closing speed of the door closer component.

9. A system according to claim 7 or claim 8, wherein the one or more sensors is configured to sense, over a predetermined distance or angle of movement of the door closer component, one or more of: a force required to open the door closer component; a force required to close the door closer component.

10. A system according to any of claims 1 to 9, wherein the one or more sensors comprise one or more of: an optical sensor; a force sensor; a torque sensor; a temperature sensor; a clock or timer.

11. A system according to any of claims 1 to 10, wherein the system comprises a user interface in communication with the test apparatus.

12. A system according to claim 11, wherein the user interface is configured to enable a unique identifier to be input and associated with the testing procedure for the component.

13. A system according to claim 11 or claim 12, wherein the user interface is configured to enable a user to input one or more commands to the test apparatus, wherein the one or more commands comprise one or more of: a start command for starting the testing procedure; a stop command for stopping the testing procedure; a pause command for pausing the testing procedure.

14. A system according to any of claims 1 to 13, wherein the test report generator is configured to produce test reports in conformance with one or more requirements of a certification or industrial standards agency.5 15. A system according to any of claims 1 to 14, wherein the system is configuredto send a completed test report to a certification or industrial standards agency or an approved notified body via the communication interface of the system.

16. A system according to any of claims 1 to 15, wherein the test report generator io is configured to enable the authorised user to download the full or partial test report.

17. A system according to any of claims 1 to 16, wherein the system comprises multiple test apparatus.

Images