Q&A_v12.pdf

Question:

Answer:

PWS

1. Q: PWS Paragraph 1.1.2 “Support is required for offsite locations throughout the state of New Mexico, Socorro and White Sands and one out of state location in Camp Navajo, Arizona.” Would the government confirm if these locations have equipment accounts with assets that must be inspected/inventoried by EAE personnel on an annual basis or do they fall within the realm of Geographically Separated Units?

A: Yes, those locations do have equipment and they are considered GSUs.

2. Q: Reference PWS Paragraph 1.1.6: The paragraph states that Offerors are to submit an Organizational Chart with labor categories indicated on it. It is our understanding that the Department of Labor has ruled that functions within the Base Supply organization should have categories used that are higher than the SCA Wage Determination categories typically used for similar work at other locations based on precedence. Does the Government have job descriptions for the categories that are listed in the Collective Bargaining Agreement?

A: No, The Government does not have job descriptions for the categories that are listed in the Collective Bargaining Agreement, contractors are responsible for developing the individual job descriptions IAW the PWS.

3. Q: Government has indicated in PWS 1.1.6 that cross-utilization of personnel will not be allowed. Request that the Government define their meaning and intention of this requirement. Is the Government indicating that the contractor cannot use a 0.5 FTE in one function and the other 0.5 of that FTE in another function, such as Document Control, PWS 2.3 and Customer Service, PWS 2.4? Please clarify the requirements on this issue.

A: Yes, the contractor cannot use a 0.5 FTE in one function and the other 0.5 of that FTE in another function.

4. Q: PWS Paragraph 1.1.6 states “Cross-Utilization of personnel shall not be allowed.”

Would the government please clarify the intent here, as having a flexible staff who are trained to support more than one work center greatly enhances the vendor’s ability to respond to surges in workload, while at the same time, save the government money by avoiding the hire of additional staff.

A: PWS PARA 1.1.6. UPDATED as follows for clarity.

1.1.6. Offerors must submit a Staffing Plan outlining proposed staffing, lines of authority, and an organizational chart with labor categories. Staff Plan and positions identified shall remain in place during the life of the contract. The plan should provide evidence that the offeror understands the requirements of the PWS and acknowledges the Government provided workload (Appendix D) is based on historic workload analysis coupled with recent changes in AFMAN/AFI 23 Series guidance. Cross-utilization of personnel may be allowed when workload increases or changes to requirements are identified by the contractor that have been verified by Contracting Officer concurrence.

Cross-utilization of personnel may be allowed during workload surges, when the government directs the surge to take place, or when proportional duties are combined to maximize efficiencies and approved by the COR(s) and Functional Director and no negative impact is experienced. Cross-utilization will not be used as a means of providing daily services or long term staffing. Identify management support structure that will be responsive to contractual problem areas. (CDRL A012)

5. Q: Reference PWS Paragraph 1.1.6: The paragraph states “Cross-utilization of personnel shall not be allowed.” Please confirm that cross-utilization in the Government’s statement does not preclude personnel from doing tasks within their immediate area such as personnel working in Receiving to put away property.

A: See question 4

6. Q: Reference PWS Paragraph 1.1.6: The paragraph states “Cross-utilization of personnel shall not be allowed.” If the intent of the Government is to limit cross-utilization, please state which specific areas where cross-utilization is not allowed.

A: See question 4

7. Q: Is the Contract Manager the only key personnel position? If not, please provide a listing of Key Personnel. (Reference: PWS Section 1.1.9 which requires Provide a signed letter of intent and consent from the proposed key personnel consenting to the release of their contract past performance information to the prime contractor.)

A: Contract Manager and alternate are key personnel. PWS 1.1.9 updated.

8. Q: PWS Paragraph 1.1.9 states, in part, “Provide a signed letter of Intent and consent from the proposed key personnel consenting to the release of their contract past performance information to the prime contractor”. Will the Government please clarify what is desired regarding “contract past performance information” on personnel? Which personnel require a signed letter of intent?

A: Information should include how effective the contract manager is in the performance of the contract they were hired to perform. The Key Personnel position requires the signed letter of intent.

9. Q: PWS Paragraph 1.1.9 also states “Key personnel will be required to hold a current Secret security clearance at start of contract period and maintain throughout the life of the contract.” Will the Government please be more specific who the key personnel are?

A: Contract Manager and alternate

10. Q: Reference PWS Paragraph 1.1.9: The paragraph states the Contract Manager must have four years’ experience as a Supply Contract Manager. Would a candidate who has managed a functional area (such as the warehouse) in a contractual setting as a Deputy or experience of leading similar services in an Active Duty position as an Officer or Senior Non Commissioned Officer be acceptable?

A: Offerors need to explain the capabilities of their experience and experience factors.

Explain the magnitude and relevancy, and recency as compared to the work being proposed

11. Q: Reference Addendum to FAR 52.212-2 and PWS Paragraph 1.1.9: The paragraph states “Provide a signed letter of intent and consent from the proposed key personnel…”. Are we to provide the letter of intent and consent with our proposal?

A: Yes

12. Q: Reference PWS 1.1.11: The paragraph describes a detailed plan for EAE personnel who will use the AFEMS system. Will the Government be providing DPAS training to EAE personnel who will use the AFEMS system. Will the Government be providing DPAS training to EAE personnel as part of the migration process to DPAS?

