Attachment_2_QASP.pdf

Attachment (2)

Quality Assurance Surveillance Plan

(QASP)

For

The National Training Center Mission Support (NTCMS)

W900KK-18-R-0015

Dated: 12 December 2017

Contents

1. Introduction

2. Roles and Responsibilities

3. Contract Requirements

4. Authority

5. Quality Assurance Surveillance

6. Documentation Procedures

7. Acceptance of Services

8. Remedies

9. QASP Changes

10. References

Appendix A – Publications

Appendix B – Methods and Metrics

Appendix C – Contractor Discrepancy Report (CDR)

Appendix D – Surveillance Checklist

1. Introduction

The purpose of this Quality Assurance Surveillance Plan (QASP) is to ensure the contractor satisfactorily performs the contract requirements, that the government receives quality services as defined in the Performance Work Statement (PWS) and to provide a planned process for assessing the contractor performance in a systematic manner. Performance assessment will be accomplished in accordance with this document and the terms of the contract.

This plan is a “living” document that can be revised or modified by the Government as circumstances warrant. It is based on the premise that the contractor, not the government, is responsible for managing and ensuring that contract requirements are met and that quality controls meet the terms of the contract. It is not intended to provide details of how the contractor accomplishes the work.

The surveillance/evaluation methods identified in the QASP, in concert with the contractor’s quality management and quality improvement procedures, provide a comprehensive approach to contract performance assessment. The COR will review the QASP to ensure that it will work in concert with the contractor’s Quality Control Plan (QCP). In areas where gaps or increased surveillance is warranted, adjustments may be made to the QASP.

In the event of a conflict between this QASP and contractually stated inspection requirements, the Order of Precedence (contract) shall prevail. (FAR 52.215-33) Items that are observed IAW this QASP may be used as input for documenting contractor past performance.

2. Roles and Responsibilities

The following individual direct roles for monitoring contract performance:

2.1 Contracting Officer (KO): The individual with a prescribed authority to enter into, administer, and/or terminate contracts and make related determinations and findings.

KO responsibilities:

1) Ensure appropriate contractual remedies and solutions are applied when contractors fail to meet contract requirements.

2) Ultimately responsible for final determination of the adequacy of the contractor’s performance in accordance with Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), DoD directives, instructions and policy letters.

2.2 Contracting Officer’s Representative (COR): The COR for this effort is the NTC Operations Group Director of Contracts. This individual is designated and authorized in writing by the KO to perform specific technical or administrative functions, and is the senior organization contract administrator responsible for adequate surveillance of contractor performance. A COR does not have the authority to change the contract terms, as this can only be accomplished by the KO.

COR Responsibilities:

1) Defines, guides, and coordinates surveillance activities to ensure satisfactory contractor performance of contract requirements

2) Ensures adequate resolution of contractor technical performance issues

3) Reviews SME documentation

4) Reviews the Contractor’s Quality Control Plan (QCP) in coordination with SMEs for acceptable quality level in all areas of the contract

5) Maintains consolidated quality assurance files and current SOPs

2.3 Assistant Contracting Officers Representatives (ACORs): The ACORs will be assigned during the transition period and updated semiannually. The Government will provide the Contractor with an approved list of ACORs, identified by the service section for which they are responsible. An ACOR can be responsible for more than one service category. The ACOR will be responsible to determine that the level of service provided meets or exceeds the PWS and the approved service sections SOP. The ACOR is the first person to review a services section SOP but they cannot approve the document.

The ACOR does not have the authority to change the contract terms, as this can only be accomplished by the KO.

3. Contract Requirements

The contract requirements applicable to this QASP are listed in the Performance Work Statement and Appendix D. However, the Government is not limited to contract monitoring/surveillance for only those contract requirements included in this QASP. The contractor is responsible for satisfactory performance of all contract requirements and the Government will modify methods and requirements subject to monitoring as necessary.

3.1 Safety: The ACORs and the COR will observe and determine if the contractor is abiding by safety rules and regulations. All safety items need to be rectified as they are identified. All data needs to be reported via the Management Interface System (MIS).

3.2 Other General Requirements: The ACORs and the COR will observe general on-site contractor performance. These areas include professional conduct and maintaining an orderly work space.

4. Authority

