Air Force Contracting Information Systems (AFCIS)

Added: Jun 18, 2013 10:46 am

18 JUNE 2013 ADDITIONAL COMMENT:

Request for Proposal FA8771-13-R-0002 Air Force Contracting Information Systems (AFCIS) is anticipated to be awarded no later than 01 July 2013.

Added: Apr 15, 2013 10:04 am 15 APRIL 2013 ADDITIONAL COMMENT: 

In accordance with Request for Proposal FA8771-13-R-0002 Section M - Evaluation Factors, the Government has decided to invoke Section III Contingency Procedure.

Added: Mar 21, 2013 6:46 pm

21 MARCH 2013

ADDITIONAL COMMENTS:

1. Reference toExpeditionary Combat Support System (ECSS) has been deleted from Performance Work Statement (PWS) paragraphs 2.4.10, 2.6.5, and 2.8.4 and Standard Form (SF)33 CLINs 0001, 1001, 2001, 3001, and 4001.  Revised PWS 20 March 2013 is attached to the SF33.

REVISED:  PWS Section 2.4.10

Support current SPS XML standards for integration with Enterprise Resource Planning (ERP) solutions such as the Defense Enterprise Accounting and Management System (DEAMS), the General Fund Enterprise Business System (GFEBS), and the Defense Medical Logistics Standard Support System (DMLSS).

REVISED:  PWS Section 2.6.5

Support other SPS teams (such as adapter support team) with testing of other systems as required.

REVISED:  PWS Section 2.8.4

Provide analysis and support to integrate EAP procurement processes into Air Force and DoD Enterprise Resource Planning (ERP) solutions such as the Defense Enterprise Accounting and Management System (DEAMS), the Air Force Way I & II (AFWay I/II), and the DoD eMall System.

REVISED:  SF33 CLINs 0001, 1001, 2001, 3001, and 4001

This is a firm fixed price CLIN. The contractor shall furnish non-personal information technology services support to include but is not limited to, sustainment, upgrades, implementation, and integration of Standard Procurement System (SPS) and similar contract writing systems into the existing USAF/DoD contracting environment as described in the Air Force Contracting eBusiness Procedures (AFCEP) and Continuity of Operations Plan (COOP) (examples include eBusiness initiatives such as AFWay II, Defense Medical Logistics Supply System (DMLSS), etc).  The contractor shall support existing contracting information systems (as implemented by the USAF) and continued technological transition throughout the contracting community. Services support shall be in accordance with the AFCIS PWS, 20 March 2013.

2.  The following sentence has been deleted from PWS paragraph 3.1:

Contractor shall provide a plan for maintaining technical currency with training and knowledge of the contracting field in order to provide the most current data to the field. 

REVISED:  PWS Section 3.1 The Contractor shall provide personnel appropriate for the tasks identified in this PWS and have a working knowledge of the functional software process.

3.  The following sentence has been revised in Section L, L-II, 13:

REVISED:  Proposals are limited to a maximum of twenty-five (25) pages, excluding Cover Page, Table of Contents, Executive Summary, and Technical Summary Template.  In addition, the Past Performance and Cost/Price Volume do not count against the proposal page count.

4.  The following sentence has been revised in Section L, L-II, 18:

REVISED:  The original proposal shall be identified as such.  One signed copy shall be delivered via email no later than 4:00 PM. CST on 01 April 2013, to the addresses identified below.

Clarifications of Air Force Contracting Information Systems FedBizOps Questions and Answers 15 March 2013

42. Section L Instructions to Offerors, 13 a. Proposal Format:  Proposals maximum page count is Please clarify if that is 25 pages for Executive Summary and 25 pages for technical?  Or 25 total for both?

Answer:  Answer: No, both the executive summary and technical volume combined is limited to 25 pages.

Clarification:  The Executive Summary is not included in the proposal 25 maximum page count for technical. 

Section L, L-II, 13, has been revised to state:  Proposals are limited to a maximum of twenty-five (25) pages, excluding Cover Page, Table of Contents, Executive Summary, and Technical Summary Template.  In addition, the Past Performance and Cost/Price Volume do not count against the proposal page count.

46. What is the total number of hard copies required for delivery and should they arrive by 28 March, 8AM?

