Inactive

REQUEST FOR INFORMATION The Regional Contracting Office – National Capital Region (RCO-NCR), Marine Corps Base, Quantico, VA is seeking information for Training and Education Command (TECOM), Aviation... REQUEST FOR INFORMATION The Regional Contracting Office – National Capital Region (RCO-NCR), Marine Corps Base, Quantico, VA is seeking information for Training and Education Command (TECOM), Aviation Standards Branch (ASB): Marine Sierra Hotel Aviation Readiness Program (M-SHARP). CONTRACTING OFFICE ADDRESS: Marine Corps Installations National Capital Region – Regional Contracting Office (MCINCR-RCO), 2010 Henderson Rd, Quantico, VA 22134. INTRODUCTION: This Request For Information (RFI) is to seek market information for planning purposes and provide industry with an opportunity to ask questions and provide recommendations regarding the required services outlined in the Performance Work Statement (PWS). The United States Marine Corps (USMC), Training and Education Command (TECOM) Aviation Standards Branch (ASB): Marine Sierra Hotel Aviation Readiness Program (M-SHARP) is moving forward into its -fifteenth year of implementation across the Aviation and Aviation Ground Fleet Marine Corps Forces and Reserves (hereafter referred to as ‘Units’) wherein training and readiness is guided by the Aviation Training and Readiness Program Manual, Navy and Marine Corps Directive (NAVMC) 3500.14. The objective of this requirement is to continue execution of efforts to deploy and support M-SHARP and implement new and enhanced functionality of the application by July 2020 and beyond to fully support the Fleet Marine Forces, Headquarters Marine Corps (HQMC) and Aviation Training System (ATS) needs of Marine aviation, allow more simulator and ground utilization, increase functionality on multiplatform based systems, and increased security and current functionality. M-SHARP application increased functionality and sustainment will allow for ground and other units to use and build on current capabilities. Sustained development and support of a user friendly, web-based and stand-alone application and are paramount to ensure M-SHARP remains a viable and authoritative resource for US Marine Corps Aviation flight hour and sortie based training data. The scope of this effort entails technical, analytical, and programmatic support to implement and sustain mission capabilities. Specifically: (1) continue the development of M-SHARP through sustainment of current capabilities and development of additional needed functionalities; (2) continue building, fielding, and supporting an integrated web-based application for the Units; and (3) provide the Higher Headquarters (HHQ) elements with reporting services necessary for the collection of data required to justify budgetary decisions. DISCLAIMER: THIS REQUEST FOR INFORMAITON IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A REQUEST FOR PROPOSAL. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY. CONTRACT/PROGRAM BACKGROUND: Contract Number: M00264-19-C-0005 Contract Type: Firm Fixed Price (FFP) Vendor: ECS Federal, LLC Method of previous acquisition: Unrestricted Place of performance: Quantico, VA INDUSTRY FEEDBACK: This is a REQUEST FOR INFORMATION (RFI) ONLY to obtain industry’s feedback on the anticipated scope of work, potential cost and performance risks as well as any other related considerations for the required services. Please provide detailed answers to the following: What software or technological improvements would you expect from a program like this? Is this next contract period the appropriate time to make the program serverless? Would you recommend going serverless? Why or why not? Are there any technological improvements that could/should be developed concurrently with going serverless that would increase efficiency or reduce long-term costs? Do you think this program is technologically ready to begin implementing Artificial Intelligence or Machine Learning to optimize flight scheduling, readiness, or risk mitigation? What enhancements or changes would you recommend to this program to best prepare it for AI/ML? How many data scientists or data analytics professionals would your company need to develop tools that track both student and instructor performance and trends? How would you contract/price cloud sustainment to reduce costs? Should cloud sustainment be it’s on contract line item? How would you contract/price data exchange (API) sustainment? How would you structure a contract to account for the requirement to build future APIs without yet knowing the details? Does your company have the capability to perform all required services in the draft PWS? Please explain your ability to provide seamless support services as identified in the draft PWS? How much lead-time will your company need from notification of award to start if work? Does the draft PWS contain information that would enable you to adequately respond to a RFP? What are the key cost drivers? What other Government agencies are contracting for similar requirements? Who is doing it best? What historical information will vendors require to propose? What technical information will vendors require to propose? What portions of the requirement cannot be fixed-price, and why not? What portions on the contract could be “at cost” to reduce to save money? What are variables that drive price up or down? What can be done to minimize the cost? What areas of the requirement seem restrictive? What is the remedy? What areas of the requirement seem vague? What is the remedy? Which new functionally requirements would you recommend consolidating or developing concurrently? Why? Which new functionally requirements would you recommend dividing into small parts to expanding into multiple contract years? Why? If a requirement were split into parts that were developed over multiple contract years, how would you structure the requirements and deliverables to allow for efficient and effective pricing of the contract line item? Are there any new technological developments that can be applied towards the service? What obstacles would prevent your business from submitting a future quote/proposal for this requirement? Are you likely to propose on this effort? Why or Why not? What NAICS code is the most appropriate for this requirement? ATTACHMENTS: PWS SUBMISSION DETAILS: Interested parties who wish to respond to this RFI shall send responses via email no later than 27 September 2023, 1:00 PM Eastern Standard Time (EST) to grace.gonzalez@usmc.mil and christa.eggleston-sc@usmc.mil. Submissions shall reference RFI No. “M00264-23-RFI-0025 – USMC M-SHARP” in the subject line. Interested parties should respond to the areas of concerns cited under the “INDUSTRY FEEDBACK” section of this document. Request responses limit page count to only provide detailed information necessary to adequately respond to the information requested. Responses must include: Responses to all questions cited in “Industry Feedback” section of this RFI Business name and address Name of company representative, business title, phone number and e-mail address Type of Business Cage Code Contract vehicles that would be available to the Government for the procurement of the product and service, to include ENCORE II, General Service Administration (GSA), GSA MOBIS, NIH, NASA SEWP, Federal Supply Schedules (FSS), or any other Government Agency contract vehicle. (This information is for market research only and does not preclude your company from responding to this notice.) PROPRIETARY INFORMATION: Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. All government and contractor personal reviewing Sources Sought responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.