Quality assurance surveillance will be performed IAW the policies and procedures described in FAR Subpart 46.4, Government Contract Quality Assurance. Authority for issuance of QASPs is provided under the following clauses:

52.246-4 Inspection of Services-Fixed Price August 1996 52.246-5 Inspection of Services Cost-Reimbursement April 1984

5. Quality Assurance Surveillance

FAR Part 5 46.103(a) requires a Quality Assurance Surveillance Plan (QASP) for all service contracts. FAR 52.246-4 gives the Government the right to retest and inspect all services called for by the contract at any time so long as such tests and inspections do not unduly delay the contractor.

Quality assurance surveillance is prioritized to survey major outputs of the Performance Work Statement. The focus of the surveillance plan is on quality of the service, not on the procedures used to provide the service. The surveillance plan includes appropriate use to measure and/or conduct: progress/performance on the contract for (6.1), customer input (6.2), pre-planned inspections (6.3), meetings (6.4), and contractor reporting. The level of effort involved with the surveillance is commensurate with the criticality of a given phase of training and/or Governments concern over the execution of a given phase of the Performance Work Statement or the Performance Work Statement in its entirety.

The methods of evaluating contractor compliance may vary depending on the tasks specified by the PWS. The COR is responsible for selecting the method(s) to be used and the specific detailing of the method(s). In determining the evaluation method, considerations include surveillance resources available, what the contract specifically calls for, how performance can be observed, and if the method of surveillance is adequate to assure the required level of performance has been achieved. In making this determination, the COR also considers the Contractor’s Quality Control Plan (QCP).

Periodic (scheduled or non-scheduled) performance assessments will be accomplished utilizing a combination of assessment methods and metrics as identified in Appendix B.

The methods used for surveillance on this contract are contractor self-reporting, customer input, periodic performance meetings, periodic inspection, and observations.

5.1 Customer Input. The COR may receive customer input about the quality of services performed under the contract. These inputs maximize the government’s resource potential and are considered in regular assessments as they may identify contractor process improvement opportunities or required corrective actions; however, unsolicited input must be validated. Customer input requires documentation. The COR will document or obtain documentation from the customer and validate any input before commending the contractor or before corrective action is required from the contractor.

One of the first things a COR does after receiving a customer commendation or complaint is to notify the contractor that it is being given consideration.

5.1.1 Validation of Complaints - The ACOR must investigate all customer complaints in order to verify whether or not the complaint is valid. If the complaint is found to be valid, the ACOR must document it in their file by preparing a formal Contract Discrepancy Report (CDR) (Appendix D) and submit it to the COR who will submit it through the KO to the Contractor.

5.2 Pre-planned Inspections will evaluate tasks selected on other than a 100% basis as shown in Appendix D.

The COR will receive reports from the person conducting inspections. The KO or COR, will conduct inspections during their Government oversight visits. Inspections will be conducted for the items specified in the surveillance checklist (Appendix C). The effectiveness of Program Management is reflected in the quality of the products and services that will be evaluated with this checklist. It is recommended the inspectors print the documents out for use during inspections.

At the completion of the inspection, the inspector will document the inspection and, in an email, forward the completed checklist to the COR within ten (10) working days after the inspection. The documents will be maintained in the inspector’s files as described in paragraph 6.

5.2.1 Observation - Observation of contractor performance by the inspector can provide useful indicators of the contractor meeting contractual requirements. The COR will be guided by their observances as to whether additional actions are required which could include, but are not limited to, repeat performance of work, more frequent periodic meetings/reviews, and coordination with the KO as to further steps.

For the purpose of observation and inspections, the Contractor shall allow agencies or individuals authorized by the Government access to work performance areas. The CORs will conduct all observations or inspections in such a manner that it does not interfere with the contractor accomplishing PWS tasks.

5.3 Meetings Performance meeting/reviews are an effective tool for keeping performance on course, measuring performance levels, and making adjustments as necessary to avoid more serious deficiencies. Training event planning and other contractor performance related meetings attended by the KO or COR assist the Government with its oversight role. The contractor shall produce meeting minutes and forward them to the KO and COR for retention. The minutes are a useful source to review for surveillance and past performance purposes.

