1 EPoS Attach 1 Instructions to Offerors 20171207 CC.DOCX

ATTACHMENT 1

Solicitation SP4703-17-R-CB01 Electronic Point of Sale (EPoS) and Supporting Services E-2. Instructions, Conditions, Notices to Offerors

ATTACHMENT 1

Solicitation SP4703-17-R-CB01 Electronic Point of Sale (EPoS) and Supporting Services E-2. Instructions, Conditions, Notices to Offerors general information

Offerors may submit an offer on one, two, or all three of the following groups: Group 1: Active Directory Services; Group 2: Fixed Facility Devices; Group 3: Mobile Devices. Offers must address all performance requirements and evaluation factors/subfactors of each group for which submitted. When quoting two or three groups, submission of an offer cannot be contingent upon receiving award of more than one group. Refer to paragraph 2.6.3 for further details on Group / Volume Structure submission.

The Offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet or exceed the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements and associated risks, the Offeror is able, willing, and competent to devote the resources necessary to meet the requirements, and has valid and practical solutions for all requirements and potential risk areas. The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors and or subfactors identified in this solicitation. The Offeror is advised that the Government may incorporate into the final contract any portions of the Offeror’s proposal deemed beneficial to the Government. With the exception of the Volume III Price, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the cost/price proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in a rating of unacceptable.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or subfactor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Offeror is expected to comply with all requirements of the solicitation. The Government advises the Offeror that taking exception or deviating from any term or condition of the solicitation may make an offer unacceptable, and the proposal unawardable, unless the solicitation expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the solicitation that is not expressly authorized by the solicitation to be a deficiency.

QUESTIONS:

Offerors may submit questions requesting clarification of solicitation requirements by emailing the Contract Specialist at Charlotte.Bumgarner@dla.mil and the Contracting Officer at Emma.Pfeiffer@dla.mil.

It is requested that all questions be received within 7 business days from the date this solicitation is issued. NO PHONE CALLS WILL BE ACCEPTED. Responses to the questions will be posted to Federal Business Opportunities website (fedbizopps.gov) 7 days prior to solicitation close date.

Recommend list of questions to be on MS Excel spreadsheet including document name, page number, paragraph or section number, context, and question or comment.

SAMPLE:

proposal Submission The submission date for all volumes shall be no later than the date and time specified in the solicitation.

Packaging and Marking The Offeror shall package the proposals in cartons or equivalent packaging containers in the most efficient manner possible and clearly mark all packages with the solicitation number and appropriate volume number.

Late Submissions Proposals submitted after the closing date and time specified for receipt of offers are “late” and will not be considered for award.

The Government will process late submissions of proposals in accordance with FAR 52.215-1. If either the hard copy or electronic copy is received late and is not eligible for consideration in accordance with FAR 52.215-1 and Alternate I, then the Government will reject that proposal without evaluation. If a discrepancy exists between the hard copy of the proposal and the electronic/emailed copy, the hard copy will take precedence.

Proposal Submission Address Offeror shall not submit proposals by facsimile. Offeror shall submit hard copy proposals via United States Postal Service or through a commercial carrier using the address provided below:

DLA Contracting Services Office at Columbus ATTN: Mr. Adam Bourassa 3990 E. Broad Street DSCC Building 20 Columbus, OH 43213

Hand carried proposals may be delivered to the address above, attention: Mr. Adam Bourassa (614-692-7120).

In addition, Offeror shall submit electronic copies of the proposal and must be emailed to Adam Bourassa@dla.mil by no later than solicitation close date. Refer to Section 2.6.4.3 Volume Structure for further details.

CAUTION NOTICE – EMAIL DELAYS

Submission of quotations/proposals via electronic mail (email) is authorized. However, the Defense Information Systems Agency (DISA) has informed all DoD Activities that all email traffic from Non-DoD sources is experiencing delays upon entry to the Enterprise Email Security Gateway (EEMSG). Therefore, it should be anticipated that any proposal submitted via email in response to this solicitation will experience some level of delay. All potential offerors are hereby cautioned that any proposal, modification, or revision that is received at the designated Government office AFTER the exact time specified for receipt of proposals is “late” and will not be considered. For purposes of this solicitation only, any proposal, modification, or revision that is submitted via email to the designated Government office AND received by DISA/EEMSG no later than the time specified by this solicitation will be considered to have been timely received at the designated Government office.

Classified Data All proposals must be UNCLASSIFIED.

