HC1028-13-R-0046-0001.docx

HC1028-13-R-0046

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

QUESTIONS / ANSWERS

INDUSTRY QUESTIONS AND GOVERNMENT ANSWERS (Q&A’s)

Amendment 1

1. RFP - Would the government consider increasing the page limit for the technical/management volume to 25 pages? Given the number of performance requirements and the scope of the solution, we believe that offerors would be able to provide more complete responses with the increase.

Answer: The government will increase the page limit on the technical/management volume to 20 pages.

1. RFP, Section A.1.4 –Would the government reconsider the requirement to resolve assumptions only through questions and answers? Since questions are shared among all vendors, there is sometimes a reluctance to ask questions that might reveal a strategy or other advantage.

Answer: No – the government will not reconsider.

1. PWS, Section 6., capability 2 – Does the government require a separate centralized database for each of the SIPR and NIPR discovered components or will all data be stored in a single database? If so, will cross domain transfers be covered by the government or does the proposal need to accommodate it?

Answer: Yes - the government requires a separate centralized database for each of the SIPR and NIPR discover components. No – cross domain transfers are not required for the solution scope in this solicitation.

1. PWS, Section 6., capability 19 – Would the government please clarify and provide more detail of what “monitor” means for the solution? Is the government looking for an active monitoring solution to detect changes to baseline service models?

Answer: Monitor indicates a requirement to discover any change during an initial discovery, a regularly occurring scheduled discovery or an adhoc discovery as determined by an authorized user.

1. PWS, Section 6.1 and 6.4 – Will each of the 900 users listed require training or only those specified in section 6.4? Can you provide a breakout of the number of users that will be required to administer and the number that will just be users (viewers) of the data?

Answer: Only the users listed in section 6.4 will require training by the vendor. An estimated 102 users will have varying levels of administration duties.

1. PWS, Section 6.3 – Please clarify whether the sixteen services defined represent 16 specific business applications, or, is DISA looking for just the discovery of the components listed?

Answer: Section 6.3 represents 16 specific business applications; DISA requires the solution to meet each requirement designed to discover these specific business applications accurately and in their entirety.

1. PWS - Do the ITSM modules (IM, PM and CM) need to interact with discovered data in the BAM repository?

Answer: The requirement includes integration with DISA’s instances of ITSM. The intent is for BAM data to interact with ITSM to create relationships between existing ITSM OE records, communication device records and storage device records based on matching key data.

1. PWS - Have the mappings and relationships between business applications and business services already been identified?

Answer: POCs for these applications have varying level of information regarding the relationship maps for these business services.

1. PWS, Section 6.3 - What does “non-consecutive days of on-site installation support” imply? Does that mean that contractor personnel cannot be performing installation activities on consecutive days?

Answer: The offeror is not required to be on site for the entire installation period. The environments are transitioned to site technical staff for security reviews at multiple points during the installation and configuration processes. The security reviews can take several days. The contractor does not need to be on site on the days where this review is being completed.

1. PWS - What type of MAC level and COOP (failover) environment is the government asking for? MAC Level II? RTO/RPO=24 hours? Or will the ADDM application reside on current ITSM infrastructure for which there is already MAC and COOP levels defined?

Answer: The MAC level for this system is MAC III. The solution will reside on infrastructure as designed during the engineering phase of the project.

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

SECTION A - RFP INFORMATION

A.1.1. Defense Information Technology Contracting Organization (DITCO) is issuing a Request for Proposal (RFP) /solicitation for a Commercial Off-The-Shelf (COTS) Business Application Mapping (BAM) Solution, in support of Defense Information Systems Agency (DISA).

A.1.2. The RFP HC1028-13-R-0046 responses are due no later than Wednesday, November 13, 2013, 3:00PM, CST. See section L for further delivery instructions. Questions pertaining to this RFP shall be submitted electronically to christopher.p.jordan13.civ@mail.mil not later than Wednesday, November 4, 2013, 3:00PM, CST. The Government cannot guarantee a response to any questions received after this date/time.

A.1.3. DITCO/PL8321 is requesting proposals from qualified contractors who can provide a BAM solution. The agency will award a Firm-Fixed-Price contract using the best value criteria in section M. The government reserves the right to make award to one contractor, or to make no award in respond to this solicitation.

