C2SES_III_Sec_L_Draft.docx

GENERAL INSTRUCTIONS AND INFORMATION

L1.0. PROPOSAL PREPARATION INSTRUCTIONS

L1.1. To assure timely and equitable evaluation of proposals, offeror’s must follow the instructions contained herein. Offeror’s are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offeror’s must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The response shall consist of the volumes as identified in Paragraph L2.0., Table 2.0. It is the offeror’s responsibility to ensure the completeness of the proposal. Evaluation of a proposal will be conducted only on the basis of the information contained within it and the Government will not assume that an offeror possesses any capabilities not specified. This does not limit the government from evaluating past performance data obtained from other sources in accordance with section M 3.2.

L1.2. The Contracting Officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the contracting officer will review this determination and if, in the contracting officer's opinion, adequate price competition exists no additional cost/price information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the contracting officer determines that adequate price competition no longer exists, offeror’s may be required to submit information to the extent necessary for the contracting officer to determine the reasonableness of the price.

L1.3. SPECIFIC INSTRUCTIONS

L1.3.1. BUDGET PROFILE

The following provides the projected budget profile for C2SES III. Dollars shown below are in millions. The IDIQ will consist of an ordering period of 5 years, and a six month extension IAW FAR 52.217-8. The first task order will consist of a one month transition (1 October 2017 – 31 October 2017) and 11 months of full performance (1 November 2017 – 30 September 2018) for a full 12 months PoP. The four option periods (Option Period 1 – 4) will be one-year in duration, running 1 October – 30 September. Option Period 5 (FY23 funding) is for the 6-month extension period of 1 October 2022 –31 March 2023 in accordance with FAR 52.217-8.

L1.3.2. POINTS OF CONTACT (POCs) The Contracting Officer (CO)/Contract Administrator (CA) are the sole points of contact for this acquisition. Address any questions or concerns you may have to the Contracting Officer and the Contract Administrator. For this acquisition, the Contracting Officer is Ms. Theresa Bryant and the Contract Administrator is Ms. Melissa Hergenrader.

Contracting Officer contact information:

Phone: (402) 294-7304 or DSN: 271-7304

L1.3.2.1 All inquiries must be made in writing and submitted electronically to the above e-mail addresses. A copy of the e-mail shall be sent to the CO (theresa.bryant@us.af.mil) and the CA (melissa.hergenrader@us.af.mil). Offeror's will receive a notice of receipt. If they do not, it is their responsibility to follow-up by contacting the Contracting Officers or Contract Administrator (phone numbers listed above). Written inquires (questions) will be answered in writing and provided to all offeror’s via posting(s) to the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov.

L1.4. PROPOSAL ACCEPTANCE PERIOD AND DUE DATE

The proposal due date is specified in Table 2.0 and proposals shall be submitted in accordance with the instructions in L1.0 through L6.5. The offeror shall make a clear statement that its offer is valid for at least 2 years beyond the due date. Late proposals will be handled IAW FAR 15.208. If any proposal is received late, the Contracting Officer will promptly notify the offeror that its proposal was received late and whether the proposal will still be considered. It is the offeror’s responsibility to confirm the Government has received the proposal. A receipt e-mail will be sent to the offeror. If the offeror does not receive a confirmation, it is their responsibility to contact the POC.

L1.5. BROCHURES, DOCUMENTATION, BINDING, AND ARTWORK

Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

L1.6. DISCREPANCIES

If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the Contracting Officer in writing with supporting rationale, prior to proposal submission.

L1.7. DISPOSITION OF PROPOSALS

In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain the “original” copy of all proposals and supplemental documents provided. Unless the offeror requests otherwise, the Government will destroy all extra copies of proposals and additional documents submitted.

L1.8. PROPOSAL CLARITY

The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet the requirements. The offeror shall also provide a matrix cross-referencing back to the requirements documents. (NOTE: Section J, Attachment 14: Technical Cross Reference Matrixes may be utilized or a matrix in the offeror’s format; however, whichever format is used by the offeror shall address the areas in both Performance Work Statements (PWS’s): the IDIQ contract PWS and the task order 0001 PWS.) The offeror shall assume that the Government has no prior knowledge of the offeror’s capabilities and experience, and will base its evaluation on the information presented in its proposal. This does not limit the government from evaluating past performance data obtained from other sources in accordance with Section M 3.2. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

L1.9. RESTRICTIONS ON DISCLOSURE AND USE OF PROPOSAL

