Transcription

Request for Solutions (RFS)Immersive Training Environment (ITE) Prototype Project02 August 2021Amendment 011. Purpose and AuthorityThis Request for Solutions (RFS) is seeking vendors for an Other TransactionAuthority (OTA) agreement, for the Immersive Training Environment (ITE) PrototypeProject. The Government will evaluate the solutions with the intent to competitivelyaward one or multiple Other Transaction (OT) Agreements for prototype projectsthrough the Training and Readiness Accelerator (TReX) vehicle, in accordance with10 U.S. Code § 2371b.2. Summary and BackgroundSince 2007, the United States Marine Corps (USMC) has been utilizing InfantryImmersion Trainers (IITs). While these systems provide adequate training for theirintended purpose, there are training scenarios within the IITs that require theemployment of Role Players. Upon analysis of these scenarios, the USMC believesthere are instances where these hired actors or Role Players can be replaced bycomputer generated entities while still providing valuable and essential training. TheUSMC would like to issue an OTA Prototype Project for an Immersive TrainingEnvironment (ITE) capable of supporting an innovative solution that would eitherreduce or eliminate the use of these Role Players in various training scenarios.The IIT currently provides high-fidelity fixed immersive training environments withenhanced battlefield realism including exposure to operational complexities, mentaland physical stresses, and challenging ethical decision-making. The IITs alsoprovide realistic training with Role Player Support Services. This training requires theemployment of Role Players to serve as Foreign Language Specialists, Civilians onthe Battlefield (with linguistic and cultural accuracy or background), general RolePlayers who would fill the role of insurgents, terrorists, embedded foreign commandstaff/military/police units and other personnel encountered in the intended theater ofoperations. However, there are times when human Role Players may not beavailable.The USMC is seeking ITE capabilities designed to meet contemporary and futuretraining requirements that adapt as changes occur in the operational environmentwith hardware and software Computer Generated Forces (CGF) technology that willenable the USMC infantry team leader to reinforce decision-making skills and After1

Action Reporting for Commanders. The CGF should be able to create high fidelitysimulations primarily Shoot no Shoot scenarios with the purpose to train Marines forthe ever-changing realities of the 21st century. The CGF will provide the buildingblocks for creating tactical simulations requiring more than one entity.The CGF should meet Live, Virtual and Constructive objectives: Live - A simulation involving real people operating real systems. Militarytraining events using real equipment are live simulations. Consideredsimulations because are not conducted against a live enemy. Virtual - A simulation involving real people operating simulated systems.Virtual simulations inject a Human-in-the-Loop into a central role byexercising motor control skills (for example: flying jet or tank simulator),decision-making skills (for example: Shoot no Shoot, committing fire controlresources to action), or communication skills (for example, as members of aMarine Corps Special Operations Command team). Constructive - A simulation involving simulated people operating simulatedsystems. Real people enhance such simulations but are not involved indetermining the outcomes. A constructive simulation will be a computerprogram. For example, a military user may input data instructing a unit tomove and to engage an enemy target. The constructive simulationdetermines the speed of movement, the effect of the engagement with theenemy and any battle damage that may occur. These terms are not to beconfused with specific constructive models such as CGF, a generic term usedto refer to computer representations of forces in simulations that attempts tomodel human behavior and human/systems interactions.The CGF is one of the Family of Systems (FoS) that provides realism within the ITE.This feature is a Key Performance Parameter (KPP) for the ITE. CGF allows units toconduct essential tasks in a replicated contemporary operating environment. Arealistic environment sets the conditions to create both tactical and ethical dilemmasfor the Marines. The development of a realistic environment (live, augmented orvirtual) and associated scenarios are integral to the successful creation of an ITE.This prototype project is unclassified.3. General Information3.1. Vendors interested in responding to this RFS must be members of theTraining and Readiness Accelerator (TReX). Information about membership can befound at the following webpage: https://nstxl.org/membership/2

