EPoS_Attach_14_Group_2_Task_Order_2_Fixed_Software_Sustainment_PWS_20170820.docx

GENERAL DESCRIPTION:

The contractor shall provide the necessary technical and subject matter expertise to accomplish the tasks described within the PWS of the Task Order (TO) on a Firm Fixed Price basis. The work shall be performed in accordance with all sections of this Task Order and the contractor’s proposal for the overall EPoS Indefinite Delivery Indefinite Quantity (IDIQ) effort for Group 2: Fixed Facility Devices.

TECHNICAL PROPOSAL:

In accordance with the solicitation, Factor 1: Technical, Subfactor A: Technical Approach of the Solution, Subfactor B: Management Approach and Capabilities, and Subfactor C: Key Personnel Qualification under Group 2, the contractor shall provide a technical proposal that shall include:

1. A list of assumptions used in your proposal

1. Resumes of Key Personnel

1. Documentation demonstrating the contractor’s understanding of the TO PWS and the contractor’s proposed methodology and technical approach to completing the stated tasks. Additionally, the contractor shall provide a proposed plan (including milestones and timelines) for overall implementation and execution of project.

PRICING:

In accordance with solicitation, the contractor shall provide a firm fixed price proposal for this Task Order utilizing sample pricing sheet for task order provided in the attachment section of the solicitation.

Performance Work Statement (PWS)

Table of Contents

ATTACHMENT 14

Solicitation SP4703-17-R-CB01 Electronic Point of Sale (EPoS) and Supporting Services Group 2 Task Order 2 Fixed Facility Device Interface and Application Software Sustainment PWS

I ii

Background, Objective and Operational Environment Background DLA Energy requires an electronic Point of Sale (EPoS) turn-key solution for capturing military fleet management fuel retail transactions at unattended military service stations, mobile ground fuel transactions and capturing aviation fuel transactions for mobile airfield/flight line operations that meets the current standards for Cybersecurity and Audit Readiness. The solution shall comply with the security control requirements documented in National Institute of Standards and Technology (NIST) Special Publication (SP) 80053r4, “Security and Privacy Controls for Federal Information Systems and Organizations” and NIST 800-82r2, “Guide to Industrial Control Systems (ICS) Security as specified in this PWS.

Turn-key is defined as immediately ready to use upon implementation and designed to fulfill the requirements including required interfaces.

Operational Environment The operational environment consists of sites described by the Government-provided site diagram and site requirements.

Task Order Scope Project Management The contractor shall provide Task Order project management support activities as needed by the Program Manager (PM). Those activities include coordination, update and maintenance of various program deliverables including the Integrated Master Schedule (IMS), Work Breakdown Structure, project status, program charts, briefing charts, work coordination, monthly status reports, project plans, and general contract oversight.

Fixed Facility Interface and Device Application Software Sustainment EPoS environments must be operational 24 hours a day, 7 days a week.

The contractor shall sustain the EPoS fixed facility interface and device application software and its functionality. The contractor shall ensure that the EPoS fixed facility interface and device application software is appropriately sized and tuned for the most efficient operations/performance possible. The contractor shall ensure all detected problems are promptly reported to the EPoS PMO.

The contractor shall provide the processes, procedures, people, documentation, operations support, deployment, security, configuration management and training materials required to sustain the fixed facility interface and device application software. The contractor shall correct faults, improve performance or other attributes, and adapt the applications to a changing organizational and technical environment. The contractor shall support the resolution of problems discovered through the testing or operation of the EPoS fixed facility interface and device application software.

Defects identified in any development Task Order will be corrected prior to production deployment unless otherwise agreed to by the EPoS PM through the COR.

Documentation The contractor shall develop and provide end user training documentation as updated for fixed facility device interface and application software changes and releases.

Tasks Tsk 1: Project Management The contractor shall provide Task Order project management support activities as needed by the Program Manager (PM). Those activities include coordination, update and maintenance of program deliverables, project status, project plans, and general Task Order oversight.

