TE-3_NEC-CDRL_2_Nov_2016.xlsx
XLSX spreadsheet 29 KB Posted
- Attached to
- NEC-RIA ITSS Recompete Federal contract opportunity
- Solicitation number
- W52P1J-16-R-4002
About this file
TE-3_NEC-CDRL_2_Nov_2016
View the file
Other files for this federal contract opportunity
Show all 30
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Baseline CDRL
| CONTRACT DATA REQUIREMENTS LIST (CDRL) FOR NEC-RIA ITS CONTRACT - BASELINE | |||||
| PWS Reference | Requirement Title | Report Description | Initial Submittal | Subsequent Submittals | |
| Frequency | Copies | Distribution | Method of Delivery |
1.5 Alert Support Roster Contractor Alert Support Roster to include Full name and their after hours oncall phone number in order they are to be called by the NEC or other Government support agency Contract start Within one day of any changes 1 AESD (online portal) /
NEC-RIA AESD AOR /
| NEC-RIA/JMC/ASC CORs | Electronic Excel Spreadsheet | |||||||
| 1.4.1 | Employee Roster | Contractor Employee Roster to include Full name, phone extension, support group/team | 5 calendar days prior to contract start | Within one day of any changes | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic Excel Spreadsheet | |
| 1.6 | Joint Inventory Listing | Annual and Contract Phase-out Inventory | Upon Contract Start | Annually; |
Upon contract phase out; or
| Upon request | 1 | NEC-RIA COR and | ||||||
| Property Book Officer (PBO) | Electronic Spreadsheet | |||||||
| 1.7 | Key control officer | A report which lists the employee and assigned keys | Upon initial receipt of keys | Semi-Annually | 1 | NEC-RIA Key Control AOR | Electronic Excel Spreadsheet | |
| 1.10.1.2. | Information Assurance | Contractor Employee Training/Certification report to include Full name, certifications, ATCTS registration completion date | Contract start | Within 5 working days of change | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.11.1 | Anti-Terrorism Training | complete Antiterrorism (AT) Level I Awareness training within 30 calendar days after start of employee performance on this contract. | 30 calendar days | Within 5 working days | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.11.1.1 | iWATCH | all contractor employees and subcontractor employees performing work under this contract, are trained on the local iWATCH program | 45 calendar days | Within 30 days of start of new employee | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.11.1.3 | OPSEC | all employees, including sub-contractors performing work under this contract, complete Level I OPSEC training | 30 calendar days | Annually | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.12 | CMRA | Contractor shall report all Contractor manpower (including sub-contractor manpower) required for performance of this contract | Reported by 31 October of contract award | Annually by 31 October | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.15. | Staff and Key Personnel | The Contractor shall identify the staffing plan and organization required to meet the objectives and requirements identified in this PWS. | Contract start | Annually | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet/Word | |||||||
| 1.15.3 | Organizational Structure and Key Personnel | The Contractor shall identify, maintain, and update a list of Key Personnel within their organization for all requirements identified in the PWS. | Contract Start | As Needed | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet/Word | |||||||
| 1.15.4. | Recruitment and Retention Plan | The Contractor shall provide the Government with a recruitment and retention plan | Contract Start | As Needed | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 1.17.2 | In-Process Reviews (IPR) | The Contractor shall plan and conduct IPRs every two weeks. IPRs will present, discuss, and analyze trends in system performance, support center performance, and to conduct forecasting with respect to system upgrades, deployments, projects, and other potential, or planned surge situations. | 14 days after contract start | Every two weeks | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 1.17.2 | New Technologies | present a new technology, concept, or change to existing technology in an effort to enhance NEC capabilities or efficiencies. | 3 months after start of contract | Every Quarter | 1 | PCO/ | ||
| NEC-RIA COR | Electronic Excel Spreadsheet | |||||||
| 1.18 | Quality Control Plan | Contractor's Quality Control Plan | Contract start | As needed | 1 | PCO/ | ||
| NEC-RIA/JMC/ASC CORs | Electronic Word document | |||||||
| 1.19 | Quality Assurance | Complete and return the Contract Discrepancy Report | Five days after receipt from Government | Five days after receipt from Government | 1 | PCO/ | ||
| NEC-RIA COR | Contract Discrepancy Report Form | |||||||
| 1.23. | Quarterly Reimbursable Report | A quarterly reimbursable report which includes customer organization, the amount of labor dollars and material dollars charged to the customer for that quarter. | Within 3 working days following the end of the government quarter after contract start | 3 working days after the end of the standard government quarter | 1 | NEC-RIA COR/NEC-RIA SLM | Electronic | |
| 1.23. | Contractor Clearance Annex A | Detailed Report Utilized by 106th SIG BDE to track contractor clearances by SMO codes | Contract start | Within 2 working days following the deaprture or arrival of an employee. | 1 | NEC-RIA COR | Electronic Spreadsheet | |
| 1.23. | After Hours Support Data Analysis | Detailed report of all NIPR/SIPR after hours support by month. Report should include ticket number, customer name, VIP status, date/time opened, date/time acknowledged, date/time resolved, date/time closed, ITSM template, description of resolution. Reports should be split into 5 tabs: ASC, JMC, ACC-RI, First Army, NEC (everyone else) grouped by NIPR and SIPR. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic | |
| 1.23. | Incident Resolution Deficiency Report | A detailed report that shows all incidents in which the contractor did not meet the performance requirements of the contract. This report will show the time required to meet standards of performance, the amount of time that the contractor missed the requirement, the reason for the failure and proposed resolution and plan to avoid future problems. The report will at a minimum show the time opened, the time work began and the resolution time. | Within 3 working days following the end of the first calendar month after contract start | Weekly | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic | |
| 1.23. | Army IT Metrics Program | Quarterly data for all services that fall within the scope of this contract IAW the current Army Information Technology standard metrics program. | Within 5 working days following the end of the government quarter after contract start | 5 working days after the end of the standard government quarter | 1 | NEC-RIA | ||
| COR/IT Metrics AOR | Electronic | |||||||
| 1.23. | Infrastructure | Projects and economic analysis may be requested | Contract start | Specific requests from higher headquarters | 1 | NEC-RIA COR/Infrastructure AOR | Electronic | |
| 1.23. | C4IM Performance Measures Program | A Plan of Actions and Milestones (POA&M) for the corrective action for each C4IM performance that is lower than identified in the performance documents accompanying the contract for approval by the government. | Within 15 working days following the end of the government quarter after contract start | 15 working days after the end of the standard government quarter | 1 | PCO / | ||
| NEC-RIA COR | Electronic | |||||||
| 1.24.1 | Safety Program | Establish and implement a comprehensive Safety Program Plan | 30 calendar days | 5 days from changes | 1 | PCO / | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 1.26 | Remote site travel | Request for travel, including names of travelers, cost under the JTR, detailed proposed itinerary and purpose of travel, including coordination steps required and that have been performed. | In advance of any travel requirements after Contract start | Request for Travel prior to travel dates; After action report within 3 working days upon return from travel | 1 | PCO / | ||
| NEC-RIA COR | Electronic | |||||||
| 1.26.1 | Travel/Training Costs | Submit all requests for reimbursable travel/training prior to commencing travel or training | 10 workdays prior to travel/training | 10 workdays prior to travel/training | 1 | PCO / | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 1.26.2 | Remote site travel | Provide an after action report to the Government upon return from travel. | 3 days after travel | 3 days after travel | 1 | PCO / | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 1.28 | Obtaining Materials and Supplies to in Timely Manner | A report that includes all materials and supplies (and invoices) purchased by the contractor during the reporting period. Report will reflect anything reimbursed by the customer via credit card transaction or modification to the contract. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA COR | Electronic | |
| 1.29 | Process and Procedures Documentation | The Contractor shall develop and operate a document management system utilizing standard naming conventions for document retrieval. | Within 60 Days of award of contract | Always available | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic (and Paper if required) | |
| 1.30 | Records Management Plan | he Contractor shall provide a record management plan to the COR within 60 days of the award of the contract. | Within 60 Days of award of contract | As needed | 1 | PCO / | ||
| NEC-RIA COR | Electronic Word document | |||||||
| 5.1.4 | Interactive Customer Evaluation (ICE) Satisfaction Survey | Forward ICE survey link/instructions to the customer for all work completed. Use web-based ICE system to review all responses, follow-up with customers on all responses requiring follow-up, and update customer comment card notes field with "No follow-up required" for all responses not requiring follow-up. | Contract start | Within 3 working days following completion of work request; | ||||
| Customer response follow-up within 2 days of receipt | 1 | Customers | Electronic | |||||
| 5.1.8 | Project Implementation and Management | Provide project status updates | Every Two weeks or when any significant change occurs | Every Two weeks or when any significant change occurs | 1 | NEC-RIA COR | Electronic | |
| 5.1.13 | Warranty Repair | provide all required data to designated Government personnel for acquiring or renewing maintenance | Contract start | One Year Prior to equipments warranty expiration or as needed | 1 | NEC-RIA COR/AOR | Electronic | |
| 5.2.1.2.3 | Storage Services | Conduct monthly data restore testing | Contract start | 5 business days after testing | 1 | NEC-RIA COR | Electronic | |
| 5.2.1.2.4 | Storage Utilization | provide storage utilization, performance reporting, trending, and management capabilities | Contract start | Every 14 days during IPR | 1 | NEC-RIA COR | Electronic | |
| 5.2.3.2.5 | Software/Hardware Installs and Uninstalls | Detailed report, grouped by customer organization, of all software and firmware installs, updates, configurations and uninstalls (ticket number, customer information to include office symbol, Software, version, Serial Number, System Name). | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic Excel Spreadsheet | |
| 5.2.3.2.6 | Software Testing/patching/version Upgrade Report | Provide a detailed report on the outcome of any software testing/patching/version upgrade performed; i.e., ticket number, customer information, system name, software, test or patch or version upgrade, if hardware, if involved specify which HW; grouped by customer organization. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic Excel Spreadsheet | |
| 5.2.3.5 | Life Cycle Distribution Report | Detailed report of life cycle replacement (LCR) distribution project. Report should include a schedule with owning organization, projected completion date, list of affected equipment or software or anything considered LCR. | 5 working days following the first request for Life Cycle Replacement Requirement | Weekly | 1 | NEC-RIA/JMC/ASC CORs, NEC-RIA QAEs | Electronic | |
| 5.2.4.2. | Web Support | The Contractor shall provide a formal web application change management process to deploy and maintain web sites, portals, web pages, and customized applications. | Contract start | As needed | 1 | NEC-RIA COR | Electronic | |
| 5.2.4.4 | Scans | perform monthly scans for compliance | Contract start | 3 workdays of each month | 1 | NEC-RIA COR | Electronic | |
| 5.2.5.1.5 | Scans | Notify the Government of any discrepancies, problems, or anomalies with scans. | Contract start | Within 2 hours | 1 | NEC-RIA COR | Electronic | |
| 5.2.6.1 | Utilization Reports of Networks | Provide a utilization report per established schedule. | Contract start | Weekly and upon request | 1 | NEC-RIA COR | Electronic | |
| 5.2.6.4.1 and 5.2.6.4.3. | Network Management | Perform network discovery and conduct fault analysis. | 1 working day of discovery | 1 working day of discovery | 1 | NEC-RIA COR | Electronic Excel Spreadsheet | |
| 5.2.6.4.1 | Outages | Mass notification of problems affecting a large user base (network down; power outage). Notification must include a means to inform key staff (Technical POCs) for all Mission Partners if notification via email or network is not available. | Within 30 minutes of discovery of an outage | As required for outages | NEC, Technical POCs and/or key individuals, User base as required | Most Expedient Method available. If email or network outage, by phone. | ||
| 5.2.7.1.1 | COOP | implement and exercise IT Service Continuity Management in support of installation COOP for critical portions of the automation infrastructure. Provide AAR upon completion. | Perform annually | Provide AAR within 5 days of completion | 1 | NEC-RIA COR | Electronic Excel Spreadsheet | |
| 5.2.7.1.3 | COOP | Test recovery of data monthly and provide a synopsis of the test results to the COR. | First Month following contract start | monthly | 1 | NEC-RIA COR | Electronic Excel Spreadsheet | |
| 5.2.7.2.1 | Disaster Recovery | Create and Test Disaster Recovery Plan using metrics to assess the effectiveness of the plan | Provide Plan within 30 days of contract start. | Test Annually and provide AAR within 5 Days of completion | 1 | NEC-RIA COR | Electronic Word document | |
| 5.2.8.3 | Service desk System Management Opened Tickets data analysis | Detailed report of all NIPR/SIPR tickets opened weekly. Report should include ticket number, customer name, VIP status, date/time opened, date/time acknowledged, date/time resolved, date/time closed, ticket status, ITSM template, description of resolution. Reports should be split into 5 tabs: ASC, JMC, ACC-RI, First Army, NEC (everyone else) grouped by NIPR and SIPR. | First business day following the first contract week | First Business day following week end | 1 | NEC-RIA/JMC/ASC COR | Electronic | |
| 5.2.8.4 | Automation Service Support | Send out approve email notifications no less than 24 hours prior to scheduled outage or system mainatenace | Contract start | monthly/ As needed | 1 | NEC-RIA COR | Electronic | |
| 5.3 | VTC Bridge Report | A monthly VTC Bridge usage report that includes Command requesting the bridge, requested conference length, actual time used, Participant Transport time (sum of all connections), Participants total duration for All end Points, and a summary total for all conferences by Command. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA COR/NEC-RIA VTC AOR | Electronic | |
| 5.4.3.1 | Security Risk Assessment, Information Assurance Certification and Accreditation Program, and Certificate of Networthiness (CON) | Maintenance of all data and documentation required by RMF and DoD 8500.2 IA Controls compliance | Contract start | Always available | 1 | NEC-RIA IA RMF AOR | Electronic (and Paper if required) | |
| 5.4.3.1 | Security Risk Assessment, Information Assurance Certification and Accreditation Program, and Certificate of Networthiness (CON) | Review C & A annually | Annually | Annually | 1 | NEC RIA COR | Electronic | |
| 5.4.3.2. | Vulnerability Risk Assessment | Provide analysis and reports of known or potential LWN vulnerability risks to the Government on a weekly basis. | One week after Contract Start | Weekly | 1 | NEC RIA COR and IA | Electronic | |
| 5.4.4.1 | Defense in Depth | Report undisclosed classified incident remediation. | As necessary | As necessary | 1 | NEC RIA COR and IA | Electronic | |
| 5.4.4.2. | Information Assurance (IA) Reporting | Report IA resource requirements to the NEC. | Within 60 Days of contract start | As necessary | 1 | NEC RIA COR and IA | Electronic | |
| 5.4.4.2. | Information Assurance (IA) Reporting | Provide success or failure information and reports about signature updates and last-run status | As incident(s) occur | As necessary | 1 | NEC RIA COR and IA | Electronic | |
| 5.4.5.1 | IAVA Reporting | IAVA compliance reporting in the required database (e.g., A&VTR, VMS); systems in AITR, CND IN FISMA). Initial IAVA report is required upon receipt of an issued IAVA. | Contract start | Weekly updated reports required until compliance is achieved. | 1 | NEC-RIA IA | https://home.ria.army.mil/sites/itsecurity/its_iavaComplianceIntro.cfm | |
| 5.4.5.1 | IAVA Reporting | The Contractor shall develop Mitigation Action Plan (MAP) and IAVM Plan of Action and Milestones (POA&M). | Within 60 Days of contract start | As necessary | 1 | NEC-RIA IA and COR | Electronic | |
| 5.4.7.1. | Installation IA Program | Publish electronic messaging security guidance in conjunction with the Local Network Security Guidance. | Within 60 Days of contract start | As necessary | 1 | NEC-RIA IA and COR | Electronic Word document | |
| 5.4.9.2 | Security Reviews and Vulnerability Assessments | conduct security reviews and vulnerability assessments of installation units for compliance with IAVM policies and messages and coordinate the review of alternate security request, based on MAP and POA&M before approval by the appropriate Designated Approving Authority. | Contract start | As necessary | 1 | NEC-RIA IA and COR | Electronic | |
| 5.4.5.3 | IA Reporting | Detect and report malicious/unauthorized activity to the Government | Contract start | As necessary | 1 | NEC-RIA IA | Electronic | |
| 5.4.5.2 | IA Scanning | Compile vulnerability reports from routine and random network and system scanning. Vulnerability reports to facilitate corrections forwarded up System Administrators/POCs | Contract start | As detected | 1 | NEC-RIA IA | Electronic |
&P
ASC Above Baseline CDRL
| ABOVE BASELINE ARMY SUSTAINMENT COMMAND (ASC) - CDRL | ||||
| PWS | ||||
| Reference | Requirement Title | Report Description | Initial Submittal | Subsequent Submittals |
| Frequency | Copies | Distribution | Method of Delivery |
| 5.5.1.1. and 5.5.1.5. | DBA Support Report | Monthly DDL_AUDIT_INFO report on each DB instance, OS user name, user name, user hostname, terminal, timestamp, action name, owner, object name, return code and return text. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | ASC COR | Electronic Excel Spreadsheet |
| 5.5.1.2.1. and 5.5.1.5. | Conference Room Event Incident | Detailed report of a scheduled event that incurs an equipment incident*. Report should contain full details of issues, actions taken to resolve, resolution or conclusion of event. G6 should be alerted as a heads-up of equipment issues and provided copies of any non-phone correspondence related to troubleshooting. |
*Example of event with incident would entail connectivity issues before or during event, voice feedback or loss of video during scheduled event - any type of issue that requires technical involvement or intervention. During all troubleshooting efforts, techs should provide a heads-up to the G6 of any issues encountered as soon as time allots and, subsequently copy G6 on any non-phone correspondence during the troubleshooting phase.
| Example of event without incident would entail connectivity without issue, no voice feedback or dropping of connectivity of any type during scheduled event | During the course of event as required | 1 hour after event depending upon support provided | 3 | ASC COR, AMSAS-IMC Chief, Deputy Chief of Staff for Information Management or equivalent G6 military | Electronic | |||
| 5.5.1.2.1. and 5.5.1.5. | Conference Room Scheduling/Usage Report | Detailed report of conference room scheduling/usage to include number of events scheduled in each room, secure or non-secure event, event purpose, type of support provided (e.g. open the room only, full support during Commanding Generals presence, etc.), NEC technician supporting the event/room, duration, highest ranking official in attendance and an overall total for all conference rooms supported. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 3 | ASC COR, AMSAS-IMC Chief, Deputy Chief of Staff for Information Management or equivalent G6 military | Electronic | |
| 5.5.1.2.2. | VTC Conference Room Equipment | The Contractor shall be responsible for providing the Government all information/costs regarding maintenance for the conference room IT equipment. | 180 days prior to maintenance expiration | Annually | 1 | ASC COR | Electronic | |
| 5.5.1.3.2 | After Hours Support Secure Video Bridge | All ‘On-Call’ conferences shall be documented and information concerning the call shall be provided to the COR for situational awareness | Contract start | Business Day following On-Call | 3 | ASC COR, AMSAS-IMC Chief, Deputy Chief of Staff for Information Management or equivalent G6 military | Electronic | |
| 5.5.1.3. and 5.5.1.5 | Secure Bridge Event Incident | Detailed report of a secure bridge that incurs an equipment incident*. Report should contain full details of issues, actions taken to resolve, resolution or conclusion of event. G6 should be alerted as a heads-up of equipment issues and provided copies of any non-phone correspondence related to troubleshooting. |
*Example of event with incident would entail connectivity issues before or during event, voice feedback or loss of video during scheduled event - any type of issue that requires technical involvement or intervention. During all troubleshooting efforts, techs should provide a heads-up to the G6 of any issues encountered as soon as time allots and, subsequently copy G6 on any non-phone correspondence during the troubleshooting phase.
| Example of event without incident would entail connectivity without issue, no voice feedback or dropping of connectivity of any type during scheduled event | During the course of event as required | After event depending upon support provided | 3 | ASC COR, AMSAS-IMC Chief, Deputy Chief of Staff for Information Management or equivalent G6 military | Electronic | |||
| 5.5.1.3 and 5.5.1.5. | Secure Bridge Scheduling/Usage Report | Detailed report of secure bridge support. Report should include number of bridge events scheduled for the month, | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | NEC-RIA VTC AOR | Electronic | |
| 5.5.1.4 | System Accreditation and Re-Accreditation for Secure Video Bridge | Assist in performing yearly reviews of the accreditation, or whenever changes/additions are made to the system and prepare risk assessments. | Contract start | yearly/as needed | 1 | AMSAS-IMC Chief | Electronic |
Above Baseline All Tenants
| ABOVE BASELINE - ALL TENANTS CDRL | ||||
| PWS | ||||
| Reference | Requirement Title | Report Description | Initial Submittal | Subsequent Submittals |
| Frequency | Copies | Distribution | Method of Delivery |
| 5.5.4.2. | Server Support | |||||||
| Physical Server Support | Monitor server and event logs and report changes to mission partners POC on a monthly basis. | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | For each customer purchasing this service | Electronic | ||
| 5.5.4.2. | Server Support | |||||||
| Physical Server Support | Develop, and maintain documentation of server changes/configurations and provide change documents to the POC quarterly. | Within 3 working days following the end of the first Fiscal quarter after contract start | Every Quarter | 1 | For each customer purchasing this service | Electronic | ||
| 5.5.4.4 | Embedded Tech for Above Baseline IT Tech Support | Report that includes Ticket number, customer's name, office symbol, barcode, make and model | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | For each customer purchasing this service | Electronic | |
| 5.5.4.6. | Above Baseline Desktop Support for VIPs | Report that includes Ticket number, customer's name, office symbol, barcode, make and model | Within 3 working days following the end of the first calendar month after contract start | Every month by the 3rd workday | 1 | For each customer purchasing this service | Electronic |
File details come from the government source that posted it. Updated .