HC102815R0025_ATTACH_J-4_DIDS.docx

Source Selection Information – See FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

DRAFT HC1028-15-R-0025

ATTACHMENT J-4 DIDs

CARTS R/M DOCUMENT REQUIREMENTS — DATA ITEM DESCRIPTIONS (DIDs) General Requirements For All Documents

1. Changes. Contractor will describe and track Government approved changes to all documents in a table in each document that lists the date, section and page, and nature of change.

2. Format. The DIDs will be produced in Microsoft (MS) Office format. The contractor will use MS Word to produce written documents, MS PowerPoint for presentations, MS Project for schedules, and MS Excel for spreadsheets.

· Page Size. The paper copies will be legible and suitable for reproduction. The pages will be printed on 8.5 x 11 inch paper, sequentially numbered, and placed in a three-ring binder.

· Table of Contents and Index. Plans of more than 30 pages in length will contain a Table of Contents. Plans of more than 120 pages in length will also include an index.

3. Distribution. Documents should be distributed in accordance with the following:

· One electronic transmittal letter will be delivered to DITCO at the following email address: michelle.r.crain2.civ@mail.mil

· One electronic copy will be delivered to DeCA at the following email address: Ericka.pearson@deca.mil

Title: Program Management Plan; DID 6.1

Purpose: Provide the format, content, and intended use for the Program Management Plan generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Organizational Structure. The Program Management Plan will:

· Describe the contractor’s organizational structure and functions, duties, and responsibilities that will be assigned in support of CARTS R/M requirements as specified in the SOO and its attachments. The plan will include quality recognitions and certifications such as ISO 9000/9001, Malcolm Baldrige Awards, or Software Engineering Institute Capability Maturity Model and Integration Level.

· Identify the contractor’s procedures, policies, and reporting requirements established to initiate, monitor, control, complete, and report on activities required by CARTS R/M as specified in the SOO and its attachments.

2. Methodology. The Program Management Plan will:

· Provide a narrative description clearly defining the technical approach including tools, standards, and procedures to be used to accomplish the delivery of CARTS R/M as specified in the SOO and its attachments to include an associated contractor work breakdown structure (CWBS).

· Describe reports and reviews the contractor will deliver to the Government to document and review program status, challenges, and achievements to effectively manage the program. All documentation, activity, or decisions required from the Government will be identified in the Program Management Plan.

3. Personnel. The Program Management Plan will list the contractor’s management personnel that direct CARTS R/M as specified in the SOO and its attachments. The plan will list the education, training, skills, and experience of the personnel assigned to each of the key positions. The plan will also stipulate that the Contracting Officer’s Representative (COR) will be notified in writing of any additions, deletions, or changes in all proposed key work assignments before the change occurs. No change in key personnel will be implemented without the prior written approval of the COR.

4. Other Subjects. The following functions will also be addressed in the Program Management Plan: risk mitigation, quality control of Government property, delivery procedures, testing and certification, packaging and shipping, reliability, configuration control, and any special or unique security requirements regarding the SOO or its attachments.

5. Schedule. A MS Project plan that indicates the critical path, milestones, and events associated with the delivery of CARTS R/M. The level of detail must be sufficient to clearly show how each task and subtask will be performed.

6. Risk Management. The contractor's approach to risk management for CARTS R/M that describes how the contractor plans to identify, analyze, monitor, mitigate, and document risks. The Program Management Plan will include an initial risk assessment.

Submission. The Program Management Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 business days of Government review; and update 90 business days after contract award.

Title: Acceptance Test Plan; DID 6.2

Purpose: Provide the format, content, and intended use for the Acceptance Test Plan generated by the specific task requirement in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Organizational Structure. The Acceptance Test Plan will:

· Describe the contractor’s organizational structure and functions, duties, and responsibilities that will be assigned in support of the acceptance testing for CARTS R/M, ensuring support of the required integration with the EBS NCR Retalix 10 point of sale (POS) software.

· Identify the contractor’s procedures, policies, and reporting requirements established to initiate, monitor, and complete test activities required by the contract.

2. Methodology. The Acceptance Test Plan will include the following:

· Testing and Acceptance. The contractor will describe testing and acceptance procedures for pre-delivery acceptance testing in the contractor’s test facility, DeCA test lab, and live operational environment. Acceptance testing already conducted or to be conducted by the contractor will be described to include integration of the EBS NCR Retalix 10. The contractor’s acceptance test plan will include a description of the following procedures:

· Evaluation of requirements as specified in the System Performance Specification (SPS) to ensure compliance

· Evaluation of system performance (including stress/load testing) and satisfaction of thresholds for key performance parameters and key system attributes

· Evaluation of hardware components for operational and functional capability, and adequacy and maturity of integration

· Verification of technical data accuracy and ease of use of the system and user documentation

· Evaluation of the ability to coordinate and install CARTS R/M collaboratively with NCR (the EBS contractor).

· Scope of Test. Describe the hardware component items that will be or have been tested, test procedures that will be or have been used, the functions that will be or have been tested, any measurements that will be or have been taken, and the performance objectives. Describe any differences between the system components that will be or have been tested and the system proposed to DeCA.

· Test Conditions. The contractor will describe the following test conditions:

· If testing was conducted in a laboratory test bed or in a live environment

· Hardware components that will be or were involved

· Communications devices and interfaces to business or other systems that will be or were involved

· If live or test data will be or was used

· Any data generators or simulations that will be or were used, and how measurements will be or were taken

· If testing will be or was conducted in a live environment, also describe size of a typical site, number of sites involved, transaction volumes, employee and customer involvement, and test control measures employed.

· Test Locations. List all test locations and describe the functions to be performed at each location.

· Test Results. Describe procedures and format for reporting test results and tracking/correcting discrepancies discovered during testing.

3. Personnel. List the contractor’s management personnel that direct the specific tasks, projects, and programs.

4. Security. Identify any special or unique security requirements resulting from the contract.

5. Schedule. Milestone charts and other charts that indicate responsibilities and resources required to complete all phases of testing. The level of detail will be sufficient to clearly show how each task and subtask will be performed. Detail must include the required integration with the NCR Retalix 10.

Submission. The Acceptance Test Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 business days of Government review; and update 90 business days after contract award.

Title: System and User Documentation; DID 6.3

Purpose: Provide the format, content, and intended use for the System and User Documentation generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The System and User Documentation will provide up-to-date CARTS R/M technical systems and user documentation. The documentation will include:

· Hardware technical manuals,

· Operating system manuals, and

· Preventive and routine maintenance procedures and schedules including clear designation of responsibility (contractor or government).

Submission. The System and User Documentation will be submitted in accordance with the SOO Section 6.0. Deliverables — provide six months after contract award; updates one year after contract award; and then appropriate updated documentation as the system evolves.

Format. The System and User Documentation will be the standard COTS format.

Title: Training Plan; DID 6.4

Purpose: Provide the format, content, and intended use for the Training Plan generated by the specific task requirement in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Strategy. The Training Plan will contain an overview of the contractor’s strategy to provide:

· COTS training. At least 30 days before the Developmental Test and Evaluation (DT&E), the contractor will provide training on the commercial off-the-shelf (COTS) hardware at DeCA HQ. The target audience will be DeCA subject matter experts (SMEs) who will assist the contractor with configuring the COTS hardware. The objective of this training is to provide insight on configuration and technical aspects of the solution.

· Test team training. The contractor will train the DeCA test team on all aspects of the CARTS R/M hardware in preparation for Government test and evaluation. This training will include training on user and technical aspects of CARTS R/M. The test team training agenda should mirror the store-level user initial training. As part of the Government testing and evaluation, the Government test team will evaluate the contractor-provided training, training aids, and materials. Ergonomic training will be included.

· Initial User / Super User Training. In collaboration with DeCA HQ personnel (and NCR as required), the contractor will provide initial user and super user training. This will provide super users and key system users training of hardware use and troubleshooting.

