OSI Policies

As part of an ongoing commitment to process improvement and quality within the organization, the Office of Systems Integration (OSI) has set forth the following policies to guide projects toward uniform standards of excellence in the management of OSI projects.

Note: The policies listed in this section still reference Systems Integration Division. The policies will be reviewed, revised and re-published in the future. For questions please use the Contact Us link.

OSI Policy on Adoption of the OSI Best Practices Website - This policy establishes the OSI Best Practices Website as the official repository for policies, standards, guidance, and industry best practices for projects managed by the Office of Systems Integration.

OSI Policy on Communications Management - This policy establishes the requirements for the collaboration and dissemination of project information between the various groups (within OSI and outside OSI) that have a vested interest in the project. Communications Management addresses such areas as governance, issue & action Item tracking, dispute resolution, escalation, problem tracking, status reporting, and performance reviews.

OSI Policy on Configuration Management - This policy establishes the requirements for the handling of project items as divided between three categories: project office items, prime contractor items, and stakeholder items, and addresses other areas such as the project website, documentation management, and project change control.

OSI Policy on Contract Management - This policy establishes the requirements for the oversight and management of any contractual agreements made between the project office and the two types of contractors used in projects: the prime contractor, and consultant contractors.

OSI Policy on Procurement Management - This policy establishes the requirements for the solicitation of a contractor (prime or consultant) for the project and addresses such areas as the IT Procurement Plan (ITPP), Request For Proposal (RFP), Statement Of Work (SOW), and Deliverable Expectation Documents (DEDs).

OSI Policy on Project Management - This policy establishes the project management requirements for all projects managed by the OSI. This policy is the overarching policy that identifies the highest-level documents for the project: The Project Charter and the Master Project Plan (MPP). The policy on Project Management also addresses several areas not covered by the other policies: Administrative Management, Human Resource Management, Implementation Support, Budget/Cost Management, and Schedule/Workplan Management.

OSI Policy on Quality Management - This policy establishes the requirements for defining what “good” and “acceptable” looks like for products created by both the project team and the contractors that support the project. The policy addresses such areas as the Quality Management Plan, metrics program, process improvement program, Test Strategy, System Test Plan, and Acceptance Test Plan.

OSI Policy on Requirements Management - This policy establishes the requirements for defining and managing the business, enterprise architecture, system, and software requirements for the project. The policy addresses such things as the Requirements Management Plan, the Interface Management Plan, and System Requirement Specification (SyRS).

OSI Policy on Risk Management - This policy establishes the requirements for managing project risk (as stated in the project Risk Management Plan), is in compliance with the Information Technology Oversight Framework, and includes additional best practices from the Software Engineering Institute (SEI).

OSI Policy on Training (Project Office) - This policy establishes the requirements for training that is required for all OSI staff as well as well as training that is unique to the composition of the project. Training requirements are delineated between “division-level” training (defined in the OSI Training Plan) and “project-specific” training (defined by the Project Training Plan).

OSI Policy on Transition to M&O - This policy establishes the requirements for dealing with a variety of Maintenance & Operations (M&O) transition situations, including: (1) Initial transition of projects from the System Implementation life cycle to the initial Maintenance & Operation (M&O) life cycle; (2) Transfer of responsibility from an M&O Type 1 provider to M&O Type 2 provider; and (3) Transfer of responsibility between subsequent M&O Type 2 providers (including impacts to state and county support entities caused by the transition).

Type 1 M&O represents the initial period of M&O (typically two to five years) that is part of the original system acquisition under the prime contractor. This approach is titled Type 1 M&O because it allows for extended testing and stabilization of the system while giving the project office time to make full transition into the M&O phase.

Type 2 M&O represents the life cycle phase that comprises full support of the production system for its remaining life. It does not necessarily involve the same support team from Type 1 M&O. Type 2 M&O typically has a five to twenty year lifespan depending on the system, and may include several reprocurements for continuing M&O (Type 2) services.