A proposal may include data, such as technical designs or concepts, financial data, or management plans that the offeror does not want disclosed to the public for any reason, or used by the Government for any purpose other than proposal evaluation and contract award. If the offeror wishes to restrict the proposal, the offeror shall mark it in accordance with FAR 52.215-1. Any unmarked information will be considered releasable under the restrictions of the Freedom of Information Act.

L1.10. GOVERNMENT FURNISHED PROPERTY (GFP)

There is currently no Government Furnished Property. However, there is a possibility that GFP may be required in future task orders.

L1.11. SECURITY REQUIREMENTS

The DoD Contract Security Classification Specification, DD Form 254, incorporated as Attachment 1 in Section J, identifies the security clearance requirements and classified material handling requirements of this contract.

L1.12. TECHNICAL LIBRARY

A technical library has been established for the C2SES III Contract. The library is composed of technical, architecture, and schematic data and information. This information will be available for all interested contractors. The library is located in the LeMay Building (Building 500, USSTRATCOM) on Offutt Air Force Base, NE. The library contains program and technical information (up to and including TOP SECRET) pertaining to the existing systems and contract activities for C2SES III. The library will be open Monday through Friday, from 0800-1200 and 1300-1500, excluding U.S. Government holidays. Library users are cautioned that although the Government has attempted to gather current and relevant material, the Government does not represent or warrant that the material is accurate, current, or complete. The following rules apply to the use of the library:

a. To have access to the library and the LeMay Building (USSTRATCOM), corporate security offices must fax a Visit Authorization Request (VAR) as specified in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) to the USSTRATCOM Personnel Security Manager (FAX 402-294-6868), and the C2SES Program Office (FAX 402-294-7961). The purpose of the visit request should state "Visit the C2SES III Bidders Library". The VAR must arrive five (5) business days prior to the time of the scheduled visit. This lead-time is required to conduct security checks and verifications necessary to allow access to Offutt Air Force Base. Corporate security offices should call the J050 Security Manager (402-294-6868) to confirm receipt of the VAR.

b. Persons viewing the bidder’s library will require the appropriate clearance. A security clearance of TOP SECRET is required to view the entire library. Visits to the library will be by appointment ONLY and on a first come-first served basis. Bidders will be permitted to schedule up to four (4) hours per day, subject to availability. Appointments should be made prior to sending a visit request to confirm availability of requested date and time. Appointments must be made at least five (5) business days in advance of the requested date/time. Appointments will be made by calling or emailing David Griggs at 402-294-4944, griggsd@stratcom.mil, or Greg Perez at 402-232-6003, perezgj@stratcom.mil. Contractors who fail to show within 30 minutes following the scheduled start time, without prior notification, will have to reschedule.

c. No more than three (3) individuals will be allowed in the library at any one time. All visitors are required to sign in/out on each visit and must be escorted at all times. Visitors will not be allowed to bring computers, storage media, cell phones, or personal data assistants into the LeMay Building. Visitors will not be allowed to remove originals of any documents from the library. Library material shall not be photocopied. Contractors will not be allowed to take handwritten unclassified notes. Notes must be protected using the appropriate DoD security procedures in DoD 52100.1R. Visitors will be expected to abide by all other general rules of the reference library, which will be briefed at the beginning of the appointment. Contractors may ask questions by using question forms that are available in the library. The Government will answer questions in a timely manner and post on FedBizOpps. Unclassified questions may also be submitted by email to melissa.hergenrader@us.af.mil.

d. Directions to the LeMay Building are as follows: For entrance to the SAC gate of Offutt AFB, stop at the Visitor Control Center, on Capehart Road, to obtain a temporary contractor ID for unescorted entry on Base. After leaving the Visitor's Center, enter the SAC gate and veer left onto SAC Boulevard. Turn right onto Looking Glass Avenue and park in the parking lot on the left side of the street. Bidders should proceed to the USSTRATCOM Visitor Center (Building 591) located on the north side of the LeMay Building next to the Mercury Avenue entrance into the STRACOM compound. A telephone is available in the Visitor's Center to contact the Program Office (294-4944 or 232-6003) to arrange an escort to the library.

L1.13. DEBRIEFINGS