3.2. The cost of preparing and submitting a response is not considered anallowable direct charge to any Government contract or agreement.3.3. An individual vendor may not submit more than one solution in response tothis RFS as a Prime. A vendor may participate as a subcontractor to multipleresponses. Additionally, the Government will consider and accept partial solutionsfor this requirement.3.4. Non-compliance with the submission instructions provided herein maypreclude the vendor from being considered for award.3.5. Government participants and advisors, both Government and Contractorpersonnel, in the evaluation process and will be required to sign non-disclosureagreements (NDAs), as well as ensuring the procedures are in accordance with 41U.S.C. 423, Procurement Integrity Act.3.5.1. Advising Contractor Support Staff: Alaka’ina Foundation Family ofCompanies, 12565 Research Parkway, Orlando FL 32826; CAGE Code 4C108.4. Government Furnished Information (GFI)/ Government Furnished Property(GFP)4.1. The Government will make immediately available, upon RFS release, theAttachments listed in Section 10, for use during solution preparation.4.2. All hardware and associated technical information provided to the vendor asGFI/Government Furnished Equipment (GFE) is anticipated to be ControlledUnclassified Information (CUI).4.3. Upon award of the project, the Government anticipates the distribution ofControlled Unclassified Information (CUI) related to the ITE effort as Distribution D.The Government anticipates this project to be classified at the UNCLASSIFIEDlevel. All hardware and associated technical information provided to the vendor asGFI/Government Furnished Equipment (GFE) is anticipated to be ControlledUnclassified Information (CUI).The Government will provide the vendor with Security Classification Guides (SCGs)related to the technology developed under the ITE effort, to ensure that classifiedinformation is not inadvertently created by the vendor during execution of the project.Please refer to the following link for more information on DD/issuances/dodm/520001m vol1.pdf?ver 2020-08-04-092500-2033

The Government intends to provide additional GFI to the awardee within 15 daysafter award of agreement.4.3.1. Vendor Vetting: The vendor is required to complete and submit, with theirsolution, the Vendor Self Vetting Form (Attachment 08).4.4. Furthermore, vendors must provide a list of all Government FurnishedInformation (GFI) / Government Furnished Equipment (GFE) that the vendorbelieves is critical to enable development and demonstration of prototype. TheGovernment cannot guarantee that all GFI / GFE requests can/will beaccommodated.5. Solutions Paper Responses5.1. Solution Paper responses shall consist of one volume to include anAdministrative, Technical, and Price section. Responses shall be submitted in aneditable/executable (not scanned) Word/Adobe PDF format. The Technical sectionis limited to no more than 10 standard size (8 ½” X 11”) pages for the total volumecount using standard 12-point Arial font. No more than 3 foldouts are allowed with apage size of 11”x17” and will be counted towards the 10-page limit. Please note,each one-sided page will count towards the page count limit. Charts or figures arenot bound by the 12-point font requirement but shall be clearly legible. If the solutionexceeds the page limitation, the Government may choose not to read anyinformation exceeding the 10-page limit and the information may not be included inthe solution evaluation.SectionSubsectionFormat**Countedtowards pagelimitYesGeneralTechnicalPriceNoCover PageMS Word/PDFXNontraditional StatusMS Word/PDFXFOCI StatusMS Word/PDFXOCI & Mitigation PlanMS Word/PDFXSub-Vendor ListMS Word/PDFXVendor ExperienceMS Word/PDFXProject ManagementMS Word/PDFXSolution PaperMS Word/PDFXGovt Desired Rights inTech Data & Computer SWAnticipated DeliveryScheduleMS Word/PDFXMS Word/PDFMS Project/PDFXExcelXSchedule (POAM)Pricing Breakout4Page Limit*No Page Limit10-Page LimitXNo Page Limit

