Procurement and Contract Vehicles for Buying a Digital Twin

Most organizations buy an operational digital twin through one of four routes: an existing cooperative purchasing contract, a state term contract, a purchase from a state approved-vendor or pre-qualified list, or a sole-source award. The route you pick determines almost everything a business manager actually cares about: how many weeks pass before a purchase order is issued, how many board agenda items are involved, whose signature is required, and how much of the file an auditor asks to see two years from now. The technology question is usually settled long before the procurement question is. This page is written for the person who has to make the purchase legal, documented and fast, in that order, and it is written from the buy side rather than the sell side.

Which buying route fits your organization, and how do you choose between them?

Start by classifying the purchase, not the product. Three questions settle the route in almost every case. First, is your organization a public entity subject to a competitive procurement statute, or a private operator (a hotel group, a private hospital system, an energy operator) governed only by internal signature authority? Second, what is the aggregate value of the buy across a twelve-month period, including capture, platform licensing, updates and any professional services? Third, does a competitively awarded contract already exist that your entity has legal authority to use?

Aggregate value is where most buyers get into trouble. Purchasing thresholds apply to total spend in a category over a defined period, not to the size of any single invoice. A digital twin engagement bundles initial field capture, model production, platform access and periodic updates, and those pieces arrive on separate invoices at separate times. Splitting a single procurement into invoices that each sit under a threshold is the most common finding in a purchasing audit, and it is treated as an intentional act even when it was an accident of scheduling. Add the pieces up first, then choose the route.

Ranked by elapsed time from decision to purchase order, cooperative contracts and state term contracts are the fastest, approved-vendor list purchases sit in the middle and depend entirely on your funding source, and sole source is the slowest and the most heavily scrutinized. Choose the fastest defensible route rather than the one that feels most thorough. A well-documented cooperative purchase survives an audit better than a poorly documented competitive process.

What is a cooperative purchasing organization, and how does riding an existing contract work?

A cooperative purchasing organization exists so that one competitive solicitation can serve many buyers. A lead public agency, which is typically a school district, a city, a county, a regional education service center or the cooperative's own governing entity, writes a scope of work, advertises it publicly, evaluates the responses it receives, and awards a contract. The critical detail is that the solicitation states up front that the resulting contract is awarded on behalf of the lead agency and on behalf of other public agencies that join the cooperative. The competition is real, it is just performed once, by someone else, before you arrive.

Because the competitive step already happened at the lead agency level, a member agency buying from that contract inherits the competition rather than repeating it. That inheritance is what buyers mean by piggybacking. In practice the mechanics are short: execute a membership agreement or interlocal agreement with the cooperative if you have not already, confirm the vendor holds a current award under that cooperative for the specific scope you are buying, reference the cooperative name and contract number on the requisition and the purchase order, and keep a copy of the award documentation in the purchase file. Those four steps are the file an auditor will ask for.

An interlocal agreement is the legal instrument underneath much of this. It is a contract between two governmental entities that lets one perform a function for the other, including purchasing, and nearly every state authorizes some version of it. It is what allows a school district to buy through a contract a city competed, or a county to buy through a contract a state authority competed. Interlocal purchasing is recognized as a legitimate procurement method in its own right in many state purchasing statutes, which is why it appears alongside bidding and proposals rather than as an exception to them.

Cooperatives a public buyer commonly encounters include BuyBoard, TIPS, Sourcewell, NCPA and OMNIA Partners. Naming them here describes the category so the terminology is recognizable on your next requisition. It is not a statement that Ark or any other vendor holds an award with any of them. Verify a vendor's award status directly with the cooperative, using the cooperative's own public contract listing, before you cite a contract number in a purchase file.

Four checks separate a clean cooperative purchase from a messy one. Confirm your entity's membership is active and that the person signing has delegated authority to use it. Confirm the awarded scope genuinely covers what you are buying, because a contract awarded for hardware does not automatically cover professional services or recurring platform access. Confirm the contract has not expired or entered a renewal gap. Confirm whether your own board policy requires a separate board action to use a cooperative contract above a stated dollar figure, because state law permitting the method does not override a stricter local policy.

What is a state term contract, and when is it the cleanest route?

A state term contract is a contract that a state's central procurement office competes once, on behalf of state agencies, and then publishes with fixed pricing, fixed terms and a defined catalog of what is covered. State agencies buy from it directly. In most states, local political subdivisions such as cities, counties, school districts and public higher education institutions are also permitted to buy from designated state contracts, either automatically by statute or by opting in through a registration step with the state.

The advantage for a business office is that two expensive activities are already finished. Pricing has been competed and set, so you are not defending price reasonableness from scratch. Terms and conditions have been through a state legal review, which matters enormously for anything involving facility data, hosting, retention and access control. Your contract review shrinks to confirming that the state's terms cover your specific data handling requirements rather than negotiating an agreement from a blank page.