The Contracting Officer will promptly notify offeror’s of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505, Preaward Debriefing of Offeror’s. The Contracting Officer will also notify unsuccessful offeror’s in the competitive range of the source selection decision in accordance with FAR 15.503, Notifications to Unsuccessful Offeror’s. Upon such notification, unsuccessful offeror’s may request and receive a debriefing after contract award. Offeror’s desiring a debriefing must make their request in accordance with the requirements of FAR 15.506, Postaward Debriefing of Offeror’s, as applicable. At the offeror’s request, the preaward debriefing may be delayed until after award; offeror’s are entitled to no more than one debriefing (either preaward, if applicable, or postaward).

L2.0. ORGANIZATION OF PROPOSALS

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 2.0 below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.0. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. The proposal organization shall be as follows:

Table L2.0

(5 references @ 3 pages each, additional allowed for subcontractors - see para. L 4.5.1)

III. Cost/Price (Section J, Attachment 12, Cost/Price Model shall be returned as a part of the Cost/Price Proposal)

IV. Contract Documentation/ Fill-in Clauses

*CD Rom shall be submitted IAW Para L2.1.6

*All documents due by 4:00 PM Central Time on the date specified in this table

*The executive summary (although part of Vol I) shall not count against the 60 page limit

*Small Business Subcontracting Plan – to be submitted in Volume IV and reviewed IAW FAR 19.704.

L2.1. PROPOSAL FORMAT AND CONTENT

L2.1.1. PAGE LIMITATIONS

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and paper copies will not be returned to the offeror. Excess pages shall be destroyed along with all extra copies of unsuccessful proposals (ref. L1.7). For electronic submission, no hidden fields, macros, comments, etc. will be read. All information must be written clearly and be easily accessible. Page limitations may also be placed on Evaluation Notices (ENs), if required. The page limitations for EN responses, if any, will be identified in the correspondence forwarding the ENs to the offeror’s. When both sides of a sheet of paper display printed material, it shall be counted as two pages. Each page shall be counted except: cover pages, tables of contents, cross-reference matrix, tabs, glossaries, and overview section if offeror takes exception to any requirement (reference L6.2).

L2.1.2. PAGE SIZE

Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than Times New Roman 10 point. Use at least 1-inch margins on all sides of each page. Pages shall be numbered sequentially by volume. If there are discrepancies in page counts between paper, CD-ROM volumes and e-mail submittals, the paper version shall take precedence.

L2.1.3. TABLES, CHARTS, GRAPHS, AND FIGURES

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 by 17 inches in size when printed. Foldout pages shall fold entirely within the volume, and count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, and not for pages of text. For tables, charts, graphs and figures only, the text shall be no smaller than 8 point using Times New Roman or Arial font.

L2.1.4. CLASSIFIED INFORMATION

Proposals shall not contain classified information.

L2.1.5. COST/PRICING INFORMATION

All cost/pricing information shall be addressed only in the Cost/Price Volume.

L2.1.6. ELECTRONIC MEDIA

In addition to submission of the required number of proposal volume paper copies, offeror’s shall submit all volumes in electronic format, using IBM-compatible, virus-free CD-ROM(s). On each CD-ROM indicate the offeror’s name, solicitation number, volume, and title. One CD-ROM containing all volumes with all documents is preferred, but multiple CD-ROMs are acceptable. WinZip shall be the compression/decompression program used if files are required to be compressed. The electronic copies of the proposal shall be submitted in a format readable and usable by Microsoft Office 2010 (MS Word, MS Excel, PowerPoint or PDF format viewable with standard Adobe Acrobat Reader X). Hidden fields, comments, macros, etc. shall be omitted, and read passwords on files shall not be used. The price model shall be submitted in excel and not as a picture shot. The files shall be consistent and uniformly named to allow for easy distinction between Volume, Tab, etc. Inclusion of company name or abbreviation is acceptable if the offeror prefers. The documents submitted in electronic format, if printed, should match the original paper copy. In the event there is a discrepancy between the content found in a paper copy and an electronic copy, the paper copy shall take precedence. The receipt of the paper copy shall constitute the timely receipt of the formal proposal.

L2.1.7. CROSS-REFERENCE MATRIX

To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with minimal cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Offeror shall provide Section J, Attachment 14: Technical Cross Reference Matrixes as a cross-reference matrix indicating the corresponding proposal paragraph in that section and/or volume which addresses the referenced item. Information required for proposal evaluation that is not found in its designated volume will be assumed omitted from the proposal. The cross-reference matrix will not count against the page limitations for their respective volumes.

L2.1.8. TAB INDEXING

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Indexes and tabs do not count against the page limitations for their respective volumes.

L2.1.9. GLOSSARY OF TERMS