Rough Order of Magnitude(ROM)ExcelX*The Administrative and Pricing Sections along with the cover pages Sub-Vendor List,Government Desired Rights in Technical Data and Computer Software, List of Figures, Plan ofAction and Milestone (POAM)Delivery Schedule, GFI List, Section 889-Telecommunicationsand Representations, and Acronym Definitions do not count towards the page count limit.**All PDF’s will be editable (not locked).5.2. Administrative Section (unlimited page count)The following shall be included in the Administrative Section: Cover PageNontraditional statusForeign Owned, Controlled or Influenced (FOCI) statusOrganizational Conflicts of Interest and Mitigation Plans5.2.1. Cover PageThe cover page shall include the vendor’s name, Commercial and GovernmentEntity (CAGE) Code (if available), NAICS Code, Business Size, Traditional or NonTraditional status, address, primary point of contact, and status of U.S. ownership.NAICS code for this effort is 541330.5.2.2Nontraditional StatusThe vendor shall provide its nontraditional (see paragraph 5.2.2.1 for definition)business status or its ability to meet the eligibility requirements of 10 U.S.C. §2371b.The vendor shall check one of the following boxes – with appropriate justification ifneeded.There is at least one nontraditional defense contractor or nonprofit researchinstitution participation to a significant extent in the project.All significant participants in the transaction other than the FederalGovernment are small businesses or nontraditional defense contractors.At least one third of the total cost of the project is to be provided by sourcesother than the Federal Government.If the vendor is not a nontraditional defense contractor (NDC) additional informationis needed. Vendor shall provide the name and CAGE code information for the NDCparticipating in the prototype project. Additionally, the vendor shall provide whatportion of the work the NDC is performing and an explanation of the significance ofthe NDC’s contribution to the prototype project.5

5.2.2.1 Definition of Nontraditional Defense Contractor – an entity that is notcurrently performing and has not performed, for at least one-year period precedingthe solicitation of sources by the Department of Defense (DoD) for the procurementor transaction, any contract or subcontract for the DoD that is subject to fullcoverage under the cost accounting standards prescribed pursuant to 41 U.S.C§1502 and the regulations implementing such section.5.2.3 Foreign Ownership, Control, or Interest (FOCI) StatusIn accordance with RFS Attachment 2, Security Process for Vetting Contractors, thevendor must include certification that the vendor (and subcontractor(s)) are notForeign Owned or under USA FOCI status (and are not in merger or purchasingdiscussions for a Foreign company or USA FOCI Company). Should a prospectivevendor be unable to so certify, they will be ineligible for award unless the mitigatingcircumstances in Attachment 2 Security Process for Vetting Contractors are met. Insuch a case, these mitigating circumstances shall be detailed in an appendix to theAdministrative Section.5.2.4 Organizational Conflicts of Interest and Mitigation PlanVendors will submit an Organizational Conflict of Interest (OCI) Mitigation Plan viaan appendix to the General Volume. In the event there are no real or perceivedOCIs, simply state so and annotate what actions would be taken in the event thatone is realized.5.3. Technical Section (10-page count)The following shall be included within the Technical Section: Sub-Vendor ListVendor ExperienceProject ManagementSolution PaperGovernment Desired Rights in Technical Data and Computer SoftwareAnticipated Delivery SchedulePlan of Action and Milestone (POAM)5.3.1. Sub-Vendor ListVendor shall provide a list of all sub-vendors involved and their role within theperformance of your submission as an appendix (which will not count towards thepage count). The list shall include FOCI status and OCI.5.3.2. Vendor ExperienceVendor shall describe their company or team’s, recent and relevant previousexperiences developing and deploying an e-learning system similar to the required6

work of this prototype project. Projects worked in the last three years are consideredrecent.5.3.3. Project ManagementVendor shall describe their company’s methodologies, organizational structure,quality assurance processes, and staffing they intend to use to manage thisprototype project.5.3.4. Solution PaperSolution Paper responses shall include the vendor’s proposed technical solutionclearly describing the approach, feasibility and technical risks and mitigationsolutions identified in fulfilling the Project Technical Objectives and associateddeliverables identified below. The approach shall clearly address planneddocumentation deliverables (including format and content) and any planneddemonstrations, design reviews (including product line quality factors such as agilityand reuse), feasibility of implementation, total project risk, and management reviews.5.3.5. Technical Objectives of the ProgramThe PM TRASYS ITE prototype project goal is to design, develop, test, andpotentially field a successfully completed CGF capability prototype. The ITEanticipates a materiel solution that has the ability to support hands-on small unitpractical training in immersive realistic and complex scenario-based trainingenvironments. The following information is intended to support vendor solutionresponses that will support Marine Corps Systems Command’s desire for asuccessfully completed CGF capability prototype. If necessary, and dependent uponsolutions received, the Government may determine to implement an Initial OperatingCapability (IOC) milestone. If implemented, the IOC will be considered a baselineallowing the vendor to further mature the technology and materiel solution.The ITE prototype project has a primary goal to replace up to 15 live actors whereappropriate. The ITE seeks solutions enabling CGF to support culturally diversetraining scenarios, generate these scenarios through a scenario generator, andprovide an After Action Review (AAR). These CGF will replace the traditionalactor(s) in real-world scenarios for both individual and collective training. Thistraining will need to cover an array of requirements to include decision-making andjudgement, rules of engagement, building entry, and room navigation and clearing.All training will need to be able to be conducted in realistic, culturally appropriatesettings and executed in both day and night along with an array of weatherconditions. PM TRASYS is open to additional ideas and approaches. However, allsolutions must, at a minimum meet and support system performance for real-timetraining standards such as 1080p at 30 frames per second (fps). The ITE is intendedto be able to be used at any deployment site and must be able to represent realisticentities (i.e. projections, augmented or virtual reality, holograms, etc.).7

