Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * Schedule information * Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • Status of each order and CLIN * Plans and recommendations for future priorities and activation of work items * Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • Requirements traceability * Assessment of progress toward enterprise integration • Quality assurance activity * Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.
Status Reporting. 1. Closure of problem reports shall require an examination of the symptoms to determine if the fault is hardware or software related or both.
Status Reporting. Watchit Media will provide weekly status reports, addressing the following areas: · Overall Project Status – highlighting activities performed during the reporting period, activities planned for next reporting period, schedule variances, variances in the financials of the project, hours actually performed per phase vs. hours originally planned for same phase and staffing · Issues – escalation of project issues, obstacles · Risks – escalation and visibility into project risks, and mitigation strategies · External Project Dependencies – escalation and visibility into external project dependencies and requirements · Change Requests – escalation of project change requests, requiring approval to change project scope, timeline, and/or cost · Milestones – escalation and visibility into key project milestones · Key Performance Indicators (KPIs) – highlighting progress against phase exit criteria and deliverable completion
Status Reporting. Consortium members executing Project Agreements executed under this Agreement shall provide status reporting as specified in each Project Agreement. This status reporting will, at a minimum, require a monthly status report and, upon completion of the project, a final report that provides a recap of the program that may be used for public release purposes. The Consortium Member awarded a Project Agreement shall prepare and submit the following Reports to the CM for each Project Agreement they have been awarded.
Status Reporting. Provide written status reports to FBCDD once per month throughout the duration of the project. Project status reports will include, at a minimum, a summary description of activities completed, description of activities planned for the next 30 days, financial status of the project, status of schedule for the project, and identification of any technical or other issues which may have an impact to the overall project budget and/or schedule. Project status reports will be provided with each invoice.
Status Reporting. Service Provider will provide status updates during the Outage isolation and resolution process, which may include the following information:
Status Reporting. The Medpace Senior CTM will serve as the central channel for communication between Medpace and VIVUS. The OB-301 CTM will work in conjunction with the clinical monitoring group to track study progress and report to VIVUS on a weekly basis. In addition, the OB-301 CTM will be responsible for overall management of site information, overseeing the status of Investigator contracts, direct supervision of CRAs, tracking of enrollment information, and distribution of study supplies. The Medpace OB-301 CTM will be the primary contact for the sites to address protocol interpretations and inclusion/exclusion criteria. All protocol-related issues will be recorded in an ongoing document to ensure consistency. The CTM is available 24 hours a day, 7 days a week via the Medpace Project Helpline. Medpace will develop a communication plan at the start-up of the study. The CTM will work with the VIVUS project team to define details regarding study communication, including status reporting and team conference calls. Medpace typically delivers status reports on a predetermined day (and time) of the week, which is established around the weekly team calls so that the information can be discussed. Utilization of IVRS will also allow the project team to review patient status on a real time basis. The Medpace CTM will collaborate with the Medpace Medical Expert and the VIVUS Study Manager to address any questions that may arise. The ClinTrak Study Management databases will serve as the primary source of project status information and will allow the Medpace CTM to report on any aspect of the study. The databases are updated on a real-time basis, providing accurate and up-to-date information. Elements of ClinTrak include: · Phone contacts; · Monitoring visit reports; *** INDICATES MATERIAL THAT WAS OMITTED AND FOR WHICH CONFIDENTIAL TREATMENT WAS REQUESTED. ALL SUCH OMITTED MATERIAL WAS FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO RULE 24b-2 PROMULGATED UNDER THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED. · Patient status including details on withdrawals during the treatment phase; · Study supplies; and · Protocol deviations. Medpace will provide weekly status reports via a secure project website, to include the following status by site: · Number of patients screened; · Number of screen failures; · Number of patients randomized; · Number of patients dropped with drop rates; and · Number of patients completed. In addition, monthly reports will be provide...
Status Reporting. 5.1 Scirex will provide status reports on the Projects as agreed to in each specific Project Exhibit. The status reports will include, but not be limited to: the number of patients entered, dropped, and completed in the Projects. Reports of monitoring visits will also be provided on a timely basis as specified in attached Project Exhibits.
Status Reporting. All of the Studies shall be performed in close cooperation with Sponsor, and designated Sponsor personnel will be kept informed of the progress of the Study. CRU shall also provide Sponsor status reports on the Study in accordance with the IPA. The status reports may include, but not be limited to, the number of subjects entered, dropped, and completed in the Study.
Status Reporting. Each Party shall prepare a [**] Development Report regarding each [**]-month period, which shall show the status and progress of the development in respect of the Licensed Product that this Party has made during such [**]-month period against the activities and timelines listed in the Development Plan or decided in writing by JDC. Except as may be otherwise agreed upon in writing by the other party, such [**] Development Report shall be submitted to the other party within [**] days past each [**]-month period [**] and at least [**] days prior to JDC Meeting set for in Article 2. The [**] Development Report due on [**] of the year [**] shall be the [**], which details the progress that the Party has made against the activities and timelines listed in the Development Plan or decided in writing by JDC during the [**].
