Issues for Consideration in Designing a Local Swipe Card System
- What form will the customer complete when first visiting the One Stop? In addition to the mandatory data fields, is there any other data that the One Stop wishes to collect? Could the ES 100 be used? Shall a local form be developed?
- How will the swipe card system be marketed within the One Stop so that the customer sees value in its use?
- When will the card be issued to the customer?
- Will the customer swipe the card to record activities/services, or will that be done by the One Stop staff?
- Does the customer need to swipe out?
- How will the One Stop educate the customer as to what the bar codes mean?
- How many staff will be required to implement and maintain the system to assure consistent use, accurate recording of activities and services, and system maintenance?
- How many card printers and scanners will be required to meet the needs of the One Stop?
- Where will they be physically placed? If there is a need to move them, can it be done?
- What PC will be used to run the reports?
- Should formal affiliates and One Stop Centers within an LWIA be on a local area network so that all the data rolls up by One Stop to provide an LWIA perspective to their Board?
- What, if any, are the issues around PC capacity, power sources, electrical capability, Internet connections?
- Can the vendor provide immediate relief for problems encountered? Are remote fixes available?
- What information does the One Stop need to collect, beyond that which is required, to make operational and financial decisions within the One Stop?
- How will the swipe card systems and OSOS be interfaced? If the participant reporting system is other than OSOS, how will the interface with be accomplished between the swipe card system and the participant reporting system?
- If the participant reporting system is other-than OSOS, can the swipe card data be subsequently interfaced with OSOS as well.