Attachment_0002,_DDD_for_ECPs_and_VECPs.doc

11/20/2017

NUMPAGES 14

DATA DELIVERY DESCRIPTION - ECP/VECP (Cont'd)

DATA DELIVERY DESCRIPTION -

ENGINEERING CHANGE PROPOSAL (ECP) AND

VALUE ENGINEERING CHANGE PROPOSAL (VECP)

This Data Delivery Description (DDD) contains the content and preparation instructions for the data product resulting from the work task specified in the contract. This DDD is used in conjunction with an Engineering Change Proposal/Value Engineering Change Proposal (ECP/VECP). A requirement for ECP/VECP submittal shall be contractually imposed in conjunction with this DDD. The same information is required for a VECP.

Requirements:

Reference Documents. The applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

Format and Content. The Engineering Change Proposal shall be prepared in contractor format, or ECP/VECP forms included as part of this DDD. ECPs that are submitted by contractor for the purpose of spare part procurement are required to use the shaded elements that are in the table below. System Technical Support (STS)/Production contractor prepared Class I ECPs are required to use all fields applicable within this DDD. If the ECP is designated as a Class II change, the minimum requirements are indicated with an “*”.

Supporting Data. In addition to the information required below, the ECP/VECP shall include supporting data. Formal ECPs/VECPs shall be supported by drawings and other data (e.g., Logistic Support Analysis (LSA) data, detailed cost proposal data, test data and analyses) as specified in the contract to justify and describe the change and to determine its total impact including assessments of changes to system operational deployment characteristics. When a life cycle cost and/or operation and support cost model has been included in the contract, the ECP/VECP shall also include the costs expected to result from the implementation of the change into all future production and spare items procured for the program. Also for all projected operation and support costs for the total inventory of items by the Government. A summary of any testing done to validate concepts or new technology to be employed in the proposed ECP/VECP shall be presented with the supporting data. Details of such test data, shall be provided if it is vital to the decision making process.

ENGINEERING CHANGE PROPOSAL (Blocks below pertain to STA FORM 1692/1)

a. The Functional Configuration Documentation (FCD) or Allocated Configuration Documentation (ACD) is affected to the extent that any of the following requirements would be outside specified limits or specified tolerances:

(1) Performance.

(2) Reliability, maintainability or survivability.

(3) Weight, balance, moment of inertia.

(4) Interface characteristics.

(5) Electromagnetic characteristics.

(6) Other technical requirements in the specifications.

NOTE: Minor clarifications and corrections to FCD or ACD shall be made only as an incidental part of the next Class I ECP/VECP NOR, unless otherwise directed by the Government.

b. A change to the Product Configuration Documentation (PCD) will affect the FCD or ACD as described in block 5a or will impact one or more of the following:

(1) Government Furnished Equipment (GFE).

(2) Safety.

(3) Compatibility or specified interoperability with interfacing Configuration Items (CIs), support equipment or support software, spares, trainers or training devices/equipment/software.

(4) Configuration to the extent that retrofit action is required.

(5) Delivered operation and maintenance manuals for which adequate change/revision funding is not provided in existing contracts.

(6) Preset adjustments or schedules affecting operating limits or performance to such extent as to require assignment of a new identification number.

(7) Interchangeability, substitutability, or replaceability as applied to CIs, and to all subassemblies and parts except the pieces and parts of non-reparable subassemblies.

(8) Sources of CIs or repairable items at any level defined by source- control drawings.

(9) Skills, manning, training, biomedical factors or human-engineering design.

c. Any of the following contractual factors are affected:

(1) Cost to the Government including incentives and fees.

(2) Guarantees or warranties.

(3) Deliveries.

(4) Scheduled milestones.

For Class II, only the ECP/VECP elements indicated with a * symbol, and the following minimum information content, are applicable:

· Name and part number of item affected

· Name and part number of next higher assembly

· Description of the engineering change

· Need (reason) for making the engineering change

Code Title Criteria for Assignment B Interface

Proposed to eliminate a deficiency consisting of an incompatibility between CIs.

C Compatibility

a. The need, for the change has been discovered during the system or item functional checks or during installation and checkout and is necessary to make the system or item work.

b. By assigning the compatibility code the contractor is declaring that the effort required to accomplish the change is considered to be within the scope of the existing contract except for changes caused by the Government.

c. Contractual coverage completing the formal documentation of the engineering change will not reflect an increase in contract price for the corrective action in production and to delivered items in-warranty or otherwise stipulated in the contract.

Note: The contractor must also notify the Government within 48 hours after determining that a compatibility change is necessary. The contractor’s message must define the need, identify factors that are impacted, and provide a preliminary estimate of cost and schedule. A formal ECP/VECP is required 30 days after the initial message. Where further procurement or manufacturing action is necessary due to lead-time considerations prior to approval of a Code C ECP/VECP, the contractor may proceed at his own risk (except where the Government caused the deficiency), after notifying the Government of the additional systems/items to be corrected.

D Correction of Deficiency

To eliminate a deficiency. Code D is used if a more descriptive code (such as S, B, or C) does not apply.

O Operational or Logistic Support

To make a significant effectiveness or performance change in operational capability or logistic support. Commonly known as an improvement change.

P Production Stoppage

To prevent slippage in an approved production schedule, where delivery to current configuration documentation is impractical or cannot be accomplished without delay.

R Cost Reduction

To provide net total life cycle cost savings to the Government and not pursuant to a contract VE clause. Code R ECPs/VECPs include cost and price of the current contract(s), plus costs resulting from associated changes in delivered items (retrofit), and life cycle logistic support.

S Safety

Correction of a deficiency that is a hazardous condition

V Value Engineering

To effect a net life cycle cost reduction, and the VECP is being submitted pursuant to the Value Engineering (VE) clause of the contract

Priority Code Criteria Emergency An emergency priority is assigned to an ECP/VECP for any of the following reasons:

(1) To effect a change in operational characteristics which, if not accomplished without delay, may seriously compromise national security;

(2) To correct a hazardous condition which may result in fatal or serious injury to personnel or in extensive damage or destruction of equipment. (A hazardous condition usually will require withdrawing the item from service temporarily, or suspension of the item operation, or discontinuance of further testing or development pending resolution of the condition); or

(3) To correct a system halt (abnormal termination) in the production environment such that Computer Software Configuration Item (CSCI) mission accomplishment is prohibited.

Urgent An urgent priority is assigned to an ECP/VECP for any of the following reasons:

(1) To effect a change which, if not accomplished expeditiously, may seriously compromise the mission effectiveness of deployed equipment, software, or forces

(2) To correct a potentially hazardous condition, the un-corrected existence of which could result in injury to personnel or damage to equipment. (A potentially hazardous condition compromises safety and embodies risk, but within reasonable limits, permits continued use of the affected item provided the operator has been informed of the hazard and appropriate precautions have been defined and distributed to the user).

(3) To meet significant contractual requirements (for example, when lead time will necessitate slipping approved production or deployment schedules if the change was not incorporated)

(4) To effect an interface change which, if delayed, would cause a schedule slippage or increase cost

(5) To effect a significant net life cycle cost savings to the tasking activity, as defined in the contract, where expedited processing of the change will be a major factor in realizing lower costs

(6) To correct a condition causing unusable output information that is critical to mission accomplishment

(7) To correct critical CI files that are being degraded

(8) To effect a change in operational characteristics to implement a new or changed regulatory requirement with stringent completion date requirements issued by an authority higher than that of the functional proponent.

Routine A routine priority is assigned to an ECP/VECP when emergency or urgent implementation is not applicable, required or justifiable.

Model or type designation, or identifier of the CI or CSCI for which proposal is being submitted. For Computer Software Configuration Items (CSCI), enter the CSCI identification number.

CAGE code *

CAGE code for the activity originating the ECP/VECP

System designation *

The system or top-level CI designation or nomenclature

ECP/VECP Number *

Provide an ECP/VECP number. Once an ECP/VECP number is assigned to the first submission of a change proposal, that number shall be retained for all subsequent submissions of a change proposal. One of the following methods of assigning ECP/VECP numbers may be used unless otherwise stated in the contract:

a. ECP/VECP numbers shall run consecutively commencing with number 1, for each CAGE Code identified activity, or ECP/VECP numbers may be assigned in a separate series for each system that the contractor is producing.

b. When an ECP/VECP is split into a basic ECP/VECP and related ECPs/VECPs, the basic ECP/VECP shall be identified with the number prescribed above and each related ECP/VECP shall be identified by the basic number.

c. Other systems may be used provided the ECP/VECP number is unique for any CAGE Code identified activity.

Type

For Class I ECPs/VECPs, indicate either a "P" for preliminary, or "F" for formal. A Class I ECP/VECP shall be preliminary if it meets the criteria below.

a. A preliminary change proposal is one that is submitted to the Government for review prior to the availability of the information necessary to support a formal ECP/VECP. It shall include a summary of the proposed change, its impact on related areas, and a justification. Examples are to furnish the Government with available information in order to permit:

(1) A preliminary evaluation relative to the merits of the proposed change

(2) (e.g. installation of a proposed change for the purpose of evaluation and testing prior to making a final decision to proceed with a proposed change); or,

(3) A determination regarding the desirability of continuing expenditures required to further develop the proposal.

(4) To provide alternative proposals; or

(5) To supplement a message relative to an emergency or urgent priority

(6) ECP/VECP when it is impracticable to submit a formal ECP/VECP within 30 calendar days; or

(7) To obtain Government approval to proceed with software engineering development prior to the development of the actual coding changes.

b. A formal ECP/VECP is the type, which provides the engineering information and other data in sufficient detail to support formal change approval/contractual implementation.

Revision *

If an ECP/VECP is being revised, enter the proper identification of the revision, i.e., R1 for the first revision; R2, R3, etc. for subsequent revisions. (The date submitted (Block 1) shall be the date of the revised ECP/VECP.)

b. For CSCI's, provide the name and identifier of each lower level CI and computer software unit affected.

b. For CSCI's, identify the CSCI version number, if known, into which the change will be incorporated. Where applicable, the effectivity of the end item CI and vehicle (aircraft, tank, ship, etc.) into which the capability represented by the new version of the software is proposed to be incorporated shall also be provided. If the impact of the ECP/VECP merits the release of a new software version include a recommendation to this effect. Serial numbers may be used in lieu of version numbers if approved by the Government.

b. Estimated kit delivery schedule. State estimated kit delivery schedule by quantity and date. When special tooling for retrofit is required for Government use, provide the dates of availability of tools, jigs, and test equipment required in conjunction with the kits to accomplish the change.

c. Ship/vehicle class affected. When the delivered CI is installed in one or more ship/vehicle classes, enter the identification of such classes.

d. Locations or ship/vehicle numbers affected. State the location(s) where retrofit is to be accomplished. If retrofit is to be accomplished in ships (or in vehicles for which the serial numbers are not shown in block 23c), enter the ship hull numbers or vehicle numbers.

NOTE: The appropriate information shall be provided for CSCI changes that are to be incorporated as part of hardware or equipment change; and implemented per a hardware retrofit schedule, or where the fielded version of the software is to be replaced.

Estimated costs/savings applicable to production of the item resulting from the change. Includes the costs of redesign of the CIs or components thereof, of factory test equipment, of special factory tooling, of scrap, of engineering design, of engineering data revision, of revision of test procedures, and of testing and verification of performance of new items.

Retrofit Costs

Estimated costs applicable to retrofit of the item including installation and testing costs. Includes retrofit-specific engineering data revision, prototype testing, kit proof testing, purchase of retrofit kits for operational systems, preparation of modification instructions, design and manufacture of special tooling for retrofit, installation of kits by contractor personnel, installation of kits by government personnel, testing after retrofit and modification, and testing and verification of performance of Government Furnished Equipment/Property (GFE/GFP).

Logistics Support Costs/Savings

Estimated costs/savings of the various elements of logistics support applicable to the item. Includes spares/repair parts rework, new spares and repair parts, supply/provisioning data, support equipment, retrofit kit for spares, operator training courses, maintenance training courses, revision of technical manuals, new technical manuals, training/trainers, interim support, maintenance manpower, and computer programs/documentation.

Other Costs/Savings

Includes estimated costs of interface changes accomplished by other contractor activities. (Do not include costs if the changes are covered by related ECPs/VECPs by other contractors. Also includes estimated costs of interface changes accomplished by the Government for changes which must be accomplished in previously delivered items (aircraft, ships, facilities, etc.), other interfacing products, and/or retrofit of GFE/GFP, to the extent that such costs are not covered under production, retrofit, or logistics support.

a. Title and name of submitting activity

NOTE: BLOCKS 27-31 ARE ONLY FILLED IN IF THE SYSTEM SPECIFICATION IS IMPACTED.

ENGINEERING CHANGE PROPOSAL (Blocks below pertain to STA FORM 1692/2)

a. Other systems affected. Provide only if other systems/configuration items are affected as indicated in Block 10.

b. Other contractors/activities affected. Identify other contractors or Government activities that will be affected by this engineering change.

c. Configuration items affected. Enter the names and numbers of all CIs, maintenance and operator training equipment, and support equipment affected.

d. Effects on performance allocations and interfaces in system specification. Describe the changes in performance allocations and in the functional/physical interfaces defined in the system specification.

e. Effects on employment, integrated logistic support, training, operational effectiveness, or software.

(1) For hardware, describe the effects of the proposed change on employment, deployment, logistics, and/or personnel and training requirements which have been specified in the approved system and/or CI specifications, including any changes or effects on the operability of the system. In particular, there shall be an entry detailing any effect on interoperability.

(2) For CSCIs, the following information shall be entered as applicable to the degree of design development of the CSCI at the time of ECP/VECP submission:

(a) Identify any required changes to the data base parameters or values, or to data base management procedures;

(b) Identify and explain any anticipated effects of the proposed change on acceptable computer operating time and cycle-time utilization;

(c) Provide an estimate of the net effect on computer software storage; and,

(d) Identify and explain any other relevant impact of the proposed change on utilization of the system.

b. For CSCIs, identify the scheduled sequence of computer software design and test activities, which will be required. ECPs/VECPs initiated after preliminary design which affects the FBL and/or the ABL shall identify, as appropriate, significant requirements for computer software redesign, recoding, repetition of testing, changes to the software engineering/test environments, special installation, adaptation, checkout, and live environment testing. In addition, the specific impact of these factors on approved schedules shall be identified. The impact of the software change on the hardware design and input/output cabling shall also be detailed.

Solutions.

Summary of the various solutions considered and reasons for adopting the solution proposed by the ECP/VECP. When analysis addresses new concepts or new technology, supporting data may be presented with the proposal to authenticate the trade-off analysis.

a. Production

b. Retrofit

ENGINEERING CHANGE PROPOSAL (Blocks below pertain to STA FORM 1692/3)

a. Effects on schedule and content of the ALS plan.

b. Effect on maintenance concept and plans for the levels of maintenance and procedures.

c. System and/or CI logistics support analysis (LSA) tasks to be accomplished and LSA data requiring update wherever it exists in the contract. (MIL-PRF-49506).

d. Extension/revision of the interim support plan.

e. Spares and repair parts that are changed, modified, obsoleted or added, including detailed supply data for interim support spares. NOTE: Failure to include detailed supply data will delay ECP/VECP processing.

f. Revised or new technical manuals.

g. Revised or new facilities requirements and site activation plan.

h. New, revised, obsoleted or additional support equipment (SE), test procedures and software. For items of SE and trainers, which require change, furnish a cross reference to the related ECPs/VECPs, and for any related ECP/VECP not furnished with the basic ECP/VECP, furnish a brief description of the proposed change(s) in SE and trainers.

i. Qualitative and quantitative personnel requirements data which identify additions or deletions to operator or maintenance manpower in terms of personnel skill levels, knowledge and numbers required to support the CI as modified by the change.

j. New operator and maintenance training requirements in terms of training equipment, trainers and training software for operator and maintenance courses. This information should include identification of specific courses, equipment, technical manuals, personnel, etc. required to set up the course at either the contractor or Government facility.

k. Any effect on contract maintenance that increases the scope or dollar limitation established in the contract.

l. Effects on packaging, handling, storage, and transportability resulting from changes in materials, dimensions, fragility, inherent environmental or operating conditions.

a. Interfaces having an effect on adjacent or related items, (output, input, size, mating connections, etc.).

b. GFE or Government Furnished Data (GFD) changed, modified or obsoleted.

c. Physical constraints. Removal or repositioning of items, structural rework, increase or decrease in overall dimensions.

d. Software (other than operational, maintenance, and training software) requiring a change to existing code and/or, resources or addition of new software.

e. Rework required on other equipment not included previously which will effect the existing operational configuration.

f. Additional or modified system test procedures required.

g. Any new or additional changes having an effect on existing warranties or guarantees.

h. Changes or updates to the parts control program.

i. Effects on life cycle cost projections for the configuration item or program, including projections of operation and support costs/savings for the item(s) affected over the contractually defined life and projections of the costs/savings to be realized in planned future production and spares buys of the item(s) affected.

a. Production

b. Retrofit

ENGINEERING CHANGE PROPOSAL (Blocks below pertain to STA FORM 1692/4)

a. Production Costs/Savings Summary. Estimated costs/savings applicable to production of the item resulting from the change. Includes the costs of redesign of the CIs or components thereof, of factory test equipment, of special factory tooling, of scrap, of engineering design, of engineering data revision, of revision of test procedures, and of testing and verification of performance of new items.

b. Retrofit Costs. Estimated costs applicable to retrofit of the item including installation and testing costs. Includes retrofit-specific engineering data revision, prototype testing, kit proof testing, purchase of retrofit kits for operational systems, preparation of modification instructions, design and manufacture of special tooling for retrofit, installation of kits by contractor personnel, installation of kits by government personnel, testing after retrofit and modification, and testing and verification of performance of Government Furnished Equipment/Property (GFE/GFP).

c. Logistics Support Costs/Savings. Estimated costs/savings of the various elements of logistics support applicable to the item. Includes spares/repair parts rework, new spares and repair parts, supply/provisioning data, support equipment, retrofit kit for spares, operator training courses, maintenance training courses, revision of technical manuals, new technical manuals, training/trainers, interim support, maintenance manpower, and computer programs/documentation.

d. Other Costs/Savings. Includes estimated costs of interface changes accomplished by other contractor activities. (Do not include costs if the changes are covered by related ECPs/VECPs by other contractors. Also includes estimated costs of interface changes accomplished by the Government for changes which must be accomplished in previously delivered items (aircraft, ships, facilities, etc.), other interfacing products, and/or retrofit of GFE/GFP, to the extent that such costs are not covered under production, retrofit, or logistics support.

e. Subtotal costs/savings. Enter the subtotals of columns 1, 4, 5, and 6 on this line. The subtotal in column 5 shall be the sum of columns 1 and 4. This subtotal under the contract then shall be entered on the line so titled in column 6, and in Block 24, page 1.

f. Coordination changes with other contractors. This term applies to interface changes to items other than GFE, and changes to GFE being covered under 46b.

g. Coordination changes by Government. Enter in this block an estimate of the cost to the Government of interface changes which must be accomplished in delivered items (aircraft, ships, facilities, etc.) to the extent such costs are not covered in Block 46b.

h. Estimated Net Total Costs/Savings. Enter the sum of all cost savings on column 6 and in Block 25, page 1.

ENGINEERING CHANGE PROPOSAL (Blocks below pertain to STA FORM 1692/5)

RESPONSIBILITY FOR PREPARATION:

(1) Prime contractor. The prime contractor shall summarize the costs/savings of all related ECPs/VECPs for which the contractor is responsible. If there is no system integrating contractor, the prime contractor submitting the basic ECP/VECP shall include the costs of related ECPs/VECPs being submitted by other affected contractors to the extent such information is available.

(2) System integrating contractor. When a system integrating contractor (or coordinating contractor) has contractual responsibility for ECP/VECP coordination, the contractor shall summarize the costs of related ECPs/VECPs of the several primes involved in an interface or interrelated ECP/VECP.

SUMMARIZATION TECHNIQUES.

The costs of certain related ECPs/VECPs are entirely ALS costs. Costs of ECPs/VECPs for trainers, other training equipment and SE shall be listed in total under the “ILS costs” heading. Other ECPs/VECPs (applicable to weapons, aircraft, tanks, and subsystems thereof, etc.) shall be split into the four subtotals of “production,” “retrofit,” ‘ALS,” and ECP/VECP Form Page 5. The sum of the four subtotals attributed on Page 5, column (3), to an individual ECP/VECP should agree with the subtotal of costs/savings under contract, line e, column (5) of STA Form 1692/4 of that ECP/VECP. Cost breakdowns should be arranged in such manner that costs/savings are neither included more than once on the summary nor omitted. The purpose of the grouping on the cost summary is to arrive at a total ALS cost, and a net total cost of all actions for the entire group of related ECPs/VECPs. If more related ECPs/VECPs will have to be summarized than there is room available in the blocks on the form, the summarization of each cost area shall be accomplished on a separate enclosure and the total for that cost area entered on the subtotal line for that area on the STA Form 1692/5.

SOFTWARE CHANGES ONLY.

This form shall not apply in the case where all related ECPs/VECPs being summarized refer to software changes only. However, a separate page(s) shall be provided with the ECP/VECP detailing the summary of the individual CSCI costs/savings for each of the related ECPs/VECPs, grouped by the cost areas, and providing the total costs/savings for all of the related software ECPs/VECPs.

a. Production costs/savings. Enter the ECP/VECP number in column (2). Enter the production subtotals from columns (5) and (6) of Block 46a of each ECP/VECP applicable to weapons, aircraft, tanks, subsystems thereof, etc. in columns (3) and (4) respectively. (Note that total costs of ECPs/VECPs on trainers, training equipment, and SE are entered in Block 47c.)

b. Retrofit costs. Retrofit costs may be charged by the Government to production funds or maintenance funds or may be split between the two. The type of funds used depends upon the phase in the items life cycle. If the practice of the Government in this regard is known to the originator of Page 5, retrofit costs shall be entered in, or split between, Blocks 47b and 47c.1, as appropriate. If such practice is unknown, enter in Block 47b the ECP/VECP number and the retrofit subtotals from the columns (5) and (6) of Block 46b for each applicable ECP/VECP.

c. ALS costs/savings. Enter retrofit costs in Block 47c.1, if appropriate. Enter in Block 47c.2 the ALS subtotals from columns (5) and (6) of Block 46c of each ECP/VECP applicable to weapons, aircraft, tanks, subsystems thereof, etc. Enter costs of ECPs/VECPs for ALS items in Blocks 47c, 3, 4, 5 and 6. Enter costs of revision or preparation of ALS plans and LSA records for the CI or complete system in Block 47c.7. Enter in Block 47c.9 costs of revision of the interim support plan to the extent such costs have not already been covered under Block 46c of STA Form 1692/4 of the applicable ECPs/VECPs. Enter in Blocks 47c.10 through 47c.18 the costs of all new requirements for ALS not covered by ECPs/VECPs, such costs being broken down into nonrecurring and recurring costs, as appropriate, and totaled in column (3).

d. Other costs/savings. Enter in Block 47d the sum of the “other costs” totals from column (5) and (6) of Block 46d of each ECP/VECP applicable to weapons aircraft, tanks, subsystems thereof, etc. Enter the subtotals of columns (3) and (4) on this line. The subtotal under contract(s) shall then be entered on the line so titled in column (4).

e. Estimated net total costs/savings. Enter the sum of the preceding two lines of column 4.

ENGINEERING CHANGE PROPOSAL ENCLOSURE LIST (Blocks below pertain to STA FORM 1692/6)

b. Enter document item number (part number).

c. Enter latest document date.

d. Enter CAGE Code.

Enter pending ECP/VECP number, if applicable.

b.

Check box Yes if there is a conflict between ECP/VECP and pending ECP/VECP; Check box No if there are no pending ECPs/VECPs

Check corresponding End Items or Models Affected, if known using the Legend Code.

b.

Annotate End Item or Models Affected from block 51a.

c.

Check applicable changes that affect the change proposal.

ECP/VECP/DEVIATION INTERCHANGEABILITY FACTORS (Blocks below pertain to STA FORM 1692/7)

b. Enter N for New, or C for Canceled for applicable part number.

c. Enter Replacement part number, if applicable.

d. Enter the up assembly used.

e. Check box for YES; leave box blank for NO if the new part interchanges with the old part number.

f. Check box for Yes; leave box blank for NO if the old part number interchanges with the new part number.

g. Check box for YES; leave box blank for NO if either part number can be reworked to interchange with the other.

h. Check box for YES; leave box blank for NO if one part number can be interchanged with the other by combining with other parts.

i. Check box, if applicable.

j. Check box, if applicable.

k. Check box, if applicable.

l. Check box, if applicable.

m. Enter remarks, if applicable.

n. Enter date.

o. Enter total number of pages per enclosure list.

2:04 PM 11/20/2017

PAGE

2:04 PM 11/20/2017