1. Rapid Operational Capacity

Example

The ROC is a rapid fielding prototype of limited capability. The first fielding of the ROC shall provide an early operational capability for the IRIS program no later than three (3) months from contract award. The purpose of the ROC is to provide early capability to the DoEE’s HRM Directorate and provide a method to measure vendor performance.

The Contractor shall deliver a capability that enables the Government to receive, create and store Human Resources data and related data. The Live Technical Demo should address the below capabilities. The follow listing of capabilities address both ROC and Increment 1.0 functionality but are not limited to items A thru N :

Attendance and Paid Time Off use
Pay raises and history,
Pay grades and Positions held,
Staffing and Position Classification capabilities
Unfair Labor Practice claims filed and tracked
U.S. Merit System Protection Board case tracking
Employee Performance Development Plans,
Training received and proposed,
Disciplinary action received and proposed,
Grievances filed and tracked,
Personal employee information,
Management and key employee succession plans,
Applicant tracking, interviewing, and selection.
Application Admin capability for HR Staff (to include user account provisioning)

The ROC shall be initially hosted in the DoEE facility. During IRIS increment 1.0, ROC will be ported into IRIS and IRIS will be hosted at a either a DOD facility or the hosting facility proposed by the Contractor. The Contractor shall provide hosting services and support to operate the delivered systems. (Note: The Government may, at its discretion, provide IRIS hosting services at a DoD Facility.)

2. Technical Objectives

Example

The Contractor shall deliver a solution that is highly interoperable with commercial products (preferably non-proprietary) thus allowing the Government to accomplish the following functionalities:

Operational capability included in the ROC
Fielding/legacy migration support to enable seamless transition from the current legacy capabilities to

Contractor developed systems

Development of capabilities based on a set of loosely-coupled interchangeable core components technology that uses open industry standards
Development of an information access and exchange capability that minimizes point-to-point system interfaces to communicate with an extensible list of Systems-of-Record (SoR) that will be provided during the

Requirements Phase of the System Development Life Cycle as discussed in your ITEC 630 textbook (as well as in class). Demonstration of what the Government will receive can be simulated with respect to minimizing point-to-point interfaces.

3. Help Desk Objections

Example

The Contractor shall provide a help desk management plan that is comprehensive. In addition, the Contractor shall provide: tiers one, two and three help desk support to IRIS (ROC and Increment 1.0) users to include system network administration and support staff (as determined by the Government hosting management). The help desk function shall at a minimum coordinate corrective actions, user queries, and system related trouble/issue responses, including service issues, incidents, training issues, and requests for fault/trouble isolation, correction and feedback.

4. Security Objectives

Example

5. Continuity of Operations

Example

The Contractor shall provide the necessary plans, processes, procedures, analysis, documentation, updates, tests, reports and management support to develop and maintain the appropriate levels of availability and documentation required for, at a minimum, MAC II systems. The Contractor’s COOP Plan shall support the prescribed IRIS

Program requirements. The Contractor shall provide, at a minimum, the necessary personnel, controls, processes, documentation, and technical and physical lifecycle support to plan, schedule and maintain the appropriate levels of

Continuity of Operations required for MAC II Sensitive systems and Federal Information Process

Standards-199/National Institute of Standards 800-53 Moderate systems. The Contractor shall provide, establish and/or develop, and test such Continuity of Operations, contingency, emergency response and computer network defense plans, procedures and processes as required by Federal policy or law. Please refer to the FEMA Federal

Preparedness Circular (FPC) 65, dated June 15, 2004.

6. Hosting

Example

The Contractor may provide Hosting services and support to operate the delivered systems in accordance with the overall IRIS requirements documentation. (Note: The Government may, at its discretion, provide IRIS hosting services.)

The Contractor’s solution shall be implemented for hosting in a managed facility compliant with Government hosting regulations, guidance, instruction, and policies. Government hosting planning shall include, as a minimum, characteristics such as physical and information security factors outlined in the Open System Interconnection (OSI)

