Department of the Air Force, Air Force Materiel Command, AFFTC -- AF Flight Test Center, 30 North Wolfe Avenue, Edwards AFB, CA, 93524-6351

70 -- RESOURCE ALIGNMENT / SCHEDULING SOFTWARE SOL F04611-00-R-0060 DUE 070500 POC Leanne Collins, Contract Specialist, Phone 661-277-9553, Fax 661-275-9626, Email leanne.collins@edwards.af.mil -- Cathi Cleveland, Contracting Officer, Phone 661-277-9448, Fax 661-275-9683, Email WEB: Visit this URL for the latest information about this, http://www.eps.gov/cgi-bin/WebObjects/EPS?ACode=R&ProjID=F04611-00-R-0 060&LocID=906. E-MAIL: Leanne Collins, leanne.collins@edwards.af.mil. DESC: THIS IS A SOURCES SOUGHT ANNOUNCEMENT ONLY. BASED ON RESPONSE TO THIS SOURCES SOUGHT, A REQUEST FOR PROPOSAL IS PLANNED IN THE NEXT 60 DAYS. THERE IS NO SOLICITATION AVAILABLE AT THIS TIME. REQUESTS FOR A SOLICITATION WILL NOT RECEIVE A RESPONSE. THE SIC CODE IS 7372 WITH A DOLLAR LIMIT OF $18 MILLION. INTERESTED PARTIES NEED TO IDENTIFY IF THEY FALL INTO ONE OF THE SMALL BUSINESS FOLLOWING CATAGORIES: Small Business, Hub Zone Small Business, Veteran Owned Small Business, Woman Owned Small Business, or Small Disadvantaged Business. This is a request for sources of technical and marketing information on the availability of resource scheduling COTS product(s), similar to today_s web-based airline/hotel reservation systems. The desired IT solution is envisioned to be a commercial-off-the-shelf (COTS) product to meet a majority of our requirements, however, we realize there will be a need to tailor the product for our specific purpose. Operations and maintenance (O&M) and follow-on development will be provided by an in-house support organization. The tailored COTS product(s) should meet the following minimum capabilities: User Interface -- Provide user with a graphical, web based browser interface, which may utilize the latest Netscape and Internet Explorer production versions. The system should be usable across current browser platforms. -- Provide user visibility into resource availability allowing all users _self-scheduling_ of resources in a real-time mode. -- Provide user interface(s) for the creation, modification and deletion of mission records and selective add/modify/delete of resources assigned to a mission record. -- Provide the capability to cancel an entire mission or individual resources. Record Management -- Generate unique mission identifiers for every mission record. -- Ensure current data state reflects uncommitted/in-process transactions. -- Maintain data integrity between mission record and all assigned resources. -- Maintain record transaction information for historical reporting and tracking purposes. Resource Management -- Ability to define, change and maintain resource attributes (resource types, resource availability/non-availability, resource configuration, preparation times, and dependencies). -- Provide capability to input and maintain resource profiles (commonly used resources) that will aid users in creating missions. Business Rules -- Support time-based and event-based actions on mission and resource state changes. Mission state codes shall be user definable and configurable by user. -- Ability to apply business rules for individual customers and resources. -- Ability to employ a _Cancellation Policy_. -- Ability to process user _Priority System_. -- Ability to process _Waitlists_ or _Standby_ lists against scheduled resources. -- Ability to _Block Schedule_ resources for a given customer for specified time windows. -- Ability to apply a customer priority adjustment based on historical data. Outputs/Reports -- Users shall have the ability to query and output, to both screen and printer, current schedule and metric data/information. System Interfaces -- The system shall use an open system design (no proprietary elements) to maintain scalability/extensibility to allow incorporation of new technologies. -- Client: Intel Pentium PC-based platform with Windows 9x/2000/NT, MS Office Pro 97/2000, Internet Explorer/Netscape Navigator front-end. -- Server: UNIX-based Oracle or Windows NT-based SQL Server -- Use a DBMS system (i.e., Oracle, SQL Server) that is an industry standard and not be developed as a customized DBMS. -- Support MAPI (Outlook) and SMTP email notifications based on event (state changes) or time triggers. -- Ability to interface with legacy databases for resource availability (availability/non-availability and configuration) information interchange. Examples: CAMS/ASD (Aircraft Maintenance), MAMS (Airspace), EFDS (Frequency Management), MP2 (Range Resources), CenterMIS (Edwards AFB MIS) -- 781 (Flying Hours Repository). -- Capability to export data in variety of standard formats (ASCII, CSV, etc.). System Volume -- Ability to accommodate up to 150 concurrent users. -- Ability to accommodate up to 2000 resources. -- Ability to accommodate up to 30000 missions or at least three years of data online. -- Provide a capability to archive historical records to an off-line storage medium that can be reloaded if required. The time periods for the archive capability will be user definable and configurable. System Response Times -- Maintain current scheduling data in a real-time mode with no data latency. Synchronized system-wide updates.. -- Be able to process any transaction within 10 seconds or less. A normal transaction is defined as a scheduling action that invokes a state change to a mission and/or resource record. All response times are measured from any point within the boundaries of the Edwards AFB LAN. -- Allow for instant updates to system operations when scheduling rules are altered by authorized users. All future scheduling actions will be affected without the system being stopped and restarted. System Administration -- Provide capabilities to define, change or maintain user attributes, system access, read/write/edit/cancel and other rights/privileges. -- The system shall support FIPS 140-1 compliant SSL Secure Communications -- User validation and authorization must integrate with existing Microsoft Windows NT domain security authentication. -- Be available in a 24 hours, 7 days a week. System backups must occur while system is operational. -- Provide a capability to recover and restore to a saved state (backups) when system operations are disrupted. Operations and Maintenance -- The system shall be developed and documented to allow in-house operations, maintenance and support. Training -- On-site user and system administration training shall be performed during system rollout. A more detailed System Requirements Document which includes process charts, entity relationships, business rules, and interface diagrams, is available at our web site: http://bsx.org. (BSX Public Marketplace, Edwards Marketplace, Resource Alignment / Scheduling Software) Please include: a) pricing for the base COTS product and any licensing or future upgrade fees, b) pricing for customization/tailoring/integration costs to achieve minimum system requirements, and c) a schedule that outlines major development, test and rollout milestones, d) points of contact that are knowledgeable about the technical aspects of the software, and e) 10 copies of literature that addresses the above capabilities and any other important technical aspects of the software. Only firms that currently have COTS or GOTS product(s) or offerors with demonstrated ability and experience successfully integrating COTS or GOTS product(s) possessing a majority of the above capabilities are invited to respond. An operational system is desired by May 2001. Responses to this sources sought should be addressed to AFFTC/PKAA, ATTN: L. Collins, 30 North Wolfe Avenue, Building 1609. Any questions regarding this sources sought should be emailed to the contracting officer, leanne.collins@edwards.af.mil. Telephonic requests will not be accepted. Posted 06/20/00 (D-SN466752). (0172)

Loren Data Corp. http://www.ld.com (SYN# 0270 20000622\70-0014.SOL)