Attachment_1_ProjectTajMajal_CSO Call 7.xlsx

Instructions

Roles & Rates

UnitofIssue

CLIN 0001 Agile Kickoff

Feasibility: The plan must be realistic and achievable within the given constraints.

Stakeholder Approval: The plan must be reviewed and approved by all relevant stakeholders.

Alignment wiht Project Goals: The plan must align with the overall project objectives and goals.

Roles and Responsibilities: Clearly defined roles and responsibilities for all team members.

Communication Strategy: A Comprehensive communication strategy that ensures effiective information flow among stakeholders.

Performance Metrics: Defined performance metrics to measure project progress and success.

Acceptance Criteria Initial Deployment Plan, PMP, backlog, RTVM, and architecture submitted to Government

SLIN 0003 Requirements Traceability Verification Matrix (RTVM) The RTM is a document that maps and tracks the requiremnts throughout the project lifecycle. It ensures that all requirements are met and provides a clear likage between requirement, design, development, and testing. Ref CDRL 0005

SLIN 0004 Draft Architecture The Draft Systems Architecture provides an intial overview of the systeem’s structure, inlcuding components, interfaes, and data flow. It serves as a blueprint for the development and integration of the Oracle HCM SaaS solution. Clarity and Detail: The architecture must be clearly defined and detailed, coveraing all major components and interfaces.

Feasibility: The architecture must be feasible and align with the project’s technical requirements and constraints.

Stakeholder Approval: The draft must be reviewed and approved by all relevant stakeholders.

Alignment with Requirements: The architecture must align with the project’s requirements and objectives.

&"Helvetica,Regular"&12 &K000000&P

CLIN 0002 MVP Development

Clarity and Usability: The documents must be clear, easy to understand, and usable by the intended audience.

Stakeholder Approval: The documents must be reviewed and approved by relevant stakeholders.

Feasibility: The plan must be realistic and achievable within the given constraints.

Stakeholder Approval: The plan must be reviewed and approved by all relevant stakeholders.

Acceptance Criteria Draft training documents, Deployment plan, and Accepted MVP demo and Initial Intergrations submitted to Government

SLIN 0003: Accepted MVP Demo by Government Product Owner This sub-CLIN involves the demonstration of the MVP to Government Product Owner. The MVP should showcase core functionalities and integrations of the Oracle HCM SaaS solution. Functionality: The MVP must demonstrate all specified core functionalities and integrations.

Performance: The MVP must perform reliably and meet the performance criteria outlined in the project requirements.

Approval: The MVP must be reviewed and accepted by the Government Product Owner.

SLIN 0004: Initial Integrations Complete This sub-CLIN covers the completion of initial integrations required for the Oracle HCM SaaS solution. These integrations should ensure seamless interactions between the HCM system and other relevant systems. Integration Completeness: All specified integrations must be completed and functioning as intended.

Testing and Validation: The integrations must be thoroughly tested and validated to ensure they meet the project requirements.

Stakeholder Approval: The integration must be reviewed and approved by relevant stakeholders.

&"Helvetica,Regular"&12 &K000000&P

CLIN 0003 Core Modules

Clarity and Usability: The materials must be clear, easy to understand, and usable by the intended audience.

Stakeholder Approval: The materials must be reviewed and approved by the Government Product Owner.

Performance: The modules must perform reliably and efficiently.

Stakeholder Approval: The modules must be reviewed and accepted by relevant stakeholders.

Acceptance Criteria Training Material (CDRL, Dellivery of Core Capabilities, Test Automation and UTA Preparation

SLIN 0003 Test Automation This sub-CLIN involves the implementation of automated testing processes to ensure the reliability and performance of the OFC HCM SaaS solution. Test automation should cover key functionalities and integrations. Coverage: The automated tests must cover all critical functionalities and integrations.

Reliability: The tests must reliably identify issues and validate performance.

Stakeholder Approval: The automated testing processes must be reviewed and approved by relevant stakeholders.

SLIN 0004 UAT Preparation This sub-CLIN covers the preparation for User Acceptance Testing (UAT), including the setup of test environments, creation of test cases, and coordination with end-users. UAT preparation ensures that the system is ready for validation by end-users. Test Environment Setup: The test environments must be fully set up and configured for UAT.

Test Cases: Comprehensive test cases must be created to cover all key functionalities and scenarios.

Coordination: Effective coordination with end-users to ensure their participation in UAT.

Stakeholder Approval: The UAT preparation must be reviewed and approved by relevant stakeholders.

&"Helvetica,Regular"&12 &K000000&P

CLIN 0004 UAT & Final

Accuracy: The documents must accurately reflect the interfaces and integration points.

Stakeholder Approval: The ICAs and ICDs must be reviewed and approved by relevant stakeholders.

Test Reports: Comprehensive test reports must be submitted to the Government.

Approval: The test reports must be reviewed and approved by the Government Acceptance Criteria ICAs/ICDs Finialized, Full UAT complete and Test Reports submitted to the Government, Pass UAT and Dashboards and Reports Configured

SLIN 0003 UAT Passed This sub-CLIN involves the successful passing of UAT. The system must demonstrate that it meets specified requirements and is ready for production. Validation: The system must pass all UAT test cases.

Sign-Off: Successful completion and sign-off by the Government Product Owner.

Performance: The system must perform reliably in real-world scenarios.

SLIN 0004 Dashboards and Reports Configured This sub-CLIN covers the configuration of dashboards and reports within the OFC HCM SaaS solution. These tools provide critical insights and data visualization for effective management and decision-making Configuration: All dashboards and reports must be configured according to the project requirements.

Functionality: The dashboards and reports must function correctly and provide accurate data.

Stakeholder Approval: The dashboards and reports must be reviewed and approved by relevant stakeholders.

&"Helvetica,Regular"&12 &K000000&P

CLIN 0005 Hyperscare

P1 Resolution Time: 95% of P1 incidents resolved within 24 hours.

System Uptime: Greater than 99% availability.

- Concurrent User Capability: System supports up to 7,500 concurrently.

Key Process Usage: Greater than 80% of users utilize the new system for key processes.

User Satisfaction Score: 5 on a scale of 1-5.

- Critical Data Accuracy: 99.9%.

Data Integrity Checks: 100% of data integrity checks passed.

Data Reconciliation Completion: 100% of data reconciled and validated.

Deliverables should include support logs and user feedback reports.

Accuracy: The architecture must accurately reflect the system’s design and functionality.

Stakeholder Approval: The finalized architecture must be reviewed and approved by relevant stakeholders.

Acceptance Criteria Deployment support and Hypercare, Finalized System Architecture, Final Training Materials and Hypercare

SLIN 0003 Final Training Materials This sub-CLIN covers the delivery of final training materials for end-users of the OFC HCM SaaS solution. Materials should enhance user proficiency in system functionalities and key processes. User-Focused Refinement: Training materials must be updated based on feedback from end-users.

Comprehensive Coverage: The training materials must cover all key functionalities and processes.

Clarity and Usability: The materials must be clear, easy to understand, and usable by the intended audience.

Stakeholder Approval: The final training materials must be reviewed and approved by relevant stakeholders.

SLIN 0004 Hypercare This sub-CLIN ensures intensive post-deployment support, monitoring, and incident resolution to stabilize the system and provide immediate assistance to end-users. Hypercare support will focus on system performance tracking, incident resolution, and data integrity verification. Incident Resolution: P1 incidents must be maintained at fewer than 2 per week, with a resolution time of 95% within 24 hours.

System Uptime: Continuous monitoring to ensure greater than 99% availability.

Key Process Adoption: Over 80% of users must utilize the system for key processes.

User Satisfaction: Achieves a satisfaction score of 5 on a scale of 1-5.

Data Accuracy & Integrity: Ensures 99.9% data accuracy and 100% integrity checks passed.

Stakeholder Approval: Hypercare processes must be reviewed and accepted by relevant stakeholders.

&"Helvetica,Regular"&12 &K000000&P

Order Total

SaaS Pricing Tiers

Traceability Matrix

CLIN Validation Summary