Reference Model for all seven layers, specifically focusing on the Physical, Data Link, Network, and Transport

Layer. This planning should include providing a solution that is compatible within government hosting environment (e.g.

Department of Defense Hosting through the Defense Information Systems Agency (DISA) Defense Enterprise

Computing Center (DECC)) to include:

Computer/Application Hosting to support the development, testing, production, COOP, and hosting requirements for Reliability, Availability, Maintainability, Sustainability, and Performance of the system.
Global Information Grid (GIG) Engineering Services with adherence to GIG Instruction

DODI 8410.01 to support connection to Government owned networks and the mission of interoperability between commercial and government information systems.

Information Assurance (IA) with adherence to IA Instruction DoDI 8500.02 and DoDI 8580.01 to support of MAC II Sensitive operating environment.

Note: The Government will identify the increment 1.0 hosting facility (Government provided IRIS hosting services or exercise of this objective) after contract award.

Answer

Rapid Operational Capacity

The ROC is the initial and fast prototype of few capacities that shall provide a prior operational capacity for the IRIS program not later than three months from the day the contract was awarded. The essence of ROC is to offer the IRIS need to progress in a manner that maintains the organization dynamic and relevant, especially in the current state of complicated funding environment. While maintaining the capacities of its main programs in instrumentation, there is also a vast interest in the creation of other initiatives that explore the leading edge technology in addressing the engrossment of a more interdisciplinary scientific society and attracting other courses of funding to support the activities and programs.

Therefore, Contractor shall deliver such capabilities as; positioning and staffing categorization, salary allocations and positions, biased labor activities claims, employees’ appraisal developments and plans, proposed level of training, grievances raised, recruitment and selection etc.

Technical Objectives

The technical objectives tend to focus on a platform that governs the framework for key decision making by the IRIS program leadership. With that effect, the Contractor to be awarded should ensure that every action taken complies with the technical objectives. The Contractor, therefore, should ensure that the government achieves; its functional capacity included in the ROC, its legacy migration support that offers a unified evolution to contractor’s systems, the capacities are based on substitutable technology, and information availability and exchange capacities reduce point-to-point system interfaces.

Help Desk Objections

The Contractor shall offer a Help Desk plan to the clients with the key aim of involving the systems’ network administration and the support personnel in systems’ related concerns as service matters, occurrences, fault separation, and clients’ feedback etc. In essence, the support center will organize and manage the clients’ enquiries and offer a corrective actions against each.

Security Objectives

The Contractor shall provide an information security plan that is comprehensible to the principles underlined by the IRIS program to all the personnel and partners to follow and maintain the security of IRIS data and client’s information. The plan should involve a wide range of safeguards, security rules and responsibilities that develop and establish the outline for data management and information security.

Continuity of Operations

Continuity of Operations (COOP) is a government initiative that guarantees that various agencies are capable of maintaining their functionality of vital performance under a wide range of circumstances. The Contractor is, therefore, required to specify various requirements that enhance continuity plan development, as well as the development of programs that integrate, and overlaps the continuity capacity in the sustenance of the National Essentials Functions. In effect, the Contractor will offer the required plans, procedures, inquiry, documentation, tests, reports and management support to improve and maintain the suitable levels of availability and documentation required for COOP systems. The Contractor will also create and examine the likelihood, emergency response and computer network defense framework, and processes as stipulated for continued operations.

Hosting

Maintaining the integrity and security of the networks and servers is the key priority for the Contractor to ensure a safe and dependable system. The Contractor shall provide a hosting provider that will take care of various security measures, depending on the strategic plan of the contractor and are in compliance with the IRIS requirements documentation. The services shall avoid the usage of untrusted 3^rd party applications that have not undergone through the security audit but only allows such characteristics as Physical and Information Security factors defined in the Open System Interconnection (OSI).