Each volume shall contain a glossary of all abbreviations, acronyms and/or terms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L2.1.10. BINDING AND LABELING

Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet shall be included in each volume, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

L2.1.11. DISTRIBUTION

The “original” and all copies of the proposal (See Table L2.0) shall be identified and mailed or delivered to 55CONS at the following address:

(Theresa Bryant or Melissa Hergenrader)

Offeror’s are cautioned that Offutt AFB, NE has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. SIGNIFICANT DELAY SHOULD BE ANTICIPATED WHEN HANDCARRYING PROPOSALS AND ALSO YOU ARE WARNED THAT YOU MAY NOT BE ABLE TO ACCESS THE BASE (E.G. DURING A BASE LOCK-DOWN). IF YOU PLAN TO DELIVER YOUR PROPOSAL AND DO NOT HAVE ACCESS TO THE BASE, YOU MUST COORDINATE WITH THE 55 CONS POCS LISTED ABOVE PRIOR TO THE PROPOSAL DUE DATE.

If mailing, the outside of the envelope or box(es) should be marked as follows:

L3.0. VOLUME I – TECHNICAL CAPABILITY AND TECHNICAL RISK VOLUME

L3.1. GENERAL

The purpose of the Technical Capability and Technical Risk Volume is to provide the Government the ability to evaluate the management and technical capability of the offeror to perform the Command and Control Software Engineering and Support III (C2SES III) requirements. At a minimum, the Technical proposal shall consist of the following subfactors:

Technical Subfactors:

Subfactor 1: Software Engineering Services Subfactor 2: System Engineering Subfactor 3: Program Management Subfactor 4: Small Business Participation Commitment Document (SBPCD)

L3.1.1. The offeror’s Technical Capability and Technical Risk proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The Technical and Technical Risk volume may consist of offeror-prepared approach such as a systems engineering approach, program management approach, etc. Through proposal submission, the offeror represents that it will fulfill the requirements specified in the solicitation; therefore, it is not necessary or desirable for an offeror to state this in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. The Technical Capability and Technical Risk proposal shall not include price/cost information or classified information. The Technical Capability and Technical Risk Volume will be used to evaluate the technical acceptability of the offeror’s proposal. Evaluation will be against the Technical and Technical Risk subfactors as specified in Section M, Evaluation Factors for Award, of this RFP.

L3.1.2. The offeror’s Technical Capability and Technical Risk volume shall present a clear, thorough demonstration of how the offeror plans to manage the requirements defined in the PWS, resources to be used, and the methodologies/processes that will be used in accomplishing the C2SES III requirements. All the requirements specified in the solicitation are mandatory. The “shalls” of the PWS are not required to be addressed individually but as a whole in accordance with the requirements.

L3.1.3. This paragraph explains how the services summary performance objectives, listed under Section 7 of the PWS(s) measure satisfaction of the PWS requirements The services summary identifies what the Government wants offeror performance to achieve. The measurement of the level of performance the Government expects the offeror to achieve is specified by the thresholds in the service summary. The PWS defines the Government’s requirements in terms of the deliverables (CDRLS) and deliverable’s content the Government wants to receive from contractor processes. The deliverables are the performance the Government requires the offeror to achieve. The Government evaluates if the deliverables meet the PWS requirements by using the thresholds specified in the services summary criteria.

L3.2. EXECUTIVE SUMMARY

Provide the Government evaluators an executive summary with a clear and concise introduction to the content and structure of the Technical proposal. This should be a "big picture" explanation and provide the offeror’s overall approach and supporting rationale for the management and operation of the C2SES III requirements. The format of the Executive Summary is at the discretion of the offeror, but shall include a Master Table of Contents of the entire proposal that identifies where material may be found for each evaluation factor and/or subfactor as described in this RFP. Any summary material presented here shall not be considered as meeting the requirements of any portions of other volumes of the proposal. Within the Executive Summary, the offeror shall state that its proposal is valid for the timeframe designated in paragraph L1.4 Proposal Acceptance Period and Due Date. The offeror shall identify those personnel authorized to negotiate on behalf of the company along with the telephone number, fax number, mailing address, and e-mail address. Furthermore, the offeror shall also provide the person to contact if the Government initiates discussions and who to contact if the offeror is awarded the contract (provide at a minimum, contact’s name, title, phone number, and e-mail address). The Executive Summary will not count towards the maximum page count for Volume I, Technical Capability and Technical Risk. Technical Capability and Technical Risk information shall not be included in the Executive Summary. If Technical Capability and Technical Risk information is included in the Executive Summary, it shall not be evaluated.