Document Requirement All volumes of the proposal shall be delivered to the address provided prior to the closing date/time stated in this solicitation. There shall be no reference to pricing in the Non-Price proposal or in the cover letter or executive summary.

It is requested that your company mark each page of its proposal with the legend “Source Selection Information – See FAR 2.101 and 3.104.” This includes the cover page and EVERY page that may contain source selection information. Note that you have an independent requirement to mark anything you deem to be bid or proposal information, protected proprietary information, or other information you wish to be protected from disclosure in order to ensure that the information is protected.

Proposal Content and Volumes Cover Page:

Each volume shall contain the following items in addition to the non-price and price proposal data required by the solicitation.

Title of the proposal Proposal Group Number and Title Proposal Volume Volume No.

Name and address of Offeror Name and phone number of a principal point of contact

CAGE / DUNS

Note: The Cover Page and Table of Contents are not included in page counts with respect to page limitations.

Cover Letter and Executive Summary The cover letter should be on company letterhead and must contain a statement committing the Offeror to the proposal and stating its validity for a period of at least 180 days. This letter should also include the name, title, phone number, and e-mail address for the persons authorized to negotiate with the Government in connection with the solicitation. The letter must be signed by a responsible officer or partner/principal of the Offeror who is authorized to bind the firm contractually. The letter must also contain a statement that the proposal meets the specifications of each subsection of the solicitation.

An Executive Summary of the Offeror’s entire proposal is required. This summary will not be evaluated but will be used to gain an understanding of the overall proposal contents. It should identify and highlight significant features of the proposal and include the salient points contained in the various volumes and chapters. The Executive Summary shall not include any price-related information.

The following format should be followed in developing the summary:

1. General Information (see Note 1)

2. An overview of Technical Capability

3. Solicitation Qualifications/Deviations (see Note 2)

(Note 1): The General Information section of the Executive summary should include the following information:

0. Company name and address,

0. Company Taxpayer Identification Number (TIN),

0. Dun and Bradstreet number

0. CAGE code

0. The name, phone number, and e-mail address for the authorized company negotiator relative to the proposal.

(Note 2): Solicitation exceptions are proposed deviations from the requirements contained in the Request for Proposal and resultant contract terms and conditions. Qualifications where an Offeror states it will not comply with one or more of these requirements may cause proposals to be considered unacceptable. Therefore, firms must address such qualifications and provide a detailed description of any form of exceptions, deviations or waivers, and indicate the firm’s difficulty with the applicable requirement in addition to the firm’s proposed approach.

Solicitation Amendments (if applicable) If any amendments are issued to the solicitation, proposal should include an acknowledgment of the amendments. This information should be included as an additional chapter. Refer to Volume Structure section.

Proposal Groups / Evaluation Factors / Volume Structure

2.6.4.1 Proposal Groups:

Offeror may submit a proposal for one, two, or all three of the groups. If the Offeror is submitting a proposal for more than one group, you must submit a separate proposal for each group and submission of an offer cannot be contingent upon receiving award of more than one group. The three groups are listed below:

Group 1: Active Directory Services Group 2: Fixed Facility Devices Group 3: Mobile Devices

2.6.4.2 Evaluation Factors:

Evaluation factors and subfactors are listed as follows (note that not all factors are applicable to all groups):

Group 1: Active Directory Services

Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Subfactor C: Key Personnel Qualification Factor 4: Past Performance Factor 5: Small Business Participation Factor 6: Price

Group 2: Fixed Facility Devices

Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Subfactor C: Key Personnel Qualification Factor 2: Solution Demonstration Factor 3: Cybersecurity Demonstration Factor 4: Past Performance Factor 5: Small Business Participation Factor 6: Price

Group: 3 Mobile Devices

Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Factor 2: Solution Demonstration Factor 3: Cybersecurity Demonstration Factor 4: Past Performance Factor 5: Small Business Participation Factor 6: Price

2.6.4.3 Volume Structure:

Proposals submitted shall be contained in separate volumes with tabs separating chapters in the required number of copies. Page limitations for each volume, if any, are also specified in the table below. Title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation. Offerors are strongly encouraged to use tabs and dividers within volumes in order to facilitate ease of review. If you do not follow the volume structure indicated below, your proposal may not be evaluated or further considered for award.

List of volumes and factors for each group are as follows:

Group 1: Active Directory Services

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Vol I Non-Price Proposal Refer to Section 3 Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Subfactor C: Key Personnel Qualifications

(see Note 3)