The limits are worth stating plainly. State contract catalogs are written in categories, and the category boundary is often narrower than a real project. A contract that covers software licensing does not necessarily cover the field capture work that produces the model, and buying the covered half off the state contract while handling the uncovered half informally recreates the exact splitting problem described above. Eligibility for local entities differs by state and sometimes by contract. Verify eligibility and scope with your state's central procurement office or your own purchasing director, not with a vendor, and put the answer in writing in the file.

What does an approved-vendor or pre-qualified list actually do for a buyer?

Qualification is a gate, not an award. When a state agency or program office publishes an approved-vendor list or a pre-qualified vendor list, inclusion means the vendor submitted an application and met the criteria that program defined. Those criteria typically cover things like insurance, corporate standing, references, category fit and sometimes a technical review of the offering. Inclusion is a statement about the vendor. It is not a statement about your price, your terms, your scope or your competition.

What a list does for you is real and useful. It reduces the vendor due diligence you perform yourself, because someone with subject matter authority already checked a defined set of boxes. It satisfies eligibility conditions that a funding program attaches to how its money is spent. And it gives you a short, defensible answer to the question an auditor asks most often, which is how you knew the vendor was qualified to do this work at the time you committed the funds.

What a list does not do matters more. It does not exempt you from your own competitive threshold, so a purchase from a listed vendor at an aggregate value above your statutory threshold still requires a lawful purchasing method. It does not establish price, because nobody competed price to build the list. It is not a contract, so it carries no terms, no warranty language and no data provisions. Treating a list entry as though it were a contract award is a distinct and very visible audit finding, and it is one of the few procurement errors that is obvious to a reader who was not in the room.

When is a sole-source justification legitimate, and what has to be in the memo?

Sole source is a real and lawful method, and it is the wrong first choice most of the time. It applies when only one vendor is genuinely capable of furnishing what the entity needs. Grounds that purchasing offices commonly recognize include an item available from a single source because of a patent, copyright or exclusive distribution right, a component required for compatibility with an already installed system where no alternative integrates, captive replacement parts for existing equipment, and a documented emergency, though emergency purchases usually run under their own separate authority rather than as a sole source.

A defensible memo establishes five things, and a weak one skips at least three of them. It describes the requirement in functional terms rather than brand terms, because a memo that names a product in its statement of need has assumed its own conclusion. It documents the market research performed, meaning which alternatives were examined and the specific, written requirement each one failed to meet. It explains why that requirement is essential rather than preferred, which is the single hardest sentence in the document to write honestly. It establishes price reasonableness without competition, using published pricing, cooperative pricing for comparable scope, prior pricing history or an independent cost estimate. And it is signed by a person with delegated authority on a date that precedes any commitment to the vendor.

The audit exposure is concentrated and predictable. Sole-source memos written after the purchase order was issued, memos that describe a brand instead of a need, and memos that rest on the word preferred are the three patterns reviewers look for first. Where the funds are grant funds, a rejected justification converts into a disallowed cost and a repayment demand, which lands on the business office rather than on the department that wanted the product. Sole source also runs slowly: legal review, frequently a board action, and in some jurisdictions a public posting period before award. If a cooperative contract or a state term contract covers the scope, use it and keep the sole-source route in reserve.

How does the Texas school safety funding rule work, and why is it so often misquoted?

Texas is the clearest worked example because it contains two separate rules that buyers routinely merge into one. Texas Education Code 48.160(c-1) requires the Texas Education Agency, or the Texas School Safety Center if TEA designates it, to establish and publish a directory of approved vendors of school safety technology and equipment that a school district selects from when spending School Safety Allotment funds. Districts are not obligated to use a vendor from that directory. If a district buys technology or equipment from a vendor that is not in the directory, the district must solicit bids from at least three vendors before completing the purchase. That is the three-bid rule, and its source is the Texas Education Agency letter titled School Safety Vendor Technology Directory, a To the Administrator Addressed letter dated June 27, 2024, which lists Emergency Response Mapping as one of the technology categories accepting vendor applications.

Check the section number before you cite it. This allotment lived at Texas Education Code 48.115 until House Bill 2 of the 89th Legislature transferred it to Subchapter D and redesignated it as Section 48.160, effective September 1, 2025. The rule itself did not change, but the number did. The June 27, 2024 TEA letter predates the move and still cites 48.115(c-1), so a memo written from that letter alone will carry the old number.

Here is the distinction to preserve. That three-bid requirement is specific to School Safety Allotment purchases under 48.160(c-1). It is not the general Texas school purchasing rule, and quoting it as though it were is the fastest way to lose credibility with a purchasing director.