A.1.4. In response to this RFP, no terms, conditions or assumptions will be entertained. All issues will be resolved with questions and answers. Submission of terms, conditions or assumptions included in your proposal may be cause for your proposal to be determined non-responsive to this RFP and may be excluded.

SECTION G - CONTRACT ADMINISTRATION DATA

52.204-9000 Points of Contact As prescribed in 4.103(S-90), insert the following clause:

POINTS OF CONTACT (AUG 2005)

Contracting Officer Name: Lisa O’Donnell Organization/Office Symbol: DISA/DITCO-PL8321 Phone No.: (618) 229-9721 E-Mail Address: lisa.a.odonnell4.civ@mail.mil

Contract Specialist Name: Christopher Jordan Organization/Office Symbol: DISA/DITCO-PL8321 Phone No.: (618) 229-9714 E-Mail Address: christopher.p.jordan13.civ@mail.mil

Government Customer Point of Contact Name: Amy Spande Organization/Office Symbol: DISA ESD Phone No.: (303) 224-1796 E-Mail Address: amy.c.spande.civ@mail.mil

Contractor Point of Contact Contractor Legal Business Name: **TO BE COMPLETED BY OFFEROR**

DUNS:

CAGE CODE:

Contractor POC:

E-Mail Address:

Phone Number:

Fax Number:

(End of clause)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

INFORMATION TO OFFERORS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 INFORMATION TO OFFERORS AND INSTRUCTIONS FOR PROPOSAL PREPARATION

L.1.0 General Instructions

(a) This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS). Non-conformance with the instructions provided in this Information to Offerors may result in an unfavorable proposal evaluation and/or removal from consideration for award.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror's proposal.

L.2.0 General Information

L.2.1 Point of Contact The contracting officer (KO) and the contract specialist are the only points of contact for this procurement. Address any questions or concerns you may have to the KO and contract specialist. Written requests for clarification must be sent to the KO at the address located in Section A of this solicitation.

L.2.2 Discrepancies If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO in writing with supporting rationale as well as the remedies the offeror is asking the KO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

L.2.3 Electronic Reference Documents All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov.

L.2.4 Communications Exchanges of source selection information between Government and offerors will be controlled by the KO and/or contract specialist. Emails may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. E-mail is the sole means of official communication unless authorized by the KO.

L.2.5 Organization/Number of Copies/Page Limits The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 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.2. The attachments identified in the table shall be contained in individual documents/files, as necessary. The contents of each proposal volume are described in the information to offerors paragraph as noted in the table below.

Table 2.2 - Proposal Organization

Number

L.2.6 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 excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of the proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this solicitation. Each page shall be counted except the following: The cover page, table of contents, list(s) of tables and drawings.

L.2.7 Page Size and Format A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be in Times New Roman font. Except for the reproduced sections of the solicitation document, the text size shall be no less than 10 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs.

L.2.8 Cost or Pricing Information All cost or pricing information shall be addressed in the Cost/Price Proposal and Contract Documentation Volumes. All formulas shall remain present in the spreadsheet for verification. The file size of each document shall not exceed 2MB. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this RFP.

L.2.9 Classified Information We are not accepting classified proposals for this requirement.

L.2.10 Cross-Referencing To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

L.2.11 Indexing Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

L.2.12 Glossary of Abbreviations and Acronyms Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L.3.0 Proposal Submission Prior to submitting proposals, the offerors are required to be register in the System for Award Management, www.sam.gov.

L.3.1 Electronic Offers

a. Proposal Submission: In order to respond to this solicitation, the offeror provide a complete proposal to christopher.p.jordan13.civ@mail.mil and betty.a.burris4.civ@mail.mil not later than the time and date specified in Section A of this RFP.

b. Complete Proposal: Indicate on each file the volume number and title (i.e. Volume I Executive Summary). Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit Volumes I through V. In accordance with Section L and FAR 52.212-1, Instructions to Offerors, the offeror’s proposal submission will be considered complete when all Parts are received.

c. RFP Questions: Additional questions pertaining to this RFP shall be submitted electronically to christopher.p.jordan13.civ@mail.mil and betty.a.burris4.civ@mail.mil not later than the time and date specified in Section A of this RFP. The Government cannot guarantee a response to questions received after this date/time.