For the ITE to deliver high-performance, real-time, realistic training, there areminimum requirements that must be met in the near-term. Each incremental deliverycycle will include several phases as defined in the RFS. Each cycle will includedesign, development, and test phases where some cycles and/or phases will requirefielding and delivery for user tests and feedback. Vendors will propose cycles withappropriate phases for incremental prototype capability deliveries and testing thatinclude milestones attached to payment plans.It is Government’s intent to support an iterative approach towards attaining thefollowing required objectives:Operational System Objectives: Provide participants with realistic battlefield audio and visual cues forweapon effects, atmospherics and CGF Virtually demonstrate adaptable environment to support operations acrossRange of Military Operations Allow Marine Corps Ranges to fully support pre-deployment training cyclesin anticipation of operational deployments Provide high-end training venues that replicate modern battlefields forrealistic led training exposure Provide simulation-based models (for example: projection, augmentedreality, holographic or other) to impact human senses for combat immersion Allow the ability to adjust training levels in varying degrees of competenceand complexity for the benefit of training units Administer the ability to track, model and simulate interactive environmentsfor participants Interface with existing AAR capabilities Ability to create and control training scenarios for training applicationpurposes Provide a training environment with realistic battlefield terrain formultidisciplinary user interaction Adaptable to support application of kinetic and non-kinetic responses incombat simulation Flexible in rendering three-dimensional (3D) computer generated images inaccordance to program mission (for example: projecting on walls,augmented reality) Respond based on “free-play” with the use of artificial intelligenceFunctional System Objectives: Compliance with MIL-STD 810H and in accordance with environmentalstandards using National Electrical Manufacturers Association (NEMA) box8

Connect to the main server to allow user to access machines fromworkstationsProvide functionality to fire Special Effects Small Arms Making System(SESAMS) rounds at images for trainees to test decision-making skillsAccount for laser tracker for capturing laser shots by user to determine if“Friendly/Foe” was hit or missedAllow the image generating machines to be controlled from an array ofinstructor stations from AAR and/or control nodeAbility to play sounds produced by software to create the most realistictraining environmentIntegrate Instrumented-Tactical Engagement Simulation System (I-TESS)/Force on Force Training System Next (FoFTS-Next) configuration devicesfor re-configuration of Small Arms Transmitters (SATs) with reducedMultiple Integrated Laser Engagement System (MILES) and Urban CombatAdvanced Training Technology (UCATT) Laser Engagement InterfaceStandard (ULEIS) codesCompliance with existing I-TESS/FoFTS-Next Marine Corps configurationdevices (M4, M16, and M249 Squad Automatic Weapon (SAW), etc.)These requirements also include the need for scenario generation and AARcapabilities.5.3.6. ScenarioThe ITE requires a scenario generation capability (SGC) to support end-userscenario development and deployment at the point of need. The scenario generatormust be able to provide an array of CGF entities and environments to capture thereal-world training described throughout this document. The SGC must take intoaccount the realistic nature required for these training requirements to includepolitical, military, economic, social, information, infrastructure, physical environment,and time variables such as entity movements, behavior, demeanors, characteractivity matching the environment and cultural nature of the training environment,armaments, ethnicities (skin tone and dress), age ranges (infant through adult),gender (male and female), and the ability to speak in language and dialectappropriate for the training scenario.5.3.7. AARThe ITE AAR is intended to provide effective, actionable feedback to the trainee(s).The AAR must provide a variety of data points and metrics surrounding the eventswithin the training scenario. The AAR will support instrumented training feedback toinclude individual and collective feedback to include but not limited to video andsound capture and playback.9

