IAGSC Industry Day QA.docx

IAGSC Industry Day Q&A Q: For development, are there any technical areas for fourth and fifth gen systems that SW is focusing on?

A: Principally simulations, mission system integration, hardware-in-the-loop, data links, sensors.

Q: What is the current situation for task orders the team is focused on and how are those anticipated to grown and change?

A:Focused on JSE currently,ith a desire to scale. There is not an infinite budget, but infinite requirements.

Q:What is the current task order bid process? And what will it look for the MAC?

A: The current process follows the typical RFP, Proposal, Technical evaluation order. At the MAC, we are still deciding how the task orders will be structured. We are considering per project, per team, blended concepts with possible teaming arrangements. Likely we will be releasing a supplemental PWS for each task order, with the requirement for the proposal to be bid to the specific elements of the supplemental PWS.

Q: What problems or challenges are being inherited? Are there technical problems or service challenges? Anything else inherited?

A: The biggest thing being inherited is the contractor-government teaming arrangement. One benefit of working closely with Government is that everyone is on the same page every day.

Typical challenges in this realm, but we have good documentation, not a lot of dead code. No severe issues to be inherited.

However, there are challenges across the software directorate. Modern infrastructure here locally (WPAFB) but not the case across all directorate locations.

Some of the projects cross security classifications, which can present difficulties.

Some of the other risks include scaling to meet demand, bringing aircraft into simulated environments, technical complexity increasing, integration risk is high, as well as personnel risk in being able to be cleared and perform at the high level necessary.

Continuous staffing can be a problem.

Q: How do you anticipate the work being parsed out?

A: Software development is the largest piece, then in-house services, cybersecurity and physical security.

Q: How can we enable and support to ramp in for roughly $150M annual budget? How do we write a proposal to possibly fit 40-80% of the work?

A: Bid to your strengths. It is not requisite to propose to all components of PWS. We are looking at how to possibly split the work to allow companies to propose to their strengths and perform that work.

Q: Will this be utilizing new or existing infrastructure?

A:SWX has modern infrastructure, cloud-based infrastructure. There is a combination of legacy development systems, and applying modernized wrapping for legacy systems where possible. More modern development environment at WPAFB, more legacy across some of the other locations.

Sometimes there may be the requirement to stand up new environments. Occasionally there may be the requirement to stand something up, then tear down, with a new ATO each time.

Q: How firm is the staffing at WPAFB? Can it be located at another cleared facility?

A: Vast majority of on-site work performed on Government systems. Other software groups will likely require on-site support as well.

Telework or remote work not applicable to this vehicle.

Q: For the labs being sustained currently, can you tell us more about what we would be doing?

A: Core service and plug-ins for JSE, following design paradigm developed with Navy. Scalability of our CUI development system. Image generation, mixed reality for simulation technology. Development Floor. JSE integration lab, integration tests, regression, fault testing, Dome system image generation (IG) systems, stand-alone enclaves, Line Replaceable Unit (LRU) Sustainment.

Currently approximately 35-40 developers, can expand to roughly 100 without increasing infrastructure.

Collateral level lab of 6-8 people which contains Dome System, IG, with cockpit simulator systems.

Across the directorate, there are 4-8 development networks, trying to consolidate to smallest number that makes sense.

Q: Will most of the work support real-time simulation and hardware in the loop (HITL)?

A: Most of the current work is real-time simulation, although there is some interest in faster than real-time if necessary.

Q: You mentioned OPS research, can you expand what skills you are looking for?

A: OPS Research tool, JSE, AFSIM, interested in pursuing more space.

Q: Do you have a sandbox for these environments? What is the process for fast development?

A: Currently have a sandbox to test open-source software, cyber requirements are necessary. We are always looking to bring in best tools.

There is a demilitarized zone to test, and to bring authorizing official to evaluate whether it is necessary.

Q: What is the training piece of TT&Ps?

A: SMEs for TT&Ps like kill chain, we have developers that are awesome at software development, but they are not pilots. We bring in active operators to consult for quality of software and discuss.

SMEs allow us to produce a better product.

Systems engineering support is helping to derive requirements breakdown of what is required for project.

The TTP is training people on how the systems works and how the software works. Also includes training of junior developers.

Q: How many awardees will be on the MAC?

A: Likely that it will come down to capabilities. We do not have an established max and min. Anticipating that draft RFP will have a rough estimate. At this point we are anticipating more than five.

