Enterprise Scheduling Platform (ESP)
This Request for Information (RFI) is being issued by the Defense Health Agency (DHA), Deputy Assistant Director, Information Operations (DAD IO/J-6), Solutions Delivery Division (SDD). The intent of this RFI is to research the marketplace and obtain industry's feedback on the preferences and capabilities currently defined for an Enterprise Scheduling Platform (ESP). The Government codes this market as Product Service Code (PSC) Category "D" Information Technology Services, services in the Federal Procurement Data System. DAD IO/J-6, SDD is seeking information from vendors who provide (or intend to provide) a Commercial Off the Shelf (COTS) product, capable of providing an ESP in a web-based, cloud solution for the Military Health System (MHS) in the form of a brief market research response.
BACKGROUND:
The DHA supports the delivery of integrated, high-quality health services to beneficiaries of the MHS and serves as Program Manager for acquisitions in support of the Military Treatment Facilities (MTFs). DAD IO/J-6, SDD delivers information technology solutions to the MHS through expert acquisition program management, process reengineering, integration activities and training in order to support and advance the delivery of health care to our patients.
The DAD IO/J-6, SDD is contemplating the award of a new contract to provide D-Coded Information Technology Services for the MHS in the form of an Enterprise Scheduling Platform (ESP).
The DAD IO/J-6, SDD does not currently have a single scheduling tool that provides enterprise program management allowing visibility of events that impact the MTFs. Our environment currently contains many individually maintained schedules with limited integration among shareholders. We are looking to improve the critical link in communication between DHA, J-6, the PEOs, PMOs, and MTFs through an enterprise-wide repository.
The ESP is intended to integrate the scheduling of all major IT events in the Military Health System and provide a/an
Clearinghouse for all HIT Scheduling
Enterprise-wide repository
Hub for interactive booking
Customized dashboard views
Scheduling events to be included in the ESP are as follows:
Deployments
Upgrades
Decommissioning
Inspections
Governance
Information Assurance
Military Construction Projects
Training Schedules
Facility Updates
IT Lifecycle Events
FUNCTIONAL & TECHNICAL REQUIREMENTS:
The functional & technical requirements defined thus far:
Performance Objective
Functional Requirements Requirement (R) Optional (O)
The system shall be comaptible with (or capable of replacing capability) tools in the existing SDD ecosystem:
The system shall be capable of importing and exporting native MS Project files, while recognizing all constraints used in MS Project and maintaining full data integrity R
The system shall be capable of importing XML documents R
The system shall be compatible with MS Sharepoint O
The system shall be capable of managing and displaying calendars based on user-based role and assigned profile location. R
The system shall facilitate effective and targeted communications and collaboration amongst SDD staff:
The system shall include capability for effective top-down communication to SDD staff R
The system shall include capability to facilitate communication and collaboration within project team R
The system shall include role-based electronic alerts (email or mobile compatible) R
The system shall support end-user customization/configuration of alert preferences (to include triggers, threshholds, etc.) R
The system shall have a customizable level of detail in the alert to notify end-user of change (e.g. task ID & name, previous date, current date, source of slip, etc.) R
The system shall include the capability of allowing document storage (MS Office & PDF Documents) R
The system shall provide for the capability to store and provide direct linkage to URLs O
The system shall include schedule management capabilities:
The system shall support the planning, scheduling, and control of large-scale programs and individual projects R
The system shall support the creation of hierarchical schedule portfolios, to include the grouping of projects into PMO portfolios and the grouping of PMO portfolios into an enterprise portfolio R
The system shall import and export custom data fields R
The system shall facilitate the standardization of custom data fields across the enterprise with import and export capability. R
The system shall be capable of creating dependencies (cross project) within portfolios and across the enterprise (cross project) R
The system shall be capable of producing Gantt chart reporting capabilities anywhere throughout the system. R
The system shall provide a clearinghouse for all MHS IT scheduling events that directly orindirectly impact the MTF. R
The system shall provide customized enterprise views of schedules to include IT events, dependencies and risks. R
The system shall include portfolio management capabilities:
The system shall support the application of common project governance, controls, and workflows O
The system shall support the identification and prioritization of projects that best align with organizational strategy O
The system shall support the identification and prioritization of projects that maximize the impact to mission O
The system shall include resource management capabilities:
The system shall support resource monitoring across the enterprise O
The system shall include capability to resource load and level across projects, portfolios, and the overall enterprise O
The system shall be capable of resource trend analysis O
The system shall include a financial module allowing for the tracking of budgets for each program O
The system shall include risk and issue management capabilities:
The system shall support the identification and tracking of project and portfolio risk across program lifecycle O
The system shall support the integration or mapping of project risk data directly to project schedule data O
The system shall facilitate the quantitative analysis of schedule risk with respect to project, portfolio, and enterprise level critical paths O
The system shall include task management capabilities:
The system shall support the management of tasks and task lists outside of MS Project O
The sytem shall support the integration and/or mapping of external task lists to existing project schedules O
The system shall include Business Intelligence, Reporting, and Dashboarding capabilities (ad-hoc and role-based):
The system shall include standard and ad-hoc role-based reports to increase visibility across the enterprise R
The system shall support the in-house development of customized reports to monitor project and portfolio performance R
The system shall support the in-house development of customized end-user dashboards to provide project and portfolio level decision support R
The system shall support the in-house development of project performance data visualizations R
The system shall support the query and export of project or portfolio performance data in MS Office compatible format to support additional ad-hoc analysis R
The system shall allow users to build customized reports based on type of events, location of events and time of events with the ability to drill down for detailed information R
Technical Requirements
The system shall meet the following application requirements:
The system shall include a web-based application R
The web-based application shall be compatible with current DHA image versions of IE, Chrome, and Firefox R
The web-based application shall not rely on DHA non-compatible third-party software (i.e. Java) R
The system shall manage credentials and employ role-based permissions R
The system shall utilize DOD CAC/PKI or PIV authentication R
The system shall support simultaneous read/write capabilities for multiple users on a project R
The system shall have a native comprehensive help tool functionality covering basic processes with the added capability for custom help topics R
The system shall have interactive help functionality to assist in the performance of common tasks R
The system shall include error messages with sufficient detail to support end-user troubleshooting R
The system appearance shall be customizable with organizational logo and information R
The system shall meet the following network & hosting requirements:
The system shall be hosted, at minimum, in a FEDRAMP Level 2 certified environment R
The system shall be capable of meeting DoD/DHA RMF IA standards R
The system shall have an anticipated availability of 98% or better if hosted by vendor R
The system shall be highly responsive with minimal latency issues (XX ms threshhold) R
The system shall meet the following data storage requirements:
The system shall ensure data is available in an Oracle or SQL (or compatible) database R
The system shall include capabilities to allow SDD to backup and restore project data R
The system shall include extensible storage capabilities to accommodate future programs/projects R
Missed Requirements
The system shall have change history audit trail capability such that changes made can be identified by the date, time, and user making the change R
The system shall have the capability to assign, maintain, compare and archive multiple schedule baselines per project schedule or across the enterprise R
The system shall have the ability to trace multiple critical paths across multiple schedules by actively calculating the Total Float/Slack between tasks R
The system shall support Status Date or Data Date capability allowing end users to 'status' or 'progress' the % Complete of an activity to where it should be based off a planned end date R
The system shall facilitate a proposed change process workflow that enables socialization of updates from the Project Teams to the SDD Stakeholders through formats including, but not limited to, Dashboard Reporting R
The system shall facilitate the development of schedules in a draft format before being published R
The system shall not have duration limitations for tasks, Projects, Programs, or Portfolios R
The system shall prioritize Project Schedule tasks over MTF scheduled tasks through the calendar views R
The system shall provide conflict resolution methods to include: but not limited to; calendar functionality, proposed changes, and what if scenarios to deconflict scheduling overlaps and cross-project dependencies R
The system shall have the ability to ingest and align to the monthly DMIS ID table update (Excel format) R
The system shall have the ability to upload and manage Functional Area process Models or Templates to be used for reference or initial schedule development R
The system shall be capable of producing a report to include a customizable Gantt Chart R
The system shall allow for the management of data fields by the end user administors R
The system shall be compatible with Agile based tools, such as Jira O
These requirements are a continued work in progress and may need to be refined as possible solutions are identified.
GOALS OF THE RFI:
• Gain knowledge on common business practices available for integrating Information Technology (IT) scheduling needs
• Understand existing best practices to improve defined requirements
• Identify existing software solutions that can meet the capabilities and requirements as defined
• Understand budgeting requirements needed for this type of solution
The RFI is designed to assist the DHA in building an effective strategy that will consider preferences and capabilities found in the Information Technology marketplace. This market research effort is part of an ongoing PSC Category D service acquisition process. Information captured from this RFI will only be used for market research and participation is voluntary.
REQUEST FOR INFORMATION RESPONSE INSTRUCTIONS:
The intent of this RFI is to conduct Market Research in accordance with FAR 10.002 and FAR 15.201. It is for informational purposes only. This RFI shall not be construed as a formal solicitation or an obligation on the part of the government to acquire any supply or service. It does not guarantee a solicitation will be issued. Costs associated with any submission shall not be reimbursed by the government.
If your company is interested in providing information about its capabilities, common business practices, and preferences, please SUBMIT RESPONSES TO RFI VIA EMAIL TO NORA.L.CROSSAN.CIV@MAIL.MIL. DO NOT SUBMIT RESPONSES VIA TELEPHONE. TELEPHONE CALLS TO PROVIDE QUESTIONS, COMMENTS, RECOMMENDATIONS OR RESPONSES WITH REFERENCE TO THIS NOTICE WILL NOT BE RETURNED.
Nora L Crossan, Acquisition Lead - South, Phone 2103106149, Email nora.l.crossan.civ@mail.mil