PDF

1 Original, 12 copies plus emailed copy

Vol II Non-Price Proposal Details on Section 3.0 Factor 4: Past Performance Factor 5: Small Business Participation

1 Original, 3 copies plus emailed copy

Vol III Price Proposal Details on Section 3.0

1 Original, 1 copy plus emailed copy

Group 2: Fixed Facility Devices

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Vol I Non-Price Proposal Details on Section 3.0 Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Subfactor C: Key Personnel Qualifications Factor 2: Solution Demonstration Factor 3: Cybersecurity Demonstration (see Note 3)

PDF

1 Original, 12 copies plus emailed copy

Vol II Non-Price Proposal Details on Section 3.0 Factor 4: Past Performance Factor 5: Small Business Participation

1 Original, 3 copies plus emailed copy

Vol III Price Proposal Details on Section 3.0

1 Original, 1 copy plus emailed copy

Group 3: Mobile Devices

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Introduction to Vol I

1 Original, 12 copies plus emailed copy

Vol I Non-Price Proposal Details on Section 3.0 Factor 1: Technical Subfactor A: Technical Approach of the Solution Subfactor B: Management Approach and Capabilities Factor 2: Solution Demonstration Factor 3: Cybersecurity Demonstration (see Note 3)

PDF

1 Original, 12 copies plus emailed copy

Vol II Non-Price Proposal Details on Section 3.0 Factor 4: Past Performance Factor 5: Small Business Participation

1 Original, 3 copies plus emailed copy

Vol III Price Proposal Details on Section 3.0

1 Original, 1 copy plus emailed copy

Notes:

1. Any spreadsheet information should be on functional EXCEL spreadsheet(s) (e.g. Total Column utilizes equation that sums appropriate lower level items).

1. The Offeror is responsible for providing adequate documentation to enable a thorough evaluation of the proposal.

1. The page limit indicated for Key Personnel Qualifications does not include resumes. Solution and cybersecurity demonstrations documentation also excluded from the total number of pages as is the Integrated Master Schedule and Work Breakdown Structure. Content of Volume I Non-Price Proposal shall not exceed 100 pages.

Written proposals must be formatted using a Times New Roman 12 pt. normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 pt. font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented.

SUBMISSION REQUIREMENTS RELATING TO Evaluation factors and SUBFACTORS Evaluation factors and subfactors are described in Attachment 2, Evaluation Factors for Award, to the solicitation. Offerors’ proposals shall include all information necessary for evaluation as described in Evaluation Factors for Award. In addition, specific submission requirements for certain items are described below:

Instructions:

Group 1: Active Directory Services Factor 1

0. Factor 1: Technical Subfactor A: Technical Approach of the Solution The Offeror shall propose a technical approach that addresses the conceptual operational view of the solution and identifies how the offer meets the requirements identified in Attachment 3, EPoS and Supporting Services Performance Work Statement.

The Offeror shall propose a technical approach meets the Government’s requirements including any associated risk of the Offeror’s non-performance of the approach; illustrates knowledge and understanding of EPoS system processes; and demonstrates an understanding of EPoS concept of operations. Each technical approach factor will be used to evaluate the degree to which the Offeror’s proposed approach meets all requirements and challenges and demonstrates a clear understanding of the EPoS solution requirements as described in the solicitation.

The success and operational capability for the EPoS solution will depend on the Offeror’s technical capability to establish a systems engineering approach that will ensure compliance with the PWS and all other technical and functional requirements proposed for the effort.

The conceptual operational view of the solution is in the Performance Work Statement, 4.0 Scope.

0. Software Development/Configuration Approach

0. Development/Configuration Plan The Offeror shall provide an approach to address requirements:

· Describes the approach for meeting requirements identified in the PWS

· Describes the process for documenting, configuring and managing all development/configuration

· Explains the capability of the solution to meet requirements Quality Control Plan The Offeror shall provide draft Quality Control Plan (QCP):

· Describes the activities and tools that the Offeror will use to ensure a process is in place to deliver quality products and services required by this solicitation

· Provides methods and procedures for adhering to a Quality Assurance Surveillance Plan (QASP); plans and procedures to meet and comply with the quality standards established in the PWS; the Offeror’s self-inspection plan; internal staffing plan; procedures to maintain quality, timeliness, and responsiveness and customer satisfaction for the entire effort Software Sustainment Approach The Offeror shall provide a strategy and management organization structure for the effective and efficient sustainment of the completed implementation. The Government will review and evaluate the Offeror's proposed management approach, including plans for program; quality; security; risk; and personnel management that will be used to ensure the successful sustainment of the resultant contract.