A: Refer to Paragraph 1.3.4.2.2. The Government will provide technical training for new equipment requirements or new technologies the government specifies for use in the performance of the contract. This training will be provided to a minimum of one contractor employee. This initial cadre shall provide the training to the remainder of the contractor’s employees as required, to ensure 100% task coverage. Initial training will be provided at the Government’s expense.

13. Q: PWS Paragraph 1.1.15 “All contractor Level 1, 2 and 3 Information Assurance Technicians (IAT) and Information Assurance Managers (IAMs) will maintain the appropriate 8570 IA certifications. This certification must be obtained prior to being engaged with the responsibilities. The AF does not fund certification training, maintenance fees or exam vouchers. Does the government provide a grace period to obtain certification or must the contractor already possess?

A: The Contractor must possess the certification prior to first day of performance as the contractor will not be authorized to manage the IT requirements without it, which would cause a critical delay and inability of the contractor to perform required services through all functions of the contract.

14. Q: Reference PWS Paragraphs 1.1.19 and 1.1.20: The paragraphs state that Pickup and Delivery, Receiving, DIFM, and IEE could be removed from the resulting contract and these functions are to be priced out as separate CLINs. The CLIN structure does not reflect all these functions as separate functions. Please clarify how Offerors are to price these functional areas.

A: This function is part of CLINs X008, X009, and X010. Under paragraph 1.1.20 of the PWS there 3 separate functions listed that may be removed during the contract. (a) Receiving function, (b) DIFM pick-ups and (c) IEE.

15. Q: PWS Paragraph 1.1.20 (a) “The Receiving function could be removed from the existing contract and performed by the government. A separate CLIN will be established for personnel and services associated with this function/service and priced out accordingly. The Receiving function has not been identified by its on CLIN in current PWS or RFP. In the event that the government removes this function from the current PWS, does the government expect to descope and decrease the CLIN that is currently affected?

A: CLIN X008 changed to Receiving Function.

16. Q: PWS Paragraph 1.1.20 (b) “Specifically the pick-up of Due-In From Maintenance assets from all customers. A separate CLIN will be established for personnel and services associated with this function/service and priced out accordingly.” AFI 23-101, Section 4C, Para. 4.3.1.2.1 “Serviceable and unserviceable DIFM items will be returned directly to FSC within 4 days from date of issue” suggests that maintenance personnel will be returning the DIFM items to the FSC. However, paragraph 4.3.1.3.1 reads “LRS Commanders’ option to have DIFMs picked up by Flight Service Centers for those activities within maintenance repair facility compounds. (T-2).” Because the pick-up of DIFM assets from customers does not have a separate CLIN identified, can the government provide the “LRS Commander’s option”? Specifically, is the contractor required to perform the function of picking up the DIFM assets from maintenance activities?

A: CLIN X009 changed to Due-In From Maintenance pick-up. The contractor is required to pick up DIFM assets from the customers.

17. Q: PWS Paragraph 1.3.1 “Contract Manager. Provide a person responsible for the performance of the work. This person shall be physically present at KAFB during normal working hours and shall have the authority to act for the contractor on all matters relating to daily operation of this contract and shall have the authority to make policy/procedural decisions. Submit in writing to the CO the name of the primary and alternate contract manager within 5 days of the start of transition period. Does the government require that an alternate contract manager be on site during times of Contract Manager’s absence?

A: Yes, requirement added to PWS para. 1.3.1.

18. Q: PWS Paragraph 1.3.2.1 “Warehouse personnel will be required to wear steel toe safety shoes at all times.” Are warehouse personnel the only personnel required to wear steel toe safety shoes or are EAE, Inventory, etc. required to as well?

A: Only personnel “working in the warehouse with equipment, cargo or any related task that require safety toes shoes for protection from working hazards must have safety toe shoes. Any personnel from other functions of the contract that go to areas to perform work where safety toes shoes are required, must be in compliance with this as well.

19. Q: PWS Paragraph 1.3.2.2 “The contractor shall not employ any person who is an employee, or a former employee, of the United States government without authorization by written legal opinion from a designated Agency Ethics Counselor.” Can the government please provide regulation, directive, etc. as this limits the recruiting capability for the contractor in obtaining fully qualified personnel with significant experience in Air Force Supply operations?

A: Individuals that have worked for the government in the past are counseled by local Agency Ethics Counselors when they depart their government position. Former government employees that desire to work for a contractor should contact the government Agency Ethics Counselor that provided that departure briefing.

20. Q: Reference PWS Paragraphs 1.3.2.2: The paragraph states a legal opinion from a designated Agency Ethics Counselor is required to hire a current or former employee of the U.S. Government. Please provide details on this process.

A: Individuals that have worked for the government in the past are counseled by local Agency Ethics Counselors when they depart their government position. Former government employees that desire to work for a contractor should contact the government Agency Ethics Counselor that provided that departure briefing.

21. Q: PWS 1.3.2.3 The statement related to Military Reservists and National Guard personnel appears to give the negative connotation to hiring military personnel in the Reserves or Guard. Is that the intention of this statement?

A: The statement is only listed to bring attention to absence of personnel will not constitute an excuse of nonperformance under this contact.

22. Q: Will government accept an interim TS facility clearance?

A: Yes, per PWS para 1.3.3.11. Clarification added.

23. Q: PWS Paragraph 1.3.3.11. Facility Clearance Requirements, states “Possess or obtain an appropriate facility security clearance level as established in the applicable DD Form 254, DoD Contract Security Classification Specification at time of award. Submit security clearance requests to the 377 ABW/IPD within 15 days after award.” Will the Government please clarify the following: Is there a window of time to “obtain” the facility clearance since this is presented as an option to “possessing” the clearance?