5.4 Contractor reporting The government will use the contractor’s reports as part of its surveillance process for monitoring the performance of the contract requirements.

6. Documentation Procedures

DOD guidance maintains the surveillance documentation constitutes an official record and the surveillance personnel assessing performance are to use a checklist to record their observations of the contractor’s performance. The guidance also concludes that all performance should be documented whether it is acceptable or not. All surveillance records will be maintained on file (digital preferred, with back up) for the length of the contract. The COR files will also contain documents listed in the COR and this QASP.

The COR will maintain copies of all inspections and performance issues of the contract.

Adequate surveillance and documentation of surveillance results, together with timely discrepancy reporting, are important activities in correcting Contractor errors, and acknowledging Contractor superior performance.

On closure of the contract, the files will be forwarded to the COR for consolidation and submission to the KO.

7. Acceptance of Services

The COR will review the contractors performance, deliverables, and other submittals (reports or plans). When performance does not meet standards, the CORs shall notify the KO. When performance exceeds standards, the COR and ACOR must document the performance in the monthly reports. The level of service is directly tied to potential incentive fees and the Contactors annual performance reports.

7.1 Deficiencies

If deficiencies are found during surveillance or through observation at any other time, the contractor must be notified. There are two reasons to notify the contractor of deficiencies:

1) We want the contractor to correct the problem. We’ve contracted for the performance of a needed service and want the service performed correctly and in accordance with the contract provisions.

2) The Government has a responsibility to mitigate any damages to the contractor.

Therefore, we do not want to keep these problems to ourselves. We need to advise the contractor of the problem so they can take corrective actions prior to the service being declared unacceptable for the surveillance period.

7.2 Discrepancy Reports

If any aspect of performance is not within conformity with the requirements of the contract, and is not immediately resolved, the COR will issue to the contractor a Contract Discrepancy Report (CDR). Guidance and an example is contained in Appendix C. Upon presentation of a CDR, the contractor shall immediately sign and return one copy. The contractor shall explain to the COR, in writing and within three working days of receipt of the CDR, why performance was not in conformity with the requirements of the task. The contractor shall also report corrective and preventative actions in its response to the COR. The COR shall maintain a file copy of the CDR.

Each CDR will be annotated as a critical nonconformance, major nonconformance, or minor nonconformance. A blank CDR is included at Appendix C for illustrative purposes and an electronic format is available via web.

8. Remedies

The COR will consult with the KO for nonconforming services remedies. FAR Part 46, Quality Assurance, Subpart 46.407 – Nonconforming Supplies and Services, paragraph f, states “For services, the contracting officer can consider identifying the value of the individual work requirements or task (subdivisions) that may be subject to price or fee reduction. This value may be used to determine an equitable adjustment for nonconforming services. However, when supplies or services involving minor non-conformances are accepted, the contract need not be modified unless it appears that the savings to the contractor in fabricating the nonconforming supplies or performing the non-conforming services will exceed the cost to the Government for processing the modification.”

9. QASP Changes

As a living document, this QASP is subject to change based on the PWS, mission, or other changes. Suggestions for improvements or changes should be sent to the COR.

Changes to the QASP will be provided to the KO and distributed to the CORs and the contractor.

10. References

The documents listed below form the basis for Quality Assurance Surveillance

1) Federal Acquisition Regulation (FAR)

2) Defense Federal Acquisition Regulation (DFARS)

3) Army Federal Acquisition Regulation Supplement (AFARS)

4) Performance Work Statement (PWS) NTCMS-PWS-01

Appendix A – Publications

FAR Part 46, Quality Assurance Subpart 46.4, Government Contract Quality Assurance 52.246-4 and 52.246-5 Inspection- Firm, Fixed Price with Cost Provisions (FFP + Cost) contract.

Appendix B – Methods and Metrics

Periodic performance assessments will be accomplished using a combination of assessment methods and metrics as identified in this appendix. Performance objectives in the Surveillance Checklist have been extracted from the PWS. All of the three rating categories are acceptable with the exception of “unsatisfactory.”

Frequencies:

Surveillance Method/By Whom Frequency Comments Contractor Self Reporting/Contractor Monthly COR reviews reports upon receipt and elevates any concerns to PCO Periodic Inspection Monthly Evaluates by using PWS and Appendix D