L3.3. TECHNICAL SUBFACTORS

L3.3.1. SUBFACTOR 1 - Software Engineering Services The offeror shall describe the software engineering approach for C2SES III as identified in the ”Contract PWS” to include the Services Summary. The offeror shall include internal processes and shall address the following:

L3.3.1.1. The offeror shall demonstrate the offeror’s software engineering processes ensure Government requirements are met. Provide an overview of the software lifecycle processes that will be followed to maintain software under this contract. Describe the ability/flexibility of software processes to support agile/rapid development, short duration release cycles, and creation of applicable web services. Describe processes for developing applications using an n-tier architecture, while utilizing x86 standard hardware and system software (UML and Object Oriented Design). Demonstrate legacy language design and programming (i.e. ADA, Fortran and C++)

L3.3.1.2. The offeror shall demonstrate the offeror’s integration strategy, identify COTS, GOTS, and platform impacts to the system and associated software architectures; ensure successful implementation of software quality (requirements decomposition, minimizes errors and produce no failures). Include the approach the offeror will use to identify the technical impacts of the design, coding, test, security adherence, and implementation/integration to the defined enterprise architecture. Describe the tools and techniques that will be used to coordinate all internal and external activities and dependencies to support early identification of issues in the Government defined environments.

L3.3.1.3. The offeror shall demonstrate the offeror’s sustainment processes to maintain the operational readiness of C2 systems. Identify the specific mechanisms within the software sustainment processes that ensure the quality (e.g., minimize defects) and operational availability of software delivered under this contract. Include what approach will be used for on-call responses to ensure no degradation in operational readiness.

L3.3.1.4. The offeror shall demonstrate the offeror’s processes accurately document and track changes during the release cycle to ensure proper documentation of modifications between major releases. Include what approach will be used to ensure that no information is lost and documentation updates are only accomplished when necessary.

L3.3.2. SUBFACTOR 2 - System Engineering The offeror shall describe the system engineering approach for C2SES III as identified in the ”Contract PWS” to include the Services Summary. The offeror shall include internal processes and shall address the following:

L3.3.2.1. The offeror shall demonstrate the offeror’s systems engineering processes ensure Government requirements are met. Include a description of the processes, techniques, and tools that will be used to implement rigorous system engineering processes across the software life cycle. Describe methods and processes that will be employed to ensure the use of common system engineering processes, software tools, techniques, and where practicable, services/languages/libraries/code across the C2SES III systems/applications. Provide a description of the offeror’s management approach of the software life cycle process and how it aligns with the Government SEMP, emphasizing reviews, documentation, and deliverables.

L3.3.2.2. The offeror shall demonstrate the offeror’s requirements processes ensure traceability between Government System-Level requirements and the program software requirements. Include a description of how the offeror will control and manage the software requirements baseline, what tools and techniques will be employed, and how stakeholder requests and deficiency reports will be tracked and managed. Include descriptions of Government touch-points, accessibility/availability of tools and information, and mechanisms to ensure alignment and traceability to system requirements.

L3.3.2.3. The offeror shall demonstrate the offeror’s systems engineering processes ensure software quality and contribute to/enhance the delivery of defect-free software. Describe the procedures the offeror will employ during the software lifecycle process to identify, mitigate and manage risk and contribute to optimal/efficient design solutions.

L3.3.2.4. The offeror shall demonstrate what processes and techniques will be used to proactively plan and prepare for upgrades or changes to the operational environment, changes/upgrades to interfacing systems, and major requirements. Include a description of how system analyses and trade studies will be conducted to arrive at optimal design solutions.

L3.3.2.5. The offeror shall demonstrate what approach will be used to identify the communication impacts from external programs to the design, coding, test, and implementation/integration to the defined enterprise architecture. Describe the specific processes and techniques that will be used to proactively plan and prepare for upgrades or changes to the operational environment, changes/upgrades to interfacing systems, and major requirements identified by C2 functional managers. Include a description of how system analyses and trade studies will be conducted to arrive at optimal design solutions, and drive cost efficiencies to reduce life-cycle costs.

L3.3.2.6. The offeror shall demonstrate the offeror’s requirements processes ensure tracking between Government System-Level requirements related to communication devices and the program software requirements. Include a description of how the offeror will control and manage the software baseline for communication interfaces, what tools and techniques will be employed, and how will change requests related to dependencies on communication devices be tracked and managed. Include descriptions of government touch-points, accessibility/availability of tools and information, and mechanisms to ensure alignment and traceability to system and software requirements.