d. Electronic Files: If necessary, separate the electronic files of the proposal at logical breakpoints using the table of contents as a guide. Each file must be autonomous and complete.

e. Virus Check: Offerors shall perform a virus check prior to proposal submittal. Virus checking will be conducted at the source selection site prior to the beginning of the evaluation using the current version of Norton Antivirus.

f. Clarification of Proposals: All changes resulting from clarifications to the proposal will be submitted on a page-by-page basis. Each page change should contain a revision date located in a uniform location. Submissions will follow the electronic format.

g. Freedom from Ambiguity: The information supplied shall be closely aligned with the procurement under consideration and shall be free from ambiguities. Ambiguous statements or statements with dual meanings will be interpreted in their most stringent or unfavorable sense.

h. Proposal Preparation Cost: The RFP does not commit the Government to pay any cost for the preparation and submission of a proposal in response to this RFP. The KO is the only individual who can legally commit the Government to the expenditure of public funds in connection with this procurement.

i. BAM Solution Testing: Testing will require Offerors that have been notified by the Contracting Officer that they are in the competitive range (in the event the Government elects to establish a competitive range and to not award based on initial proposals) to provide their proposed COTS solution for testing. Offerors that have been notified as having been placed in the competitive range will be required to send their solution to DISA as described in solicitation Attachment J-2. After the Contracting Officer's notice and testing instructions are provided to contractors in the competitive range, remaining contractors will have 15 days to deliver their solution to DISA ESD, 5450 Carlisle Pike, Mechanicsburg PA 17055 (mainframe testing), and 8705 Industrial Blvd, Oklahoma City, OK 73145 (server testing). Additional information and Point of Contact regarding these locations will be included in the testing invitations. Testing will then proceed in accordance with Attachment J-2 Test Plan. The objective of the Testing is to validate the offeror’s proposal. The testing will be fully documented and included as part of the final technical evaluation.

Additional Instructions include:

(A) Location of Testing: Offerors’ solution will be shipped to testing locations at 5450 Carlisle Pike, Mechanicsburg PA 17055, and 8705 Industrial Blvd Oklahoma City, OK 73145 facility.

(B) Representation at Testing: Each offeror may be represented by no more than 2 people per site. The Offeror is required to set up their solution during time of testing. During the testing process, any minor assistance given to offerors by the testing staff, or any comment or questions that take place during testing, will not constitute as an exchange (such as: clarifications, discussions or other communications) with offerors as discussed in FAR 15.306. Any such FAR 15.306 exchanges will solely be issued by the KO or Contract Specialist.

(C) Schedule: Each solution will be allotted sixteen (16) working days for integration and requirements evaluation. On day one, the Contractor will present an overview of their solution to the government evaluation team and for the remainder of the first week, assist the integration team with installation and proper configuration of their solution in the Government test environment.

Contractors will be provided with a detailed testing schedule and will be expected to be available by phone for the test phases for their product. Each Contractor will be given the same amount of time to complete the test activities as every other Contractor.

(D) Scenario: The Schedule for a given Requirement Evaluation session is sixteen (16) working days and will follow the same phases:

The Testing shall validate the solution/product integration and the ability/approach for meeting all security/functionality requirements in a DISA STIGed environment. The testing is designed to validate the offeror’s proposal and enhance the Government’s understanding of the proposal. The offeror is providing a BAM solution as stated in the PWS. The offeror will be responsible for shipping their solution. The offeror is required to supply two full sets of their proposed solution to support testing. This includes all products required to verify their BAM solution in accordance with the PWS, such as, software, necessary licenses, documentation, and hardware/appliances/cables (if part of the solution) as required. Both sets will be used for SRR/SAAT and Functional End-to-End testing. The Offeror is responsible for cost associated with the proposal submission. The Government is not responsible for cost of shipping, personnel attendance or any other requirements during the testing period or preparation of proposal.

L.3.2 Volume I Executive Summary The offeror shall provide an executive summary that describes the significant attributes and theme of its proposal. The Executive Summary shall not be more than five (5) pages.

L.3.2.1 Narrative Summary The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L.3.2.2 Table of Contents Include a master table of contents of the entire proposal.