Surveillance Checklist Observation/PCO, COR, ACOR Monthly Evaluates by using PWS and Appendix D

Surveillance Checklist. COR’s periodic inspection will take the place of this report if none of the other personnel are able to observe contractor work performance.

Customer Input/Customer As received COR will validate unsolicited input, and respond to the customer

CORs will conduct monthly inspections using the attached Surveillance Checklist and documenting results on the checklist. The checklist data and COR observations will be condensed into the COR Observation Report Format, which will include, at a minimum:

1) Date, time and place of inspection

2) Who conducted the inspection and contractor personnel, by name, on hand for the inspection

3) Overall contractor performance

4) Details of excellent contractor performance

5) Details of less than adequate contractor performance (including any contractor responses and possible impact of performance to mission accomplishment).

The checklist contains a column for noting discrepancies for each inspected task Metrics:

Rating Definition

Above standards (3)

Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the element or sub-element being assessed was accomplished with few minor problems for which corrective actions taken by the contractor were highly effective.

Meets standards (2)

Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the contractor appear or were satisfactory.

Below standards (1)

Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the element or sub-element contains serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

The results of the inspection will be recorded in the respective columns of the checklist.

When the results are satisfactory, that is all that needs to be recorded. When the results are excellent or unsatisfactory rating is recorded in the comments column. If more space is required, use the back of the checklist. All unsatisfactory ratings will be brought the attention of the contractor and forwarded to the COR and KO.

If the unsatisfactory service must be performed by the contractor, the re-inspection of the performed service will be recorded on the checklist initially used. When the performance is satisfactory, this cancels the previous unsatisfactory rating. The COR will then line out and initial the unsatisfactory rating (being sure not to obliterate the entry). The COR will forward a copy of the revised checklist to the KO.

Appendix C – Contractor Discrepancy Report (CDR)

Nonconforming services will be documented on a DA 5479. Contract Discrepancy Report (CDR) IAW with paragraph 8 of this QASP. Each CDR will be annotated as a Critical, Major, or a Minor nonconformance.

A CDR officially documents unsatisfactory performance by a contractor. It includes a description of the deficiency, contractor response as to cause, contractor’s corrective action plan, the Government’s evaluation of the corrective action plan and any Government corrective action taken with the contractor.

Any life or mission threatening safety issue must be corrected immediately

Nonconformance Definition Response Requirements

Critical* Likely to result in hazardous or unsafe conditions for individuals, using, maintaining, or depending upon supplies of services; or is likely to prevent performance of a vital aspect of the contract

The contractor is provided 24 hours to provide written response to the CDR

Major* Other than critical, that is likely to result in failures of supplies or services, or to materially reduce the usability of the supplies of services for their intended purpose

The contractor is provided 5 calendar days to provide written response to the CDR

Minor* Not likely to materially reduce the usability of the supplies or services for their intended purpose, or is a departure from established standards having little bearing on the effective use or operation of the supplies or services.

The contractor is provided up to 15 calendar days to provide written response to the

CDR

*Definitions of nonconformance are derived from FAR 46.101

Some notes on filling out the CDR are shown at the end of the document

Block Sub-Part Comments

8 Actual Cause

Contractor will investigate and determine cause of the condition reported in Block 4. Actual cause should be stated as specifically as possible

8 Action Taken to Correct Corrective Action should address root cause, not the symptom

Action Taken to Monitor Effectiveness of Corrective Action

Generate data as proof. State the monitoring method put in place and who is responsible for reviewing the data

9 COR Signature/Title/Date Signed Form must be signed before returning

Appendix D – Surveillance Checklist National Training Center Mission Support (NTCMS) Services

Date and Time of Inspection:_____________________ _________________

Place of Inspection:______________________________________________

Inspector(Name/Rank):___________________________________________

Contractor Personnel Present:_____________________________________

Inspector Contact Information:_______________________________________

Organization: ____________________________________________________

Email:__________________________________________________________

Phone:_________________________________________________________

Rating Overall Contractor Performance:

E = Excellent*

VG = Very Good*

G = Good

SAT = Satisfactory

UNSAT = Unsatisfactory*(does not meet standard)

*The comments should provide details of Excellent, Very Good, and Unsatisfactory ratings (No Comments required for Good & Satisfactory)