Project Management Plan The contractor shall prepare a Project Management Plan (PMP) (Contract Data Requirements List ((CDRL) S001) describing the technical approach, organizational resources, and management controls to be employed to meet the cost, performance, and schedule requirements for the proposed effort. The contractor shall provide the planning, supervision, coordination and controls necessary to accomplish all work contained in this PWS. The contractor shall document the approach and plan that defines the activities, tools, and techniques to ensure high-quality products that are defect-free, that meet PWS requirements and that are delivered in accordance with the approved schedule.

The plan shall include a description of the organization structure and assigned responsibilities, including the contractor staff that will deliver and implement this Task Order. The organization structure shall include the identification of key personnel. The contractor shall provide an organization chart and describe other corporate organizations that will support the team.

The contractor shall provide an explanation of how, within the scope of the Task Order, the contractor will perform technical management and will manage personnel and physical resources.

The plan shall include a work breakdown structure (WBS) (CDRL S002) that shows tasks required to complete the work and the dependencies of each task. The WBS shall be detailed to the level of effort necessary to support the accomplishment of work to be performed under this PWS. The contractor shall deliver the PMP to the Contracting Officer’s Representative (COR) in a contractor proposed, Government approved format within 30 days of contract award.

Integrated Master Schedule The Integrated Master Schedule (IMS) is a time-based schedule containing the networked, detailed tasks necessary to ensure successful project/ Task Order execution. The IMS is traceable to the PMP, the WBS, and this PWS. The IMS is used to verify attainability of Task Order objectives, to evaluate progress toward meeting project objectives, and to integrate the project schedule activities with all related components.

The contractor shall produce and maintain an IMS (CDRL S003) that shows the activities required for the completion of tasks and deliverables for this Task Order. The contractor shall deliver to the COR a draft and baselined IMS within 30 and 75 calendar days after Task Order award, respectively.

The contractor shall deliver a Project IMS, with updated actuals, to the COR a minimum of two business days prior to each Monthly Performance and Progress Report (See section 3.1.5 of this Task Order). The IMS shall be delivered in a contractor proposed, Government approved format.

Risk Register The contractor shall apply a risk management approach to develop and maintain a risk register that documents and tracks contractor and Government identified project risks. For each risk, the register shall include at least a description of the risk, a rating (high, moderate, low), a description of the impact should the risk occur and a mitigation strategy. The contractor shall deliver a Risk Register (CDRL S004) resulting from the contractor’s risk management process to the COR within 30 calendar days of the issuance of the Task Order and provide updates as changes are made, at least monthly. The Risk Register shall be provided in a contractor proposed, Government approved format.

Monthly Performance and Progress Report The contractor shall monitor activities and deliverables under this Task Order and provide a Monthly Performance and Progress Report (MPPR) (CDRL S005) that describes project progress, costs, issues, problems and their status. The MPPR shall be the contractor’s method of reporting progress against the PMP. The period covered by the MPPR shall include the previous calendar month’s activities; any issues, actions or other MPPR reported information not satisfied or closed in previous reporting periods; and any required interfaces, meetings or other commitments. If applicable, travel costs shall be broken down by destination, duration, purpose, and costs for both monthly and cumulative to date. MPPRs for the previous month shall be delivered to the COR by the fifth day of the following month.

The MPPR shall include but not be limited to the following information:

· Summary of Activities

· Activities and Progress (Integrated Master Schedule)

· Software Engineering Metrics and Measures

· Costs

· Deliverables

· Significant Meetings

· Significant Issues

· Significant Plans

· Travel

· Action Item Status

· Risks to the contractor based on Government pending actions

· Risks to EPoS application performance based on contractor issues Briefing, Meeting, Conference Call Presentation Material and Minutes The contractor shall prepare briefing materials and represent the EPoS program at briefings, meetings and conference calls with organizations of interest, stakeholders, external and internal systems. This representation shall be at a level that functionally and technically represents EPoS mission and capabilities.

The COR or an authorized Government representative will be present at all briefings, meetings and conference calls. Read ahead and presentation materials (CDRL S006) shall be delivered to the COR five days prior to any meetings, briefings or conference calls, as required. If meetings, briefings or conference calls are scheduled less than five days in advance, the contractor shall provide read ahead and presentation material as soon as practicable.

The contractor shall document meeting notes including, but not limited to, any action items, status of action items, and summary of discussions. The contractor shall deliver these meeting notes (CDRL S007) to the COR no later than five days after the meeting. Approved meeting notes will be disseminated by the COR.

Kick-off Meeting The contractor shall schedule a kick-off meeting with the PMO, COR, and stakeholders within two weeks of award or as agreed on between the Government and contractor, to introduce the Government team to the contractor’s overall operating plans and approach to this work. The contractor shall present and deliver the Kick-off Meeting Briefing Presentation Material (CDRL S006) and be prepared to discuss the content of the Program Management Plan, to include the staffing plan, schedule and proposed metrics. The contractor shall produce and distribute Kick-off Meeting Minutes (CDRL S007) identifying all the discussion points, agreements and action items within five days following the meeting.

Weekly Production Status Contractor personnel shall be prepared to actively participate in support calls by having status updates ready and also be available for any questions from the customer. As requested by the COR, the contractor shall provide a Weekly Status Report (CDRL S008) on the first Monday of the following week that describes issues, resolutions and timeframes.

Task 2: Fixed Facility Device Interface and Application Software Sustainment The contractor shall provide the necessary software engineering, technical, programming, documentation and analytical services, as directed by this Task Order required to sustain the fixed facility interface and device application software. The contractor shall correct faults, improve performance or other attributes, and adapt the applications to a changing organizational and technical environment. The contractor shall support the resolution of problems discovered through the testing or operation of the EPoS fixed facility interface and device application software.

Sustainment Plan The contractor shall develop and implement a Sustainment Plan for the installed solution by site to ensure that the installed systems and equipment meet the requirements. The Sustainment Plan shall include the periodic maintenance, repair, replacement, and overhaul of existing systems, hardware, and software inclusive of Information Assurance Vulnerability Alerts (IAVA Patching).

The Sustainment Plan shall include the contractor’s approach to:

· Position qualified personnel, test equipment, etc. needed to quickly diagnose and make repairs

· Plan, perform, and document system confidence tests, periodic inspections, and preventive maintenance

· Identify critical system operations and implement strategies to prevent potential failures or administrative down-time from creating a critical system outage

· Analyze fault histories and fault trends to proactively predict and mitigate repetitive issues

The contractor shall develop and deliver to the COR a Sustainment Plan (CDRL S009) within 30 days after Task Order award.

Configuration Management The contractor shall conduct Configuration Management (CM) for all Fixed Facility Interface and Device Application Software Sustainment incidents, and requests for change using the Government’s in-place CM tracking system. The contractor shall update and track all development and sustainment efforts by submission, review, level of effort (LOE), funding, approval, delivery, testing and enhancements to production.

The contractor shall create, maintain, and post technical documentation and revisions for the application, as approved by the COR. The contractor shall accept input from the help desk for base level user issues / problems and update technical documentation as required.

The contractor shall provide the necessary controls and data gathering capabilities to assemble, verify, and validate requirements for various ongoing interface development efforts. The contractor shall provide the direct quality assurance support. The contractor shall also assist with the onsite tier 3 support documentation and assistance with performance of Beta testing as directed by the Task Order. The contractor shall provide Quality Assurance Reports to the COR for each system and software change request, as they are required.

The contractor shall develop and deliver to the COR a Configuration Management Plan (CMP) (CDRL S010) within 30 days after Task Order award.

Tier 1 Help Desk Support Tier 1 is the initial entry point for all customer support. This is where all initial customer information and problem definition data is collected, acted on, or forwarded to higher support echelons. Tier 1 provides limited technical and functional support of all applications, hardware, and software. Tier 1 support provides initial triage and proper routing for all problems.

The DLA Enterprise Help Desk (EHD) will provide tier 1 Help Desk Support. Instructions on EHD access and use will be provided at contract award.

Tier 2 Help Desk Support Tier 2 provides advanced technical and functional support of all EPoS owned applications, hardware, and software that are beyond the scope of the tier 1 analysts. Tier 2 analysts provide advanced and complex technical support for all EPoS applications.

The contractor shall provide tier 2 Help Desk support through technical assistance to the Government in resolving any problems associated with EPoS. These problems may include but are not limited to hardware or software failure or errors that hinder operations.

The contractor shall review and analyze production trouble tickets and propose fixes.

The contractor shall identify methods and mechanisms to actively assist system users in performing their tasks, minimizing the need to communicate with the help desk for items that are addressed by online system documentation or other methods.

The contractor shall provide issues, resolutions and timeframes related to tier 2 Help Desk support in the Weekly Status Report (CDRL S008).

Tier 3 Help Desk Support Tier 3 is support beyond the scope of the tier 2 analysts and includes functional application support and making recommendations for changes to the EPoS applications software or business processes.

The contractor shall provide tier 3 Help Desk support on tickets assigned to them and report on work done on those tickets to the EHD. Tier 3 is the support beyond the scope of tier 2 and includes functional application support and making recommendations for changes to the EPoS fixed facility interface and device application software or business processes. It includes developers, subject matter experts, other representatives that are appropriate to ensure tickets for the EPoS software, both Commercial off the Shelf (COTS) and developed software, are resolved within the EPoS configuration management process.

The contractor shall support the resolution of problems discovered through the testing or operation of the EPoS fixed facility interface and device application software.

The contractor shall provide issues, resolutions and timeframes related to tier 3 Help Desk support in the Weekly Status Report (CDRL S008).

On Site Support If a site is determined to be in a down condition, the contractor will immediately notify the EPoS PMO and the Government will determine the appropriate response. If the Government directs the contractor to travel to the site to affect on site repairs, the contractor shall dispatch personnel to meet the required repair time as defined below. The required repair time will not begin until the Government directs the contractor to proceed to the site. The contractor is authorized to travel to a site at the direction of the COR.

CONUS - The contractor required repair time for a down site is three (3) calendar days after notification. Notification begins at 0800 hours on the following normal business day on which a call is received. If the notification is received on a Saturday, a Sunday or a federal holiday, the repair time starts at 0800 hours on the first normal business day thereafter. However, if the third calendar day falls on a Saturday, Sunday, or a federal holiday, the contractor shall report on the first normal business day thereafter.

OCONUS - The contractor shall be permitted a seven (7) day response time after notification for all non-CONUS and special sites. Start time for notification is the same as CONUS sites. If on-site support by contractor personnel is required, the contractor repair time will not start until such time that appropriate clearances have been obtained with the assistance of EPoS PMO.

OTHER - Other maintenance issues that do not render the site down will be managed in the same expeditious manner, however, the 3 and 7-day period will not apply.

Problem Resolution The contractor shall work as an integrated team with Government personnel and other Government contractors supporting sustainment of the solution. The contractor shall assist the Government with continued interface support between the contractor’s application and upstream energy applications, currently FuelManager® Defense (FMD). The contractor shall use the system change process in use at contract award, currently Eagle Incident and Request for Change process to complete all changes to the system. Instructions on access to and use of the DLA change process will be provided at contract award.

The contractor shall perform all necessary research, analysis, and troubleshooting of work orders generated by a help desk ticket, to address problem issues with configuration management, cybersecurity, DOD Network, the contractor’s application and associated interfaces. The contractor shall coordinate and work with Military Services Local Area Network (LAN) Administrators and Information Operations technical staff at Fort Belvoir, Area Support Group (ASG) senior analysts, Service Control Points (SCPs) and other support activities involved with connectivity, configuration, and access to resolve problems. The contractor shall document the description of the problem and its resolution for the user and help desk in accordance with the ASG Standard Operating Procedure (SOP).

The contractor shall provide issues, resolutions and timeframes related to problem resolution in the Weekly Status Report (CDRL S008).

Conditions reported to the EPoS PMO for problem resolution shall be assigned a priority level 1 through 4 based on the following criteria.

capability, or violate security policy and procedures, for example, buyer is unable to obtain account ledger information or a seller is unable to obtain inventory ledger information in order to process base-level transactions.

capability; technical, cost, or schedule risks to the project; or the life-cycle support of the system. No work-around solution is known.

operational or mission-essential capability, and is non-value-added practice for development or support personnel, but does not prevent them from accomplishing their responsibilities.

Problem resolution standard telephone response time will be in accordance with the table below. Response and resolution times are measured from the initial ticket assignment until the ticket is resolved.

System Response and Resolution Time Requirements

Post Production Support The contractor shall provide post production support. The contractor shall provide support to users, business process analysts, others as designated by the Government until the capability is within acceptable process and system performance thresholds; support the complete acceptance of the capability as it transitions to normal operations, support and sustainment. Within the first 30 days of a production release, any confirmed production problem associated to the contractor developed and tested components shall be resolved as part of post-production support even if a service ticket is created and assigned to the contractor.

Security Incident Reporting In addition to adhering to the reporting requirements as outlined in DFARS clause 252.204-7012, when the contractor discovers a cyber-incident that affects covered defense information or the contractor’s ability to meet the requirements of the contract, the contractor shall:

1. Provide the results of any reviews conducted for evidence of compromise of covered defense information or that affect the contractor’s ability to provide operationally critical support; including, but not limited to, identifying compromised computers, servers, specific data, and user accounts.

1. Rapidly report the incident(s) to the applicable Contracting Officer and the DLA Cyber Resilience Program Office (the point of contact information will be provided at the time of contract award).

1. Preserve and protect relevant artifacts (e.g., configurations, audit logs, packets, etc.) for at least 90 days from the submission of the cyber-incident report so that if it is deemed necessary, DLA’s Cyber Resilience Program Office or Cyber Emergency Response Team may request access to the artifacts.

1. Provide, as requested by the Contracting Officer on behalf of the DLA Cyber Emergency Response Team, access to additional information (to include damage assessment information gathered, etc.) or equipment that is necessary to conduct a forensic analysis related to an identified incident.

The contractor shall provide issues, resolutions and timeframes related to security incident reporting in the Weekly Status Report (CDRL S008).

Change or Release Requirement For any change or release, the contractor shall provide the following to the COR within 10 days of the scheduled change or release implementation:

· The Updated Software (CDRL S011)

· Software Version Description (SVD) – defining all the changes included in the software update (CDRL S012)

· Software Installation Plan (SIP) – defining how the software is to be installed at the Government site (CDRL S013)

· Developmental Plan and Results – results of contractor testing conducted prior to delivery (template to be agreed upon at time of Task Order award) (CDRL S014) Task 3: Documentation The contractor shall develop and provide end user training Documentation (CDRL S015) as updated for fixed facility device interface and application software changes and releases.

Key Personnel Note: All Labor Categories will require that contractor resources possess an Information Technology (IT) Level I Security Clearance.

Program Manager The Program Manager shall manage all day-to-day operations including administrative functions, assessing risks and identifying unstated assumptions, and resolving interpersonal conflicts in support of making the program successful.

Duties and Responsibilities:

The Program Manager acts as manager and overall point of contact for all work on this contract and:

· Directs staff and reviews work products for completeness and adherence to customer requirements

· Provides communication to management to review project plans, status reports, and deliverables

· Develops overall project milestones and monitors the execution of the project against planned time lines

· Directs and reviews program plans, status reports, and deliverables with program director and project teams

· Provides technical and functional management to one or more project teams for specific projects or sub-tasks Education and Experience:

The Program Manager must possess minimum of Bachelor’s Degree from an accredited college or university in related field. Preferred: Technical degree or direct experience in engineering or systems development and Master’s Degree. Requires minimum of 10 years of experience as a Program/Project Manager or Team Lead with increasing responsibility, preferably with experience managing fuel industry related projects.

The Program Manager shall have a technical background as well as a management background. The Program Manager has experience with the execution and management of information technology (IT) programs. This includes direct experience in leading and executing IT solutions in the private or public sector. Experience includes:

· Program management of technically and functionally diverse and complex IT programs.

· Implementation of detailed management techniques such as Critical Path Method (CPM) and Earned Value Management.

· Complex product configuration management and control.

· Business case development.

· IT solution architectural analysis and design.

· Detailed migration planning and trade-off analysis.

· System data exchange design, development, and implementation.

· Hosted application support/management in environments without direct contractor control Cybersecurity Engineer The Cybersecurity Engineer shall manage all day-to-day cybersecurity operations including administrative functions, assessing risks and identifying unstated assumptions, and resolving interpersonal conflicts for the solution in support of making the program successful.

Duties and Responsibilities:

The Cybersecurity Engineer ensures the cybersecurity of the system is in accordance with Federal and DOD requirements and:

· Determines applicable enterprise cyber and security standards

· Develops and implements defined cyber/security standards and procedures

· Coordinates, develops, and evaluates security programs for an organization

· Recommends cyber/security solutions to support customer requirements

· Identifies, reports, and resolves security violations

· Establishes and satisfies cyber and security requirements based upon the analysis of user, policy, regulatory, and resource demands

· Supports customers at the highest levels in the development and implementation of doctrine and policies

· Applies know-how to Government and commercial common user systems, as well as to dedicated special purpose systems requiring specialized security features and procedures

· Performs analysis, design, and development of security features for system architectures

· Analyzes and defines security requirements for computer systems which may include mainframes, workstations, and personal computers

· Designs, develops, engineers, and implements solutions that meet security requirements

· Provides integration and implementation of the computer system security solution

· Analyzes general cyber-related technical problems and provides basic engineering and technical support in solving these problems

· Performs vulnerability/risk analyses of computer systems and applications during all phases of the system development life cycle

· Ensures that all information systems are functional and secure Education and Experience:

The Cybersecurity Engineer must possess minimum of Bachelor’s Degree from an accredited college or university in related field. Preferred: Degree in computer science, computer engineering, advanced analytics, applied mathematics, or physics. Requires minimum of 8 years of relevant experience.

The Cybersecurity Engineer shall have demonstrated an understanding of the cybersecurity requirements and system engineering processes, is aware of business objectives, and shall be proficient in advanced internal/external network routing and switching technologies. Experience includes:

· CISSP at a minimum with a preference for CISSP- IA Workforce System Architect or Engineer (IASAE)

· A clear understanding and relevant experience of at least three years with the design, maintenance and operation of highly complex and high secure communications network environments

· An understanding of embedded systems

· Multi-discipline experience with Firewall/IPS, Antivirus, host-based protection, security incident (i.e. Contingency/COOP, Investigative forensic) event management, virtual shared computing environments and network/security management

· A solid understanding of communication protocols, network technologies and the ISO Open Systems Interconnection telecommunications model, solid troubleshooting skills and methodologies

· Knowledge of Defense Information and Accreditation Risk Management Framework (RMF) and process for system and application controls

· Knowledge of DOD/DLA security policies and CERT compliance

· DOD 8570.01 Information Assurance Manager level III Certification Senior Applications Programmer The Senior Applications Programmer is responsible for translating technical software and hardware specifications into software and hardware design and providing IT technical guidance to site-specific installers. The Senior Applications Programmer shall provide project leadership as the principal designer under this PWS.

Duties and Responsibilities:

· Collaborates with business analysts, architects, others to plan, design, develop, test, and maintain applications

· Collects and documents user requirements

· Prepares reports, manuals and other documentation on the status, operation and maintenance of application software

· Designs, develops, and unit tests applications in accordance with established standards

· Participates in peer-reviews of solution designs and related code

· Packages and supports deployment of releases

· Develops, refines, and tunes integrations and interfaces

· Configures services for performance, security, and error handling

· Analyzes and resolves technical and application problems

· Assesses opportunities for application and process improvement

· Assists in determining and enforcing development standards and best practices

· Performs application related Security Technical Implementation Guides (STIGs) and vulnerability reporting Education and Experience:

The Senior Applications Programmer must possess minimum of Bachelor’s Degree from an accredited college or university in related field. Requires minimum of 5 years of combined experience in hardware and software configuration for the selected solution. Two years or more experience in international implementations; this can be in conjunction with the five years of experience requested above. Experience includes:

· Certification in applicable experience areas

· Proficiency in analyzing user-defined functional, technical system requirements as well as writing design and technical specifications

· Proficiency in drafting integration test plans and integration test cases as well as executing and documenting integration testing activities

· Proficiency in complex testing and debugging of hardware and software solution

· Knowledge of Section 508 compliance Database Administrator The Database Administrator (DBA) manages all database administrator functions to include, but not limited to, database design, recoverability, integrity, security, availability, performance and development and testing support.

Duties and Responsibilities:

· Provides all activities related to the administration of computerized databases

· Projects long-range requirements for database administration and design in conjunction with others working EPoS applications

· Designs, creates, and maintains databases in required environments

· Conducts quality control and auditing of databases in required environments to ensure accurate and appropriate use of data

· Advises users on access to various databases

· Designs, implements, and maintains complex databases with respect to access methods, access time, device allocation, validation checks, organization, protection and security, documentation, and statistical methods

· Applies knowledge and experience with database technologies, development methodologies, and front-end/back-end programming languages

· Performs database programming and supports systems design

· Includes maintenance of database dictionaries, overall monitoring of standards and procedures, file design and storage, and integration of systems through database design

· Performs database related Security Technical Implementation Guides (STIGs) and Vulnerability Management System (VMS) reporting Education and Experience:

The Database Administrator must possess minimum of Bachelor’s Degree from an accredited college or university in related field. Requires minimum of 5 years of experience in projects using the solution database management system. Experience includes:

· DOD 8570.01 IAM level III Certification

· Demonstrated experience with:

· Database designing development and management to include, but not limited to: Web Services/XML, materialized views, performance tuning, and database modeling

· Data engineering or management of data warehouses with multiple environments with multiple sources of inbound data

· Knowledge of:

· Creating, deploying, and executing database scripts and stored procedures as well as in creating, maintaining and optimizing application database table, triggers, materialized views, configurations and interfaces

· Executing data migration tasks to include ETL tasks

· Risk Management Framework (RMF) processes for application controls

· DOD/DLA security policies and CERT compliance Systems Engineer The Systems Engineer provides support of the design, execution, and oversight of IT projects.

Duties and Responsibilities:

· Supports all program and project planning and milestone development.

· Supports business case analysis and identification of alternative solutions and resulting business impacts.

Education and Experience:

The Systems Engineer must possess minimum of Bachelor’s Degree from an accredited college or university in related field. Requires minimum of 6 years of experience in a network management environment.

The Systems Engineer has experience with the design, execution, and oversight of IT projects. This includes direct experience in the design and development of integrated software and hardware solutions in the private or public sector. Experience includes:

· Security+ or equivalent IAT/IAM/IASAE Level II

· Detailed functional analysis and gap/fit analysis of software solution packages

· Software solution package selection and business case development

· Software and system developmental and acceptance testing

· Legacy system data exchange design, development, and implementation Deliverables Deliverable Requirements The COR will review all deliverables to ensure accuracy, functionality, completeness, professional quality, and overall compliance with contract requirements. The contractor shall ensure the accuracy and completeness of all deliverables. Unless otherwise noted, the contractor shall only deliver final completed products to the Government for acceptance. The Government will consider errors, misleading statements, incomplete or irrelevant information, excessive rhetoric, or repetition as deficiencies and the contractor shall make corrections.

Unless otherwise indicated in a deliverable description, the Government will have ten business days to review deliverables. If the Government has comments, the contractor shall have five business days to make corrections to the deliverable and resubmit the deliverable to the Government. In the event that there are exceptional circumstances impacting the delivery of a Contract Deliverables Requirements List (CDRL) item, the COR may grant up to a five business day extension on the delivery of any CDRL item. To be granted an extension the contractor shall submit a written justification to the COR and Contracting Officer no less than 2 business days in advance of the CDRL item due date.

All completed deliverables shall be delivered to the COR or Government individual identified for this effort. Except as specified in this PWS, the contractor shall use best commercial practices for formatting all deliverables. Electronic copies of all deliverables shall be sent to the COR via email in Microsoft Office compatible or Portable Document Format (PDF) formats. If deliverable exceeds email size limitations (10 MB), the deliverable shall be sent via Compact Disk (CD) or other media as appropriate for the size of the deliverable and approved by the COR.

Deliverable Schedule Unless otherwise specified all delivery dates are in calendar days.

Table 5.1: Deliverable Schedule

MASTER DELIVERABLES SCHEDULE

Baselined 75 days after Task Order award

Performance Requirements Performance Measurements The performance measurements to be used to assess the contractor’s performance under this contract will determine whether the contractor is performing at acceptable levels to allow for a 100% payment of monthly invoices.

The Government will make objective and subjective assessments of the contractor's performance to determine whether contractor performance is acceptable. The contractor shall perform all functions in a professional manner and prepare accurate and timely documentation. Progress will be tracked based on the milestone event when the contractor receives a specific tasking. The number of completed actions will be balanced against the quality of this output.

The performance measurements under this contract shall be based on timeliness and quality of the work and deliverables provided by the contractor under the contract. These measurements are defined as:

· Timeliness – The completion of taskings or the submission of deliverables within the schedule set forth by the Government during the performance of the contract

· Quality – The quality of work completed under the resulting tasking’s will be measured based on the Government’s determination of the validity, accuracy, clarity and usefulness of a deliverable or if the work performance met the expected outcomes as was communicated to the contractor by the Government Performance Standards The following performance standards will be used to support the requirements in this Task Order and that will be used in evaluating performance on a monthly basis and in determining the amount of the payment owed to the contractor.

Performance standards and ratings are designed to determine if performance exceeds, meets, or does not meet a given metric and acceptable quality level. The performance will be rated each month by the COR. These findings will be the basis for the amount paid for that month Note: The application of these performance ratings or failure of the Government to apply these performance ratings does not waive any of the Government’s rights to damages under this contract. The following overall ratings shall be used.

Performance Standards

Good

Performance meets or exceeds contract requirements in terms of timeliness and quality. The COR recommends and the Contracting Officer will make a determination to pay the contractor 100% of the invoice amount.

Poor

Performance narrowly meets contract requirements by at least one of the following: bordering on unacceptability in terms of or quality of performance, bordering on unacceptability in terms of timeliness, or potentially having an adverse impact on the mission of the Agency. The COR recommends and the Contracting Officer will make a determination to pay the contractor 80% of the invoice amount.

The ratings, as described in the table above, will be based on the performance of the contractor on the timeliness and quality of the services provided using the rating scale for each criterion as shown below.

Timeliness

Quality

Unacceptable Quality of performance has been at a less than acceptable level. Possible issues include, but are not limited to: low quality documents requiring multiple reviews and rewrites, significant or serious complaints submitted by the customers, documents that did not comply with acquisition or policy regulations or one or more cure notices have been issued by the Contracting Officer.

Quality Assurance Surveillance Plan In fulfillment of this effort, the contractor shall provide the deliverables identified in this Task Order. All deliverables shall be submitted to the COR and the DLA Contract Support Office-Richmond (CSO-R) CO where stated in the section 5.0 Deliverables of this Task Order. The Government will have a maximum of five working days from the day the draft deliverable is received to review the document, and provide comments back to the contractor either approve or disapprove the deliverable. The contractor shall have a maximum of five working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government.