Purchase Order (PO) solutions in government utilize Requisitions which
flip into commercial documents called Purchase orders. The POs are issued by the government entity to suppliers indicating types, quantities, and agreed prices for products and services. They typically include standardized terms. The Purchase Order Software is used to gain visibility and transparency to the purchasing process. These solutions are an essential part of managed spending and compliance. The most basic PO process is.|
Purchasing Glossary >
Not in an industry above?|
That's okay. This list is a small representation of the industries we serve. Call for details.
Your Purchase Order solution starts with a base system which is changed to satisfy your needs. You may
need to merge our Purchase Order system with other data in your environment or extend it beyond a basic Purchase Order solution. You may want some, all, or none of the add-ons Aestiva provides.|
At Aestiva, our job is to streamline your processes, not make them more complicated. All solutions are designed to give you just what you want. Burdening users with unnecessary features is counter-productive. After all, things are already complicated enough.
Last but not least, Aestiva technology is change-friendly. After any changes we make, your system will maintain its ability to be upgraded and its ability to be extended at any later time.
The Setup Process.
All of Aestiva's industry-specific solutions include a "Design, Build, and Deploy" (DBD) process.
This is how it works. First, before any commitments, Aestiva will schedule a time with an engineer to review your general needs. Aestiva will then issue you a quotation that includes your requirements plus a good faith "allocation budget for features known and unknown" (which you should not exceed unless you request items out of the original scope and budget). After purchase, Aestiva will complete a thorough specification with you, notify you how much of the "allocation budget" is actually needed (we strive to budget more than needed), and with your approval, complete the project on a fixed cost basis. For further questions please schedule a demo.
Your Aestiva Purchase order System was designed to be changed after deployment. You can request limited changes,
add modules, and add new systems.|
If applying a change without proper review does not put your system in danger (like adding a custom report, for example), then Aestiva can apply the addition directly to your live solution. For all other changes, Aestiva uses an industry-standard enterprise software change process.
Purchase Order Change Process
A Change is specified.
A Test (Staging) system is created or updated.
The Change is assigned to Aestiva production for completion.
The Change is applied to the Staging system.
The Change is reviewed by the customer.
Upon acceptance and Change is scheduled to be applied.
The Change is applied to the live (Production) system.
Changes are managed by your Aestiva Account Coordinator in conjunction with Aestiva's production team and, when needed, with oversight by Aestiva's engineering and senior staff.
Want to find out more? Give Aestiva a call.