Circle or mark overall rating

Appendix D – Surveillance Checklist (cont)

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.

* A sporadic review means at least 1 visit every 4 days per RTU. ACOR review will be conducted after each RTU event.

PWS Performance Standard Acceptable Quality Level

Performance Threshold

Method of Surveillance

2.5.2 The Contractor shall establish

clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement.

Provide a consolidated SOP on how the Contractor will manage the overall program requirements

SOP will identify all service requirements and how they will be accomplished

No more than (5) violations of the SOP per year. (0% allowed for Access Control)

COR Monthly review

2.5.3 The Contractor shall establish

processes and assign appropriate resources to effectively administer the requirement.

Provide qualified service providers for all PWS requirements

No less than 95% of agreed staffing level per service category and / or total effort

No more than 30 days per year will staffing levels dip below 95% for a category or total effort

COR Monthly review

3.1 The Contractor shall provide

access control services.

Security–in-depth control measures and access control IAW DoDM 5200.01

100% badge verification

No unauthorized access (0% tolerance)

Random security audit by NTC Security Manager

3.2.1 The Contractor shall support

the creation and presentation of an estimated 60 and 100 AARs per rotation for theater, mobile, and AVI sites to include live fire.

Video feeds are acceptable per the NTSC

95% of feeds pass NTSC level

No more than 1% of audio / video feeds are corrupt

ACOR review after RTU training event, COR Monthly review

AARs complete 6 hrs. after training battle

AARs complete IAW Rotation Plan

No more than (2) one hour AAR delay per

RTU

Facilitate hot washes within 1 hour after completion of a battle / training event

Hot washes are ready with minimal input and source data available

Facilitates 100% of assigned hot washes, no more than (1) one hour delay

3.2.2

The Contractor shall support the completion of no more than

(10) ten THPs for RTU distribution per year and shall maintain an electronic copy for historical purposes.

Provide (1) complete THP to the RTU per training event via regular mail NLT 7 days after training complete.

THP is shipped with an itemized list with a directory of files

THPs mailed to RTU with no more than (2) late ship dates per year

ACOR review after RTU training event, COR Monthly review

Provide (1) complete THP to the CALL per training event

Electronic copy of RTU THP with all files with electronic directory

THP sent to CALL NLT 14 days

- Maintain (1) complete digital copy of each final THP for two years

Raw data and final THP. Directory available

Raw and complete THP data available for review on site at the

NTC

3.2.3 The Contractor shall provide

services to cover the software licensing, hardware and extended phone support for the NLE AV production capabilities in the VVCEC and the Media on the Battlefield site.

Provide the AVID annual software and maintenance license agreement for both locations

100% AVID software coverage at both locations with no loss of capabilities

Active and operational 95% of time during non RTU days

Active and operational 99% of time during RTU events ( no more than 1 nonoperational)

ACOR sporadic review

3.3 The Contractor shall provide

integrated LVC simulation support for every training evolution.

Provide trained SMEs to operate all the LVC fielded systems at the

NTC

90% of all SMEs are cross trained on all systems

Between 95% and 100% coverage for every RTU with 0% capabilities reduction

ACOR review after RTU training event

3.4 The Contractor service shall

provide specially trained operators to create a real world battlefield and social media environment.

Provide operators to enhance the live training environment

Operators must meet the RTU plan in type, quantity and language skills

95% and 100% coverage.

ACOR review after RTU training event

Create pamphlets, posters, newspapers, press releases to

Materials must use data from the RTU and

Material prepared for each training event as directed by ACOR enhance the live training environment provide a realistic product

Replicate a realistic social media environment to conduct OSINT

Social Media Virtual environment must follow the RTU plan

100% Operational during scheduled time.

3.5 The Contractor shall provide

and support simulated Full Spectrum Operations battlefield effects.

SMEs must have live fire range experience and / or range safety experience

95% of requested battlefield effect delivered on time at the correct location.

A break or delay of training due to shift change or a lack of service providers is unacceptable.

ACOR review after RTU training event

3.6 The Contractor shall provide

DTOC and TAFF support for every training evolution.

Provide real-time data to the scheduled teams during each

RTU

All teams staffed to support the RTU with trained SMEs

