DEFENSE INTELLIGENCE AGENCY, BUILDING 6000, BOLLING AFB, WASHINGTON, DC 20340-3084

B -- AUTOMATED MESSAGE HANDLING SOLUTIONS SOL DP2/0079Z/97 DUE 052197 POC Purchasing Agent, IDA LOGSDON, (202)2318290 The Virginia Contracting Activity on behalf of The Defense Intelligence Agency (DIA) is looking for suggestions on replacing its current automated message handling system (AMHS). THIS IS NOT AN RFP AND THE GOVERNMENT IS IN NO WAY OBLIGATED TO A RESPONDENT. RESPONDENTS ARE NOT TO REQUEST COPIES OF A SOLICITATION DOCUMENT AS NONE EXISTS. The minimum functional requirements are: (1) Ability for users to query the system for documents meeting certain criteria. (2) Ability for users to write profiles (i.e. standing queries; the system will compare incoming documents to the profiles and, if they match, send the document to the user). (3) Ability for users to save a document (either the full text of the document or a pointer to where the full text is stored) in his/her own files. (4) Ability for users to print a document. (5) A Graphical User Interface for both users and administrators (the client component must run on Windows NT, SunOS 4.1.x, and Solaris 2.5 workstations). The minimum administrative requirements are: (1) Administrator can control user accesses to categories of documents and to other user's profiles. (2) Ability to detect and remove incoming documents that have errors or have been identified by a "rejects" profile; ability to edit those documents; ability to resubmit those documents to the system after editing. (3) Ability to backup and recover data (documents, profiles, folders, etc.). The minimum technical requirements are: (1) Receive documents feed it from DIA's Communications And Message Profiler (CAMP) System (if you are not aware of the specific CAMP system, then identify how your solution can be adapted for a particular document feed). (2) Capable of handling ("handling" means the system will not crash under this load) 1000 concurrent users, 300 queries per hour retrieving about 5000 documents, 15000 active profiles, 15000 documents per day with a peak of 850 per hour, document size between 1KB and 200KB (average of 4KB), average document matches against 100 profiles. (3) Year 2000 compliant (can understand incoming documents with four digit years and correctly interpret those with 2 digit years; i.e. treat '00' as '2000'); user interfaces can accept 4 digit years; all reports use 4 digit years. (4) Application Programming Interfaces (APIs) for external functionality. (5) Ability to combine sectional documents (i.e. wait for a specified period of time until all parts of a document are received and then process them as one). In addition, there are many features which are desirable. For its query and profiling capability, its desired that the system has the following features: (1) A choice of query or profile creation interfaces for the user; e.g. user can build the query through a point and click form or enter the query in free text at a command line. (2) User can save, copy, delete, and rename queries and profiles; user can change a query into a profile and vice versa. (3) Queries and profiles can handle complex boolean logic (i.e. extensive nesting of parenthesis). (4) Queries and profiles can include context restriction (i.e. the 'NOT' boolean operator). (5) Queries and profiles can include proximity (e.g. search for 'Russia' within 5 words of 'tank'). (6) Queries and profiles can refer to zones of a document (e.g. search for subject contains 'Russia' and body contains 'tank'). (7) Queries and profiles can refer to catalog information derived from a document (e.g. source = 'DIA' and type = 'Evaluation'). (8) Queries and profiles can specify a date range. (9) Queries and profiles can include wildcards. (10) Queries and profiles can search based on sound of word (soundex searches). (11) Queries and profiles can search based on concepts (e.g. system will understand what "field artillery" means). (12) System has synonym lists for use in queries and profiles (e.g. user won't have to spell out every variation of the name "Khadafi"). (13) Weights can be assigned to different terms in a query and profile for use in ranking results. (14) User can submit searches to be run at a given time in the future (an unattended search). (15) System will allow searches to continue after a user logs off. Desired query and profiling results reporting capabilities are: (1) System tells user how many documents were retrieved by a query. (2) System can provide status of a query (number of hits so far); status can be updated automatically; user has option to abort; user can begin working with retrieved documents before a query is complete. (3) System updates a list of profile results immediately even while being viewed by user. (4) User has ability to save query results hit set; user has option to specify name of saved hit set. (5) System indicates to the user which documents the user has not viewed. (6) Ability to rank query results based on relevancy to query criteria; ability to display results in rank order and permit user to specify where to cut off (e.g. don't show results with rank below x). (7) User can sort the documents in a list (whether the list is from a search, from profile results, or folder contents) in various ways (e.g. rank order, date descending). (8) Ability to alert user as soon as a document matching a specific profile arrives. (9) System highlights terms that matched the terms in the user's query or profile. (10) Ability to jump directly to the first or next highlighted term in a document. Desired query and profiling results handling capabilities are: (1) Ability to add personal annotations to a document and later modify or delete them. (2) User can submit iterative searches (i.e. search the results of my query or profile). (3) Ability to send documents to other users; ability to include his/her personal annotations; ability to upgrade (not downgrade) documents before sending them to another user. (4) Ability for a user to save a document in his/her own folder; the user can create several folders; the folders can have a hierarchical structure; user can grant access (e.g. read, write, modify) to a folder to another user; system will assign a default name to a saved document which the user can change; user can attach keywords to a document saved in a folder and perform searches based on those keywords; user can move and copy documents between folders, preserving annotations, keywords, and attributes. (5) When printing a document, system extracts classification and puts it in header and footer; user can upgrade (not downgrade) the classification. (6) User can upgrade (not downgrade) the classification of documents saved in a folder. (7) If the document saved in a folder is actually a pointer to a central copy of the document, then need ability to export the full text a document to a user's file. The desirable administrative features are: (1) Ability for an administrator to modify the synonym list. (2) Ability to monitor and report current status of system and components (e.g. size of document queue). (3) Ability to control which individuals can look at certain documents (based on classification, caveats, or originator). (4) Ability to audit and report user activities (e.g. failed logon/access attempts, what documents a given user saw and what he did with them, which users saw a given document and what they did with it). (5) Ability to detect and remove duplicate incoming documents. Other desirable features are: (1) Reasonable response times under the load described previously ("reasonable" is deliberately vague to allow maximum latitude for solutions). (2) Context sensitive help. (3) User definable macros and function keys. (4) Accessible via a web browser. (5) GUI gives the user flexibility in customizing the appearance (e.g. window sizes, fonts, colors). Desirable technical features are: (1) Ability to give precedence to some documents in the document queue. (2) Stores documents once; pointers to the documents rather than the document itself is sent to the user. (3) Identify zones of a document (zones are specific portions of a document; e.g. subject line, addressee) to permit querying against them. (4) Extract catalog information (e.g. source, type, classification) from a document to permit querying against them. Please address all minimum requirements listed above. If your solution can not satisfy a minimum requirement, please explain why its still a viable solution. Please submit your suggestions in writing (no more than 4 pages) to Defense Intelligence Agency Attn: SYD-1/Andrew Sheldon, Bldg. 6000; Bolling AFB, Washington, DC 20340. Please reference AMHS. Vendors MUST include a facsimile number, if available, in their correspondence. (0090)

Loren Data Corp. http://www.ld.com (SYN# 0016 19970402\B-0005.SOL)