We are participating in Pune Expo 2009. The theme this year is Business @ Innovation. You can know more details on http://www.punexpo.com. We are showcasing CentralStation, Time Office, Visitor Management system there with Live Demonstration. You are cordially invited.
Dates: 4th to 8th November 2009
Venue: COEP College Ground, Shivajinagar, Pune
Timings:
Business Hours: 10AM to 4PM
Others: 4PM to 8PM
Our booth is in Hall C, #41.
See you there!
Wednesday, November 4, 2009
Monday, November 2, 2009
Snehapadma CentralStation™ R9.07.01 B9.10.30 Maintenance Release
We are pleased to release a maintenance release of Snehapadma CentralStation™ R9.07.01 B9.10.30. We have incorporated your feedback and fixed some issues along with some enhancements. Please find more about that in the Changelog.
Should you update?
If you are affected by any of following changes, you should update. Specifically, if you are using Mifare or Corporate 1000 format cards, or have number of controllers more than 20, you should update. Another reason to update could be if you get the error "Software has outlived its utility". Should you have any queries, please call us on 9975570715 for advice.
Update procedure:
Download the current release from link http://www.snehapadma.com/SnehapadmaCentralStation.msi
Uninstall the Snehapadma CentralStation from Control Panel
Install from the downloaded msi file.
That is it.
Changelog:
384: Support for 35 bit card format
349: Server should display pertinent Controller information
348: In case controller is not updated, transaction is logged for old employee. Transaction log now corresponds to _current_ employee in DB as against _in memory_ employee of server
347: Cleared cards cannot be reassigned in some cases. Cases: 1. When the credentials are not updated on the Controller, 2. If card is disabled for employee and then unassigned
346: Employee Deletion in Time Office causes inconsistency
345: Cards of employee deleted from Time Office can not be reassigned
344: Footer to Configurator with User Name and Role of Login
343: RBAC for HRM in Configurator
320: CentralStation server shows array out of bounds error, This error is shown in case the number of accessgroups is more than 8.
319: CentralStation reports does not show for some employees. Reports in central statio are not visible for employees with Credential id > 2G.
296: Maitenance Release for release 9.07.1 to fix emergency and revoke emergency batch files.
What is yet to be fixed: The license enforcement is yet to be fixed in this maintenance release.
Should you update?
If you are affected by any of following changes, you should update. Specifically, if you are using Mifare or Corporate 1000 format cards, or have number of controllers more than 20, you should update. Another reason to update could be if you get the error "Software has outlived its utility". Should you have any queries, please call us on 9975570715 for advice.
Update procedure:
Download the current release from link http://www.snehapadma.com/SnehapadmaCentralStation.msi
Uninstall the Snehapadma CentralStation from Control Panel
Install from the downloaded msi file.
That is it.
Changelog:
384: Support for 35 bit card format
349: Server should display pertinent Controller information
348: In case controller is not updated, transaction is logged for old employee. Transaction log now corresponds to _current_ employee in DB as against _in memory_ employee of server
347: Cleared cards cannot be reassigned in some cases. Cases: 1. When the credentials are not updated on the Controller, 2. If card is disabled for employee and then unassigned
346: Employee Deletion in Time Office causes inconsistency
345: Cards of employee deleted from Time Office can not be reassigned
344: Footer to Configurator with User Name and Role of Login
343: RBAC for HRM in Configurator
320: CentralStation server shows array out of bounds error, This error is shown in case the number of accessgroups is more than 8.
319: CentralStation reports does not show for some employees. Reports in central statio are not visible for employees with Credential id > 2G.
296: Maitenance Release for release 9.07.1 to fix emergency and revoke emergency batch files.
What is yet to be fixed: The license enforcement is yet to be fixed in this maintenance release.
Thursday, April 9, 2009
Snehapadma CentralStation™ Released
Today, we released Snehapadma CentralStation™. It has multiple applications:
CentralStation™ Configurator: to let the software know positioning of controllers, readers, input monitors, output controllers, their interrelation, various areas, relations between doors, locks, readers and areas etc.
CentralStation™ Server: to manage credentials, schedules, area controls, and monitoring access, inputs and outputs by directly interacting with the controllers and storing them in database.
Time Office software: to manage role based access control, employees, departments, shifts, schedules, holidays, business logic and view reports etc.
The more is yet to come:
CentralStation™ Client: to monitor access, inputs and outputs by reading through database logs.
Visitor Management System: Upcoming software that is also integrated with the above is complete visitor management software. It has on-the-go card creation for the visitor on Visitor Terminal that is equipped with fingerprint reader, a camera and card reader. Employee can put information about the expected visitor through this system. Company can also put up a list of prohibited people. When a visitor arrives, his/her schedule is checked against expected schedule. His/her fingerprint is taken and compared against previously stored set of fingerprints to check if he/she is not blacklisted. Then, a card is configured so that he/she can access only those areas as approved by employee that has put up the request. His time between main gate and building he is supposed to visit is checked against pre-determined value at the time of in as well as out to raise alarm for security.
Please follow the link below for installation instructions.
http://sites.google.com/a/snehapadma.com/central-station/installation-manual/
We are continuously documenting the help manual. Please visit the following link for the latest version.
http://sites.google.com/a/snehapadma.com/snehapadma-centralstation-manual/
Happy Monitoring!!
Snehapadma CentralStation™ Team
CentralStation™ Configurator: to let the software know positioning of controllers, readers, input monitors, output controllers, their interrelation, various areas, relations between doors, locks, readers and areas etc.
CentralStation™ Server: to manage credentials, schedules, area controls, and monitoring access, inputs and outputs by directly interacting with the controllers and storing them in database.
Time Office software: to manage role based access control, employees, departments, shifts, schedules, holidays, business logic and view reports etc.
The more is yet to come:
CentralStation™ Client: to monitor access, inputs and outputs by reading through database logs.
Visitor Management System: Upcoming software that is also integrated with the above is complete visitor management software. It has on-the-go card creation for the visitor on Visitor Terminal that is equipped with fingerprint reader, a camera and card reader. Employee can put information about the expected visitor through this system. Company can also put up a list of prohibited people. When a visitor arrives, his/her schedule is checked against expected schedule. His/her fingerprint is taken and compared against previously stored set of fingerprints to check if he/she is not blacklisted. Then, a card is configured so that he/she can access only those areas as approved by employee that has put up the request. His time between main gate and building he is supposed to visit is checked against pre-determined value at the time of in as well as out to raise alarm for security.
Please follow the link below for installation instructions.
http://sites.google.com/a/snehapadma.com/central-station/installation-manual/
We are continuously documenting the help manual. Please visit the following link for the latest version.
http://sites.google.com/a/snehapadma.com/snehapadma-centralstation-manual/
Happy Monitoring!!
Snehapadma CentralStation™ Team
Wednesday, December 3, 2008
Snehapadma CentralStation
Recent events like Mumbai Siege by terrorists have heightened the need for security. It happened to some iconic buildings, but the same can happen anywhere, anytime. No body can claim to be immune from such type of attacks. We must try to protect and secure our establishments from possible internal and external threats with best of the technologies that are available at our disposal.
And this means not just buying post-event security gadgets like CCTVs, but preventive security measures that help you
These HID products communicate with credential readers (like card readers or biometric readers) through weigand protocol and various input output devices with potential free contacts. These products can be used for complete centralized access control and building security management like fire alarm, smoke detectors, motion detectors, lights, temperature etc.. We recommend you visit website of HID and these products for more details.
Snehapadma CentralStation brings to you a unified, realtime, multi-location, central monitoring system for access control and building management.
And this means not just buying post-event security gadgets like CCTVs, but preventive security measures that help you
- Detect patterns, anomalies
- Prevent access to installations on need to know basis
- Ensure that all the visitors are accompanied by a person from establishment
- Ensure that minimum occupancy rules are followed for certain parts of the establishment
- Prevent misuse of credentials by the perpetrators
- Remain top of all these things at all times and at location of your convenience.
These HID products communicate with credential readers (like card readers or biometric readers) through weigand protocol and various input output devices with potential free contacts. These products can be used for complete centralized access control and building security management like fire alarm, smoke detectors, motion detectors, lights, temperature etc.. We recommend you visit website of HID and these products for more details.
Snehapadma CentralStation brings to you a unified, realtime, multi-location, central monitoring system for access control and building management.
Friday, November 21, 2008
Auto-Shift Scheduling and Detection
In the last post of Shift Scheduling, Shift Scheduling Is Even More Easy, we saw how we can attach Shift Pattern to the Employee, and thereby reduce the work load and automate shift scheduling. This can very well be used when the Shift Pattern is determinable.
What about the scenarios when it is not possible to predict which employee is expected in which shift?
User of the System is not expected to enter shift on daily basis, rather he/she looks up to the system to assist him / her in this. To do that we need to detect shift automatically. And how?
In the Time Office Software, we examine the time stamps from beginning of the day to next 36 hours. We find First In and Last Out. Now we find which is closest shift to this First In and Last Out. We say that the Shift which has highest proximity to this is Shift automatically detected.
e.g. In a company, where sift timings are 7am - 3pm - 11pm - 7am, and employee is found to have In time of 7:25pm and Out time of 6am, it is determined that 11pm - 7am shift is closest to the time recorded for employee, and other details are evaluated as if employee was assigned this shift.
Please note that the time events recorded must of type In or Out. If time event is of type InOut, system shall not be able to detect shift accurately. E.g., in the above example, had the time events been ambiguous InOut, it is not possible to determine systematically where person is coming in at 6am or going out at 6am. Thus you must configure the devices specifically for In mode or Out Mode.
Ok, how do we tackle the problem of automatic shift detection when employee is supposed to come in a subset of all defined shifts?
A slightly bigger organization might have several shift patterns. E.g. the problem is this: As employee1 works in Unit 4, and Unit 4 shifts are 7am to 3pm to 11pm to 7am, employee can come in these shifts only. However, another employee2, works in Unit 5, whose timings are 8am to 4pm to 12am to 8am. Then there are employees of maintenance department whose shifts are 11am to 7pm to 3am to 11am.
Here comes in Autoshift. You can define multiple autoshifts which is essentially a group of shifts that can be interchanged by the employee. In the above example, we shall have 3 autoshifts: for Unit4, Unit5 and Maintenance.
You can then assign these autoshifts to employees through employee master. Thus while automatically detecting shift of employee working in unit4, only shifts 7am to 3pm to 11pm to 7am are considered. Even if person comes at 8am (actually an hour late), 8am to 4pm shift is not detected though it might be closer to the actual timings.
Flexibility
But not everybody wants this. In such a case, AushiftId of 0 is assigned to employee. If set so, it does not detect the shift, and does time evaluation as per the shift set during shift scheduling.
Others want this to know if two employees have switched the shifts between them, it should not have immidiate approval. It should still process the data according shift given in shift scheduling, where detected shift provides assistance. How do we have all these? Ofcourse through configuration variables which is: SetShiftToDetectedShift.
Only if this variable is set to 1, the detected shift is automatically assigned to the employee. Otherwise, it shows as detected shift, and you can view a report where detected shift is not same as assigned shift to take futher action.
In conclusion:
Employee has additional property: Autoshiftid: 0 means no detection, otherwise detects shift automattically amongst the shifts set in autoshift master. The SetShiftToDetectedShift gives flexibility to determine whether this automatically detected shift be considered in time evaluation calculations directly.
Snehapadma Time Office Team
What about the scenarios when it is not possible to predict which employee is expected in which shift?
User of the System is not expected to enter shift on daily basis, rather he/she looks up to the system to assist him / her in this. To do that we need to detect shift automatically. And how?
In the Time Office Software, we examine the time stamps from beginning of the day to next 36 hours. We find First In and Last Out. Now we find which is closest shift to this First In and Last Out. We say that the Shift which has highest proximity to this is Shift automatically detected.
e.g. In a company, where sift timings are 7am - 3pm - 11pm - 7am, and employee is found to have In time of 7:25pm and Out time of 6am, it is determined that 11pm - 7am shift is closest to the time recorded for employee, and other details are evaluated as if employee was assigned this shift.
Please note that the time events recorded must of type In or Out. If time event is of type InOut, system shall not be able to detect shift accurately. E.g., in the above example, had the time events been ambiguous InOut, it is not possible to determine systematically where person is coming in at 6am or going out at 6am. Thus you must configure the devices specifically for In mode or Out Mode.
Ok, how do we tackle the problem of automatic shift detection when employee is supposed to come in a subset of all defined shifts?
A slightly bigger organization might have several shift patterns. E.g. the problem is this: As employee1 works in Unit 4, and Unit 4 shifts are 7am to 3pm to 11pm to 7am, employee can come in these shifts only. However, another employee2, works in Unit 5, whose timings are 8am to 4pm to 12am to 8am. Then there are employees of maintenance department whose shifts are 11am to 7pm to 3am to 11am.
Here comes in Autoshift. You can define multiple autoshifts which is essentially a group of shifts that can be interchanged by the employee. In the above example, we shall have 3 autoshifts: for Unit4, Unit5 and Maintenance.
You can then assign these autoshifts to employees through employee master. Thus while automatically detecting shift of employee working in unit4, only shifts 7am to 3pm to 11pm to 7am are considered. Even if person comes at 8am (actually an hour late), 8am to 4pm shift is not detected though it might be closer to the actual timings.
Flexibility
But not everybody wants this. In such a case, AushiftId of 0 is assigned to employee. If set so, it does not detect the shift, and does time evaluation as per the shift set during shift scheduling.
Others want this to know if two employees have switched the shifts between them, it should not have immidiate approval. It should still process the data according shift given in shift scheduling, where detected shift provides assistance. How do we have all these? Ofcourse through configuration variables which is: SetShiftToDetectedShift.
Only if this variable is set to 1, the detected shift is automatically assigned to the employee. Otherwise, it shows as detected shift, and you can view a report where detected shift is not same as assigned shift to take futher action.
In conclusion:
Employee has additional property: Autoshiftid: 0 means no detection, otherwise detects shift automattically amongst the shifts set in autoshift master. The SetShiftToDetectedShift gives flexibility to determine whether this automatically detected shift be considered in time evaluation calculations directly.
Snehapadma Time Office Team
Sunday, November 16, 2008
It has been pretty quite
Dear Readers,
Yes it has been pretty quite for last few months. Which means we were too busy to blog about what we were doing all the time. Not a great scenario. However, this means that we now have a lot of things to tell you about!
In all this time, we were continuously improving upon the time office software, whose current version now 8.11 has most of the things that were on the wish-list.
We were also busy on couple of other projects. Expect announcements on those soon.
I guess we are going to have a lot of activity on the blog in next two months.
Stay tuned
The Snehapadma Team
Yes it has been pretty quite for last few months. Which means we were too busy to blog about what we were doing all the time. Not a great scenario. However, this means that we now have a lot of things to tell you about!
In all this time, we were continuously improving upon the time office software, whose current version now 8.11 has most of the things that were on the wish-list.
We were also busy on couple of other projects. Expect announcements on those soon.
I guess we are going to have a lot of activity on the blog in next two months.
Stay tuned
The Snehapadma Team
Tuesday, August 5, 2008
Self Manual Entry: Should it be Allowed or Not
One of our client asked us this thing. Should a Department Head, or an Acting Department Head be able to do manual entry for himself or not...
Our natural response was: How do you want it? Client said no. They should not. Now there are other clients who do not care about this. So what do we do?
Now we have configuration parameter DenySelfManualEntry which shall be 0 (i.e. Selft Manual entry not denied but Allowed) by default. Client can set it to 1 (or deny) and is now assured that user shall not be able to make manual entries for himself or herself.
This feature shall be included in 8.09 version of the software.
Yet another configuration parameter so that the Time Office Software behaves the way you want.
Our natural response was: How do you want it? Client said no. They should not. Now there are other clients who do not care about this. So what do we do?
Now we have configuration parameter DenySelfManualEntry which shall be 0 (i.e. Selft Manual entry not denied but Allowed) by default. Client can set it to 1 (or deny) and is now assured that user shall not be able to make manual entries for himself or herself.
This feature shall be included in 8.09 version of the software.
Yet another configuration parameter so that the Time Office Software behaves the way you want.
Subscribe to:
Posts (Atom)
