BUYER KNOWLEDGE / NEW ARK
Support & Product Lifecycle
Questions about training, maintenance, technical support, software updates, and long-term product lifecycle planning.
95—100
Support & Product Lifecycle
95What warranty do you offer?
Warranty duration and coverage must be stated in the project agreement; no standard warranty length is established. Confirm the terms for the exact hardware and software configuration rather than assuming one policy covers every delivered item.
Ask when coverage begins, what defects are covered, which exclusions apply and how a claim is assessed. Clarify repair or replacement responsibilities, shipping costs and any site work. Keep warranty separate from spare availability, maintenance, software updates and support response commitments, since a warranty does not automatically establish an uptime guarantee or repair SLA.
96What is the spare-parts and repair turnaround?
Spare-part availability and repair turnaround require project-specific confirmation. New Ark's published scope allows discussion of local maintenance and spare arrangements, but it does not establish stock levels, delivery dates or a guaranteed restoration time.
Identify critical items for the selected configuration and agree the reporting, diagnosis, return and repair responsibilities. Ask whether any proposed times refer to acknowledgement, assessment, dispatch or completed repair. Confirm shipping, customs, replacement compatibility and costs in writing; a spare arriving at the site is not necessarily the same milestone as restoring the system to service.
97What training do you provide?
Training content, duration and delivery arrangements need to be agreed for the project; no standard course package is established. For detection-only use, useful requirements include interpreting alerts and confidence information, understanding limitations, reporting events and recognising when maintenance review is needed.
Specify the operator and technical roles, language, location and assessment criteria in the written scope. Confirm which materials and practical exercises are included. Any active-response training or qualification must be assessed separately by competent authorities and accountable qualified personnel; detection training does not itself confer permission to use countermeasures.
98How much maintenance does the system need?
Maintenance workload depends on the selected configuration, installation environment and agreed operating scope. No fixed maintenance interval or maintenance-free claim is established. Noise conditions, obstruction and changes to the site can also affect whether performance needs to be reassessed.
Ask for a written maintenance plan identifying inspection items, authorised procedures, responsible parties and criteria for further testing. Clarify spare requirements, access arrangements and how sensor or network faults are reported. Keep routine maintenance separate from repairs and software updates, with their respective costs and entitlements confirmed in the agreement.
99Are software updates included?
Software updates and patch entitlement must be confirmed in the project agreement; they should not be assumed to be included indefinitely with hardware. Security patches, feature changes and interface revisions may involve different scope and compatibility considerations.
Ask which update categories are covered, for how long, and who is responsible for deployment and testing. Confirm licensing, supported configurations, integration impact and any charges. The written scope should also address how changes are communicated and validated, without assuming a fixed release schedule, automatic updates or continued support for every previous version.
100What is your support SLA, and is local support available?
Support SLA and local availability must be agreed for the project. New Ark's published scope permits discussion of local assembly, maintenance and spare arrangements, but it does not establish a local support location, service hours or guaranteed response and resolution times.
Specify the site, required coverage hours and fault priorities. The agreement should distinguish acknowledgement, technical response, on-site attendance and restoration, and name each responsible party. Confirm escalation channels, remote access conditions, spares and charges so that a general contact route is not mistaken for a contractual service commitment.
NEW ARK / PROJECT CONSULTATION
Have a question about your site?
Share your application, target types, existing sensors and procurement requirements. We can use those details to scope the next project discussion.