A: Submit the security clearance request to the 377 ABW/IPD within 15 days after award. There is no window of time for the contractor to obtain the clearance, only a timeline for the contractor to submit it to the office identified in the paragraph.

“Possess” removed from paragraph and paragraph updated for clarity.

24. Q: What is the purpose of submitting security clearance requests to the 377 ABW/IPD?

Does this imply the Government will process those requests?

A: Yes, within 15 days after award.

25. Q: Reference PWS Paragraph 1.4.5.2: The paragraph states the Contractor is to review and provide input as required for compliance with Base Operation Plans listed in Appendix C. There are no base specific plans identified in that list beyond the installation IDP. Please provide specifics of support requirements levied on Base Supply or copies of the specific plans for review by potential Offerors.

A: 1.4.5.2. Review and provide input as required for compliance with all Base Operation Plan(s) (OPLAN) listed in Appendix C.

Appendix C as referenced in paragraph 1.4.5.2. references KAFB Installation Deployment Plan, Defense Plan and Kirtland OPLANS.

Added to Appendix C:

AFI 10-403 Deployment Plan AFI 10-404 BaS&E, Base Support Plan Part One AFI 10-2501 Emergency Responses

Base Supply will not be the author of the OPLANS. Supply will review and provide input as required for compliance. There is no additional work levied on supply.

Copies of plans will be available for review when contract is awarded.

26. Q: PWS Paragraphs 1.10.2 thru 1.10.4 and 1.11.1 thru 1.11.8 Reference “M” (Government Furnished Facilities). With regards to Building 1010, as the government occupies the majority of the building, is the contractor solely responsible for all operations identified within the above paragraphs?

A: The contractor will only be responsible for the areas where they maintain office space and storage space. The contractor will only be responsible for the keys to their office and storage space areas.

27. Q: PWS Paragraph 1.19.5 “Obtain security clearances, as required. Does the government have a suspense date/period of time required for personnel to obtain required clearances?

A: Paragraph 1.3.3.3 of the PWS identifies the timeframe for this.

28. Q: The term MICAS is no longer used, and has been replaced by Enterprise Solutions- Supply (ES-S) Mobility. Will all references to MICAS be change to state "Mobility IT system or ES-S Mobility"?

A: PWS updated to remove the MICAS as the system name.

29. Q: PWS Paragraph 2.1 “The quantities of work are listed in Appendix D. The contractor shall not be required to perform Stock Fund Management and Pick-up and Delivery Functions.” Can the government clarify Pick-up and Delivery Functions (i.e.

DIFM assets as identified in question 5).

A: The contractor will not be required to deliver assets to customers around the base.

The contractor is only required to pick up DIFM assets from customers.

30. Q: PWS Paragraph 2.2.20 “All requested logs will be posted and maintained electronically and by hard copy to support functions of supply where required. The FD or COR personnel will approve the format of all logs. All requested/required logs will be available real-time, immediately following actions or transactions that are required to be recorded/listed within the logs.” If the contractor is required to purchase office supplies, i.e. paper, toner, etc., will the government reimburse or provide paper for any documentation or logs that are required to be provided by hard copy to support functions?

A: Paper and toners for government owned printers will be provided upon request through the COR for approval and government purchase.

31. Q: Reference PWS Paragraph 2.3.2: The paragraph references the Electronic Document Control Storage and Retrieval System. Please confirm the annual licenses for this package is provided by the Government or reimbursed by the Government in the event that it is to be purchased by the Contractor.

A: Licenses and Retrieval System are provided and paid for by the Government.

Contractor will not purchase this equipment.

32. Q: Ref. PWS 2.6.6. This paragraph states “Conduct annual organizational visits to ensure custodians are performing accountability responsibilities. Perform a “floor to book” “book to floor” inventory.” AFI 23-101, Paragraph 5.4.2.6.8 states it is the responsibility of the owning organization to conduct their own inventories. Please clarify the responsibility of the offeror as to the performance of these inventories. If offeror’s are required to perform these inventories, please provide the relevant workload – how many organizations are to be visited and how many items are to be inventoried?

A. PWS para 2.6.6. changed to read: The contractor, as the supply Subject Matter Expert (SME), is responsible when conducting annual surveillance to look in the work areas to ensure items are accounted for on the appropriate Accountable Property Systems of Record (APSR). Floor to book refers to physically checking the entire work area to ensure items are accounted for on the appropriate APSR.

Workload for all EAE responsibilities is located in Appendix D of the PWS.

33. Q: Ref. PWS 2.6.7. This paragraph states “Periodically accomplish 100% hands-on specialized inventories of categories requested by the CORs, CO or Senior Logistics manager.” Paragraph 5.4.2.6.8 states it is the responsibility of the owning organization to conduct their own inventories. Please clarify the responsibility of the offeror as to the performance of these inventories. If offeror’s are required to perform these specialized inventories, please provide the relevant workload – how often are these inventories performed and how many items are to be inventoried?

A: The requirement for this is as stated in the PWS. It will only be performed on an as required/requested basis when there are problems in accountability for specialized controlled assets (Weapons, COMSEC, Capital Assets, etc. as mentioned in the guidance) which are the responsibility of the contractor to inventory or when the contractor has discrepancies in the 10% check they are require to perform on non-specialized controlled assets, the commander, FD or COR personnel may ask for the service to be re-performed.

