Process Robotics SOW Final.pdf
PDF 15 KB Posted
- Solicitation number
- N00039-18-P-0013
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Process Robotics CDRLs.pdf | ||
| Process Robotics Solicitation Final.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK (SOW)
Robotic Process Automation Pilot
1.0 SCOPE
This Statement of Work is being issued as a pilot effort to automate the Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I) Purchase Requisition process using process robotics. The pilot effort will leverage other process robotics efforts in the Department of Navy to ease software application approval processes for use on the Navy/Marine Corps Intranet (NMCI).
2.0 BACKGROUND
The Purchase Requisition process is high complexity process due to the requirement to use a Remote Desktop Program such as Citrix to access Navy-ERP and the necessity of over 50 screens that the bot will need to navigate. PEO C4I intends to use process robotics as a way to handle low-value transactional work, which will free up the current workforce and allow for higher-value analytical work.
3.0 TECHNICAL REQUIREMENTS
The contractor shall leverage existing Robotic Process Automation technology for implementation into the PEO C4I/SPAWAR Purchase Requisition business process in the NMCI environment. The bot shall minimize human intervention by developing configurations that automate manual and repetitive Purchase Request tasks; integrate with existing software; replicate desktop actions and is driven by simple rules and business logic. The bot provided shall verify data sets between systems (e.g. N-ERP, NMCI), copy data from one system to another system, print pages, create notifications, route notifications and create audit trails for future use.
The application and any specific configuration shall attain an Interim Authority to Test (IATT), Interim Authority to Operated (IATO) or an Authority to Operate (ATO) within 11 weeks of contract award under the Risk Management Framework (RMF) process. The contractor shall follow the Navy /Marine Corps Intranet (NMCI) integration and hosting requirements (CLIN 47 AB, AC and AF).
The contract shall submit a delivery plan (in contractor selected format) for the Purchase Request RPA pilot within one week of contract award.
The contractor shall inform the Government on the Robotic Process Automation (RPA) COTS software selection, assist with the RMF approval process and assist with loading and configuration of RPA software in the NMCI environment.
The contractor shall provide a Business Case and Plan for production and sustainment of the provided bot pilot.
4.0 PLACE OF PERFORMANCE
Space and Naval Warfare Systems Command (SPAWARSYSCOM), San Diego, CA
5.0 PERIOD OF PERFORMNACE
Twelve (12) weeks
File details come from the government source that posted it.