The general rule is Texas Education Code 44.031(a). District contracts for goods and services valued at $50,000 or more in the aggregate over a twelve-month period must be made using one of the statutory methods: competitive bidding, competitive sealed proposals, a request for proposals, an interlocal contract, a reverse auction, and for construction the methods provided in chapter 2269 of the Government Code. Section 44.031 itself contains no three-bid requirement and no three-quote requirement. Those words are not in it.

The widely repeated practice of obtaining three written quotes for purchases between $10,000 and $50,000 is local school board policy, not Texas state law. Many districts adopt exactly that threshold, which is why it circulates as though it were statutory. Follow your own adopted policy to the letter, because a local policy binds you, but do not cite it in a memo as a state requirement, and do not assume that a neighboring district's threshold is also yours.

The practical consequence is that requirements stack rather than substitute. A district paying from the School Safety Allotment for a vendor that is not in the directory plans for the three bids under 48.160(c-1) and separately satisfies 44.031(a) if the aggregate value over twelve months reaches $50,000. Satisfying one does not satisfy the other, because they come from different sources with different purposes. Write both citations into the requisition file so the next person reading it understands why each step happened.

What should you ask any vendor for before you raise the requisition?

A vendor file assembled before the requisition is written takes an afternoon. Assembled afterward, under audit, it takes weeks and rarely turns out complete. Ask for the documentation up front and make receipt of it a condition of moving to a purchase order. The list below is what a purchasing office typically wants in hand, and any capable vendor produces all of it without friction.

Ark states its own position directly, because a procurement page is the wrong place for inference. Ark is registered in SAM.gov. Insurance certificates are available on request. Ark is veteran-led, and Ark is not a certified VOSB or SDVOSB, because veteran ownership sits below the 51 percent threshold after dilution. That negative is stated plainly here on purpose: a reader on a procurement page would reasonably assume set-aside eligibility from the phrase veteran-led, and that assumption is wrong. Do not build a small-business set-aside strategy around Ark, and do not code a requisition to a set-aside category on that basis.

Contract vehicle availability changes as awards are competed, renewed and extended, and a published list on a website goes stale faster than any other content on it. Contact Ark directly to confirm current contract vehicle status for your state or your agency before you write a vehicle reference into a requisition, and confirm anything you are told against the cooperative's or the state's own public contract listing.

One boundary is worth restating because it affects how the budget is built. Ark does not sell panic alarms. Alyssa's Law is panic-alert legislation, concerning silent alarms that connect directly to law enforcement, and it is distinct from school mapping requirements. Those are two different purchases with two different vendor sets, and combining them into a single line item makes both harder to approve. ZeroEyes and Verkada are integration partners rather than Ark products, so anything sourced from them is procured on its own paper.

How do you sequence this against your budget cycle and board calendar?

Work backward from the date the model needs to be in service, not forward from today. Field capture is scheduled work that competes with facility access windows, and in school and hospital environments those windows are narrow and fixed. Then add the procurement calendar in front of it. A cooperative purchase adds days to a few weeks once membership is confirmed. A state term contract purchase is similar. A sole-source award adds legal review plus at least one board cycle. A full solicitation adds a quarter or more, because advertising periods, evaluation and award all sit on published calendars you do not control.

Board calendars are the hard constraint that surprises people. Most boards meet monthly, agenda deadlines close one to two weeks ahead, and summer schedules go quiet. A purchase that misses an agenda deadline by two days slips a full month, and if that month crosses a fiscal year boundary the funding source changes and the approval starts over. Identify the specific meeting date you are targeting and count backward from the agenda deadline rather than the meeting itself.

Distinguish encumbrance from expenditure when a funding source has a spending deadline. Whether a purchase order encumbering funds satisfies the deadline, or whether the work has to be performed and invoiced within the period, is a question with a definite answer in your program rules and a costly one to assume. Get it in writing from the program office before you schedule capture work.

The most useful habit is to put the procurement route on the same page as the budget request from the beginning. When a business manager brings a funding item to a board with the vehicle, the citation and the timeline already identified, the item passes as a routine approval. When the vehicle is worked out afterward, the same item comes back a second time, and second appearances invite questions that the first appearance never would have.

Buying for a school district? The K-12 version of this guide covers board approval sequence, grant allowability and the audit file. Working to a funding window or a statutory date, see the compliance and grant deadline calendar.

What do buyers ask most often before they commit?

Want your buying route confirmed before you build the budget?

Tell us your entity type, your funding source and the date you need the model in service, and we will tell you which purchasing routes are open to you and what your file needs to contain. If the answer is that you should run your own solicitation, we will say so.