34. Q: Ref. PWS 2.6.39 and PWS 2.6.40 – these paragraphs instruct the offeror to manage the Q09 and Q10 and “coordinate with CEMO and other agencies where required. EAE can view changes and updates made via available supply systems and listings.” These items are managed at 437 SCOS. Please clarify the offeror’s responsibility for these requirements.

A: The contractors responsibility is to review the reports, assist customers where required and take actions when needed to resolve any concerns. The Contractor is also the liaison between CEMO and the customers they support.

35. Q: PWS Paragraph 2.6.62 EAE personnel are required to “Assist in coordination of equipment pickup.” Can the government provide additional information concerning the requirement to “assist” and to what degree personnel involvement entails?

A: The government requires EAE to assist in coordination. Coordination meaning to ensure appropriate transactions, documentation and tags are completed for turn in/pickup actions. These task are associated with EAE responsibilities.

36. Q: PWS Paragraph 2.6.63 “EAE personnel will provide the commanders responsibility briefing IAW AFI 21-101, AFMAN 23-122, and AFH 23-123 and all applicable guidance where it requires organizational commanders, directors or responsible personnel to receive equipment briefings, training or information. Can the government provide additional information, aside from workload data already provided in Appendix ‘D’? Specifically, is there training modules that will be provided to the contractor prior to assuming this responsibility; where will training be conducted and anticipated duration of training?

A: There are briefing slides maintained in the EAE files for the briefing. The training will be conducted in the training space within the LRS provided by the government.

Training at other locations on the installation will be approved by the FD and COR personnel.

37. Q: PWS Paragraph 2.11.1 “Receive and process incoming MICAP shipments within one hour of receipt.” Paragraph is conflicting with Paragraph 2.11.4 which states “MICAP assets will be processed within 30 minutes of delivery to supply”. Can the government confirm which time frame is to be used as the “one hour” time frame is a Service Summary Item?

A: The PWS has been updated (see Amendment 6) to reflect one hour for the MICAP requirement identified in paragraph 2.11.4

38. Q: PWS Paragraph 2.11.39 “Maintain existing low-level radioactive storage facility and coordinate disposition of radioactive material with the base radiation safety officer.” A “low-level” radioactive storage facility is not identified in Appendix “M”.

Can the government confirm that such a facility exists?

A: Paragraph deleted there is no longer low-level radioactive storage facility.

39. Q: Is there any vehicles, other than the items listed in Appendix L provided by the Government to support the various tasks, such as, pick-up of DIFM items from customers, PWS 2.11.51. Please provide a listing of vehicles that will be assigned to the contractor.

A: All vehicles that will be provided to the contractor are listed in Appendix L.

40. Q: PWS Paragraph 2.11.73 (SS-2) Process all supply transactions IAW AFI 23-101, AFMAN 23-122, AFH 23-123 and applicable guidance. Information for transaction inputs are required to be accurate prior to transmittal. All record reversal transactions will be forwarded to COR personnel for approval prior to processing. Requests will be reviewed and validated by COR personnel to determine the cause of record reversals.

Actual SS #2 allows for 8 “Contractor caused discrepancies” within the month. Can the government clarify what transactions are associated with these discrepancies as the workload in Appendix “D” has an average of 34,481 “Printable Transactions” per month. 8 discrepancies within the month would equate to an error rate of < 0% placing the contractor in jeopardy each month for not meeting the threshold. Additionally, can the government provide historical data, identifying contractor caused discrepancies?

A: SS-2 will only come in to play if the contractor directly causes more than 8 RVP’s in a single month. RVP transactions that are based on multiple transactions even when the contractor is at fault will only be looked at a single RVP error. The Printable Transactions per month will NOT be a determining factor. The government has considered all of the relevant information for this requirement and is confident that 8 discrepancies are more than fair in providing the contractor a baseline for success while ensuring the government is getting the expected level of service. Additionally COR personnel will review discrepancies and the contractor justification for the record reversals. If determined to be contractor caused, it will be identified as a discrepancy against the contractor. This places emphasis on the contractor that they are providing qualified, responsible and professional personnel to execute the base supply service.

Example of contractor direct cause of RVP:

RVP Transactions due to Warehouse Refusals. A warehouse refusal occurs when the warehouse location stated on an issue or shipment document is either empty or does not contain enough quantity to fill the request.

RVP due to process of erroneous TIN, ISU, RECs due to lack of attention to detail

41. Q: Ref. PWS 2.13.8 – this paragraph states offerors are to “Store, inventory, update contents, maintain, and issue standardized individual mobility bags when requested by Base organizations IAW AFMAN 23-122 and unit agreements.” Per AFI 23-101 paragraph 5.3.8.1.3.2.2, “All IPE assets will be bulk stored. Kits are not authorized.”

Please clarify the offeror’s responsibility with regard to this requirement.

A: This requirement is on an “as requested” basis as mentioned in the PWS. This request would be for the purpose of supporting deployment or training requirements which are already mentioned in the PWS.

42. Q: Reference PWS Paragraph 2.13.18: The paragraph states “Accomplish the following tasks in the performance of armed escort duties.” There is nothing following this sentence. Please clarify the Government’s intent for this paragraph.

A: Paragraph updated for clarification of requirement following questions from contractor.

2.13.18. Perform armed escort duties for bulk shipped weapons during base exercises and real world deployment operations. Personnel will be required to escort IPE issued, bulk shipped weapons to deployment staging location. Personnel will be required to stay with weapons until weapons are moved to the aircraft for loading or until the weapons have been released for storage back to the LRS vault. IPE personnel will not be required to transport weapons for this requirement. Armed escort responsibility expected to last up to 12 hours for each base exercise or real world deployment.