· End / Business User Training. In collaboration with DeCA HQ personnel (and NCR as required), the contractor will provide user training to end users. This training may be combined with DeCA/EBS training. The contractor should provide their proposed method of training delivery (onsite, virtual, or computer based training (CBT)). The contractor must also identify a means to validate that trainees have grasped the required knowledge. Validation results and corrective action to resolve training deficiencies must be provided to the CARTS R/M PMO during each site’s post conversion support period. Appropriate ergonomic training will be included.

· Sustainment training. Upon DeCA’s request, the contractor will provide user or technical sustainment and/or refresh training to DeCA personnel. The contractor will provide instructors and necessary training materials. Sustainment/refresher training may be broken out in the following categories:

· User level training conducted at DeCA HQ, DeCA test lab, or on-site at a specific commissary location.

· Technical or SME training at DeCA HQ, server center, or at a specified location, as deemed necessary.

2. Organizational Structure. The contractor will provide a detailed description of the training organization structure to include the methodology for delivering quality training.

3. Curriculum. As a minimum, the Training Plan will include details on the course structure, overall strategy, programs of instruction, training documentation, syllabuses, training materials, training devices, method for delivering lesson plans, schedules, locations, and support requirements.

4. Schedule. The Training Plan will include a milestone chart graphically depicting the schedule of events associated with the contract. The level of detail will be sufficient to clearly show how each task and subtask will be performed. Training delivery dates and technical modules must be clearly defined.

5. Materials. Draft training materials will be delivered to the Government for review and comments prior to the beginning of test team training. Training materials will be evaluated during test team training and further evaluated during operational testing and evaluation (OT&E). Final Government acceptance of training material will not be given until completion of OT&E.

6. Qualifications. The Training Plan will include detailed instructor qualifications and experience.

Submission. The Training Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 business days of Government review; and update 90 business days after contract award.

Title: Modernization and Implementation Plan; DID 6.5

Purpose: Provide the format, content, and intended use for the Modernization and Implementation Plan generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Organizational Structure. The Modernization and Implementation Plan will:

· Describe the contractor’s organizational structure and functions, duties, and responsibilities that will be assigned in support of the tasks specified in the SOO and its attachments.

· Identify the contractor’s procedures, policies, and reporting requirements established to initiate, monitor, control, complete, and report on activities required by the delivery or task order.

2. Methodology. The Modernization and Implementation Plan will include the following:

· Installation procedures for:

· The DeCA Test Lab.

· The five test commissaries, Server Centers, and Headquarters solution designated for test and acceptance.

· Full scale deployment to all other operating locations once test and acceptance is complete.

· Major tasks, responsibilities, resources, and schedules required to integrate and install CARTS R/M hardware to include loading the hardware with the NCR Retalix 10 software.

· The CARTS R/M PMO will work with the contractor after contract award to finalize the deployment schedule beyond pilot site installations.

· The CARTS R/M PMO will coordinate the deployment schedule with DeCA management for approval prior to finalization.

· The contractor is responsible for obtaining customs clearance for equipment delivered outside the continental United States.

· Support services required for deployment including:

· Pre-configured hardware

· Training

· Post installation support. This will include assisting supervisors with operational issues, correcting procedural problems, reporting and resolving hardware problems, and conducting training sessions

· Installation and de-installation (repair of any damages during installation)

· Trade-in and disposal of all de-installed equipment

3. Personnel. List the contractor’s management personnel that direct the specific tasks, projects, and programs specified in the SOO and its attachments.

4. Security. Identify any special or unique security requirements resulting from the contract.

5. Schedule. Include milestone charts and other charts that indicate the task, responsibilities, and resources required to complete deployment of the CARTS R/M hardware.

Submission. The Deployment and Implementation Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 business days of Government review; and update six months and 12 months after contract award.

Title: Maintenance Plan Hardware (HW) and Software (SW); DID 6.6

Purpose: Provide the format, content, and intended use for two Maintenance Plans generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Overview: Although one Maintenance Plan will be submitted—it must address maintenance for both the existing CARTS system (hardware and software to include all current functionality as outlined in the SOO and its attachments) and the new CARTS R/M hardware.

Content.

1. Organizational Structure. Both Maintenance Plans will:

· Describe the contractor’s organizational structure and functions, duties, and responsibilities that will be assigned in support of the contract.

· Identify the contractor’s procedures, policies, and reporting requirements established to initiate, monitor, control, complete, and report on activities required by the contract.

· List the contractor’s management personnel that direct the specific tasks, projects, and programs.

· List the contractor’s field locations and staffing that will support all DeCA locations worldwide as well as commissaries where it may not be economically feasible to provide routine/preventative on-site maintenance as required.

2. Methodology. Both Maintenance Plans will contain a description of the following concepts and procedures for maintaining the POS hardware to ensure hardware availability with a minimum threshold of at least 98% system availability and an objective of 99% (calculated as detailed in the System Performance Specification 2.4).

· Describe maintenance procedures for the various types of system failures such as critical, non-critical, and routine failures.

· List mean time between failure data for all hardware

· List mean time to repair data for all hardware

· List mean down time (MDT) data for all hardware (the average total downtime required to restore a hardware item to full operational capabilities)

· Describe hardware maintenance escalation procedures

· Describe procedures for processing and addressing repeat discrepancies

· Describe levels of maintenance support and procedures for unscheduled, scheduled, or preventive maintenance to include upgrades to

· Hardware

· Firmware

· Describe depot maintenance procedures and provisioning for spares and repair parts

· List and describe the type, distribution, and function of test, measurement, and diagnostic software and equipment

· List and describe all technical manuals and repair documentation

· List all hardware including warranty provisions

· Describe alternative hardware maintenance plans or service level agreements for routine and critical failures where it is not economically feasible to provide on-site maintenance within the specified maintenance response and repair times, and list the locations

· Describe configuration management procedures and applications for maintaining and accounting for the CARTS and CART R/M hardware baselines

· Describe procedures for installation/replacement and removal/disposal of equipment

· Describe the procedures for preventive maintenance to include the list of required tasks, frequency, and responsible party (contractor or government)

· The contractor must provide a schedule for all preventive maintenance for DeCA review and approval

· The contractor must provide detailed instructions for any preventive maintenance required to be completed by DeCA personnel

· The contractor must submit reports showing completion of all scheduled preventive maintenance with a signature of acceptance by DeCA personnel

3. Process Flow Diagram. Both Maintenance Plans will include diagrams depicting the process flow of events associated with the delivery or task order. The level of detail will be sufficient to clearly show how each task and subtask will be performed.

Submission. Both Maintenance Plans will be submitted in accordance with the SOO Section 6.0 Deliverables—draft with proposal; revisions within 30 days of Government review; and update six and 12 months after contract award.

Title: Help Desk Support Plan; DID 6.7

Purpose: Provide the format, content, and intended use for the two Help Desk Support Plans generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Overview: Although one Help Desk Support Plan will be submitted—it must address help desk services for both the existing CARTS system (hardware and software to include all current functionality as outlined in the SOO and its attachments) and the new CARTS R/M hardware.

Content.

1. Strategy. Both Help Desk Support Plans will include the organizational structure, program management plan, methodology, personnel, call center structure, and management triage process including escalation procedures and certification process, security, quality assurance, and reports. The plan will detail help desk support for both the CARTS R/M hardware and sustainment of the legacy CARTS.

2. Organizational Structure. Both Help Desk Support Plans will include an organization chart and supporting narrative portraying the contractor's business (corporate) structure. It will describe the functional relationships and responsibilities among the organizational elements that will participate in the accomplishment of the contractual commitments.

3. Program Management. Both Help Desk Support Plans will define the direct lines of control, responsibilities, functional relationships, and authority between the Help Desk function and the contractor's other organizational elements. The plan will also describe all interfaces between the contractor and the Government as well as those between the contractor and other contractors that are necessary to accomplish help desk support.

4. Methodology. Both Help Desk Support Plans will include:

· 24/7/365 procedures to allow for direct call in support from the DeCA Enterprise Service Desk. The help desk procedures will include prioritized evaluation and dispatch procedures. The plan must provide the process that will provide the CARTS R/M PMO with direct access into the help desk ticketing system and required ad hoc reports. This process must provide real time status of the incident/resolution process. Access will be provided to archived, store-specific data, for trending and analysis by DeCA. All reporting must be automated. The help desk will provide electronic notice to the DeCA Tier 1 Enterprise Service Desk of incident establishments/closures. Recipients of incident notice/closure will be established with the contractor after contract award. Additionally, all CARTS R/M alerts must be monitored and coordinated with the DeCA Tier 1 Enterprise Service Desk. Help desk support will include periodic meetings and interfaces with DeCA.

· A narrative description of the technical approach and methods the contractor will employ to support customer identified hardware and software problems. The narrative will address Help Desk mode of operation, updates to the help desk knowledge base, responsiveness to worldwide locations, escalation process, measures of call center effectiveness, and method of certification for the call center and personnel. Additionally, the contractor is required to keep the knowledge base updated as part of the help desk scope. The contractor must provide an online knowledge base and provide DeCA with access.

· A list of the contractor's help desk management personnel that direct call center operations. The list will include the education, training, skills, experience, and security requirements of the personnel required to fill each position and will state the identity, background, and work experience of the personnel assigned to fill those positions.

· Identification of software tools to track and report incidents and software tools supporting the knowledge base.

· Description of the staffing required for proper accomplishment of help desk operations by skill type, skill level, number of personnel, and security clearance. The plan will state the number of personnel currently available, the number of new hires required to accomplish each task as scheduled, and the time required to train and prepare those new hires.

· Description of the procedures to ensure adherence with Service Level Objectives as outlined in paragraph 3.5.3 Service Level Objectives (SLOs) of the Functional and Technical Requirements (SOO Attachment C).

6. Security. A description of the security policies, practices, and procedures that will be used in conjunction with the project to protect contractor and Government assets and personnel.

7. Quality Assurance. A description of the quality assurance plan for delivering quality services to the Government, for all tasks specified in the PWS. Inclusion by reference to the Quality Assurance Plan is acceptable.

Submission. Both Help Desk Support Plans will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with proposal; revisions within 30 days of Government review; and update six and 12 months after contract award.

Title: Configuration Management Plan; DID 6.8

Purpose: Provide the format, content, and intended use for the Configuration Management Plan generated by the specific task requirement in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Organizational Structure. A description of the contractor’s organizational structure and assignment of functions, duties, and responsibilities that will be assigned in support of the contract.

2. Methodology. A comprehensive approach for delivering Configuration Management Plan services to the Government, for all tasks specified in the SOO and its attachments. The following will be incorporated into the Configuration Management Plan:

· Standards and policies for effective configuration management of delivered hardware. An updated inventory list of the installed hardware will be provided to the CARTS R/M COR after each deployment.

· Methods, procedures, and controls for effective configuration management to include:

· Configuration item identification

· Configuration change control

· Controlled storage and release management including firmware

· Change control flow

· Change documentation

· Change review process to include timelines for delivery of change requests

· All change request proposals must be submitted to the government within 30 days of written notice of requirements

· All final proposals must be submitted within 60 days of the initial written notice from the government

· Configuration status audits of total configuration, including hardware and firmware.

· Describe methods for developing and establishing the current system baseline and for establishing and identifying its contents. Identify the process for introducing new hardware to the baseline.

· List job titles and qualifications of personnel to perform configuration management.

· Provide a comprehensive program to plan and deliver configuration management services to the Government.

· Describe a method for identifying deficiencies in the configuration management services provided before the level of performance becomes unacceptable. Address the processes to be used for corrective actions.

· Establish and maintain records of all configuration management and corrective actions throughout the term of the contract including reports and logs. These records will be submitted to the CARTS R/M COR on a quarterly basis.

· Develop methods of direct and indirect communications with the Government regarding performance.

3. Security. Identify any special or unique security requirements resulting from the contract.

4. Schedule. A milestone chart graphically depicting the schedule of events associated with the contract. The level of detail will be sufficient to clearly show how the contract activities will be performed.

Submission. The Configuration Management Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 days of Government review; and update 90 days after contract award.

Title: Quality Assurance Plan; DID 6.9

