Skip to content
View in the app

A better way to browse. Learn more.

Security Installer Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cash for Windows

Featured Replies

3 minutes ago, MrHappy said:

 

once obsolete, they'd not show unless you checked the box for obsolete ?

 

if you describe your product as 10 ir leds turrent, 3.2 mm lens ect...

 

what happen when the latest batch is 12 ir leds & 2.8mm lens ect ?

 

if you just amend the part, should you print a spec then it won't match up ?

Just found this 

image.png

 

Hopefully I just go through the old products and tick that box and it will be less to trawl through quoting 

  • Replies 110
  • Views 1.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I think you do need them. When do you discover a part is superseded? At point of ordering? Contract review? Whenever it is you mark the part in your parts section of your system so it can’t be ad

  • My mate in does swear quite a bit tbf

  • I'm aware of them doing this in the past   TBH I'm surprised nobody picked up AM to try & do a similar thing.   I'd assume the the expertise in running an ARC could make more £

Posted Images

6 minutes ago, MrHappy said:

 

once obsolete, they'd not show unless you checked the box for obsolete ?

 

if you describe your product as 10 ir leds turrent, 3.2 mm lens ect...

 

what happen when the latest batch is 12 ir leds & 2.8mm lens ect ?

 

if you just amend the part, should you print a spec then it won't match up ?

Once the spec is produced and saved that's it, it doesn't change just because the database products has changed  

  • Author
16 minutes ago, PeterJames said:

Once the spec is produced and saved that's it, it doesn't change just because the database products has changed  

 

what happen when you add to an existing system ?

 

you must have to edit the existing word document if you what a complete spec ?

Mr th2.jpg Veritas God

33 minutes ago, MrHappy said:

 

what happen when you add to an existing system ?

 

you must have to edit the existing word document if you what a complete spec ?

No the sales enquiry is a new number and a new spec number. I just produce a quote for the additions, so an extra camera to an existing system would read:

Cameras 1-5 Existing 

Camera 6 Back Garden bla bla bla

In any case, because the original quote is saved as a word doc I could just make a copy and add another device to it. Its just cleaner for me to have separate quotes set to the date I did them, it gives a better historical record. I can see whats in warranty ect

 

  • Author
27 minutes ago, PeterJames said:

No the sales enquiry is a new number and a new spec number...

 

whatever works best for you,

Mr th2.jpg Veritas God

2 hours ago, MrHappy said:

whatever works best for you,

That’s not helpful it just means “whatever”.

Exclude from product looks promising, however referencing the word quote in cabinet doesn't sound like the best idea, it’s a work around. 
A DBase is good for feeding info for printing docs to PDF, Word etc, BUT the data should remain the work horse. By example if you make changes to a job then those changes are recorded on the commissioning sheet and these are fed back to the DBase. This will automatically produce a new as fitted spec in PDF, Word etc (issue 002 xxxxxx) which goes to the filling cab. 
This highlights my gripe with the PDA on CASH as the info will not feed to the DBase which means it has to be entered manually as the PDA is little more than an electronic form of paper albeit better.

The referencing quoted by 6WB is crucial at the point of set up, we left chronological space for 100 detector types on setup and not using half dosent cause any issue.

Customers!

22 hours ago, PeterJames said:

I am not saying that the part number is deleted from all existence once I decide to stop using it, and it wont be because the original part no's will be saved to the original quotes and the original purchase order. In fact the PO is the most important thing to be saved as this tells me exactly what was ordered for the job. Therefore in the unlikely event of a warranty claim I have a record of what it is where it was purchased, and when, on the customers database.

 

The irony of it all is that if an engineer changes a camera under warranty, he will not likely have the same camera onboard (most likely a later camera) when we send the faulty cam back we will most likely get a later model in return. 

 

How often do I check: Everytime I do a  CCTV quote I compare the suppliers quote to my excel sheet  

 

What I do not need is superseded part numbers in my products database, as this means I have to trawl through 20/30 different products to find the current one.

 

I dont need 20 different 5mp cameras when I am currently only using vfocal or fixed lense bullet or turret, white or grey.

 

We only use 4 different detectors for precisely that reason quad, rfquad, dtG3, rfDT, 

We used to be similar in this regard, but we have a much wider portfolio of products these days. I used to be against it but once we moved into the enterprise/global client market you don’t get as much control. We are still relatively restricted on the core systems, but not everyone wants the same cameras on the end of the VMS.

14 hours ago, PeterJames said:

I think nobody seems to think of the bigger picture here. The more I think about it, holding old product numbers in your products area of your database is just another form of hoarding in a paperless way. Maybe I am wrong, but if I need to know when we installed, I can see that on the front page of the customers database. If I need to know what we installed I can look at the spec in the cabinet on the customers database. for warranty I can see it on the PO. I am sure that newsagents didnt keep Marathons on their purchasing list when mars changed the name to Snickers, chocolate bars are only superseded once in a blue moon cameras are changing every other week. 

 

It sounds to me like you aren’t working to an asset level, maybe that’s the difference here.

 

Assets for us are a live item, but they start as a product on a quotation.

21 minutes ago, alterEGO said:

It sounds to me like you aren’t working to an asset level, maybe that’s the difference here.

 

Assets for us are a live item, but they start as a product on a quotation.

To what purpose?

On 11/02/2022 at 20:17, PeterJames said:

I think nobody seems to think of the bigger picture here. The more I think about it, holding old product numbers in your products area of your database is just another form of hoarding in a paperless way. Maybe I am wrong, but if I need to know when we installed, I can see that on the front page of the customers database. If I need to know what we installed I can look at the spec in the cabinet on the customers database. for warranty I can see it on the PO. I am sure that newsagents didnt keep Marathons on their purchasing list when mars changed the name to Snickers, chocolate bars are only superseded once in a blue moon cameras are changing every other week. 

 

Not that I know much about this , but isn't there a simple sort by date for part numbers that have been entered so it would ignore part numbers from old 

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.