43. Q: PWS Paragraph 2.3.19 references a “Secret Security Check” among other requirements for weapons management personnel. Will the Government please clarify the terminology and requirements in this section?

A: The government assumes this question is about PWS para 2.13.19 as PWS 2.3.19 is not a part of the PWS. Para 2.13.19. Changed to read “Secret Security Clearance” and deleted the work “ Check”.

44. Q: Ref. PWS 2.15.1 – this paragraph states offerors are to “Maintain a file of the HQ AFMC Clothing Multiple Address Listings (CMAL) and use to provide customers with information pertaining to clothing and textile items.” Currently there are no CMALs posted on the Air Force Uniform Office website. CMAL is no longer distributed and appears to have been replaces with the Informational Memos and Policy Documents forum on the AF Portal Air Force Uniform Office website. Please clarify the offeror’s responsibility with regard to this requirement.

A: The contractor will maintain a file of the Informational Memos and Policy Documents forum obtained from the AF Portal Air Force Uniform Office website and use to provide customers with information pertaining to clothing and textile items.

45. Q: Are the Government Comments left on the document to be taken as incorporated into the published PWS?

A: An updated PWS was included in Amendment 2 without comments. Per Amendment 3, an additional updated PWS will be posted.

46. Q: Last document in the Amendment #2 package was not attached successfully.

Would you be able to forward a copy of the document and/or reupload it on FBO?

A: Disregard, no document to attach.

47. Q: There are numerous methods for working the Date of Last Inventory for equipment, which method is employed at Kirtland?

A: The methods which are acceptable per Air Force guidance are the methods that will be used. They are stated in the guidance (AFI 23-101, AFMAN 23-122, AFH 23-123 and LIMS-EV guidance). Methods are subject to change as Air Force directives change.

There are no methods specific for Kirtland that are required. All documented, guidance driven Air Force methods are acceptable.

48. Q: Please clarify the offeror’s responsibility to track accountable assets not listed on a

CA/CRL? Is this not the owning organization’s responsibility?

A: The contractor is responsible to ensure the organizations have a system in-place for managing these types of asset.

49. Q: Will the Government please clarify the references in CDRL A005, Letter of Competency for Vehicle Operators? The CDRL is referenced in PWS paragraph 1.3.4.2.2 (along with CDRL A006), but block 16 of CDRL A005 includes a paragraph 3.5.3 reference that is not included in the PWS. CDRL A005 also references paragraph

1.3.4.2.2 in block 5, thus creating conflicting references.

A: Paragraph 3.5.3. has been added to the PWS. CDRL A005- Block 5 reference has been changed to 3.5.3. This is in Amendment 2.

50. Q: Will the government please provide workload data on the following:

1.2.1 – War Readiness - Number of exercises performed per year?

Average 4 per year-WL Data will be updated in Amendment 6.

1.3.4.2.7 – Number of exercises per year Average 4 per year-WL Data will be updated in Amendment 6.

1.3.5 – Average duration of meetings.

1 Hour-PWS will be updated in Amendment 6.

1.4.4 – How many MICT questions as the current MICT is rather vague.

MICT is populated by Headquarters Air Force personnel. The number of MICT questions changes regularly. Average amount of questions is 250. MICT questions come directly from the AFIs, AFMANs and other guidance the contractor is already required to perform IAW the PWS. The time taken to process the checklist will depend upon how well the contractor is performing their contract related responsibilities.

WL Data updated in Amendment 6

1.5.13.2 – Average number of hazardous waste shipments generated per year.

6 WL Data updated in Amendment 6

1.5.14 – Number of MICT Stage 1 areas to inspect.

MICT is populated by Headquarters Air Force personnel. The number of MICT questions changes regularly. Average amount of questions is 50 for this requirement.

WL Data updated in Amendment 6

1.6.1 – Number of exercises per year.

Average 4 per year-WL Data will be updated in Amendment 6.

1.10.2 – Number of items to inspect monthly.

The number of fire extinguishers to inspect is subject to change due to changes in facility requirements. There has been an average of 20 extinguishers to inspect.

WL Data updated in Amendment 6

1.10.4 – Number of items to inspect monthly.

Currently 15 for this requirement. WL Data updated in Amendment 6

1.13.1 – Training duration and average number of records to maintain.

Training is a one-time 8 hour in classroom course and 1 hour annual Computer Based Training. The number of records to maintain cannot be calculated to an average number.

The contractor will be required to maintain all records in accordance with the records management program. ADDED TO PWS 1.13.1. in Amendment 6

1.14.9 – Average number of routine inspections per year.

One annual inspection and others are conducted as directed/required. ADDED to PWS in Amendment 6

1.15 – Average number of “no notice” inspections per year.

There have been as many as 5 no notice inspections for this requirement throughout one year. However they are “no notice” inspections. There’s no additional workload to consider as the contractor is responsible for being in compliance with all guidance and requirements that govern these processes on a daily basis.

2.2.10 – Average number of SDR’s per year that require analysis.

150 WL Data updated in Amendment 6

2.2.13 – Average number of SDR’s per year.

150 WL Data updated in Amendment 6

2.2.18 – Specific training and duration thereof.

This is as requested training for personnel outside of base supply for education in base supply functions. The Commander, FD and COR personnel will ensure the request are valid and the duration for training does not disrupt daily operations for the contractor.