L.3.3 Volume II – Technical/Management Volume

The Technical/Management Volume should be specific and complete. Your responses will be evaluated against the technical/management subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

The technical proposal should include all information the offeror desires the Government to consider/evaluate, regarding capability to meet the PWS. The proposal should address all aspects of the PWS. The proposal should be prepared simply and economically, providing straightforward, concise delineation of capabilities to perform satisfactorily the contract being sought. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired. The Technical/Management volume shall not be more than 15 pages.

The proposal shall not merely offer to perform work in accordance with the proposed PWS, but shall outline the actual approach proposed as specifically as possible. Particular proposal strengths or unique approaches should be highlighted. Repeating the requirements without sufficient elaboration will not be acceptable. You are not limited to any suggested approaches for equal or even preferred consideration; however, any deviations should be fully substantiated in the proposal. In order to ensure a complete proposal, it is recommended that the offerors follow the format presented below and outline their response by Subfactor. Additionally, the offeror should cross-index its proposal elements to the evaluation criteria listed in Section M. It is the offerors’ responsibility to ensure the completeness of its proposal. The evaluation team for the Government has been instructed to evaluate on the basis of the information provided in the proposal. The Government shall not assume that an offeror possesses any capability unless specified in the proposal.

L.3.3.1 Technical/Management In the Technical/Management volume, address your proposed in accordance with the PWS and your approach to meeting or exceeding the minimum performance or capability requirements of each technical/management subfactor, as well as the risks in your proposed approach in terms of technical/performance, cost, and/or schedule.

The proposal may not merely offer to perform work in accordance with the proposed PWS, but must outline the actual approach proposed as specifically as possible. Particular proposal strengths or unique approaches should be highlighted. Repeating the requirements in the PWS, without sufficient elaboration will not be acceptable. You are not limited to any suggested approaches for equal or even preferred consideration; however, any deviations should be fully substantiated in the proposal. In order to ensure a complete proposal, it is recommended that the offerors follow the format presented below and outline their response by Subfactor. Additionally, the offeror should cross-index its proposal elements to the evaluation criteria listed in Section M. It is the offerors’ responsibility to ensure the completeness of its proposal. The evaluation team for the Government has been instructed to evaluate on the basis of the information provided in the proposal. The Government will not assume that an offeror possesses any capability unless it is specified in the proposal.

L.3.3.2 Technical/Management Risk Address technical/management risk by identifying those aspects of the proposal you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Classify each risk in accordance with the DISA Source Selection Procedures, paragraph 4.5.1.2. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (e.g., PWS), whether or not those requirements are identified as subfactors. Propose a realistic "workaround" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

L.3.3.3 Volume Organization The Technical/Management volume shall be organized according to the following general outline:

Subfactor 1.1: Technical Solution Subfactor 1.2: Implementation Subfactor 1.3: Integration Subfactor 1.4: Operational Solution

Subfactor 1.1, 1.2, 1.3, 1.4:

Subfactor 1.1 The contractor demonstrates a complete understanding and offers a technical solution to fully meet or exceed technical requirements outlined in the PWS sections 6 and 7 - Performance Requirements, Software Licenses, Maintenance Support and Performance Standards.

Subfactor 1.2 The contractor shall demonstrate in their proposal a complete understanding and plan and for providing the required support, to fully meet or exceed the services required to map all of the business applications/services outlined in the PWS in section 6.3 - Implementation of Business Application Mapping/Dependency Mapping Solution.

Subfactor 1.3 The contractor shall demonstrate in their proposal a complete understanding and plan for providing the required support for the design, configuration, DISA Enterprise ITSM integration, and transition as outlined in the PWS sections 6.3 and 6.4.

Subfactor 1.4 The contractor shall demonstrate in their proposal, and will be tested on, their COTS solution's operational/functional ability to integrate into DISA environment as outlined in PWS section 6.

L.3.4 Volume III - Past Performance Past Performance information shall include either commercial or government contracts performed within three (3) years prior to the date of release of the solicitation, and having requirements/objectives similar in size and scope to the requirements of the performance work statement. The past performance information may include both the prime offeror’s and the subcontractor’s efforts. The offeror shall each provide no more than three (3) past performance references using the Past Performance Form Attachments J-3. The offeror shall provide names, addresses (including email addresses), facsimile, and telephone number(s) of point of contacts (POCs) who have detailed and in-depth knowledge of the work performed on the referenced contract (and/or task order). No more that the first three (3) past performance references will be reviewed or evaluated for this requirement. If an offeror has no current or relevant past performance information, then the proposal should state this information in this part or volume.

