D -- INFORMATION TECHNOLOGY SERVICES, INCLUDING TELECOMMUNICATION SERVICES -- POTENTIAL SOURCES SOUGHT

Notice Date

November 20, 2000

Contracting Office

Defense Supply Service-Washington, 5200 Army Pentagon, Rm. 1D245, Washington, DC 20310-5200

ZIP Code

20310-5200

Solicitation Number

H91269-0326-JSAP

Response Due

December 22, 2000

Point of Contact

CDR John Gelinne, Contracting Officer Representative, Joint Staff

E-Mail Address

CDR John Gelinne, Contracting Officer Representative, (john.gelinne@js.pentagon.mil)

Description

DESC: The Joint Staff has identified a requirement to investigate the enhancement or replacement of its existing workflow application which automates development, routing and archiving of "action" folders (with supporting electronic files). The objective is to propose a replacement or re-engineering solution to the existing workflow application (to include rough order magnitude (ROM) costs) into a secure, Windows / Office 2000 compatible, web-based Action Processing collaboration tool that leverages, reuses (if applicable), and enhances the capabilities of the existing Joint Staff Action Processing system. Current concept of operations: The current Joint Staff Action Processing (JSAP) system was developed and fielded to allow automated, paperless development, coordination and routing of action packages. "Actions" are tasks the Joint Staff Secretariat receives and subsequently assigns to the appropriate Directorate for completion/response. Actions are further assigned through that Directorate's Military Secretariat to an Action Officer on the Joint Staff who collaborates on his response internally within his own Directorate or other Joint Staff Directorates, externally with other commands/agencies, or both. Once the action is completed by the AO (predominately through the use of MS Office suite), it is formatted using a custom "Master Document" MS Word template (provided upon request) and routed for electronic signature (Salinas ApprovIt software) by appropriate approval authority. The Joint Staff record(s) is then distributed, as necessary, with an electronic copy archived into either the Joint Staff corporate or Directorate repository through a Document Management System/Records Archive Management application (Intertech-Docupact/Opentext-iRIMS applications). Actions can be generated by agencies external to the Joint Staff or from within one of the Joint Staff Directorates. The current system resides on the Top Secret network and interfaces with MS Outlook client 97 (planned upgrade to MS Outlook 2000 in FY01) and MS Exchange Server mail for package routing and coordination. The Joint Staff uses a variety of modern automation systems to respond to, coordinate with, and task external agencies. These systems are used to communicate, track tasks, craft responses, create briefings, and monitor resources. This information infrastructure consists of approximately 2200 PCs (Pentium through Pentium III 700 using Windows NT 4.0 (with planned upgrade to Windows 2000 in FY 2001) in a network environment running Microsoft's Office/Outlook 2000 suite of applications. The current JSAP implementation uses a highly customized client application that requires extensive development and maintenance to provide enhanced functionality. Ideally, the system should transition to one based almost entirely on commercial off-the-shelf (COTS) components to reduce the life cycle costs of upgrades and ensure basic compatibility with future upgrades to related systems. Areas of special interest to the Joint Staff include the following: 1. Action Tracking System (ATS) commensurate with the current JSAP functionality (current system ATS functionality provided upon request). In addition, support multiple structured action assignment and workflow/mapping(s) in accordance with the Joint Staff business process (workflow map provided upon request). 2. Integration/migration of current workflow into user selectable workspace to either internet, web-based technology or Outlook interface. The user should be able to interact, input documents and taskers or access actions in two ways (depending on system rights): (1) Within an Outlook pane inbox (2) in a browser window spawned from Outlook. The second option will allow greater flexibility and facilitate cross browser support. Portals to collaborative tools such as white board, chat, collaborative planning, communities of interest and real-time video should also be supported by the architecture. 3. Integration with the existing Document Management System/Records Management Archive (Intertech: Docupact/Opentext: iRIMS/Oracle), electronic signature application (Salinas Approvit) currently licensed (or under software maintenance agreement) by the Joint Staff, unless it is shown to be neither cost effective nor functionally beneficial. 4. Support migration to public key infrastructure (PKI) security services within the workflow application to include authentication, access control, auditing, data privacy, data integrity, non-repudiation and security management / authorization or other measures deemed appropriate to support secure workflow. PKI should be supported to provide secure access to the workflow data/repository with eventual scalability to multilevel secure environment. Data storage shall provide the capability to establish and maintain data base/ data security (grant permissions). User, workstation, and user functional role will control access permission. DOD directives on Mobile Code will be considered with the proposed architecture. 5. Support distribution of workflow functionality/standards over wide area networks and multiple enterprises (i.e.: ensure compliance with applicable industry workflow standards to facilitate interoperability with other commercial workflow products). Although the system will be initially implemented on a classified network, the proposal should include a strategy for allowing migration of the workflow system to an unclassified network, while retaining centralized action tracking functionality. 6. Enable/integrate with collaboration and portal tools to Knowledge Management (KM) technologies being studied/developed by the Joint Staff. In this regard, apply current knowledge management best practices and technology to provide a portal to a collaborative/KM environment. In addition, provide effective search tools to help in the initial research required to complete tasks. 7. Support current Joint Staff forms and mechanism of action processing review/approval by senior leadership (template sample provided upon request). 8. Support data storage, replication and backup functionality within current Storage Area Network architecture at the Pentagon and proposed architecture to an alternate site (COMPAQ StorageWorks High level SAN Architecture provided upon request). 9. The product must support various file types to include (but not limited to) images, text, audio and video. Specific design principles including ease of use, simplified system administration, open systems environment (OSE) compliant architecture, scalable to support up to 600 concurrent users in multiple collaborative sessions. Simultaneous editing on multiple file copies distributed in accordance with the workflow rules must be supported. In addition, the product should be extendable to add further functionality in the future as may be required by the Joint Staff. Vendor responses shall be limited to 25 pages, single sided in MS Word 97 compatible format (Times New Roman 12 Pitch). Vendors who respond should summarize in a MS Word table their product's ability to satisfy the eight general requirements cited above (Exceeds/Meets/Does not Meet) and level of product customization required to satisfy each requirement (High, Medium, Low, None). Additional amplifying information can be provided in any format but should be cross-referenced to show how it applies/meets the basic requirements cited above. Vendors who respond should include comments regarding technical support provided during testing and implementation as well as training provided to system administrators and end users. In addition, the government requires product specifications, hardware and software requirements, bandwidth requirements, company history and a list of customers and points of contact who are now or intend to be using the proposed solution. The contractor shall define the full level of engineering and technical services including system development and support, programming services, requirements definition, system design, development, verification and validation, implementation, life cycle support, routine maintenance, facility requirements, acquisition support, technical services support, research and development, integrated logistics support, technical data review, configuration control, operator training, computer security services, network security requirements, and technical program management support required to fulfill the proposed solution. Proposal shall include rough order magnitude cost for the above effort. The facilities clearance required is Top Secret and the level of safeguarding required is Top Secret. This request is for information only. Industry is requested to identify features or performance requirements in the specification that may incur unwarranted cost or risk. In addition, the identification of requirements that should be added to the specification is also encouraged. As industry may expect to see portions of submitted information in future solicitations, no proprietary information should be submitted. THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS REQUEST FOR INFORMATION OR OTHERWISE PAY FOR THE INFORMATION SOLICITED. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of the submission of industry information. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. In addition to the above information, you may submit information regarding existing contracts where the products and services you offer are available, i.e. GSA or other Government contract vehicle. Questions regarding this RFI will be submitted via email only to the address below. Interested parties are requested to submit RFI response by 22 December 2000. These responses shall be submitted via e-mail and hardcopy to: john.gelinne@js.pentagon.mil CDR John Gelinne Joint Staff/SEID Pentagon RM 1B743 Washington DC 20318-9100

Record

Loren Data Corp. 20001122/DSOL016.HTM (W-325 SN5070X6)