SOURCES SOUGHT
D -- Market Research- Request for Infomation - FLIS Transformation - Enterprise Workflow Tool
- Notice Date
- 1/9/2009
- Notice Type
- Sources Sought
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Defense Logistics Agency, DLA Acquisition Locations, Defense Reutilization and Marketing Service, Federal Center, 74 Washington Avenue North, Battle Creek, Michigan, 49037-3092
- ZIP Code
- 49037-3092
- Solicitation Number
- FLISTransRFI
- Archive Date
- 2/10/2009
- Point of Contact
- David D Straughn,, Phone: 269-961-7258, David D Straughn,, Phone: 269-961-7258
- E-Mail Address
-
david.straughn@dla.mil, david.straughn@dla.mil
- Small Business Set-Aside
- N/A
- Description
- REQUEST FOR INFORMATION- ENTERPRISE WORKFLOW TOOL 1. INTRODUCTION This document is a market research Request for Information (RFI) for a single enterprise workflow tool for the Defense Logistics Information Service (DLIS). The current aim of DLIS is to procure and implement a technical solution that receives, sorts and routes input requests; provides customized research screens depending on type of input request; and generates data input to the Federal Logistics Information System (FLIS). The structure of the enterprise workflow tool will be distributed across DLIS; using the software to connect employees into one cohesive, transparent working community. Together with workload tracking, the organization will be able to monitor work effectively and therefore optimize the workforce. The technical solutions needed for the initiative fall into three broad areas of work; but all pieces should flow seamlessly together: •A workflow manager •A customizable screen to view data/information for research purposes •A data input tool For efficiency reasons, the successful implementation of the enterprise workflow tool is centred on the desire that data be sent from multiple sources into a single workflow manager. 1.1 Scope of the Request for Information Potential suppliers should note that this Request for Information is for guidance leading to a process of a final solution selection, and is for the supply and help with the operation of: •A robust enterprise workflow tool to include collaboration requests •A reporting tool DLIS is seeking innovative and cost-effective solutions, which will meet the evolving requirements of the project. It is hoped that from the RFI responses that DLIS will be able to select and approve its solution to subsequently begin development/procurementconcept refinement, technology development and eventually procurement. 2. BACKGROUND A short description of the primary type of workload to be completed by the enterprise workflow tool follows: 2.1 FLIS A large portion of the workload DLIS performs revolves around FLIS and the information necessary to keep the FLIS data base current. For this reason, it is helpful to understand how the FLIS system works. FLIS is the primary component of the Federal Catalog System (FCS) which was mandated by the Defense Cataloging and Standardization Act through Public Law 82-436, Chapter 539, 1 Jul 52 and is regulated by Department of Defense (DoD) 4100.39-M. The intent of FLIS is to record a unique item identifying number for items of supply based on a part number and supplier. In order to define the unique item identifying numbers, FLIS allows for a systemic, standardized approach to naming, classifying, and describing an item of supply, as well as, a mechanism to distribute item of supply data to customers. This process is referred to as “cataloguing” because the FCS is an electronic catalog identifying the attributes of DoD procured part numbers based on suppliers. The information in the FLIS data base relates to military activities, Federal civil agencies, participating foreign countries, and private industry. Management information is processed in the following areas: supply management, item identification, tailored data products, DoD Interchangeability and Substitutability (I&S) family data, standardization, and Commercial and Government Entity (CAGE) Code Management. General information about the FLIS system can be found here: http://www.dlis.dla.mil/PDFs/Procedures/vol01.pdf. The FLIS system is very robust in supporting legacy customers that communicate via standardized legacy formats, however the logistics landscape is rapidly changing. The emergence of Enterprise Resource Planning (ERP) based supply chain systems, Performance Based Logistics, Base Realignment and Closure (BRAC), and an increased need for master data exchange is driving the need to modernize the FLIS system. Evaluating workflow options and methods in which the database is updated is a crucial beginning to true modernization of the system. 2.1.1 Scenarios for use: The Federal Catalog Program is composed of those tasks that build the comprehensive logistics data record utilized to identify, requisition, ship, store, dispose and make other logistics decisions related to an item of supply during its operational life cycle. The tasks in this process include: Item Name Assignment: •Designation of commonly recognized noun or noun phrase that answers “What is it?” •Based on availability of technical data and other tools Item Entry Control: •Filtering process which scrutinizes potential candidates for inclusion in federal catalog •Manual and systemic comparisons done with existing items and standards Item Identification Preparation: •Recording of characteristic data to describe the physical/functional attributes of an item of supply •Based on availability of technical data Data Maintenance: •Actions necessary to ensures complete, accurate, and current logistics data records •Results of service requests, system incompatibility notices, etc. Requests for Supply Support: •Requests to record user interest, assign management data, and review/accept substitutes •Originate from requests by service/agency to be a user of item managed by another service/agency The above tasks are just a sample of the types of workload DLIS performs. The proposed solution should be robust enough to cover a wide range of scenarios and workload. 2.1.2 Transmissions & file types Database entries PDFs Web pages E-Mail 3. Functional Requirements:- DLIS is seeking a workflow tool that is capable of receiving work requests from multiple sources and then routing the work into different categories based on specified data attributes. The following is a list of general functional requirements that DLIS would like the tool to meet: Database Structure Database with tables and a user interface that displays information based on user profile and permissions. Capability to update business rules/permissions for workload assignment and balancing with ease. Security for internal/external users (user login, password, access, read, write, and historical). History files need to be retained for a specified time period (i.e. 6-12 months). After history timeframe has expired, files should migrate from history to archive. Archive files need to be retained in a format that is searchable and can be quickly retrieved/viewed. Beginning-to-end work request tracking with audit trail (timestamps, actions, dates, etc). The tool must be configurable (NOT CUSTOMIZABLE) by designated internal team (setting permissions, adding attributes, configuring reports, etc.). Require a method to edit business rules on-the-fly. Creation/Alteration of Work Requests Create standard submission form for entering a work request (capable of entering multiple data elements). Ability to add, change or delete data within request based on permissions. Ability to add, close or cancel request based on permissions. Capability to designate workload as open, closed, or hold status. Capability to enforce users to complete a form with predefined questions to move a request back to “hold” status. The tool shall have the ability to auto-populate certain fields such as name, number, organization, etc. within a request. The tool shall have the capability to notify the designated users when mandatory fields are left blank (e.g. when user tries to submit a new request, a window pops up to tell user if required information is missing). Workload Assignment Workflow tool will have capability to assign workload to technicians by a “first-in, first-out” based on specified criteria (i.e. due date). Capability to create business rules/predefined set of questions to be answered in order to assign a due date. Need ability for technician to request the next item in queue and need system capability to assign the next item in queue based on “closing” a work request. Tool can automatically reassign workload based on due date and technician’s availability. Ability to assign unassigned request(s) in a bucket to a user based on permissions. Capability to turn off assignment of a request based on “next in queue”. Automated assignment of system generated interim due date that will move request back to the active workbench. Ability to complete mass updates on multiple National Stock Numbers (NSNs). Reassign workload based on permissions. Assign workload based on attributes. Track individual request suspense dates and be able to notify technician of upcoming/passed due dates. If initial request is changed, workload can be auto-reassigned to the correct area. Workbench View Ability to customize workbench views (includes filtering, sorting, column manipulation, etc.). Need capability to see all items that are available in a user’s bucket (both assigned and unassigned- if assigned need to know who is working request). Reports must be generated from within the tool. Print requests. Print query results. Ability to view multiple buckets. Workload can be tracked in “hold” status while technician is waiting for additional information to complete request. Need ability to address/close multiple requests in “hold” status. Auto refresh of workbench based on pre-defined frequency Research Tool Structure Tool is a customizable work-screen with various icons depending on bucket. Templates will have required fields and data entry requirements depending on type of workload (i.e. date is mandatory and can only be entered in a Day/Month/Year format). Tool can either pre-populate or give users the option to search for cataloging tool data in request i.e.; FLIS data. External linking capability (e.g., tech data repository, vendor websites). Tool should provide the ability to perform quick and accurate searches of stored documentation. Research Tool View Receive/store/view/print attachments. Ability to tag/select data element fields that need to be added/deleted/changed and create a new screen with just those fields. Within FLIS screening, ability to display definition of codes when rolling over code. Research Tool Request Add, change, or delete data within internal request based on permissions (this includes the ability to add comments or add/change other required data based on workload type). Ability to add, close or cancel request (with permissions). Ability to generate e-mail upon request completion. Based on request submitter, generate e-mail systemically to get additional information to complete request and automatically provide request details in e-mail body (pre-populate e-mail address in e-mail). Pre-populate external data to a form that can be sent to another person to review. Reassign workload at technician/supervisor or administration levels based on permissions (this includes situations where the technician cannot work the request or where the request needs to be progressed through various processes before it can be closed). Input Tool Database Structure Pre-populate cataloging tool data within request (i.e. pull from the FLIS database or similar location which houses FLIS data). Option to automatically update screening with original incoming request data. Anytime a data element is changed/added/deleted that was not in the original request, the tool will prompt the user to add a comment explaining why the change was made (from a standard table of responses). Populate recommended effective dates, allowing for technician override. Creation/Alteration/Completion of Request Add, change, or delete data within request based on permissions. Ability to add, close or cancel request based on permissions. Ability to generate e-mail upon request completion. Ability to recognize futures data and only allow technician to update futures data (user can update current data if there is no future data on NSN). Ability to complete mass updates on multiple NSNs. Input Tool View Print requests. Drop-down menus allow user ability to type over field entry (provided the typed entry is within the drop-down menu). Data element title fields within original request are highlighted in the screening (right side of screen). Anytime a value is changed in the screening, the value is highlighted (or underlined) in a separate color (regardless of whether it was a data element in the original request or not). Within the screening, a user can roll the mouse over the data element and get the definition for that data element. 5. Technical Parameters and Background Questions (cross-referenced in Section #6, #3d) Please answer the following questions in regards to your proposed solution: 1.What are the database platform, operating system, and development standards that could be used in your proposed solution? 2.What are the hardware requirements of your proposed solution? 3.DLIS will require a minimum number of 500 users. What are the limits on adding new users in your proposed solution? How do you purchase licenses (incremental basis, one at a time, etc.)? 4.Are there any physical limitations enforced in product versions of your proposed solution (i.e. maximum number of connections, maximum size of the database, maximum number of queries/transactions, etc.)? 5.DLIS would prefer a solution that allows for self-customization. Within your proposed solution, would DLIS be able to make modifications to the code? Is a software development kit available? Provide info on applicable software licensing requirements. 6.What kind of supporting documentation is included or available for your proposed solution (user manual, administrative guide, etc.)? 7.If your proposed solution is a web tool, does the web front end run under Internet Information Service (IIS) 6.0? If not, what does it run under? Is your proposed solution capable of being compliant with Section 508 regulations? 8.What kinds of support after sale options are available for your proposed solution? 9.The proposed solution must be able to meet all applicable Department of Defense (DoD) security requirements. Is your proposed solution capable of meeting this requirement? 10.What is your background working with the FLIS system or data within the FLIS system? 6. Submissions DLIS appreciates responses from all technically capable and qualified sources. To respond to this RFI, interested parties should provide a white paper response, which will include the information outlined below. 1.Please submit one copy only via e-mail attachment to the Technical Point of Contact listed below. Page format specifications include: 12 point font, single spaced, single-sided, 8.5 by 11 inches paper, with 1-inch margins. All white papers must be written in English. All submissions must be formatted in either Microsoft Word or Adobe PDF. NO PROPRIETARY OR CLASSIFIED INFORMATION SHOULD BE INCLUDED IN THE RFI RESPONSE. 2.Cover Page a.Title b.Organization c.Responder’s technical and administrative points of contact (names, addresses, phone and fax numbers, and email addresses) 3.Technical Ideas (up to 10 pages) a.Executive Summary b.Discussion of the capability of your proposed solution c.Technical Response- Your discussion should include answers to the following: What is your proposed innovative technology? How does it address the requirements listed? d.Additionally, please address each of the questions listed in Section #5 relevant to technical questions and past experiences. 4.An optional list of citations, including URLs, if available. The anticipated place of performance for this work is negotiable within CONUS. The anticipated period of performance is to begin in February 2010 with a one-year contract with possible option years. The inspection, acceptance and Free On Board (FOB) points will be the DLIS Contracting Office Representative (COR), the DLIS Contracting Office Technical Representative (COTR) and the FLIS Program Management Office (PMO). If freight is required, it will be paid for by the contractorat destination Battle Creek, MI. Please note that submissions will not be returned. Respondents may are strongly urged to mark their submission with restrictive legends and the Government will honor those restrictive legends in accordance with existing public law and implementing regulations. RFI responses will NOT be shared with other industry suppliers and will solely be used solely as part of the acquisition planning process. The following requested information to be provided is for planning purposes only and does not constitute a Request for Proposal (RFP) nor does it restrict the Government as to the ultimate acquisition approach. The Government does NOT intend to award a contract on the basis of this RFI or to otherwise pay for the information solicited. Any contract that might be awarded based on information received or derived from this RFI will be the outcome of the competitive acquisition process. The Government will not provide acknowledgment of the number, identity or socio-economic status of responses received. THIS IS NOT A SOLICITAITON SOLICITATION ANNOUNCEMENT FOR PROPOSALS. NO CONTRACT WILL BE AWARDED FROM THIS ANNOUNCEMENT. NO REIMBURSEMENT WILL BE MADE FOR ANY COSTS ASSOCIATED WITH PROVIDING INFORMATION IN RESPONSE TO THIS ANNOUNCEMENT OR ANY FOLLOW-UP INFORMATION REQUESTS. NO TELELPHONE CALLS OR REQUESTS FOR A SOLICITATION WILL BE ACCEPTED OR ACKNOWLEDGED. COMPANY BROUCHURES ARE NOT DESIRED. Do not send any cost or pricing information with your submittal. Carefully forward your response within 30 calendar days from the date of publication in FEDBIZOPS to: DLIS-LF- Federal Catalog Division 74 Washington Ave N. Suite 7 Battle Creek, MI 49017 J6BFLISTRANS@dla.mil Replies sent in error to either the primary or secondary points of contact as listed in this FEDBIZOPS announcement WILL NOT be forwarded.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=86d66b77cca2af112d0092e8b4854e4f&tab=core&_cview=1)
- Place of Performance
- Address: Defense Logistics Information Service, ATTN: DLIS-LF/Federal Cataloging Division, 74 N. Washington Avenue, Battle Creek, Michigan, 49037-3092, United States
- Zip Code: 49037-3092
- Zip Code: 49037-3092
- Record
- SN01730197-W 20090111/090109222446-86d66b77cca2af112d0092e8b4854e4f (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 |