NOTE: The Government reserves the right to obtain information relative to present and past performance on its own, in addition to that provided by the contractor.

L.3.5 Volume IV - Cost/Price The Offeror shall submit a cost/price proposal containing their proposed unit prices and total cost of each CLIN/SLIN in Section B. The Offeror’s cost/price proposal shall be complete, submitting prices for all of the CLIN/SLINs identified for the entire contract period (i.e., the one year basic period, four one year options and include 6 month extension IAW FAR 52.217-8 ), to include all formulas and calculations. Failure to price all of the requirements in the CLIN’s may result in rejection of the Offeror’s proposal.

In addition, the Offeror shall provide supporting data in a separate document that provides a detailed break-out of the proposed CLIN/SLIN price in Section B. Offerors should ensure price proposals include detailed information regarding the resources required to accomplish the task (e.g., labor categories, labor hours, number of employees for each labor category, rates, travel, incidental equipment, etc.). The cost/price proposal spreadsheet shall be a separate document from the technical proposal.

Offeror’s cost/price proposal shall be complete, submitting prices for all of the CLIN/SLINs identified for the entire contract period to include all formulas and calculations. Failure to price all of the requirements in the CLIN’s may result in rejection of the Offeror’s proposal.

Offerors shall propose a fixed price payment plan commensurate with the value of the deliverables and/or significant milestones in the PWS for Implemetation of this requirement (CLIN 0002). A firm fixed price payment plan with the total dollar amount divided into twelve (12) equal monthly payments will not be accepted.

Offerors are instructed to propose travel cost but it will not be included as part of the evaluation. Actual travel shall be authorized by the Contracting Officer’s Representative (COR) in writing prior to performance and will be paid IAW the Joint Travel Regulations and FAR Part 31.205-46. The eventual awardee will be authorized to invoice monthly for all approved travel costs incurred and approved by the COR. Clauses can be viewed on http://farsite.hill.af.mil.

Copies of the offerors commercial price list shall be included with the Offeror’s Volume V, so the prices proposed can be cross-referenced to the commercial price list. All items proposed must be identified on the offerors commercial price list. Because of the competitive nature of this solicitation, this supporting documentation shall be considered information other than cost or pricing data. According to FAR 15.403-5, information other than cost or pricing data may be submitted in the Offeror’s own format unless the contracting officer decides that use of a specific format is essential and the format has been described in the solicitation. For this solicitation, the Offeror may choose the format of the supporting information.

L.3.6 Volume V Contract Documentation Contains the information necessary to award prior to contract award, Volume V documents shall be reviewed and verified as accurate and consistent with the Offeror's proposal. No page limitation applies to Volume V. All proof of certifications as required in the PWS.

Transmittal Letter identifying the Name of the Offeror, Taxpayer Identification (TIN), DUNS Number, Cage Code, Complete Mailing Address, Remittance Address and e-mail address and telephone number for two Points of Contacts for the RFQ. Points of Contacts are limited to two. Offerors shall include a copy of their commercial prices list from which the prices are being quoted. The Offeror must demonstrate that every item quoted is on their commercial price list. If you fail to provide you will not be considered for award. At a minimum the Prime should consider, if available, at least one small business, veteran-owned small business, service disabled veteran-owned small business, HUBZone small business, women-owned small business, or small disadvantaged business schedule contractor(s).

This section is to include a signed copy of this Solicitation/Contract/Order for Commercial Items, Page 1.

L.4. Discussions.

The Government intends to evaluate proposals and award a contract without discussions with offerors. However, the Government reserves the right to conduct discussions or seek clarifications if the KO later determines them to be necessary. In the event issues pertaining to a proposed task cannot be resolved to the satisfaction of the KO, the KO reserves the right to withdraw and cancel the proposed task. In such event, the contractor shall be notified in writing of the KO’s decision.

(End of Summary of Changes) image1.wmf