SST

It's a very fast airplane.

yeah... I've flown one once.... inverted...

That will pop up three years from now in a post about who did or didn't do what. :o]

So many things have "popped up" that people have never said, it makes little difference...

"Roland Moore" a écrit dans le message de news: RHV1h.331$ snipped-for-privacy@tornado.texas.rr.com...

SST is a systems integrator. Using Software House and Panasonic? Must not be too integrated. We took over one like that and Software House doesn't have the API for older Panasonic gear. AD for sure and Integral play but it looks like Verint got the boot off the SoftwareHouse web site. Must be those Nextiva bugs. Didn't Panasonic just end of life the only switch they made? Panasonic has their own up the coax protocol that no one else shares for their PTZs. SST must be old school integrator. Looks like they have an APC-8X on their site instead of an iSTAR Pro. I never heard the term "Software House Enterprise Partner" I would ask our rep what that is but he wouldn't call us back even if we told him we just bought the company and fired him. Anybody else know? Looks like SST wants to buy something too. More companies it looks like. You selling out Petem? I say sell them all of Canada first.

Nope not selling but they asked us to "help" them on a contract,and i have a strange feeling that it will a catch 22 thing...

you get burn from doing thing with them,and your sell reps want the job....GGGGrrrrrrr

It is not bad to team up with a larger company if you get the conditions right. First establish a draw schedule so you're not being a finance company for them. Especially don't buy into the "the customer hasn't paid us yet." If they want to be the prime then that's their problem not yours. Second make certain you get a good portion of the action on the parts end, not just the labor. You can do that on a percent basis or by saying I'll buy this part for the job and keep the whole margin and you buy that part and do the same. Help? Doesn't sound like they need help or you need practice. If you do the job, make the terms fit you. I used to think that on big jobs everything was very detailed. It's just the opposite. Make sure you have everything covered to the last detail for the whole job, just like you were the prime, and get the margin you need to stay in business or tell them to take a hike.

Not always fun to team with "large"company...btw we all ready have 6 office around Canada,and a dedicated central for 3rd party monitoring,does that at least make us as "big" as SST?

once we got called by a company,they got a contract with one of the top 500 company that have facility in USA and Canada,and since we were doing the Northern part of the customer ,they asked us to "help" them change there whole security concept,by integrating every think on one access control system and "standardise" they're video recording concept..

We did the rewiring and connecting and testing everything and they were programming and managing every thing else.. So they sent us some documentation on how they wanted it looked like a good plan,we started the job,first thing we knew is that the Programmer that was supposed to do the job was working only part time on the project cause he had other project to manage,we could call him at 8:30 in the morning telling him that he forgot to program some stuff on a door (like rte or even output relay) and he would call us back only at 15:30 (and that if he called back on the same day)and he was arguing we needed to check our wiring...witch we already check cause we didn't want to look like fool we were check and rechecking every thing..

we didn't had the capacity to program the system(no rights in the software) but we could see the programming,and about 99% of the time it was simple mistake,but still cause of this we lost about 25% of the time on job looking at stuff that was ok hardware wise,but was not program properly...And the first thing we know is the supposedly programmer was sending mail to the customer telling we were a bunch of moron not to fix ourselves the programming,that he had done,to make thing go,when he knows that we cant do it..

one thing I know is that our local customer (that we were dealing with for more the 15 years) didn't listened to the "programmer" and filed a complaint to his boss caused he was damn tired to have doors dot working for days cause they were not program properly,(and he knew our work was usually done ok,before that project)this led to more irritation from the programmer where he started removing some already working stuff to make "intermittent trouble" on some doors,to bad I was clever enough task a report of programming change in the software (my customer did it cause I didn't had rights) and we saw that on the same days that some door were going havoc the programmer worked on it in the morning and in the evening...

the whole thing cost us more in time that the job was paying,all cause a "big" company wanted some "help" from us...

so when SST come asking for help...I have a bad feeling....

"Roland" a écrit dans le message de news: N3t2h.3601$ snipped-for-privacy@tornado.texas.rr.com...

The guy who gave you the trouble said he was programming? It is hardly programming. It is more like fill in the blanks on the data front end. Most of the time the GUI never lets you even see the real programming. Okay. Well it is always a good idea to make friends with the real IT folks at a job site (not the IT cable pullers). Once you buddy up with IT guys you could avoid that type of problem you mention. Here's how it works for us. If someone is not there to commision the system properly, make certain that remote desktop, via Widows Web TS or even dial up is on (or anything from pcANYWHERE to Win VNC). If there is a computer to do data entry make certain the guy tasked with that is able to hit it in some manner. We do this all the time. If there is finger pointing it is not hard to get a copy of the activity log to see the errors. Sumbmit that log and a bill for your time to his boss. Even if you can't get into the program to print reports, the old ALT & Print Screen key pasted into word works almost as well. For us things always get fixed pretty fast after that.