Training averages 4 hours per person. WL Data updated in Amendment 6

2.4.9 – Average number of customer assistance visits.

40 per quarter. WL Data updated in Amendment 6

2.4.37 – Average number of accounts participating in PMRP.

63 WL Data updated in Amendment 6

2.4.39 – Average number of accounts participating in PMRP.

63 WL Data updated in Amendment 6

2.4.51 – Average number of work centers.

40 WL Data updated in Amendment 6

2.4.55 – Average number of maintenance activities with DIFM assets.

40 WL Data updated in Amendment 6 2.4.57, 2.4.60 and 2.4.61 – Average number of work centers.

40 WL Data updated in Amendment 6

2.5.12 thru 2.5.20:

2.5.12. Verify, prepare, and process inputs for item record indicative data changes (FIC) for local purchase/manufacture.

163 per Quarter WL Data updated in Amendment 6

2.5.13. Process requests as received for locally assigned Expendability Recoverability Reportability Cost Designator (ERRCD) and provide appropriate logistics center or supply chain management.

Past 17 months there have been zero locally assigned ERRCD loads. Probability exists to load in future, reason for inclusion to the PWS.

2.5.14. Review management data and process ERRCD and Equipment Management Code (EMC) as changes occur for local purchase daily.

Estimated 50 per year, no historical data

2.5.15. Verify, prepare, and process inputs to update unit of issue/unit price changes (FCU) for local purchase items only. Ensure there is a letter on file for all Local Purchase reason code “R” requests.

163 per Quarter WL Data updated in Amendment 6

2.5.16. Receive and coordinate on request to load, change, or delete organization records.

Workload data has number of ORG records maintained.

Workload data shows trends by month of records.

2.5.17. Submit data electronically for processing, controlling, and follow-up on AF Form 86.

Average one annually WL Data updated in Amendment 6

2.5.18. Update repair cycle records (FRR)

890 Annually WL Data updated in Amendment 6

2.5.19. Maintain exception control files and validate code. Estimated 250 semi-annually reviewed. Monthly review of Issue Exception (IEX) and Requisitions (REX) Code: 250 Records Number changes with stock requirements. WL Data updated in Amendment 6

2.5.20. Monitor, edit and maintain the Reporting Organization File.

Deleted from PWS in Amendment 6

2.5.21.1 thru 2.5.24:

2.5.21.1. Ensure all Plus Turn-ins are forwarded to the COR office.

Average 25 Plus Turn-ins for 2016. WL Data updated in Amendment 6

2.5.22. Perform unit price verification on L and P numbered items.

163 per Quarter WL Data updated in Amendment 6

2.5.23. Perform item and part number detail loads for local purchase and part number NSN’s only.

163 per Quarter WL Data updated in Amendment 6

2.5.24. R02 lists stock numbers within the ISG. Add, change, and delete all ISG’s for local stock numbers.

The R02 updates automatically. Add, change, and delete take place during the Quarterly review which currently had 163 NSNs for review. WL Data updated in Amendment 6

2.6.12 – Average number of Capital Assets and accounts possessing.

289 WL Data updated in Amendment 6

2.6.23 thru 2.6.25 – Average number of concept briefings per year.

4 WL Data updated in Amendment 6

2.6.29 – Average number of transactions processed.

120 Per Year WL Data updated in Amendment 6

2.6.32 thru 2.6.34 – Average number of transactions, training and duration.

120 transactions per year. 10 Training sessions per year. 3 hours each session. WL Data updated in Amendment 6

2.6.38 thru 2.6.41 – Average number of transactions.

2.6.38.

Transactions AVG 120 Annual in Workload Data. Obtaining letters is part of the transaction process. WL Data updated in Amendment 6

2.6.41 doesn’t all associate with an average number of transactions.

2.6.40 is just reviewing, managing and coordinating information from a listing

2.6.49 thru 2.6.53 – Average number of transactions.

This is identified within Appendix D for EAE workload. It’s a part of those numbers.

2.6.58 and 2.6.59 – Average number of transactions.

This is identified within Appendix D for EAE workload. It’s a part of those numbers.

2.7.2 – Average number of transactions.

3 Per Month WL Data updated in Amendment 6

2.8.1 thru 2.8.4 – CANN actions, downgrade and cancellation.

Average 50 monthly WL Data updated in Amendment 6

2.8.9 – Average number of AWP assets.

5 per month WL Data updated in Amendment 6

2.9.4 thru 2.9.7 – Average number of tasks performed.

2.9.4.Reset passwords Avg 20 per year WL Data updated in Amendment 6

2.9.5. Add/Delete ES-S Group/Capability 25 per year WL Data updated in Amendment 6

2.9.6. Establish general email address box –Contractor driven at time of Award

2.9.7. Provide Discrepancy Report – Provide list to COR personnel Quarterly or when listing is produced out of cycle. PWS para 2.9.7.Updated

2.10.3 – Average number of requests.

3 Per Annually WL Data updated in Amendment 6

2.11.5 and 2.11.6 – Average number of contractor created documents.

TIN workload is located within Appendix D.

2.11.9 thru 2.11.11 – Average number of transactions:

2.11.9. Process, maintain, and update all Material Deficiency Report (MDR) and Quality Deficiency Report (QDR) exhibits for supply and equipment items awaiting disposition

TO 00-35D-54.

Monthly average 10 WL Data updated in Amendment 6

