RFI Responses 1.xlsx
XLSX spreadsheet 22 KB Posted
- Solicitation number
- W912JB-25-Q-A039
About this file
This is a Questions and Answers (Q&A) document related to RFI W912JB-25-Q-A039 for Joint All Domain Air/Ground Systems (JADAGS) Subject Matter Expert and Training services for the Michigan Army National Guard. The Q&A addresses key operational aspects including: workload expectations of 1,338 individual hours per contractor with typically 2 contractors supporting 4-10 units annually; fully remote work except for training, planning conferences and execution; travel requirements included in workload estimates with an average of 8 hours per day for 109 days of on-site events; and surge capabilities expected during peak times without additional government funding.
The document clarifies that training priorities are equal across PWS sections 5.1-5.6, with contractors expected to provide expertise on specified systems and potential new technologies. Response times for support requests are 1 business day normally and within hours during exercise execution. Monthly reporting is required in Word format detailing units trained and RFIs addressed. The government will not provide systems/equipment - units will use their organic equipment in various configuration states. Contractor performance will be evaluated on timely responses and ability to provide adequate solutions, with proof required for uncontrollable disruptions like flight cancellations or system crashes.
View the file
Other files
Show all 11
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
| Focus Area | Question | Reasoning | Response |
| Scope and Prioritization of Tasks | Are all requirements under PWS Sections 5.1 to 5.6 considered equal in priority, or are there specific tasks the government deems critical? | This helps allocate resources effectively and ensures high-priority tasks are completed without strain. | These are all equal, determination will be made on priority of training if there is conflicting schedules |
| Can the government clarify the expected number of units to be supported annually and the anticipated frequency of MTT deployments? | This will allow for better workload and travel planning. | The overall requirement is unknown year over year, more than 4 and less than 10 is typical | |
| What level of detail and format is required for reports (PWS 5.1.1), and can templates or examples be provided to reduce preparation time? | Ensures reporting aligns with government expectations and minimizes preparation time. | Format is a word document that outlines each subparagraph 5 to include a detailed response on units trained and RFI’s addressed | |
| Are there specific milestones or deliverables within PWS 5.1–5.6 that are time-sensitive or linked to other operations? | Helps ensure tasks that are time-critical are prioritized appropriately. | Major milestone is execution – training is to be complete before with support provided during by the MTTs | |
| Staffing and Resource Allocation | Does the government anticipate that two contractors will be sufficient to meet the workload, especially during peak exercise periods requiring MTT deployments and JELC attendance? | Clarifies whether additional personnel may be needed in a surge capacity or if tasks can be reprioritized. | For training, 2 is typically enough, however, there are times when additional may be required. 1 is sufficient for planning conferences assuming communication amongst the team is adequate |
| Is the estimated workload (1,338 hours) intended to be managed collectively between the two contractors, or is it expected to represent the workload per contractor? | Confirms workload requirement per contractor for accurate pricing. | Workload is Individual. Conferences are for an individual with the total estimated hours for training and execution being for the MTT. | |
| How many systems are expected to be supported during each Northern Strike exercise (PWS 5.5)? | Clarifies resource allocation per exercise. | Total system is unknown and changes year over year | |
| Are contractors expected to support multiple units simultaneously, and if so, how should resources be divided? | Ensures clarity on multitasking expectations and resource allocation. | For training leading up to exercise, prioritization of training will be determined to avoid conflicts. During execution the team will have to support multiple units simultaneously | |
| Are any surge capabilities expected during peak exercise periods, and if so, will the government provide additional support or funding for temporary personnel? | Clarifies expectations for high-demand periods and identifies potential resource gaps. | Surge capabilities are expected, however, the government will not provide additional funding during peak surge times. The vendor will need to allocate resources appropriately to reflect peak times and lull times. | |
| Can the government clarify the anticipated ratio of on-site to remote work for contractors outside MTT deployments? | Helps manage expectations for on-site versus telework. | This position is fully remote with the exception of training units, attending planning conferences, and execution (see technical exhibit 3) | |
| Travel and Deployment | Can the government provide a detailed schedule of anticipated MTT training locations and the number of units per location (PWS 5.2)? | This helps determine the travel burden and logistics requirements. | Training locations are unknown year over year |
| Will travel expenses be reimbursed for additional travel not initially planned for? | Reduces financial ambiguity related to travel-heavy requirements. | Vendor will need to bid appropriately for travel based on anticiapted workload as outlined in technical exhibit 3 | |
| Does the government allow for remote or virtual training sessions for units unable to participate in-person? | Virtual sessions could mitigate travel risks and reduce workload. | Virtual training sessions are not ideal due to the systems being trained on, however, in extreme cases may be approved | |
| Are travel times to and from events included in the 1,338 estimated workload hours, or are they considered separate from the estimated workload? | Addresses how travel is factored into overall workload estimates. | Travel days are included for in the total estimated workload as outlined in technical exhibit 3 | |
| For on-site event attendance (109 days), are these days calculated as full 8-hour days, or is the duration flexible depending on event requirements? | Ensures accurate understanding of how on-site hours are recorded. | The in-day attendance is a mix of hours depending on the event with an overall average of 8 hours per day. Some days will be less and some more | |
| Technical Expertise and Systems Support | What specific systems are expected to be prioritized for training and operational support (e.g., Link 16, TAK, MANET) (PWS 5.2.3)? | This ensures contractors focus on the most critical and commonly used systems. | Paragraphs 5.2.3 and subsequent subparagraphs outline the various systems currently in use |
| Are there government-provided resources (e.g., manuals, training aids) to support system-specific training? | Clarifies whether contractors must develop their own training materials or rely on existing government resources. | The contractor(s) is expected to the be the subject matter expert in these areas and capable of providing the training required | |
| Does the government anticipate incorporating additional emerging systems beyond those listed in PWS 5.2.3.10? If so, can they provide notice timelines? | Mitigates risks of being unprepared for new technology requirements. | It is anticipated additional systems, as they become prevalent, will be incorporated in the required training over the upcoming years | |
| Will government-provided systems and equipment be preconfigured for MTT use, or will contractors need to perform initial setup/configuration for each deployment? | Clarifies setup responsibilities during training and exercises. | Northern strike plans group (NSPG) will not provide government provided systems. Units will have organically owned equipment that will be in various states of configuration | |
| On-Call and Reporting Expectations | What is the expected response time for on-call support requests (PWS 5.3), and is there flexibility during high-demand periods like exercise execution? | Clarifies whether contractors will be penalized for delays due to conflicting priorities. | Initial responses are required within 1 business day with the understanding that complete solutions may take longer to implement. During execution the response time is expected to be within hours as the unit and contractor(s) will be in close proximity. If there is a conflict due to multiple requests within a short time period, guidance will be provided on order to resolve with input expected from the contractor |
| Can the government define the frequency and volume of RFIs expected under PWS 5.1.2 that would increase the estimated workload? | Helps manage expectations around ad hoc requests. | As every unit will have personnel with different levels of experience it is difficult to provide an accurate estimate. Please refer to estimated number of units trained for estimated workload. | |
| Are there specific success metrics for reporting and on-call support performance, or will they be evaluated qualitatively? | Ensures clarity around evaluation criteria. | Due to the unknowns regarding RFIs and the potential range in the type of questions, metrics will be on timely responding and then the contractor ability to provide an adequate response/solution. Acceptable Quality Levels (AQLs) focus on the contractor’s ability to provide the necessary training for these units to be successful. If they are unable to provide quality/adequate response to RFIs than they will not be able to perform the training necessary for the units to be successful during the execution phase. | |
| For RFIs, will the government provide a centralized repository or platform for tracking and submitting responses, or is this expected to be contractor-managed? | Helps streamline reporting and reduces duplicative effort. | NSPG has a central link for all RFIs regarding the exercise. These will be shared with the vendor/MTT. Once in communication with a unit, it is likely the unit will ask the contractor directly questions that come up. It is the vendor’s responsibility to include these in the required monthly reports for tracking purposes. | |
| Risk Mitigation and Flexibility | In cases where simultaneous support is needed (e.g., multiple MTTs), does the government have contingency plans, or will additional contractors be required? | This ensures clear risk-sharing responsibilities between the contractor and the government. | If simultaneous support is required from multiple units than prioritization will be provided to deconflict. If additional support is required for one unit, the vendor will be required to provide the necessary personnel to ensure satisfactory training is provided. |
| Is the government open to discussing potential schedule changes or task reprioritization if the two-contractor model proves insufficient? | Creates space for contract modification to address unanticipated challenges. | Yes this discussion can take place if it is determined the current model is inefficient or ineffective. | |
| If simultaneous MTT deployments or overlapping priorities occur, does the government have a preferred prioritization process, or will the contractor be expected to determine task precedence? | Ensures clarity during potential scheduling conflicts. | Contractor input would be expected and appreciated to assist the NSPG in prioritizing. | |
| In the event of task delays due to factors outside contractor control (e.g., travel disruptions, system issues), what mechanisms are in place to document and mitigate impact on performance evaluations? | Clarifies accountability for uncontrollable disruptions. | For unforeseeable disruptions, vendor would be expected to show proof that it was out of their control, e.g, notice of flight cancellation by airline or picture/screenshot of system crash. These instances will not be held against the vendor in surveillance reports. |
File details come from the government source that posted it. Updated .