Operational Medicine Service Support for Training, Deployment and User Adoption

**Update** August 19, 2021 The program office appreciates prior responses on this requirement. Based on those responses, the program office is refining its requirement and there will be more to come in the future on this acquisition. Please continue to monitor the HIVE and sam.gov for updates on this acquisition. **Update** May 14, 2021 As we continue to plan the acquisition for this work, I have more questions for you. If you are an interested vendor in this requirement, can you provide feedback on whether you believe that a single vendor should manage this requirement? Essentially, is it possible for a single vendor to provide Services training, helpdesk support, exercise support, deployment to the Services and user adoption analysis for JOMIS? If you think the different areas included in this contract lends itself to a multiple award IDIQ construct? Which GWACS interested vendors have established contracts on? Which GWACS Industry believes may be leveraged for this requirement? Finally, I have included a DRAFT list of Contract Data Requirement List (CDRL) in the OpMed Service Support Folder in the Resources section to provide further context on the extent of this requirement. I am interested in Industry's feedback on the number, type, and content of deliverables that may be submitted in response to these CDRLs. As always, the format is inconsequential. We will start looking at feedback on these questions and CDRLs on May 25, 2021. Please send feedback to dha.ncr.co.mbx.jomis-contracting@mail.mil. **Update** May 12, 2021 Thank you all for the responses to this Statement of Objectives! I did a cursory review of the responses, and JOMIS is conducting a more detailed analysis-- but the one thing that jumped out is that there seems to be Industry consensus that this requirement should be separate and apart from the TMIP-J Sustainment effort. Suppose any vendors did not provide feedback on this requirement but are interested in this requirement. Can you please provide feedback by the end of the business day on May 17, 2021, on the preference for JOMIS to pursue this requirement separately from TMIP-J Sustainment or whether it would be more helpful to join these two requirements into a single contract? Industry responses to this question could have a significant impact on the acquisition strategy for this requirement. Please please send your feedback to dha.ncr.co.mbx.jomis-contracting@mail.mil. Thanks everyone! ** Update** April 30, 2021 So, I have received feedback on this requirement. There is confusion about the distinction between the Theater Medical Information Program-Joint Sustainment effort and the Operational Medicine Service Support for Training, Deployment, and User Adoption effort. As of right now, these are two separate efforts, and I am trying to gauge if they should remain that way. Currently, the posted Statement of Objectives for the Operational Medicine Existing Capabilities- Service Support and User Adoption is the high-level objectives for a potential requirement involving OpMed training, user adoption, and deployment support. The goal of this requirement is to provide the Services (Air Force, Army, Marines, Navy) the needed support (training, deployment, and user adoption) for JOMIS-developed software. The potential requirement for Operational Medicine Service Support for Training, Deployment, and User Adoption is different from the TMIP- J Sustainment. The TMIP-J sustainment work will be solely dedicated to maintaining the TMIP-J software information system per JOMIS's direction. Conversely, the goal of the Statement of Objectives for the Operational Medicine Existing Capabilities- Service Support and User Adoption is to provide training, deployment, and user adoption for all JOMIS-developed software that may potentially be released to our Service stakeholders. While this may include TMIP-J and its future iterations, it will also support new software such as MedCOP, Theater Blood, and other JOMIS applications that may be in the works. The goal of the Operational Medicine Service Support for Training, Deployment, and User Adoption effort is to find a JOMIS partner that can provide this necessary support to ensure that the OpMed capabilities are effectively deployed to and actually used by the Services. The JOMIS partner that may be selected to provide this service will fill a vital role in supporting the Services in fully understanding the capabilities of the JOMIS-developed software and demonstrating the benefits of this software so that it is regularly used. As I stated previously, there is no format for responses to the Statement of Objectives. My goal in releasing this information is to gauge interest in this requirement and whether the information included in the Statement of Objectives is sufficient for an organization to develop a Performance Work Statement for a competitive acquisition. Feel free to provide this feedback in an email, a tabulated list, a white paper, PowerPoint. The format is inconsequential- I just want Industry's thoughts on this one. Please monitor this conversation on the HIVE as we continue to release information on this requirement. Main JOMIS Page: https://hivegov.mobilize.io/main/groups/46682/lounge Verified Registration: https://hivegov.mobilize.io/registrations/groups/43511 Anonymous Registration: https://hivegov.mobilize.io/registrations/groups/43575 **Original Message** April 26, 2021 Please review the attached draft Statement of Objectives for a potential upcoming Joint Operational Medicine Information System (JOMIS) program office requirement. As background, JOMIS is currently assessing its deployment and training for its operational medicine systems. JOMIS is considering whether there is the market capability to support a combined training, deployment, and user adoption requirement. JOMIS is in the very early stages of acquisition planning for this requirement, and this is our initial communication to Industry regarding this requirement. JOMIS does not have an approved acquisition strategy for this requirement, and that means that the following determinations do not exist: Whether this will be a full and open acquisition or a small business set aside Whether this will be a definitive contract or an indefinite-delivery contract Which contract types will be used The solicitation timeline JOMIS is in the initial market research phase and is collecting intelligence on this requirement. The information collected now will influence the acquisition strategy and any future decisions on the areas mentioned above. Regarding the Statement of Objectives, JOMIS is seeking feedback on whether they need to clarify some areas to give Industry better insight into what JOMIS is seeking. To that end, please review the draft Statement of Objectives and provide your initial thoughts and comments on this requirement and advise whether you believe enough information has been provided for your organization to develop a Performance Work Statement to address the included objectives. In terms of a deadline for comments on the Statement of Objectives, there is not one. Please provide your feedback when you are ready. However, JOMIS will continue with its requirements development and acquisition planning activities, and if you submit your feedback too late, JOMIS may not consider it. JOMIS will not start its review of SOO feedback until May 10, 2021. If you have Statement of Objectives feedback that you would like considered, please send it to dha.ncr.co.mbx.jomis-contracting@mail.mil. As I said earlier, we will not start looking at it until May 10, 2021. Please join the HIVE to monitor future conversations as we continue to release further information on upcoming competitive opportunities. Main JOMIS Page: https://hivegov.mobilize.io/main/groups/46682/lounge Verified Registration: https://hivegov.mobilize.io/registrations/groups/43511 Anonymous Registration: https://hivegov.mobilize.io/registrations/groups/43575