Answer:  One copy.  Yes it should arrive by revised proposal due date 01 April 2013, 4:00PM CST.

Clarification:  No hard copy is required to de delivered. 

Section L, L-II, 18 has been revised to state:  The original proposal shall be identified as such.  One signed copy shall be delivered via email no later than 4:00 PM. CST on 01 April 2013, to the addresses identified below.  


New Attachments:
FA8771-13-R-0002 Rev. 2
Request for Proposal Questions and Answers II

Added: Mar 15, 2013 2:37 pm 15 MARCH 2013 ADDITIONAL COMMENTS: 

Standard Form 33, Block 9 Revised
Proposals shall be submitted electronically to the Contracting Officer via email address lashunya.johnson-vinson@gunter.af.mil and Contract Specialist via email address yolanda.dixon@gunter.af.mil. Proposals are due NLT 4:00 PM CST on 01 April 2013, and must conform to the requirements of this RFP and its attachments.

Section L, L-II #18 Revised
The original proposal shall be identified as such. One signed copy shall be delivered via email no later than 4:00 PM. CST on 01 April 2013, to the addresses identified below.

Section L, L-II, #17 Revised
All questions and/or concerns related to this RFP shall be addressed to the Contracting Officer in writing, via email no later than 19 March 2013 at 4:00 PM CST.  All information provided by the offeror, as long as it is consistent with the constraints of the RFP; e.g., page limitations, appropriate volume, is subject to evaluation as described in the RFP, Sections L and M.

Section M, III, #3 Revised
Once we have reduced the number of offerors to a manageable number by completing Step 1 and, if necessary, Step 2. We will then proceed to evaluating the remaining proposals in accordance with the RFP.

New Attachments:
FA8771-13-R-0002 Rev.
Request for Proposal Questions and Answers
Past Performance Questionnaire in Microsoft Word
Storage Equipment List

Added: Feb 28, 2013 4:45 pm

28 FEBRUARY 2013 ADDITIONAL COMMENT:  This notice is a solicitation and the Request for Proposal is attached. 

Section L, L-II, #17 Revised
All questions and/or concerns related to this RFP shall be addressed to the Contracting Officer in writing, via email no later than 15 March 2013 at 8AM CST.  All information provided by the offeror, as long as it is consistent with the constraints of the RFP; e.g., page limitations, appropriate volume, is subject to evaluation as described in the RFP, Sections L and M.

Added: Feb 27, 2013 5:59 pm FAR 52.232-18 -- Availability of Funds (Apr 1984)

Notice to Offerors: Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs."
AFFARS 5352.201-9101 Ombudsman (NOV 2012)

As prescribed in 5301.9103, insert the following clause:
(a) An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern.

(b) Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions).

(c) If resolution cannot be made by the contracting officer, the interested party may contact the Center/MAJCOM/DRU or AFISRA ombudsmen, Colonel Mary McRae, 9 Eglin Street, Bldg 1606, Hanscom AFB, MA 01731, Comm: 781-377-5106, Fax: 781-377-2223, Email: mary.mcrae@hanscom.af.mil. Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/DRU or AFISRA level, may be brought by the interested party for further consideration to the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2397, facsimile number (571) 256-2431.
DESCRIPTION: The objective of the Air Force Contracting Information System (AFCIS) acquisition is to provide Information Technology (IT) support services to include sustainment, upgrades, implementation, and integration of SPS and similar contract writing systems into the existing USAF/DoD contracting environment as described in the Air Force Contracting eBusiness Procedures (AFCEP) and Continuity of Operations Plan (COOP) (examples include eBusiness initiatives such as AFWay II, Expeditionary Combat Support System (ECSS), Defense Medical Logistics Supply System (DMLSS), etc). The contractor shall support existing contracting information systems (as implemented by the USAF) and continued technological transition throughout the contracting community.

COMMENT: Proposals shall be submitted electronically to the Contracting Officer via email address lashunya.johnson-vinson@gunter.af.mil and Contract Specialist via email address yolanda.dixon@gunter.af.mil. Proposals are due NLT 8AM CST on 28 March 2013, and must conform to the requirements of this RFP and its attachments.