Sustainment Plan The Offeror shall provide sustainment plan that documents how the Offeror proposes to:

· Address periodic maintenance, repair, replacement, and overhaul of existing systems, hardware, and software inclusive of Information Assurance Vulnerability Alerts (IAVA Patching)

· Identify position qualified personnel, test equipment, etc. needed to quickly diagnose and effect repairs

· Provide for the planning, performing, and documenting of system confidence tests, periodic inspections, and preventive maintenance

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

· Analyze fault histories and fault trends to proactively predict and mitigate repetitive issues Help Desk Support The Offeror shall provide help desk support that addresses how the Offeror proposes to:

· Provide technical assistance to the Government in resolving hardware, software failures that result in errors that hinder operations

· Review and analyze production trouble tickets and propose fixes

· Identify methods and mechanisms to actively assist system users in performing their tasks, minimizing the need to communicate with the help desk

· Identify online system documentation or other methods to provide support beyond the help desk Subfactor B: Management Approach and Capabilities The Offeror shall provide Program Management approach to determine the Offeror has developed a strategy and management organization structure for the effective and efficient management of contract activities to successfully fulfill the requirements of the PWS. The Offeror’s approach shall address all aspects of Program Management found within the PWS. The Government will review and evaluate the Offeror's proposed Program Management approach, including plans for program, quality, security, risk, and personnel management that will be used to ensure the successful execution of the resultant contract.

The Offeror shall provide:

· Plan for managing the EPoS effort from a program perspective, including both information technology management and program support activities to include communication and interaction with EPoS PMO, Governance Boards, the DLA Contracting Services Office-Richmond (DCSO-R) Contracting Officer, contract administration and functional requirements staffs

· Risk Management Plan that identifies how the Offeror will proactively track, identify and mitigate risks throughout the life of the proposed effort and how risks will be communicated to appropriate EPoS program personnel

· Proposed Integrated Master Schedule to determine:

· Inclusion of significant milestones, design, development, testing, deployment and installation related activities

· Inclusion of activities related to cybersecurity compliance for certification and accreditation in the production environment

· Provision of a comprehensive, implementable timeline that aligns with the approach in the technical proposal

· Plan for personnel management including program specific training; continuity and succession management of proposed personnel labor mix; the organizational structure and the use of proposed team members and subcontractors in support of this effort

· Work Breakdown Structure (WBS) for assigning resources to the proposed effort. The WBS shall describe how the labor categories and hours proposed for each task are sufficient to meet the PWS requirements

· Plan to support and manage DOD cybersecurity requirements on an ongoing basis; physical security and personnel security including a clear description of the Offeror’s security program and structure; how security fits into the overall management plan and structure; responsibilities of personnel; and how the security plan and personnel will operate/interact with the Government security team

· Communication plan that outlines the method of providing communication to DLA program staff, management, customers and users; addresses the Offeror’s understanding of the importance of communications; and how changes will be communicated Subfactor C: Personnel Qualifications The Offeror shall provide Key Personnel resumes proposed for those resources listed as Key Personnel in listed in the PWS: Program Manager, Cybersecurity Engineer, Senior Applications Programmer, Database Administrator, and Systems Engineer. The resumes of Key Personnel proposed will be evaluated for a clear demonstration that the proposed resources meet or exceed the education and experience requirements outlined in the PWS and List of Attachments:

· Attachment 12, Group 1 Task Order 1 Active Directory Services PWS The information presented in the Offeror’s proposal together with information from any other available sources will provide the primary input for evaluation of this factor. The Government reserves the right to verify Key Personnel performance on other contracts identified by the Offeror in the proposal. The Government reserves the right to use other available information to evaluate Key Personnel. The Government may query contract references and other end user representatives regarding Key Personnel experience and quality of experience.

Group 2: Fixed Facility Device Factors 1, 2, 3 Factor 1: Technical Subfactor A: Technical Approach of the Solution The Offeror shall propose a technical approach that addresses the conceptual operational view of the solution and identifies how the offer meets the requirements identified in Attachment 3, EPoS and Supporting Services Performance Work Statement.

