For a GSA professional-services requirement, identify the outputs, where delivery takes place and which customer systems and teams the work must interface with. STi’s portfolio includes engineering, logistics, program support and information technology.
An initial discussion should establish the customer objective, general discipline, anticipated deliverables, delivery interfaces and the assumptions that affect performance. That gives acquisition and technical teams a shared basis for identifying the next step.
- Engineering and technical support
- Program, reporting and coordination services
- Technology and logistics support
- Requirement and acquisition-pathway discussions
Separate technical scope from vehicle eligibility.
A suitable technical capability and an available ordering route are related but separate questions. The selected vehicle must cover the contemplated work, and its current eligibility, ordering authority and instructions must be confirmed. Use the contract vehicle directory to identify the relevant GSA contract or pool before confirming the ordering requirements.
Prepare a clear requirement discussion.
Useful inputs include the work purpose, operating context, expected outputs, customer interfaces and the proposed procurement route. Start with unclassified general information; detailed program material can be coordinated through an authorized channel.
CONNECT THE REQUIREMENT TO THE RIGHT DISCIPLINE