L3.3.2.7 The offeror shall demonstrate how the offeror will ensure that software baselines are properly managed and controlled. Describe the configuration management (CM) processes and tools for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design, and operational information throughout its lifecycle. Include how the offeror’s processes will align with government configuration management processes and procedures (i.e., the J864 C2 Mission Portfolio Configuration Management Plan), especially with respect to government and contractor integration/touch points.

L3.3.2.8. The offeror shall demonstrate the offeror’s configuration management processes ensure all risks are identified and how risk mitigation plans will be actively implemented for moderate and high risks. Provide a description of the offeror’s risk management processes, including how risks will be identified, tracked, and mitigated. Include a description of how the offeror will engage the Government in this process.

L3.3.2.9. The offeror shall demonstrate the offeror’s quality control processes minimize implementation errors and produce no integration failures. Include a description of the overall approach, procedures, metric collection, and continuous process improvement methodologies to ensure software quality for delivered systems/applications. Describe reporting methods for tracking/ trending quality factors/attributes, and how the offeror will ensure that the Government maintains visibility into software quality information metrics and issues.

L3.3.2.10. The offeror shall demonstrate the offeror’s quality assurance, security engineering, system administration, and database/database administration processes that ensures all risks are identified and risk mitigation plans are actively used for moderate and high risks. Provide a description of the offeror’s risk management processes, including how risks will be identified, tracked, and mitigated. Include a description of how the offeror will engage the Government in this process.

L3.3.2.11. The offeror shall demonstrate the offeror’s quality assurance processes ensure all key milestones and key milestone due dates are met. Describe how the offeror’s quality assurance processes will ensure/contribute to the timely delivery of all documentation and software for C2SES systems.

L3.3.2.12. The offeror shall demonstrate how the offeror’s security engineering processes minimize security findings and ensure on-time deliveries. Describe security engineering processes and/or mechanisms that ensure security/information assurance is addressed throughout the software life cycle. Include a description of how these processes will be used to identify, resolve, or mitigate security vulnerabilities early in the process. Describe methods and processes that will be employed to ensure the use of common processes, techniques, documentation, support and where practicable, security scanning tools across the C2SES III systems/applications. Provide a description of the offeror’s security management approach and how it aligns with the Government SEMP, DoD guidance, and USSTRATCOM policies, emphasizing reviews, documentation, and deliverables.

L3.3.2.13. The offeror shall demonstrate the offeror’s security engineer, system administration, and database administration processes that ensures contractor personnel have appropriate professional certifications and have sufficient number of personnel with required certifications at the beginning of full performance.

L3.3.2.14. The offeror shall demonstrate the offeror’s system administration processes that minimizes impact to software and test activities and ensure on-time deliveries of software. The offeror’s system administration processes will demonstrate the capability to manage multiple simultaneous task orders which are integral amongst each other.

L3.3.2.15. The offeror shall demonstrate the offeror’s system administration processes and identify what metrics will be used to measure system performance across all environments, including trend analysis.

L3.3.2.16. The offeror shall demonstrate the offeror’s database and data administration processes to minimize errors and ensure on-time deliveries. The offeror’s database administration processes will demonstrate the capability to manage multiple simultaneous releases which are integral amongst each other.

L3.3.2.17. The offeror shall demonstrate the offeror’s database administration processes to identify metrics used to tune and measure database performance including trend analysis and Government access to reports and history.

L3.3.2.18. The offeror shall demonstrate the offeror’s test processes to ensure that Government requirements are satisfied and the delivery of defects to the operational environment are minimized. Describe the overall test and verification methodology/approach for all phases and how test processes support/align with the C2 Test Process Description document. Include a description of tools and methods to ensure integration with existing capabilities/infrastructure and also demonstrate performance requirements are met or in the absence of a stated performance requirement, performance is not significantly degraded as a result of software maintenance activities.

L3.3.2.19. The offeror shall demonstrate the offeror’s test processes to ensure that regression testing is satisfied. Describe the regression testing methodology and approach for all software releases, and how regression test processes support/align with the C2 Test Process Description document.

L3.3.2.20. The offeror shall demonstrate the offeror’s test processes accurately capture and track identified issues during the test cycle and ensure problem resolution and proper documentation before software release. Include what approach and process will be used to ensure tracking of issue and resolution with documentation updates.