The Offeror shall propose a technical approach meets the Government’s requirements including any associated risk of the Offeror’s non-performance of the approach; illustrates knowledge and understanding of EPoS system processes; and demonstrates an understanding of EPoS concept of operations. Each technical approach factor will be used to evaluate the degree to which the Offeror’s proposed approach meets all requirements and challenges and demonstrates a clear understanding of the EPoS solution requirements as described in the solicitation.

The success and operational capability for the EPoS solution will depend on the Offeror’s technical capability to establish a systems engineering approach that will ensure compliance with the PWS and all other technical and functional requirements proposed for the effort.

The conceptual operational view of the solution is in the Performance Work Statement, 4.0 Scope Software Development/Configuration Approach Development/Configuration Plan The Offeror shall provide an approach to address requirements:

· Describes the approach for meeting requirements identified in the PWS

· Describes the process for documenting, configuring and managing all development/configuration

· Explains the capability of the solution to meet requirements Interface Development The Offeror shall provide an interface development approach that:

· Describes a plan for coordinating, maintaining and implementing EPoS interfaces on the EPoS side of the exchange

· Identifies a clear and effective process for properly documenting, configuring and managing all EPoS interfaces

· Demonstrates the capability of the solution to meet requirements

· Is supported by detailed explanations and illustrations Hardware Capabilities The Offeror shall provide an approach to address Fixed Facility Point of Sale device requirements detailed in section 5.2 of the PWS.

Quality Control Plan The Offeror shall provide draft Quality Control Plan (QCP) that:

· Describes the activities and tools that the Offeror will use to ensure a process is in place to deliver quality products and services required by this solicitation

· Provides methods and procedures for adhering to a Quality Assurance Surveillance Plan (QASP); plans and procedures to meet and comply with the quality standards established in the PWS; the Offeror’s self-inspection plan; internal staffing plan; procedures to maintain quality, timeliness, and responsiveness and customer satisfaction for the entire effort Software Sustainment Approach The Offeror shall provide a strategy and management organization structure for the effective and efficient sustainment of the completed implementation. The Government will review and evaluate the Offeror's proposed management approach, including plans for program; quality; security; risk; and personnel management that will be used to ensure the successful sustainment of the resultant contract.

Sustainment Plan The Offeror shall provide a sustainment plan that documents how the Offeror proposes to:

· Address periodic maintenance, repair, replacement, and overhaul of existing systems, hardware, and software inclusive of Information Assurance Vulnerability Alerts (IAVA Patching)

· Identify position qualified personnel, test equipment, etc. needed to quickly diagnose and effect repairs

· Provide for the planning, performing, and documenting of system confidence tests, periodic inspections, and preventive maintenance

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

· Analyze fault histories and fault trends to proactively predict and mitigate repetitive issues Help Desk Support The Offeror shall provide help desk support that addresses how the Offeror proposes to:

· Provide technical assistance to the Government in resolving hardware, software failures that result in errors that hinder operations

· Review and analyze production trouble tickets and propose fixes

· Identify methods and mechanisms to actively assist system users in performing their tasks, minimizing the need to communicate with the help desk

· Identify online system documentation or other methods to provide support beyond the help desk Solution Installation Approach Installation Plan The Offeror shall provide an installation plan that:

· Exhibits an understanding of the work required under the contract

· Addresses the worldwide implementation of EPoS

· Demonstrates an understanding of customer’s business processes

· Enables seamless conversion from the current systems environment to the replacement system

· Addresses the identification and development of required information exchanges

· Implements EPoS within the period identified in the integrated master schedule

· Minimizes or mitigates interruptions to the operational environment Subfactor B: Management Approach and Capabilities The Offeror shall provide Program Management approach to determine the Offeror has developed a strategy and management organization structure for the effective and efficient management of contract activities to successfully fulfill the requirements of the PWS. The Offeror’s approach shall address all aspects of Program Management found within the PWS. The Government will review and evaluate the Offeror's proposed Program Management approach, including plans for program, quality, security, risk, and personnel management that will be used to ensure the successful execution of the resultant contract.

The Offeror shall provide:

· Plan for managing the EPoS effort from a program perspective, including both information technology management and program support activities to include communication and interaction with EPoS PMO, Governance Boards, the DLA Contracting Services Office-Richmond (DCSO-R) Contracting Officer, contract administration and functional requirements staffs

· Risk Management Plan that identifies how the Offeror will proactively track, identify and mitigate risks throughout the life of the proposed effort and how risks will be communicated to appropriate EPoS program personnel

· Proposed Integrated Master Schedule to determine:

· Inclusion of significant milestones, design, development, testing, deployment and installation related activities