95% and 100% coverage during scheduled time, NO loss of capabilities

ACOR review after RTU training event, COR Monthly review

3.7 The Contractor shall provide

real time monitoring, system data collection, computer operations, lifecycle maintenance and data analysis functions for the SOC.

Maintain individual service providers certifications IAW DOD 8570.01-M

Must be certified prior to award / within (30) days after hired after contract award

No lapse in certifications, compliance with employee certification plan

Sporadic ACOR review during RTU event, ACOR review after RTU training event, COR Monthly review

Maintain operational status of the 52 ID network

During RTU events the 52 ID must be operational 98% of the time

Training events that are reduced / delayed / degraded due to maintenance or system failure cannot exceed 2 hours.

3.8 The Contractor shall provide

Mission Command Information System Support for the Network Operations Center and DTOC.

Maintain certified SMEs Provide enough SMEs to perform all services simultaneously, Must be certified prior to award / within (30) days after hired after contract award

No lapse in certifications, compliance with employee certification plan

Sporadic ACOR review during RTU event, ACOR review after RTU training event

3.9 The Contractor shall provide

technical support for the integration of the provided DCGS-A assets.

Maintain certified SMEs Provide enough SMEs to perform all services simultaneously, Must be certified prior to award / within (30)

No lapse in certifications, compliance with employee certification plan

Sporadic ACOR review during RTU event, ACOR review days after hired after contract award after RTU training event

3.10 The Contractor shall provide

SME to perform Radio Operations/ TOCNET support.

Maintain certified SME Must be certified prior to award / within (30) days after hired after contract award

No lapse in certifications, compliance with employee certification plan

ACOR review after RTU training event

3.11 The Contractor shall provide

SMEs to provide Joint Planner Support Operations.

Maintain certified SMEs Provide enough SMEs to perform all services simultaneously, Must be certified prior to award / within (30) days after hired after contract award

No lapse in certifications, compliance with employee certification plan

Sporadic ACOR review during RTU event, ACOR review after RTU training event,

3.12 The Contractor shall install, remove, troubleshoot, store, and maintain the FBCB2/BFT/ JCR provided communications.

Scheduled equipment for each RTU installed and operational on time

Installed equipment must pass inspection prior to release.

Equipment must be at or above 90% operational status. A break or delay of training due to shift change or a lack of service providers is unacceptable.

ACOR review after RTU training event,

3.13 The Contractor shall provide

SME to advice on replication of HUMINT operations.

Maintain certified SME Must be certified prior to award / within (30) days after hired after contract award

No lapse in certifications, compliance with employee certification plan

ACOR review after RTU training event, COR Monthly review

3.14 The Contractor shall provide IA

Core Support for each RTU

Replicate different Unified Action Partners with SMEs

Provide enough SMEs to perform all services simultaneously

95% and 100% coverage during scheduled time, NO loss of capabilities

ACOR review after RTU training event

Provide a Senior Management Curriculum and Scenario Developer

Must be qualified prior to award, no waiver for experience is authorized

95% and 100% coverage during scheduled time, NO loss of capabilities

3.15 The Contractor shall provide

SMEs to conduct the LTP training package.

All SMEs meet or exceed the experience level required

A temporary waiver for a reduction of an experience

95% and 100% coverage during

ACOR review after RTU training event requirement can be requested via the

PCO.

scheduled time, NO loss of capabilities

3.16 The Contractor shall provide

SMEs to perform SOF support

Maintain certified SMEs Provide enough SMEs to perform all services simultaneously

95% and 100% coverage during scheduled time, NO loss of capabilities

ACOR review after RTU training event

3.17.5 The Contractor shall provide a

single graphical user interface to the Contractor's relational/transactional database or databases to provide accurate, complete, comprehensive management information in real-time or near real-time (near real-time means that information is delayed only due to automatic data processing time).

Continuously accessible system that provides required data for Contract administration assistance and Performance tracking

MIS must be operational and accessible within the first 60 days during transition and operational and accessible throughout the life of the contract.

All data must be extractable and exportable.

Must be operational Monday through Friday during NTC business hours during non-RTU days.

Must be continuously operation during RTU events (out of operation no more than 2 hours per RTU event).

COR Monthly review