SOURCES SOUGHT
70 -- AIir Force Services Agency (AFSVA) Services Activity Management System (SAMS)
- Notice Date
- 2/16/2006
- Notice Type
- Sources Sought
- NAICS
- 517910
— Other Telecommunications
- Contracting Office
- Department of the Air Force, Direct Reporting Unit - Air Force Services Agency, HQ AFSVA - AFNAFPO, 9504 IH35N Suite 370, San Antonio, TX, 78233
- ZIP Code
- 78233
- Solicitation Number
- F41999-06-I-6010
- Response Due
- 3/17/2006
- Archive Date
- 4/1/2006
- Description
- 1.Introduction. The Air Force Services Agency?s (AFSVA) is Requesting for Information (RFI). This is not a Request for Proposal (RFP). Any inquiries about or requests for a solicitation will not receive a response. This synopsis is for information and planning purposes only. It does not, in its issuance, restrict the NAFIs as to their ultimate acquisition approach. AFSVA is looking for an enterprise-wide Services Activity Management System (SAMS) software/systems technical solution that will provide flexible user-designed business rules and features that support various activity management operations. We have included in depth information about AFSVA?s Hardware and Software requirements (Appendix A), Security Requirements and Management (Appendix B) and Acronym List (Appendix C) at our web site at http://www.afnafpo.com. 2. Respondents? Replies to RFI. To maintain consistency and equality in this process, vendors are requested to use the structure outlined below for their response. Cover Page Vendor Name Vendor Address Contact information for the vendor representative Response to the substance of this RFI Brochures and/or other literature While hardcopy is acceptable, e-mail is the preferred submission method. The file should be in Adobe Acrobat or Microsoft Word format. It should be sent to the individual below no later than 17 April 2006. Ms. Hope Young 9504 IH 35 North, Suite 370 San Antonio, TX 78233 (210) 652-6931 (Voice) (210) 652-6309 (Fax) hope.young@randolph.af.mil AFSVA will not provide reimbursement for any expenses incurred in connection with this RFI including costs of preparing a response, providing any additional information, or preparing/presenting a software demonstration. 3. Scope and Description. This must be a web-based system that supports federal and state(s) laws and be capable of running under common commercial operating systems in stand-alone or network environments. The supported Services activities must share common data elements (customer information, facility and equipment schedules, etc.) across the entire system. Customer self-serve functions (reservations, update of household data, payments, etc.) via touch-tone telephones and web-based routines must be available. The system must be able to import, export, and report data for use by other government and non-government data systems (e.g. accounting) through user-initiated routines or ?live? interfaces. Data entry/capture methods include standard and programmable keyboards, touch screen, barcode and magnetic-stripe reader. The system must support common peripherals to include electronic cash drawers, pole displays, hand-held inventory taking units, credit card transactions and multiple print devices. 3.1 There are approximately 98 Air Force bases with appropriated fund (APF) and non-appropriated fund (NAF) activities. The Headquarters, Air Force Services Agency (HQ AFSVA), is seeking information for a SAMS system to meet the needs of a range of community and recreation programs. The types of programs include youth activities, child development centers, family day care, full-day and before and after school programs, community centers, fitness and sports centers, bowling centers, outdoor recreation programs, equipment rental, golf courses, marketing, aero clubs, information-tickets-travel, arts and crafts centers, auto hobby shops, swimming pools, recreational vehicle (RV) storage, campgrounds, veterinarian and deployed operations. These programs require a system to handle functions which include, but are not limited to, activity registration, instructor and volunteer management, campsite reservations and check in/out, locker and storage management, equipment checkout, equipment and parts inventory management, facility and court reservations, equipment and facility maintenance management, retail sales management including food and beverage operations, customer records including medical and immunization data, facility and program membership and access control, league and tournament management, ticket sales and trip/tour bookings, tee time reservations, average/handicap calculations, and related program management functions. The software should also support deployed activity operations. Many of the above functions are performed manually because the activities lack connectivity to the Internet. 3.1.1. Prospective vendors should include all information regarding implementation, field guidance, training and sustainment services needed to support all Air Force Services entities worldwide. 3.1.2. AFSVA reserves the right to request software demonstrations from any prospective vendor. If desired, demonstrations will be scheduled on a non-interference basis during the remainder of the current calendar year. 3.1.3. Prospective vendors: 3.1.3.1. Should include any hardware/software that augments or enhances their products? performance or utility as separate items in their RFI 3.1.3.2. Should understand that replies consisting of software yet to be developed (e.g., ?Vaporware?) will not be accepted, and 3.1.3.3. Should understand that replies consisting of DOS or Macintosh based software products will not be accepted. 4. Common Activity Requirements. All prospective software must meet each of the following requirements (if applicable): 4.1. Capable of managed and/or automated software updates. 4.2. The system will be Web-based able to be accessed over a wide area network. 4.3. Must have the capability for various management levels to access the system through the Internet 4.4. Able to create, format, and transmit a daily flat-file interface to the AFSVA Oracle 11i E-Business Suite. 4.4.1. Initial flat file interface must capability of migrating to new messaging technologies such as XML in future. 4.4.2. The interface will have established or create application processing interface (API) into Oracle?s E-business suite. 4.5. Software database is relational or open database connectivity (ODBC) compliant. 4.6. Able to allow administrators to customize screens. 4.7. Software must run on any workstation that meets or exceed the minimum requirements set by the Air Force. (See Appendix A and B) 4.8. Capable of role-based or individual security setup. 4.9. Laser and/or thermal printer compatible. 4.10. Capable of automated backup and recovery procedures. 4.11. DoD Public Key Infrastructure (PKI) X-509 certificate compliant. 4.12. Compatible with common non-proprietary POS peripherals 4.13. Compatible with handheld devices for recording visits, tee starts, inventory and attendance 4.13.1. Works with e-mail programs for automatic communication 4.13.2. Supports range of customer self-service transactions via touch-tone phone 4.13.3. Supports range of customer self-service transactions via web using standard internet browsers such as Netscape and Microsoft Internet Explorer 4.14. Able to accept major debit and credit cards as payment. 4.15. Able to conduct debit/credit card verification over IP. 4.16. Support transaction processing for the Air Force Proprietary Club Card (private label card prefix "603028") 4.17. Ability to process through "Paymentech", the Air Force's current credit card transaction processor 4.18. Able to accept multiple currencies types as payment. 4.19. Capable of providing a full audit trail of all transactions. 4.20. Ability to change from old to new chart of accounts (GLACs and Cost Centers) without losing historical detail 4.21. Capable of electronic check handling 4.22. Software must perform activity operational related functions: 4.22.1. Must perform and generate a variety of analysis functions and reports 4.22.2. Must provide users the capability to generate ad hoc reports. 4.22.3. Must be able to output report data as graphs and spreadsheets 4.22.4. Data must be export capable to provide vertical and horizontal reporting 4.22.5. The graphical user interface and functionality of the software must provide flexible and efficient navigation for all functions needed for daily use by clerks, technicians, and managers alike 4.23. The software must support a large number of onsite users and remote authorized web-based users with limited viewing access. 4.24. Software must provide immediate on-screen user Help capability. 4.25 Software must reads barcode and magstripe based ID cards. 4.26. Common Operational Functional Requirements 4.26.1. Activity Management 4.26.2. Site/Storage Management 4.26.3. Customer/Household Management 4.26.4. Equip. Loan/Rental & Management 4.26.5. Facility Management 4.26.6. Guest/Member Management 4.26.7. Inventory Management 4.26.8. League/Tournament Management 4.26.9. Point of Sales 4.26.10. Trips/Tour Management 4.26.11. Instructor/Coach/Pro Scheduling 4.27. Family Member Programs (FMP) Flight Unique Requirements: Child Development Centers (CDC)/ Family Child Care (FCC)/Youth Programs (YP)/School Age Programs (SAP)/Community Centers (CC): 4.27.1. Employee/Contract Staff/Volunteer Management 4.27.2. Ability to track Employee/Contract Staff/Volunteer Background Clearances and alert renewal requirements 4.27.3. Ability to track and change immunization requirements and fee payment options/costs 4.27.4. Track child/youth/family/employee/facility data to include information from AF Forms, USDA, and other forms currently in use and governing daily regulatory operational requirements
- Place of Performance
- Address: AFNAF PURCHASING OFFICE, 9504 IH 35 NORTH SUITE 370 SAN ANTONIO, TX
- Zip Code: 78233
- Country: United States
- Zip Code: 78233
- Record
- SN00989720-W 20060218/060216212811 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |