P25 CAP Program Services

• Analyze the features and services of the manufacturer’s product to determine which P25 CAP test cases apply.

• Review any legacy P25 CAP reports tested to 2016/2017/2018 CAB requirements. Define any GAP testing or document upgrades needed to comply with 2017/2018 CAB’s.

• Provide Detailed Test Reports (DTR) of results for each and every test.

• Create Summary Test Report (STR) and Supplier’s Declaration of Compliance (SDOC) documents.

• Submit STR/SDOC’s to DHS S&T, answer all questions and resolve format or content issues.

“Beyond P25 CAP” Program

CTL can test features an agency finds important, or wants verified.

Before you purchase P25 Equipment –

• “Beyond P25 CAP” – Features with no published CAB’s – Agencies may want testing features/services to P25 standards not yet included in CAB’s These features or services may be important to the agency to accomplish their mission.
• Non P25 features – Agencies may want testing to verify features/services/specifications not included in the Project 25 program. These features or services may be important to the agency to accomplish their mission.
• Custom test plan – Verify compliance to TIA-102 standards. Create a custom test plan for the agency or their supplier to verify their compliance to the manufacturer’s features/services/specifications.

After you purchase P25 Equipment –

• Subscriber Unit (“SU”) Certification for use on the User System – Must be compliant and registered on the DHS Website. Review Documents, test results, features and services and compare to User Defined requirements.
• “Beyond CAP” – Features and services determined to be critical to mission accomplishment and/or written operation plans. Review manufacturer documents and compare to User Defined requirements.
• FCC/ISED et al certification test reports – Review Documents, Test Results  and compare to User Defined requirements.
• Ensure radios from varying manufacturers can perform the basic functions in this test plan and interact correctly with the User system. Includes test cases used for informational purposes and may/may not be mandatory for acceptance.
• Verification – Bench test features/services in the SU and issue a detailed test report of pass/fail. Work with User to develop a test plan.
• Acceptance – Field test the SU on the User system to ensure the performance according to the test plan. Work with User  to develop a test plan.

Periodically –

• P25 Compliant – Test the System Core to ensure it is still P25 CAP Compliant. This would be an ANAB and DHS accredited test. Issue detailed test report.
• System Performance – Develop a test plan to measure specified performance factors of the core site and other sites. This could include RF specs (power, alignment, spurious emissions, etc.) and/or data specs on the actual CAI and other data signals transmitted over the system.
• Coverage – Conduct drive tests to measure the coverage in all or sampled areas of the system.