A03_DRAFT PWS_AARO CMS.pdf

AARO CMS PERFORMANCE WORK STATEMENT (PWS) (April 2025)

Case Management System Development for the

Office of the Under Secretary of Defense for Intelligence and Security

May 19, 2025

Part 1

General Information

1. GENERAL: This is a non-personal services contract to develop and implement a Case Management System for the Office of the Under Secretary of Defense for Intelligence and Security, All domain Anomaly Resolution Office (AARO). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to develop and implement a Case Management System for the Office of the Under Secretary of Defense for Intelligence and Security, All domain Anomaly Resolution Office (AARO) as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: On July 15, 2022, the Deputy Secretary of Defense directed the Under Secretary of Defense for Intelligence and Security (USD(I&S)) to establish the AARO. USD(I&S) is the principal staff assistant and advisor to the Secretary of Defense and the Deputy Secretary of Defense on intelligence, counterintelligence, security, sensitive activities, and other intelligence-related matters and is responsible for administrative support to the AARO. The Deputy Secretary of Defense (DSD) and the Principal Deputy Director for National Intelligence (PDDNI) exercise operational control and direction. The Director of the AARO reports directly to DSD and PDDNI and is responsible for the whole-of-government efforts to detect, identify, attribute, and as appropriate, mitigate, spaceborne, airborne, and maritime objects of interest in or near national security areas.

1.3 Objectives: The contract would develop, implement, and sustain a case management system on the JWICS domain for AARO. The intent is to field this capability for AARO personnel at AARO HQ and for use at supporting organizations.

1.4 Scope: The contract would develop, implement, and sustain a case management system on the JWICS domain for AARO. Services include software development, fielding and certification of the software for the AARO JWICS domain, training of AARO personnel to use the software, sustainment, and spiral development of additional functionality. Onsite support consisting of a minimum of one (1) FTE would be provided.

1.5 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months and four (4) 12-month option years. The Period of Performance reads as follows:

Base Year Option Year I Option Year II Option Year III Option Year IV

1.6 General Information

1.6.1 Quality Control The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program (QCP) is the means by which he assures himself that his work complies with the requirement of the contract. The QCP is to be delivered within 30 days after contract award, three copies of a comprehensive written QCP shall be submitted to the KO and COR within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system.

The contractor will provide a monthly status report (MSR) no later than the 10th of every month accurately reflecting progress and a summary status of the tasks outlined in paragraph 5 and other requirements and deliverables in this PWS.

• Description of work completed and plans for next two months.

• Summary of Meetings between Contract Managers/PMs and the COR or other Government Point of Contact/Program Leads.

• Resource status

• Manning Status and related metrics.

• Travel conducted/projected.

• Issues and resolutions

The MSR shall be provided in Microsoft Word format and shall include the items listed above and other quality measures/metrics from the QCP or other information as requested by the COR.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays:

New Year’s Day, January 1.

Martin Luther King Jr.’s Birthday, the third Monday in January.

President’s Day, the third Monday in February.

Memorial Day, the last Monday in May.

Juneteenth National Independence Day, June 19.

Independence Day, July 4.

Labor Day, the first Monday in September.

Columbus Day, the second Monday in October.

Veterans Day, November 11.

Thanksgiving Day, the fourth Thursday in November.

Christmas Day, December 25.

1.6.4 Hours of Operation: The contractor is responsible for conducting onsite support, between the hours of 0700 to 1500 Monday through Friday and for at least 8 hours a day. Contractor personnel will have typical start days no earlier than 0600 and end times normally no later than 1800. Extended hours can be approved by the COR or Director of AARO to meet mission requirements. This excludes Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government direct facility closings. For other than firm fixed, the Contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract will be performed at the contractor’s facility (software development) and AARO’s offices located in the Mark Center at 4800 Mark Center Drive, Alexandria VA (onsite support) .

1.6.6 Type of Contract: The government will award a Time and Material contract.

1.6.7 Security Requirements: The Contractor shall possess and maintain a Top-Secret Facility Clearance from the Defense Counterintelligence & Security Agency (DCSA) at the time of proposal submission and maintain the level of clearance for the life of the contract. Contractor personnel performing work under this contract must have an active Top Secret (TS) security clearance from Defense Industrial Security Clearance Office with Sensitive Compartmented Information (SCI) eligibility, eligibility for access to Special Access Programs (SAP), and a current background investigation at time of award. Contractor personnel are required maintain the level of security required for the life of the contract. Proposed new contractor personnel shall possess the necessary security clearance requirements prior to being hired to work under this contract. The Contractor shall fully comply with all security requirements established for this Contract in the associated “Contract Security Classification Specification” (DoD Form 254). The security requirements are in accordance with the attached DD254.

CI eligibility, as defined by the Intelligence Community Directive (ICD) 704, Eligibility for Access to SCI, and reinforced in the DoD Manual 5105.21, Volume 3 is considered “in scope” for personnel security investigations (Tier 5, Tier 5 Reinvestigation) and access determinations that are void of deviations, conditions, or waivers. ICD 704.4 defines “in scope investigations” as those that are less than seven years old, without a 24-month break in service. To preserve reciprocity, the subject reinvestigation must be in progress within seven years from the completion of the previous investigation. SAP eligibility is defined by DoDM 5205.07-V2, November 24, 2015, Enclosure 4.

Continuous Evaluation (CE): The OUSD(I&S) Memorandum, "Department of Defense Guidance for the Implementation of Measures to Reduce the Federal Government's Background Investigation Inventory in Fiscal Year 2018", July 27, 2018, allows for the deferment of investigations and enrollment in CE. If a subject appears out of scope consistent with ICD 704, CE enrollment can be confirmed in the Defense Information System for Security (DISS) or Scattered Castles (SC). Once confirmed, the subject’s most recent SCI eligibility applies.

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use at the Mark Center. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.2 Key Control. The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.7.2.1. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.7.2.2. The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.7.3 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning technical aspects of the contract:

issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Key Personnel: The follow personnel are considered key personnel by the government: Once the system is developed and implemented, on-site support personnel are key personnel. The contractor shall provide a contract manager who shall be responsible for the performance of the work.

PWS Task # Position Qualifications 5.1, 5.2, 5.3, 5.4, 5.5 Onsite Program Manager (1 FTE) Minimum Skills/Experience:

5 years of public sector consulting experience.

5 years of experience in managing large complex Federal Government projects.

Security:

Top Secret/SCI eligibility.

Education:

Bachelor’s Degree (e.g. Business, etc.) or related field.

Preferred Education:

1.6.12 Identification of Contractor Employees: All onsite contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service.

1.6.13 Contractor Travel: Contractor will be required to travel CONUS and within the NCR during the performance of this contract to attend meetings, conferences, and training. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS.

Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

1.6.14 Other Direct Costs. Other direct costs requirements travel (outlined in 1.6.13), reproduction, and shipping expenses associated with training activities and visits to contractor facilities.

1.6.15 Data Rights. [See DFARS 227.71 and confer with OGC. Do not use legacy language on unlimited rights.]

1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Phase in Phase out Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the thirty

(30) calendar days phase in period during which the Contractor shall complete administrative and transition requirements, overlapping with the incumbent Contractors. The phase-in period will include onboarding new Contractor staff and acceptance of turned over system documentation. The Contractor shall work with the COR, Task Monitor, or Government Lead to obtain the following: network accounts, permissions, Common Access Cards, GFE, desktop software installations/configurations and any other materials or access needed to assume responsibility for supported systems. During the phase in period, the Contractor shall become familiar with performance requirements, transfer accountability of Government furnished equipment and tools, review respective standard operating procedures, and interface with appropriate Government leadership and staff. During the transition period, the new Contractor shall become familiar with all sustainment efforts and processes in order to commence full performance of services on the contract start date. During the phase-in period, the contractor shall execute the Phase-In Plan that it submitted with its proposal.

1.6.18 Phase-out: Address the plan for transitioning from an incumbent Contractor to a new Contractor and/or contract type and the plan for ensuring that government furnished items, property, or information is accounted for (The incumbent Contractor is responsible for reconciling discrepancies.). Include transition strategies, schedules and identify the individuals responsible for facilitating a smooth transition. A final written report will be delivered to COR and KO at least 30 days before the end of the contract.

1.6.19 Limitation on Subcontracting Reporting: The Contractor shall comply with FAR 52.219-14, Limitation of Subcontracting that’s listed in the contract, and submit yearly report at the end of each period of performance.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CASE MANAGEMENT SYSTEM. A case management system is a software solution designed to help organizations manage and track mission related data, cases, and interactions efficiently. Key features include:

• Centralized Information: It allows for the storage and easy access of case information, facilitating collaboration among stakeholders.

• Data Management: Users can compile and organize vast amounts of information.

• Workflow Automation: The system can streamline processes related to service requests, incidents, or investigations, enhancing overall efficiency.

• Interaction Tracking: It helps organizations track interactions across various channels, ensuring cases are resolved effectively.

• Document and Records Management: Many systems provide secure storage and sharing of essential documents related to cases.

• 1

2.1.3 CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.4. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.5. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.6. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.7. DELIVERABLE. Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

2.1.8. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.9. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.10. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.11. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.12. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.13. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.14. WORKDAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.15. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

ACOR Alternate Contracting Officer's Representative BCTF Boards, Commissions, and Task Forces CFR Code of Federal Regulations CMS Case Management System CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative COTS Commercial-Off-the-Shelf DD Form 254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DOD Department of Defense EM Enterprise Management Directorate FAR Federal Acquisition Regulation HIPAA Health Insurance Portability and Accountability Act of 1996 KO Contracting Officer OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program TE Technical Exhibit WHS Washington Headquarters Services

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide access to the JWICS domain as required to accomplish the tasks.

3.2 Facilities. The Government will provide the necessary workspace for the contractor staff to provide the onsite support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment].

3.3 Utilities: All utilities in the facility will be available for the contractor’s use in performance of tasks outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

3.4 Equipment. The Government will provide all onsite equipment.

3.5 Materials. Not applicable

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform offsite work under this contract that are not listed under Section 3 of this PWS.

4.2 Materials. The Contractor shall furnish materials, supplies, and equipment necessary to meet the off-site developmental requirements under this PWS.

4.4. Equipment. The Contractor shall provide all offsite equipment to meet the requirements under this

PWS.

PART 5

SPECIFIC TASKS

5. Specific Tasks:

5.1. Basic Services. The contractor shall p develop, implement, and sustain a case management system on JWICS for AARO. The intent is to field this capability for AARO personnel at AARO HQ and at supporting organizations.

5.2. Tasks

5.2.1 Procure required software licenses. Vendor will provide up to 100 licenses to AARO for the use of the CRM platform.

5.2.2 Development of Case Management Software. Vendor will use the CMS, Tableau, and develop additional requirements as provided by AARO to develop the CMS. At a minimum, the CMS will:

• Case Capture, Logging, and Categorization o Intake new data and information.

o Converts document content into structured data with unique identifiers automatically which can then be linked to case objects. Each case should be able to capture relevant data such as weather, location, distance, speed, etc.

o Categorize cases based on type, severity, and priority.

o Attach relevant metadata to incidents, such as timestamps and location, to cases.

o Generate automated responses to people submitting information.

o Triage cases based on predefined criteria, based by AARO, ensuring proper categorization and prioritization of incoming cases.

• Case Tracking and Monitoring o Track the status of cases from initiation to resolution.

o Provide real-time updates and notifications on case status changes.

o Maintain a history of action taken on cases.

• Workflow Management o Define and manage case workflows.

o Manage and track tasks and case deadlines by case and by user.

o Automate assignment of cases and workflow steps to appropriate personnel or teams o Support escalation processes for unresolved or high-priority cases.

• Communication and Collaboration o Enable communication between personnel through comments or chat features.

o Attach documents, images, metadata, or other files to case records.

o Provide a shared workspace for teams to collaborate on cases.

o Create a centralized dashboard for tracking and managing multiple cases and overall metrics. Monitor progress, allocate resources, and identify potential risks in real-time.

• Reporting and Analytics o Utilize Tableau as part of the reporting and analytics suite.

o Generate reports on case findings and resolutions.

o Generate administrative reports on incident trends, resolution times, and team performance.

o Provide dashboards with key performance indicators (KPIs) and metrics.

o Support custom report creation and data export capabilities.

• Access Control and Security o Implement either role-based access control (RBAS) or attribute-based access control

(ABAC) to restrict data access.

o Ensure secure data storage and transmission.

o Maintain secure data storage and transmission.

o Encrypt data in accordance with their sensitivity levels.

o Can gain an Authorization to Operate on JWICS fabric used by AARO.

• Integration Capabilities o Integrate with other systems such as CRM, or other communication tools.

o Support API access for data exchange with external applications.