· Inclusion of activities related to cybersecurity compliance for certification and accreditation in the production environment

· Provision of a comprehensive, implementable timeline that aligns with the approach in the technical proposal

· Plan for personnel management including program specific training; continuity and succession management of proposed personnel labor mix; the organizational structure and the use of proposed team members and subcontractors in support of this effort

· Work Breakdown Structure (WBS) for assigning resources to the proposed effort. The WBS shall describe how the labor categories and hours proposed for each task are sufficient to meet the PWS requirements

· Plan to support and manage DOD cybersecurity requirements on an ongoing basis; physical security and personnel security including a clear description of the Offeror’s security program and structure; how security fits into the overall management plan and structure; responsibilities of personnel; and how the security plan and personnel will operate/interact with the Government security team

· Communication plan that outlines the method of providing communication to DLA program staff, management, customers and users; addresses the Offeror’s understanding of the importance of communications; and how changes will be communicated Subfactor C: Personnel Qualifications The Offeror shall provide Key Personnel resumes proposed for those resources listed as Key Personnel in listed in the PWS: Program Manager, Cybersecurity Engineer, Senior Applications Programmer, Database Administrator, and Systems Engineer. The resumes of Key Personnel proposed will be evaluated for a clear demonstration that the proposed resources meet or exceed the education and experience requirements outlined in the PWS and List of Attachments:

· Attachment 13, Group 2 Task Order 1 Fixed Software Development PWS

· Attachment 14, Group 2 Task Order 2 Fixed Software Sustainment PWS

· Attachment 15, Group 2 Task Order 3 Fixed Installation and Sustainment PWS The information presented in the Offeror’s proposal together with information from any other available sources will provide the primary input for evaluation of this factor. The Government reserves the right to verify Key Personnel performance on other contracts identified by the Offeror in the proposal. The Government reserves the right to use other available information to evaluate Key Personnel. The Government may query contract references and other end user representatives regarding Key Personnel experience and quality of experience.

Factor 2: Solution Demonstration The Solution Demonstration will be conducted in two steps. Refer to attachment 8, Solution Demonstration, provided in Attachments section of the solicitation for further details. Documentation for Factor 2 is due at the time of the demonstration.

Instructions:

The Offeror shall create a demonstration of the solution that validates that the set of software, hardware and operating environment work together to provide the capability. The set of software, hardware and operating environment that comprises the solution set shall remain at the Lorton location for a period not to exceed 3 calendar weeks from the date of demonstration for Government review and testing.

Demonstration Location:

Demonstrations will take place at the Fuel Management Defense (FMD) lab located at 10400 Furnace Road, Suite G, Lorton, Virginia 22079 as scheduled by the Contracting Officer.

Demonstration Environment:

Offerors shall provide all hardware, software and Internet access to support the demonstration.

Demonstration Requirements:

Offerors shall:

· Use the EPoS solicitation documentation to extract the functional and technical requirements necessary to adequately configure the demonstration scenarios at the appropriate level of detail

· For each scenario, identify and provide a written record of all EPoS functional and technical requirements in their proposed technical approach that are used to support the scenario

· For each scenario, identify and provide a written record of all information exchanges and methods used to accomplish these exchanges to support the scenario

· For each scenario identify and provide a written record of all instances in the demonstration of the scenario where a stub or a simulation is used as a temporary substitute for a yet to be developed element of their proposed technical approach

· For each scenario, demonstrate the main course of action, as well as all of its variations sequentially

· Wherever parts of the scenario lack a clearly visible user interface component, Offerors shall ensure that good visualization techniques are used to demonstrate the underlying proposed technical approach

· For each scenario, describe how preconditions (if any) have been accomplished

· During the demonstration, identify all system boundaries, information exchanges and user-to-system interactions

· Identify and provide a written record of all external organizations that were connected with via a live or simulated connection (specify which) as necessary to perform the described tasks in the demonstration of scenarios Demonstration Assumptions:

The following is a list of assumptions:

· Demonstration scenarios do not represent additional EPoS requirements, nor do they modify the requirements specified in the solicitation documentation

· Any deviation in a business process description of the demonstration scenarios from the specification of the same business process in the solicitation documentation shall be regarded as serving the sole purpose of facilitating the demonstration scenarios

· Offerors shall not customize the proposed technical approach to support the demonstration of scenarios