As outlined in Section 7, the PM TRASYS team requires each vendor to submit aPlan of Action and Milestone (POAM) that includes a schedule identifying long-leaditems. PM TRASYS also expects the POAM to reflect spiral development milestoneswhere each milestone has a tangible outcome to include designs anddemonstrations.5.3.8. Prototype ApproachThe Government estimates the total period of performance will be 36 months fromthe date of award. Vendors shall include its anticipated delivery schedule to reflectits individual solutions.The delivery timeframe is estimated to be divided among the five (5) followingphases:Phase 1: DesignThe Design Phase is intended to focus on the vendor’s proposed solution oftechnical and functional requirements and the results of thorough analysis of thesoftware and hardware viability.Phase 1 Technical Objectives: Basic principles of technology readiness includingwritten studies. The Design Phase will discuss the integration of sub-systems andtechnology insertion to accomplish the objectives of CGF.Phase 1 Expected Outcome: White paper with complete system design that includesall of the CGF technical objectives.Phase 1 Decision Point (DP): Based upon the results of Phase 1, the Governmentmay or may not determine to enter into Phase 2. The specific DP criteria will bedefined during SOW collaboration.Phase 2: Prototype DevelopmentThe Prototype Development Phase is intended to focus on the physicalmanifestation of the white paper from Phase 1.Phase 2 Technical Objectives: Component or application formulated. Prototype isrealized and matured from a white paper to a physical prototype system.Phase 2 Expected Outcome: Basic technological hardware/software components ofCGF are integrated in an operational environment to establish that they will worktogether and meet training objectives for the CGF. Deliverable is a system (TRL 6minimum, as referenced in Attachment 1) to demonstrate the solution described inthe white paper from Phase 1.10

Phase 2 Decision Point: At the end of Phase 2, the Government may or may notdetermine to enter into Phase 3, based on whether or not the demonstrated solutionis at least TRL 6. The specific DP criteria will be defined during SOW collaboration.Phase 3: User AssessmentThe User Assessment Phase is intended to focus on assessing the prototype(s)solution(s) from Phase 2. The system will be deployed for use at MCB CampPendleton, CA and MCB Camp Lejeune, NC to collect operational feedback.Phase 3 Technical Objective: Collect user feedback on the prototype at MCB CampPendleton, CA and MCB Camp Lejeune, NC.Phase 3 Expected Outcome: The User Assessment will be conducted at the Indoorand Outdoor Infantry Immersion Trainer for operational environment. Deliverable issystem completion and qualification through test/demonstration.Phase 3 Decision Point: Based upon the results of Phase 3, the Government willdetermine if the prototype has reached an acceptable maturity level based onevaluator feedback collected from users. The acceptable maturity level and exitcriteria will be defined during SOW collaboration.Phase 4: Increment 2 DevelopmentThis phase is intended to incorporate feedback received in Phase 3 and to continueto mature the technology to reach a level of TRL 8.Phase 4 Technical Objectives: Mature solution to TRL 8. Incorporate user feedbackfrom Phase 3.Phase 4 Expected Outcome: Deliverable is a system (TRL 8 minimum) todemonstrate the ruggedized CGF.Phase 4 Decision Point: At the end of Phase 4, the Government may or may notdetermine to enter into Phase 5, based on whether or not the demonstrated solutionis at least TRL 8. The specific DP criteria will be defined during SOW collaboration.Phase 5: User Assessment 2The User Assessment 2 Phase is intended to focus on a second assessment on theoutcome of Phase 4.Phase 5 Technical Objective: Collect user feedback on the prototype at MCB CampPendleton, CA and MCB Camp Lejeune, NC.11