L3.3.2.21. The offeror shall demonstrate the offeror’s test processes to ensure all key test activities and deliverables align with the software and system engineering processes are delivered IAW established milestones.

L3.3.3. SUBFACTOR 3 - Program Management The offeror shall describe the program management approach for C2SES III as identified in the ”Contract PWS” to include the Services Summary. The offeror shall include internal processes and shall address the following:

L3.3.3.1. The offeror’s program management/systems management processes ensure sufficient personnel are available to meet mission requirements. It shall also describe what approach will be used to recruit and retain personnel to accommodate varying staffing requirements over the life of the contract, including long-term, ongoing tasks, special efforts of lesser duration, and rapid replacement/addition of personnel in the event of emergencies/contingencies. The subfactor will be deemed technically acceptable if the offeror demonstrates a process that identifies mission essential billets (reference DFARS 252.237-7023) and ensures they are continually filled for the life of the contract with qualified personnel with appropriate security clearance (e.g., Secret, Top Secret). The offeror’s process must demonstrate ability for flexible staffing to accommodate manpower requirements for emergencies/contingencies, special projects, and personnel losses. The offeror must also demonstrate key positions will be filled with qualified personnel and the ability to provide letters of intent for key personnel. The demonstrated processes have to ensure sufficient numbers of personnel are available to meet mission requirements. Reference Attachment 17, Key Contractor Personnel for additional details.

L3.3.3.2. The offeror shall demonstrate how the offeror will recruit, hire, retain, and replace trained and qualified personnel with appropriate security clearances (e.g., Secret, Top Secret) to support mission requirements through the life of the contract. The offeror describes what approach will be used to recruit, train, and retain personnel to accommodate varying staffing requirements over the life of the contract, including long-term, ongoing tasks, special efforts of lesser duration, and rapid replacement/addition of personnel in the event of emergencies/contingencies.

L3.3.3.3. The offeror shall demonstrate how the offeror will lead, manage, and control C2SES III efforts to include understanding of the C2SES III systems and missions, plus the agencies they support, as well as their systems/subsystems and capabilities, in order to assess, enhance, maintain, and sustain USSTRATCOM C2 systems. Include how the contractor will support Government lead groups to include Integrated Team Processes (IPT)s, management boards, and working groups identified by the Government. Include how the contractor will institute and maintain a process to ensure problems, issues, and action items are discussed with the Government, tracked through resolution, and provide timely status reporting.

L3.3.3.4. The offeror shall demonstrate how the offeror will provide unscheduled Technical Support. Include uninterrupted 24/7 support during a labor strike, surges, natural disasters, disruptive world events, terrorist attacks, government shutdowns and/or other emergencies.

L3.3.3.5. The offeror shall demonstrate how the offeror will provide management of facilities, equipment, and material provided by the Government, at no additional cost to the Government.

L3.3.3.6. The offeror shall demonstrate the offeror’s program management/systems management processes that manage cumulative to date priorities and minimize schedule variances. Include what approach will be used to keep the Government informed of cost, schedule, and performance status, notified timely of issues with contract performance, metrics to measure contract and system performance to include trend analysis, and provide the Government access to the metrics history for the contract. The offeror’s processes shall demonstrate the capability to manage multiple simultaneous task orders which are integral to each other.

L3.3.3.7. The offeror shall demonstrate the offeror’s organizational structure and effective lines of authority, communication, functional relationships, roles and responsibilities to include integration of teaming partners and subcontractors, and reach back capabilities to ensure successful mission accomplishment.

L3.3.3.8. The offeror shall demonstrate how the offeror will ensure uninterrupted support with no degradation of service for C2SES III requirements and implement a phase-in process that is comprehensive and realistic for assumption of full responsibility.

L3.3.3.9. The offeror shall demonstrate how the offeror will execute a comprehensive approach for ramping up and obtaining/retaining personnel with the appropriate mix of qualifications/skill sets, IT certifications, and personnel security clearances from award to start of full performance. Demonstrate how the offeror possesses or how the offeror will acquire prior to award, a Facility Security Clearance equal to the highest billet clearance requirement. Include the approach to ramp up during the transition period to assume full performance by the required date. The approach should identify the time phasing required for such key tasks such as systems engineering, program and system management, and sustainment. Identify when key personnel will be brought on and the roles they will play during the transition period.

