Attachment 1 RFI Response.pdf
PDF 220 KB Posted
- Solicitation number
- HT0038-24-X-XXXX
- Issued by
-
Defense Health Agency
About this file
This document contains questions from the Defense Health Agency regarding a Development Multiple Award Contract reboot solicitation. The agency is seeking responses by November 29, 2023 to inform the development of an indefinite-delivery/indefinite-quantity multiple award contract to provide software development capabilities. Specifically, the agency requests diagrams and narratives to illustrate appropriate grouping of development methodologies, talent, and pricing at the MAC level. It also asks for feedback on whether certain enabling capabilities, such as data management, should be managed under individual task orders or across multiple orders.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DevMAC Reboot_Eval Criteria_final.pdf | ||
| DevMAC Reboot_Final_v2_1.pdf | ||
| DevMAC Reboot_Final_v2.pdf | ||
| Attachment 2 RFI Respones.pdf | ||
| DevMAC Reboot_Final.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Development Multiple Award Contract (DevMAC) Reboot Request for Information
ATTACHMENT 1
The following questions are focused at informing the MAC IDIQ level.
The information requested will help inform the Government in its quest to have an ecosystem of builders with expanding capabilities to leverage the Federal Single-Record Ecosystem and drive innovation across the Health IT sector
1. How should the different types of development methodologies (aka product lines) be grouped at the MAC level? (see slide 9)
2. How should talent be grouped to support DevSecOps/DevOps Task Order levels? (See Slide 14)
3. How should talent be priced at the MAC level? (see slide #14)
4. Are there capabilities (e.g. data management, etc.) that should managed under a single task order vs multiple task orders? (see slide #20)
a. If so why? If not why not?
Request: Please provide a similar diagram as below to answer questions 1-4. It can be as simple or as complex as needed. Excluding the grouping of the different types of development methodologies (aka product lines), the remainder of the data may be specifically focused on DevSecOps product line or can expand to other product lines. If needed, a one (1) page narrative may be provided to explain the diagram provided back to the Government.
Ordered as Needed
Base Ordering Period – Lot I
Task Order 0001
0001 – PM
0002 – Travel 0003 – ODCs 0004 – CDRLs 0005 – License 0007 – S/W Maint 0009 – Int & Config
Task Order 0002
0001 – PM
0002 – Travel 0003 – ODCs 0004 – CDRLs 0006 – License 0008 – S/W Maint 0010 – IOC Deploy
Deployment Ordering Period – Lot II
Ta sk
O rd er s
Deployment Ordering Period – Lot III Award Term Ordering Period
Lot IV
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10
Notional DHMSM Task Order Strategy (Not to Scale – Illustrative Only, Not Meant to Depict Actual Task Order Timing)
Ordered by Stage
Stage TO
1001 – PM
1004 – CDRLs 1005 – License 1008 – S/W Maint 1014 – Ent Sustain
Stage TO
2001 – PM
2004 – CDRLs 2005 – License 2008 – S/W Maint 2014 – Ent Sustain
Stage TO
3001 – PM
3004 – CDRLs 3005 – S/W Maint 3006 – Ent Sust
Stage TO
3001 – PM
3004 – CDRLs 3007 – S/W Maint 3008 – Ent Sust
Stage TO
1001 – PM
1004 – CDRLs 1006 – License 1009 – S/W Maint 1015 – Ent Sustain
Stage TO
1001 – PM
1004 – CDRLs 1007 – License 1010 – S/W Maint 1016 – Ent Sustain
Stage TO
2001 – PM
2004 – CDRLs 2006 – License 2009 – S/W Maint 2015 – Ent Sustain
Stage TO
2001 – PM
2004 – CDRLs 2007 – License 2010 – S/W Maint 2016 – Ent Sustain
Ordered by Wave
Deployment TO (by Wave) 1002 – Travel 1003 – ODCs 1004 – CDRLs 1012 – Site Deploy
Deployment TO (by Wave) 2002 – Travel 2003 – ODCs 2004 – CDRLs 2012 – Site Deploy
As Needed 1011 – Ad Hoc Training 1013 – Site Eng Sup 1017 – Seg 2 Sup 1018 – Prod Improv
As Needed 2011 – Ad Hoc Training 2013 – Site Eng Sup 2017 – Seg 2 Sup 2018 – Prod Improv
As Needed 3002 – Travel 3003 – ODCs 3009 – Seg 2 Sup 3010 – Prod Improv 3011 – Transition 3012 – Ad Hoc Training
Development Multiple Award Contract (DevMAC) Reboot Request for Information
The next two questions focus around the split of the enabling capabilities available for developers to do what they do best, develop world class software.
DevX (nee: FXaaS) is the PEO 3.0 identified “solution” that would enable developers to develop software. Below are the identified enabling capabilities in DevX that the Government has identified:
Request: Given the above please provide a response (no more than one (1) page written or five (5) power point slides) for the following questions :
1. Is the above an appropriate mix of enabling capabilities or are there some capabilities that should remain with DevMAC that are currently depicted under DevX (nee: FXaaS)? (see slides
#6, #7, and #11)
2. How does the Government make it easier for developers, integrators, and all other prime contractors? (see slide #6 and #7)
Thank you for taking the time to provide responses.
Please send responses to sonya.m.edom.civ@health.mil NLT Nov 29, 2023.
mailto:sonya.m.edom.civ@health.mil
File details come from the government source that posted it. Updated .