o Enable integration with email and notification systems for alerts.

o Integrate with AARO’s current and planned data architecture.

o OPTION: Vendor will work with AARO to ensure the integration of CMS with additional data sources and architecture and across other domains.

• Knowledge Base o Maintain a knowledge base of common issues and resolutions.

o Allow for the creation and management of case-related documentation.

o Enable search functionality for quick access to relevant information.

• User Interface and Experience o Provide an intuitive and user-friendly interface.

o Offer customizable views and dashboards for different user roles.

• Feedback and Continuous Improvement o Collect feedback from users on incident management processes.

o Implement mechanisms for continuous improvement based on feedback.

o Provide a feedback mechanism and tracker to reporters of data o Support post-case reviews and analysis to improve future responses.

• User Training and Support o Provide user training.

o Provide user support.

o Be Section 508 compliant.

5.2.3. Development Sprints: After discussion with the vendor, the Government may execute this task to provide additional funding for new requirements identified through the development cycle to meet time deadlines and ensure CMS is sufficient to AARO’s requirement.

5.2.4. Deliverables: See PWS Technical Exhibit 2

5.2.5. Place of Performance/Delivery: Government sponsored office. The vendor shall provide a point of contact with managerial authority. This POC shall be available to the COR and AARO by telephone, upon request and within normal working hours, to coordinate delivery of services and resolve any discrepancies regarding the performance of the deliverables within this task order.

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required—usually a shall statement)

Standard Performance Threshold (This is the maximum error rate. It could possibly be “Zero deviation from standard”)

Method of Surveillance

PRS # 1.

The contractor shall conduct an in-person kickoff meeting to outline key goals, milestones, timeline, and requirements. .

The contractor provided the relevant personnel and staff for the kick-off and will be held within 14 days of award.

Zero deviation from standard

100 Percent Inspection by

COR.

PRS # 2

The contractor shall provide 15 licenses for the Tableau solution to USG (PWS 5.2.1).

The contractor provided the 15 Tableau licenses to the COR. The licenses will be compliant with DoD and Joint Service Provider standards and security requirements. Licenses will be provided within 14 days of award.

Zero deviation from standard.

100 Percent Inspection by

COR

PRS # 3

The contractor shall provide a monthly status report (PWS 1.6.1).

The contractor provided a monthly status report to the COR no later than the 10th of every month. The report will detail the activities done in support of this PWS for the previous month.

Zero deviation from standard.

100 Percent Inspection by

COR

PRS # 4

The contractor shall provide an in-person program management review meeting.

The contractor provided a program management review after 6 months from award and prior to 8 months from award.

The review will include progress towards the goals, milestones, and requirements established in this PWS and from the kick-off meeting.

(See example provided in PRS 1.)

Zero deviation from standard.

100 Percent Inspection by

COR

(See example provided in

PRS 1.)

PRS #5

The contractor shall provide the case management solution and remaining tableau licenses.

The contractor provided the case management solution and remaining 85 tableau licenses to the COR and USG within 12 months of award.

Zero deviation from standard

100 Percent Inspection by

COR.

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

Deliverable Frequency # of Copies Medium/Format Submit To Project Kick-off Meeting

Once within 14 days of award.

Once In person meeting and briefing slides in PDF or MS PowerPoint.

Monthly Status Report (PWS 1.6.1)

Once a month and no later than the 10th of every month.

One copy once a month and no later than the 10th of every month.

Electronic PDF file. COR

Software Licenses

(PWS 5.2.1)

Twice within the period of performance. 15 licenses within 14 days of award. The remaining 85 licenses within 12 months or with delivery of Task 5.2.2., which every is earlier.

100 licenses, Delivered via CD or electronically.

COR.

PWS Paragraph

5.2.2 Case

Management Software (PWS 5.2.2)

Once within 12 months of award.

15 copies Delivered and download electronically onto COR identified systems.

TECHNICAL EXHIBIT 3

ESTIMATED WORKLOAD DATA

Base Period: 12 Months Item Labor Category FTEs Hours

PWS

1.6.11

Program Manager 1.0 TBD

Option Period 1: 12 Months

PWS

Option Period 2: 12 Months

PWS

Option Period 3: 12 Months

PWS

1.6.11

Program Manager 1.0 TBD

Option Period 4: 12 Months Item Labor Category FTEs Hours

PWS