L3.3.3.10. The offeror shall demonstrate how the offeror will ensure an understanding of the activities and resources required to successfully transition personnel and workload requirements for continuity of mission support.

L3.3.3.11. The offeror shall demonstrate how the offeror will aggressively mitigate transition risks and implement measures to ensure a successful transition. The offeror’s transition risk mitigation approach will identify resources required to support the transition, support early identification of transition risks, and show a logical set of steps within the resources identified to diminish realized risks that would prevent being fully capable to perform all contract requirements by full performance date.

L3.3.4 SUBFACTOR 4 - Small Business Commitment Document (SBPCD) All offerors shall submit a SBPCD which will be used for the purposes of evaluating the offeror’s identification of and commitment to small business in contract performance on the C2SES III program. The SBPCD is required from all offerors, including small businesses, large businesses, non-profit entities and companies with commercial subcontracting plans, master subcontracting plans, individual (program) subcontracting plans and/or comprehensive subcontracting plans. Based on experience with the current contract and market research analysis, the Government has established a baseline for small business participation at a minimum of 15% of total contract value. Table L3.3.4 The offeror’s SBPCD shall:

L3.3.4.1. Specifically identify small business firms in the SBPCD and provide detailed explanations/documentation supporting the proposed participation percentages. The offeror shall provide contact information and DUNS number for all identified small businesses.

L3.3.4.2. The extent of commitment to use small businesses in all socioeconomic categories by providing enforceable commitment letters or related documents.

L3.3.4.3. Include the offeror’s initiatives to assist, promote and utilize small business (SB), small disadvantaged business (SDB), women-owned small business (WOSB), Historically Underutilized Business Zone (HUBZone) small business, veteran-owned small business (VOSB) and/or service-disabled veteran-owned small business (SDVOSB).

L3.3.4.4. Demonstrate examples of how the offeror will maximize small business opportunities and use small business in meaningful work (e.g. mission critical, technology innovation) throughout the program and by Identifying the complexity and variety of work small businesses will perform.

Table L3.3.4 Small Business Participation Commitment

Small

Disadvantaged

Woman

Veteran

Service Disabled Veteran

HUBZone

Note 1: Small Business offerors shall include their performance as part of the small business commitment.

Note 2: The offer may provide additional tables for the Base Period and each Option Year if their intent is to increase small business participation through the life of the contact.

L4.0. VOLUME II – PAST PERFORMANCE INFORMATION

L4.1. INSTRUCTIONS

Offeror shall provide past performance information for evaluation. Failure to provide the information may result in the offeror being removed from consideration for award. (Note: An offeror with no past performance experience should submit the Volume with an explanation that they have no recent or relevant experience). The Government will evaluate past performance through an integrated analysis of the strengths and weaknesses the Government identifies in the offeror’s recent and relevant record. The other aspect of the past performance evaluation is to determine how well the contractor performed on the contracts (i.e. quality of their prior performance). The Government will evaluate past performance of the offeror’s recent and relevant contracts to determine an overall Confidence Assessment rating. In evaluating the offeror’s past performance record, the Government will use past and present performance information gathered from various sources. The sources may include, but are not limited to, the Past Performance Information Documents submitted, Past Performance Information Retrieval System (PPIRs), questionnaires, and interviews. The Government will place more weight and consideration on more relevant past performance information. For the purpose of this evaluation, the term “offeror” includes the prime offeror and/or team members and major subcontractors performing 10% or more of the effort.

L4.2. CONTENT OF PAST PERFORMANCE VOLUME

The offeror’s Past Performance Volume shall contain the following sections:

1. Table of Contents

2. Summary

3. Contractor’s Past Performance Information Documents

4. Past Performance Questionnaire (PPQ) Tracking Record

5. Past Performance Assessments

6. Consent Letters

7. Client Authorization Letters

8. Organization Structure Change History

9. Quality Awards

L4.3. TABLE OF CONTENTS

The Table of Contents shall list all documents contained in the Past Performance Volume.

L4.4. SUMMARY

The Summary shall describe the role (for the proposed C2SES III requirement) of the offeror and each subcontractor, teaming partner/joint venture partner that the offeror is required to provide Past Performance Information Documents pursuant to the paragraph below.

L4.5. CONTRACTOR’S PAST PERFORMANCE INFORMATION DOCUMENTS

Offeror's should provide past performance information on contracts and/or task orders considered most relevant in demonstrating their ability to perform the C2SES III requirements. If the offeror submits a delivery/task order as past performance, it shall be counted as one reference.