2.11.10. Manage and maintain the Awaiting Parts (AWP) status program. An AWP checklist will be utilized IAW AFI 23-101, AFMAN 23-122 and AFH 23-123 for each AWP end item. Maintain the AWP checklist for a minimum of three months. COR will review this on a monthly basis.

Average 5 per month WL Data updated in Amendment 6

2.11.11. Process lean logistics and two level maintenance assets IAW AFMAN 23-122, AFI 23-101 and AFI 21-129, Two Level Maintenance and Regional Repair of Air Force Weapon Systems and Equipment.

34 NSNs coded as 2LM. Turn-in Transactions located in Workload Data.

2.11.16– Average number of daily updates performed by contractor.

There are on an average 232 details on the D23. At least one update per detail until item is turned-in. WL Data updated in Amendment 6 2.11.17– Average number of organizational refusals.

Average 5 monthlyWL Data updated in Amendment 6

2.11.24 – Average number of transactions processed.

This is identified within Appendix D for EAE workload. It’s a part of those numbers.

2.11.29 – Average number of items to inspect.

35 Items per month.

2.11.55 thru 2.11.57 – Average number of transactions processed This is identified in Appendix D with condition code changes.

2.11.59 – Average number of items.

WL Data updated in Amendment 6

2.11.71 – Average number of transactions.

5 per month. WL Data updated in Amendment 6

2.13.3 – Average number of exercises.

4 per year. WL Data updated in Amendment 6

2.13.12 – Does this include assets that are issued to on base organizations such as Security Forces. If so, is Appendix G reflecting these numbers?

This requirement does currently include the number of masks issued to on base organizations. Appendix G will be updated with the most current number of mask when it becomes available, as Appendix G states that the document is a living document which is subject to change due to mission requirement, etc.

2.17.3 – Average number of transactions.

3 per year. WL Data updated in Amendment 6

2.17.5 – Average number of transactions.

5 per month. WL Data updated in Amendment 6

2.18 – SS# 3 number of SDRs managed.

150 per year. WL Data updated in Amendment 6

2.18 – SS# 4, number of functional check items.

35 per month. WL Data updated in Amendment 6

2.18 – SS# 5, number of shelf life items maintained in stock.

800 shelf life items are on hand on a monthly basis to be managed. WL Data updated in Amendment 6

SF 1449

51. Q: CLIN 0004 makes reference to PWS 2.9, Information & IT Management Section.

However, there is no CLIN referenced to capture the pricing for PWS 2.10, Supply Systems Operations. Please provide the CLIN for pricing PWS 2.10.

A: Included in CLIN 0001

52. Q: The CLIN structure does not specify which CLIN PWS 2.11, Material Management is to be priced. Are we to assume that pricing for PWS 2.11 is to be located in CLIN 0001?

Please clarify which CLIN PWS 2.11, Material Management is to be priced.

53. Q: There does not appear to be a CLIN structure listed in Section SF 1449 to price the PWS 2.3 requirements. Is the Contractor to assume this is priced under CLIN X0001? If not, please provide where PWS 2.3 requirements are to be priced in Section SF 1449.

A: Yes, this is priced under CLIN 0001.

54. Q: There does not appear to be a CLIN structure listed in Section SF 1449 to price the PWS 2.13 requirements. Please advise as to which CLIN the IPE function is to be priced.

55. Q: Expanded Hours CLIN correlates to section 1.2.2 which states that Expanded hours could feasibly last for 30 days at 24x7. The CLIN is limited to $60,000.00. Is that number based on historical data of the contract to support a 30 day sustained timeframe?

A: In the PWS para. 1.2.2. The use of an Emergency Special Program (ESP) Code will be provided by HHQ to charge the added support. PWS para. 1.2. list 24 hours daily, Monday thru Sunday Functions such as MICAP, and Warehouse After Hours Support.

The War Readiness Function would need to extend their hours of work to cover the 24 hours. CLIN limit changed to $70,000.00 to adjust for additional hours to the estimated 30 day surge.

Instruction to Offerors/Evaluation

56. Q: Appendix O has been removed from the PWS. Request that the requirement to address Appendix O be removed from the RFP. (Reference: 52.212-2(b), An Offeror shall provide a description of its approach to and demonstrate its understanding of the Staffing Plan requirements as described in PWS paragraphs 1.1.6 through 1.1.10. and Appendix O.)

A: Appendix O and requirement to address removed from the PWS in Amendment 1

57. Q: Is a Mission-Essential Contractor Services Plan required with the proposal? If so, where shall it be included within the proposal? (Reference, 252.237-7023

CONTINUATION OF ESSENTIAL CONTRACTOR SERVICES (OCT 2010))

A: No, a Mission-Essential Contractor Services Plan is required during transition. PWS Para 1.2.4. changed to read, a “Mission-Essential Contractor Services Plan”.

58. Q: Please confirm a total of 3 completed Past Performance Questionnaires are desired.