· Offerors shall disclose all extensions that were created to support the demonstration of scenarios. An extension is defined as a supplementary routine that adds capabilities to an application without changing the proposed technical approach Factor 3: Cybersecurity Demonstration The Offeror shall conduct execution and assessment of the two Security Technical Implementation Guides (STIGs) in Attachments section of the solicitation. The Offeror shall execute STIG One and Two to show percentage of compliance and provide results of the demonstration. The Offeror shall fill in the appropriate information in the table that is part of Attachment 9. Refer to attachment 9, Cybersecurity Demonstration, provided in Attachments section of the solicitation for further details.The Offeror shall produce a written summation of the number of required control setting compliances as a percentage of the total number that can be accomplished prior to the demonstration. The Offeror shall create a response not to exceed seven pages on letterhead that identifies the results. Documentation for Factor 3 is due at the time of the Factor 2 demonstration.

Group 3: Mobile Device Factors 1, 2, 3 Factor 1: Technical Subfactor A: Technical Approach of the Solution The Offeror shall propose a technical approach that addresses the conceptual operational view of the solution and identifies how the offer meets the requirements identified in Attachment 3, EPoS and Supporting Services Performance Work Statement.

The Offeror shall propose a technical approach meets the Government’s requirements including any associated risk of the Offeror’s non-performance of the approach; illustrates knowledge and understanding of EPoS system processes; and demonstrates an understanding of EPoS concept of operations. Each technical approach factor will be used to evaluate the degree to which the Offeror’s proposed approach meets all requirements and challenges and demonstrates a clear understanding of the EPoS solution requirements as described in the solicitation.

The success and operational capability for the EPoS solution will depend on the Offeror’s technical capability to establish a systems engineering approach that will ensure compliance with the PWS and all other technical and functional requirements proposed for the effort.

The conceptual operational view of the solution is in the Performance Work Statement, 4.0 Scope Software Development/Configuration Approach Development/Configuration Plan The Offeror shall provide approach to address requirements:

· Describes the approach for meeting requirements identified in the PWS

· Describes the process for documenting, configuring and managing all development/configuration

· Explains the capability of the solution to meet requirements Interface Development Plan The Offeror shall provide an interface development approach that:

· Describes a plan for coordinating, maintaining and implementing EPoS interfaces on the EPoS side of the exchange

· Identifies a clear and effective process for properly documenting, configuring and managing all EPoS interfaces

· Demonstrates the capability of the solution to meet requirements

· Is supported by detailed explanations and illustrations Hardware Capabilities The Offeror shall provide an approach to address Mobile Device requirements detailed in section 5.5 of the PWS that addresses mobile device requirements.

Quality Control Plan The Offeror shall provide draft Quality Control Plan (QCP) that:

· Describes the activities and tools that the Offeror will use to ensure a process is in place to deliver quality products and services required by this solicitation

· Provides methods and procedures for adhering to a Quality Assurance Surveillance Plan (QASP); plans and procedures to meet and comply with the quality standards established in the PWS; the Offeror’s self-inspection plan; internal staffing plan; procedures to maintain quality, timeliness, and responsiveness and customer satisfaction for the entire effort Software Sustainment Approach The Offeror shall provide an approach to which the Offeror has developed a strategy and management organization structure for the effective and efficient sustainment of the completed implementation. The Government will review and evaluate the Offeror's proposed management approach, including plans for program; quality; security; risk; and personnel management that will be used to ensure the successful sustainment of the resultant contract.

Sustainment Plan The Offeror shall provide a sustainment plan that documents how the Offeror proposes to:

· Address periodic maintenance, repair, replacement, and overhaul of existing systems, hardware, and software inclusive of Information Assurance Vulnerability Alerts (IAVA Patching)

· Identify position qualified personnel, test equipment, etc. needed to quickly diagnose and effect repairs

· Provide for the planning, performing, and documenting of system confidence tests, periodic inspections, and preventive maintenance

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

· Analyze fault histories and fault trends to proactively predict and mitigate repetitive issues Help Desk Support The Offeror shall provide help desk support that addresses how the Offeror proposes to:

· Provide technical assistance to the Government in resolving hardware, software failures that result in errors that hinder operations

· Review and analyze production trouble tickets and propose fixes

· Identify methods and mechanisms to actively assist system users in performing their tasks, minimizing the need to communicate with the help desk

· Identify online system documentation or other methods to provide support beyond the help desk Device Replacement Approach and Plan The Offeror shall provide a device replacement plan that:

· Exhibits an understanding of the work required under the contract

· Addresses the worldwide implementation of EPoS