Phase 5 Expected Outcome: The User Assessment will be conducted at the Indoorand Outdoor Infantry Immersion Trainer for operational environment. Deliverable issystem completion and qualification through test/demonstration.Phase 5 Decision Point: Based upon the results of Phase 5 the Government willdetermine if the prototype has reached an acceptable maturity level and evaluatefeedback collected from users to determine if the prototype should go intoproduction. The acceptable maturity level and exit criteria are conditional and will befurther defined during the SOW collaboration.5.4 Government Desired Rights in Technical Data and Computer Software5.4.1The Government requires Government Purpose Rights (GPR) in alltechnical data (including computer software documentation) and computer softwaredeveloped under any OT awarded pursuant to the RFS, for, at least, a five-yearperiod. The five-year period, or such other period as may be negotiated, willcommence upon execution of the OT that required development of the technicaldata (including computer software documentation) and computer software. Uponexpiration of the five-year (or other negotiated period), the Government desiresunlimited rights in the technical data (including computer software documentation)and computer software. Printed deliverable (e.g., printed hardcopies, .doc, webbased html, etc.) will be labeled accordingly and contain all appropriate markingsassociated with the distribution classification.All technical data, intellectual property and non-commercial off the shelf (non-COTS)software are desired to be provided with a minimum of GPR.Any commercial or COTS shall be provided with a transferable license that allowsdistribution of the software and transfer of the license to any government agency orDoD vendor for any ITE prototype project related purpose. All software licensingshall include a minimum term of five years of use. All software shall be provided withany available major upgrades, minor updates, security patches and technicalsupport for the entire period of performance. When the addition of new software orhardware is proposed for the system or developed under this agreement withgovernment funding or partial government funding, the vendor shall ensure thatsufficient rights in technical data to include software and hardware are procured toenable the government to maintain and modify the system using governmentpersonnel and/or third-party vendors. Government approval is required forexceptions to GPR.In its proposal, the vendor for any OT awarded in accordance with this RFS shallanalyze feasible non-proprietary solutions and incorporate such solutions into itsproposed solution when practicable. This preference for non-proprietary solutions12

applies to any technical data (including computer software documentation) andcomputer software developed or delivered under the OT. The vendor shall clearlystate all assumptions made during development of its proposal.The vendor shall provide a data rights assertion table, Attachment 04, for alltechnical data (including computer software documentation) and computer softwareto be developed or delivered under the OTA. The data rights assertion table shallidentify at the lowest segregable level the technical data (including computersoftware documentation) and computer software to be developed or delivered underthe OT, the vendor’s assertion as to the government’s rights in each item oftechnical data (including computer software documentation) and computer software,the basis for such assertion, and the name of the person asserting any restrictions.For any technical data (including computer software documentation) or computersoftware in which the vendor asserts the Government will have less thanGovernment purpose rights, the vendor shall provide the open source, commercial,or other license it asserts is applicable. The vendor’s assertions, including anyassertions of its sub-vendors or suppliers must be submitted as an attachment to itsSolution Paper. The tables must be completed in the format set forth in theattachment, dated and signed by an official authorized to contractually obligate thevendor. If additional space is necessary, additional pages may be included. There isno page limit for the Data Rights Assertions Tables, and they do not count againstthe proposed technical solution page limitation.All technical data and information developed under this effort should be marked withthe appropriate marking in accordance with DoDI 5320.24, Distribution Statementson Technical Documents. This generally should be marked with “DISTRIBUTIONSTATEMENT D. Distribution authorized to the Department of Defense and U.S. DoDcontractors only (fill in) (14 May 2021). Other requests shall be referred to PEOSTRI.”5.4.2For the purposes of this RFS and final award document, the Governmentwill use the data rights and computer software related terms defined in Attachment5, Data Rights License Terms Definitions.5.4.3Vendor shall complete the Data Rights Assertions Tables using the formatprovided in Attachment 04, Data Rights Assertions Tables. The vendor’s assertions,including any assertions of its subcontractors or suppliers must be submitted as anattachment to its Solution Paper. The tables must be completed in the format setforth in the attachment, dated and signed by an official authorized to contractuallyobligate the vendor. If additional space is necessary, additional pages may beincluded. There is no page limit for the Data Rights Assertions Tables, and they donot count against the proposed technical solution page limitation.13

5.4.4A

Project Management MS Word/PDF X Solution Paper MS Word/PDF X Govt Desired Rights in Tech Data & Computer SW MS Word/PDF X Anticipated Delivery Schedule MS Word/PDF X Schedule (POAM) MS Project/ PDF X Price Pricing Breakout Excel X No Page