Questions and Answers Set 2.xlsx
XLSX spreadsheet 42 KB Posted
- Attached to
- Base Alarm Services - Los Angeles Air Force Base
- Solicitation number
- FA2816Q0002
- Issued by
-
Department of the Air Force
About this file
This is a Questions and Answers (Q&A) document Set 2 for solicitation FA2816Q0002, addressing clarifications on contract structure, pricing, performance requirements, and administrative procedures for Base Alarm Services at Los Angeles Air Force Base (LAAFB). The document contains 157 numbered questions and government responses covering the SF 1449, Performance Work Statement (PWS), and solicitation terms.
Key contract structure clarifications include: the Government will remove all Time & Materials (T&M) and Labor Hour clauses, making the contract fully Firm Fixed Price (FFP); CLIN X001 series is FFP and all-inclusive for direct/indirect labor and profit, while CLIN X002 series materials are Not-to-Exceed with COR/CO price verification; the base period runs nine months (April 19, 2026–January 18, 2027) with standard 30/60-day option exercise procedures; total evaluated price includes all option years with offerors responsible for proposing realistic pricing strategies; and wage rates will be provided per FAR 52.222-41 with price adjustments following FAR 52.222-43 procedures. Evaluation factors will be stated in descending order of importance: Technical Capability (significantly more important than price), Past Performance, and Price. Service requirements center on preventive maintenance, break-fix repairs, VPN maintenance, surveillance and access control system support across four primary LAAFB locations (LAAFB main, Fort MacArthur, Pacific Crest, Pacific Heights), with 24/7 four-hour onsite response SLAs for mission-critical systems; FFP pricing must be all-inclusive for after-hours and holiday coverage. Government-provided equipment includes office space (Building 272, Room C1227), spare parts funding, hazardous waste disposal, and GFP inventory; the contractor is responsible for employee clearances, OEM certifications (MDI, Vindicator, Advantor, Genetec), TAA-compliant parts, and compliance with AFI 31-101, AFI 31-501, AFM 14-304, and ICD 7051/7052 standards. The Government will issue corrected documentation at award regarding WAWF routing, supporting documentation requirements, backup cadence consolidation, and detailed performance metrics; a site visit will not be conducted, and the solicitation will be amended to remove contract type inconsistencies before Q&A closes.
View the file
Other files
Show all 15
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
Sheet1
| Number | Document | Section/Paragraph | Topic | Clarifying Question | Column1 |
| 1 | SF1449 Solicitation | Sec B – Supplies or Services & Prices (CLIN 0001, 0002; 1001–4002) | Pricing structure | CLINs show Firm Fixed Price (FFP) for services and a Not‑to‑Exceed (NTE) materials CLIN, yet the solicitation also incorporates time‑and‑materials/labor‑hour payment clauses. Can you explain the intended contract type(s) by CLIN (e.g., FFP for services only, materials at NTE, any T&M/LH elements), and how each will be invoiced and reconciled? | T&M Clauses will be removed, CLIN X001 series is FFP and should be all-inclusive for direct and indirect labor costs as well as profit. CLIN X002 series is explained in SF 1449. |
| 2 | SF1449 Solicitation | Sec B – CLIN 0002, 1002, 2002, 3002, 4002 | Materials CLIN | The parts CLINs prohibit labor, profit, and OH, but require COR and CO price verification before ordering. What is the approval workflow, lead‑time, and documentation we must submit to validate price reasonableness for parts under the NTE? | PWS 1.2 |
| 3 | SF1449 Solicitation | Sec B – CLIN 0002 narrative | Materials pricing basis | When you say pricing will be “verified by the contracting office,” which pricing standards will be applied (e.g., catalog/market price, historical purchase data, OEM quotes), and how will discounts (volume, GSA, BPA) be treated against the NTE? | CO will work with COR to ensure prices are fair and reasonable |
| 4 | SF1449 Solicitation | Sec B – CLIN 0002 narrative | Materials exclusions | Please clarify whether freight, taxes, expedite fees, import duties, and hazmat surcharges for parts are allowable under the materials NTE, and how they should be reflected on invoices. | Will be allowable with proper documentation and annotation |
| 5 | SF1449 Solicitation | Sec B – CLIN 0001 (Base), Options 1001–4001 | Period of performance | The PoP for the base period is 9 months (Apr 19, 2026–Jan 18, 2027). What drove the short base period, do you anticipate ramp‑up activities, and will pricing for base months differ from option years due to seasonality or initial transition efforts? | Internal decision |
| 6 | SF1449 Solicitation | Sec B – Options | Option exercise | Clause 52.217‑9 notes the Government may extend within 30 days, with a 60‑day preliminary notice; however, the bracketed fields aren’t completed. What are the specific advance‑notice windows you intend to use to exercise options? | will be deleting brackets, we will be using the standard 30/60. |
| 7 | SF1449 Solicitation | Sec B – Options | Option pricing | Will you evaluate offers based on total evaluated price including all options? Are there expectations for levelized pricing across option years, or do you expect escalation aligned to SCLS wage updates and OEM price trends? | Total price including all options years will be evaluated. Offerors are responsible for proposing a pricing strategy that they determine to be adequate and realistic for the life of the contract. |
| 8 | SF1449 Solicitation | Sec F – Deliveries or Performance | Place of performance & sites | The Deliveries section lists the 61 SFS address but the PWS covers multiple locations (LAAFB, Fort MacArthur, Pacific Crest, Pacific Heights). Can you provide a complete sites list with access constraints, escort requirements, and hours per site for planning? | Those 4 locations listed are the main locations. |
| 9 | SF1449 Solicitation | Sec E – Inspection & Acceptance | Acceptance criteria | Acceptance references “see Contract Terms and Conditions/PWS.” Can you provide the specific acceptance metrics (e.g., restoration times, pass/fail test thresholds) we’ll be judged against for preventive maintenance and break/fix? | The Government will not be providing prescribed performance metrics; instead, our technical experts will evaluate the soundness and feasibility of the Offeror's proposed approach for meeting the performance requirements outlined in the PWS |
| 10 | SF1449 Solicitation | Sec I – 52.232‑7006 WAWF | WAWF routing | The WAWF routing table includes DoDAACs but some fields are blank. Will you issue a final routing table at award, and can you confirm whether Invoice 2‑in‑1 will be used for service CLINs and Combo for materials CLINs? | Info will be provided at time of award. |
| 11 | SF1449 Solicitation | Sec I – 52.232‑7006 WAWF | Supporting docs | For WAWF submissions, what supporting documentation must accompany invoices (e.g., labor detail, timecards, parts pick‑lists, OEM quotes, COR approvals) for timely acceptance? | this will be explained to awardee at time of award |
| 12 | SF1449 Solicitation | Sec I – 52.232‑7006 WAWF | Acceptance timing | What is the expected Government acceptance timeline for WAWF submissions (services vs. materials), and will the CO or COR provide partial acceptance if a monthly package contains mixed work? | this timeline will vary |
| 13 | SF1449 Solicitation | Sec I – FAR 52.212‑4 (Alt I, Deviation) | Payments language | 52.212‑4 Alt I embeds T&M/LH payments logic, including hourly rates, overtime, other direct costs, and a ceiling price. If the service CLINs are FFP, how do you intend to apply these T&M mechanisms, or should we ignore those paragraphs when pricing? | T&M Clauses will be removed |
| 14 | SF1449 Solicitation | Sec I – FAR 52.232‑7 | T&M/LH clause | 52.232‑7 (Payments under T&M/LH) is present. Will any labor categories, hourly rates, ceilings, or ODC elements be established at award? If not, what basis should we use to build and submit rate cards and labor mix assumptions? | T&M Clauses will be removed |
| 15 | SF1449 Solicitation | Sec I – 52.232‑7(b)(6) | Discounts & rebates | The clause requires giving credit for cash/trade discounts, rebates, and salvage. How will this be tracked and applied to the Government for parts under the NTE, especially when OEMs issue rebates after the fact? | will discuss tracking process at time of award |
| 16 | SF1449 Solicitation | Sec I – 52.232‑7(d)-(e) | Ceiling price | Please identify the ceiling price(s) you intend to include at award and how we should forecast burn rates and provide 85% notifications if no T&M labor categories or ODCs are ultimately used. | T&M Clauses will be removed |
| 17 | SF1449 Solicitation | Sec I – 52.212‑4(i)(1)(E) | Overtime | Will overtime be allowed for alarm emergencies outside 0700–1600? If so, how should we price it (e.g., premium factors), and what is the pre‑approval process? | CLIN X001 series is FFP and should be all-inclusive for direct and indirect labor costs as well as profit. This would include after hour calls. |
| 18 | SF1449 Solicitation | Sec H – Special Contract Requirements | Security & exclusions | Security prohibitions/exclusions clauses are included. Please specify any brand exclusions (e.g., Huawei, ZTE, Kaspersky) relevant to cameras/NVRs/switches so we can pre‑screen OEMs and their firmware. | We will be adding FAR 52.240-91 |
| 19 | SF1449 Solicitation | Sec L – Instructions to Offerors | Submittal content | The evaluation section lists Technical/Past Performance/Price but lacks subfactor detail. What technical subfactors (e.g., staffing, OEM certifications, PM plan, cybersecurity plan) and page limits do you expect? | see solicitation |
| 20 | SF1449 Solicitation | Sec M – Evaluation Factors | Relative importance | The evaluation factor weights (price vs. non‑price) aren’t completed. Can you state whether non‑price is more important than price, and whether risk/approach will be explicitly scored? | We will update the solicitation and SF 1449 to state "The evaluation factors are listed in descending order of importance: Technical Capability, Past Performance, and then Price. All technical factors, when combined, are significantly more important than price." |
| 21 | SF1449 Solicitation | Sec L/M – Only One Offer (DFARS 252.215‑7008) | Cost/price data | If only one offer is received, what additional data do you expect (e.g., cost breakdowns, rate build‑ups), and will you allow updates/revisions post‑submission for fairness? | N/A |
| 22 | SF1449 Solicitation | Sec I – 52.222‑41 / 52.222‑42 | SCLS applicability | The Statement of Equivalent Rates table is blank. Will you issue a Wage Determination and provide equivalent federal rates/fringes for expected labor categories (e.g., Alarm Tech, CCTV Tech, Network Tech)? | FAR 52.222-41, we will be including wage rates |
| 23 | SF1449 Solicitation | Sec I – 52.222‑43 | Price adjustment mechanism | How will SCLS price adjustments be handled for option years if WD rates change—FFP unit pricing adjustments, or a separate economic price adjustment? | Follow procedures in FAR 52.222-43 |
| 24 | SF1449 Solicitation | Sec I – 52.245‑1 Government Property | GFP handover | The PWS mentions a GFP inventory within 20 workdays; SF1449 includes GFP clauses. Can you confirm the exact GFP list, its condition/status, and any repair/replace responsibility on the contractor? | All cost associated with repaire and or replacement is a governement cost |
| 25 | SF1449 Solicitation | Sec I – 52.245‑1 / WAWF UID | Item Unique Identification | Will any items we deliver (e.g., NVRs, switches, UPS, servers) require UID marking and reporting per DFARS 252.211‑7003? If so, which CLINs and thresholds apply? | See DFARS 252.211-7003 |
| 26 | SF1449 Solicitation | Sec I – 52.240‑1 (Drone Act) | UAS prohibition | If any aerial inspection tools (UAS drones) are proposed for pole/camera inspections, will they be prohibited under 52.240‑1, and if so, what alternative methods do you prefer? | Yes, drones are prohibited |
| 27 | SF1449 Solicitation | Sec I – Cyber clauses (DFARS 252.204‑7012 dev.) | Cyber incident reporting | Please outline the CDSI handling expectations for alarm/CCTV data (e.g., retention, encryption, reporting of incidents), and whether any system boundary diagrams will be provided. | reference the PWS for instruction |
| 28 | SF1449 Solicitation | Sec L – 52.212‑1 (Deviation) | Proposal format | Do you require volumized proposals (Vol I Tech, Vol II Price, Vol III Past Performance) and any specific templates for staffing matrices, OEM certs, and past performance questionnaires? | see solicitation |
| 29 | SF1449 Solicitation | Sec E/F – Inspection/Deliveries | Reporting cadence | The PWS requires monthly status reports. Should report submission be synchronized with WAWF invoice cycles, and will acceptance of the monthly report be a payment prerequisite? | Every employee is required to provide a service report, should be part of the company requirements. Provide the reports as outlined in the PWS. |
| 30 | SF1449 Solicitation | Sec B – CLIN structure | CLIN breakout | Would you consider separate CLINs for Preventive Maintenance, Break/Fix Service Calls, Training, and Software Maintenance to simplify pricing and acceptance? If not, how should we allocate costs within the single service CLIN? | no, should be all-inclusive for direct and indirect labor costs as well as profit. |
| 32 | PWS | 1.1 Basic Services | Small installs & relocations | “Small installations/relocating equipment when required due to construction” appears out of scope for FFP maintenance. What triggers (e.g., CE projects) will cause these tasks, and how should they be priced (FFP service CLIN vs. materials NTE vs. separate mods)? | Work within scope. |
| 33 | PWS | 1.1 Basic Services | OEM/software mix | The PWS references MDI, Vindicator, Advantor, Genetec. Which software licenses/support agreements are Government‑owned vs. Contractor‑furnished, and who funds renewals/upgrades? | Reference the PWS |
| 34 | PWS | 1.1 Basic Services | Quarterly failover testing | The PWS requires quarterly MDI server failover testing. Please specify the test plans, success criteria, acceptable downtime, and whether tests occur in production or a staging environment. | All testing is the reponsibility of the contractor, follow MFG suggestions for each task |
| 35 | PWS | 1.2 Spare Parts Availability | On‑site spares policy | Spare parts must be maintained on‑site “providing funding is available.” Who funds the initial spares stock, what minimum quantities are required, and how is replenishment authorized? | The initial stock is on site PWS 1.2 |
| 36 | PWS | 1.2 Spare Parts Availability | Same‑make/model requirement | Repairs must use same make/model; alternates require prior approval. Given OEM end‑of‑life realities, can you provide an approved replacement matrix per device type to avoid repeated approvals and expedite repairs? | This is the responsibilty of the contractor to provide equipment that that is TAA compliant. |
| 37 | PWS | 1.2 Spare Parts Availability (list) | Approved vendor list | The spares list includes specific items (e.g., AXIS S2208 Recorder, Cisco 3850 FAN). Will you issue an Approved Products List (APL) with current model numbers, firmware baselines, and bid alternates? | it is the responsibilty of the contract to provide all TAA compliant parts or equipment. |
| 38 | PWS | 1.2 Spare Parts Availability | GSA pricing | The PWS says use GSA pricing when applicable. If a vendor is not on GSA, what pricing basis is acceptable (e.g., OEM MSRP less standard discount), and do you require competition among resellers for parts buys? | competition among resellers would be the easiest method to determine if the pricing is fair and reasonable. |
| 39 | PWS | 1.3 Testing & Evaluation | Standards alignment | Testing references AFI 31‑101, AFI 31‑501, AFM 14‑304, ICD 705‑1/705‑2. Will the Government provide specific test procedures, templates (e.g., AF Form 340), and frequency tables per facility type (SCIF vs. non‑SCIF)? | It is imperative that a contractor know and understand the manuels that govern requirements within the Federal Government |
| 40 | PWS | 1.3.1 | Recordkeeping restrictions | The PWS states contractor will not maintain copies of test records and will log activities in a logbook. How do you want electronic logging, audit trails, and data retention handled to meet QA while complying with restrictions? | All testing done in special access areas will be the property of the facility. Outside of that alarm test records will placed in a binder and kept as a logged record. Some exceptions will be made to accommodate the contractor |
| 41 | PWS | 1.4 Scheduled Maintenance | Off‑hours testing | Alarm testing may occur after hours/weekends. What notice window and approval chain are required for off‑hours testing, and how should we price any premium labor or escort costs? | That is at the request of the facility and escorts are provided by the facility |
| 42 | PWS | 1.4.1 Maintenance Plan | Active monitoring | Please clarify expectations for active monitoring of surveillance‑associated network equipment (e.g., SNMP polling, syslog review, thresholding). Do you require a NOC‑style service with SLAs? | Check the system daily |
| 43 | PWS | 1.4.1.1 Logbooks | Electronic logs | May we use an electronic CMMS or ticketing system instead of physical logbooks, provided it meets security and audit requirements? If yes, what fields must be captured? | PWS 1.4.1.1 |
| 44 | PWS | 1.4.1.2 Cisco Network Assistant | Network access | The PWS states 61 CS provides Network Assistant support. What access level (read vs. admin) will be granted, and how do we request changes to camera/switch configs without violating base network change‑control? | 61 CS provides network support for the infastructure no tht equipment tiesd to the base network that is the responsibility of the contractor |
| 45 | PWS | 1.4.1.3 RAID Manager | HDD replacements | For RAID rebuilds, do you require specific OEM drives, and what is the mean time to repair expectation from failure detection to full rebuild in production? | Replace bad drives wih MFG suggest equipment. As soon as possible |
| 46 | PWS | 1.4.2 Daily Tasks | BDOC coordination | Daily check‑ins with BDOC are required. What format (in‑person vs. electronic), time, and content do you expect (e.g., alarm history, camera health, background programs)? | Contractors responsibility to come up with a schedule The contractors will report ot the desk daily in person |
| 47 | PWS | 1.4.2.4 Automated backups | Backup cadence inconsistency | Backups are described as quarterly with “system designed to automatically back up every 60 days.” Which interval governs for compliance, and what retention period is required for the Genetec Directory and AutoVu databases? | Check quarterly just to insure that backups are working properly |
| 48 | PWS | 1.4.2.5 Spare BDOC workstation | Spares funding | The PWS says “providing spares are available.” Are spare workstations GFP or contractor‑furnished, and if contractor‑furnished, how should they be priced (materials NTE vs. service CLIN)? | The government provides funding for all spare parts |
| 49 | PWS | 1.4.2.6–1.4.2.13 Monthly tasks | Patch management | For patches/firmware updates (switches, cameras, OS, DB), do you require a test bed, rollback plans, and CAB approval? Please define maintenance windows to avoid mission disruption. | Patches are only required if the system configuration is changed, also read the PWS |
| 50 | PWS | 1.4.2.10.1 Genetec updates | OEM engagement | The PWS instructs checking with Genetec. Will the Government provide current SMA/support contracts with Genetec, and should we include OEM support hours in our price? | The contractor must have the proper certifacation for tech support. That is the contractors responsibity |
| 51 | PWS | 1.4.2.11 Visual inspection | CE Form 332 dependency | The PWS notes 61 SFS submits Form 332 to CE for corrections. What is the typical turnaround time, and how should we track awaiting CE action in performance metrics? | Irrelevant question |
| 52 | PWS | 1.4.3 Quarterly tasks | Pole inspections | For folding poles, do you require certified fall protection technicians, and are cranes/lifts Government‑provided or contractor‑furnished? How should such equipment be priced? | Irrelevant question |
| 53 | PWS | 1.4.3.3 UPS batteries | Warranty handling | The PWS references APC warranties. Will the Government provide proof of purchase for warranty claims, or must the contractor manage warranty registration for replacement units installed under this contract? | This the resposibility of the contractor |
| 54 | PWS | 1.4.3.5 Power cycle | Annual power cycling | Power cycling network equipment annually can be disruptive. What coordination and blackout windows are required, and do you prefer rolling restarts by segment? | Coordinate with BDOC |
| 55 | PWS | 1.4.3.6 SD card replacement | Funding dependency | SD cards replaced at 3‑year mark “providing funding is available.” Will you establish a funded replacement program with baseline counts, or should we propose a per‑unit price under the materials CLIN? | The contractor is responsible for IDing SD card replacement if required |
| 56 | PWS | 1.4.3.7 UPS batteries | Lifecycle plan | UPS batteries expected life 3–5 years with semi‑annual testing. Can you provide a current inventory with install dates to build a replacement schedule and budget forecast? | No documentation |
| 57 | PWS | 1.4.3.8 Failed equipment | Repair vs. replace decision | “Reasonable time period” is defined relative to install time. Can you provide thresholds (e.g., 4 hours field repair vs. 2 hours swap) and priorities by site type (SCIF vs. perimeter vs. BDOC)? | will vary on complexity and urgency |
| 58 | PWS | 1.5 Service Calls | Response SLAs | The PWS requires onsite within four hours for facilities under AFI 31‑101 and special access areas. Is this 24x7, including holidays, and how are non‑mission areas prioritized? | Yes |
| 59 | PWS | 1.5 Service Calls | Contacting techs | What dispatch mechanism (BDOC call tree, ticket system) will be used, and do you require a single dedicated phone line or on‑call rotation roster from the contractor? | ittelevant question |
| 60 | PWS | 1.6 Service Logs | Government review | Who (COR, Alarm System Administrator, SSO) will review logs, how often, and do you require standard metrics (MTTR, first‑time fix, backlog) in the logs? | Read the PWS |
| 61 | PWS | 1.7 Software Products | Licensing & patches | The PWS requires corrections of substantial defects and periodic patches. Are software maintenance agreements (SMA) funded by the Government, and which products (MDI/Vindicator/Advantor/Genetec) are covered? | read the PWS |
| 62 | PWS | 1.8 Reporting | Monthly status report | Please define report content templates, required KPIs, and whether training, patching, and database backups should be summarized separately by site. | Contractor format expectable |
| 63 | PWS | 1.9 Training | Audience & dates | Two 8‑hour training sessions per year are required. Who approves the curriculum, how many students per session, and do you require hands‑on lab vs. lecture? | The government provides the location outside of special access reas, Special access areas will determing the locations. Read the PWS |
| 64 | PWS | 1.9 Training | Materials & delivery | Should we provide student guides, quick reference cards, and video recordings? Is training in‑person only, or may we use secure virtual delivery for refreshers? | Read the PWS |
| 65 | PWS | 2. Service Summary | Performance thresholds | The Service Summary references objectives but lists only monthly reporting and training frequency. Can you provide thresholds and deductions/credits for missed PMs, late responses, or repeated defects? | All PMs are the responsibility of the contractor to schedule. Missed PM will be noted on a SAR report |
| 66 | PWS | 3. Government Furnished Property | Office space & utilities | Office space will be furnished (Bldg 272, rm C1‑227). What square footage, access controls, network connectivity, and storage capacity are available for spares and test equipment? | Irrelevant question |
| 67 | PWS | 3.3 Government‑Furnished Services | Hazardous waste | For battery and electronic waste disposal, do you provide base disposal services, or must the contractor arrange off‑site disposal? How is cost handled? | Government provided |
| 68 | PWS | 3.3.4 Security Forces | Security coordination | Who is the primary POC at 61 SFS for operational coordination (updates, outages), and do you require weekly syncs during the first 90 days? | POC will be given at time of award |
| 69 | PWS | 4. General Information | Employee restrictions | The Government reserves the right to restrict employment. Can you outline the adjudication process, timelines, and replacement staffing expectations if a tech is denied access? | COR’s documentation justifying removal of an employee as out line in the PWS |
| 70 | PWS | 4.1 Contract Roles | On‑site Manager | The Contract Manager must perform PM tasks when onsite. Should we assume full‑time on‑site presence, or is a hybrid presence acceptable? How should we price manager hours? | Full time |
| 71 | PWS | 4.1.6 Contractor Employees | Clearances | Final Secret facility clearance required; interim possible within 30 days. Will the Government sponsor clearances, and what are the processing timelines you typically see at LAAFB? | The contractor is responsible for employss clearence |
| 72 | PWS | 4.1.8 Certifications | OEM certificates | The PWS requires MDI/Vindicator/Advantor dealer licenses and Genetec certification. Please specify minimum certification levels (e.g., Genetec Omnicast/AutoVu) and how many certified personnel must be on staff. | The contractor should have mutiple staff members that are certified and able to perform the tasks outline in the contract |
| 73 | PWS | 4.1.8 Certifications | UL compliance | You require compliance with UL for IDS/ACS/Surveillance installation. Which UL standards (e.g., UL 2050) apply to maintenance vs. installation, and what documentation is required? | This is something the contractor should know |
| 74 | PWS | 4.1.9 Controlled Areas | SCIF access | Contractor access is escorted only in SCIFs. How should we plan durations for escorts, and will escort availability impact response SLAs? | This is not the responsibility of the contractor |
| 75 | PWS | 4.1.9.1–4.1.9.5 | Badging & CAC | AF Form 1199 CD, CE issuance rules, and revocation/extension details are listed. Can you provide the badging process map, expected processing time, and work‑hour limitations for temp badges? | The contractor will be issued a Access badge and Comon Access Card |
| 76 | PWS | 4.1.11 Parking | Parking policy | Are service vehicles allowed near secured areas for rapid response, and do you issue temporary passes for vendor deliveries of equipment? | This would only apply to first responders, deliveries are routed through 61SFS to coordinate deliveries |
| 77 | PWS | 4.1.13 Dress & Appearance | Uniforms & ID | Do you require uniformed attire with company logo every day, and are there additional markings (e.g., high‑viz vests) required at perimeter sites? | PWS 4.1.13 |
| 78 | PWS | 4.2 Hours of Operation | Coverage hours | Hours are 0700–1600 Mon–Fri except federal holidays, yet service calls require 4‑hour onsite response for certain facilities. Do you expect after‑hours on‑call coverage, and how should we price that coverage? | CLIN X001 series is FFP and should be all-inclusive for direct and indirect labor costs as well as profit. This would include after hour calls. |
| 79 | PWS | 4.2.3 Crisis performance | Essential services | During crisis declarations, what staffing minimums, access provisions, and mission continuity plans must we support, and will there be priority passes issued? | The contractor is required to perform all duties and responsibility as outline in the PWS. The is no change to your responsibilities as a contractor. |
| 80 | PWS | 4.3 Quality Control (QCP) | QCP content | Beyond inspection systems and recordkeeping, do you require process capability metrics, root‑cause analyses, and CAR response timelines in the QCP? | |
| 81 | PWS | 4.3.2 Government QA | Observation initialing | When COR observations are initialed by the manager, how are disagreements documented and resolved, and do they affect CPARS? | Will be done via CPARS and CO will review validity |
| 82 | PWS | 4.4 Meetings | Meeting cadence | Weekly meetings may be required during the first month. Will you provide a standard agenda, and do you expect action item tracking and risk logs? | this will be explained to awardee at time of award |
| 83 | PWS | 4.5 Administrative Records | Ownership of records | Records become Government property and remain in place. How should we handle contractor operational docs (e.g., SOPs, configs) that typically remain proprietary? | Meeting only to review first steps of progress |
| 84 | PWS | 4.6 Safety | Safety plan | You require a Safety Plan for Operational Contracting. Are there base‑specific safety standards (e.g., confined space, hot work) we must incorporate, and is there a CDRL template? | OSHA compliance will be mandatory and on base-specific safety standards will be briefed to awardee. |
| 85 | PWS | 4.7 Phase Out | Transition | At contract end or changeover, what knowledge‑transfer deliverables (as‑built updates, credential rotations, admin rights handback) do you expect, and should we include transition hours in base pricing? | Reference PWS |
| 86 | PWS | Appendix A – Workload | Device totals accuracy | The appendix lists extensive device IDs and totals. Can you confirm current counts, identify retired devices, and provide a delta list since publication? | There might be some system coming offline at time of contract award, and others system following soon after. Equipment count is correct. |
| 87 | PWS | Appendix A – Workload | Critical assets | Which devices/sites are considered mission‑critical (e.g., BDOC, gates, SCIFs) with higher response priority and stricter uptime targets? | All IDS equipment and surveillance equipment is considered mission critical |
| 88 | PWS | Appendix A – Workload | Data accuracy | Some device listings have typos/misaligned formatting (e.g., “Genetic” vs. Genetec). Will you issue a cleaned data spreadsheet for planning and CMMS import? | Irrelevant questions |
| 89 | PWS | Appendix B – GFP | GFP completeness | Appendix B lists only three items (laptop, printer, monitor/keyboard/mouse) whereas the PWS references office space and other resources. Is there a full GFP catalog besides Appendix B? | Reference PWS |
| 90 | PWS | Appendix C – Definitions | Rogue devices | “Rouge devices” are defined. Do you expect the contractor to detect/isolate rogue devices (e.g., unauthorized IP cameras) and perform forensic analysis or merely report? | We expect the contractor to do there the job as outline in the PW. |
| 91 | PWS | Appendix D – BDP | Vetting & DBIDS | For contractor staff, will DBIDS enrollment, NCIC checks, and fitness determinations be handled prior to start, and what lead times should we plan? | Personnel from the company will be handled as visitors, the individuals assigned to the facility will have CAC and Access control cards. DBIDS will be issued to all nonessential personnel. |
| 92 | PWS | Appendix D – BDP | Privatized housing | Work includes Pacific Crest/Pacific Heights. What are access procedures for privatized housing, and are there resident notification requirements before maintenance? | Coordinate with 61SFS prior to dispatching to Crest and Heights |
| 93 | PWS | Appendix D – Publications | Changes clause | The appendix states immediate implementation of changes that decrease price and a 30‑day proposal for increases. How will scope changes be communicated (CDRL vs. mod), and will equitable adjustments be processed under REAs quickly? | in and out of scope changes may be done via mod and will vary depending on said scope |
| 94 | SF1449 Solicitation | Sec I – 52.245‑9 Use and Charges | Use of Govt property | Will we have access to any Government test equipment (fiber testers, lifts), and if so, what are the use/charge rules under 52.245‑9? | No |
| 95 | SF1449 Solicitation | Sec I – 52.244‑6 Subcontracts | Subcontract flowdown | Are there any specific subcontracting restrictions (e.g., similarly situated entity rules) beyond 52.219‑14 that would affect OEM/VAR partners? | the main restrictions are listed in the solicitation |
| 96 | SF1449 Solicitation | Sec I – 52.240‑92 Security Requirements | Cyber & physical | Can you provide the Security Requirements attachment referenced by deviation clauses, including data handling and physical hardening for contractor‑managed servers? | Have you ever maintained a government contract? |
| 97 | SF1449 Solicitation | Sec I – 52.223‑23 Sustainable Products | Sustainability | Do you require environmentally preferable products (e.g., energy‑efficient UPS, recycled packaging), and how will compliance be validated? | Follow government standards |
| 98 | SF1449 Solicitation | Sec I – 52.228‑5 Insurance | Insurance levels | What minimum insurance limits (CGL, auto, workers’ comp) are required for work on Government installations under this contract? | FAR 52.228-5 |
| 99 | SF1449 Solicitation | Sec I – 52.247‑7023 Sea Transport | Logistics | If parts ship from overseas, do sea transport clauses apply, and will you require proof of U.S.‑flag carriage or is air freight preferred for critical spares? | should not apply |
| 100 | SF1449 Solicitation | Sec I – 52.229‑12 Tax on Foreign Procurements | Tax mechanics | If any OEMs are foreign, how should we handle the 2% excise tax and W‑14 submissions—do you prefer vendors with domestic distribution to avoid the tax? | should not apply |
| 101 | PWS | 1.1 Basic Services | Cleaning of cameras | The PWS requires daily checks and quarterly cleaning of domes. Are there site‑specific constraints (e.g., coastal corrosion at Fort MacArthur) we should plan for with enhanced maintenance? | No |
| 102 | PWS | 1.4.2.12 PTZ testing | PTZ motion issues | For “negative feedback/spotty motion,” do you expect motor replacements to be treated as materials, and will there be an approved vendor list for PTZ repairs vs. full replacements? | Check all cameras make any necessary adjustment, if the camera needs to be replaced and stock is available replace unit. The contractor must ensure all equipment ordered meets all TAA requirements |
| 103 | PWS | 1.4.2.13 Card readers | Reader cleaning | Quarterly reader cleaning is required. Are any readers in restricted zones requiring extra coordination, and will consumables (cleaning kits) be Government‑provided? | General locations are accessible to everyone on base, any areas that are controlled will be handled accordingly . Cleaning material will meet environmental standard. |
| 104 | PWS | 1.7 Software Products | Change control | Are there formal change control boards (CCB/CAB) for alarm/ACS/CCTV changes, and do you require RFC documentation with risk assessment and backout plans? | Irrelevant question |
| 105 | PWS | 1.8 Reporting | Release notes | For each installed upgrade/patch, you ask for release notes itemizing impacts. Do you also require lab validation summaries and pilot results prior to production rollout? | As out lined in the PWS |
| 106 | PWS | 4.1.8 Certifications | Special video analytics | You require “thorough working knowledge of special video analytic software installed at LAAFB.” Please list the analytics platforms/modules (e.g., Genetec VMS analytics, LPR models) and required competency evidence. | Reference the PWS |
| 107 | PWS | 4.2.2 Federal Holidays | Holiday service | If a federal holiday is observed, but a mission‑critical system fails, do you expect holiday response, and how should such premium coverage be priced? | CLIN X001 series is FFP and should be all-inclusive for direct and indirect labor costs as well as profit. This would include after hour calls. |
| 108 | PWS | 3.2 Equipment – LAN | Network restrictions | The PWS says no wireless network allowed for contractor use. Are cellular hotspots for remote diagnostics also prohibited, and will wired VPN access be provided? | No |
| 109 | PWS | 3.1.2 HAZMAT | MSDS requirements | You require a list of all hazardous materials with MSDS. Please confirm which cleaning solutions, battery types, and aerosols are permitted on base. | The conttrator can contact environments on base for a list of items not permitted. |
| 110 | PWS | 1.4.2.4 Backups | Backup storage | Backups must be stored on a Government‑provided removable device. What is the required encryption standard, chain of custody, and off‑site storage policy? | Irrelevant question |
| 111 | PWS | 1.4.2.5 Spare BDOC workstation | DR exercises | Beyond monthly power‑on tests, do you require disaster recovery (DR) drills to swap BDOC workstations and validate operator readiness? | No |
| 112 | PWS | 1.3.1 Standards | AFI/ICD conflicts | If AFI requirements conflict with ICD 705 guidance in SCIFs (e.g., testing intervals), which standard will prevail, and will you issue clarifying policy? | Particular facilities need to meet a particular requirements that is what separates the manuals |
| 113 | PWS | 1.4.3.4 Workstation fans | Preventive cleaning | Semi‑annual workstation cleaning is required. Are dust covers permitted, and do you have ESD requirements for servicing BDOC/servers? | Yes |
| 114 | PWS | 1.4.3.8 Warranty | Out‑of‑warranty replacements | When hardware is out of warranty, should we propose standardized replacement SKUs and unit pricing now, or will replacements be handled case‑by‑case under the parts NTE? | Equipment is end of life |
| 115 | PWS | 1.5 Service Calls | Special access facilities | For SCIF alarms, who authorizes masking/unmasking during repairs, and do you require SSO presence for any particular procedures? | Irrelevant question |
| 116 | PWS | 1.9 Training | Train‑the‑trainer | You intend a train‑the‑trainer model. Will you designate unit trainers, and should we include certification tests or skills validation at the end of training? | All initial training will be conducted by the contractor |
| 117 | PWS | 2.2 Performance Evaluation | CARs & remedies | The PWS references CARs under 52.246‑4. What are the graduated remedies (e.g., withholds, re‑performance), and do you use award term/fee incentives for superior performance? | will be discussed with awardee if situation arises |
| 118 | PWS | 3.3.3 Emergency medical | EMS | If contractor personnel require EMS, are there on‑base first‑aid requirements (kits, training) and must we include medical surveillance for specific tasks (lifts, heights)? | No the local emergency services (FD) will be notified. Follow UL safty standards |
| 119 | PWS | 4.1.12 Physical Security | End‑of‑day security | What are the expectations for after‑hours secure storage of contractor tools/spares in Government space, and do you require serial‑number logs for all items? | PWS 3.1 |
| 120 | PWS | Appendix A – Cameras/LPR | LPR calibration | License Plate Reader cameras are listed at gates. Do you require periodic calibration and accuracy reporting (read rates, false positives), and how should this be documented? | No |
| 121 | PWS | Appendix A – UPS | UPS topology | Can you provide a single‑line diagram of power to alarm servers/NVRs/BDOC to validate UPS capacity and plan battery replacements strategically? | No |
| 122 | PWS | Appendix A – NVR/Archivers | Storage sizing | What are the recording retention policies (days per camera/resolution), and do you require storage growth planning or tiered archiving? | Follow AFI requirements |
| 123 | PWS | Appendix A – Readers/ACS | Reader types | Please provide a reader technology inventory (prox, smartcard, CAC, turnstile), encryption standards, and any migration plans we should accommodate. | Irrelevant question |
| 124 | PWS | 1.2 Spare Parts | Inventory system | The contractor must maintain an up‑to‑date inventory list. Do you require integration with base property systems, barcode labeling, and periodic cycle counts with Government witnessing? | No |
| 125 | SF1449 Solicitation | Sec I – 52.212‑5 (Deviation) | Clause flowdown | Are there any agency‑specific deviations we must flow down to subs beyond what is already listed (e.g., AFMC supplements), and will you provide a flowdown checklist? | No |
| 126 | SF1449 Solicitation | Sec E – Inspection & Acceptance | Service acceptance | Do you require service call tickets to be individually accepted by the COR, or will acceptance be at the monthly roll‑up level? What is the dispute process for questioned tickets? | Service tickets are not part of the requirements, worked performed will be noted on monthly services logs as per the PWS. If the contractor wants to maintain services so be it. |
| 127 | SF1449 Solicitation | Sec L – HUBZone PEP | Price evaluation preference | HUBZone PEP (10%) is included as a deviation. Will you request waiver declarations from HUBZone offerors at submission, and how will you apply the factor across multi‑CLIN pricing? | deleting clause as it applies to full and open competition |
| 128 | PWS | 1.4.2.1 Camera cleaning | Environmental considerations | Fort MacArthur is coastal. Do you require anti‑corrosion measures or protective housings for cameras, and should we propose a higher cleaning frequency? | If equipment is to be replaced the contractor should take the environmental factors into consideration and order equipment accordingly. Cleaning process is identified in the PWS |
| 129 | PWS | 1.4.3.1 Exterior domes | Cleaning solutions | What approved cleaning solutions and cloth types do you mandate to avoid dome scratching and coating damage? | Reference the MFG suggestion for cleaning |
| 130 | PWS & SF1449 | Cross‑document consistency | Alignment of SOW & CLINs | There are several cross‑document inconsistencies (FFP service CLINs vs. T&M payment clauses; backup cadences; undefined evaluation weights). Will you issue an amended solicitation to reconcile these before Q&A closes so offerors can price accurately? | Yes |
| 131 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Contract Type Conflict | The solicitation includes T&M payment clauses (FAR 52.212‑4 Alt I, FAR 52.232‑7) while all service CLINs are labeled Firm‑Fixed‑Price. Can the Government clarify the intended contract type and whether any amendment will align clauses and CLIN types? | T&M clauses will be removed |
| 132 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Contract Type Conflict | If the contract is intended to be fully FFP, will the Government remove the T&M hourly‑rate, overtime, and cost‑reimbursable language to avoid confusion during pricing and later administration? | T&M clauses will be removed |
| 133 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Contract Type Conflict | If hybrid FFP/T&M is intended, will the Government publish a CLIN‑to‑clause mapping showing which clauses apply to which CLINs and what labor categories or ODCs must be priced? | T&M clauses will be removed |
| 134 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Rate Structures | Will the Government issue labor category definitions and a rate table template if any T&M elements or hourly billing mechanisms are expected? | T&M clauses will be removed |
| 135 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Rate Structures | If no hourly billing is intended, how should offerors handle clause requirements for documenting hours, approving overtime, and tracking ceilings referenced in 52.232‑7? | T&M clauses will be removed |
| 136 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | FFP Pricing Scope | Will the Government specify which tasks (e.g., relocations, small installs, construction‑driven moves) are FFP‑included and which require T&M or modification support? | T&M clauses will be removed |
| 137 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Cost Structure Alignment | Would the Government consider restructuring CLINs into clearer categories (e.g., PM, Service Calls, Training, Software Support) to reduce pricing ambiguity? | No |
| 138 | SF1449 & PWS (Cross‑Document) | Contract Type vs Clauses | Amendment Request | Will the Government issue an amendment to reconcile contract type inconsistencies before the Q&A period closes so offerors can price accurately? | Yes |
| 139 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Backup Frequencies | The PWS lists multiple conflicting backup cadences (daily, quarterly, every 60 days). Will the Government provide a single authoritative backup schedule for all systems? | Yes |
| 140 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Backup Frequencies | Until clarified, should offerors assume the highest frequency (most labor‑intensive) backup cadence, or will the Government define the intended requirement via amendment? | No |
| 141 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | System‑Specific Cadence | Will the Government publish system‑by‑system backup intervals for MDI, Genetec Directory, AutoVu, NVRs, and Archivers so staffing and storage can be accurately planned? | Follow directives as outline in Af instructions |
| 142 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Retention Policy | Will a unified data retention policy (duration, storage medium, encryption, off‑site requirements) be issued to eliminate conflicting instructions? | I do not understand the question |
| 143 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Manual vs Automated | The PWS requires both manual and automated backups. Can the Government clarify whether both must occur, and if so, at which intervals and for which systems? | The contract employees will ensure the automated backs are being executed quarterly |
| 144 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Operational Impact | Will the Government provide expected maintenance windows when backups or test restores may temporarily affect system availability? | The contractor will schedule all work accordingly |
| 145 | SF1449 & PWS (Cross‑Document) | Backup Cadence Conflicts | Amendment Request | Does the Government plan to issue a corrected, consolidated set of backup requirements to eliminate ambiguity across PWS subsections? | Insuficient information to answer |
| 146 | SF1449 & PWS (Cross‑Document) | Evaluation Criteria | Evaluation Weights | The SF1449 lists evaluation factors but does not indicate their weights. Will the Government release factor weightings (e.g., Technical > Past Performance > Price)? | We will update the solicitation and SF 1449 to state "The evaluation factors are listed in descending order of importance: Technical Capability, Past Performance, and then Price. All technical factors, when combined, are significantly more important than price." |
| 147 | SF1449 & PWS (Cross‑Document) | Evaluation Criteria | Evaluation Weights | Should offerors assume equal weighting of Technical and Price, or does the Government intend to provide explicit weighting prior to proposal submission? | We will be updating FAR 52.212-2 in SF 1449 to match verbiage in soliciation |
| 148 | When is the Job Walk? | no site visit will be done | |||
| 149 | Standalone surveillance system 2 Location. What are the system Manufacture and size? | two cameras per site one DVR per site | |||
| 150 | will the government please define "Validated customer compliants" | The contractor will review if the complaint is valid. | |||
| 151 | will there be a walk-through | no site visit will be done | |||
| 152 | We noticed that one of the documents was marked as CUI. What is the CMMC-level of compliance required? | (Could not locate any CUI marked documents) | |||
| 153 | We noticed that one of the documents was marked as CUI. Does the government anticipate issuing a DD-254? At what level? | (Could not locate any CUI marked documents) | |||
| 154 | Must th VAR relationships be in place at the Prime level, or can a teammate/subcontractor possess those? | PWS 4.1.8 | |||
| 155 | will the government issue a formal SF-1149, to include all FAR and DFARS clauses that must be accepted? | The SF 1449 is attached to the solicitation | |||
| 156 | will the government please provide plug numbers for those CLINS? | SF 1449 in the solicitation has breakdown of CLINS | |||
| 157 | there are multiple references to SCIFS; are these currently accredited? | Irrelevant question |
File details come from the government source that posted it. Updated .