RFI_Integrated_Scheduling.docx
DOCX document 20 KB Posted
- Solicitation number
- FA8770-20-R-0507
About this file
Integrated Scheduling
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI_Integrated_Scheduling.docx | DOCX document |
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
REQUEST FOR INFORMATION
AFLCMC/ HIBX
19 July 2019
1.0 Description
AFLCM/HIBX (Acquisition Systems Branch) in support of SAF/AQX is seeking information regarding an Integrated Master Scheduling (IMS) tool capability for Acquisition programs/projects, available in today’s marketplace, which could satisfy the Air Force’s Acquisition enterprise business requirements, as indicated below.
Pursuant to FAR Part 10 (Market Research), the purpose of this notice is to: (1) determine what sources are capable of satisfying the agency’s requirements; (2) ascertain potential market capacity; (3) determine the small business presence in the market; and (4) collect industry experience with successful fielding of integrated master scheduling capabilities, focusing on COTS and GOTS, with minimal customization.
DISCLAIMER: THIS REQUEST FOR INFORMATION is for Market Research purposes only and is being used as an instrument to identify potential sources that can provide the capabilities described within this notice. The information provided in this notice is subject to change and is not binding on the Government. This notice does not constitute an Invitation for Bids (IFB) or a Request for Proposal (RFP) and is not a commitment by the U.S. Government to procure subject services. No funds are available to pay for preparation of responses to this notification. Additionally, all submissions become government property and will not be returned. No basis for a claim against the Government shall arise as a result from a response to this RFI.
2.0 Background
In accordance with Acquisition policy and guidance, all Acquisition programs/projects are required to conduct IMS tasks and activities on a frequent basis, and provide status reporting to senior leadership. Populating and maintaining the program IMS is currently very time-consuming (i.e., requires more program office personnel and increases complexity if resource loading is a requirement), and would be increasingly more time-consuming if it requires the integration of schedules from multiple programs/projects. Currently, all schedules need to be in the same format to support integration, and could require costly contract modifications to have schedules delivered in the PMO’s selected (correct) format.
3.0 Anticipated Capability
In accordance with AFPD 63-1/AFPD 20-1, Acquisition/Logistics, Integrated Life Cycle Management, 7 August 2018, and AFI 63-101, Integrated Life Cycle Management, 9 May 2017, future state business capabilities are needed in order to achieve higher-order IMS requirements.
3.0.1 The initial IMS capability will facilitate the following abilities for customers:
--Ability to populate a program schedule and make changes. This includes the ability to create events, milestones, and timeframes, as well as change them.
--Ability to resource load a program schedule, if required.
--Ability to integrate schedules from various projects related to the program.
--Ability to conduct "what-if" analysis on a version of the program schedule.
--Ability to migrate schedule information from one document to another, and preserve the ability to make changes to the schedule after it is moved.
--Ability to identify program interdependencies within and across program management offices (PMOs).
3.0.2 The AF needs to be able to move data between scheduling tools and not have to enter the data from one to another tool manually. This reflects the facilitation of interoperability between scheduling tools.
3.0.3 The AF needs to be able to standardize on an Acquisition program integrated master scheduling capability, which would facilitate comparison and analysis within and across AFPEO portfolios.
4.0 HOW TO RESPOND:
4.1 Interested parties are requested to respond to this RFI with a white paper.
4.2 White papers in Microsoft Word for Office 2000 compatible format are due no later than 02 August 2019, 12:00 p.m. EST. Responses shall be limited as described below, and submitted via e-mail only to jonathan.ketter@us.af.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. If any respondee does not currently have a Proprietary Data Protection Agreement (PDPA) that would permit the AFLCM/HIBX support contractors listed below to review and evaluate white papers submitted in response to this RFI, the respondee is requested to notify AFLCM/HIBX
4.3. Section 1 of the white paper shall provide administrative information, limited to five (5) pages, and shall include the following as a minimum:
4.3.1. Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.
4.3.2. Recommended contracting strategy.
4.3.3. Either 1) copies of executed non-disclosure agreements (NDAs) with the contractors supporting AFLCM/HIBX and AFLCM/HIBX supported PEOs and DRPMs in technical evaluations or 2) a statement that the respondee will not allow the Government to release its proprietary data to the Government support contractors. In the absence of either of the foregoing, the Government will assume that the respondee does NOT agree to the release of its submission to Government support contractors.
4.3.4. Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 541512, Computer Systems Design Services. “Small business concern” means a concern, including its affiliates that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, averaging no more than $27.5 million dollars in annual receipts. Annual receipts of a concern that has been in business for 3 or more complete fiscal years means the annual average gross revenue of the concern taken for the last 3 fiscal years. Annual receipts of a concern that has been in business for less than 3 complete fiscal years means its total receipts for the period it has been in business, divided by the number of weeks including fractions of a week that it has been in business, and multiplied by 52. Respondees are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://www.arnet.gov.
4.3.5 The facility security clearance of the offeror.
4.4 Section 2 of the white paper shall answer the issues addressed in Section 3 of this RFI and shall be limited to five (5) pages, and typed in 12 point font.
5.0 Industry Discussions
AFLCM/HIBX representatives may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks.
6.0 Questions
Any questions (technical, contractual, etc.) shall be submitted via email to jonathan.ketter@us.af.mil. Telephone inquiries are not acceptable. NO SOLICITATION IS AVAILABLE AT THIS TIME. WE WILL NOT RESPOND TO REQUESTS FOR SOLICITATION MATERIAL.
7.0 Summary
THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can provide an IMS tool, as described herein. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.
8.0 POINTS OF CONTACT:
Questions regarding this RFI should be submitted to the Procuring Contracting Officer and Contract Specialist identified below:
Air Force Procuring Contracting Officer, James Wilson, at james.wilson.11@us.af.mil Contract Specialist, Jonathan Ketter, at jonathan.ketter@us.af.mil
File details come from the government source that posted it.