RFP Blitz - Medium

Resource Page Link

This is the RFP Blitz site. This link opens it with your account prepared for your session's level. Sign in if you are asked to, then check the results here after your run.

https://pathfinder.automationanywhere.com/challenges/training/Build_An_Agent_Resources/RFPBlitz/index.html?level=medium

Control Room Link

This is the link to the control room you will be performing all hands on activities within.

https://aa-community.cloud.automationanywhere.digital/

Your session's build is in Bots/BAA/RFP Blitz/Medium_Bid or No Bid.

API Documentation Page Link

The page below has all the API documentation for RFP Blitz.

View API Documentation

Action One: Give AG_BidOrNoBid its tools

Steps:

  1. Navigate to Medium_Bid or No Bid/AG_BidOrNoBid and click the name to open it. Its role and three of its four tools are there; the goal and the plan are empty.
  2. Go to Tools. RB_ResearchBidSet, RB_ClassifyForBid and RB_MatchCapabilities are already added. Add the fourth API Task. Each tool works on one RFP at a time.
  3. RB_GetDraftPack: press Add tool, select API Task, click Choose, then the Browse button at the top right (not Search), and get Medium_Bid or No Bid/RB_GetDraftPack from there, in private. In its Tool description for AI, clear any text and paste:
    Reads the RFP you pass: its client, format, numbered items, the requirements in the client's own words, what the product desk has already said, and the document itself. Use it to read a tender before you judge it.
  4. Still on RB_GetDraftPack, under Input descriptions for AI, clear the text for iStrRfpNumbers and paste:
    One RFP number, exactly as you were given it.
    • The other three tools already say this: each one works on one tender at a time.
  5. Take note: RB_ClassifyForBid runs the prebuilt classification skill, AS_ClassifyRfp, and RB_MatchCapabilities sends the must-haves to Ask it Straight (AS_AskItStraight). Each description says what the tool is for, not when to call it: the agent picks what to ask next from what the last tool told it. The agent only recommends; you decide on the form.

Action Two: Write its goal and plan

Steps:

  1. Go to the Prompt tab. In the Goal, paste:
    Every tender waiting on a bid call has a picture a person can decide from: what the client asks for and rules out, which service line really owns the work and why, what the product desk says the firm can deliver, who the requesting company is and what has won or lost before on that line, and a recommendation with the deciding fact. You are done when each picture is in your outputs, or when nothing is waiting.
  2. Go to the Action plan and paste:
    The AG_BidOrNoBid action plan - click to copy
  3. Take note: the plan has no numbered steps and no answers. It is the same rule you read on the form, written as principles.
  4. Press Save and close the agent.

Action Three: Build the decision form: FM_BidDecision