Q: What is the greatest risk to getting award? What is the upside to winning the award? The timeline for ramping is difficult to retain and deliver quality people to fulfill requirement.

A: We understand the difficulties of staffing a competent team to do what we do every day. We anticipate that as a top risk to get qualified staff spun up on this project.

As far as the upside, there is opportunities for growth, getting involved in a lot of other projects and labs as other centers (SW locations) come into play.

Q: Under current administration, has use of existing IDIQs been considered?

A: We have and continue to look at existing vehicles such as OASIS+, will look at VAULT and ASTRO among other vehicles. Expect a formal decision to be released in the future.

One difficult consideration is that this contract will use Earned Credit Hours, and many existing MAC IDIQs do not allow for EHC.

Q: How much of a sticking point are data rights? What’s the appetite for previously developed IPs?

A: The expectation is unlimited rights for developed software.

COTS licenses are procured for necessary systems and integrated software. There is the potential to use existing software depending on project.

Q: What will the material requirement be?

A: There will be a small amount of material procurement.

Q to KTRs: How is the environment for teaming arrangements? Traditional prime with subcontractors?

A: Largely depends on the evaluation criteria. Could be decided at task order level if so chosen.

One-on-One Q&As Q: How will the coding challenge be evaluated?

A: Likely that it will be a pass/fail. The metric will be whether it can be completed or not.

Q: What is the organization like and how does it function? What is the management approach?

A: We are considering releasing a high-level org chart that shows how we are set up. The management approach has to be flexible to meet requirements as they change.

Q: As far as meeting objectives, are there any issues with staffing? What is the hardest position to fill?

A: There is a hiring backlog and the hiring freeze is impacting the ability to fill those positions. The hardest position is to find the person with the necessary skillset and time to train on frameworks in place.

Q: Is the training requirement on the government or the contractor?

A: Government performs DevSecOps training and is looking into possible internships to train government people.

Q: What do the development cycles typically look like?

A: Highly variable by project, dependent on the lab and platform, but we do follow the Navy release cycle for JSE.

Q: Will key personnel or key positions be a factor in selection?

A: Required experience could be defined at task order level for specific tasks or projects.

Q: Are you still in market research phase?

A: Yes, we are still in the market research phase, Q: How many people are necessary to be a prime?

A: No perfect answer, depends on the task order, but there is not a strict limit.

Q: How long will the overlap period be?

A: For the basic MAC, the overlap period is anticipated to be six months. On task orders, the overlap period will be significantly less than that.

Q: At what security classification will the proposal be?

A: The highest classification for the proposal will be controlled unclassified information (CUI).

Q: What are the typical security levels for projects?

A: Secret SAR, TS/SCI Q: Will an initial task order be awarded at the same time as basic?

A: There will be an initial task order awarded, with additional task orders to follow shortly after.

Q: What will the roles of Tinker, Robins, and Hill be for the MAC?

A: JSE has support at all locations, software development occurs at all sites, then additional support for specific programs at those operating locations.

Q: Are you anticipating needing personnel at the other operating locations?

A: It is likely that personnel will be needed at the locations issuing the task orders. There is a possibility of blending to use people at Wright Patterson.

Q: What types of image generation are being utilized?

A: Heavily using Aechelon, less so in Subr Scene Q: Based on the needs described during the general session, what else is missing?

A: We face some challenges on ancillary functions, retention, etc. Software development is an outstanding aspect, but admin can present challenges.

Q: What level of workload is expected to come from other SWEGs?

A: There is a high level of interest from other software engineering groups, typically they range around 100 FTEs short for their existing workload. There is a solid business case to augment government employee with contractor workforce.

Q: What is the modeling software used for?

A: Model aircraft for simulators used in Pilot in the Loop (PITL). Also used for real world data links used with models. Also used for systems integration.

Q:How is integration used in this effort?

A: Mostly integrating software systems & software systems design.

Q: Is the decision to use NAICS 541511 firm?

A: The preponderance of the effort will be software development, so this will likely be the NAICS used.

Q: Regarding pricing, what is being considered for sections L & M?

A: We are not decided on this portion yet. Possibly labor categories & professional compensation plans will be evaluated.

Q: For the coding challenge, can existing code be provided?

