Before starting with the CATS+ TORFP Template, herein referred to as "O&M," agencies should have completed later-phase System Development Life Cycle (SDLC) activities if applicable and engaged in stakeholder discussions with the agency business unit, IT staff, and procurement office. These activities will help generate sufficient documentation of technical, business, and non-technical requirements for system O&M. O&M task orders normally are task based with requirements defined as duties and responsibilities. Questions about developing a TORFP may be referred to the DoIT Procurement Office at email@example.com.
Below are recommended best practices to help ensure a quality TORFP and timely release. This information is advisory only, some elements may not apply to specific TORFPs.
Routine operations, e.g., jobs processing
Routine support tasks, e.g., user help
Routine maintenance, e.g., table refreshes, data back-ups, etc.
Unique maintenance tasks, e.g., system patches, software / hardware upgrades, etc.
Consider a fixed hours / price structure for routine operations, maintenance and support tasks
Consider a "work order" process for ad hoc maintenance tasks (See Section 2.6.1 below)
Allow flexibility and evolution of duties; include a method to approve task changes via mutual agreement with the TO Contractor
Require the use of a work order tracking application
The TORFP Process:
100 Community Place, Crownsville, MD 21032
300-301 West Preston Street, Baltimore MD 21201
410-697-9700 - Dial 7-1-1 to place a call through Maryland Relay