Purpose: Provide the format, content, and intended use for the Quality Assurance Plan generated by the specific task requirement in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content.

1. Organizational Structure. A description of the contractor’s organizational structure and assignment of functions, duties, and responsibilities that will be assigned in support of the contract.

2. Methodology. A comprehensive Quality Assurance Plan for delivering quality services to the Government, for the contract. The Quality Assurance Plan will:

· Detail the contractor’s corporate policy on quality assurance.

· Identify methods for obtaining measurable inspection results.

· Document past performance with quality assurance.

· List job titles and qualifications of personnel to perform quality control.

· Address overall project management and administration.

· Provide a comprehensive program description to plan and deliver quality hardware, software, and services to the Government.

· Describe the contractor’s method for identifying deficiencies in the quality of hardware and services provided before the level of performance becomes unacceptable. Address the processes to be used for corrective actions.

· Establish an inspection system covering all hardware and services required. Specify areas to be inspected on both a scheduled or unscheduled basis. Identify the title of the individuals and the description of duties of individuals to perform the inspections.

· Establish and maintain records of all quality control inspections and corrective actions throughout the term of the contract. These records will be submitted to the COR on a quarterly basis.

· Develop methods of direct and indirect communications with the Government regarding performance.

3. Security. Identify any special or unique security requirements resulting from the contract.

4. Schedule. A milestone chart graphically depicting the schedule of events associated with the delivery of CARTS R/M. The level of detail will be sufficient to clearly show how each task and subtask will be performed.

Submission. The Quality Assurance Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 days of Government review; and update 90 days after contract award.

Title: Quality Assurance Surveillance Plan; DID 6.10

Purpose: Provide the format, content, and intended use for the Quality Assurance Surveillance Plan generated by the specific task requirement in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Overview: Although one QASP will be submitted—it must address both the existing CARTS system (hardware and software to include all current functionality as outlined in the SOO and its attachments) and the new CARTS R/M hardware.

Content. The Quality Assurance Surveillance Plan will propose an effective and systematic surveillance method for services provided in the contract to be used by the Government. The plan will include:

· Work requirements (tasks specified in the Performance Work Statement)

· Scope of performance

· Performance standards tied back to key performance parameters (KPPs) outlined in the Functional and Technical Requirements document

· Acceptable Quality Level

· Primary method of surveillance and frequency

· Evaluation method

· Metrics (positive and/or negative) to manage cost, schedule, and performance

· Identification of key surveillance monitors and documentation of the roles and responsibilities of each (i.e., for CARTS and CARTS R/M, functional representatives, technical representatives, etc.).

Submission. The Quality Assurance Surveillance Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; revisions within 30 days of Government review; update 6 months after contract award; and update 12 months after contract award.

Title: Program Management Review Documentation; DID 6.11

Purpose: Provide the format, content, and intended use for the Program Management Review Documentation generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The Program Management Review Documentation will describe the management methods the contractor will use to ensure meeting all preparation, format, and submittal requirements established by the Government.

1. Agenda and briefing slides. The contractor will conduct monthly Program Management Reviews (PMRs) for the first five years of the contract and quarterly thereafter. One week prior to each meeting, the contractor will submit an agenda and briefing slides addressing the following:

· Technical progress

· Problem areas

· Subcontractor activity

· Risk areas

· Accomplishments

· Schedule status

· Forecast information

2. Minutes. The contractor will prepare PMR minutes and submit to the Government within one week after each meeting. The minutes will include:

· Documenting the program management review

· Presentation materials

· Action items (addressed by the action item deadline and briefed at subsequent PMRs, as appropriate)

· Any other materials designated by the CARTS R/M Program Manager Submission. Program Management Review Documentation will be submitted in accordance with the SOO Section 6.0. Deliverables — monthly for first five years and then quarterly for duration of contract.

Title: Program Management Quarterly Status Report; DID 6.12

Purpose: Provide the format, content, and intended use for the Program Management Quarterly Status Report generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The Program Management Quarterly Status Report will describe the management methods the contractor will use to ensure meeting all preparation, format, and submittal requirements. The report will include:

· Details on key performance metrics

· Accomplishments

· Program changes

· Projected milestones

· Contractor’s overall assessment Submission. The Program Management Quarterly Status Report will be submitted in accordance with the SOO Section 6.0. Deliverables — quarterly for duration of contract.

Title: Maintenance Report; DID 6.13

Purpose: Provide the format, content, and intended use for the Maintenance Report generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The Maintenance Report will describe the methods the contractor will use to ensure meeting all preparation, format, and submittal requirements. The report will include:

· Listing of all calls received

· Names of the DeCA points of contact initiating the calls

· Names of the personnel receiving the calls

· Names of maintenance personnel maintaining the system

· Date and time of calls

· Reported problems

· Location of the problems

· Type of problem (hardware and/or software) and priority/severity level

· Problem equipment identification name and code

· Work order number

· Response time

· Problem resolution time

· Actions taken to resolve the problems

· Approved delays, person granting the delay, and agreed to future arrival time

· At a minimum, maintenance reports must include automated calculations of lanes down, mean down time per component and end item, and mean time between failure per component and end item Submission. The Maintenance Report will be submitted in accordance with the SOO Section 6.0. Deliverables — weekly with a quarterly roll up for duration of contract.

Format. The Maintenance Report will include the Incident Analysis Report. The contractor will use MS Word with a list of tickets in MS Excel for spreadsheets.

Title: Incident Analysis (Help Desk) Report; DID 6.14

Purpose: Provide the format, content, and intended use for the Incident Analysis Report generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The Incident Analysis Report will describe the methods the contractor will use to ensure meeting all preparation, format, and submittal requirements established by the Government. The report will include:

· Incident status (open or closed)

· Site/customer identification name and number

· Incident number

· Priority/severity level of incident

· Problem description

· Repeat discrepancy

· Problem resolution

· Open date and time

· Estimated completion date (if open)

· Closed date and time

· Closure comments Submission. The Incident Analysis Report will be submitted in accordance with the SOO Section 6.0. Deliverables — weekly with a quarterly roll up for duration of contract.

Format. The Incident Analysis Report will use MS Word with a list of tickets in MS Excel for spreadsheets.

Title: Transition Plan; DID 6.15

Purpose: Provide the format, content, and intended use for the Transition Plan generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

1. Organizational Structure. A description of the contractor’s organizational structure and assignment of functions, duties, and responsibilities that will be assigned in support of the transition of the current solution from the incumbent (IBM).

2. Methodology. A Transition Plan for assuming responsibility for ensuring consistent performance of the CARTS solution and supporting POS functionality until the final store is transitioned to the modernized solution. The Transition Plan will:

· Detail the contractor’s approach to assembling the support team and obtaining necessary access.

· Identify methods for transferring knowledge.

· Provide a comprehensive program description to plan and deliver required support for DeCA’s POS system, to include but not limited to: Configuration Management, DeCA’s construction/new store projects, software deployment, monitoring interfaces, Help Desk support and problem resolution.

· Develop methods of direct and indirect communications with the Government regarding transition.

3. Schedule. A milestone chart graphically depicting the schedule of events associated with the transition of responsibilities. The level of detail will be sufficient to clearly show how each task or subtask will be performed.

Submission. The Transition Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; update 30 days after contract award; revisions within 30 days of Government review.

Title: Hardware Plan; DID 6.16

Purpose: Provide the format, content, and intended use for the Hardware Plan generated by the specific task requirements in Section 6.0 Deliverables in the Statement of Objectives (SOO) and its attachments.

Requirements:

Content. The Hardware Plan will describe the components the contractor will use to ensure meeting all POS hardware requirements established by the Government (SPS 2.1). The report will describe the components that comprise the offeror’s solution and should include, but not be limited to model names and numbers and firmware types and versions.

Submission. The Hardware Plan will be submitted in accordance with the SOO Section 6.0. Deliverables — draft with initial proposal; update 1 year after contract award.

Format. The Government anticipates that the Hardware Plan will be in a tabular format and must be presented in a MS format, Word or MS Excel.