Document Intake / Upload received
If details are missing, the request goes back to the requester. The system update waits until a person records the review decision.
Explore process engineering →iBi Nexus / Systems lab
Try the engineering ideas.
Try four interactive examples: automate a process, organize information, connect applications or design a system. The examples use sample data and run in this page.
Enter the labInteractive engineering lab
Try an example. See what changes.
Choose an example and use the controls to explore it. The result stays beside the controls so you can see what changed.
Interactive example · sample data
What needs to happen before the next step?
Follow a request through its steps. Its document and responsible person stay visible, and a review decision is required before the system can update the record.
P-204 · Stage 1 of 7: Upload received · review required before the next system update
Upload received · review required
- Document
- Supporting document needs its reference checked
- Owner
- Requester
- Who takes the next step
- Intake coordinator
- Upload receivedStage being shown
- Required fields checkedPending
- Document classifiedPending
- Reviewer assignedPending
- Record updatedPending
- Requester notifiedPending
- Activity loggedPending
Interactive example · simulated AI output
From supplied information to a useful next step.
Choose a document or message. Compare the original with the organized information, then see what someone could do with it. You can also explore questions the source cannot answer.
Q-204
Quote Q-204: 12 filter kits at $35 each. Deliver to North depot. Requested by Facilities.
You can check the result against the original source.
A draft purchasing record
- Item
- Filter kits
- Quantity
- 12
- Unit price
- $35
- Total
- $420
- Destination
- North depot
Information ready to use.
Prepare a purchasing record with the quoted item, quantity and destination.
Purchasing draft ready for a person to check; no order is placed.
Discuss a similar task →See what the source does and doesn’t tell us
The output preserves the supplied facts. Check it before using it in a system.
What we can explore with you
- AI-assisted developmentUse AI to develop and refine prototypes, with engineers reviewing and testing the results. This website is one example.
- Document and information extractionExtract information from approved documents and organize it for use in your application.
- Knowledge and search assistanceHelp people find relevant references and answers without leaving the application they use.
- Workflow recommendationsOrganize information and suggest where work should go next, with the right checks for the task.
Interactive example · sample data
Who receives the update, and what happens if it cannot proceed?
An application programming interface (API) lets one application ask another to do something and return a response. An event announces a change; each receiving application is responsible for acting on it.
CRM means customer relationship management: software for customer records. ERP means enterprise resource planning: software for business records and processes.
U-204 · The receiving system confirms the result
Portal
CRM
Connection between applications
Business system / master record
Shared information
POST /record-updatesResponse: U-204 accepted- Payload
- request: R-204; status: reviewed; update: U-204
- Source owner
- The portal manages the request’s review status
- Destination
- The ERP system manages the business record
- Exchange status
- The receiving system confirms the result
Identity / API
Only the service allowed to update request R-204 may call the destination interface. User access and service access have distinct responsibilities.
The sending application waits for a response. If the receiving service is unavailable, the request stays pending.
Explore integration →Try the systems lab →Inspect related responsibilities →Need → architecture → prototype → system.
Explore how a need becomes a system design, or follow an equipment reading into an application. Each example explains the connections and who is responsible for them.
Design path / Need
Need
Architecture
Prototype
System
Need
Understand who will use the system, what they need to do, the information involved and any limits.
- Design output
- Context map: requester → review → service
- Decision
- Which handoff needs to change?
Deployed system
Washington State Department of Commerce Solicitation Management System
Designed and deployed by iBi Nexus; fully deployed and operational for solicitation and RFP/RFX-related workflows.