(Reference: 52.212-1(5.2), Relevant Contracts. “Past Performance Information on three

(3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort.”) A: The 52.212-1 (Atch 1) and 52.212-2 (Atch 2) make no reference to a required number of PPQs. Please note Past Performance Questionnaires (RFP Attch 3), are different than the required Past Performance Information outlined in 52.212-1(5.2).

59. Q: This section [Page 6 of Atch_1, Para 5.0, Volume III - Past Performance] states “Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Past Performance Questionnaire.” Can you clarify to what specific “format contained” within the Past Performance Questionnaire you are speaking to?

A: Offerors should address the same information included in the Past Performance Questionnaire (Atch 3 of RFP).

60. Q: Please clarify how many past relevant contracts are expected for the prime offeror and teammates/subcontractors. Are prime offerors limited to 3 past relevant contacts total and the teammates/subcontractors limited to 2 per company? (Reference: 52.212-1(5.2), Relevant Contracts. Past Performance Information on three (3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort.”

“Also include information on two (2) recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort.”) A: Offerors are to submit PPI’s on 3 recent contracts that the offeror deems relevant in demonstrating their ability to perform some or all aspects of the base supply function.

Recent being defined as within the last 5 years from the date of issuance of the solicitation (see 52.212-2, Atch 2, para c(2)(i). In addition, offerors are to submit 2 recent contracts performed by each of the teaming partners/significant subcontractors they consider most relevant to demonstrate their ability to perform the proposed effort.

See para 5.2 and 5.3 in 52.212-1 (Atch 1). Para 5.3 discusses how to determine relevancy.

61. Q: Will the Government accept CPARS in lieu of PPQs?

A: No

62. Q: Paragraph 6.1.4 Pricing Data Requirements is also unclear – is the Government requesting offerors to provide “data other than certified cost or pricing”?

A: IAW 6.1.4, data other than certified cost or pricing data may be required to support a determination of price reasonableness. Para 6.1.1 and 6.1.3 allows offerors to submit data essential to documenting or supporting their price position should they deem it necessary to support their position and this shall be placed in the price volume. Additionally, if after receipt of proposals, the CO determines there is insufficient data to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

63. Q: Paragraph 6.1.3 Price Data states “All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal. This statement conflicts with the instructions in Section 7.0, paragraph 7.1.2 Services and Prices, which states “Complete pricing information in the line item/pricing schedule of the model contract.” Where does the Government want offerors to place the line item/pricing schedule (Schedule B) – in Volume IV or Volume V, or both?

A: Both. RFP Updated to resolve confusion. A completed Section B is required in Volume V. Pricing information included in Volume IV should adhere to the instructions provided in Atch 1, 52.212-1.

64. Q: Does the Government require a pricing narrative?

A: No

65. Q: Ref. 52.212-2 Subfactor 4, Offerors are instructed to “Detail the transaction processes required to Ship and Receipt NWRM”. According to AFI 23-101 and AFI 24-203 shipping is performed by the Traffic Management Office. Please clarify the offeror’s responsibility for shipping NWRM.

A: This subfactor states “Detail the transaction processes required to Ship and Receipt NWRM” meaning the contractor will be required to detail the base supply transactions and responsibilities that are required in order for NWRM assets to be shipped. Once all of the required Base Supply transactions/requirements have been met, the contractor will turn the assets along with all documentation over to the Traffic Management Office for their separate shipping processes. The contractor will only be responsible for the required base supply transactions identified in the Air Force guidance for NWRM as stated in the

PWS.

66. Q: Reference Addendum to FAR 52.212-2 and PWS Paragraph 1.1.9: The paragraph states “Provide a signed letter of intent and consent from the proposed key personnel…”.

Are we to provide the letter of intent and consent with our proposal?

67. Q: ADDENDUM TO FAR 52.212-1 – ATTACHMENT 1, Paragraph 6.1.6 addresses

FAR 52.217-8, Option to Extend Services and states “Offerors shall not provide additional pricing for these 6 months.” Does this mean that all the 50xx CLINs are to be left blank in Section B of the model contract (pages 29 – 33)?

A: Correct. Pricing for the Option to extend services (CLIN 5001-5010) will be formulated by the government by dividing Option Year IV proposed prices by two. No price proposal is required for CLIN 5001-5010.

68. Q: Please clarify the requirement for “List of Table”. Is this a list for tables only, or would this include figures such as the Organization Chart?

A: Yes, List of Table can include figures.

69. Q: Offeror requests the Government to consider the List of Table(s) to be non-counted pages. (Reference 52.212-1 (2.2.1), which states in part, “Each page shall be counted except the title pages, the table of content for each volume, and glossary of abbreviations and acronyms.” Also see 52.212-1(4.2.2), Volume Organization, which requires a “List of Table.”) A: List of Tables is not counted in the page count. See Amendment 6.

70. Q: Does an 11 x 17 sized page equal one or two pages?

A: 11 x 17 sized pages are to be used for tables, charts, graphs and figures wherever practical (RFP Atch 1 52.212-1 para 2.2.1.1(b)), and will be counted as one page.

71. Q: No Page Limit defined for Technical Portion of the proposal. Is this correct?

A: IAW Atch_1_52.212-1_v10 para 2.2.1, title pages, table of contents, list of tables, and glossaries are not included in page counts. Regarding the Technical Volume II, each subpart is allowed 10 pages.

72. Q: 48 CFR 22.2110 – Contract Clause; Solicitation para 52.212-5, c, (2), page 48 of 61 (FAR 52.222-41); and Solicitation para 52.212-5, c, (9), page 49 of 61 (FAR 52.222-62);

para 52.212- 5, e, (1), (xx) (flow down requirements). CFR 22.2110 states “Insert the clause at 52.222-62, Paid Sick Leave Under Executive Order 13706, in solicitations and contracts that include the clause at 52.222-6, Construction Wage Rate Requirements, or 52.222-41, Service Contract Labor Standards, where work is to be performed, in whole or in part, in the United States (the 50 States and the District of Columbia).”

Paragraph 52.212-5 (c) states the…