MIOES DRFP Inc1 CONSOLIDATED QandAs.xlsx
XLSX spreadsheet 20 MB Posted
- Solicitation number
- HQ0857-MIOES-ZA
- Issued by
-
DOD Missile Defense Agency
About this file
This document is a set of Questions and Answers (Q&A) related to the MDA IT Operations & Engineering Solutions (MIOES) contract opportunity, Solicitation Number HQ0857-MIOES-ZA.
The Q&A covers topics such as the release of the conformed solicitation from the current IRES contract, which was previously controlled but is now being made available, with the exception of the outdated bidders library and property list. The document clarifies that the MIOES scope may be similar but not identical to IRES, and that the government has not yet determined the acquisition strategy for MIOES. Companies are encouraged to interact and develop working relationships as the government engages in the acquisition strategy. The Q&A also provides a point of contact, Troy Mitchell, for companies seeking additional documents from the original IRES solicitation or its amendments.
View the file
Other files
Show 40 more
Latest 50 of 77 listed here. See the rest on GovTribe.
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
Sheet1
| MIOES DRFP Increment 1 Consolidated Q&As | ||
| Question: | Answer: | Reference Document/Page No./Paragraph |
| Sub paragraph 8.2 notes a fact, "The incumbent contractor has one Associated Contractor Agreement with Lockheed Martin that aligns with Information Technology (IT) Projects." |
| Question: Can you please provide some clarity as to the scope of this agreement, relevance and impacts to MIOES contract and any associated interdependencies? | This information will be provided with the final Draft RFP. | Performance Work Statement, Page 6, Paragraph 8.2 |
| Noting Program Integration and Standards require integration across the MIOES contract (task orders) and further noting standards to communicate /report dependencies and potential impacts to the critical path across all of the appropriate stakeholders and develop Courses of Action and mitigation strategies for government approval. |
Question: Recommend that the government identify other MDA contracts on which MIOES will be dependent for successful performance and clarify any known interdependencies between them. The following are examples of other MDA contracts. The final RFP will provide a comprehensive list.
--Collaboration and coordination required with the Research and Development Collaborations Services (RECS) --Advanced Research Center (ARC) --Missile Defense Data Center (MDDC) --Agency Information Management and Software Services (AIMSS) --Technical, Engineering, Advisory and Management Support-Next
(TEAMS-NEXT)
| Performance Work Statement, Page 16, Paragraph 10.1.3, Program Integration | |
| Question: Please provide additional information on how MDA views Digital Transformation as it relates to MIOES. | 1. As stated in PWS paragraph 10.1.6, the government expects the contractor to build a digitally-empowered contract by adopting, utilizing, institutionalizing, and integrating Digital principles, technologies, standards, and practices in executing the requirements of this contract. PWS standards will reflect this thought process. We also expect these principles to be incorporated into your management and business approach and processes and don't necessarily represent a "stand alone" digital project. An example is your Data Management (CDRL) Plan and approach. The standards highlighted in the PWS direct this plan to adopt digital principles and tools. |
2. The government also expects there to be specific Digital related funded projects that will be executed throughout the life of the MIOES contract. A notional project could be, "Architect and deploy a Tier 0 Service Desk capability that leverages AI powered virtual assistants, automated knowledge base management, and automated FAQ generation to deliver self help services to MDA users."
| Performance Work Statement, Page 16, paragraph 10.1.3, Program Integration | |
| The scope table in Section 3.0 mentions that IRES TO 6100 will migrate to the AIMSS contract. | |
| Recommendation: Please provide the title and scope of TO 6100. | Title: MDA/DW Warfighter Operations Support |
| This effort will enable MDA/DW to support the Warfighter IAW MDA Goal #1 via the development and maintenance of software to enable the Missile Defense System Operational Readiness Reporting process and the Warfighter Request for Analysis (RFA), Request for Information (RFI), Request for Alliance Participation in Test (RFT), and maintenance of software. This enables the Ballistic Missile process to maximize global and regional Missile Defense System capabilities and availability to defend our nation, allies, and forward-deployed forces. | Acquisition Strategy White Paper, Page 4, Paragraph 3.0, Acquisition History |
| Para. 4 of the Acquisition Strategy states that the transition period will allow for negotiation of the "remaining task orders" that are not part of the contract award process. Phase-in PWS Section 2 states that 10 - 12 active TOs will be awarded and negotiated during the transition period. This seems to be contradictory. |
| Question: Request that the Government identify the specific awardable MIOES Task Orders the offerors will be required to price as part of the MIOES proposal submission. Request the Government identify the additional task orders which will be awarded and negotiated during Transition. | At this point only the transition/phase-in TO will be priced in the proposal, evaluated and awarded at IDIQ award. Offerors will also price a labor category table against hours provided by the government for each labor category. Paragraph 2.0 of the Phase-In PWS identifies which task orders will be negotiated during the Phase-In period. | Performance Work Statement, Page 4, Paragraph 2, Section 2.0 |
| Program Integration. The contractor shall provide comprehensive and enforceable, collaborative and agile program integration required to establish enterprise level standards in order to seamlessly execute all activities across the MIOES contract. |
Question: What are MDA's processes and tools associated with Data Normalization? MDA does have a master data catalog. MDA has a business glossary for common data terms (each 2-letter organization maintains their own for domain-specific terms). MDA is working on how to address requirements for a common vocabulary at the dept level that links to local vocabularies. Overall, data standards/governance is a work in progress for MDA.
| Tackling this MDA challenge and implementing MDA wide data strategies is outside the scope of the MIOES contact. However, the intent of 10.1.3 is to ensure the MIOES contractor will develop and execute processes and develop methodologies and tools that will enable effective data management practices within the MIOES contract. We would expect these strategies to be identified in the MIOES Management Plan that will be a deliverable under the contract and focus on what the MIOES contractor can control within the contract with respect to an overall data plan, acting within the overall MDA governance models. | Performance Work Statement, page 17, Paragraph 10.1.3, Program Integration |
| Program Integration. The contractor shall provide comprehensive and enforceable, collaborative and agile program integration required to establish enterprise level standards in order to seamlessly execute all activities across the MIOES contract. |
Recommendation: MDA enforce standardization across IT services including IM/IT services for Missile Defense System Mission & Event Operations: IT Architectures & Solutions and Information Management (IM) Solutions to better enable better measurement and enforcement for Program Integration. The Program Integration referenced in paragraph 10.1.3 pertains to the program integration "leadership" from the contractor team that will be required to ensure MIOES program level integration across the MIOES contract and establishes the governance and standards to execute from a holistic perspective at the overall contract level.
| Standardization across IT services is a requirement as well, but those standards, governance, and enforcement will occur as identified in those applicable task orders. The work associated with this integration will be charged to those task orders with this specific requirement. | Performance Work Statement, Page 17, Paragraph 10.1.3, Program Integration |
| The cover page of the MIOES Phase In TO states that the TO will be priced as FFP. |
| Question: While the Government has not introduced how it intends to define the Total Evaluated Price (TEP), recommend MDA exclude the this TO from the TEP to ensure a level competitive environment? | TEP is defined in Section M (DRFP increment 2). | Performance Work Statement (no page or paragraph reference) |
| This paragraph of the Phase-In TO states that the Government will provide facilities, equipment and access for approximately 15 people at the MDIOC in ColSpgs and the VonBraun complex in HSV during the transition period. |
| Question: Is that 15 people at each location or 15 people combined total? | There will be space for ~15 people at each location. | Performance Work Statement, Page 5, Section 7.0, Paragraph 3 |
| Strategic Data Management |
Question: Does MDA have an existing catalog of data assets? Are there current data governance processes and policies that we should align with? MDA's Chief Data Officer is developing a catalog of data assets and establish governance processes and policies. The MDA Data Strategy is to implement the 2023 Data, Analytics, and AI Adoption Strategy. That document is an iterative approach to implementing the VAULTIS concepts of the 2020 Data Strategy, 2018 AI Strategy, and "Data Mesh" Concepts such as Domain oriented / Federated Governance and Data as a Product delivery.
Data normalization and product development will take place within the domains (e.g. programs or functions contributing to the DGB) in accordance with Data Mesh principles, so 'data normalization' will likely vary from domain to domain. e.g. Financial data stewards likely have different tools to normalize data going to their reporting servers than tools and processes contracts, schedule, or engineering, or test. Each of these domains sharing data as a product (APIs, dashboards, etc.) is how we integrate across domains to create new data products. - That's basically Data Mesh 101, and what is called for in the updated 2023 DoD strategy.
MDA does have the MDA MMDC where we are doing existing data collection. We are also in the process of expanding use of the ADVANA Federated Catalog. Min metadata standards that are required for all MDA data are already incorporated into both the MDA Catalog and ADVANA.
Data management support as an Enterprise solution for the Agency is not part of the MIOES scope. Most Test Data and similar niche efforts will come from the AIMSS contract and the Data Management Specialist / App development work will come from the CoMETS contract. MIOES will be responsible for all the normal contract data deliverables associated with any contract, but MIOES contractor role in Data / Analytics and AI is infrastructure oriented.
The PWS has been updated to clarify how this requirement is focused on Strategic Contract Data Requirements Delivery List (CRDL) Data Management. The focus is on the collection, storage, and reporting of the data associated with the delivery of DD Form 1423's associated with MIOES contract.
| Performance Work Statement, Page 34, Section 10.1.7 Digital Business Strategy |
| Integration by definition is across the TOs so it needs to be defined at the Program Level. The costs associated with this task would be spread across the various TOs. |
| Recommendation: Include a reference in the table for TA 4 to PWS Task 10.1 for clarity. | TA 4 is in reference to MDIOC Facility Integration and Planning and these requirements will be identified in a specific Task Order. Paragraph 10.1 applies to all technical areas and is the management, leadership, and integration required internally to govern and manage the MIOES contract. Under the IRES contract these two requirements are combined under a single task order (TO 8002). Under MIOES, the MDIOC Facility Integration and Planning requirement will remain on a single task order managed by MDA/SSM, but the MIOES management, leadership, and integration is no longer on a separate task order but will be a paragraph on each task order and will require the contractor to determine how to spread these costs across the contract. The government will, however, appoint a Contracting Officer Representative with the responsibility to monitor performance associated with paragraph 10.1. | Performance Work Statement, Page 4, Table row "System Engineering and Program Integration" |
| On the title page of the Phase-in TO its states "6 months" |
The acquisition strategy summary says 4 - 6 months.
| Question: Will the Government please clarify the duration of the phase-in period or identify what factors will determine the phase-in period of performance. | The duration is 6 months as identified in the PWS. | Acquisition Strategy White Paper, Page 5, Second Paragraph |
| Task Area 4, MDIOC Planning and Integration cites MA and CM as work areas. These activities are also referred to under PWS 10.1 under Program Management. If TA 4 will have its own TO, there may be some overlap with 10.1 which will presumably be spread across all TOs. |
Question: Will the Government please clarify which activities properly belong under TA 4 vice 10.1. We expect MA and CM type activities to be performed on every task order. Each set of task order requirements must be properly managed within that task order and will require the contractor to have MA and DM discipline in order to execute those requirements within that task order.
| At the same time, each task order does not operate on their own disparate island and there will be MA and CM coordination between all task orders. Any MA and CM activities required to enable this cross task order coordination and collaboration falls within the scope of 10.1. Creating that culture and MIOES wide MA and CM processes, methodologies, and reporting infrastructure will occur under 10.1. | Performance Work Statement, Page 2-4, Table |
| Program Integration will be conducted at the Program Level but since it will be allocated to the TOs, it can be incentivized using CPIF contract type. |
| Recommendation: If an individual TO contract type is not CPIF, recommend the government consider alternatives to incentivize integration performed at the program level. | Those discussions are on-going within the MIOES acquisition team and will be clearly identified in the QASP. | Performance Work Statement, p.18, Note 10.1.3 |
| Recommendation: Separate Digital Transformation from the Integration task and be measured at the Program level. Additionally recommend the government allow offerors propose measurements that are appropriate to sufficiently measure impact of Digital Transformation on the enterprise. | There will be Digital Transformation implications on every task order. Standards will be developed that will require the adoption of Digital principles such as the establishment of single authoritative sources of data. |
The purpose of 10.1.6 is not for a contractor to come in and convert all legacy systems to a digital infrastructure. There is no roadmap, milestones, phases or a rollout timeline or funding to do this.
The purpose of 10.1.6 is to set the foundation and framework for this to occur. As new MIOES processes are developed and new tools adopted for integration requirements we want them to embrace, incorporate and be executed utilizing digital principles, tools, and values. We want to build a digital culture into MIOES. From this perspective, Digital Transformation is not a separate task, but represent principles woven into every requirement.
| Over time we expect digital related requirements/projects will be generated that will have a definitive start and stop, e.g. Digitize a legacy system. In the meantime if a contractor is developing a new process, ensure it incorporates digital principles and practices. For example, the MIOES contractor will be developing a data management program to manage the development and delivery of CDRLs, so we expect the incorporation of digital principles and practices into this program. Another example would be with respect to managing the MIOES integrated master schedule. Digital principles must be utilized in the collection, storage and reporting of scheduling data across the MIOES contract. | Performance Work Statement, p.18, Note 10.1.3 | ||
| Question: Does MDA have a collaboration and information sharing dashboard today? If so, please identify. | MDA utilizes numerous capabilities for collaboration and information sharing dashboards depending on the stakeholder/requirement. Some examples of tools utilized are (not all inclusive): TEAMS, Sharepoint, Jabber, PowerBI, Qlik, GitLab, JIRA, Project, Primavera, IBM Jazz. | Performance Work Statement, Page 20, Para. 10.1.6 (sixth bullet) | |
| Question: What automated engineering and business workflows does MDA have currently that supports this requirement? | MDA utilizes numerous capabilities for collaboration and information sharing dashboards depending on the stakeholder/requirement Some examples of tools utilized are (not all inclusive): Sharepoint, PowerAutomate, PTC Windchill, IBM Jazz. | Performance Work Statement, Page 21, Para. 10.1.7 | |
| Question: Does MDA currently have a master data catalog? If so, what is its completion state and can it be made available to bidders? | Reference answer to Data Management question above. The government will release as determined necessary for the development of the proposal. | Performance Work Statement, Page 22, Strategic Data Management, First Bullet | |
| Question: Does MDA expect to receive any contractor-developed solutions with no less than Government-purpose rights? | No. | Performance Work Statement, Page 21, "Strategic Asset Utilization" | |
| Recommendation: Clarify the distinction between Process Optimization/Improvement and Innovation since there is an overlap. The two can be integrated under the Innovation task or if kept separately, innovation can focus on the introduction of new technologies while process improvement focuses on existing processes. | The Innovation task will be deleted. | Performance Work Statement, Page 23, Paragraph 10.1.8 Third bullet | |
| Question: Will the Government please provide volumes and types of infrastructure, such as Window Servers, LINUX, Storage volumes? | This information will be included in the bidder's library. | Performance Work Statement, Page 4, Paragraph 3.1.2 | |
| Question: Will the government please further clarify what types of services encompass system and network management? For example: O&M? Provisioning? Engineering? | System and Network Management includes, Procurement of HW & SW, O&M, Provisioning, Engineering & Architecture (design, installation, testing & integration), Cyber hardening, patching and monitoring, testing and |
accreditation.
| Performance Work Statement, Page 4, Paragraph 3.1.2 | ||
| Question: Will the government please provide a list of current ITSM Tools and features/processes used to support the IT Infrastructure? | This information will be included in the bidder's library. | Performance Work Statement, Page 4, Paragraph 3.1.2 |
| The Acquisition Strategy states that the % of Effort is 2%. It furthers states that Systems Engineering & Program Integration (SEPI) work for MDIOC integration will be moved to the MAPSS contract. |
Question: Does this indicate that the 2% effort represents residual work not moved to the MAPSS contract? Can you clarify the anticipated work identified under the PWS TA4 requirements? Only a small portion of the SEPI work performed under IRES is migrating to MAPSS. MIOES TA4 requirements represent approximately 2% of the overall value of the MIOES contract. The PWS for work aligned to TA 4 will be released with the final DRFP. Acquisition Strategy White Paper, Page 3, Paragraph 2;
Acquisition Strategy White Paper, Page 4, Paragraph 3;
Performance Work Statement, Page 7, Paragraph 3.4 In the Acquisition Strategy, it was stated about the Systems Engineering and Program Integration (SEPI) requirements, that Program Integration requirements will be identified in each individual task order.
| Question: Please clarify if this includes the Systems Engineering requirements as well. Can you estimate the percent of effort for each Task Area, that will be cover Program Integration and Systems Engineering? | The Program Integration requirements are identified in paragraph 10.1 of the basic PWS. Each task order PWS will identify their specific SE requirements. We aren't able to identify any percentages. | MIOES Acquisition Strategy, Page 4, Paragraph 3 | |
| "MDIOC Planning and Integration will occur under a severable MIOES task order." | |||
| Does "severable" mean part of the MIOES IDIQ contract or separate from the MIOES IDIQ contract? | MDIOC Planning and Integration will be one of the task orders issued under the MIOES contract. | Acquisition Strategy/Section 3, Pg4, Table (Systems Engineering and Program Integration) | |
| Will the "Descriptions" of each Technical Area be turned into separate TOs/PWSs? | Multiple task orders will be developed from a single technical area. The only exception is TA 4 where only one task order will come from that TA. | Acquisition Strategy/Section 2, Pg2, MIOES Technical Areas | |
| What is driving the migration of some technical requirements that are in IRES to other contract vehicles (AIMSS/MAPSS/Other?) | The application of DoD IT optimization initiatives is causing the migration of some requirements away from the IRES/MIOES contracts. An example is our requirement for procuring enterprise cloud computing capabilities and services. |
On 31-Jul-2023, the DoD CIO issued memorandum “Department of Defense Joint Warfighting Cloud Capability and Next Steps to Rationalize Cloud Use Across the Department of Defense”, which directs the use of the Joint Warfighting Cloud Capability Contract for all available offerings to procure future enterprise cloud computing capabilities and services. Additionally, it directs that all cloud capabilities and services currently under contract will transition to the JWCC vehicle upon expiration of their current period of performance.
| This is an example of just one DoD optimization initiative. We expect others initiatives will be issued throughout the life of the MIOES contract. | Acquisition Strategy/Section 3, Pg4, Acquisition History | |
| Please provide more detail on how the MIOES contract will be different than the IRES contract due to: "Application of DoD IT optimization initiatives" and "Application of Category Management" principles" | See example from above of an IT Optimization initiative. |
An example of applying Category Management principles is the migration of MDA Unified Communications requirements to a single contract as identified in the Acquisition Strategy. Acquisition Strategy/Section 3, Pg4, Acquisition History Statement starts with, "Although MIOES is a follow-on to IRES, the MIOES scope is different due to the following:"
| What are the next set of TOs/PWSs that will come out with DRFP Incr 2 and Inc 3? | All task order performance work statements from the IRES contract have been posted to SAM.gov. Any task order that will have a PWS that is expected to be significantly different than what is being performed under IRES will be updated and provided in the bidder's library. | Acquisition Strategy/Section 3, Pg4, Acquisition History |
| Will the TOs being released in DRFP Inc 2/3 note all added or removed scope as compared to the IRES contract? | The government will ensure sufficient explanations are provided. | Acquisition Strategy/Section 3, Pg4, Acquisition History |
| Does the government anticipate any new TOs included with MIOES that are not currently in IRES? | Throughout the life of the MIOES contract we expect new requirements will be executed through modifications to existing task orders or through the issuance of new task orders. | Acquisition Strategy/Section 3, Pg4, Acquisition History |
| The basic PWS requires Baseline Management in all 4 Technical Areas. IRES Task Orders that will be inherited require baseline management and imply there are established and documented technical baselines and reference architectures baseline today. Question: How many baselines are there today? How are baselines documented ? How (and when) will they be provided/articulated to industry? | You are correct in saying that there are different baselines. For example, there is a MDIOC facility baseline that is managed under the current IRES Task Order 8002. There are also different baselines managed under IRES Task Order 8003. Each task order will define their requirements when it comes to managing baselines in their respective Performance Work Statements. Appropriate baseline artifacts will be released in the bidder's library. | MDA Information Technology Operations & Engineering Solutions (MIOES) Contract, DRAFT Performance Work Statement, 14 June 2024 - page 2/3 MIOES Scope TA-1, 2, 3, 4 - regarding baseline management |
| Will there be on-site Industry Day(s) so that industry teams can "walk the floors" of MDIOC, VB-III, Dahlgren MDA facility, Ft Belvoir MDA facility, and other locations, to gain an understanding of MIOES requirements, technical area baselines, and gain an understanding of the complexities and interfaces to other non-MIOESsystems/architectures? | There will only be a in-person tour at the MDIOC. Artifacts will be provided for each location and sufficient documentation will be provided in the bidder's library required to gain an understanding of the complexities and interfaces to other non-MIOES systems/architectures. | |
| This statement (in quotes) seems to contradict itself. Will there be not be a single task order or will there be a single task order? "Under the MIOES contract, there will not be a single task order for the MIOES Program Management and Program Integration task. Instead, the contractor is expected to create an “overhead/indirect” type account that collects these costs that can then be charged against each task order. Under MIOES there will still be a single task order for MDIOC Planning and Integration which covers Technical Area 4 requirements." | TA 4 is in reference to MDIOC Facility Integration and Planning and these requirements will be identified in a Task Order only containing that scope. The MIOES Program Management and Program Integration task, which is identified under paragraph 10.1 applies to all technical areas and is the management, leadership, and integration required internally across the MIOES contract. |
| Under the IRES contract these two requirements are combined under a single task order (TO 8002). Under MIOES, the MDIOC Facility Integration and Planning requirement will remain on a single task order managed by MDA/SSM, but the MIOES management, leadership, and integration is no longer on a separate task order but will be a paragraph on each task order and will require the contractor to determine how to spread these costs across the contract. | MDA Information Technology Operations & Engineering Solutions (MIOES) Contract, DRAFT Performance Work Statement, 14 June 2024 - page 14 Attachment 1 - Task 10.1 | ||
| The paragraph conveys the complexities and importance of schedule integration and deconfliction. Is there a baseline schedule that will be provided as a point of departure for proposal purposes? Is the scheduling tool/software that is used today, GFP or will the Government be looking for industry to provide their own tool for schedule integration? | The IRES contractor is required to integrate the schedules they develop under MIOES and identify non MIOES "baseline schedule(s)" that are needed for integration purposes to ensure dependencies/integration and de-confliction of MIOES scope. This schedule will be provided to the winning offeror. Project Server is the current scheduling tool/software that is utilized under IRES. It has been approved by the Authorizing Official. | MDA Information Technology Operations & Engineering Solutions (MIOES) Contract, DRAFT Performance Work Statement, 14 June 2024 - page 4 para 2.0 Scope - (regarding schedule integration | |
| What is meant by this statement? Will additional clarification of these two items be provided? "Although MIOES is a follow-on to IRES, the MIOES scope is different due to the following:" |
"• Application of DoD IT optimization initiatives" "• Application of category management principles" We were explaining the reason for why the scope will be different.
The following DoD IT optimization initiative is an example of work being removed from IRES and we expect other requirements will migrate away from IRES and MIOES over time.
| On 31-Jul-2023, the DoD CIO issued memorandum “Department of Defense Joint Warfighting Cloud Capability and Next Steps to Rationalize Cloud Use Across the Department of Defense”, which directs the use of the Joint Warfighting Cloud Capability Contract for all available offerings to procure future enterprise cloud computing capabilities and services. Additionally, it directs that all cloud capabilities and services currently under contract will transition to the JWCC vehicle upon expiration of their current period of performance. | Acquisition Strategy Whitepaper - page 4 - paragraph 3 Acquisition History | ||
| Given unspecified nature of non labor requirements, Does the Government intend to provide plug numbers for all non labor pricing elements for proposal purposes? | Yes | General | |
| Will the Government provide a list of all applicable Governance Documents (Departmental/National, Agency, Cyber, MDIOC standards and processes, and site/functional) for Industry feedback and provide documents in the bidders library? | Yes | Basic PWS/p.31/Attachment 3 | |
| Will the Government provide a list of all GFE/X/P, GOTS, and COTS products in a near term Increment release available to the MIOES contractor for execution? | They will not be part of an incremental release. It is anticipated that all non-CUI documents will be released with the DRFP. The library will be updated will any CUI artifacts when the final RFP is released. | General | |
| Given the Cloud First approach, will the Government provide any existing Cloud migration roadmaps and/or status? | The government will provide our most current roadmap and status |
within the bidders library.
| Basic PWS/p.4/para 3.1.4 | ||
| Will the Government provide additional detail on the current state of the IM and IT Ecosystem(s) (general architecture information, roadmaps etc..) | This level of detail will be provided in the bidder's library. | Basic PWS/p. 4/para 3.1.1 |
| Is MDA currently utilizing an Agile Management and associated methodology across all stakeholders? Are all tenants, systems, and enclaves leveraging the same process? | Agile principles and methodologies have not been equally adopted across all government stakeholders. Opportunities exists for tenants, systems, and enclaves to leverage common processes. |
Basic PWS/p. 17/para 10.1.5 Basic PWS/p. 16/para 10.1.3
| Can the Government provide an expected release date for the Bidders library and the projected classification level? | It is anticipated that all non-CUI documents will be released with the DRFP. The library will be updated will any CUI artifacts when the final RFP is released. | MIOES Acquisition Strategy/p. 8/para 14.0 |
| The cost reimbursement contract type is listed for non-prime contract labor. With a 40% SB goal, prohibiting prime contractors from adding any fee on the subcontracted work has significant ramifications. Would the Government please confirm that subcontractor labor will NOT be CR and that primes shall propose, be awarded and invoice fee on subcontractor labor as appropriate for the FFP, FPIF, CPIF, CPFF, CPAF or T&M contract type of the prime's TO? | The government is assessing the application of fee on non-prime labor/ODC/material. A decision will be made before final RFP. | MIOES Acquisition Strategy, Section 7.3, page 6 |
| The cost reimbursement contract type is listed for equipment, SW licenses, materials and vendor support. Would the Government please confirm that these cost elements may be proposed and awarded as CPFF type CLINs? | The government is assessing the application of fee on non-prime labor/ODC/material. A decision will be made before final RFP. Contract types will be determined for each TO and may vary. | MIOES Acquisition Strategy, Section 7.3, page 6 |
| Would the Government please release the 5 June 2023 MDA Instruction 5013.06, Source Selection Procedure document referenced in the dRFP to industry in a near term incremental release? | Yes | MIOES Acquisition Strategy, Section 9.0, page 7 |
| Paragraph “15.1 Security considerations states” “The contract will require access to classified information up to the Top Secret level, to include access to Sensitive Compartmented Information (SCI) and involve Special Access Programs.” Will the Government provide an estimated share of those personnel requiring Secret, TS, or TS/SCI clearances? | Secret -- 78% |
Top Secret -- 13%
| Top Secret/SCI -- 8% | MIOES+Acquisition+Strategy+Summary+-+24+June+DRAFT+RFP, Paragraph 15.1, Page 9 | ||
| Can the Government clarify the number of contractor personnel required to work on Government site versus Contractor and/or offsite? | The government will not dictate this. The nature of the requirement dictates whether the work can be performed on-site or off-site. The government will identify requirements that can only be fulfilled with on-site personnel. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP, Paragraph 5.1, page 10 | |
| Will the Government provide a list of required certifications (Cybersecurity workforce, Network, ITIL, etc...) and/or specialty training necessary to hold specific positions on the MIOES program? | These certifications are identified in the various directives and regulations that are referenced in the Basic PWS. We will not provide a list. Each offeror is expected to be familiar with the stated directives/regulations. | Various locations in MIOES+Acquisition+Strategy+Summary+-+24+June+DRAFT+RFP and MIOES+Basic+IDIQ+PWS+14+June+DRAFT+RFP | |
| Will the Government consider providing a forecast of acquisition documents by incremental release? | Yes, the Government will provide via SAM.gov | General | |
| Will the Government provide specific SB Socioeconomic requirements to all bidders in a near term increment release? | Yes, the Government will provide via SAM.gov and/or will include in the Basic IDIQ PWS. | General | |
| Will the Government please consider the MIOES Program Integration feedback contained in the attachment entitled, "[REDACTED CONTRACTOR NAME]_MIOES-Inc1_Notes_To_Industry_Response_Program Integration"? | The response has been reviewed and recommendations are being studied and considered for incorporation. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP Paragraph 10.1.3 | |
| Will the Government please consider the MIOES Agile Management feedback contained in the attachment entitled, "[REDACTED CONTRACTOR NAME]_MIOES-Inc1_Notes_To_Industry_Response_Agile Management"? | The response has been reviewed and recommendations are being studied and considered for incorporation. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP Paragraph 10.1.5 | |
| Will the Government please consider the MIOES Digital Framework feedback contained in the attachment entitled, "[REDACTED CONTRACTOR NAME]_MIOES-Inc1_Notes_To_Industry_Response_Digital Framework"? | The response has been reviewed and recommendations are being studied and considered for incorporation. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP Paragraph 10.1.6 | |
| Will the Government please consider the MIOES Cost Reduction feedback contained in the attachment entitled, "[REDACTED CONTRACTOR NAME]_MIOES-Inc1_Notes_To_Industry_Response_Cost Reduction"? | The response has been reviewed and recommendations are being studied and considered for incorporation. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP Paragraph 10.1.8 | |
| Will the Government please consider the MIOES Innovation feedback contained in the attachment entitled, "[REDACTED CONTRACTOR NAME]_MIOES-Inc1_Notes_To_Industry_Response_Innovation"? | The response has been reviewed and recommendations are being studied and considered for incorporation. | MIOES+Basic+IDIQ+PWS+24+June+DRAFT+RFP Paragraph 10.1.9 | |
| Page 4, Enterprise Communications & IT - states, "Unified Communications migrating to the R&D Enterprise Collaboration Services (RECS) follow-on contract." Can the Government clarify if this includes all requirements currently listed in IRES 22F8003 PWS section 10.15, including Cable Plant Management, Collaboration Services (email, chat, etc.), and Mobile Devices? | Yes, Unified communications will migrate to CoMETS and Cable plant management will remain with MIOES. |
It is anticipated that email services will be transitioned to DISA soon (possibly completed by contract award) and alternate planning is presently underway. Details will be provided to bidders as more information becomes available.
| Mobile provisioning services will remain with MIOES and Collaboration Tools will migrate to CoMETS (the RECS follow-on) | MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 4/3. Acquisition History | ||
| Section 10 indicates that after submission the Government will conduct "discussions with offerors." Is this discussion expected to be accomplished through EN/FPRs or does the Government expect a formal Orals phase for the acquisition? | Most likely EN/FPRs, but the Government is considering orals. Will be determined before final RFP. | MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 7/10.0 Acquisition considerations, paragraph 10.1 | |
| Section 13 states that the "...contractor will utilize/maintain the MDA provided Remedy system for the management of GFP and CAP." Is the expectation that the BMC Remedy system will be maintained throughout the MIOES program? We recommend the Government clarify that the contractor will utilize/maintain the MDA provided "ITSM" system to account for any future state. | Remedy may or may not be the system used under the MIOES contract. The appropriate language, as recommended, will be used when the Performance Work Statement is developed. | MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 8/13. Government-furnished property | |
| The Government states, "The contract will require access to classified information up to the Top Secret level, to include access to Sensitive Compartmented Information (SCI) and involve Special Access Programs... All classified processing/storage will be at MDA site and not contractor site." The bolded reference seems to suggest only or specifically at MDA Facilities, which precludes other locations and appears to be counter to the "cloud first strategy" cited in 3.1.4 of the MIOES Basic IDIQ PWS 14 June DRAFT RFP document. | |||
| Please confirm that DoD & GovCloud IL6/7 classified cloud services could be utilized over the life of the MIOES program? If yes, please reconcile the conflicting guidance above. | The intent behind this, is that work will be conducted from the MDA sites. There will not be a classified processing/storage requirement at the contractor site(s). |
We currently have IL6 - IL7 classified cloud services and these could be utilized over the life of the MIOES program
| MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 9/15.0 Security considerations, paragraph 15.1 | ||
| Please confirm if IT-as-a-Service capability extends to on-premise, private cloud, and/or other capabilities. | IT as a service would default to Cloud offerings where possible; on-premise where necessary. | MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 5/3.1 Global Communications & RDT&E/Enterprise Information Management (IM) Solutions & Integrated Architectures, paragraph 3.1.10 |
| Enterprise Services and Solutions, System Architecture Solutions, and Mission Assurance and Configuration Management do not appear to have requirements listed in 3.1. Can the Government align the Section 3 MIOES requirements with the sub-sections listed in the Section 2 MIOES Scope Technical Area table, with sufficient detail to describe the desired outcomes and scope of responsibility? | Paragraphs 3.1.1 - 3.1.6 cover Enterprise Services and Solutions. Additional paragraphs have now been added that create scope for System Architecture Solutions, and Mission Assurance and Configuration Management. | MIOES Basic IDIQ PWS 14 June DRAFT RFP/Pages 2, 3 and 4 to 8/2.0 MIOES Scope & 3.0 MIOES Requirements (Technical Areas 1 – 4) |
| TA4 is currently defined as a "severable" Task Order. Please define what a "severable" Task Order is within a single-award IDIQ contract. Please clarify what the intent of this approach is. | It means that there will be a separate task order under MIOES that covers TA4 requirements. | MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 4/3. Acquisition History |
| The Government states, "Integrate the TO Integrated Master Schedule (IMS) into the MIOES Integrated Schedule (IIS)," but the MIOES Integrated Schedule is not otherwise defined in this document. Please clarify the definition of the IIS. | The IIS is a deliverable under the Integrated Program Management Data and Analysis Report (IPMDAR) CDRL that is referenced in 10.1.2. | MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 29/Attachment 2 Task 10.2, 10.2.2 Task Order Measurement and Control |
| The Government states, "A schedule will be provided for proposing and negotiating the task orders. The start date [effective date] of all task orders (other than the Transition TO) will be 8 February 2027," at what point will the Government release this schedule to enable the offers to appropriately develop Phase-In plans? | This schedule will be provided in the final RFP. Several factors are being considered that could impact the number of awardable Task Orders and the schedule of awarding the remaining Task Orders within the phase-in period. | MIOES Phase-In Task Order PWS 14 June DRAFT RFP/Page 4/2.0 Background |
| The Government states, "The incumbent contractor is responsible for mission accomplishment during the transition window with the MIOES contractor responsible to assume 100% of mission accomplishment the day immediately following the transition window with no interrupted execution of the MIOES mission." This appears to be a single transition and with the MIOES contractor responsible to assume 100% of mission accomplishment the day immediately following the transition window. This contradicts the concept of a phased approach to TO responsibility turn over, described in 2.0 Background. Please reconcile and/or clarify. | The MIOES contractor will be responsible to assume 100% of mission accomplishment on day 1 following the phase-in period. The phased [staggered] approach is referring to the negotiation and award of the task orders. Task Order awards are anticipated to be staggered within the phase-in period but as stated in paragraph 2.0, the anticipated period of performance start date for all task orders will be 8 February. | MIOES Phase-In Task Order PWS 14 June DRAFT RFP/Page 4/3.0 Scope |
| The Government states, "An initial list of critical/high risk MDA activities, processes, and personnel that should be observed, understood, and coordinated to ensure a continuity of services upon contract award after contract award and before the transition task order begins is identified in Appendix A." The bolded section is confusing, please consider rewording for clarity. | Concur -- An initial list of critical/high risk MDA activities, processes, and personnel that should be observed, understood, and coordinated to ensure continuity of services on February 8, 2027 is identified in Appendix A. | MIOES Phase-In Task Order PWS 14 June DRAFT RFP/Page 6/8.0 Facts, paragraph 8.4 |
| The Government states, "The contractor will be given an opportunity to meet with each MDA organization that owns a MIOES task order for a deep dive into their requirements within the first 14 calendar days of the task order start date." It is unclear to which task order the "14 calendar days" statement refers. Does this apply to the Phase-In Task Order or is it the MIOES task order which the MDA organization owns? Please provide clarity. | It applies to the start date of the Phase-In task order. | MIOES Phase-In Task Order PWS 14 June DRAFT RFP/Page 6/8.0 Facts, paragraph 8.9 |
| Increment #1 included a "basic PWS" for review and feedback which does not yet have the same level of technical scope detail (Section 3) that the "TMR RFI Attach 2 Summary of Requirements (Technical Areas)" contained at release, dated August 2022. We request that the Government provide industry the ability to review and comment on a detailed PWS draft before the Final Draft in October 2024. | The Basic PWS released with Increment 1 is not going to have greater detail than what has been published. The purpose of the Basic PWS is to provide the general scope of the IDIQ contract. The Basic PWS is being revised to ensure the entire scope is accurately represented. | General |
| Huntsville ARC is not mentioned in the RFP. Is there a requirement for MIOES to be integrated with the ARC or vise versa? | Yes, MIOES will need to be integrated with the ARC contract. MIOES will manage the MDA Wide Area Network (U/CNET) and the ARC Contract manages the Local Area Network at the ARC (ARC MGMT/DEV/TEST). Both contracts must collaborate/communicate regularly during planning, integration, and execution of test event activities conducted at the ARC. | General |
| The % of Effort assignment is provided as a valuable reference. What does the % reflect measurement of - scope, FTEs, dollar value, etc.? | Dollar value. | MIOES Acquisition Strategy Summary 14 June Draft RFP/Pages 2-3/2. MIOES Technical Areas Table |
| MIOES Systems Engineering Scope - Please provide clarification around where the SE&I TA 5 scope now resides within the new TA makeup. To help bidders formulate better informed solutions, a more detailed understanding of where the SE&I work now resides is requested. | TA 4 covers MDIOC Facility Integration and Planning and these requirements will be identified in a specific Task Order. |
The MIOES Program Management and Program Integration task, which is identified under paragraph 10.1 applies to all technical areas and is the management, leadership, and integration required internally across the MIOES contract.
Under the IRES contract these two requirements are combined under a single task order (TO 8002). Under MIOES, the MDIOC Facility Integration and Planning requirement will remain on a single task order managed by MDA/SSM, but the MIOES management, leadership, and integration is no longer on a separate task order but will be a paragraph on each task order and will require the contractor to determine how to spread these costs across the contract.
Each requirement owner will have a different set of SE requirements and those SE requirements will be managed at the task order level. For example the MDIOC facility Systems Engineering requirements will be covered under the MDIOC Facility Integration and Planning task order. Any SE type requirements required by MDA/IC for their associated common core and RDT&E systems will be identified in their task order. Task 10.1, which applies to all task orders will require an integrated approach/processes for how the contractor will implement these SE requirements across the contract. MIOES Acquisition Strategy Summary 14 June DRAFT RFP/Page 4/3. Acquisition History, "Original IRES Scope" Table row entitled "Systems Engineering and Program Integration (SEPI)"
MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 9/4.0 Other Requirements, paragraph 4.6
| How does the requirement for a MIOES Data Catalog integrate with the MDA Agency-wide Master Data Catalog, sponsored by the MDA CDO? | There is no requirement for the MIOES data catalog to integrate with the MDA data catalog. The MIOES requirement pertains only to data that is required to fulfill the DD Form 1423 collection and reporting requirements and other business functions that require the collection, storage, and reporting of data, e.g. property reporting, cost reporting. The PWS will be modified to better explain our intent. | MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 21/ 10.1.7 Digital Business Strategy, Strategic Data Management |
| Please clarify if the Space Test and Integration Laboratory is inclusive of the Enterprise Sensors Laboratory (for BOA)? | Enterprise Sensor Lab (ESL) is an element within MDA/ BC and interfaces with C2BMC, it is the BOA environment for non-operational sensors such as HBTSS. ESL is an external supporting element for HBTSS. HBTSS will provide data to ESL for C2BMC processing consistent with above. | |
| MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 3/2.0 MIOES Scope, Item 2 in table | ||
| The Government states, "Ensure processes are integrated with each other and align with the MDIOC level plans." Please clarify what "MDIOC level plans" encompass, versus the other plans, schedules, and events throughout this section? | Examples of MDIOC level plans: MDIOC Systems Engineering Plan, MDIOC Mission Assurance Plan, MDIOC Configuration Management Plan | MIOES Basic IDIQ PWS 14 June DRAFT RFP/Page 7/3.4.1 MIOES Process Development, paragraph 3.4.1.1 |
| It appears that the Government has assigned Phase-In as a priced task. Transition costs for an incumbent performer will differ significantly from non-incumbent Offerors. To ensure a level playing field, will the Government provide a plug number OR normalize the bids by taking the average of all bidder's Phase-In price and applying it across as the plug number for all bids? | The Government is reassessing this. | MIOES Phase-In Task Order PWS 14 June DRAFT RFP/Page i/Cover page |
| Will the Government clarify what is meant by "information dissemination management" in this context? | Information Dissemination Management = Network Outages, Comms Roundable, general information sent/posted for the great MDA audience | MIOES Basic IDIQ PWS/Page 4/Paragraph 3.1.2 |
| The basic PWS requires the MIOES contractor to provide "telecommunications". How are the telecommunications required different from the Unified Communications provided by the RECS follow-on contractor? | MIOES will retain and perform cable plant services (e.g. infrastructure of cables, fiber, connectors, splices, and other components. The system that allows the transmission of data or information from one point to another). CoMETS will absorb and perform Unified Comms and Telecommunications previously performed under RECS. | MIOES Basic IDIQ PWS/Page 4/Paragraph 3.1.2 |
| Basic PWS 3.1.9 states, "Includes event requirements management, coordination, planning, architecture development, service solutions, execution support, resource management, asset management, and work activity de-confliction while ensuring full cybersecurity (Tier IIILCC) services and support.” This paragraph may be confusing to non-MDA personnel. "Event" is ambiguous and will likely be interpreted as an ITSM activity. Recommend the Government either avoid the use of the term "event" in this document when referring to RDT&E activity, or explicitly refer to each instance as a "missile test event" for clarity. | Recommendation accepted. | MIOES Basic IDIQ PWS/Page 5/Paragraph 3.1.9 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .