IT:AD:Documentation:Request for Information (RFI)

A decent RFI will contain the following:

• Introduction
• Purpose of project
• Bachground to the current process
• Info as to due date, participation, Contract, may cancel at any time.
• Guidelines to RFI Guidelines
  • It's always confidential…
• Process Objectives: what they want to acheive
• Process Options: a straw man diagram of options
• Services Requirements ans scope
  • High level reuqirements
    • A list of requirements, and rationale behind them (that's good to see)
    • Multiple access channels
    • Workflow templates/reuse

• Example Information Requested:
  • Information about the company
  • Information about the proposal
    • How is OOTB versus How much Dev effort?
    • Indicative costs of
      • Hardware
      • IMplementation services
      • software
      • Ongoing maintenance
    • Describe capability of proposed system to interact with incumbent organisational systems (Tasks/Emails/Data retrival).
    • Local market to support additional development
      • In parrallel (work with other dev shops)
      • In future
        ## Resources ##
• Projects:NZTA
• Projects:NZTA:Customer Improvements to Permitting for Heavy Vehicles Project (CIPHVP)