SEWP VI Category A vs B/C Integration: Architecting Compliant Line-Item Bundling Under FAR 16.505

NASA SEWP VI fundamentally divides IT products (Category A) from service-led and complex mission solutions (Categories B & C). Learn how capture teams must structure task order quoting, labor-product bundling, and fair opportunity defenses under FAR 16.505.

GovCon Architect Editorial Team·September 14, 2026

GovCon Architect is an independent platform and is not affiliated with, endorsed by, or sponsored by NASA or the SEWP Program Office. Program information is published at the NASA SEWP site.

The Strategic Divide in SEWP VI Architecture

The structure of the NASA Solutions for Enterprise-Wide Procurement VI (SEWP VI) Government-Wide Acquisition Contract (GWAC) marks the end of pure IT hardware commoditization. By partitioning awards across Category A (Information Technology, Communication, and Audio-Visual Solutions), Category B (Enterprise Multi-Platform Applications), and Category C (Mission-Focused Services and Solutions), the NASA SEWP Program Office engineered a system designed to support complex, cradle-to-grave digital transformation.

However, this structural categorization creates severe quoting and proposal pitfalls during task order execution under FAR Subpart 16.505. In SEWP V, contractors routinely bundled ancillary installation, engineering, and managed services under product CLINs. Under SEWP VI, order-level Contracting Officers face stricter oversight regarding NAICS-code scope creep, fair opportunity competition, and the clear separation between product supply chains and professional engineering services.

Capture managers who fail to master cross-category bundling rules risk disqualified quotes, contract disputes, and bid protests under the Small Business Administration's (SBA) ostensible subcontractor affiliation rules at 13 CFR § 121.103(h).

Line-Item Bundling Rules Across Categories A, B, and C

When federal program offices issue Requests for Quote (RFQs) on the SEWP web portal, task orders frequently blend enterprise hardware/software licensing with complex systems integration. To structure compliant quotes, offerors must evaluate where their scope lives across the SEWP VI taxonomy:

  • Category A (Products/Platforms): IT hardware, COTS software, cloud compute, A/V, telecom, and ancillary maintenance.
  • Categories B & C (Solutions/Ops): Enterprise IT architectures, custom DevSecOps, systems engineering, and AI pipelines.

Under FAR 16.505(b), fair opportunity rules require that every task order adhere strictly to the scope of the parent GWAC vehicle. Capture teams must observe three critical architectural rules when quoting bundled solutions:

  • The "Ancillary Service" Boundary in Category A: In Category A orders, professional services and labor must remain strictly ancillary to the commodity or platform being deployed. If labor costs exceed the value of the underlying hardware/software assets or represent ongoing, independent system operations, the quote crosses into Category B/C territory and can be rejected by the SEWP Program Office during pre-award quote verification.
  • NAICS Code Dominance and Set-Aside Integrity: Category A task orders typically carry product-oriented NAICS codes (e.g., 334111) with a 1,250-employee threshold, whereas Category B and C orders rely on service-oriented NAICS codes (such as 541512 or 541519) with monetary size standards. Quoting teams must ensure their small business joint ventures or prime entities meet the specific size standard applied to the task order, avoiding reliance on parent contract size eligibility if an order-level recertification is triggered.
  • Open Market Item Segregation: Hardware or software items not pre-approved on the prime's SEWP VI catalog cannot be buried within services CLINs. Any open-market item must be explicitly flagged and quoted in compliance with SEWP's non-contract item authorization rules.

Mitigating the Ostensible Subcontractor Risk in Complex Orders

For small business primes competing in Categories B and C, complex multi-line task orders carry high protest risks. Large defense system integrators frequently partner with small SEWP VI contract holders to provide the bulk of high-end software development or cloud engineering.

If the prime contractor merely functions as an administrative pass-through while the large subcontractor performs the primary and vital requirements of the performance work statement (PWS), competitors can file size protests citing the ostensible subcontractor rule. To insulate task order awards from SBA size protests:

  1. Retain Management Control of Primary Workstreams: The small business prime must directly oversee mission-critical technical management, systems security engineering, and quality assurance. Prime personnel must fill key personnel roles such as Technical Director and Solutions Architect.
  2. Labor-Hour and Cost Accounting Audits: Proposals must clearly demonstrate compliance with the limitation on subcontracting requirements under FAR 52.219-14, proving that the small business prime will incur at least 50 percent of the cost of contract performance incurred for personnel.
  3. Independent Past Performance Mapping: In oral presentations or technical proposal narratives, never attribute core technical capabilities solely to the large subcontractor's heritage systems. Articulate the prime's specific operational workflows, toolchains, and oversight frameworks.

Winning Orders in the Fair Opportunity Quoting Engine

Success on SEWP VI requires moving beyond transactional price-discounting. Federal procurement leads utilize the SEWP Tool for Quoting (QTool) because of its automated compliance checks and rapid turnaround. Prime contractors must establish programmatic quoting workbenches that link their SAM.gov entity registrations, dynamic supply chain risk management (C-SCRM) software bills of materials (SBOMs), and real-time labor pricing.

When a mixed hardware-service task order drops, capture managers should evaluate the Statement of Objectives (SOO) within the first 24 hours. Determine whether the agency's primary intent is asset acquisition or sustained operational integration.

By cleanly delineating hardware delivery from integration labor in the Price Work Breakdown Structure (WBS) and aligning every quote line item with clear category rules, contractors can capitalize on SEWP VI's massive ceiling while staying completely bulletproof against post-award compliance audits.

The GovCon Architect editorial team writes practitioner guidance on federal capture, compliance, and proposal operations. GovCon Architect is an AI-powered federal government contracting platform for opportunity intelligence, capture, compliance, competitive intelligence, and proposal workflows.

More in SEWP VI

Explore the platform