The file's text, extracted by GovTribe without its formatting.
Request for Information (RFI)
Army Publishing Directorate
Version 1.0 Date: 11/19/2014 Table of Contents
General 3
Background 3
Introduction and purpose of the RFI 3
Statement of High-Level Business Requirements 3
High-Level Functional and Non-functional Requirements 4
RFI Submission Details 9
Proposed Strategy 10
Submission of Information 10
Disclaimer 11
General The Army Publishing Directorate (APD) is conducting market research to determine the availability and technical capabilities of vendors that can meet APD’s Lifecycle Management System and software requirements. APD requires a Lifecycle Management System and software for processing and managing Army publications and forms. The system will bring together all data and content management processes in a secure, indexed, and searchable repository. The workflow will manage and facilitate all stages of APD’s processes from initial request through completion and hosting online. Finally, the software will format and edit documents.
Background APD manages Army departmental publications and the electronic publishing process, including the lifecycle management of departmental forms and printing, in accordance with Army regulation (AR) 25-30. APD designs, builds, operates, maintains, and sustains the technology platforms and applications necessary to accomplish its mission.
· The APD Portfolio consist of: 17,000 active publications and 3,000 forms
· The APD annual workload is: 2,000 print requests, 1,800 publications and forms publishing actions The APD website is www.apd.army.mil.
Introduction and purpose of the RFI THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Army is not at this time seeking proposals. Respondees are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.
Statement of High-Level Business Requirements Edit Tool: A commercial off-the-shelf (COTS) software application capable of indentifying editorial and content consistency errors in electronic documents.
Format Tool: A commercial off-the-shelf (COTS) or government off-the-shelf (GOTS) software application capable of formatting Department of the Army (DA) administrative publications, to include but not limited to, Army regulations, DA pamphlets, DA General Orders, Army directives, and DA memorandums.
Lifecycle Management System: A commercial off-the-shelf (COTS) software application capable of:
· Content Management - Provides storage of large files securely through a managed check-in/check-out process for all types of files.
· Database - Provides a robust database solution.
· Compliance & Discovery - Provides an analysis on data maintained on the system.
· Process & Workflow - Provides a mixture of ad-hoc and structured workflow with the ability to track and monitor work in progress. The workflow will be adaptable for quick changes.
· Reporting - Provides a robust ad-hoc Graphic User Interface (GUI) reporting capability, which can be implemented as part of the user’s inbox/dashboard screen and/or web page.
· Search - Provides a robust searchable capability within the metadata and content residing in the system.
· Security - Provides compliance with Department of Defense security policies, to include Common Access Card (CAC) authentication for access, when required.
The Lifecycle Management System shall be robust, user friendly, easily customizable, and easily modified by user administrators rather than information technology (IT) staff. Workflow and task specifics change frequently and the system needs to be able to easily accommodate these changes without involvement of IT personnel; although IT support may be needed to assist user administrators who make changes infrequently. The system shall have a dashboard and dynamic reporting functionality to allow for various levels of detail. User administrators shall be able to customize a dashboard to meet their various levels of permission requirements.
Performance Services: Contractor shall provide support for development, integration, implementation, and operations and maintenance (O&M) of system in a .mil environment. Government will provide network and hardware.
High-Level Functional and Non-functional Requirements
| Requirement Name |
| Functional Requirement Statement |
| Edit Tool |
| Application shall scan documents for punctuation and grammatical errors and identify content inconsistencies within documents. |
| Edit Tool |
| Application shall produce a report detailing identified errors and inconsistencies, and allow user to make document-wide corrections. |
| Edit Tool |
| Application shall allow for customization/modification of style sheets and addition of specific editorial and consistency rules to align with Government Printing Office, Department of Defense, and Department of the Army requirements. |
| Format Tool |
| Application shall integrate with Microsoft Word as a macro add-on and seamlessly apply XML tagging and document structure requirements in a “what you see is what you get (WYSIWYG)” approach. |
| Format Tool |
| Application shall guide users through document construction, in a step by step method through final formatting. |
| Format Tool |
| Application shall create an XML source file (all figures, tables, and other associated files will be inclusive of the source file. |
| Format Tool |
| Application shall export the XML source file to portable data file (PDF) and other formats (mobile device or eBooks) as required. |
| Format Tool |
| Application shall validate content against official databases (for example, acronym and term databases). |
| Format Tool |
| Government personnel shall be able to make customizations/modifications to the XML style sheet within framework of the application without contractor support. |
| Format Tool |
| Application shall provide users a function that creates a print preview for standard word processing (i.e. Microsoft Office) and exports figures, tables, and associated files on demand. |
| Format Tool |
| Application shall have role based functionalities. |
Lifecycle Management System
| Content Management |
| Application shall provide import/export functions. |
| Content Management |
| Application shall provide version control processes and archival functions. |
| Content Management |
| The system shall make the information available securely and efficiently at every phase of its life cycle. |
| Content Management |
| The system shall have version control capabilities. |
| Content Management |
| The system shall provide the capability to manage published web content. |
| Content Management |
| System shall implement Records Management Policies, to include functions to execute those policies. |
| Content Management |
| The Content Management software shall provide ability to migrate content. |
| Content Management |
| System shall have the capability to check-in/check-out content. |
| Content Management |
| System shall provide for a robust and highly customizable foldering structure (i.e. "parent child relationship"). |
| Process & Workflow |
| The system must support process modeling and workflows, and facilitate routing (Business Process Management - BPM). |
| Process & Workflow |
| System shall have the capability to send emails ad-hoc and/or automatic. |
| Process & Workflow |
| System shall be able to handle workflows that must address new or unique solutions on demand. |
| Process & Workflow |
| System shall provide capabilities for monitoring work in progress (customizable dashboard). |
| Process & Workflow |
| System shall be able to allow for analysis capabilities on historical data. |
| Process & Workflow |
| System shall be able to provide the ability to facilitate participation in business activities that are associated with the content which can trigger pre-defined actions, rules and conditions to enable automation in workflows. |
| Process & Workflow |
| Individual inboxes shall provide sorting and filtering capabilities. |
| Process & Workflow |
| System shall provide workflow management capabilities which include inboxes, work object routing, group queues and process tracking. |
| Process & Workflow |
| System shall provide an internal accounting tool. |
| User Interface |
| The software shall provide user interfaces that can access the content and the process flows. |
| User Interface |
| It shall provide the capabilities to view the content repository. |
| User Interface |
| It shall provide user interface for process management items such as queues, step processors and inboxes. |
| User Interface |
| It shall provide input, Presentation and Output services as the way to collect, capture, archive various sources of contents in the Content Management system utilizing the display and interface supports for the users and applications. |
| Compliance & Discovery |
| System shall provide capabilities of indexing and classifying analysis. |
| Compliance & Discovery |
| System must be able to expand beyond traditional content lifecycle management capabilities and incorporate the decision making as an integral part of the APD mission and operation. |
| Reporting |
| System shall provide investigation tools and reports to facilitate auditing and business intelligence. |
| Reporting |
| System shall provide structured and ad-hoc reporting. |
| Reporting |
| Reports shall be exportable in pdf or excel format and other files types as required. |
| Reporting |
| Reports shall be a graphical representation within the dashboard capabilities. |
| Reporting |
| Reporting capabilities shall provide drill down functions for further detailed data analysis. |
| Database |
| Database will be robust enough to provide workflow data and content metadata. |
| Database |
| Contractor shall integrate existing databases into Lifecycle Management System. |
| Search |
| Robust search capabilities for all metadata and content within the Lifecycle Management System System. |
| System |
| The system shall provide automated synchronization (export/import) with other systems identified on a daily basis. |
| System |
| The Content Management system shall provide an area for testing and developing application such as forms and other applications related to APD core mission such as process, application, for, object and design. |
| Requirement Name |
| Non-functional Requirement Statement |
Performance
| Lifecycle Management System (Reporting) |
| System reporting shall update at a minimum of every 24 hours. |
| Lifecycle Management System (System) |
| Industry standard for response time. |
Compatibility
| Edit Tool |
| Application shall be compatible with current and future upgrades of Microsoft office products. |
| Edit Tool |
| The application shall supplement current Microsoft Word review functions (spelling and grammar). |
| Lifecycle Management System (Content Management) |
| Application shall be compatible with existing storage software applications currently used. |
Security
| Security Service Content Management |
| The integrity and confidentiality of the data must be provided from acquisition to disposition. |
| Security Service Content Management |
| The foundation of Content Management software must provide data services and storage services that include the integrity, encryption and other related functionality to ensure data protection at the data layer. |
| Lifecycle Management System (Content Management) |
| Levels of access and check-in/check-out capabilities. |
| Lifecycle Management System (Security Service) |
| Security Services include modules for identity management, perimeter, and security models. |
Availability
| Lifecycle Management System (System) |
| System shall be accessible anytime and anywhere within industry-standard applications (i.e. internet browser with access authentication). |
Location/Hardware
| Lifecycle Management System (System) |
| System will reside on a government managed network (.mil environment). |
| Lifecycle Management System (System) |
| System data will reside on a government managed hardware. |
| Lifecycle Management System (System) |
| System will be developed and maintained in a virtual environment. |
| Lifecycle Management System (System) |
| Contractor shall provide test, development and production environments on a .mil provided network. |
| Lifecycle Management System (System) |
| Contractor shall develop COOP for implementation on government managed secondary network. |
Licensing
| Edit Tool |
| Approximately 200 licenses will be required for use within Army Publishing Directorate (25 licenses) and through Headquarters, Department of the Army (175 licenses). |
| Format Tool |
| Application shall not have a license restriction and be available to all of Headquarters, Department of the Army principal officials and Commanders of Army commands. |
| Lifecycle Management System (System) |
| Approximately 50 licenses will be required for APD personnel only. |
Maintenance and Support, Training, etc.)
| Edit Tool |
| Contractor shall provide maintenance and updates through an annual operations and maintenance contract. |
| Edit Tool |
| Contractor shall provide on-site application training to Army Publishing Directorate staff. |
| Edit Tool |
| Contractor shall provide training material (video- and manual-based) and update material annually. |
| Lifecycle Management System (System) |
| Contractor shall provide training material for Lifecycle Management System system (video- and manual-based) and update material annually. |
| Lifecycle Management System (System) |
| Contractor shall integrate Lifecycle Management System Solution with APD's website. |
| Lifecycle Management System (System) |
| Contractor shall develop system to work with both CAC-enabled users and non-CAC users. |
| Lifecycle Management System (System) |
| Contractor shall provide development & integration of system requirements and annual O&M. |
Lifecycle Management System
| System |
| The solution shall be compliant with the Joint Technical Architecture Army (JTA-A). |
| System |
| The solution shall be compliant with Army Data Management Standards. |
System
The solution shall be compliant with the Army Public Key Enabling (PKE) Standards.
| System |
| The solution shall be compliant with the DoD Public Key Infrastructure (PKI) Standard. |
| System |
| The solution shall be compliant with the Section 508 requirements of Part 28 U.S.C. |
| System |
| The solution shall be compliant with Army Regulation (AR) 25-1, Army Information Management. |
| System |
| The solution shall be compliant with AR 25-400-2, The Army Records Information Management System (ARIMS). |
| System |
| The solution shall be compliant with AR 340-21, The Army Privacy Program. |
| System |
| The solution shall be compliant with AR 380-5, Department of the Army Information Security Program. |
| System |
| The solution shall be compliant with AR 380-19 or AR 25-2, Information Systems Security. |
| System |
| A Certificate of Net-worthiness (CON) as directed by the Army CIO/G6 in the Army net worthiness Program Policy Guidance, dated 2 July 2003, will be required before this system can connect to any Army network. |
| System |
| The solution shall be compliant with the applicable Army and DoD policy and requirements standards and specifications. |
| System |
| The solution shall support the following for authenticating users onto the system: DoD Common Access Card; single sign on from the Army Knowledge Online (AKO); and user id and password authentication via the central AKO LDAP directory service. |
RFI Submission Details This is a request for information only. Do not submit a proposal or quote.
The Government's suggested approach is to obtain information from vendors via a standardized vendor product demonstration and a capabilities statement. Interested vendors must provide capabilities statement prior to their vendor project demonstration.
Primary vendors with the capability of meeting high-level requirements may be invited to provide an on-site demonstration of the functional capabilities between 16 – 22 December 2014. Demonstrations shall not exceed 2 hours.
Capabilities Statement shall include:
· Business name and address
· Name of company representative and their business title:
· Phone number and email address of representative
· Type of Business
· DUNs number and Cage Code
· Proposed Contract Vehicle if any (Example: GSA, Army CHESS, etc.)
· Capabilities statement demonstrating their ability to supply and perform the services as listed in the requirements herein. Responses should specifically describe the vendor’s ability to meet the requirements as outlined in the RFI.
The Capability Statement must also include detailed answers to the following questions:
1. What is your company’s experience specific to lifecycle management of integrated systems?
2. What is your company’s experience specific to content and data management, hardware, software development and improvement, design, implementation, integration, interfacing, installation, life-cycle replacement, technical support, and operations and maintenance?
3. Based on list of the requirements, would your company propose for this effort as a prime contractor performing at least 51% of the work? Would you plan to team with subcontractor(s)? If so, describe the subject matter and approximate percentage of work that your company would be likely to perform as a prime contractor. Describe how you would manage a suite of subcontractors for this type of contract.
Proposed Strategy The Government intends to review all submissions received in response to this RFI. Firms may be requested to submit information in the form of an on-site demonstration with a panel of Government representatives and in written form in response to the request for additional functionality (see Functional and Non-functional Requirements).
Submission of Information Vendors who wish to respond to this RFI should send responses via email NLT 10:00 AM (Eastern) Friday, December 12, 2014 to yoon.s.song4.civ@mail.mil. Vendors should submit a Capabilities Statement Package of no more than 10 pages, formatted in Times New Roman, 12-point type, single spaced (Microsoft Word or .pdf attachments are preferred), 8-1/2 x 11” pages, with 1 inch margins.
All vendors shall be registered in SAM (www.sam.gov)
Vendors are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to vendors with respect to the information submitted.
The Army will evaluate the responses to help identify interest and the ability to provide support in the areas outlined in this RFI. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this notice that is marked PROPRIETARY, will be handled accordingly. Proprietary information will be safeguarded in accordance with applicable government regulations. The Government shall not be held liable for or suffer any consequential damages for any proprietary information not properly identified. Responses to the notice will not be returned and respondents will not be notified of the evaluation.
Primary Point of Contact:
Yoon Song 9301 Chapek Road, Building 1456 Fort Belvoir, VA 22060-5527 Phone: 703-614-3765 Email: yoon.s.song4.civ@mail.mil
Secondary Point of Contact:
Julie Marshall 9301 Chapek Road, Building 1456 Fort Belvoir, VA 22060-5527 Phone: 703-693-1499 Email: julie.a.marshall12.civ@mail.mil
Disclaimer THIS SOURCES SOUGHT IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A REQUEST FOR PROPOSAL. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO HTIS ACCNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY.
3 | Page image1.png