· Demonstrates an understanding of providing replacement devices within required time periods

· Enables seamless conversion from the current systems environment to the replacement system

· Addresses the identification and development of required information exchanges

· Implements EPoS within the period identified in the integrated master schedule

· Minimizes or mitigates interruptions to the operational environment Subfactor B: Management Approach and Capabilities The Offeror shall provide a Program Management approach to determine the Offeror has developed a strategy and management organization structure for the effective and efficient management of contract activities to successfully fulfill the requirements of the PWS. The Offeror’s approach shall address all aspects of Program Management found within the PWS. The Government will review and evaluate the Offeror's proposed Program Management approach, including plans for program, quality, security, risk, and personnel management that will be used to ensure the successful execution of the resultant contract.

The Offeror shall provide:

· Plan for managing the EPoS effort from a program perspective, including both information technology management and program support activities to include communication and interaction with EPoS PMO, Governance Boards, the DLA Contracting Services Office-Richmond (DCSO-R) Contracting Officer, contract administration and functional requirements staffs

· Risk Management Plan that identifies how the Offeror will proactively track, identify and mitigate risks throughout the life of the proposed effort and how risks will be communicated to appropriate EPoS program personnel

· Proposed Integrated Master Schedule to determine:

· Inclusion of significant milestones, design, development, testing, deployment and installation related activities

· Inclusion of activities related to cybersecurity compliance for certification and accreditation in the production environment

· Provision of a comprehensive, implementable timeline that aligns with the approach in the technical proposal

· Plan for personnel management including program specific training; continuity and succession management of proposed personnel labor mix; the organizational structure and the use of proposed team members and subcontractors in support of this effort

· Work Breakdown Structure (WBS) for assigning resources to the proposed effort. The WBS shall describe how the labor categories and hours proposed for each task are sufficient to meet the PWS requirements

· Plan to support and manage DOD cybersecurity requirements on an ongoing basis; physical security and personnel security including a clear description of the Offeror’s security program and structure; how security fits into the overall management plan and structure; responsibilities of personnel; and how the security plan and personnel will operate/interact with the Government security team

· Communication plan that outlines the method of providing communication to DLA program staff, management, customers and users; addresses the Offeror’s understanding of the importance of communications; and how changes will be communicated

0. Factor 2: Solution Demonstration The Solution Demonstration will be conducted in two steps. Refer to attachment 8, Solution Demonstration, provided in Attachments section of the solicitation for further details. Documentation for Factor 2 is due at the time of the demonstration.

Instructions:

The Offeror shall create a demonstration of the solution that validates that the set of software, hardware and operating environment work together to provide the capability. The set of software, hardware and operating environment that comprises the solution set shall remain at the Lorton location for a period not to exceed 3 calendar weeks from the date of demonstration for Government review and testing.

Demonstration Location:

Demonstrations will take place at the Fuel Management Defense (FMD) lab located at 10400 Furnace Road, Suite G, Lorton, Virginia 22079 as scheduled by the Contracting Officer.

Demonstration Environment:

Offerors shall provide all hardware, software and Internet access to support the demonstration.

Demonstration Requirements:

Offerors shall:

· Use the EPoS solicitation documentation to extract the functional and technical requirements necessary to adequately configure the demonstration scenarios at the appropriate level of detail

· For each scenario, identify and provide a written record of all EPoS functional and technical requirements in their proposed technical approach that are used to support the scenario

· For each scenario, identify and provide a written record of all information exchanges and methods used to accomplish these exchanges to support the scenario

· For each scenario identify and provide a written record of all instances in the demonstration of the scenario where a stub or a simulation is used as a temporary substitute for a yet to be developed element of their proposed technical approach

· For each scenario, demonstrate the main course of action, as well as all of its variations sequentially

· Wherever parts of the scenario lack a clearly visible user interface component, Offerors shall ensure that good visualization techniques are used to demonstrate the underlying proposed technical approach

· For each scenario, describe how preconditions (if any) have been accomplished

· During the demonstration, identify all system boundaries, information exchanges and user-to-system interactions

· Identify and provide a written record of all external organizations that were connected with via a live or simulated connection (specify which) as necessary to perform the described tasks in the demonstration of scenarios Demonstration Assumptions:

The following is a list of assumptions:

· Demonstration scenarios do not represent additional EPoS requirements, nor do they modify the requirements specified in the solicitation documentation

· Any deviation in a business process description of the demonstration scenarios from the…