MODIFICATION
70 -- Intranet creation and migration to appropriate and DoD-Compliant Content Management System (CMS)
- Notice Date
- 10/18/2017
- Notice Type
- Modification/Amendment
- NAICS
- 423430
— Computer and Computer Peripheral Equipment and Software Merchant Wholesalers
- Contracting Office
- Defense Logistics Agency, DLA Acquisition Locations, DLA Contracting Services Office - Richmond, 8000 Jefferson Davis Highway, Richmond, Virginia, 23297-5000, United States
- ZIP Code
- 23297-5000
- Solicitation Number
- RFI-18-R-5315
- Archive Date
- 5/31/2018
- Point of Contact
- rachel l keener, Phone: 8042794362
- E-Mail Address
-
rachel.keener@dla.mil
(rachel.keener@dla.mil)
- Small Business Set-Aside
- N/A
- Description
- This is a request for information (RFI) for the Defense Contract Audit Agency (DCAA) located at Fort Belvoir, VA seeking vendors' proposed solutions, relative to NAICS code 423430 having the skills and capabilities necessary to provide intranet design, architecting, development, and implementation services. This Request for Information (RFI) is for planning purposes only and shall not be considered as an invitation for bid, request for quotation, request for proposal, or as an obligation on the part of the Government to acquire any products or services. Responses to this RFI will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this announcement or the Government use of such information. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. The contractor shall provide intranet design, architecting, development, and implementation services at the Defense Contract Audit Agency (DCAA) located at the McNamera Headquarters Complex, 8725 John J. Kingman Road in Fort Belvoir, VA 22060. This is not a solicitation, but a request for information only to determine the availability of services and market pricing for the service requirements. Responses need to include a Rough Order of Magnitude (ROM) of the cost. The information provided may be used by the DCAA, Office of Information Technology as a requirement for intranet design, architecting, and development services, in developing its acquisition strategy and statement of work/statement of objectives and performance specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. The Government does not intend to award a contract on the basis of this RFI or to otherwise pay for the information submitted in response to this RFI. Please reference the RFI # in your response. Responses must be submitted to the email address listed on the Primary Point of Contact by the closing date/time of the announcement. Statement of Work for DCAA intranet creation and migration to appropriate and DoD-Compliant Content Management System (CMS) Overview DCAA is currently operating a hand-coded, nearly 17-year-old mixed-technology intranet that supports approximately 300 locations and nearly 5,000 employees worldwide. Development of this intranet was performed mostly in plain html and Classic ASP and managed through the use of Adobe DreamWeaver. The current intranet system contains in excess of 20 micro-applications that leverage Microsoft Access databases as their back-end data store, and more than 200,000 web pages/files. In addition to this system, DCAA also seeks to combine content and applications currently built with Microsoft SharePoint 2010 into one common solution. These SharePoint capabilities include custom lists, static pages, custom workflows, Access data stores and reporting, and document libraries. This project must emphasize compliance with Department of Defense cybersecurity requirements, cybersecurity web inspection requirements, Section 508 requirements, the Open Technology Development Roadmap, and the Federal Source Code Policy. Out-of-the-box CMS functionality and configuration must be used unless unavoidable to achieve desired business outcomes or meet regulatory requirements. Project Note: Before starting this project, the vendor must study the current DCAA intranet and DCAA intranet modernization requirements through active participation in stakeholder meetings, requirements gathering and analysis, conducting content inventory, preparing system design specifications, and creating diagrams using the DoD Architecture Framework (DoDAF). •1. Analysis of existing content, applications, and databases This project has three associated content types: •1. Static Content - Organizational Charts, web page text, images, etc. •2. Collaboration Content - Document Libraries, Project Management Sites, etc. •3. Applications - Dynamic data sourced primarily from Access databases, with input forms and reporting features and workflows Analysis of existing content must be performed to determine an appropriate data structure, governance, and information architecture for the modernized solution. •2. CMS architecture and design DCAA seeks, as part of this RFI, recommendations for which technical platforms conform to DoD and Federal requirements, to include records management, that are widely used throughout industry for intranets. These recommendations should strongly consider the Federal Governments Open Technology Development Roadmap, industry trends and widely successful implementations, and total lifecycle cost. DCAA content should be standardized to the greatest extent possible to deliver a consistent "look and feel" across the new solution. A robust search capability must be delivered that leverages appropriate meta-data tagging and information architecture best practices. User Experience (UX) Design is expected to have high priority and be supported by strong user-centered design and appropriate testing. Branding and graphics should be included in the effort. DCAA seeks a homogenous environment for content management where content owners, without the assistance of IT professionals, can manage content in a structured and governed manner. Content across organizational boundaries should be simplified, disposed of if no longer needed, consolidated, and organized into common content structures for the entire organization. Static content should be managed through an appropriate and highly user friendly interface. DCAA collaboration needs must be assessed and met with a right-sized long-term sustainable solution with minimal overhead costs. Collaboration needs include, but are not limited to, sharing documents, use of shared calendars, task lists, and temporary sites to support strategic initiatives. •3. Migration of static content After inventory and analysis of existing content is performed, new governance procedures and policies should be created to establish effective and sustainable management and oversight of content. DCAA seeks to empower business units to maintain their own content without the need for technical skills. Migration of content should be done in partnership with the business units, training may be needed and is within scope of this project. •4. Architecting and implementing collaboration needs DCAA seeks to establish a robust collaborative environment for employees. This would include, but is not limited to, the ability to establish shared calendars, task lists, automated notifications, and document repositories with version control and collaboration features. Users should be able to provision these resources and assign permissions as needed through a controlled and highly governed process without the need for IT professionals. DCAA seeks recommendations of other employee performance enhancing functionality common across industry for intranet systems. •5. Migration or re-creation of several web applications Legacy functionality may need to be modernized, recreated, or even decommissioned. Possible items may include document libraries and their associated functionality (search within doc library, sortable columns, alerts when content is added, web services, custom lists, etc.), tracking systems, policy repositories with alert features, employee lookup, policy/memorandum databases, input forms, etc. Each will be evaluated for migration to the new intranet or passed to the Software Development and/or Business Integration team for evaluation and transition into a more appropriate system if needed. •6. Implementation Services Responses should address implementation tasks that emphasize a smooth organizational transition from the legacy state to the future state described in the response. Such tasks include, but are not limited to, planning, documentation, governance, and training. •7. Roadmap Beyond Initial Redesign Responses should address approaches for sustaining and extending the redesigned intranet to avoid a recurrence of the current state. Such responses should align with the organization's overall business and IT strategies and technological roadmaps. The DCAA 5-year Strategic Plan can be found at http://www.dcaa.mil/Home/StrategicPlan.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/da9e306b412e5032ee8383100505c10a)
- Record
- SN04717008-W 20171020/171018231337-da9e306b412e5032ee8383100505c10a (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 |