A: At this time, we are considering providing a modeling and simulation framework, then asking to complete a basic challenge commensurate with scope.

Q: What will be the priority for evaluation on MAC?

A: Technical will be the heaviest weighted.

Q: How did personnel management become a factor.

A: Due to using working capital funds, vacancies cost us money, so retention and management is highly important.

Q: Will the first task order cover the entirety of the incumbent’s work?

A: Currently undecided how the incumbent’s workload will be divided and how that will be parsed out on task orders.

Q: How long are task order proposals expected to take?

A: We are anticipating a 30 day proposal turn for task orders.

Q: What amount of new software will require the use of EAAGLES framework?

A: No clear answer, but it will still be used as necessary and applicable.

Q: PWS does not mention automation, ai, etc. Will this be included?

A: Likely to be used for autonomous training programs.

Q: What roadblocks are you hoping to resolve through use of a MAC?

A: Mainly spreading out risk by having a larger pool of people, helps to eliminate bottom-line issues.

Q: Is the incumbent performing all work or how is the team structured?

A: We use a blended team of contractor and government personnel.

Q: Is the bulk of work standing up new or sustaining systems?

A: Principally capability development. Not done at scale, first to develop then scale later at broader SW level.

Q: What type of contract is anticipated?

A: Cost plus fixed fee to begin, then over time it is likely to move to some FFP.

Q: How many task orders on average will be placed annually?

A: Unsure at this point, more info will become available as we get closer to RFP release.

Q: Will the first task orders mainly support SWX at Wright Patterson?

A: Likely the first task orders will be the incumbent work at SWX, may be split up into a few task orders.

Q: If the projects are split up to several task orders, would the government be the integrator?

A: Yes, the government would be the integrator. There are pros and cons, if split, it allows for more flexibility but also increases the complexity for administration.

Q: Will the task orders be 12 months long?

A: The intent is to fund 12 months at a time, due to funding regulations for severable services.

Q: A concern with 12-month task orders is that it can be counterproductive to constantly be going through proposals and evaluations. How can this be mitigated?

A: We are planning on making the evaluations quicker and easier at the task order level to offset the 12-month period of performance. Still looking at potential pitfalls from these concerns you raise.

Q: What is the anticipated timeline for proposal development.

A: For the MAC, we are still garnering feedback on what industry needs in order to complete proposal preparation.

Q: Regarding flexibility, are you looking to ramp up and down on this contract?

A: Yes, we will likely maintain the ability to ramp up or down depending on need and to maintain competition on MAC.

Q: Is the draft PWS released prior to this predicted to be representative of the actual PWS?

A: There will be some updates and new information based on the results of this industry day and how it molds our acquisition strategy, but not likely to be a large departure from what is currently on the PWS.

Q: It can be difficult to attract and retain quality software developers for this type of work. Does this increase the probability of badge-flipping on this effort?

A: Splitting FTEs or multiple task orders could make it less likely to have badge-flipping occur. Each task order will be a tradeoff where technical is the heaviest weight evaluation criteria.

Q: Is the government going to perform code reviews on work completed under task orders?

A: Not in a typical fashion. Our delivery is more akin to agile development. We do continuous delivery on government systems.

Q: Is artificial intelligence and machine learning an area of interest for SWX?

A: Yes, we are trying to incorporate Language Learning Models (LLMs) against frameworks to help developers go faster.

Q: What is the travel requirement likely to be?

A: There is significant travel to training sites and super sites.

Q: What are the material requirements?

A: The material requirements are fairly small, typically just tech refreshes.

Q: Are there any commercially available off the shelf products available to fulfill your needs?

A: Sometimes it is not cost effective to integrate those systems, renew licenses, etc. We are mainly focused on infrastructure, and we have the infrastructure to perform.

Q: Is spin-up time an issue?

A: Yes, but is more about administrative burden than technology, for example, filling out paperwork.

Q: Will there be small business set-asides?

A: We are still deciding on this, but we are leaning to full and open. There will be a small business requirement for all task orders.

Q: Are extended reality and virtual reality capabilities being used?

A: They are not currently used for research and development, more for application and integration of VR into existing systems, and we used mixed reality for training purposes.

Q: What type of funding will be used on this?

A: We will be using working capital funds.

Q: Will each prime be required to have an information systems security manager (ISSM)?

A: Currently there is an ISSM in place, but this would be defined at the task order level for that effort.