Steps:

  1. Navigate to Medium_Bid or No Bid/FM_BidDecision and open it. The three labels at the top and the boxes for Tender A and Tender B are already there. You add Tender C and the name box below them from the Elements list, in exactly this order: the Control Room numbers each element as you add it, and the process reads them by those numbers.
  2. Drop each new element on the form just below the last one (the first one goes under Tender B's reason box), so it gets its own full-width row. If one lands beside another, select it, press Delete, then select that row and delete its empty cell.
  3. Tender C. A Text Area: paste the Element label below, set Height to 170 and tick Make field uneditable:
    Tender C: the picture
  4. A Radio Button: paste the Element label below, set Radiobutton 1 to Bid and Radiobutton 2 to No bid, and tick Make field required:
    Tender C: your decision
  5. A Text Area: paste the Element label below and tick Make field required:
    Tender C: your reason (at least 20 characters)
  6. Last, a Text Area: paste the Element label below and tick Make field required:
    Your name
  7. Click each element and check its Element ID down the form: Label0 to Label2, then TextArea0, RadioButtonGroup0 and TextArea1 for Tender A, the next three for B and C, and TextArea6 for your name. Press Preview, then Save and close the form.

Action Four: Put the agent and the form in the process

Steps:

  1. Navigate to Medium_Bid or No Bid/PR_RFPBlitz and open it.
  2. Between WhatsWaiting and RecordBids, remove the connecting line.
  3. Drag an AI Agent from the Elements list onto the canvas, between them. Set the Element ID to BidPicture.
  4. Set its Task name to:
    Stage 6: The bid picture for each tender waiting on a bid call (Bid or No Bid)
  5. Under AI Agent, click Choose, then the Browse button at the top right (not Search), and get Medium_Bid or No Bid/AG_BidOrNoBid from there, in private.
  6. Under Task assignment, choose Role and click Choose. Type AAE_Robotic Interface User in the search box and press Enter, then select it and click Choose.
  7. Connect WhatsWaiting to BidPicture: drag from the dot at the bottom of one step to the dot at the top of the next. The form goes between BidPicture and RecordBids next.
  8. In its input values, set iStrApiKey to:
    $iStrApiKey$
  9. Tick iStrRfpNumbers and set it to:
    $&WhatsWaiting{output}{oStrBidNumbers}$
  10. Drag a Form onto the canvas between BidPicture and RecordBids. Set the Element ID to BidDecision.
  11. Set its Task name to:
    Bid or No Bid - your decision on the tenders waiting
  12. Under Action buttons, open the Submit button's menu, choose Edit and change its label to Record decision.
  13. Under Form, click Choose, then the Browse button at the top right (not Search), and get Medium_Bid or No Bid/FM_BidDecision from there, in private.
  14. Connect BidPicture to BidDecision, and BidDecision to RecordBids.
  15. In its input values, tick TextArea0 and paste:
    $&BidPicture{output}{oStrPictureA}$
  16. Tick TextArea2 and paste:
    $&BidPicture{output}{oStrPictureB}$
  17. Tick TextArea4 and paste:
    $&BidPicture{output}{oStrPictureC}$
  18. Take note: RecordBids already reads your answers by those Element IDs - the decisions, the reasons and your name. Press Save. Keep the process open: you run it from here in Action Five.

Action Five: Run it and decide

Steps:

  1. On the RFP Blitz home page, press Prepare my account for Medium (Prepare again if it already says prepared) and press OK, so the morning starts fresh.
  2. Back in PR_RFPBlitz, which is still open from Action Four, press Run.
    • If you closed it, navigate to Medium_Bid or No Bid/PR_RFPBlitz and open it.
  3. Get your key: at the bottom of the RFP Blitz home page, press Get your API key (on any other RFP Blitz page, open Account in the menu). On the Account page, press Copy next to your API key. Paste it into iStrApiKey and click Confirm.
  4. Watch the agent in Co-Pilot: it reads each tender, classifies it, sends its must-haves to Ask it Straight and researches the client, in the order each tender needs. It builds a picture for each and stops. This takes about 8 to 10 minutes before the form arrives.
  5. When the form arrives, read the rule at the top first. Then read each picture and decide. Check yourself against these:
    • RFP 3: the title says document processing, but its Route line in the RFP Hub says process mining, and Veridian CRM (Opportunities) shows a past process-mining bid we won. Trust the Route line: Bid.
    • RFP 5: a penetration test is a must-have, and Veridian's Scope Exclusions Standard, clause SE-2.7 (Policy Library), excludes penetration testing by default. No bid.
    • RFP 6: the title says document automation, but the work is integration, and Veridian CRM (Opportunities) shows we lost a past integration bid because we never asked for the client's integration inventory. Bid, and ask for the inventory first.
  6. Give each decision a reason of at least 20 characters. You can paste these. Tender A (RFP 3):
    Bid: the Route line says process mining, and Veridian won a past process-mining bid.
    • The form shows the tenders in the order they were waiting: Tender A is RFP 3, Tender B is RFP 5 and Tender C is RFP 6. The first line of each picture names its RFP.
  7. Tender B (RFP 5):
    No bid: penetration testing is a must-have, and clause SE-2.7 excludes it by default.
  8. Tender C (RFP 6):
    Bid: the work is integration, not document automation. Ask the client for its integration inventory first.
  9. Type your name and press Record decision.
    • It then records your calls and drafts the tenders you bid on: about 2 to 3 more minutes.
  10. Open the RFP Hub. RFP 5 is declined with your reason, and RFP 3 and RFP 6 each have a first draft in the client's own format.
  11. Open Level Progress. The Bid or No Bid lines should all be green.