Functionality Description. Procurement Suite Supplier Engagement, Evaluation and Award Solution ● Vendor Portal ● Generic Template ● Related Training and Knowledge Transfer Solicitation Development Solution ● Up to 4 Templates: ○ RFQ ○ IFB ○ RFP ○ Up to one (1) additional as agreed upon with the project team and customer. ● Related Training and Knowledge Transfer Contract Management Solution ● Up to 3 Contract Templates: ○ Professional Services Agreement ○ Up to two (2) additional as agreed upon with the project team and customer. ● Contract Migration ● Related Training and Knowledge Transfer System-wide Training ● System Admin Training ● Procurement (Super User) Training ● Template Administration Training ● Departmental User Training. Super User led, XxxxXxx supported ● Supplier Documentation
Functionality Description. Creating Environment OpenGov will provision a Procurement environment and verify that the Customer has access to all purchased modules. A customer system administrator will be added to the environment following contract signing and creation. Website Integration OpenGov meets with Customer and website resource to review website integration document. Agree on changes to be made and timeline for completion. Customer Vendor Portal live is a milestone before beginning configuration. Vendor Registration Portal OpenGov will provide the Customer with an example Vendor Intro Letter to be edited and approved by the agency. Once the Customer sends the vendor email/letter. OpenGov will import the list of vendors provided by the agency and send automated vendor invitations to the list of vendors provided to register and subscribe to the agency. Reminder emails will be sent on a weekly basis. Vendor support for registration is provided by OpenGov Tier 1 Support via live chat function 8AM -8PM Eastern.
Functionality Description. Vendor Registration Portal Customer with OpenGov will confirm and complete website updates OpenGov will provide the Customer with an example Vendor Introduction communication to be edited and approved by the agency. Customer sends the vendor an introduction email/letter. OpenGov will import the list of vendors provided by the agency and send automated vendor invitations to the list of vendors provided to register and subscribe to the agency. Reminder emails will be sent on a weekly basis. Vendor support for registration is provided by OpenGov Tier 1 Support via live chat function 8AM -8PM Eastern. Working Session ● Work alongside customer to provide knowledge transfer on how to manage the Vendor Registration Portal Supplier Engagement, Evaluation and Award Solution OpenGov will review solicitation documents provided. Supplier Engagement, Evaluation and Award Workshop OpenGov will lead workshop to: ● Create the first Bid and discuss the formats of the other solicitation types ● OpenGov will suggest changes to language based on using OpenGov Procurement ● Customer and OpenGov work together to create the bid template, and the initial generic template. Supplier Engagement, Evaluation and Award Working Sessions Work alongside customer to provide knowledge transfer on: ● Creating Bids within OpenGov Procurement ● Bid Opening, Tabulation, Evaluations, and Awarding the Project Solicitation Development Solution OpenGov will review Boilerplate or Templates of Solicitation types and Forms provided (4). Solicitation Development Workshop OpenGov will lead workshops to: ● Design the Solicitation Template in OpenGov Procurement. ● Customer selects the first solicitation type (usually either ITB or RFP), and works with OpenGov with the design Typically two to three sessions are required to complete the first template. ● First template sign off before beginning the subsequent 3. ● Subsequent template build is faster with Solution knowledge. Solicitation Development Working Sessions ● Work alongside customer to provide knowledge transfer on how to write Solicitations with OpenGov Procurement Intake Workflow Solicitation intake process, when working with decentralized sourcing, reviewed to be incorporated within OpenGov Procurement. ● Planning for expansion into internal customers/departments and bringing departments online. ● Training: Preparing for Intake (Buyers and Department Directors) ● Implement default “Review/Approval” Processes. ● Training: Internal Customer/Depart...
Functionality Description. Supplier Engagement, Evaluation and Award Solution Customer will sign off: ● Generic Template Solicitation Development Solution Customer creates test solicitations using templates and testing logic for each template. Customer will sign off: ● First bid solicitation ● Afterward, subsequent solicitations ● Intake process aligned per specifications Contract Management Solution Customer will sign off: ● Contract template ● Contract database. Dataset provided is represented within OpenGov Procurement per specifications detailed.
Functionality Description. Supplier Engagement, Evaluation and Award Solution Customer: ● Prepared first first bid for immediate or future release Customer to: ● Complete OpenGov-provided sign off document ● Review sourcing process with Administrators and Super Users, preparing them to deliver training for department users ● Department User training Solicitation process within OpenGov Procurement led by Customer Super Users with OpenGov support Solicitation Development Solution Customer goes live with up to 4 Solicitations templates. Internal Solicitation process goes live. Customer to: ● Complete OpenGov-provided sign off document ● Review Solicitation Development Solutions with Administrators and Super Users, preparing them to deliver training for department users ● Department User training of Solicitation Development Solution within OpenGov Procurement led by Customer Super Users with OpenGov support, where needed Contract Management Solution Customer goes live with the Contract Template and Database. ● Communicate access and process Customer to: ● Complete OpenGov-provided sign off document ● Managing New Contracts in OpenGov Procurement ● Review Contract Management Solution with Administrators and Super Users, preparing them to deliver training for department users (if necessary)
Functionality Description. User ID: Although not necessary for the purpose of this scenario, in a real system the application would probably be set up with a specific user ID, which it would then submit to the Maintenance Tool during the login process. Furthermore, there would probably be some user environment associated with the user ID, to be displayed when the user starts the app.
Functionality Description. Apart from the one function the maintenance tool will need, namely to order a replacement device, the inventory server should provide some visual indication that the order has been issued.
Functionality Description. In this scenario, the following component’s IPv6 addresses will be retrieved from the GRD:
Functionality Description. Although the CMS can be regarded as the central component of the automation system, in this scenario, it is a mostly passive component, merely relaying device access requests to the IoT6 Gateway and being notified of actions the maintenance tool takes.
Functionality Description. Here, the STIS is only used to provide device information based on an RFID – using the maintenance app, the engineer will scan the RFID tag of the failed device. The information the STIS will provide for both should at least contain the location of the component, so the engineer can seek it out and inspect it. Additionally, the STIS may be queried with the RFID of the replacement component – in this case, the response should contain a description of the device, which would allow the engineer to determine if it is the correct part.
